MRA Community Forum

Thank you

Hey. Could we briefly summarize this again? I suspect I just had a similar experience today. I’m using BMW ConnectedRide, and I created a GPX 1.1 route in MRA (42 way points,Tom Tom), making sure to add “via points” at very regular intervals. It ends up as a track (which is recommended) in my Connected Ride (don`t fully understand why it end up being a track in the NAV). Unfortunately, during the last third of my track today, I was completely rerouted differently. The destination was correct, but the via points seemed to be ignored. Just verified it. Based on what you described here, what is the likely cause, and what would be the best way to prevent this from happening? TomTom maps is responsible for what limitation? The ""via points" from MRA are not transmitted correctly to the Connected Ride? Thanks in advance.

Hurrah! Progress. Good chasing, Corjan.

@Mzokk exactly, but I prefer in this case the 1.2 and make the track visible.

@Corjan-Meijerink, Look great! [image: image.jpeg]

i also use trailer to move stuff and to transport my motor. maybe in future caravan.

Thank you

@KurtvPoucke nee, maar je kunt daar wel (op voorhand) iets aan doen, door eerst de route in OSM te maken en deze daarna in HERE openen. Als je de OSM-route eronder legt, dan kun je ze gelijktrekken. Eenmaal rijdend is het, zoals @con-hennekens terecht opmerkt, niet te wijzigen.

Thanks for sharing that

Good idea

Mainly as the current website also does not have a streetview option there. But I like the idea

Thanks for the tips! It's much appreciated.

Oh, right, I’d got it wrong. Maybe add "on beta" in this sentence.

Please don’t let this turn into another endless tyre-or-oil debate.

Two of my Android apps went through in 3 hours last night (not to rub salt in the wound!). They're a lot less complex than MRA, but I suspect it's to do with permissions requested (such as location, storage, access to device sensors, etc) which are a higher risk to users from Google's point of view, and need to be thoroughly tested. Maybe there's a location-specific test team and they're overwhelmed? Just politely let Google know they're falling behind the competition, and it's reputationally embarassing.

@Erdna What you are telling is crystal clear to me. But why isnt it possible to get the same expected duration in the moment I have opened the route in the MRA planner as I get from the navigaton app? Is it technically impossible for the planner to calculate with the current traffic conditions? btw: it seems my originally questions are already answered. time difference is due to traffic conditions planner is not able to consider traffic conditions

@b0hd1 I totally agree. I have received a replacement for my caretta and it's a new device for mra. Now I am locked out and have to wait for support. I think it is not acceptable.

@Tom-Grzelinski ok i wait like you Thanks