▲ | Doctor_Fegg 4 days ago | |||||||
Nice! I added a similar feature to cycle.travel (my site) a few months back. 5% of the work was writing the code to route only on waymarked routes, 95% was writing code to "heal" the accidental breaks in OSM bike route data... | ||||||||
▲ | allg12 3 days ago | parent | next [-] | |||||||
Oh wow, nice! I wasn't aware cycle.travel had this. I thought I had done something new but I see I was mistaken. By the way, good job on cycle.travel - the route finding is super smooth! | ||||||||
▲ | wintermutestwin 4 days ago | parent | prev | next [-] | |||||||
Your site doesn't appear to have waypoints? As an avid cyclist, I couldn't imagine just using some calculated route between two points. I ride for fun, not transportation. | ||||||||
| ||||||||
▲ | PrismCrystal 4 days ago | parent | prev [-] | |||||||
What does “waymarked routes” mean, exactly? And same question for the OP. Doing OSM editing from Mapillary imagery in various US states, I find that the roads that have roadside signage as “official bike routes”, predate modern safe(r) bike infrastructure. These are often highways that frankly look like death traps: no shoulder, high speed limits. Especially when so many North American long-haul cyclists now are riding “bikepacking” setups, it may be preferable for a router to prioritize quiet agricultural tracks and other unpaved terrain over the supposedly official bike route. | ||||||||
|