> For the complete documentation index, see [llms.txt](https://docs.aeroai.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeroai.io/siega-web-features/asset-library/data-layers.md). # Data Layers This section covers the data layers that populate a scene, the assets you load onto the globe to give it something to show. A layer can be a detailed model of a site, a scan of a real location, an imagery base map, a terrain surface, or a set of mapped shapes, and every layer rests on the same shared globe so that any combination can be viewed together in one place. Each supported format behaves a little differently once it is loaded, in how it is streamed, how it is styled, and how it is positioned. For that reason every format is documented on its own page, where its specific behavior and options are explained in full. Treat this section as the starting point for bringing real data into a scene, then move to the page for the format you are working with. --- # 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.aeroai.io/siega-web-features/asset-library/data-layers.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.