/v1/tilequery/{lon},{lat} Query the spatial features at any coordinate — without rendering a tile or loading a full map. Get the geographic context at a point in one request.
Returns GeoJSON features from Farun's vector layers at the given lon,lat — administrative boundaries, land use classifications, road network context, POI presence, and terrain metadata. Useful for enriching assets, validating locations, and making decisions from coordinates alone.
# Query spatial features at a coordinate
curl "https://api.farun.io/v1/tilequery/77.2090,28.6139" \
-H "X-RapidAPI-Key: YOUR_KEY" \
-H "X-RapidAPI-Host: farun-maps.p.rapidapi.com" \
-G \
--data-urlencode "layers=admin,landuse,poi" \
--data-urlencode "radius=50"
# Narrow to a single layer
curl "https://api.farun.io/v1/tilequery/72.8777,19.0760" \
-H "X-RapidAPI-Key: YOUR_KEY" \
-G \
--data-urlencode "layers=admin" \
--data-urlencode "geometry=polygon"Returns
GeoJSON FeatureCollection
No render
Point query only
Layers
admin, landuse, poi, road
Queryable layers
Tilequery reads directly from Farun's vector tile layers and returns matching features at the given coordinate — giving you geographic intelligence without the overhead of a full map render.
admin Returns the administrative hierarchy at the queried coordinate — country, state/province, district, subdistrict, and municipality — with ISO codes and official names where available.
landuse Returns the land use type at the queried coordinate — residential, commercial, industrial, agricultural, park, water body, and protected areas — from Farun's enriched OSM-based dataset.
poi Returns POIs within a configurable radius of the queried coordinate — with name, category, and geometry. Useful for validating delivery locations, enriching asset records, or providing context to a coordinate.
road Returns the nearest road segment at the queried coordinate — with road class, name, surface type, speed limit where available, and whether the point snaps to a navigable road.
Who uses it
Tilequery is the most direct way to enrich a coordinate with geographic intelligence. It answers the question "what is at this point?" without requiring a map render, a geocoding round-trip, or a shapefile intersection on your own infrastructure.
Fleet & Telematics
When a vehicle or asset reports a GPS coordinate, query Tilequery to classify the location — road type, land use, administrative zone — and attach that context to the telemetry record. No shapefile processing on your end.
Insurance & Risk
Classify an insured address or incident coordinate the moment it arrives — residential vs commercial zone, proximity to water bodies, road access type — and feed that into underwriting or claims scoring pipelines.
Delivery & Last Mile
Before dispatching a driver, validate whether a delivery coordinate is in a serviceable land use zone, on a navigable road, and within the correct administrative area for the order. Catch bad coordinates before they become failed deliveries.
Field Operations
When a field crew checks in from a GPS coordinate, automatically surface the administrative district, nearest road, and land classification for that location — reducing the need for manual lookups and improving operational reporting accuracy.
Site Intelligence
For site selection workflows — retail locations, infrastructure planning, or service coverage mapping — query Tilequery at candidate coordinates to extract zone classification, road access, and POI density without building a GIS pipeline.
Compliance & Reporting
Batch-enrich thousands of asset or event coordinates with their administrative jurisdiction — state, district, municipality — for regulatory reporting, SLA verification, or cross-border operational compliance workflows.
Parameters
lon,lat required layers radius geometry limit language Response codes
200 application/json GeoJSON FeatureCollection. Empty features array if nothing found at the coordinate. 400 Bad request Invalid coordinate format or unrecognised layer name. 401 Unauthorized Missing or invalid RapidAPI key. 429 Rate limited Request rate exceeds your plan. Upgrade on RapidAPI. Integration example
// Enrich a GPS ping with spatial context
async function enrichCoordinate(lon, lat) {
const params = new URLSearchParams(
layers: 'admin,landuse,road',
radius: '100',
geometry: 'centroid',
);
const res = await fetch(
`/api/tilequery/$${lon},$${lat}?$${params}`
);
const { features } = await res.json();
const admin = features.find(f => f.properties.layer === 'admin');
const landuse = features.find(f => f.properties.layer === 'landuse');
const road = features.find(f => f.properties.layer === 'road');
return {
district: admin?.properties.name,
zone: landuse?.properties.class,
road_type: road?.properties.class,
road_name: road?.properties.name,
};
}Response format
GeoJSON FeatureCollection
Queryable layers
admin, landuse, poi, road
Max POI radius
500m
Geometry output
Centroid or polygon
Language support
BCP 47 — localised names
Max POI results
20 per request
How it compares
Mapbox Tilequery requires a hosted tileset and per-request billing against their platform. Farun exposes the same concept — coordinate-level feature queries — through a simpler endpoint with transparent RapidAPI pricing and no tileset management overhead.
| Capability | Farun | Mapbox |
|---|---|---|
| Admin boundary query | Yes — country to municipality | Requires admin tileset subscription |
| Land use classification | Yes — OSM + Farun enrichment | Requires custom tileset or Streets data |
| POI proximity query | Yes — ?radius= up to 500m | Yes — within tileset bounds only |
| Road context | Yes — class, surface, speed, access | Yes — via road tileset |
| GeoJSON response | Yes — FeatureCollection natively | Yes — FeatureCollection |
| Tileset management | None — Farun manages all layers | Must upload or subscribe to tilesets |
| Polygon geometry | Available via ?geometry=polygon | Yes — feature geometry returned |
| Pricing model | Pay-as-you-go via RapidAPI | Mapbox platform billing — usage-based |
| Private hosting | Available for enterprise | Not available in standard plans |
| Free tier | 200 requests / month | Included in Mapbox free tier limits |
Often used together
Resolve a place name or address to coordinates first, then pass the result to Tilequery for spatial context.
Render the full map context around your queried coordinate for map display alongside the feature data.
Generate a static map image centred on the queried coordinate to accompany the tilequery results in a report.
Use the snapped road coordinate from a road layer query as a precise routing waypoint for cleaner directions.
Start building
Subscribe on RapidAPI for instant key access. The free tier covers 200 tilequery requests per month — enough to prototype a full coordinate enrichment or location validation workflow end to end.