@Mzokk said in Powerconsumption and MRA Next:

Why can't MRA use the OSM map set if the Here maps are so problematical?

Navigation apps are built around an SDK that is provided by the map provider. Switching to another map provider would basically mean developing a new app. The choice for HERE is partly based previous experience with a pretty good SDK (in the Previous Navigation app) and partly on the Flutter IDE that is compatible with the SDK. Basically that means that the app for IOS and Android can be built simultaneously with the same code. So the choice for HERE was not taken lightly, and in the light of everything getting better, probably the same choice would be made again today 😉

Niet alleen TomTom heeft dat onder de knie. Ook MRA heeft dat uitstekend onder de knie.

@Bas-Pors said in Herberekenen:

automatisch routepunten overslaan(beta) werkt soms maar meestal niet

De term beta in deze context verraadt dat het om de oude Navigation app gaat. Ik adviseer om over te stappen naar de nieuw app, de oude gaat ergen in jullie stoppen met functioneren, omdat HERE de stekker uit het platform haalt.

Wat mij betreft komt er helemaal géén optie om herberekenen uit te zetten, dat is namelijk nergens voor nodig als het terugkeren naar de route goed werkt. Met een goed uitgezette route werkt dat prima in MRA. Het mooie van de nieuwe app is dat de originele routelijn in een witte kleur zichtbasr wordt als je van de route afwijkt. De app stelt an een alternatief voor, maar je kunt dat ook negeren en zelf naar de route terug rijden zoals je gewend bent van je zumo.

@siepermann-ronald Absoluut / absolutely.

@Guzzist Thank you for your suggestion, will add it to the suggestion list.

From a design perspective I have to say though that I really dislike how steep and complex the basecamp data looks. While I will directly agree that it'd be important for people who like such complexity to be able to view this, I will most certainly try to improve the visual presentation of this. Especially in an app it's important to view things as efficiently as possible. Perhaps a solution would be to be able to download or open a data-pdf for a more in depth look.

Your general point: lunch pauses should not be included in total duraction and averages, is of course correct.

@Guzzist Thank you for clarifying that, Your comment interested me so I looked it up a little more on wikipedia and found this:

". While driving at higher speeds is not punishable, the increased risk induced by higher speeds (erhöhte Betriebsgefahr) may result in partial liability for damages. Moreover, the law forbids travel at speeds that would extend the vehicle's minimum halting distance beyond the driver's line of sight (Sicherheitsabstand).[16] On all German roads, there are speed limits for trucks, buses, cars towing trailers, and small motorised vehicles (Mopeds, etc.)."

Someone also told me that German insurers start holding you liable at speeds over 160 km/h. I'm not sure how accurate that is. Regardless, I might think twice now about going over 200.