MapFactor Forum

person, who can make comment is on holiday, please be patient

it is a very incorrect guess :-)

Thank you! I will be patient!

I agree with hurdygurdyman (again :) ).

I also want to refer to the topic "Time To Destination Algorithm".
MapFactors calculations are way off, especially when a lot of motorway and trunks are in the calculation.
If Tule's assumptions in post 1 are correct then that's also another reason to discuss the type of roads and to get a better estimated time for the route calculation.

I personally use for car navigation the below (mine) speed settings for car as it gives much better results in Netherlands, Belgium, France and Germany compared to MapFactors (default MFNF) settings:

                 default MFNF          mine

motorway       130    80    50       110    70    70
primary         90    50    50        90    50    65
major           85    50    50        80    50    60
secondary       80    50    50        70    50    50
local conn      70    50    50        60    50    50
lcl rd oh imp   60    50    50        60    50    50
local road      60    40    50        50    40    50

There are however better settings if we had better road distinctions.

:) well, yes I am avoiding this topic ;). I think that wrote somewhere currently used conversions:
  dict = {
      'motorway': (0,130),
      'motorway_link': (0,110),
      'trunk': (1,110),
      'trunk_link': (2,90),
      'primary': (3,90),
      'primary_link': (3,80),
      'secondary': (4,70),
      'secondary_link': (5,60),
      'tertiary': (6,50),
      'tertiary_link': (6,40),
      'residential': (7,30),
      'unclassified': (7,30),
      'living_street': (7,20),
      'service': (7,30),
      'footway': (9,5),
      'track':(8,5),
      'path':(9,5),
      'cycleway':(8,10),
      'pedestrian':(8,5),
      'road':(7,30),
      'steps':(10,2),
      'construction':(8,10),
      'bridleway':(8,5),
      'unsurfaced':(8,15)
      }
The number of road categories is very limited. Since Navigator 14 (Android version 1.2.x) it is possible to put more precise speed info per each link which will open way to "smarter algorithms"/conversion. OSM data are at the moment still converted into older format (and thus compatible with older applications).
p.s. I plan to be on vacation again next week ...

And at last I think residential, service and living_street only should
be used to route anywhere, if there is no other possibility to get to
target.

That's exactly what has been mentioned here in this forum by other users (myself included) many times before. Hopefully, MapFactor will finally adopt it. :-w

Hi mdx,
you are right. Small local roads are disabled by default, but unfortunately I activated them anytime before without any knowledge about that they are used to get the target there also if they are disabled. Maybe according to level8-roads there should be a message like "Activating this let you route through residential, service, living streets etc. for transit. If you don't activate, they are only in use to reach your target there."
For unclassified and motorway=yes I'm thinking about a solution and will send you an excel-sheet then by mail.

I am not sure if I understand your comment correctly
motorway = 0
trunk = 1
primary = 3

Hi Tule,
I approve your opinion. There is no need to differ *_link by number (but by speed). So we would get the chance to have some free numbers to differ lower street-categories in higher numbers. I'm thinking about, but didn't find the time within thelast days to structure it completely also with sencefull meanings for the categories to use in settings.

Sorry for cross-posting but I just filed a feature request and while doing that I had something relevant for this topic as well.

If you enable "small local roads" which I have enabled*, you also run the risk that Navigator will lead you over unpaved roads. Most drivers don't like this (me including of course).
Could there be a setting in the vehicle profiles to "avoid unpaved roads", like currently for toll roads.
(Again: sorry for cross posting)

*:I have enabled the "Small local road" also in my Car profile with
settings like 30/30/50, due to the fact that in the Netherlands many
suburbs are now (almost) completely 30 km/h. Navigator has the tendency
to go too early to a "bigger" road leading to sometimes real
"sub-optimal" much longer routes. With my setting I get correct routes in suburbs)

@riccie:
putting "unclassified" together with "residential" etc. isn't a good idea, because
"Unclassified is used for minor public roads typically at the lowest level of the interconnecting grid network."
(see http://wiki.openstreetmap.org/wiki/Tag:highway=unclassified )
And so its not a local road like the others.

It's ok....

Thank you for explanation of the problem!
My fingers crossed you can find a good solution!

@MapFactor
Could you please update us on this topic?

I'm testing routing of navigation MF Navigator Free, PC and Android version.
Before them I reinspect all roads in OSM of my town.
All roads (streets) have maxspeed sign and are mostly these types: residential - living street - service - parking_aisle (type of service road).
There are one primary road, one secondary and one tercialy.
I'm setting average speed setting in navigation menu: local road=50, small local road=40
and set to find fastest route.
OSM database is already updated and is correct.

I found these mistakes:
1.) two paralel residential roads, first with 50 km/h spedlimit and second with 30 km/h.
Navi routes over 30 km/h because this is very litle shorter (cca 5 meters).
Its seems router engine totaly ignored tag "maxspeed" in OSM.
2.) two paralel roads: one residential (50 km/h) and second service roads (20 km/h) + little segment of parking_aisle (no maxspeed tag).
Navi routes over service roads and parking aisle because is very little shorter.
3.) Engine routes also by roads with tag "motor_vehicle=destination".

It is bad idea that residential roads (typical speed 50 km/h) and living street, parking-aisle (typical 20 km/h) are the same priority. (and speed is still ignored)
In urban navigation is impossible get correct route.