
Felix, Last email for today - i'm fried.
Just a small question. If I add to a poi { add road_speed_min='-1'; add road_speed_min='1' } what happens if the original road had road_speed=0 will it be increased or stay at 0? (I assume and hope for the latter).
Yes, the min/max tags only have an effect if mkgmap:road-speed or mkgmap:road-class are in use for the way in question.
BTW - the syntax is mkgmap:road-speed-min and not road_speed_min as in your example (I think you knew that, really)
Hmm no, I find this confusing as in the lines file I have always been using road_speed and road_class... Or is road-speed working everywhere? okay so now I use this: highway=traffic_signals { add mkgmap:road_speed = '-1'; add mkgmap:road_class = '-1'; add mkgmap:road-speed-min = '1' }
I noticed that setting only road_speed or road_class was not significant enough. with the min values we have no I will try whether maybe highway=traffic_signals { add mkgmap:road_speed = '-2'; add mkgmap:road-speed-min = '1' } is more appropriate.
the reason why these new things are using mkgmap:tag syntax is because I think they should be easily distinguishable from any other tag that may appear in the OSM input. i.e. the mkgmap: prefix should achieve that. Things like road_speed and road_class are special 'magic' tokens that the style engine recognises, they are not related to the XML tag/value pairs in the OSM input. So, keep using road_class and road_speed as before but use the mkgmap:tag syntax for the values that are introduced by this new capability. Cheers, Mark