> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/data/collections/field-types/map-coordinates.md).

# Map Coordinates

Map Coordinates fields hold Latitude and Longitude values, pinpointing locations on a map, with example values like '51.523767, -0.1585557'. They can be displayed as coordinates or integrated with a [map view](/views/display/maps.md)

## Coordinate Format

Map Coordinates store:

* **Latitude**: North-South position (-90 to +90 degrees)
* **Longitude**: East-West position (-180 to +180 degrees)

Coordinates are typically displayed as decimal degrees (e.g., 51.523767, -0.1585557).

## Data Entry

Coordinates can be entered:

* Manually as decimal degrees
* By clicking on a map interface
* Automatically via geocoding from [Street Address fields](/data/collections/field-types/street-address.md)
* Through API integrations with GPS devices or mapping services

## Use Cases

Map Coordinates are ideal for:

* Precise location tracking
* GPS data from mobile devices
* Asset location management
* Geographic analysis and reporting
* Delivery route optimization
* Emergency response systems

## Integration with Views

Map Coordinates work with:

* [Map views](/views/display/maps.md) to display points on interactive maps
* Geographic filtering and proximity searches
* Distance calculations between coordinates
* Spatial analysis and clustering

## Best Practices

* Use Map Coordinates for precise locations where GPS accuracy is important
* Combine with [Street Address fields](/data/collections/field-types/street-address.md) for user-friendly address display
* Consider data privacy when storing location information
* Validate coordinate ranges to ensure they fall within valid geographic boundaries
* Test coordinate accuracy for your specific use case requirements


---

# 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://guides.noloco.io/data/collections/field-types/map-coordinates.md?ask=<question>&goal=<endgoal>
```

`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.