> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/essentials/atlas.md). # Atlas

IN THIS ARTICLE Atlases visually represent all of the activity records and associated data from the provided context. View the modeled outcomes, progress toward metric goals, and the activity locations. *** ## Atlases The **Atlas** provides a spatial overview of all activity records within your project, offering a map-based view that brings together geospatial data, metrics, and project structure. It’s a powerful way to explore where work is happening and how different components of your project relate to each other geographically. In the Atlas, users can see the locations of activities alongside their associated metrics—including organization metrics, programmatic metrics, and modeled outputs. This view is especially useful for identifying gaps, visualizing patterns across a landscape, and communicating progress to partners or stakeholders. Whether you're planning next steps or reporting on completed work, the Atlas helps connect your data to place. --- # 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://help.fielddoc.org/essentials/atlas.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.