> 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/templates/cadd/dimensionordinate-cadd.md).

# Ordinate Dimension

An **Ordinate Dimension** labels a point's coordinates relative to a reference origin — typically Northing/Easting or X/Y from a project datum. Use it for footing corner coordinates, pile coordinates, control points, and anywhere a coordinate callout (rather than a chained dimension) is the cleanest way to communicate position.

Pick a point, and the dimension shows its coordinates as `(X, Y)` or `(N, E)` depending on local convention, relative to the document's origin (or a separately set datum).

## Text and units

**Label:** Override text.

**Prefix:** Text before the value.

**Suffix:** Text after the value.

**Precision:** Number of decimal places. 2 is typical for foot-units, 3 for meters.

**Unit Style / Length Unit:** Units.

## Placement

**Offset X / Offset Y:** Leader offsets — fine-tune label position.

## Typography

**Text Height:** Text size in real units.

**Font Family / Font Weight / Font Style:** Font controls.

## Notes

Ordinate dimensions are most useful on plans where many points share a common reference origin and chained dimensions would clutter the drawing — pile coordinate schedules, footing corner schedules, working-point lists. Often paired with a points table that has the same coordinates in tabular form.

For simple two-point distances, prefer a Linear Dimension. For coordinate schedules with many points, consider a Point and a separate coordinate table rather than per-point ordinate dimensions on the drawing.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/templates/cadd/dimensionordinate-cadd.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.