Travel time discrepancies
-
@Steve-Jarrell I never really looked at the route times, only the ETAs while navigating.
But now I did for one of my routes which goes mostly over a highway
Route time for MRA-OSM is noticeably longer than MRA-Here! Kurviger is the slowest.
220km, paths are very similar in all 3.MRA Here: 2h 52m
MRA OSM: 3h 13m
Kurviger: 4h 4m@Herman-Veldhuizen Thanks Herman.. That's weird..... there doesn't seem to be any consistency. My "gold standard" is normally Waze or Google maps as I find them to be extremely accurate, but since you can't upload a specific route into either they're of no help. Although you can import a track into Google MyMaps it really doesn't create a Google route from it, so it uses the tracks time information so that's no help.
I could be wrong so if I am someone please let me know. I'm here to learn.... that's half the fun!
If I have time I'll go back and compare 5 or 6 of our group's tracks/routes and compare them in MRA using the HERE, OSM and TomTom maps.
Thanks for your input. I really appreciate it!
-
@Herman-Veldhuizen Thanks for your respons Herman. With the TomTom and OSM maps I'm finding the calculated route times to be very accurate. With the HERE maps I find it to be inconsistent.
The only thing that I can surmise is that the route calculations and the calculations that create a route from a track are built into the maps themselves and MRA has very little, if any, control over them otherwise the HERE map would not be inferior to the other two in this regard.
I also switched from Kurviger as I find the user interface to be very, very unintuitive whereas I find MRA to be extremely easy to use. I also find MRA's tech support to be excellent, and the user forum is extremely helpful as well.
Unless someone can show me why there are important advantages to using the HERE maps as the default I'm going to make the OSM maps my default, and hopefully the MRA developers will fix the bug that causes the following dialog to appear when I switch to the OSM map or import a track into it even though I have my driving mode set to "Driving" which, according to MRA, should avoid this message:
@Steve-Jarrell said in Travel time discrepancies:
Unless someone can show me why there are important advantages to using the HERE maps as the default I'm going to make the OSM maps my default
The biggest advantage to use HERE maps for planning is the least chance for the planner map to be different than the navigation map. The advice is to plan your route on map that is ost equal to the one you navigate with. For MRA Navigation that is HERE, as is for Garmin devices. There are many differences in maps between OSM and HERE, especially in rural mountenesque areas.
@Steve-Jarrell said in Travel time discrepancies:
the bug that causes the following dialog to appear when I switch to the OSM map or import a track into it even though I have my driving mode set to "Driving"
I am not aware of a driving mode called "driving". I only get this message when I switch from HERE or TomTom to OSM while I have "Motorbike" selected as driving mode.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Steve-Jarrell said in Travel time discrepancies:
It looks like MRA is using the Garmin extensions to do their track and route calculations whereas Kurviger doesn't.
To avoid confusion: Using GPX extensions (like "Garmin extensions") is a way to store additional information in a gpx file that is not part of the core gpx data model. The most popular example is the differentiation between VIA and shaping route points using the garmin:trp extension.
For time information, however, there is no need to use an extension as this is part of the core gpx data model.
And it's about storing information and has nothing to do with time calculation.
@Martin-Wilcke Thank you for the explanation!
-
@Steve-Jarrell said in Travel time discrepancies:
I definitely see the disadvantages of using the HERE map over using the OSM map in MRA. Can anyone tell me the actual advantages?
There is one I'm aware of: consideration of road closures.
@Martin-Wilcke Thank you.
That's one that I prefer not to use anyway as I've found (in our area at least) that often it's not accurate, or I'm creating a route that I'll be riding when they don't exist so I almost always disable it anyway.
-
@Steve-Jarrell said in Travel time discrepancies:
Unless someone can show me why there are important advantages to using the HERE maps as the default I'm going to make the OSM maps my default
The biggest advantage to use HERE maps for planning is the least chance for the planner map to be different than the navigation map. The advice is to plan your route on map that is ost equal to the one you navigate with. For MRA Navigation that is HERE, as is for Garmin devices. There are many differences in maps between OSM and HERE, especially in rural mountenesque areas.
@Steve-Jarrell said in Travel time discrepancies:
the bug that causes the following dialog to appear when I switch to the OSM map or import a track into it even though I have my driving mode set to "Driving"
I am not aware of a driving mode called "driving". I only get this message when I switch from HERE or TomTom to OSM while I have "Motorbike" selected as driving mode.
@Con-Hennekens You are right. My mistake. It's called "Car" so I'm not set on Motorcycle, but I still get the message every time I switch to OSM. What driving mode are you using in your profile?
Thanks!
-
@Steve-Jarrell said in Travel time discrepancies:
Unless someone can show me why there are important advantages to using the HERE maps as the default I'm going to make the OSM maps my default
The biggest advantage to use HERE maps for planning is the least chance for the planner map to be different than the navigation map. The advice is to plan your route on map that is ost equal to the one you navigate with. For MRA Navigation that is HERE, as is for Garmin devices. There are many differences in maps between OSM and HERE, especially in rural mountenesque areas.
@Steve-Jarrell said in Travel time discrepancies:
the bug that causes the following dialog to appear when I switch to the OSM map or import a track into it even though I have my driving mode set to "Driving"
I am not aware of a driving mode called "driving". I only get this message when I switch from HERE or TomTom to OSM while I have "Motorbike" selected as driving mode.
@Con-Hennekens I overlooked the first part of your post. Thanks for the detailed explanation!
Steve
-
@Con-Hennekens You are right. My mistake. It's called "Car" so I'm not set on Motorcycle, but I still get the message every time I switch to OSM. What driving mode are you using in your profile?
Thanks!
@Steve-Jarrell
When i open de route you linked in a previous post the profile is set to motorcycle… -
@Steve-Jarrell
When i open de route you linked in a previous post the profile is set to motorcycle…@BertM 
image url) -
@Steve-Jarrell
When i open de route you linked in a previous post the profile is set to motorcycle…@BertM Yes, I've changed it back and forth several time experimenting trying to figure out what's going on.
If you look at my previous post you'll see where I took a screenshot of my profile setting set to "Car' at the exact same time that the error message is appearing.
I even thought that perhaps MRA considered the routing mode when the route was created from the track and then ignored it from then on, however I created the route from scratch by importing a .gpx file with the mode set to Car, and as soon as I did I got the error message.
Thanks for the response!
-
It's specifically the road after waypoint 26 that gives way longer estimates than other map sources. It's based on the realistic travel time HERE tracks for that section and my guess is that their data on that is wrong.
Either incorrect speed limit or some anomalies in their realistic travel time estimation
@Corjan-Meijerink After riding the route last Wednesday it is possible the HERE map is using information about the roads when they were really torn up after Hurricane Helene at the end of last year as some of them were still in pretty bad shape when we rode them and you could see where one lane the road had been washed completely out.
If the HERE map is using data from late last year it is likely that at that time their estimation of the time that it would take to ride this route would be accurate. Perhaps a future map update will resolve the issue. That's a very plausible explanation.
Thanks! I don't like mysteries, and I'll consider this one solved!
