overpass.ch

The plan of the API key of this connection and its use this month: Overpass requests used and left, when the allowance starts again, running queries, elevation lookups, geocoding requests, and the date of the data. It names the products on a free plan, which is not for commercial use. It does not count as a request.

Heights above sea level in metres for a list of points, negative at sea. Switzerland and Liechtenstein: swissALTI3D, a 2 m grid of the ground (credit "© swisstopo"). Elsewhere on land: Copernicus GLO-30, a 30 m grid of the surface that includes buildings and trees. At sea: GEBCO. Each point counts as one lookup; account_status shows the plan maximum per call.

Elevation profile along a path of two or more points: distance, ascent, descent, the lowest and the highest point, and up to 100 points along the way (distance from the start, height, lat, lon). The path is sampled every 90 m unless samples or interval_m is set. Each sample counts as one lookup, up to the plan maximum per call.

Finds the address or place at a point (reverse geocoding). detail chooses what to return: the nearest address or object (address, the default), the street, the district, the city, the county, the state or the country that contains the point. The result has the same fields as those of geocode_search. One call counts as one geocoding request.

Finds places, addresses and points of interest by name (geocoding). Partial text works, as for autocomplete. Each result has the name, the address, lat and lon, a bounding box (south, west, north, east), the OpenStreetMap element (osm), and for ways and relations an overpass_area_id to use in overpass_query as area(id:N). Languages: en, de, fr. One call counts as one geocoding request.

Searches the cookbook of overpass.ch: Overpass queries that were tested on the full planet, with explanations. Give a topic in a few words, such as "bakeries in a city", "hiking routes", "count buildings" or "changes since a date", and get the 5 closest examples with their query and a link. Free: it does not count as a request.

Runs an Overpass QL query on the full OpenStreetMap planet at overpass.ch (minutely updates) and returns the matching nodes, ways and relations with their tags. Start the query with a settings line such as [out:json][timeout:25]; JSON is used when the query does not set [out:]. [timeout:N] stops the query after N s: at most 120 s through this tool, and the plan may allow less. Patterns: - Box (south,west,north,east): nwr["amenity"="cafe"](47.36,8.53,47.38,8.55); out center; - Radius in metres around lat,lon: nwr["amenity"="pharmacy"](around:1000,47.3769,8.5417); out center; - In a place: overpass_area_id from geocode_search, then area(id:3600051701)->.a; nwr["tourism"="hotel"](area.a); out center; - By name (exact, local language): area["name"="Wien"]["admin_level"="4"]->.a; - Count: out count; Tags only: out tags; At most 50: out center 50; Lines with coordinates: out geom; (large) - Regex, any case: ["name"~"^Bahnhof",i] - By id: node(3470507586); out; way(id:1,2,3); out tags; - The map at a past date (Medium and Large plans): [date:"2015-01-01T00:00:00Z"] in the settings line. The answer starts with counts and the date of the data, then one JSON object per element and line, up to max_chars characters. When it is cut, call again with offset, or narrow the query. Each call counts as one request of the plan, a cut one too. Data © OpenStreetMap contributors, ODbL.