This is just anecdotal and someone with an understanding of the algorithm would have a better answer, but using elevation data, I've made this work for a couple of hiking routes where the two routes are close to each other and (of course) wind up in the same place. One of them is in Yosemite, where the direct route climbs steeply via stairs and the alternative is a gentler climb, .6 km longer. So I think it works for some circumstances, but I'm not sure which ones.
The elevation data is embedded in the map; no contours required. On Saturday, May 25, 2019 at 2:41:03 AM UTC-7, jot ess wrote: > > Hi all, > I have been reading a bit in this forum and my impression is that I am not > alone with my question and there has not been a clear answer yet: Osmand+ > claims it uses elevation data - but obviously it doesn't. Or only under > certain circumstances. > > When I use Osmand+ for bicycle routing with Osmand routing engine and > setting "use elevation data" set "on" it doesn't make any difference to > "off". Nor does it make a difference whether I let it calculate a route > leading up a steep incline or down. > The elevation graph clearly shows that the altitude data is present and at > least roughly correct. > > Have I missed any other setting? Have I missed an answer somewhere in the > forum? Is there any additional add-on to Osmand that I would need? (I have > the contours plugin, but as far as I understand this only plots graphical > lines with no actual elevation data.) > > Best regards > Joachim > > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/6909bd07-0df7-4316-a889-791c019a8401%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
