tilemaker VS openmaptiles

You can download an extract of your country from Geofabrik, run it through Tilemaker (https://github.com/systemed/tilemaker) to get a nice mbtiles file, and then use the built-in Ruby server to give you something you can load in your web-browser locally.

I ran into this solution last week on HN and decided to give it a try. The pipeline that got me up and running was geofabrik osm.pbf[0] downloads, pass those into tilemaker[1] to create mbtiles, and then pass those into pmtiles[2] to make the pmtiles.

[0]: https://download.geofabrik.de/index.html

[1]: https://github.com/systemed/tilemaker

[2]: https://github.com/protomaps/PMTiles

Tilemaker

If you do vector tiles instead of raster, you could use tilemaker: https://github.com/systemed/tilemaker

Try to convert by GDAL files from geofabrik, ogr2ogr make my laptop hurt, but not tiles. Found tilemaker, looks better, but i get only markers, not images.

MBTiles is also a format that is supported more and more, something like tilemaker can help you with that. https://github.com/systemed/tilemaker

I'm trying to build offline maps for my app and I've figured out the app part. Now all thats left is getting the MBTiles file for all regions of the world and host it on my own somewhere. I tried to generate these files myself using [tilemaker](https://github.com/systemed/tilemaker) but I soon realised that with my limited computing power it would take forever to process 50GB worth of files for the entire planet.

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?