Download a map of Minsk: which format for which task
You can download a map of Minsk in a couple of minutes, and the main question isn't "where" but "in which format" — because a map for printing, for AutoCAD, for GIS and for a navigator are four different files. Let's go through it by task: what to choose, how to limit the area and what ends up inside the file.
Step 1. Choose the boundary
The first decision is which territory you take:
- The whole city within its administrative boundary. Good for an overview map, a scheme, a presentation. The file comes out heavy, and fine detail isn't readable on a city-wide plan anyway.
- A district or several neighbourhoods. Optimal for design work and base layers: a sensible data volume with full detail.
- A block or the surroundings of an address. For a drawing, a site plan, an illustration in a report.
A practical rule: the larger the area, the lower you should set the detail level, otherwise the file will take minutes to open. For vector formats the weight grows with the number of objects, not with the size of the picture.
Step 2. Choose the format for the task
For print and design. PDF is the universal "download and send to print" option: it opens everywhere and keeps the scale. SVG is for when the map will be reworked in Illustrator, Inkscape or CorelDRAW: layers and objects stay editable, so you can recolour roads, remove clutter and add labels. Which to pick for a specific job is covered in which format for print and design.
For CAD. DWG for AutoCAD, DXF for nanoCAD, BricsCAD, KOMPAS and everything else. Geometry arrives as polylines sorted into layers — a ready base for a master plan or a site plan. A detailed comparison is in the guide to CAD formats.
For GIS. GeoJSON if the data goes into a web map or a script. Shapefile if a colleague with ArcGIS is waiting for it. GeoPackage if you want a single file with all layers and attributes — the handiest container for QGIS.
For a navigator or phone. KML and KMZ open in Google Earth and mobile apps; GPX is accepted by practically every device for points and tracks.
What the map contains
The data comes from OpenStreetMap and is sorted into layers:
- roads — from motorways to courtyard driveways, classified by type;
- buildings — footprints, some with floor counts and usage;
- water — rivers, reservoirs, ponds;
- green areas — parks, squares, forest parks;
- railways and rail transport;
- points of interest — shops, schools, stops, pharmacies.
Completeness depends on how thoroughly the territory is described in OpenStreetMap: city centres are usually mapped in more detail than outskirts and industrial zones. This is open data, and it can be used freely under the ODbL licence — with attribution.
Step 3. Download the file
The order is the same for any format: select the area on the map, pick the format from the list, set the coordinate system and detail level if needed, hit download. For design work in Minsk the metric projection is UTM zone 35N (EPSG:32635); for the web and GIS people usually stay with WGS84 (EPSG:4326).
All the ways to obtain OpenStreetMap data — from the button on osm.org to the Overpass API — are honestly reviewed in the overview of ways to download a map, including where each route hits its limits.
Easier — get a ready file straight away
Instead of hunting for someone else's export of unclear vintage, select the part of Minsk you need on the osm2cdr.ru map and download it directly in the format you want — say PDF for print or DWG for a drawing. The data will be current, the layers separated, and the boundary can follow either the city's administrative line or your own rectangle. It's free and takes seconds.
In short
- Pick the format by task: print — PDF or SVG, CAD — DWG or DXF, GIS — GeoJSON or GeoPackage, devices — KML and GPX.
- Take the whole city for overview maps, a district or block for actual work: that keeps the file usable.
- The map holds roads, buildings, water, greenery, railways and POIs from OpenStreetMap; completeness depends on how the territory is mapped.
- For design work switch on a metric projection (UTM 35N), for the web stay with WGS84.