PMTiles VS openmaptiles

I am a novice at GIS and mapping but when I got started I thought a map/tile server was the only way to build mapping webapps.

But, in my admittedly simple application PMTiles can cover a lot of my visualization use cases with a thing Django app doing GEOJson for interactive stuff.

https://github.com/protomaps/PMTiles

This is awesome. Such a great use case for nix.

I do a lot of geospatial processing in the cloud and I've been using Tippecanoe a lot to create vector tiles. It pairs well with PM Tiles for storing on the cloud. It seriously increases the web app performance for massive data sets. I queue these up with ECS tasks to process our json/csv/parquet input and create optimize vector tile outputs.

https://github.com/felt/tippecanoe

https://github.com/protomaps/PMTiles

Tippecanoe would be a great addition to your nix packages. I've been thinking more and more about how Nix could fit into this pipeline.

Great work!

The thing being discussed is designed for cloud, so I think self managed is a better description?

https://protomaps.com/docs/cdn

Self hosting pmtiles is straightforward also, make a file available to a server that supports range requests:

https://protomaps.com/docs/pmtiles#2.-serve-your-file-locall...

It might've just been this: https://github.com/protomaps/PMTiles/tree/main/serverless/aws

There isn't a tool to do that right now. It could be a fit in either https://github.com/protomaps/go-pmtiles or https://github.com/protomaps/PMTiles/tree/main/python - the Go program is faster and more production ready at this point. I imagine if folders are working for you the quantity of tiles doesn't number into the millions, so the Python program might be sufficient.

Feel free to open an issue.

PMTiles

For the next revision of the JS decoder I'm including `fflate` as a dependency so clients can decompress gzipped tile data using JavaScript.

https://github.com/protomaps/PMTiles/blob/master/js/package....

Openmaptiles uses docker-compose for its work. It fails flat on its face with podman.

OpenMapTiles

What is the advantage of this project over something like openmaptiles https://github.com/openmaptiles/openmaptiles

Flatmap calls into user-defined profiles in 2 places: first when processing each input element to map it to a vector tile feature, then a second time right before emitting all vector features in a layer.

That second call lets you manipulate vector features on each tile using JTS geometry utilities (i.e. merge nearby polygons or lines with the same tags). PostGIS uses GEOS which is ported from JTS so you have access to pretty much the same geometry utilities - often with the same name.

It's definitely not as flexible as a PostGIS based solution - especially if you join faraway features that don't appear on the same tile, but in practice it was enough to port the entire OpenMapTiles schema.

See the basemap layers package: https://github.com/onthegomap/flatmap/tree/main/flatmap-base...

For example see the landcover layer: https://github.com/onthegomap/flatmap/blob/main/flatmap-base...

Which was ported from the SQL contained in: https://github.com/openmaptiles/openmaptiles/tree/master/lay...

Also, this OpenMapTiles PR might help improve your pipeline after it gets merged: https://github.com/openmaptiles/openmaptiles-tools/pull/383

To fully self-host a route planner (e.g. a "Google Maps" equivalent) you need GraphHopper for the routing and two other parts: you also need some visualization aka "maps" (e.g. with OpenMapTiles) and you need the address search (e.g. with Photon).

Probably not the answer you're looking for, but I have been using openmaptiles to pull osm into postgres (in docker using quickstart.sh). If you can talk postgres in python then maybe that is for you?