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

# Pin

A **Pin** is a fixed-size symbol marker that highlights a point on a drawing. Pins always render at a consistent screen size regardless of zoom, so they stay readable at any scale — useful for marking pile locations on a foundation plan that needs to print at multiple scales, sensor locations on an instrumentation plan, control points on a survey overlay, or any feature that needs a clear visual marker rather than a dimensioned callout.

## Style

**W:** Pin width in screen pixels. Default 30. The pin renders at this fixed pixel size regardless of zoom level.

**H:** Pin height in screen pixels. Default 30.

**Image Type:** Pin shape:

* **Pin** (default) — Map-pin style symbol with a teardrop head and a point.
* **Arrow** — Arrow symbol pointing at the marked location.

**Color:** Pin color.

**Thickness:** Outline thickness.

**Level:** Layer assignment.

## Placement

A pin has a single anchor point — the location it marks. Click to place. Drag to move.

## Notes

Use Pins sparingly. They're effective when there's exactly one or two important points to highlight; on a drawing with many pinned features, the pins crowd the drawing. For dense point markers (a pile group, a bolt pattern), use small Circles or filled symbols at real-world size instead.

Because pins render at a fixed pixel size, they always remain readable when the drawing is plotted — but they don't scale with the rest of the geometry. If the drawing is shown at very small print scale, a pin can look disproportionately large; tune W and H accordingly for your sheet size.


---

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