Import Alignment (.landxml)
Access an Example Steel Bridge Model
Follow the steps below to open the Steel I-Girder Training Example.
Log in to your account and locate Project in the top-right corner.
Click Project, then click NEW in the top-left corner.
Under Example Project, click New Project within Steel I-Girder Training Example.
Provide a name for your project and open the example.
The initial download of the library components takes approximately 2 minutes 30 seconds. Subsequent openings of the same project are noticeably faster because OpenBrIM library objects are cached in your browser; loading then takes less than 2–3 seconds.
Import Alignment from a LandXML File
Before Importing a LandXML File
LandXML files may contain a Geographic Coordinate System (GCS) defining the roadway alignment. Take the steps below before importing so the bridge generates in the correct location. This is especially important when building a federated model — a single coordinated model assembled from several OpenBrIM projects (for example, alignment in one project, bridge data in another).
Set the GCS: ensure the GCS of the LandXML file matches the OpenBrIM project's GCS.
Verify the alignment: confirm that the roadway alignment and coordinate data in the LandXML file are consistent with the OpenBrIM project setup. This prevents misalignment in the final model.
Set the project's Geographic Coordinate System before importing:
Once the GCS is set, you can import the LandXML file.
Follow the steps below to import an alignment from a LandXML file.
Download the example file used in the steps below: ExampleAlignment2.xml. Click the file, then click the download icon in the top-right of the screen.
Click the three-dot menu in the top-left, just to the left of the project name, and select Import.
Alternative entry point: click DATA in the bottom-middle to open the spreadsheet.
Click Bridge Alignment under Roadway Alignment in the workflow tree. The spreadsheet lists all alignments in the project.
Click the cell showing ALIGNMENT1. Open the three-dot menu that appears on the right of the cell and select Import LandXML.
In the file dialog, select one XML file (you can import only one at a time). The example file is ExampleAlignment2.xml.
When the import finishes, a confirmation appears. Click Close to view the imported alignment.
The imported alignment follows a different route. The bridge is still set to ALIGNMENT 1.
To switch the bridge to the new ALIGNMENT 2, click DATA in the bottom-middle to open the spreadsheet. The workflow tree appears on the left.
In the workflow tree, click Bridge Alignment under Bridge Geometry to view all alignments in the project.
Alignment 1 is currently set for the BRG1 bridge.
Click the cell showing ALIGNMENT1. The three-dot menu appears on the right of the cell.
Open the three-dot menu. At the bottom of the panel you'll see Set to None, Set to ALIGNMENT1, and Set to ALIGNMENT2. Click Set to ALIGNMENT2.
BRG1 is now set to ALIGNMENT2.
The spreadsheet appears on the right and the workflow tree on the left.
To resize the spreadsheet, click and hold the DATA button and drag.
To close it, click the DATA button once.
To hide roadway surfaces (so alignments display as lines only), click the gear icon in the bottom-left and choose Hide Roadway Surface.
If too many alignments exist for the inline picker, the menu shows Select instead — click it to choose from a list.
After Importing the LandXML File
You have two options for tying the alignment's coordinates to the project's local origin:
Use the alignment's Latitude and Longitude as the Project Local Origin.
image-20241106-144940.png Use the Project Origin's latitude and longitude for the alignment's latitude and longitude.
image-20241106-145054.png
For a federated model, the Set Project Local Origin to Alignment Latitude and Longitude option is strongly recommended so all related projects share the same local origin and remain spatially consistent.
Setting the Local Origin of a Project
To set the local origin for a project, follow the screenshots below.
Last updated