Navigation accuracy of Locus

[TLA]

Hi,

is it possible to change some options in order to improve navigation accuracy? Currently Locus navigates only to nearest asphalt roads which might be tens of kilometers and crossings away from the real destination. It would be especially useful when motorcycling through gravel roads here in Finland. Mapquest's website does the navigation to small roads, which you can see from this example: //http://mapq.st/q4C8rl It does not matter if I choose Compute source as MapQuest or CloudMade.

Br,

TLA

[Khaytsus]

I'd have to guess that the navigations services don't know about those roads.  You could always manually create or record such routes and follow them, Locus will guide you on any route, just automatically can create them using the web services for known routes.

[TLA]

Maybe that was a bad example, but the same happens if choosing an street address that the Locus and the MapQuest website recognises. Website is able to navigate to smaller roads. Is there a difference between this website based navigation and Locus using Mapquest?

[Menion]

hmm TLA you discovered very interesting think ... and weird.

when I insert coordinates for your path into link that I use to compute route on Mapquest server ... this

http://open.mapquestapi.com/guidance/v0 ... 5362046764

you can see at bottom of result <message>200 Unable to calculate route.</message> - this is really weird because coordinates are exactly same as on web

[TLA]

Weird indeed, maybe the website is still using the system differently...

I tried to find other differences by randomly choosing addresses from Finland.
Here is another example where MapQuest web site and Locus based navigation does not match:
//http://mapq.st/nJBr0T

Website is correctly pointing to right addresses and roads, but Locus (using MapQuest navigation) misses by over 1km at both ends, somehow it does not want to go to some of those small roads seen on map. Also it tries to navigate through different route.