> For the complete documentation index, see [llms.txt](https://docs.geoprismregistry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.1-content/5.1-content.md).

# 5.1.1. Geographic features and geographic objects

Geographic features are features of the Earth, natural (e.g., rivers) or artificial (e.g., buildings), physical (e.g., roads) or abstract (e.g., administrative division). Each sector has its own set of geographic features that are core to the implementation of its programs and activities. Those core to the health sector, for example, include but are not limited to: health facilities, vaccination points, settlements, ambulances, patients, roads and administrative divisions.

GeoPrism Registry does nevertheless only handle geographic features for which it makes sense to establish and maintain a master list. These include fixed features such as health facilities, schools, bridges, or villages; artificially-created features such as administrative units, foci or health areas; or mobile features such as vehicles or individuals. A master list for other geographic features would either not be necessary (e.g., roads, rivers)\* or not applicable (e.g., continuous features like topography or population distribution). A geographic object, or **Geo-Object**, is itself the computer representation of a geographic feature. It can be represented as a point, line, or polygon on a map (more details on this in the next section).

\**GeoPrism Registry does nevertheless provide the possibility to handle geographic objects represented by lines and can handle roads and rivers should master lists exist for them.*


---

# 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.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.1-content/5.1-content.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.