Africa's Geospatial AI Intelligence Engine
Crowdsourced field intelligence from geoDxT Map and your own coordinate uploads flow here — where the AI standardises, processes, and deploys live REST API endpoints any developer can query.
Input
Direct Upload
Coordinate CSVs, GeoJSON, and WKT boundary files you upload straight to the AI.
Engine
geoDxT AI
- ✓ Auto-detects CRS across 11+ projections
- ✓ Standardises & processes spatial data
- ✓ Deploys a live REST API per dataset
- ✓ Issues API keys for developer access
Input
geoDxT Map
Crowdsourced field attributes — road surfaces, building use, condition scores — logged by community contributors.
Spatial REST API — v1
Query verified survey boundaries, crowdsourced field attributes, and processed spatial datasets with a single Bearer token.
Base URL
https://geodxt.com/api/v1/spatial
Authentication
Add this header to all authenticated requests:
Authorization: Bearer gdxt_xxxxxx
Get your key by uploading a dataset or syncing approved Map contributions.
Endpoints
Rate limit: 60 requests / minute per key
Response: JSON — Content-Type: application/json
Errors: Standard HTTP status codes
Request
GET /api/v1/spatial/features # No auth required — returns all public datasets
cURL
curl https://geodxt.com/api/v1/spatial/features \ -H "Accept: application/json"
Response
{
"total": 42,
"page": 1,
"per_page": 20,
"datasets": [
{
"id": "kano-gra-plot22-a1b2c3d4",
"name": "Kano GRA Plot 22",
"source": "geodxt-ai:processed",
"crs": "EPSG:26331",
"feature_count": 6,
"processed_at": "2026-06-08T10:32:14Z",
"endpoint": "https://geodxt.com/api/v1/spatial/boundary/kano-gra-plot22-a1b2c3d4"
}
]
}
Request
GET /api/v1/spatial/boundary/{endpoint} # Requires Authorization header
cURL
curl https://geodxt.com/api/v1/spatial/boundary/kano-gra-plot22-a1b2c3d4 \ -H "Authorization: Bearer gdxt_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \ -H "Accept: application/json"
Response
{
"id": "kano-gra-plot22-a1b2c3d4",
"name": "Kano GRA Plot 22",
"crs": "EPSG:26331",
"crs_confidence": 1,
"feature_count": 6,
"source": "geodxt-ai:processed",
"columns": ["station_id", "easting", "northing", "height"],
"stats": {
"bbox": {
"min_easting": 398710.5,
"max_easting": 398780.2,
"min_northing": 840900.1,
"max_northing": 840960.8
},
"extent": { "width_m": 69.7, "height_m": 60.7 }
},
"processed_at": "2026-06-08T10:32:14Z",
"api_usage": { "total_requests": 17, "last_used": "2026-06-10T09:11:00Z" }
}
Request
GET /api/v1/spatial/data/{endpoint} # Returns all coordinate records as JSON array
cURL
curl https://geodxt.com/api/v1/spatial/data/kano-gra-plot22-a1b2c3d4 \ -H "Authorization: Bearer gdxt_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
Response
{
"id": "kano-gra-plot22-a1b2c3d4",
"source": "geodxt-ai:processed",
"crs": "EPSG:26331",
"total": 6,
"records": [
{ "station_id": "PL1", "easting": "398745.25", "northing": "840932.75", "height": "427.3" },
{ "station_id": "PL2", "easting": "398753.18", "northing": "840941.52", "height": "427.1" },
// … 4 more points
]
}
Request
GET /api/v1/spatial/stats/{endpoint} # Processing info + API usage counters
cURL
curl https://geodxt.com/api/v1/spatial/stats/kano-gra-plot22-a1b2c3d4 \ -H "Authorization: Bearer gdxt_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
Response
{
"id": "kano-gra-plot22-a1b2c3d4",
"source": "geodxt-ai:processed",
"processing": {
"status": "completed",
"feature_count": 6,
"crs": "EPSG:26331",
"crs_confidence": 1,
"processed_at": "2026-06-08T10:32:14Z"
},
"api_usage": {
"total_requests": 17,
"last_used": "2026-06-10T09:11:00Z",
"enabled": true
}
}
Error Codes
How Data Flows into the AI
Two pipelines — both create live API endpoints the moment data is processed or approved.
Pipeline 1
Direct Upload → geoDxT AI
-
1
Upload a coordinate CSV, GeoJSON, or WKT boundary file
-
2
AI validates the geometry and auto-detects the CRS
-
3
Pick a grid resolution and processing options
-
4
AI creates a ProcessedFile, generates endpoint slug + API key
-
5
Live REST API live at
/v1/spatial/boundary/{slug}
geodxt-ai:processed — your own uploaded dataset
Pipeline 2
geoDxT Map → geoDxT AI
-
1
Admin validates a route or building and marks it live on the map
-
2
Community contributor logs field attributes within GPS proximity
-
3
Admin reviews and approves the submission
-
4
AI sync job runs — creates ProcessedFile with geometry + enrichment data
-
5
Live endpoint at
/v1/spatial/boundary/{slug}with enriched attributes
geodxt-map:crowdsourced — includes road & building attributes
CSV or GeoJSON → Live Grid API
Upload a raw coordinate CSV or GeoJSON file directly. The AI detects the CRS, generates a spatial grid, and deploys a live JSON endpoint — same API, same key format.
Auto CRS detection
11+ projections — Minna, UTM, WGS84, OSGB
Grid processing
100m, 500m, 1km, 5km, 10km resolutions
Live endpoint
JSON API deployed in seconds
Publish or keep private
Set free or paid in the marketplace
Upload File
CSV with Easting/Northing (or WKT geometry), or a GeoJSON FeatureCollection. Column names are auto-detected.
CRS Detected
The AI identifies the coordinate reference system — Minna Belt, UTM zones, WGS84, or others — with a confidence score.
Grid + API Ready
Spatial grid generated at your chosen resolution. A live JSON endpoint is deployed and your API key is issued.
Publish & Earn
Optionally list on the marketplace — free or paid. Earn credits every time another developer queries your dataset.
Ask GeoAI Anything Geospatial
Upload a survey plan PDF and get all boundary coordinates instantly calculated. Ask about CRS, coordinate transformations, traverse closure, and API output formats.
Try a question
A → E 398745.250 N 840932.750
B → E 398753.185 N 840941.526
C → E 398767.330 N 840927.526
… 3 more points
Closure ratio: 1:8,847 ✓ Area: 4,521.75 m²
/v1/spatial/boundary/{slug} endpoint with a Bearer API key in seconds.
Utility Apps — Same Account
Small focused tools that run inside geoDxT AI. Same login, same credit wallet.
New apps shipped regularly
Quick Poll
Shareable polls with live result charts — no voter account needed.
Field Form
Data collection forms for field officers — submissions include GPS coordinates.
Data In. API Out. Instantly.
Approve Map contributions or upload a CSV directly — every path ends with a live REST API endpoint and a Bearer key.