josm VS openmaptiles

I modified an open source GPX recording app called Trackbook to turn it into a 24/7 recorder, and I wrote about it here:

https://voussoir.net/writing/obsessed_with_gpx

I have a few recent commits in my repository that I haven't put into a versioned APK yet though.

The output GPX files can be viewed on the PC with JOSM:

https://josm.openstreetmap.de/

Here's a view in my editing-program (https://josm.openstreetmap.de/):

JOSM has quite convenient merge/split functions, making deletion and re-tracing unnecessary. I took care of the issue in https://www.openstreetmap.org/changeset/134052747

Record your track and upload it onto Open Street Map. That's the map service that Strava and Garmin utilize. You'll be able to add the trail for everyone to see regardless of the program as long as it uses OSM. JOSM is a really good program to edit OSM and here's a video to get you started on how to use it.

Great for preparing data for OSM, but JOSM is the only desktop editor for actually making contributions.

One that comes to my mind would be JOSM: https://josm.openstreetmap.de/

If you want to do more advanced editing, I would suggest JOSM. It is very powerfull and there is a huge list of plugins. You can do almost anything, but it runs on desktop devices.

You could also do all of this in OpenStreetMap or one of its open source editors like JOSM, then run a filter for tags of those features (probably something like “playfield” or “baseball”) in Overpass Turbo. One cool thing about this option is all your work would be visible and usable by the general public forever.

If you want to look at the structure of OSM, JOSM is a good desktop application and Vespucci for Android is the least awful option there. The wiki can tell you what the tags mean; here's more info on the route tag. You can find more info about the Overpass API that lets you run weird queries against the map here.

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?