Hi,
I would like to report issue that happens in Navigator (older version and also 5.0).
For some weird reason the app prefers worse road (actually very bad road) over normal asphald road.
The problem occurs when you try to plan route from Kraliky in CZ to Roztoki in PL.
Sample route here (sorry not going to bother with screens from the device unless necessary).
On mapy.cz it selects correct route - after boarder is village Boboszów and afterwards Smreczyna, on yellow road33
https://mapy.cz/zakladni?planovani-trasy&x=16.6487852&y=50.1218884&z=12&rc=9mVlVxYa9y9m5vVxXvc6&rs=osm&rs=muni&ri=34786794&ri=2985&mrp={"c":111}&rt=&rt=&xc=[]
https://mapy.cz/zakladni?planovani-trasy&x=16.6487852&y=50.1218884&z=12&rc=9mVlVxYa9y9m5vVxXvc6&rs=osm&rs=muni&ri=34786794&ri=2985&mrp={"c":111}&rt=&rt=&xc=[]
What happens in mapfactor is that it selects the road that goes around Smreczyna, like this:
I was there on vacation actually almost 2 years ago when I noticed this problem and I do not know what is the problem. Back there I edited the "wrong" road with surface=gravel, because it is not even a asphalt road.
So we have designated first class road that crosses Smreczyna or third-class road without asphalt that is slightly shorter (and perhaps there is no speed limit because is outside town) but MUCH worse. The road is actually ok only for 1 care (so is no 2-lane road, but only 1 lane) and the surface is very poor. Unless it is destination this should not be preferred road.
You can see on google how this road looks.
Eithere there is some problem with the data itself (does not seem likely) or for some reason the algoritm prefers the bad road over the good road n.33
When you extract data from OSM, do you take into account the road surface? I can understand that this road is selected as it is shorter and faster (no 50 kmh speed limit like via Smreczyna).
And if this is algorithm problem than this somewhat undermines my trust into mapfactor navigator :(
Thank you for looking into it.