Estimated Arrival Time based on recent average speed #6929

Open
opened 2023-12-22 15:27:43 +00:00 by parduspanteri · 14 comments
parduspanteri commented 2023-12-22 15:27:43 +00:00 (Migrated from github.com)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. For example:

The estimated time of arrival fails to calculate the traffic situation between the start and destination points.

Describe the ideal solution
A clear and concise description of what you want to see in Organic Maps.

A much more realistic estimate can be made if the average speed during the time traveled is taken as a basis and the remaining km can be traveled with that average speed.

Start
Arrival

Estimated: 20 Minutes
Real: 56 Minutes

**Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. For example: The estimated time of arrival fails to calculate the traffic situation between the start and destination points. **Describe the ideal solution** A clear and concise description of what you want to see in Organic Maps. A much more realistic estimate can be made if the average speed during the time traveled is taken as a basis and the remaining km can be traveled with that average speed. ![Start](/uploads/f6d143d6c9c676a2b218fc7a874964e2/aa91b184-219a-4a2c-ad93-2b679c47f3ef) ![Arrival](/uploads/510c9fa22c085bcb999e835331543cf7/26f4d9c7-de3f-4571-be77-09f2195e80f2) Estimated: 20 Minutes Real: 56 Minutes
jaybg commented 2023-12-26 12:26:47 +00:00 (Migrated from github.com)

It is a good idea to take average speeds of different routes during different times and use those to show ETAs. Of course these data needs to come from users.

Since unlike other popular maps there's no continuous tracking of devices in case of organic maps, something like this would be good to show more accurate ETAs.

It is a good idea to take average speeds of different routes during different times and use those to show ETAs. Of course these data needs to come from users. Since unlike other popular maps there's no continuous tracking of devices in case of organic maps, something like this would be good to show more accurate ETAs.
parduspanteri commented 2023-12-27 09:05:53 +00:00 (Migrated from github.com)

It is a good idea to take average speeds of different routes during different times and use those to show ETAs. Of course these data needs to come from users.

Since unlike other popular maps there's no continuous tracking of devices in case of organic maps, something like this would be good to show more accurate ETAs.

The app doesn't need to get data from others. Because then it will be an online map. It can use our average speed since we started our route. At first it will still not give the exact value, but it will get closer and closer to a more realistic estimated time. It will be better than the current system.

@biodranik

> It is a good idea to take average speeds of different routes during different times and use those to show ETAs. Of course these data needs to come from users. > > Since unlike other popular maps there's no continuous tracking of devices in case of organic maps, something like this would be good to show more accurate ETAs. The app doesn't need to get data from others. Because then it will be an online map. It can use our average speed since we started our route. At first it will still not give the exact value, but it will get closer and closer to a more realistic estimated time. It will be better than the current system. ` @biodranik`
biodranik commented 2023-12-27 23:08:27 +00:00 (Migrated from github.com)

Implementing an automated, self-learning, offline ETA correction is an interesting idea. It won't replace alternate routes, and won't fix ETAs for first-time users, but may be useful for those who uses OM frequently. Did anyone implement something similar already?

Implementing an automated, self-learning, offline ETA correction is an interesting idea. It won't replace alternate routes, and won't fix ETAs for first-time users, but may be useful for those who uses OM frequently. Did anyone implement something similar already?
parduspanteri commented 2023-12-28 11:45:40 +00:00 (Migrated from github.com)

Implementing an automated, self-learning, offline ETA correction is an interesting idea. It won't replace alternate routes, and won't fix ETAs for first-time users, but may be useful for those who uses OM frequently. Did anyone implement something similar already?

I have not heard of a similar application. This will make a difference in offline maps and I believe it will attract online map users as well. To be able to write a mathematical algorithm based only on the average speed in certain minutes. I wish I had the software knowledge to write this, but I can compile the mathematical formula and results.

> Implementing an automated, self-learning, offline ETA correction is an interesting idea. It won't replace alternate routes, and won't fix ETAs for first-time users, but may be useful for those who uses OM frequently. Did anyone implement something similar already? I have not heard of a similar application. This will make a difference in offline maps and I believe it will attract online map users as well. To be able to write a mathematical algorithm based only on the average speed in certain minutes. I wish I had the software knowledge to write this, but I can compile the mathematical formula and results.
biodranik commented 2023-12-28 13:46:33 +00:00 (Migrated from github.com)

Math with comments/descriptions and examples on how to test it would be enough

Math with comments/descriptions and examples on how to test it would be enough
parduspanteri commented 2023-12-29 13:03:42 +00:00 (Migrated from github.com)

Math with comments/descriptions and examples on how to test it would be enough

Ok. I'll work on it and inform you. But I need some time for that.

> Math with comments/descriptions and examples on how to test it would be enough Ok. I'll work on it and inform you. But I need some time for that.
auge8472 commented 2024-01-01 19:17:43 +00:00 (Migrated from github.com)

Currently it looks, as if the travel time gets computed with the distance and the allowed speeds only. That's not helpful in cities with more than no traffic. As a first approach, it would be good if there was a penalty for every traffic light that had to be passed.

Currently *it looks*, as if the travel time gets computed with the distance and the allowed speeds only. That's not helpful in cities with more than *no* traffic. As a first approach, it would be good if there was a penalty for every traffic light that had to be passed.
jaybg commented 2024-01-06 08:23:19 +00:00 (Migrated from github.com)

All of these approaches combined together would definitely improve ETA calculations in an offline manner.

All of these approaches combined together would definitely improve ETA calculations in an offline manner.
parduspanteri commented 2024-10-23 09:18:41 +00:00 (Migrated from github.com)

I'm sorry for the delay, it's been a long time since I could attend to this. I tried to roughly explain the offline ETA based on average speed with two scenarios. In both scenarios (one with traffic congestion and one without), it appears to yield better results. As you can appreciate, since this system operates offline, it is not possible to calculate with complete accuracy. We only hope that it provides results closer than the current calculations. These results will align more closely with the actual time as the drive progresses, rather than at the beginning of the journey. It would be even better if the ETA could be calculated separately based on highway and city driving distances within the route. As I mentioned, the studies are rough and require further consideration.
Organic Maps ETA.xlsx

I'm sorry for the delay, it's been a long time since I could attend to this. I tried to roughly explain the offline ETA based on average speed with two scenarios. In both scenarios (one with traffic congestion and one without), it appears to yield better results. As you can appreciate, since this system operates offline, it is not possible to calculate with complete accuracy. We only hope that it provides results closer than the current calculations. These results will align more closely with the actual time as the drive progresses, rather than at the beginning of the journey. It would be even better if the ETA could be calculated separately based on highway and city driving distances within the route. As I mentioned, the studies are rough and require further consideration. [Organic Maps ETA.xlsx](https://github.com/user-attachments/files/17488264/Organic.Maps.ETA.xlsx)
Member

Thank you very much. I've been also trying to do these studies and they're hard to document. You've invested into a great document I wouldn't want to loose in time. We gotta figure out how to collaborately make more of these studies and document what are the factors for time, like traffic lights, turnings, bumbers, and find a way to put them all together to calculate.

Thank you very much. I've been also trying to do these studies and they're hard to document. You've invested into a great document I wouldn't want to loose in time. We gotta figure out how to collaborately make more of these studies and document what are the factors for time, like traffic lights, turnings, bumbers, and find a way to put them all together to calculate.
RobfromVI commented 2025-01-10 18:56:11 +00:00 (Migrated from github.com)

For city dwellers, travelling their entire route on streets, there may be some consistency in relative rate of speed for a trip depending on current traffic.

For many of us, I think we travel on very different routes for different parts of our trips. So, if I were to be stuck in traffic for the first 5kms, it would push back my arrival time whereas the remainder of my trip might be on unimpeded freeways or motorways.

So, adjusting arrival time based on actual speed achieved vs allowable speed on the completed portion of the route may provide very incorrect results.

On the other hand, if I consistently drive at say 85% of the allowable speed on certain types of routes, my anticipated ETA could be adjusted accordingly. Even that though, I sometimes drive my car, and sometime my RV, and my speed is different for each vehicle. This would require a consideration for vehicle type.

I think it gets too complicated.....

For city dwellers, travelling their entire route on streets, there may be some consistency in relative rate of speed for a trip depending on current traffic. For many of us, I think we travel on very different routes for different parts of our trips. So, if I were to be stuck in traffic for the first 5kms, it would push back my arrival time whereas the remainder of my trip might be on unimpeded freeways or motorways. So, adjusting arrival time based on actual speed achieved vs allowable speed on the completed portion of the route may provide very incorrect results. On the other hand, if I consistently drive at say 85% of the allowable speed on certain types of routes, my anticipated ETA could be adjusted accordingly. Even that though, I sometimes drive my car, and sometime my RV, and my speed is different for each vehicle. This would require a consideration for vehicle type. I think it gets too complicated.....
Member

mentioned in issue #10062

mentioned in issue #10062
Member

changed title from Estimated Arrival Time to Estimated Arrival Time{+ based on recent average speed+}

changed title from **Estimated Arrival Time** to **Estimated Arrival Time{+ based on recent average speed+}**
Member

mentioned in issue #10094

mentioned in issue #10094
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: organicmaps/organicmaps#6929
No description provided.