> 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/coordinate-systems-and-projections.md).

# Choosing the export coordinate system

When you export a map layer, you choose which coordinate system its coordinates are written in. The export behaviour is controlled by one of three **Export options**, described below.

## Reference: Export options

Select the coordinate system in which the layer will be exported.

### -Use the map coordinate system-

The coordinate system selected for the map (not on the layer!) is used for the export. The EPSG code of the coordinate system is displayed in the export dialogue, but you cannot change it there.

### -Ask user-

In the export dialogue, the EPSG code of the coordinate system set on the map is automatically specified. However, the coordinate system to be used can be changed by selecting the desired coordinate system from the integrated dictionary at the EPSG code field.

### -Fixed system-

Here, at the EPSG code field, define a coordinate system to be used when exporting this layer. The EPSG code of the coordinate system is displayed in the export dialogue, but it cannot be changed there.


---

# 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/coordinate-systems-and-projections.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.
