Meteoprog Geocoding API provides location search and location resolution for websites, apps, dashboards, widgets, and backend systems that work with weather data, city pages, or location-aware products. The API can be used as a geocoding API, city lookup API, coordinate search API, and populated place search API.
The endpoint group supports city search by name, city search by URL, coordinate-based city resolution, radius-based populated place lookup, and hierarchical browsing by continent, country, region, and city.
Geocoding API methods
Meteoprog Geocoding API uses the standard API path structure with locale, format, and apiKey, then adds location-specific identifiers or search values.
Geocoding API parameters
json or xml
What the Geocoding API provides
The Geocoding API provides machine-readable access to geographic hierarchy and populated place search.
It can be used to:
- resolve a city from a search term
- resolve a city from a URL slug
- resolve the nearest populated place from coordinates
- search populated places within a radius
- browse continents, countries, regions, and cities
- paginate city lists by country or region
This makes the endpoint group suitable for weather websites, location-driven dashboards, city selection flows, search interfaces, and backend systems that need deterministic location resolution before requesting forecast, archive, astronomy, or air quality data.
Search by Name, URL, coordinates, and radius
Meteoprog Geocoding API supports several location search modes.
Search by city name
Use city name search when users type a populated place name directly.
Search by city URL
Use city URL search when your product works with location slugs or stored city URLs.
Search by Coordinates
Use coordinate-based search when your application receives latitude and longitude and needs to resolve the nearest populated place.
Search by Coordinates + Radius
Use radius-based lookup when your product needs nearby populated places around a coordinate within a defined search distance.
Geographic entities available in the API
The Geocoding API works with these geographic levels:
- continents
- countries
- regions
- cities
- populated places resolved from coordinates
This is useful when your product needs both hierarchical browsing and direct search.
For example, a weather website can build a continent -> country -> region -> city flow, while a dashboard can resolve the nearest city from coordinates and then request forecast or air quality data for that city.
Pagination and city listings
City lists are paginated for country-based and region-based browsing.
Paginated endpoints:
- cities by country
- cities by region
This is important for applications that need large location lists, searchable selectors, or structured navigation across populated places.
Coverage and localization
Meteoprog API platform supports 2,150,000+ populated locations worldwide and 35+ languages.
This makes the Geocoding API suitable for international weather products, localized city pages, and multi-language applications that need worldwide populated place coverage.
Developer Access and production usage
You can test Meteoprog Geocoding API in Meteoprog API Sandbox before production integration.
Developer Access uses the same endpoint structure and response formats as production. The main differences are limits and available data scope.
For Developer Access, paginated populated-location listings are limited to the first three pages per country.
Production plans remove this development restriction and are intended for live applications, commercial workloads, and real user traffic.
Related Meteoprog APIs
Geocoding API is typically used together with:
- Weather API
- Air Quality API
- Historical Weather API
- Astronomy API
- Weather Forecast Calendar API
A common integration flow is:
- resolve a location with Geocoding API
- get the relevant Meteoprog city ID or populated place
- request forecast, archive, astronomy, or air quality data for that location
Use cases
This geocoding API can be used for:
- weather websites with city search
- dashboards with coordinate-based location resolution
- city selectors in apps and internal tools
- localized city pages
- search interfaces with country and region browsing
- location resolution before requesting weather or air quality data
FAQ
What does the Geocoding API return?
The Geocoding API returns hierarchical geographic lists and populated place search results, including continents, countries, regions, cities, and coordinate-based city resolution.
Is this a city-based geocoding API?
Yes. The API supports city search, city listing, and populated place resolution for weather-enabled products.
Can I search locations by coordinates?
Yes. The API supports both nearest populated place lookup by coordinates and populated place search within a radius.
Are city lists paginated?
Yes. City lists by country and city lists by region use pagination.
Can I search locations by city URL?
Yes. The API supports city lookup by URL slug.
Can I test Geocoding API before production?
Yes. You can test the endpoint group in Meteoprog API Sandbox and then move to production without changing the API structure.