|
Hi There. I use RideWithGPS that uses OSM maps as a base. I can't route a trail in a couple of sections - I have checked the source maps in OSM and can't see any particular reason why it won't work.
Any pointers or advice? |
|
I'd try illustrating "the bit that doesn't route" by creating a route on osm.org itself, like https://www.openstreetmap.org/directions?engine=graphhopper_foot&route=-44.6479%2C168.9651%3B-44.6518%2C168.9593#map=16/-44.6498/168.9621 . Then look at the dates of the osm.org data and compare it with whatever RideWithGPS is using (which might be substantially older). Ah I see with that one, it looks like the stile won't allow routing by bicycle and the RWGPS site is older there. Thanks
(06 Mar '18, 21:15)
The Flahute
|
|
Thanks all, much appreciated. I will feed this back to the router so they can make changes in the future. I know the trail well and have edited the sac_scale. It's an easy walk / intermediate mtb trail. The surrounding trails are more advanced hiking. I was aware about the map updates, I have found the router to be quite amenable to feedback, but I was stumped as to why it wouldn't work. Thanks for the answers. |
|
Won't route on the track, keeps going around. The Wharfedale Track (https://www.openstreetmap.org/#map=15/-43.2477/172.0478) So this won't route even on OSM. https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=-43.2565%2C172.0407%3B-43.2522%2C172.0448#map=16/-43.2559/172.0407 1
Hi, the problem here seems to be that sac_scale tag value, which is not well recognized by the routing services. First thing first, I'd like to suggest to you to use a proper routing service to plan your rides/hikes, see this one https://maps.openrouteservice.org/directions?n1=-43.223316&n2=172.062464&n3=13&a=-43.25594,172.040963,-43.231634,172.034526,-43.198387,172.040148&b=2b&c=0&g1=-1&g2=0&k1=en-US&k2=km There are a few trail section tagged like this one https://www.openstreetmap.org/way/43666722, with sac_scale=hiking;mountain_hiking tag, this one is preventing both graphhopper and OSMR to work properly, the only one working is the "hiking" routing, while both "walking", "mountain bike" and normal bicycle routing aren't working. If you have any local knowledge of the area you might want to update that sac_scale tag for those trail sections and leave just one value instead of "hiking;mountain_hiking". I'm pretty sure it'll then work as expected. Also keep in mind that routing services update their map once per month or so, so don't expect the routing to work in just a few days. Cheers
(07 Mar '18, 10:26)
Constable
1
sac_scale shouldn't affect bicycle routing. For bicycles there is mtb:scale which isn't present here. Although I'm unsure if GraphHopper or OSRM have a fallback to sac_scale if no mtb:scale is present.
(07 Mar '18, 10:54)
scai ♦
1
Sac scale seems to affect bicycle routing as well, see this one https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=46.30058%2C10.06819%3B46.29851%2C10.07173#map=17/46.30114/10.06949 compared with this other one https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=46.30225%2C10.07301%3B46.30148%2C10.07297
(07 Mar '18, 11:13)
Constable
2
If a particular router has a particular problem in a particular area I'd definitely feed that information back to whoever maintains the router. If you explain the problem to them it's quite likely going to be a combination that they've just never thought of.
(07 Mar '18, 12:17)
SomeoneElse ♦
|