> 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/developers/paramml-developer-guide/core-objects/alignment-object.md).

# Alignment Object

\<The "Alignment" object is used to define the alignment of a road or bridge.

* Station: The station of the starting point of the alignment.
* Azimuth: The angle that the initial alignment makes with North, expressed in radians. Zero azimuth corresponds to North (optional).
* Latitude: Defines the starting point of the route based on the X axis (optional).
* Longitude: Defines the starting point of the route based on the Y axis (optional).
* Elevation: Defines the starting point of the route, together with Latitude and Longitude. It is also known as the elevation.

**Example Syntax:**

```
...
<O T="Alignment">
...
...
</O>
```

**Example:**

```xml
<O N="AlignmentObject1" T="Project" Category="3D Geometric Objects" TransAlignRule="Right">
    <!-- created by ParamML Examples on 02.02.2023 -->
    <O N="Route" T="Alignment" Station="300" Azimuth="PI/2" Lat="0" Lng="0" Elev="1000" />
    <O T="Line" Alignment="Route">
        <O T="Point" X="0" Y="0" Z="0" />
        <O T="Point" X="10" Y="0" Z="0" />
    </O>
</O>
```

"Route" object contains Alignment parameters. To view this example in the library, see (<https://openbrim.org/platform/?application=inc&author=ParamML_Examples_OpenBrIM+Platform&folder=3D+Geometric+Objects&obj=objidzt0qdokk0eb0dh0pmbh8p>)

**Parameters of Alignment Object:**

\| | **Label** | **Mandatory** | **Name and Type Attributes** | **Default Description and Value Attributes** | **Other Attributes** | | --- | --- | --- | --- | --- | | 1 | Station | No | N="Station" | D="Station: The station number at start of the alignment." V="0" | Role="Input" UT="Length" UC="Coordinate" | | 2 | Azimuth | No | N="Azimuth" | D="Azimuth: Orientation of the heading at start of the alignment. North is zero, clockwise direction." V="0" | Role="Input" UT="Angle" UC="Coordinate" | | 3 | Latitude | No | N="StartLatitude" | D="Latitude: Optional latitude value for the start of the alignment. For GIS." V="0" | Role="Input" UT="Angle" UC="Coordinate" | | 4 | Longitude | No | N="StartLongitude" | D="Longitude: Optional longitude value for the start of the alignment. For GIS." V="0" | Role="Input" UT="Angle" UC="Coordinate" |


---

# 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/developers/paramml-developer-guide/core-objects/alignment-object.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.