My use-case for cycle.travel is having a single polyline that I can make into a route guide at https://cycle.travel/routes . Currently there’s two dozen: I’d like there to be thousands. So:
> - diversions and alternatives Give them consistent roles so I can ignore them. > - routes with different endpoints in the forward/backward directions Not fussed. I only do the route in one direction. > - spur routes Again, consistent roles so I can filter them out. > - one-way routes that may be circular If there’s an agreed start point, then put the node in the relation with an appropriate role. cheers Richard -- Sent from: http://gis.19327.n8.nabble.com/Tagging-f5258744.html _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
