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

# Measure Area

A **Measure Area** annotation reports the enclosed area *and* the perimeter of a picked polygon, written as a single label at the centroid — for example `Area: 412.500 sq ft, Perimeter: 84.250 ft`.

Pick the boundary points and the shape closes automatically; the area comes from the closed polygon regardless of the order you picked, so a re-entrant or non-convex outline still measures correctly. Because the points snap like any other CAD geometry, tracing an existing deck outline or a hatched region is exact rather than eyeballed.

Use it for quantity checks — deck surface, parapet elevation area, a patch of overlay, a plan footprint — where you want the number on screen but not a formal dimension in the drawing.

## Text and units

**Label:** Override text, replacing the measured values.

**Prefix / Suffix:** Text before and after the value.

**Precision:** Number of decimal places.

**Unit Style / Length Unit:** Units. Length Unit overrides the project geometry unit for this annotation only; the area is reported in the corresponding squared unit.

## Typography

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

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

## Notes

Both numbers are recomputed from the polygon whenever a boundary point moves, so editing the outline updates the quantity — there is no stale value to remember to refresh.

For a measurement that belongs in the issued drawing, use the dimension objects instead; Measure Area is the working tool. Related: [Measure Length](/templates/cadd/measurelength-cadd.md).


---

# 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/measurearea-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.