OK, I have fixed my fair share of route relations, both public transport and bicycle and foot routes.
I find it easier to EDIT them, when they are sorted. To figure out there are problems with them, when they are sorted. JOSM actually does a great job with the sorting. For bicycle, foot and horse route relations it can handle forward/backward roles very well, when they branch. I've been developing PT_Assistant for the parts that are missing in JOSM. It now comes with routing helper functionality, which works for bicycle routes too since this summer. Instead of having to manually select, split, deselect not needed part of ways manually, you can simply direct it by pressing numbers, which correspond to segments rendered in different colours. It would be wonderful if that could be implemented in iD as well. No need to know much about the underlying relations. If you know the itinerary you want to add, you're good to go. It takes into account oneway traffice and turn restrictions for the mode of transport of the route relation you are editing. So it behaves differently when you are closing gaps in bus route relations than when you're doing the same for bicycle route relations. It still requires lots of JOSM atm. I'll give a demo/workshop of how it works during SotM in Heidelberg. In the mean time I'm creating videos on Youtube. https://www.youtube.com/user/yoyo77777yoyo Polyglot On Mon, Aug 19, 2019 at 6:57 PM Andy Townsend <ajt1...@gmail.com> wrote: > On 19/08/2019 17:21, Peter Elderson wrote: > > the only way for the likes of me is to use detection tools and > maintenance tools to order data by hand at the mapping level, so ordinary > people can use waymarkedtrails to get usable linear gpx-s for their > basecamps, route editors, trip planners, navigation apps and devices. > > You keep perpetrating this myth - you're suggesting again that ways in > routes need to be sorted before they can be used in Garmin software and > navigation devices. It simply isn't true. For about 11 years now I've > been creating Garmin maps based on OSM data, and I've been walking along > local and national trails in the UK for far longer. Never have I needed to > "follow a GPX" - it seems a very alien thing to want to do, and (as > mentioned previously) isn't actually supported by any of the various Garmin > hiking GPSs that I've used. If you want to do that - fine - but not > everyone does. > > I suspect that "Ordinary people" will just download OSM maps from > http://garmin.openstreetmap.nl/or one of the alternatives - they'll see > the route on-screen and they will navigate using that. Sometimes they'll > stray from it because they've arranged somewhere to eat or stay; they're > not limited to "only walking along the actual ways that form the official > route" which you seem to be. > > If you have a different requirement then that's very much a personal > requirement for you; please don't try and dissuade "ordinary people" from > contributing to mapping hiking routes. If you want to manually sort and > rearrange hiking route data in a way that doesn't prevent everyone else > from contributing that's also fine, but please don't raise the bar to > contributions so high that people can't contribute at all. You'd > essentially be filling the role that Kevin Kenny identified above as > "Someone in the community who can handle relations will then have the > geometry already established, so tidying the topology becomes a clerical > task". > > The people we want adding hiking routes to OSM are people who've just > taken their boots off, know where routes have been diverted, and know what > the surface tags etc. should be, not people who've never emerged from > behind a PC. > > Best Regards, > > Andy > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
