Documentation menu
compliance
POST/geodata/validate
API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….
Call it
bash
curl -fsS -X POST "https://api.mapmap.ai/geodata/validate" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d @request.jsonRequest body
application/json · ValidateGeodataRequest
A declared CRS and a sample of the dataset's own coordinates
| Field | Type | Required | Description |
|---|---|---|---|
| coordinates | GeodataCoordinate[] | yes | A sample of the dataset's raw coordinates. A few dozen is plenty: the check is about ranges and spans, not volume. |
| declared_crs | string | yes | The CRS the dataset claims, e.g. "EPSG:4326" or "EPSG:32610". |
Responses
200Whether the declaration and the coordinates agree
| Field | Type | Required | Description |
|---|---|---|---|
| extent | GeodataExtent | yes | Observed extent of the sample, in the dataset's own units. |
| interpreted_as | string | yes | The CRS family the declaration was understood as. |
| problems | string[] | yes | Plain-language findings, most important first. Empty when consistent. |
| suggestions | string[] | yes | What the numbers look like when the declaration does not fit. |
| verdict | string | yes | consistent, suspect or impossible. |
400Empty or non-finite coordinate sample
401Missing or invalid API key
429Quota or rate limit exceeded
Error bodies follow the shared problem model documented on API conventions.
Also under compliance
Generated from https://api.mapmap.ai/openapi.json on 2026-09-17 · operationId post_validate