Poor routing through certain interchanges #10413

New issue

Open

opened 2025-03-05 04:20:17 +00:00 by AtmosphericIgnition · 0 comments

AtmosphericIgnition commented

2025-03-05 04:20:17 +00:00

(Migrated from github.com)

⚠ Have you searched for similar, already existing issues?

Describe the issue

Instead of routing through this cloverleaf interchange in a logical way, OM suggests the driver gets off in the opposite direction, then does a left turn, a U-turn, and a right turn. I thought this might be an issue with the map data, but all of OSMs routing algorithms have the driver take the logical way. Disabling my routing options still has me take the wrong way.

(I don't really understand routing algorithms, but I think this could be a symptom of OM seemingly not "penalizing" left, and u-turns nearly enough. The navigation often has me snaking through minor residential roads, instead of following major roads.)

Steps to reproduce

Make a trip using the US 23/ Washtenaw Ave intersection in Ann Arbor, MI (as an example, from 42.248670, -83.683481 to 42.255642, -83.689341)
See the navigation ask the driver to take the wrong exit direction, then ask to take several turns to get back on track.

Expected behaviour
The red path marked in the screenshot should be followed.

System information:

Operating system and its version: Android 15 - GrapheneOS
Organic Maps version: 2025.02.17-3-Google
Device Model: Pixel 8 Pro

Additional context
This is not a new behavior, I have see this since I started using OM. This cloverleaf interchange is not the only interchange I have seen affected by this, but it's the only one I remember the location of.

Possibly related issues:
#9123
My comment under #8637
#10101

⚠ Have you searched for similar, already existing issues? **Describe the issue** Instead of routing through this cloverleaf [interchange](https://www.openstreetmap.org/#map=17/42.254554/-83.683854) in a logical way, OM suggests the driver gets off in the opposite direction, then does a left turn, a U-turn, and a right turn. I thought this might be an [issue](https://www.openstreetmap.org/changeset/161878114) with the map data, but all of OSMs routing algorithms have the driver take the logical way. Disabling my routing options still has me take the wrong way. ![Image](https://github.com/user-attachments/assets/79d44951-45f4-42cf-8ec1-68c48b5f05a7) (I don't really understand routing algorithms, but I think this could be a symptom of OM seemingly not "penalizing" left, and u-turns nearly enough. The navigation often has me snaking through minor residential roads, instead of following major roads.) **Steps to reproduce** 1. Make a trip using the US 23/ Washtenaw Ave intersection in Ann Arbor, MI (as an example, from 42.248670, -83.683481 to 42.255642, -83.689341) 2. See the navigation ask the driver to take the wrong exit direction, then ask to take several turns to get back on track. **Expected behaviour** The red path marked in the screenshot should be followed. **System information:** - Operating system and its version: Android 15 - GrapheneOS - Organic Maps version: 2025.02.17-3-Google - Device Model: Pixel 8 Pro **Additional context** This is not a new behavior, I have see this since I started using OM. This cloverleaf interchange is not the only interchange I have seen affected by this, but it's the only one I remember the location of. Possibly related issues: #9123 My [comment](https://git.omaps.dev/organicmaps/organicmaps/issues/8637#issuecomment-2691039391) under #8637 #10101

👍 1 👀 1

This repo is archived. You cannot comment on issues.