> 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/vertical-segments.md).
# Vertical Segments
Vertical Segments are used in the design of the longitudinal section (profile) of the route between the two stops determined in the plan. While defining Vertical Segments; "Alignment and Vertical Curve" elements of the route in the project should be created. These are created with the longitudinal slope and red elevation parameters in different Mils that you will enter as inputs. The mil **Station** where the stops are located, the longitudinal slope **Grade** and the red elevation value are defined by **Elevation** parameters. In cases where there is a difference in longitudinal slope between two consecutive stops, the system connects the two points parabolic.
Vertical alignment can be specified by defining one or more **Elevation Point** objects along the horizontal line.
**Example:**
The design of a longitudinal section of the route is facilitated by the use of Vertical Segments. These section are created by defining the alignment and vertical curve elements of the route in the project, based on the longitudinal slope and elevation values entered as inputs at different miles along the route. The Elevation parameters define the mile Station of the stops, the longitudinal slope grade, and the elevation value. If there is a difference in the longitudinal slope between two consecutive stops, the system connects the two points with a parabolic curve. In the example given, three different stops were defined along the designed longitudinal section and the necessary values for each stop were entered. Since the elevations at stops A and B are equal and those at stops B and C are different, the distance between these two stops is automatically connected with a parabolic curve.
```xml
```
 To view this example in the library, see ()
**Exampe:**
```xml
```
 To view this example in the library, see ()
**Parameters of Vertical Segments Object (Alignment):**
\| | **Label** | **Mandatory** | **Name and Type Attributes** | **Default Description and Value Attributes** | **Other Attributes** | | --- | --- | --- | --- | --- | | 1 | Station | Yes | N="Station" | D="Station: Station number of the elevation point." V="0" | Role="Input" UT="Length" UC="Coordinate" | | 2 | Grade | Yes | N="Grade" | D="Grade: Grade at this elevation." V="0" | Role="Input" | | 3 | Elevation | Yes | N="Elevation" | D="Elevation: Elevation value." V="0" | Role="Input" UT="Length" 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/vertical-segments.md?ask=&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.