How and when the shortest / economic / fastest routes may or may not differ, I have posted about in my previous post.
Strange navigation results usually have either bad OSM mapping either bad routing reasons. In my experience, the former is more frequent. Before blaming the routing engine and/or the navigation software, the first step should always be checking the master OSM data <http://openstreetmap.org/> and eventual data propagation delay. ( OSM can be already fixed - check the timestamps when, while routing data can be still wrong ) The bad navigation due mapping can be of 3 kinds. a) heavy mapping errors - missing data ( like missing roads/road segments, or crossing roads missing the shared node ) or mapped nonsenses due the mapper mistakes b) incorrect misleading mapping, fooling the routers doing their best. Often related to delayed mapping of changes. c) correct mapping and routing, but a user had wrong idea about the current situation. Often related to delayed user change recognition. -- Poutnik ( The Wanderer ) My Brouter profiles https://github.com/poutnikl/Brouter-profiles/wiki -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
