maplibre-gl-leaflet VS go-pmtiles

At my day job we’re heavily invested in Leaflet for historical reasons, but toward the end of last year added Maplibre as a layer on top of it via the excellent https://github.com/maplibre/maplibre-gl-leaflet. This has allowed us to begin transitioning gradually instead of being forced to jump all at once.

It’s hard to beat the simplicity of Leaflet, but neither it nor OpenLayers can handle Mapbox Vector Tiles in a performant enough manner, so Maplibre is the future for us.

On the Leaflet front, if you look at the plugins list, you'll see Leaflet.VectorGrid (made a long time ago by yours truly). And if you search for a bit, you'll find maplibre-gl-leaflet, which places a Maplibre instance inside a Leaflet map pane.

https://github.com/maplibre/maplibre-gl-leaflet exists!

It's not perfect, and you don't see the full benefit of a WebGL renderer, but if you want to keep using a Leaflet API, it's great.

Seems like MapTiler is maintaining an open source full stack vector alternative, and OpenLayers[0] looks good as well, so maybe it's time for legacy libraries to add vector support, or for users to switch libraries? There's even bindings from Maplibre GL to Leaflet [1].

I at least would find it interesting to see the two compared by someone other than me ;).

[0] https://openlayers.org/

[1] https://github.com/maplibre/maplibre-gl-leaflet

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 \

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