Forward geocode — convert text into coordinates
Resolve an address, place name, intersection, or free-form location string to one or more candidate coordinates. Results are ordered by relevance; the top hit is the geocoder's best guess. Identical inputs may be served from cache for up to 7 days (X-Cache: HIT; STALE once older than 3 days, refreshed in the background); cold lookups run through the regional engine.
Request
- Base URL: https://geo.thinair.co
- URL: https://geo.thinair.co/v1/geocode
- Auth: HTTP bearer
Query parameters
Free-text query — address, place name, intersection, etc. One of text or query is required.
Alias for text. The service layer accepts either; clients should prefer text.
Maximum candidates to return (1–40). Defaults to 5 in the service layer.
Comma-separated layer filters: address, street, venue, locality, neighbourhood, region, country, postalcode, county, localadmin, coarse, intersection. Use layers=intersection to restrict results to street corners.
ISO 3166-1 alpha-2 or alpha-3 country code to scope results.
Latitude of the proximity bias point — results closer to this coordinate score higher.
Longitude of the proximity bias point.
Response
Geocoder result envelope.
Example response
{
"features": [
{
"id": "ta_place_8f3a2c9e61c04d58"
}
],
"warnings": [
"intersection_unresolved"
],
"precision": {
"class": "intersection",
"risk_flags": [
"ambiguous_without_context"
],
"required_context": [
"borough"
]
}
}Changes
No recorded changes to this operation across all 1 revision of this API.