> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/maps.md).

# Maps

- [Getting Started with Maps](https://docs.geodin.com/maps/getting-started-with-maps.md): Set up the GeoDin Maps window: supported GIS file formats, adding map data, navigating with the map toolbar, interpolating, printing, and labeling layers.
- [Adding Layers](https://docs.geodin.com/maps/adding-layers.md): Create a GeoDin map, add GIS documents, folders and query layers to it, preview cross-sections, and control layer presentation and export from the legend.
- [WMS and Web Tile Layers](https://docs.geodin.com/maps/wms-and-web-tile-layers.md)
- [Coordinate Systems and EPSG](https://docs.geodin.com/maps/coordinate-systems-and-epsg.md)
- [Choosing the export coordinate system](https://docs.geodin.com/maps/coordinate-systems-and-projections.md)
- [Map View Coordinate Picking](https://docs.geodin.com/maps/map-view-coordinate-picking.md): Displaying boreholes on a map and picking coordinates by clicking
- [Digitizing Objects](https://docs.geodin.com/maps/digitizing-objects.md)
- [CAD and GIS Exports](https://docs.geodin.com/maps/cad-and-gis-exports.md): Get GeoDin data out to CAD and GIS: export layouts as DXF from the internal PDF printer, and export query results as point shape files for ArcGIS.
- [QGIS Integration](https://docs.geodin.com/maps/qgis-integration.md)


---

# 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.geodin.com/maps.md?ask=<question>&goal=<user_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.