future-mvt
go-pmtiles
future-mvt | go-pmtiles | |
---|---|---|
1 | 4 | |
9 | 310 | |
- | 2.6% | |
10.0 | 8.4 | |
over 1 year ago | 8 days ago | |
Go | ||
- | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
future-mvt
-
How The Post is replacing Mapbox with open source solutions
> PMTiles aside, this is still Mapbox’s world.
Isn't this is a bit like saying we're still in Google's world because most maps still use Web Mercator? :)
Good tech builds on what came before. Mapbox did a lot of ground-breaking work in building tooling around OSM, but so have many others. The fact that they named it Mapbox Vector Tiles is be genius in hindsight, because even though we may use tons of tooling they didn't create to build and render them, their name is still there.
> The next challenge is to evolve the tech stack to something beyond what Mapbox worked up five/ten years ago.
Agreed, and I think we've seen a lot of iterative work in the open since then. The next challenge is likely building a OSS stack to do proper 3D: open data (including OSM) to pixels, and that work is already beginning across a lot of organizations: https://github.com/nyurik/future-mvt/discussions, Overture Maps, MapLibre, etc.
go-pmtiles
-
Protomaps – A free and open source map of the world
I just used their pmtiles tool to grab a map of just the area around Half Moon Bay, south of San Francisco.
I grabbed the latest macOS Go binary from https://github.com/protomaps/go-pmtiles/releases
I found a rough bounding box using http://bboxfinder.com/#37.373977,-122.593346,37.570977,-122....
Then I ran this:
pmtiles extract https://build.protomaps.com/20231023.pmtiles hmb.pmtiles \
-
How The Post is replacing Mapbox with open source solutions
Yes, PMTiles is a tradeoff that isn't appropriate for transactional use cases. SQLite is pretty good for that already.
There is a throughput limit on S3 files of approximately 5500 GETs/sec per key. Bare archives on S3 is an appropriate choice for small-scale, zero maintenance deployments. If your application demands any thing close to that level of throughput, you're probably either:
* Serving individual tiles over the internet: you should use the CDN integration http://protomaps.com/docs/cdn ; most tile requests will be cached and only misses will interact with the S3 bottleneck.
* Bulk accessing a spatial subset of tiles: You shouldn't be requesting HTTP GETs for single tiles, but instead entire subsets of tiles with a single Range request made possible by the internal Hilbert curve ordering. This is still WIP here: https://github.com/protomaps/go-pmtiles/issues/31
What are some alternatives?
valhalla - Open Source Routing Engine for OpenStreetMap
maputnik - An open source visual editor for the 'MapLibre Style Specification'
TileServer GL - Vector and raster maps with GL styles. Server side rendering by MapLibre GL Native. Map tile server for MapLibre GL JS, Android, iOS, Leaflet, OpenLayers, GIS via WMTS, etc.
PMTiles - Cloud-optimized + compressed single-file tile archives for vector and raster maps
planetiler - Flexible tool to build planet-scale vector tilesets from OpenStreetMap data fast
tippecanoe - Build vector tilesets from large collections of GeoJSON features.
titiler - Build your own Raster dynamic map tile services
tilemaker - Make OpenStreetMap vector tiles without the stack
basemaps - Basemap PMTiles generation and cartographic styles for OpenStreetMap data and more