Instance · Data
GeoJSON
Last updated 1 November 2026
The GeoJSON field type: a point, line or area typed in a Code box, with its settings.
A GeoJSON field holds a location or a shape: a point, a line or an area, written in the GeoJSON format. Use it for an office position, a delivery zone or a route. Your developers can then search for records near a point or inside an area.
The UI element
A GeoJSON field has one UI element, Code, and it is the default. You type or paste the GeoJSON into a code box.
| Setting | Type | Required | Meaning |
|---|---|---|---|
| Mandatory | Toggle | No | Whether a value must be given before the item can be saved |
The Appearance tab
| Setting | Type | Required | Meaning |
|---|---|---|---|
| Help Text (Tooltip) | Text | No | A short note shown beside the field, to explain what it holds |
A Code field cannot be shown, searched or sorted in the items table, so those settings do not appear. It can be used in filters.
Example value
{
"type": "Point",
"coordinates": [153.03, -27.47]
}GeoJSON puts longitude first, then latitude. This point is in Brisbane.
Using it in GraphQL
Developers filter on a GeoJSON property with distance_sphere, which finds records closer than a distance in kilometers, or within_radius. See Distance units.
Note
The UI element and settings come from the Data module source (October 2026: fieldTypes.js, uiElements.js and Appearance.vue). The docs instance has no GeoJSON fields.
Common mistakes
- Writing latitude first. GeoJSON is longitude, then latitude.
- Pasting an address. The field needs GeoJSON, not text.
- Sending a GeoJSON object through some module APIs as a parsed object instead of a JSON string. One module custom-field path then drops every custom field in the same request.