3 ms·

> Riding back roads, I'd regularly get a navigation prompt telling me to continue straight on the road I'm already on, with no other options. I had better navig

by kqr 4y ago

> Riding back roads, I'd regularly get a navigation prompt telling me to continue straight on the road I'm already on, with no other options. I had better navigation instructions on the software I developed for PocketPC back in the early 2000s. I'm not entirely sure what you mean by this, but it sounds like a bug in the underlying OpenStreetMap data, where one road has accidentally been modeled as two roads with an intersection between them. That you can fairly easily fix on your own. The rest of your feedback I agree with (though I may disagree with your priorities, but that's fine -- we have different priorities.)

wtallis 4y ago
It's also possible that OSMAnd was configured to repeat the instruction every 15 minutes or so. I don't recall if that's on by default, but I always turn it on so I get occasional reminders of how far it is to my next turn.
- snozolli 4y ago
  It happens randomly and sometimes repeatedly within a short period of time. I'm sure it's due to errors in the map data, but it still should be scrubbed from the prompt queue by OsmAnd.
- vel0city 4y ago
  The worst part of this kind of navigation bug (which I've experienced on other platforms as well) is that it obscures the next actual turn. I'll see there's some navigation event in 20 miles, but when I actually get there its just a "stay on this road for another 50 miles", which at that point its once again "stay on this road for another x miles..." I don't care about all of these stay on the road kind of events, I just want to know when my next exit might be even if that's in 300 miles.
snozolli 4y ago
where one road has accidentally been modeled as two roads with an intersection between them. That shouldn't matter. They should be processing whatever data they're getting from the mapping/navigation engine and removing things like that. Any 'intersection' with no actual intersection and no change in road name should be ignored. That's what I meant about the software I wrote in the early 2000s doing a better job at navigation prompts.

by kqr 4y ago

wtallis 4y ago

It's also possible that OSMAnd was configured to repeat the instruction every 15 minutes or so. I don't recall if that's on by default, but I always turn it on so I get occasional reminders of how far it is to my next turn.

snozolli 4y ago
It happens randomly and sometimes repeatedly within a short period of time. I'm sure it's due to errors in the map data, but it still should be scrubbed from the prompt queue by OsmAnd.
vel0city 4y ago
The worst part of this kind of navigation bug (which I've experienced on other platforms as well) is that it obscures the next actual turn. I'll see there's some navigation event in 20 miles, but when I actually get there its just a "stay on this road for another 50 miles", which at that point its once again "stay on this road for another x miles..." I don't care about all of these stay on the road kind of events, I just want to know when my next exit might be even if that's in 300 miles.

snozolli 4y ago

where one road has accidentally been modeled as two roads with an intersection between them. That shouldn't matter. They should be processing whatever data they're getting from the mapping/navigation engine and removing things like that. Any 'intersection' with no actual intersection and no change in road name should be ignored. That's what I meant about the software I wrote in the early 2000s doing a better job at navigation prompts.