Global Coverage

Geocoding depth by region

Coverage depth varies by country depending on the maturity and availability of source address data. Most countries support at least country, first-level administrative division, and major named localities. In many countries, street-level and address-level records are available. The table below reflects typical depth — individual countries may exceed or fall below the regional average.

Region	Typical admin depth	Postcode depth	Street / address depth
Western Europe	Admin 0–3 broadly available across most countries	Strong postcode handling in most countries; sector and unit-level in several	High street coverage; address-point data available in many countries
North America	Admin 0–2 with county and locality context	ZIP/postal code support with ZIP+4 where supplied	Strong street and address-level coverage in urban and suburban areas
Asia Pacific	Admin 0–2 broadly available; Admin 3 in Japan, South Korea, Australia, NZ, and others	Country-dependent; strong in countries with national postcode schemas	High in urban corridors; variable in remote and island areas
Latin America	Admin 0–2 broadly available; Admin 3 in major markets	Moderate to strong depending on national postal system	Urban street coverage strong; address points vary by locality and country
Middle East	Admin 0–2 broadly available	Postcode systems vary significantly by country	Good in major cities; sparser in rural and desert areas
Africa	Admin 0–2 broadly available	Postcode support varies by national system maturity	Improving urban coverage; significant variation between countries and regions

Fallback behaviour and result types

When a precise address point is not available for a query, results fall back in a defined order: rooftop → interpolated street range → street centroid → locality centroid → postcode centroid → admin centroid. The match_type field in each API response indicates which level was matched, so your application can handle lower-confidence results appropriately — for example, by prompting the user to confirm the location on a map.

Waterways and coastlines

The geospatial index includes named waterways and coastlines from source datasets. This supports context matching for addresses near rivers, estuaries, canals, and harbours; map rendering workflows that need river and lake geometries; and reverse geocoding behavior near water boundaries. Rivers, named lakes, canals, reservoirs, and ocean coastlines are included where available in the index.

Elevation and bathymetry — SRTM15+

Elevation data for the elevation API uses the SRTM15+ dataset from the Scripps Institution of Oceanography (topex.ucsd.edu). This dataset provides global coverage including ocean bathymetry (negative depth values for underwater terrain), land elevation, and ice surfaces. Effective resolution varies by location — some land areas resolve at finer scales, while ocean and remote regions use modeled values. Elevation values for inland water bodies and areas below sea level (such as the Dead Sea basin or Death Valley) are returned as negative numbers.

IP geolocation coverage

The IP lookup API covers approximately 99% of IPv4 and IPv6 address space. The database includes geolocation (country, region, city), ASN and ISP attribution, and connection type classification. Coverage is maintained through automated allocation and routing-data pipelines that keep geolocation assignments current as blocks are reassigned between operators. For a full breakdown of fields, connection type values, VPN detection, and dataset update frequency see the IP Address Coverage page.

IP dataset field	Coverage scope
Country	Available for ~99% of routed IPv4 and IPv6 space
Region and city	Available for the majority of routed address space; sparser in some regions
ASN and ISP	Derived from routing data; available for publicly announced prefixes
Connection type	Residential, business, hosting, mobile — classified where routing signals are available
VPN / proxy detection	Available as a separate field; based on known VPN ranges and exit-node data
IPv6	Full /32 to /128 range coverage; ~99% of announced IPv6 prefixes

Reverse geocoding worldwide

The reverse geocoding API accepts any latitude/longitude on Earth and returns the nearest named place or address, along with admin-level context (country, region, locality) and the distance to the matched point. Coverage quality reflects the same regional depth as the forward geocoding index — richer in data-mature countries, admin-level only in sparse areas.

Country-focused coverage pages

• Australian Geocoding Coverage
• UK Geocoding Coverage
• USA Geocoding Coverage
• Singapore Geocoding Coverage
• Irish Geocoding Coverage