Context for any point or line.
Send a point, a line, or a whole GPS track. RLQ returns it knowing what it sits on and what surrounds it — public land, roads, hydrography, terrain, ecology, places — from authoritative sources we normalize and keep current.
Click the map. This is the production API.
No selection yet
Click a road and we'll snap to it as a line; click open ground for a point. Then run a real enrichment.
Six kinds of context, one response.
Every match arrives under its own source key, with a distance or overlap where the geometry allows one, and decoded labels beside the raw codes. Which sources answer for a given point depends on where it is; the response says which contributed, and which were omitted and why.
National forests, PAD-US protected areas, BLM surface management, monuments, wilderness and study areas.
USFS motor-vehicle-use roads and trails, BLM ground transportation, OpenStreetMap roads with surface and access, and Forest Service trails.
USGS National Hydrography flowlines and waterbodies — rivers, streams, canals, lakes, reservoirs — with the feature type and the distance to it.
Ground elevation from USGS 3DEP inside the US and Copernicus GLO-30 elsewhere, slope and aspect computed from the surface, and the annual NLCD land-cover class.
RESOLVE Ecoregions 2017 — biome, realm and named ecoregion worldwide — and EPA Level III ecoregions across the contiguous US.
USGS GNIS named features, Overture and OpenStreetMap points of interest, and Census TIGER state, county and place boundaries.
One POST. Then collect the result.
- POLL, OR BE TOLD
GET /v1/enrich/{id}for status, or/v1/enrich/{id}/eventsfor server-sent events. Fetch the download link once when the job succeeds.- GPX IN, GPX OUT
- POST a GPX file as multipart and the enriched track comes back as GPX, waypoints and tracks intact, with the context in an
rlqextension. - FORMAT BOUND AT ENQUEUE
- What you send is what you get back. The output format never renegotiates at download.
curl -sS -X POST https://enrich.reloquent.ai/v1/enrich \ -H "Authorization: Bearer $RLQ_API_KEY" \ -H "Content-Type: application/json" \ -d '{"geojson":{"type":"FeatureCollection","features":[ {"type":"Feature", "geometry":{"type":"Point","coordinates":[-111.650,35.190]}, "properties":{"name":"Camp 3"}}]}}' # 202 Accepted -- enrichment is asynchronous { "job_id": "2a29722c-...", "status": "queued", "credits": 1, "links": { "status_url": "...", "download_url": "..." } }
What goes in, what comes back.
- Geometry
- Point and LineString, including multi-thousand-vertex tracks. GPX routes are enriched per point.
- Formats
- GeoJSON in, GeoJSON out. GPX in, GPX out.
- Coordinates
- WGS84 (EPSG:4326). Your elevation values pass through untouched; RLQ's own terrain elevation is reported separately.
- Your properties
- Preserved verbatim. Enrichment is added under its own
rlqkey, never merged over yours. - Polygons
- Not yet. The result set for an area is a different problem than for a path, and it deserves its own model.
Metered by credits. No bill shock.
A point is one credit; a line or track is one credit per hundred vertices. Reach your monthly cap and new calls are refused with a 429 — never billed.
Questions, answered plainly.
Why is it asynchronous? I just want one point.
Because the same endpoint has to serve a ten-thousand-vertex track without timing out. One code path for both means your integration does not change when your inputs grow. A single point typically completes in a few seconds — poll once, or subscribe to the events stream and get told.
Does RLQ change my data?
No. Your geometry is returned exactly as sent and your properties are preserved verbatim; enrichment is added alongside them under its own key. RLQ does spatial enrichment only — it does not clean, simplify, snap or otherwise "improve" your input.
What is a credit?
The unit the meter counts, weighted by the vertices in your request: a point is one credit, a line or track is one credit per hundred vertices. Your live usage and cap are always on the dashboard, and exceeding the cap refuses calls rather than billing them.
Do you have coverage outside the United States?
Partly, and it is growing. The base layers — places, roads, ecoregions, terrain — are worldwide; several of the richest sources, such as federal land, motor-vehicle-use roads and national hydrography, are US datasets, so a point in the US comes back with more context today. Sources for a new region are brought in on the first customer who needs them — ask us about yours.
Can I get the geometry of what you matched?
No. RLQ answers questions about a location you already have; it is not a geometry download. You keep bringing your own geometry, and we tell you about it.