Expected trunk road is not chosen for Right Turn #5997

New issue

Open

opened 2023-09-10 15:13:39 +00:00 by alext951 · 0 comments

alext951 commented

2023-09-10 15:13:39 +00:00

(Migrated from github.com)

Describe the issue
Pls see the screenshot showing that the right turn access road is not selected by the routing algorithm.
OSM id of the trunk road is: https://www.openstreetmap.org/way/11726960

What's more, the right turn suggested is actually not allowed, because both lanes of the main road are only going left. On OSM this is indicated by turn:lanes left|left (see https://www.openstreetmap.org/way/61731320).

Asking this on the Telegram chat, it appears that OM doesn't look at the turn:lanes tag at the moment, instead honoring the restriction relation.

Question here is two fold:

Should OM honor turn:lanes? In this case turn:lanes represents accurate road markings, and there are no road signs to warrant restriction relation. Or, alternatively, should restriction relation be added to OSM to reflect road markings (even though there is no road sign).
Organic Maps should route through the trunk road regardless of restrictions because that's just the natural route a driver would take. I am not sure though what is causing OM mis-route here. Implementing turn penalties has been mentioned on Telegram as a possible solution to this

Expected behavior
See point 2 above.
Example of correct routing from openrouteservice:
https://classic-maps.openrouteservice.org/directions?n1=40.950178&n2=-74.274855&n3=18&a=40.950271,-74.273146,40.951017,-74.277545&b=0&c=0&k1=en-US&k2=km

Screenshots

System information:

Operating system and its version: [Android 12]
Organic Maps version: 2023-08-18-8
Device Model: Pixel 5

**Describe the issue** Pls see the screenshot showing that the right turn access road is not selected by the routing algorithm. OSM id of the trunk road is: https://www.openstreetmap.org/way/11726960 What's more, the right turn suggested is actually not allowed, because both lanes of the main road are only going left. On OSM this is indicated by `turn:lanes left|left` (see https://www.openstreetmap.org/way/61731320). Asking this on the Telegram chat, it appears that OM doesn't look at the `turn:lanes` tag at the moment, instead honoring the restriction relation. Question here is two fold: 1. Should OM honor `turn:lanes`? In this case turn:lanes represents accurate road markings, and there are no road signs to warrant restriction relation. Or, alternatively, should restriction relation be added to OSM to reflect road markings (even though there is no road sign). 2. Organic Maps should route through the trunk road regardless of restrictions because that's just the natural route a driver would take. I am not sure though what is causing OM mis-route here. Implementing turn penalties has been mentioned on Telegram as a possible solution to this **Expected behavior** See point 2 above. Example of correct routing from `openrouteservice`: https://classic-maps.openrouteservice.org/directions?n1=40.950178&n2=-74.274855&n3=18&a=40.950271,-74.273146,40.951017,-74.277545&b=0&c=0&k1=en-US&k2=km ![image](https://github.com/organicmaps/organicmaps/assets/43077263/94ee8687-e04e-4b1c-a1d0-0f0a91fca7ce) **Screenshots** ![image](https://github.com/organicmaps/organicmaps/assets/43077263/a719a800-04d0-42ce-8408-f0a57743b9a3) **System information:** - Operating system and its version: [Android 12] - Organic Maps version: 2023-08-18-8 - Device Model: Pixel 5

This repo is archived. You cannot comment on issues.