Download OSM Extracts

Welcome to our OpenStreetMap data download page, where we regularly provide extracts from the OSM project in PBF format. Our initial focus is on administrative areas and degree tiles. Currently, updates are provided at least weekly, with more frequent updates coming soon.

Features

  • Administrative Areas: On two hierarchical levels, we offer more than 3000 administrative areas worldwide.
  • Consistency: We use the boundaries for administrative areas included in OSM.
  • Precision: Retain as many original IDs as possible while making precise cuts at boundaries; no new or additional relations are created in the process.
  • Boundary Files: Exact cutting boundaries are available in two formats: GeoJSON and Poly.
  • Grid Coverage: Based on a common naming scheme for elevation data (HGT), we offer more than 28,000 tiles in either 1° or 10° dimension.
  • Data Protection: Metadata such as user, uid, changeset are excluded, except for version.

Example

Vatican City in JOSM

Vatican City in JOSM

By downloading and using these data sets, you support and benefit from the collaborative power of OpenStreetMap. Happy mapping!

Administrative Areas (worldwide)Administrative Areas (worldwide)
Download maps of states (level 2) or their subordinate administrative areas (level 3 or 4).
 Administrative Areas (Bavaria)Administrative Areas (Bavaria)
Download maps of Bavarian regions (level 5) or counties (level 6).
 Administrative Areas (Brandenburg)Administrative Areas (Brandenburg)
Download maps of Brandenburg regions (level 6) or counties (level 8).
 Administrative Areas (Berlin)Administrative Areas (Berlin)
Download Berlin boroughs (level 9) and districts (level 10).
 10° and 1° Grids10° and 1° Grids
Download Map
 Custom SplitCustom Split
If you need special areas or custom cuttings, please contact us directly: osm@movisda.io

Notes on the Data

  • Latest Version: In any download URL, you may replace the 12-digit timestamp with the word latest to always receive the most recent version of an extract, e.g. /admin/VA-202602190100.osm.pbf → /admin/VA-latest.osm.pbf. The response includes a Content-Disposition header, and we also support HEAD requests and the Last-Modified and ETag HTTP headers.
  • Boundary Cuts: Making precise cuts at boundaries sometimes requires splitting an original OSM way and inserting new nodes or ways at the cut point. These synthetic nodes and ways do not exist in the original OSM data. Relations, however, are never split or newly created — see Relations below.
  • Synthetic IDs: Every synthetic node or way we generate is assigned an ID higher than the highest real OSM ID found in that area at the time of generation. This guarantees synthetic IDs never collide with real OSM IDs, but it also means they are not stable across updates and should not be treated as permanent identifiers.
  • Traceability: Any way we split during cutting carries an osm:ref tag containing the ID of the original, unmodified OSM way it was derived from, so you can always trace a modified way back to its source.
  • Relations: We never add new or additional relations. A relation that crosses an area boundary keeps its original ID but may be reduced, meaning it only contains the members that lie within the extract’s boundary. Because a relation can span several areas, the same relation ID may therefore appear, in reduced form, in more than one extract file. If you need the complete relation, you can reassemble it by combining these files.
  • Living Data: OpenStreetMap is a living project, and administrative boundaries are maintained by its contributors. As a result, an administrative area can occasionally disappear from our extracts — or reappear later — if its boundary relation in OSM is temporarily removed, incomplete, or restructured. Since we rely directly on OSM’s boundaries, our data reflects these changes. We actively participate in maintaining and improving these boundaries ourselves.
  • Full Metadata: These extracts omit metadata such as user, uid, and changeset to protect contributor privacy. If you need a version that retains this metadata, please contact us directly.