I've recorded the same navigation mistakes into Navigator Free as dammat has.Navigator Free is driving by car via footway and path (expecially when footway is nearer the target than highway=residental/path...My navigation settings is the same as dammat's.Please solve this problem

I think it's very simple, application should not suggest route for motor vehicle through higways with tag footway or path, no mater where is deperture or destination point. Please correct me if I am wrong...

I agree with your opinion.We should not add tag "access" to footway and path becauce Navigator Free has a problem with correct navigation. OSM maps are universal stores and maping only for Navigator is unacceptable.

Przemek you are wrong.Footway/cycleway/path are use to walking/cycling - NOT FOR DRIVING. When I drive a car I have to use only roads by car and there is no matter if destination point is closer to footway or to typical road for cars.Navigator in my opinion should stop navigate as the nearest the target as it can but only on road by car (of course if I'm going by car).I'll show you other examples - also in Sedziszow.

...hmmm, Your destination point is still on the footpath, so You decide and You get it. There are a lot of footpaths covered by roads. You can use search engin to avoid such problem. IMHO it is ok, for some type of cars and that we can choose it.

Out of curiosity I routed the above 2 examples and they are completely ok. Not using footpaths.Using PC version 12.3.0 with map from 28-04-2014 with standard car. Result is independent of routing mode.I set however departure and destination on the road and not beside it.

Dammat, I'm not an expert, but You can use Potlatch2 in simple/basic mode, and add more tags for all this roads - in tab Restrictions change 'unset' especially for motor vehicles /to allowed?/. Adding more data /tags/ give us better result. For footpath - motor vehicles - prohibited. I think it is the fastest way.

I want back to my case. Correct me if I am wrong but I understand that for now highway= track, footway or path are the same category for NF = not accessable by default for motor vehicles. I have suggestions, that highway= track, but only with tracktype=grade1 and grade2 (http://wiki.openstreetmap.org/wiki/Key:tracktype) should be for route alghoritm more than highway= track (grade3-5), footway and path but of course less than unclassified and residental. I think track with tracktype=grade1 and grade2 are acceptable for motor vehicles if there is no other options. What You think about that?

Przemek,I had email from MF technical suppport dated 19.05.2014. They confirm that problem we are talking about exists in Navigator Free app (OSM datas are good).I don't understand what are you talking about in the first part of your post. Please write me in polish to my email dawid_swider@wp.pl

I have the newest map of Poland (issued 9.06.2014).The first two cases - NF navigates in the same way when a road is under construction or road is opened. I drived this road many times beffore it was closed. NF always said: go through.

Przemek I'm sure you know that maping in OSM for one apps (NF in this case) is forbidden. OSM datas have to be universal.Show me in http://wiki.openstreetmap.org/wiki/Main_Page topic where I or everybody can read about correct/incorrect angle of roads connections.

Mapping for universal means also for navigation. Program, algoritm has to decide which angle means through, and you have to ask about it programmers, or support. If you want, you can improve maps or buy commercial.

Przemek I understand what "universal" means. I map in OSM from time to time and try to improve it specially for navigation. Of course I can buy commercial maps but I don't want it.I think we rather shoud talk in this forum about NF developing than what I can do or not.I ask you once again: do you able to show me in http://wiki.openstreetmap.org/wiki/Main_Page topic where in written how to map roads connection? I want to learn it.