> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/quick-guides/import-alignment-landxml.md).

# 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. Sign in. The **Projects** screen opens. Click **New Project**, or **NEW** in the bar on the left. (With a project already open, click the **New** icon, the page icon next to the project name in the top bar.)

   ![Projects screen](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-8259d4ccd9f7506d86ed3e7c28047ffe210635e4%2Fprojects-screen-new-project.png?alt=media)
2. The **Project Templates** screen opens. Open the **Example Projects** folder.

   ![Project Templates screen](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-14402564cc1f44ace73ad72b5a381386b6981265%2Fproject-templates-screen.png?alt=media)
3. Click **New Project** on the **Steel I-Girder Training Example** card.

   ![Steel I-Girder Training Example card](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-1cfcafab90187e24638a8bdd36bcfde8f0aeaf71%2Fexample-projects-steel-i-girder-card.png?alt=media)
4. In the **Create Project** dialog, enter a name for your project, choose a **Folder** if you want one, and click **Create**. The project opens in the 3D view.

   ![Create Project dialog](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-927d95853809887c9990c739d337476a268205ee%2Fcreate-project-dialog.png?alt=media)

![Steel I-Girder Training Example in the 3D view](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-161590db90b30d71e39a93d85b27a3d566db872f%2Fsteel-i-girder-training-example-opened.png?alt=media)

{% 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. There are two places to do it:

* Click the project name (top left), choose **Project settings** and pick the **Geographic Coordinate System**.
* Or open the **Site** view in the left sidebar and click the **+** button beside **Coordinate System** (**Import Coordinate System**; once one is set, the button changes it). Pick the coordinate system from the library list; each entry shows its EPSG code.

![image-20241106-135258.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-135258.png?api=v2)

![image-20241106-135357.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-135357.png?api=v2)

![image-20241106-135539.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-135539.png?api=v2)

![image-20241106-135818.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-135818.png?api=v2)

![image-20241106-140025.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-140025.png?api=v2)

![image-20241106-140110.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-140110.png?api=v2)

![image-20241106-140410.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-140410.png?api=v2)

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/download/attachments/2231304203/ExampleAlignment2.xml?api=v2). The link downloads the file; no sign-in is needed.
2. Click the project name in the top-left and select **Import…**.

   ![Project menu with Import](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-0d8d5a9fa3703d052954bc0725a321d4482fc9f0%2Fproject-menu.png?alt=media)
3. Alternative entry point: click **Sheet** at the right of the 3D view's toolbar to open the spreadsheet.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230712-080932.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230712-081436.png?api=v2)
4. Click **Roadway Alignment** under **Bridge Geometry** in the workflow tree. The spreadsheet lists all alignments in the project.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230712-081800.png?api=v2)
5. Open the sheet's **⋮** menu in the top-left corner of the spreadsheet and select **Import LandXML...**.

   ![Sheet menu with Import LandXML](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-ae981cb55f06a92b715058477c9748df333d3912%2Fsheet-menu-import-landxml.png?alt=media)
6. In the file dialog, select the XML file. The example file is **ExampleAlignment2.xml**. You can select several LandXML files at once; they are imported one after another, and the results are listed in one dialog.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-062620.png?api=v2)
7. When the import finishes, a confirmation appears. Click **Close** to view the imported alignment.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-071459.png?api=v2)
8. The imported alignment follows a different route. The bridge is still set to **ALIGNMENT 1**.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-072114.png?api=v2)
9. To switch the bridge to the new **ALIGNMENT 2**, click **Sheet** at the right of the 3D view's toolbar to open the spreadsheet. The workflow tree appears on the left.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-072909.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-073707.png?api=v2)
10. In the workflow tree, click **Bridge Alignment** under **Bridge Geometry** to view all alignments in the project.

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-074259.png?api=v2)
11. **Alignment 1** is currently set for the ***BRG1*** bridge.

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-074447.png?api=v2)
12. Click the cell showing ***ALIGNMENT1***. The three-dot menu appears on the right of the cell.

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-075109.png?api=v2)
13. Open the three-dot menu. At the top of the menu you'll see the choices **None**, **ALIGNMENT1**, and **ALIGNMENT2**. Click **ALIGNMENT2**.

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-075340.png?api=v2)
14. **BRG1** is now set to **ALIGNMENT2**.

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-080218.png?api=v2)

{% hint style="info" %}
The spreadsheet appears on the right and the workflow tree on the left.

* To resize the spreadsheet, drag the divider between it and the 3D view.
* To close it, click **Sheet** again.
* To hide roadway surfaces (so alignments display as lines only), open **Display** → **Alignment Display…** in the bar at the bottom of the 3D view and turn off **Roadway Surface**.
* If too many alignments exist for the inline picker, the menu shows **Choose...** instead — click it to choose from a list.
  {% endhint %}

![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-080622.png?api=v2) ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230705-080858.png?api=v2)

![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230703-083740.png?api=v2) ![](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20230703-083819.png?api=v2)

***

### 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**.

   ![image-20241106-144940.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-144940.png?api=v2)
2. Use the **Project Origin's** latitude and longitude for the alignment's latitude and longitude.

   ![image-20241106-145054.png](https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-145054.png?api=v2)

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.

<img src="https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-145534.png?api=v2" alt="image-20241106-145534.png" data-size="original"><img src="https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-150313.png?api=v2" alt="image-20241106-150313.png" data-size="original"><img src="https://openbrim.atlassian.net/wiki/download/attachments/2231304203/image-20241106-151924.png?api=v2" alt="image-20241106-151924.png" data-size="original">
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openbrim.org/quick-guides/import-alignment-landxml.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
