# Import Alignment (.landxml)
## Access an Example Steel Bridge Model
{% hint style="info" %}
Follow the steps below to open the **Steel I-Girder Training Example**.
{% endhint %}
1. Log in to your account and locate **Project** in the top-right corner.
2. Click **Project**, then click **NEW** in the top-left corner.
3. Under **Example Project**, click **New Project** within **Steel I-Girder Training Example**.
4. Provide a name for your project and open the example.
{% hint style="warning" %}
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**.
{% endhint %}
***
## 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.
{% hint style="info" %}
Follow the steps below to import an alignment from a LandXML file.
{% endhint %}
1. Download the example file used in the steps below: [ExampleAlignment2.xml](https://openbrim.atlassian.net/wiki/spaces/OBrIM/pages/2231304203/Import+Alignment+.landxml+QG-2?preview=%2F2231304203%2F2231927204%2FExampleAlignment2.xml). Click the file, then click the download icon in the top-right of the screen.
2. Click the three-dot menu in the top-left, just to the left of the project name, and select **Import**.
3. Alternative entry point: click **DATA** in the bottom-middle to open the spreadsheet.
4. Click **Bridge Alignment** under **Roadway Alignment** in the workflow tree. The spreadsheet lists all alignments in the project.
5. Click the cell showing ***ALIGNMENT1***. Open the three-dot menu that appears on the right of the cell and select **Import LandXML**.
6. In the file dialog, select one XML file (you can import only one at a time). The example file is **ExampleAlignment2.xml**.
7. When the import finishes, a confirmation appears. Click **Close** to view the imported alignment.
8. The imported alignment follows a different route. The bridge is still set to **ALIGNMENT 1**.
9. 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.
10. In the workflow tree, click **Bridge Alignment** under **Bridge Geometry** to view all alignments in the project.
11. **Alignment 1** is currently set for the ***BRG1*** bridge.
12. Click the cell showing ***ALIGNMENT1***. The three-dot menu appears on the right of the cell.
13. 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**.
14. **BRG1** is now set to **ALIGNMENT2**.
{% hint style="info" %}
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.
{% endhint %}
 
 
***
### After Importing the LandXML File
You have two options for tying the alignment's coordinates to the project's local origin:
1. Use the alignment's **Latitude** and **Longitude** as the **Project Local Origin**.
2. Use the **Project Origin's** latitude and longitude for the alignment's latitude and longitude.
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.
{% hint style="info" %}
**Setting the Local Origin of a Project**
To set the local origin for a project, follow the screenshots below.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.openbrim.org/quick-guides/import-alignment-landxml.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.