> 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/map-view-coordinate-picking.md).

# Map View Coordinate Picking

Displaying boreholes on a map and picking coordinates by clicking

Once a borehole has coordinates and a coordinate system, GeoDin can display it on a map and let you adjust the location interactively. The map view also supports the reverse workflow - clicking on the map to capture coordinates into a new or existing object.

For configuring the coordinate system itself (EPSG codes, the `G1_EPSG.GSD` dictionary, and in-mask transformations), see [Coordinate Systems and EPSG](https://docs.geodin.com/maps/coordinate-systems-and-epsg.md).

## Displaying a borehole on the map

Once coordinates and a coordinate system are entered, a borehole can be displayed on a map via the **map preview** button in the right-hand ribbon.

## Picking coordinates by clicking

The map view supports picking coordinates by clicking. The **Draw** tool lets users click on the map to capture local easting / northing values back into the coordinate fields. This is useful for establishing **tentative borehole locations** before precise survey data is available.

The **Cross-section** method also includes a top-down map view for spatially selecting boreholes - use drag-rectangle selection to pull all objects in an area into the cross-section workflow.


---

# 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/map-view-coordinate-picking.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.
