Driving ETA is highly inaccurate #10094

New issue

Open

opened 2025-01-18 22:32:56 +00:00 by PinguDEVoriginal · 4 comments

PinguDEVoriginal commented

2025-01-18 22:32:56 +00:00

(Migrated from github.com)

⚠ Have you searched for similar, already existing issues?

Describe the issue
Currently, if you create a route, OrganicMaps is really optimistic with the estimated time of arrival (ETA). While I like the routes built, the needed time is basically always false, which is bad.
I don't mean that traffic isnt calculated, because even without traffic (just traffic lights and stuff), it's not really realistic.

Steps to reproduce
Create a route, drive it, see the difference.

Expected behaviour
A somewhat correct time, well, obviously when there is low traffic.

System information:

Operating system and its version: CalyxOS with Android 15
Organic Maps version: 2024.11.27-12-Web
Device Model: Pixel 6a

Additional context
I suspect that:

The speed is thought of being always the maximum (which isnt the case)
Traffic lights (or zebra crosswalks) aren't really used

⚠ Have you searched for similar, already existing issues? **Describe the issue** Currently, if you create a route, OrganicMaps is really optimistic with the estimated time of arrival (ETA). While I like the routes built, the needed time is basically always false, which is bad. I don't mean that traffic isnt calculated, because even without traffic (just traffic lights and stuff), it's not really realistic. **Steps to reproduce** Create a route, drive it, see the difference. **Expected behaviour** A somewhat correct time, well, obviously when there is low traffic. **System information:** - Operating system and its version: CalyxOS with Android 15 - Organic Maps version: 2024.11.27-12-Web - Device Model: Pixel 6a **Additional context** I suspect that: 1. The speed is thought of being always the maximum (which isnt the case) 2. Traffic lights (or zebra crosswalks) aren't really used

Rows
Columns