You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When one drives on a straight road, OsmAnd does not announce the change of streets. Example: 5.83111 / - 55.18509.
When the direction crosses the Kernkampweg, the street name changes from Gravenberchstraat to Johannes Mungrastraat. Although it is shown in the display, OsmAnd does not announce it.
The text was updated successfully, but these errors were encountered:
alyonapinchuk
changed the title
Feature request: announce change of street names
Feature request: announce the change of street names
Apr 17, 2019
vshcherb
added
the
Nice to Have
Should be fixed but there is no priority or no possibility to fix it within current horizon planning
label
May 10, 2019
alrega
pushed a commit
to alrega/Osmand
that referenced
this issue
Apr 12, 2020
One road may be result of several streets changing one into another. In that case OsmAnd didn't indicate that street name would change, because thare was no turn left/right in the route.
Commit adds the new feature. When two segments of stright part route have different street names, a new 'stright' direction with the new name will be inserted into the list of directions.
This is not applied to roads that have international/national refs, like 'E 101'
I have looked into this and am afraid this may be rather diisruptive, because depending on your area street names can change a lot. Often by having little segments at cross roads with different or no name, and it is more confusing than helpful if users heard all this chatter? Particularly since no action is expected but going straight?
When one drives on a straight road, OsmAnd does not announce the change of streets. Example: 5.83111 / - 55.18509.
When the direction crosses the Kernkampweg, the street name changes from Gravenberchstraat to Johannes Mungrastraat. Although it is shown in the display, OsmAnd does not announce it.
The text was updated successfully, but these errors were encountered: