> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/products/maps-and-imagery-portfolio/os-openmap-local/os-openmap-local-technical-specification/feature-types/namedplace.md).
# NamedPlace
A representative point feature giving the general location of a settlement name or geographic place name, for the purposes of text placement.
UML class diagram for the NamedPlace Feature Type.
## NamedPlace attributes
### classification
The classification of the NamedPlace. The valid values are defined in the NamedPlaceClassification Code List.
* **Type:** NamedPlaceClassification
* **Length:** 40
* **multiplicity:** \[1]
### distinctivename
The settlement name or geographic place name. When a place is dual named, the Welsh or Gaelic name is presented first, followed by a space, a forward slash, a space and then the English name.
* **Type:** CharacterString
* **Length:** 100
* **Multiplicity:** \[1]
### featureCode
A unique feature code to facilitate styling.
* **Type:** Integer
* **Multiplicity:** \[1]
### fontHeight
A suggested text size to use for placing the distinctiveName as cartographic text. For most names, the text size is proportional to the size of the area to which the name applies. For valleys, the text size is based on the valley length, and for hills/mountains, the text size is based on the height of the summit. The valid values are defined in the FontHeightClassification Code List.
* **Type:** FontHeightClassification
* **Length:** 11
* **Multiplicity:** \[1]
### geometry
Point representing the cartographic position of the named place.
* **Type:** GM\_Point
* **Multiplicity:** \[1]
### textOrientation
Suggested text orientation (in degrees) to use for cartographic text placement of valley names, names of stretches of water and estuaries.
* **Type:** Measure
* **Multiplicity: \[1]**
---
# 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.os.uk/os-downloads/products/maps-and-imagery-portfolio/os-openmap-local/os-openmap-local-technical-specification/feature-types/namedplace.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.
