Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Vector Datasource | 481 | a month ago | 249 | other | Python | |||||
Tilezen vector tile service - OpenStreetMap data in several formats | ||||||||||
Osmpbf | 130 | 2 | a year ago | 3 | May 10, 2021 | 3 | mit | Go | ||
OpenStreetMap PBF file format parser in Go Lang. | ||||||||||
Osmpbf | 76 | 1 | 4 | 4 months ago | 27 | May 30, 2022 | 8 | apache-2.0 | Rust | |
A Rust library for reading the OpenStreetMap PBF file format (*.osm.pbf). | ||||||||||
Openmetromaps | 40 | a year ago | 8 | Java | ||||||
Main repository for OpenMetroMaps | ||||||||||
Osmflat Rs | 33 | 3 months ago | 1 | October 18, 2020 | 5 | apache-2.0 | Rust | |||
OpenStreetMap flatdata format and compiler | ||||||||||
Opentrafficcammap | 14 | a month ago | 7 | mit | JavaScript | |||||
A crowdsourced database of traffic cameras | ||||||||||
Osm2mp | 8 | 5 years ago | 6 | Perl | ||||||
Convert Openstreetmap data to MP format | ||||||||||
Tiny Osmpbf | 8 | 30 | 1 | 7 years ago | 2 | December 04, 2016 | isc | JavaScript | ||
smallest osm.pbf parser | ||||||||||
Osm Boundaries | 8 | 4 years ago | 1 | |||||||
data dump of openstreetmap boundaries in geojson format | ||||||||||
Osm2xmap | 6 | 6 years ago | 6 | gpl-3.0 | C++ | |||||
Converter from OpenStreetMap data format to OpenOrienteering Mapper format. |
The Nextzen vector tile service provides worldwide basemap coverage sourced from OpenStreetMap and other open data projects, updated ~quarterly.
Vector tiles are square-shaped collections of geographic data that contain the map feature geometry, such as lines and points. Information about how map features are drawn is maintained in a separate stylesheet file.
For many purposes, vector tiles are more flexible than raster tiles, which are images that already have the visual appearance of the map features pre-drawn. With vector tiles, there is no need to head back to the server and fetch a different set of tiles if you want to filter the output or change the style of a road or color of a building.
Vector tiles make real-time rendering possible by sending the underlying data geometry and tags directly to the client, whether that’s a browser or a native mobile app. Buildings and roads can be rendered in different ways, or not at all, when the vector tile is downloaded, and changes happen instantly on the client's side.
With vector tiles you have the power to customize the content and visual appearance of the map. We're excited to see what you build!
To start integrating vector tiles to your app, you need a developer API key.
The URL pattern to request tiles is:
https://tile.nextzen.org/tilezen/vector/v1/{tilesize}/{layers}/{z}/{x}/{y}.{format}?api_key=your-nextzen-api-key
Here’s a sample tile in MVT format at 512 size:
https://tile.nextzen.org/tilezen/vector/v1/512/all/16/19293/24641.mvt?api_key=your-nextzen-api-key
Here’s a sample tile in TopoJSON format at 256 size:
https://tile.nextzen.org/tilezen/vector/v1/256/all/16/19293/24641.topojson?api_key=your-nextzen-api-key
More information is available about how to use the vector tile service and specify custom layers in the service (though we recommend the default all
layer).
The Tilezen vector tile stack provides tiles in a variety of formats (service docs):
Mapbox Vector Tile: use the .mvt
extension. This is a compact format using protocol buffers that is used for raster tile rendering in TileMill2 and vector rendering in MapboxGL.
TopoJSON: use the .topojson
extension. TopoJSON is an optimized form of GeoJSON that saves space by encoding topology and reducing replication of shared geometry.
GeoJSON: use the .json
extension. GeoJSON is easy to get started with, human-readable, and compatible with many tools.
We recommend TopoJSON
format for desktop web development, and MVT
format for native mobile development. The Nextzen vector tile service gzips tiles automatically, so the TopoJSON file format is comparable in file size to MVT over the wire, and it's much friendlier to debug.
How to draw the tile in a browser is up to the vector-friendly visualization tool, such as SVG, Canvas, or WebGL. The Tangram rendering engine, which uses WebGL, is one way that you can draw the vector tile service in 2D and 3D maps.
Vector tiles are served by clipping geometries to the tile bounding box, and then simplified to match the zoom level to avoid unnecessary complexity at lower zoom levels. These geometries and features are also further processed to facilitate styling.
When changes are made to OpenStreetMap or another map data sources, rather than waiting for an image tile to be redrawn, only the geometry coordinates and feature attributes for that particular building or road need to be updated in the vector tile.
Depending on the URL syntax, Mapzen vector tiles can return all of the map data, or just individual layers, or combinations of layers, including water, earth, landuse, roads, buildings and points of interest(POI).
If you are interested in setting up your own version of this service, follow these installation instructions, or use Docker!
There is a suite of tests which can be run against a tile server to verify query results in well known tiles.
This is based on the work of Michal Migurski, and extends his OSM.US-hosted vector tile service with additional data and format support.