OpenStreetMap
OSM GPX extractor for non experts
Vum pangoSE matgedeelt de(n) 13. Februar 2020 op English. Lescht Aktualiséierung de(n) 23. Juni 2020Hi. During my engagement in swedish hiking groups I became aware of the need for a service for extracting GPX-files with huts and shelters to put into GPS-devices and phones.
I built a simple website to fill this need which was a fun and learning experience :)
Try it out here: https://pangose.github.io/gpx-extractor/ Code: https://github.com/pangoSE/gpx-extractor
Diskussioun
Bemierkung vum mmd de(n) 13. Februar 2020 um 21:27 Auer
I believe one of your example queries does not return any geometry information for ways, i.e. you’re probably missing out a few thousand objects. Maybe try this one here: https://overpass-turbo.eu/s/QHD
Bemierkung vum pangoSE de(n) 14. Februar 2020 um 10:03 Auer
Hi mmd, which query do you mean?
This is the function that builds the query: function buildQuery(areaCode) { var q = ‘https://overpass-api.de/api/interpreter?data=[out:xml][timeout:325];area(‘+areaCode+’)->.searchArea;’+query+’out;’;
I decided not to add “center” after out because it does not seem to be necessary and make the query time much longer. togpx() handles the data like this: “Points are converted to Waypoints. Lines are converted to Tracks. (Multi)Polygons are represented as a Track of their outline(s).” see https://github.com/tyrasd/togpx
I don’t know how this looks on a GPS-device because I don’t own one.
Bemierkung vum mmd de(n) 14. Februar 2020 um 10:10 Auer
Query was the second one “huts, shelters, shalets, … “. In your query you use “nwr” which returns nodes, ways, and relations. However, for the ways, you only receive the “node ids”, not the actual nodes with lat/lon details.
togpx cannot create anything meaningful in this case, as there’s simply no geoemtry available. Please compare:
Bemierkung vum H@mlet de(n) 14. Februar 2020 um 12:33 Auer
When I search for “Brittany”, it finds Q327, which is the historical entity and has no OSM relation ID, as it doesn’t exists anymore.
The correct result would be Q12130 which has the correct relation ID.
Regards.
Bemierkung vum H@mlet de(n) 14. Februar 2020 um 12:39 Auer
Otherwise it worked quite well with area “ Sweden “, with Firefox mobile 68.5.0 and osmand.
Bemierkung vum pangoSE de(n) 14. Februar 2020 um 20:57 Auer
Hi Hamlet. Have a look on WP:Brittany. It says: “This article is about the cultural region in the north-west of France. For the current French administrative region, see Brittany (administrative region).”
So in this case “Brittany (administrative region)” should work in your case as it is linked with Q12130.
Bemierkung vum pangoSE de(n) 14. Februar 2020 um 20:58 Auer
@mmd Thank you! Now I understand. I will add center to all queries then. :)
Bemierkung vum H@mlet de(n) 14. Februar 2020 um 23:01 Auer
Right, it’s a bit cumbersome, but it works ! :-)
You might want to add some kind of completion, looking for wikidata items with OSM IDs, because when I tried, your tool asked me to change the first item, which was confusing.
Anyway thanks for your tool. You could add a “water” section, I like to have drinking_water, toilets and such highlighted on my maps.
Regards.
Bemierkung vum pangoSE de(n) 16. Februar 2020 um 10:59 Auer
I now added jQuery Autocomplete from the Wikipedia API. I’m quite happy with the result! :)
Bemierkung vum pangoSE de(n) 19. Februar 2020 um 22:06 Auer
Code is now at https://github.com/pangoSE/gpx-extractor MIT license. Feel free to create issues with ideas for improvements or bugs.