> For the complete documentation index, see [llms.txt](https://docs.jmapcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jmapcloud.io/en/jmap-ng/jmap-ng-user-guide/data.md). # Data JMap NG projects can contain two types of data: **spatial data** and **non-spatial data**. ## Spatial Data Spatial data is organized into map layers. Each layer contains data on a particular theme. These layers are stacked to form the map displayed in the interface. ### Types of Spatial Layers #### **Vector layers** Composed of features represented by geometries (points, lines, polygons) and descriptive attributes. Example: A tree layer represented by points, with attributes such as species, diameter, height, and health status. Each tree thus has a geographic position and characteristics that describe it. #### **Raster layers** Composed of raster data (pixels) forming images: aerial photos, satellite imagery, digital elevation models, etc. ### **Hierarchical Organization** Layers can be grouped hierarchically by theme: urban planning, environment, transportation, etc. This multi-level structure makes navigation easier when projects contain many layers. ### **Base Maps** Base maps provide visual context for presenting your data. Your interaction is limited to selecting which base map to display. ## Non-Spatial Data The non-spatial data in the project is organized into tables. This tabular data can be linked to map layers or be completely independent. A table contains rows (records) and columns (fields or descriptive attributes). --- # 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.jmapcloud.io/en/jmap-ng/jmap-ng-user-guide/data.md?ask=&goal= ``` `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.