Map of Didi in MBTiles Vector 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.
.mbtiles-vector
About MBTiles Vector
Map of Didi in MBTiles Vector: 292 buildings, 25 km of roads — in the WGS 84 coordinate system, units are meters.
Which layers are in the file
This file for the selected area contains:
- Roads
- Buildings
- Water
Geometry by layer
- Roads — lines in vector tiles, layered by road class
- Buildings — building polygons in vector tiles
- Water — water polygons in vector tiles
What the file carries
The MBTiles Vector file for Didi: features are split into named layers, OpenStreetMap tags are kept as feature attributes.
File size
The expected size of the MBTiles Vector file for Didi is about 1 MB; the exact size depends on the chosen layers and area.
Coordinate systems
WGS 84 (EPSG:4326), selectable in the wizard
Units
Meters (projected in the chosen coordinate system)
| Category | GIS |
| File extension | .mbtiles-vector |
| Tier | Open Beta |
How to use MBTiles Vector for Didi
- MapLibre GL or Mapbox GL JS — run a tile server over the file and add it as a vector source: the map appears in the browser and you describe the style yourself.
- Maputnik (free, runs in the browser) — build the style by hand: the editor reads the layer list from the file and offers it as a list.
- TileServer GL — serve the container as a ready service at an address like /{z}/{x}/{y}.pbf, together with generated TileJSON.
Programs that open MBTiles Vector
FAQ: MBTiles Vector for Didi
How does it differ from regular MBTiles?
Regular MBTiles stores ready-made images -- the map is already drawn and cannot be recoloured. Here the file holds geometry and attributes, and you set the styling.
How does it differ from PMTiles?
The tiles are the same; the container differs. PMTiles is built for cloud hosting and partial reads over HTTP; MBTiles Vector is an ordinary file, handier for local work and a tile server.
How deep is the pyramid?
If you do not pick the depth yourself, I match it to the area and feature density and write the chosen range into the file. A depth you picked explicitly is never changed: if it is beyond reach for that area I refuse honestly instead of handing over a truncated file.
Why is the area limited?
Vector tiles are built from the features themselves, and the cost grows as tiles times features. For very large or very dense areas I refuse up front and suggest a smaller area -- that is fairer than a long build with an unknown outcome.
