Checking the data itself before you analyse it: tag completeness, mapping activity, broken and self-intersecting geometry, administrative boundaries by level. Useful for judging how far the conclusions about this area can be trusted.
Computes what share of the features of a layer carry names and key tags — the completeness of OSM coverage in this area.
A proxy estimate of data freshness: osm2pgsql does not always keep the timestamp of an edit, so activity is estimated from the density of features and the richness of tags rather than from the date of the last change.
Finds invalid and self-intersecting geometries and returns them with the places where the errors are.
Exports the administrative boundaries of the chosen admin_level with the areas computed.
The input is a rectangular bounding box in WGS84 plus one of nine data layers; some tools also take a point. The output is GeoJSON, JSON metrics or a GeoTIFF.
| Layer | What it holds |
|---|---|
| buildings | buildings |
| roads | roads and streets |
| poi | points of interest: services, shops, tourism |
| water | water bodies |
| green_areas | green areas: parks, forests, lawns |
| railways | railways |
| boundaries | administrative boundaries |
| landuse | land use |
| waterways | waterways |
Every tool in the section is free. The bounding box may cover up to 100 km². Rate limits are 10 requests per minute per tool run and 30 requests per minute for reading the catalogue. Without signing in you get up to 10 successful calculations a day; after that the service asks you to register and answers 402 with the code login_required. A box larger than the allowed area is also 402, and an unknown tool id is 404.