tilemaker VS Graphhopper

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.

Well I think what he means is that we dropped the explicit support of Android and the example app with offline maps (Mapsforge), see this issue: https://github.com/graphhopper/graphhopper/issues/1940

But offline routing should still work on Android. But as you need JDK 1.8 support this will exclude a few older Android versions and devices, I think.

Graphhopper. It has an Android client that uses its web service. You can also try out the web app.

This is now fixed and deployed. See the route here and the specific fixed examples here. Note that you can still find the dangerous spots via clicking the "stop" icon below the route information multiple times. But this is likely a result of the bad cycling infrastruture as cycle.travel contains these short dangerous parts too and if you do such longer routes for Germany it does not happen.

I'd suggest refactoring to use a self hosted version of Graphhopper (https://www.graphhopper.com/open-source/ - they have a docker image you can use and pass in an OSM file to build a graph on) or OpenRouteService to limit your cost exposure to google.

Open Source. The routing server is open source too and geocoding too.

Valhalla is great (I've contributed a few patches and run it for a while)!

Also check:

http://project-osrm.org/

https://www.graphhopper.com/open-source/

if you attached a geolocation to each meeting that should be possible. either using the google maps API or a self-hosted graphHopper instance

I just improved the documentation for the map matching a bit. Maybe this also helps a bit.