Download Codor map in Overpass JSON format
A map built from OpenStreetMap data, ready to download
Customize the map
Open this place's area in the constructor and adjust everything to your needs
Open in constructor →Map passport
What this map contains by default
This is how the map is built as-is — every setting can be changed in the constructor.
About Overpass JSON
Map of Codor in Overpass JSON — an export of real OpenStreetMap data for the selected area.
Overpass JSON is the response format of the Overpass API, a read-only query language over OpenStreetMap (Roland Olbricht, since 2008). It is a compact JSON with a list of elements (node/way/relation), their geometry, tags, and a meta block — the structure parsed directly by osmnx, the QGIS QuickOSM plugin, overpass-turbo, and dozens of pipelines that use OSM as a structured dataset. Our exporter builds JSON of the same structure from the OSM layers: each feature becomes an element of the appropriate type with id, coordinates, geometry, and tags, plus a meta section with generator and version. Honestly: we synthesize an Overpass-format-compatible response from our selection — this is not a live Overpass API query, but the result can be handed to downstream tools as a drop-in replacement for a public Overpass response.
Which layers are in the file
This file for the selected area contains:
- Roads
- Water
- Greenery
Coordinate systems
WGS 84 (EPSG:4326), selectable in the wizard
Units
Meters (projected in the chosen coordinate system)
| Category | GIS |
| File extension | .json |
| Tier | Open Beta |
How to use Overpass JSON for Codor
- Python — json.load() and work with the elements list: filter by tags, count objects, export into a table.
- jq — a quick check in the terminal: jq '.elements | length' map.json shows how many objects arrived, jq '.elements[0]' shows what a single element looks like.
- osmtogeojson — conversion into GeoJSON with one command, if it is more convenient to work in GIS or on the web from there.
Programs that open Overpass JSON
FAQ: Overpass JSON for Codor
Is this a live Overpass API query?
No. We synthesize JSON compatible with the Overpass response format from your OSM selection. In return there are no rate limits or timeouts of the public instance, and the data snapshot is reproducible.
Is the result compatible with osmnx and QuickOSM?
Yes, the structure mirrors an Overpass response (elements + meta), so downstream tools like osmnx and QuickOSM read it as ordinary Overpass output.
How does Overpass JSON differ from the main OSM API?
The main OSM API is for editing. Overpass is a read-only selection language by tags and area. Our export mirrors the Overpass response format, not the editing API.
How do I open the file?
It is plain JSON — parseable in any language. For OSM tools point them at the file instead of an Overpass URL, or load it via QuickOSM in QGIS.
Are the object identifiers in the file real ones?
No, the numbers are issued by us from a separate range that deliberately does not overlap with real OSM identifiers. That rules out confusion if the file gets mixed with a genuine export. Tags and geometry, meanwhile, are carried over unchanged.
