Aha … So in other words these types should be really used for what they are meant for.
Is it complete list of routable types which having “special purpose”?
This would be great … I miss few (3-4) routable types which I can use freely … I meant they don’t have any “special purpose”.
mira
Better use line types as defined in cgpsmapper manual. I think types 0x01 - 0x03 can have special meaning, they could be preferred when calculating fastest route and can be influenced by “avoid highways” settings (probably 0x01 only).
Some of line types can be invisible by default, you would have to add graphics definition in typ file to see them in device.
Garmin maps are designed for car routing, any other routing type, like for example bicycle routing, is difficult to obtain. If you’d like to create map for bicycle or skiing, than maybe you should use car mode using highway types for dedicated paths.
ok
My Garmin 78s has many options for navigation: car, bicikle, montain bike, walking, hiking, skiing.
mira
Hmmm …For what I should use these types?
mira
These are connections between roads on interchange.
Yep, you can use 0x0d, 0x0e, 0x0f, 0x10, 0x11, 0x12 and 0x13 for routing too.
0x14 is used for railways, but it is only rendered at very high zoom resolutions.
It is very odd that official Garmin topomaps hardly shows any railways, unless you zoom in very close. 
Aha …
got it. Thank you
Excellent! Why this is not documented? 
mira
Hi,
Another question is about routing priority.
If there are two options how to get from A to B on what depend decision?
The shorter is taken? Or quicker?
Is there any way how I can influence the choice by my personal preferencies?
e.g. I prefer bike on low-traffic roads or tracks, but tertiary road is acceptable if no other choice.
regards
mira
Garmin looks at the road_speed and road_class parameters, the number of turns it has to make (less is better) and maybe sharp bends in the road?
You can play with road_class and speed. But it also depends on the activity, with the new activity routing it looks that cycling activities seem to prefer lower road classes and driving prefers higher road classes. In my cycling map I use higher road classes for cycleways and cycling routes, so the user with a modern garmin has to use the automobile profile instead of the cycling profiles. I also recommend this because there is also a “feature” or bug that blocks routing on every way tagged with access=no if carpool lanes avoidance is activated, which is default in the bicycle profiles. So cycleways with access=no & bicycle=yes will not route in the bicycle profile, unless you switch carpool avoidance off.
To me it looks like Garmin should handle routing in clever way and I will not need do any tricky things.
I just finished big changes to my TYP file and lines file to improve using of routable types.
I build my map and make some test routing … everything works surprisingly well. 
There is only one disapointment … I thought that my garmin also do ski routing, but it doesn’t.
There are these options for routing:
direct routing
automobile driving
motorcycle driving
cycling
tour cycling
mountain biking
pedestrian walking
hiking
mountaneering
atv/off road driving
Is there any chance to make ski routing? For e.g. via “motocycle routing” option … by making ski routes “super highly attractive” for motorcycle?
best regards
mira
I’m glad it works for you but it surprises me you wont need any tricks.
You can use skirouting by using tricks like toll road avoidance, only if you dont use this feature of course.
First reset all roads by deleting all toll tags. Then apply mkgmap:toll=yes on all highway=* except the ski routes.
In your motorcycle profile activate toll road avoidance to use the ski pistes 
and you are done.
I use this trick to cycle on bike routes. If you dont want to abuse toll roads, you can try the mkgmap:ferry option or maybe treat real toll roads as they were ferry routes to avoid them with the ferry avoidance option.
I just tried find some routes in city and for car routing has been done on roads shortest possible way,
for bike it was done on bike_route and for hike it leaded shoter way on footways.
So for beginning I am happy … I will find some issues latter for sure
This sounds good to me, but I can’t find “toll road avoidance” on my navigation Should be this option on all garmin models?
Hmmm … again I can’t find “ferry avoidance” option.
mira
What about just make all road motorcycle=no and just ski routes make motorcycle=yes
Something like this:
highway=* {add motorcycle=no}
piste:type=nordic {add motorcycle=yes}
Can I break something like this?
mira
motorcycle is not understood by Garmin 
I dont know anything about your gps, but in most modern types only car and foot are supported.
Even bicycle=yes or no is not respected anymore, only in the older gps devices.
All those routing types are somehow related with the road parameters but until now mkgmap does not know exactly how.
Hmmm … Pretty limiting
But anyway I am quite happy for the moment.
Thank you for help!
mira
What you also could do, is making separate transparent routable map layers with lines only for each activity and another non routable base layer with topography (landuse, water, pois etc). In every map layer you can choose which ways you want to make routable for each activity and which ways non routable (for instance in your ski map only the pistes are routable). The disadvantage is that you cannot view more layers at the same time in Basecamp or Mapsource.
It is interesting … I would like to try. How I can do this?
This is not big problem for me
mira
It shouldnt be too difficult. Just create a new map and start with the ski map. Fill in the lines file only the lines that you want to render.
The polygon and points file you can leave empty and use --transparent in your mkgmap options. Try this on top of your other map.
Because both maps are routable you can expect problems.
Once you have created all routable map layers (car, hike, bike, ski) you can make the basic map not routable. You can even show all roads on the basic map and on the routable layers only roads that are needed for each activity plus route relations.
Routable map can contains only roads and be created as transparent and invisible. Non-routable map should contains all except routing. For me the only problem was, that mkgmap connects address search with routing, which is not optimal solution. I bypassed this creating main routable map and then removing routing with GMapTool.