I can see here two or three possible reasons: 1. problem with the phone: it would mean OsmAnd gets the wrong position (it "sees" itself further back in the road than it is, the GPS info is delayed) 2. problem with the phone: the position correct but OsmAnd for some reason react too late (RAM?) 3. problem with the route itself.
I see as probable either 1 or 2, what phone are you using? You might be able to see it if you zone at your current position - it would show you at the place the phone sees you. For 3: How are you navigating? Along the downloaded route, or do you leave OsmAnd navigate you? If you load the route and inspect it, does it correspond with the roads you see on the screen? Majka On Wednesday, 26 August 2020 16:51:04 UTC+2, Eric Benton wrote: > > Anyone have any ideas? > > On Friday, August 21, 2020 at 11:05:50 AM UTC-4 Eric Benton wrote: > >> >> Hey, all. Sorry if this has been posted before, but I searched and >> couldn't find anything. Maybe due to wording, but hey, here we are. I just >> started using the app for cycling routes and I'm relatively happy with how >> detailed the offline directions are, but they are always 200-400ft behind >> where I actually am. I'll get a "Turn in 200ft" prompt after I've already >> passed the turn pretty often. Or, more often, the app will tell me to turn >> as I'm already 75% through the turn. Any idea what setting I can mess with >> to fix this? Maybe it has to do with the gpx files I'm downloading from >> Strava? Thanks in advance. >> > -- 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/278e675a-4dd7-4d02-a4e1-d502e0c4a7bfo%40googlegroups.com.
