The built route is deeply wrong

[Gravity2106]

⚠ Have you searched for similar, already existing issues? Yes

Describe the issue
Please write a clear and concise description of the issue here.
If I tried to go from A to B, the path recommended is very bad in comparison with the best one possible and the stimated time is not reliable at all (this last one maybe due to traffic lights?).
OSM does it well.

Steps to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behaviour
A clear and concise description of what you expected to happen.
The app recommends the best route available as OSM does.

Screenshots
If applicable, add screenshots or screen recordings to help explain your problem.

System information:

• Android 14
• versión 2024.03.31-8-Web
  app.organicmaps.web
  versionCode 24033108
  targetSdk 34
  minSdk 21
  Installed: 4 abr 2024; 16:49
• Pixel 7

Additional context
Please add any other context or comments here that may be useful.

[Jean-BaptisteC]

Without start and end point of your routing, you can't doing nothing :)

[Gravity2106]

Without start and end point of your routing, you can't doing nothing :)

I cannot share that info without compromising my personal data.

[Jean-BaptisteC]

Is it possible to give approximative coordinates or just part of wrong routing?

[Gravity2106]

Is it possible to give approximative coordinates or just part of wrong routing?

It happens quite often. It is not only one area in particular. Sometimes it is not very wrong, it's just okey.
Sometimes it is horrible.
Can I contact you in private?

[Jean-BaptisteC]

Send an email to hello@organicmaps.app

[Gravity2106]

I have try again and for the exact same path, now the route is different.
In OSM the distance is 3.10 km and the time 10 minutes, but now in OM it is 3.2 and 5 minutes.
It is the same route in both.

For other random points on the map:
OSM: 4,17 km 9 min
OM: 5 km 11 min

[biodranik]

Results can be different (esp. estimated time), because different engines calculate it differently. Organic Maps doesn't take into account turns and traffic lights yet, for example.

Without knowing the coordinates of a route, we can't improve it. You can share them privately with screenshots at hello or support [at] organicmaps dot app

[matheusgomesms]

Yeah, ETA right now is really off, especially in urban areas. OM suggests very shorter ETAs compared to real life. Regarding routes, I usually don't have problems, considering OM don't have access to traffic data. It suggest quite good routes, trying to use the high priority roads etc.

[Gravity2106]

It could explain part of it... As recently the two main routes have a similar distance but a great difference in time due to traffic lights... That could also explain other "strange" suggestions that were obviously wrong (like going through a city instead of taking the highway)

[biodranik]

Did you read #1845 ?

@Tmpod it would be great if you can properly penalize traffic lights and turns in the existing implementation ;-)

CC @vng

[Gravity2106]

It could be nice having the possibility to share some routes to collect data about speed or traffic lights. Maybe it could be chosen after or before the journey?

[Explosion-Scratch]

Can you give an example route for somewhere not nearby you @Gravity2106

[Gravity2106]

Can you give an example route for somewhere not nearby you @Gravity2106

Maybe this could be useful: https://superroute.evergreen-labs.com/

[Gravity2106]

It could be nice having the possibility to share some routes to collect data about speed or traffic lights. Maybe it could be chosen after or before the journey?

I found a map with traffic lights https://github.com/sb12/OSMStreetLight?tab=readme-ov-file
Maybe this could be use to calculate routes, for example supposing that per traffic light it should add 30 seconds to the total route. Some times some of them they will be open and you don't have to wait, but if you have to stop you will be there around 1-2 minutes.

Could be that a good approach?