Time/speed calculations

Klaus r

When planning I discovered now that the travel time calculated between 2 route points are shorter then they were in previous versions.
That ends up in too high averages for speed.
E.g. >60 to 80 km/h - for profile Car with the option Avoid Highways!

Error in the one of the last updates?

Klaus r

No reply, no reaction from MRA?
I have made some test with kurviger. The times it calculates are much better.
There is something wrong in the routeplaner (web).Be it in the calculation or in the map data.
Which speed values do you use for the different type of roads?

Over all, I like the routeplanner very much but ... I am rather disappointed now. Instead of implementing more features you should take care to get the basics more usable.

In addition I propose to implement a simple speed correction factor to be applied to all type of roads.
So one can adjust the time calculations to its own needs.
Fast, slow, group rides etc.

Marinus van Deudekom

@Klaus-r As far as I know there haven't been any changes in the average speed tables. I do know that MRA will always keep on the very safe side of speedlimits. So what you experience must be something else. Maybe you can share such a route with us and make shure it's set to public so we can have a glance

Klaus r

@Marinus-van-Deudekom
Ok, will do it on Friday.
But I do not believe that it will depend on a route. I experienced it with several routes.

TomOnTour

Hello @Klaus-r,

as I was using MRA in parallell with my Garmin XT2 and experienced that the difference between MRA and the Garmin device even on routes with more than 300km is in a range of 5-10 Minutes. This difference is coming von minor differences within the final routes.
My understanding is, that MRA and Garmin are using the same routing algorithm. Seeing this minor differences between MRA and Garmin this seams to be correct.
I know that Garmin had something like the individual speed definitions for specific road types, but this is no longer available.

Personally I don‘t see really relevant differences between the planned times and my reality on my routes. I don‘t think, that a difference of a couple of minutes in a tour is no problem for me.

Greetings
Thomas

Hubert Thoring

@Klaus-r : In the application with the motorcycle, I am often surprised how well the time fits when we have arrived at the stopping point.

I have no objections, it's an orientation.
VG

Con Hennekens

@Klaus-r, those duration calculations are inherent to the the HERE algorithms. Traffic can have an impact as well as closed roads that reopen or vice versa. You could try if these differences still occur if you disable seasonal closures in the toolkit. That way traffic and closed roads are not considered during planning.

@Klaus-r said in Time/speed calculations:

Instead of implementing more features you should take care to get the basics more usable.

The basics are really great as they are. I think it is a bit short-sighted to claim this.

Klaus r

Strange.
When riding with a group we were always too late. More than just some minutes.
Why???

If there are really no longer individual speed definitions for specific road types available that would explain bigger differences.

Klaus r

As asked for a route example. Simple A-B, no shaping or via points, no breaks.
Options set:
Avoid highways
Avoid unpaved roads
Disable seasonal closures
Fastest road
Map = HERE

Results
Motorcycle 236,02km, 3h 10m
Average speed = 236,02km / 3,166h = 74,53 km/h

Car 233,94km, 3h 26m
Average speed = 233,94km / 3,433h = 68,14 km/h

Motorhome same as car! (lenght 650cm, weight 3490kg)

https://www.myrouteapp.com/en/social/route/9783965?mode=share

So, why are the average speeds so high?

Marinus van Deudekom

@Klaus-r I still don”t know wat these rifferences apear in the web planner. I”Ve looked at the route in the next app and heen I change the transport mode the distance AND thé total time stay the same
Marybelle @Corjan-Meijerink can explain wat. And oerhaps hé can and will let us know What aversge sledes are beding used in Beth thé planning and next version.