Kaart in navigatie app

[Bart De Medts]

@Marinus-van-Deudekom eens getest en ik zie idd hetzelfde gedrag als te zien op jouw screenshots... wat eigenlijk niet zou mogen lijkt mij.

[Rob Verhoeff]

@Marinus-van-Deudekom Over dit gedrag van de OSM-kaart zijn al meerdere posts te vinden hier op het forum. Het klopt wat je zegt.

[Adrian Avram]

@Marinus-van-Deudekom funny thing is that MRA is mistaken not the OSM map.
I have used those 2 locations in the OSMAND web planner (which is using OSM maps), and what do you know ... no routing errors !
You can try if you don't believe me ! Its free ...

[Marinus van Deudekom]

@Adrian-Avram I see want you've posted. This forum is all about MRA and how it works. Or how to make it even better. All comments made see to the MRA app. It's not about Osmand, Basecamp or whatever program people use or used to use. I don't know what type of sdk Osmand is using I can only state that the OSM map that you can see in MRA is the one causing those unwanted turn offs on the highway. I don't like it but that's the way it is. So it's not an OSM error but the result of the OSM map in MRA.

[Con Hennekens]

@Nomko-Nomden said in Kaart in navigatie app:

Jullie doen er goed aan mij niet niet te verbeteren op basis van jullie ongefundeerde aannames.

Over een belerende houding gesproken...

Dat OSM vaak hazepaadjes kiest bij afslagen en tankstations aan autowegen is een algemeen bekend feit.
Zoals jij het beschrijft lijkt het of je plant in OSM terwijl je (uiteraard) navigeert in HERE op basis van "Route als Track" in de MRA app.

Ook wat jij beschrijft bij veerpontjes strookt totaal niet met de realiteit. Dit komt omdat HERE voor pontjes zonder vast vaarschema (zeg maar gerust ALLE inlandse rivierpontjes...) een half uur calculeert. Dus als er omwegen te vinden zijn die korter duren dan een half uur, dan zal die genomen worden in HERE. Hoe OSM dat doet weet ik niet, maakt me ook niets uit want ik navigeer met MRA en dus HERE, maar qua pontjes is het dus doorgaans juist HERE waar de omwegen verschijnen.

Hoe dan ook vind ik jouw "verbetering" van andere forumleden totaal ongepast, want ga maar eens tellen hoe vaak ik jou al heb moeten corrigeren. Zet mij gerust op negeren, maar ter bescherming van andere forumleden blijf ik waar het nodig is jou corrigeren.

[Adrian Avram]

@Marinus-van-Deudekom you seem kinda frustrated ...jees
This is a free world, I can say whatever I want, NOT whatever you want !
My opinion is that OSM map is not the issue in this case like it or not !

[Adrian Avram]

@Marinus-van-Deudekom how about DMD2 ... they are using the same OSM map !!!!
So OSM is to blame not MRA, right ?

[Con Hennekens]

@Adrian-Avram, You can say what you want, but that does not make it correct . Fact is that MRA does not do any route calculations, route calculations are done by logic provided by the map-provider. The difference you noticed probably has to do with difference in the map versions both Osmand and MRA use.

[Adrian Avram]

@Con-Hennekens how about that ... event Graphhopper is working with OSM .....

[Adrian Avram]

@Con-Hennekens So until now 3 different web planners using OSM map route correctly but MRA doesnt ....
You guys are blind or what ? Just cannot admit that maybe its a MRA issue here ?
Or maybe you are paid by MRA to be here and contradict with everyone .... That maybe it ...

[Con Hennekens]

@Adrian-Avram, I am not being paid, I am just refuting nonsense. You can compare whatever you want, but you do not have any insight on how calculations are being done. MRA does not do the calculations, period. And yes OF COURSE there will be some explanation for what is happening. map versions is one, SDK version could be another. Some day it will be corrected in MRA as well, probably as a result of some version upgrade.

[Marinus van Deudekom]

@Adrian-Avram you don't have to agree with what I say. I'm just trying to help users understand how MRA works so they can enjoy wonderfull routes. I'm nothing stating anything about other planners. I'm not using those. I'm not frustrated. MRA doesn't pay me a single cent. In MY opinion MRA is by far the best routeplanner. Is it perfect. Not yet but it's getting pretty damned close.
Try to stay positive and enjoy the ride

[Bart De Medts]

@Con-Hennekens said in Kaart in navigatie app:

Dat OSM vaak hazepaadjes kiest bij afslagen en tankstations aan autowegen is een algemeen bekend feit.
Zoals jij het beschrijft lijkt het of je plant in OSM terwijl je (uiteraard) navigeert in HERE op basis van "Route als Track" in de MRA app.

Slim, dat is inderdaad een mogelijke verklaring.

[Corjan Meijerink]

Wow people, how disappointing. Why are you all so easily annoyed?
I am absolutely detested by the fact that of some people here I expect more as respected community members. Part of being a respected community member is also sometimes to just let things be.

First of all - this thread is not at all answering the initial question.
The simple answer "HERE" is correct - done.

Then regarding the different mapping engines.
Both HERE and TomTom are paid services and we do not influence their routing in any way apart from the options that we expose in the toolkit. These services provide excellent routes with no errors (apart from possible access rules, time restrictions, seasonal closures etc that all come from missing data that can be reported using their tools).

OpenStreetMap is an open source map data platform.
Using this data people can create their own routes but that is not OpenStreetMap. That is done with GraphHopper, yet another piece op open sourced software (or some other routing platform but this one is most popular).

We, MRA, have our own implementation of this GraphHopper engine with the latest version of OpenStreetMap loaded into it. As this is our own server with some custom algorithms we are responsible of some of the routing.
Basic routing errors can be caused by map data mistakes (OpenStreetMap) but more likely it's because we actually have a mistake in our server.

@Adrian-Avram you are completely right this is an issue on our side and I've asked the person responsible to investigate it and fix it.

Feel free to contact me personally for further discussion but I will lock this thread.