[mkgmap-dev] set display name problem ( Error in style: Error: (lines:14): Unrecognised command 'display_name', Could not open style null )
From Felix Hartmann extremecarver at googlemail.com on Mon Nov 9 22:58:03 GMT 2009
Mark Burton wrote: > Hi Steve, > > >> There is also the issue that if there is a NET section a road can have >> up to four names, which cannot be expressed in the style file currently. >> > > Actually, they can because tags "ref", "int_ref", "nat_ref" and > "reg_ref" will assign to them (and they can all have multiple elements > separated with ";") > > could you explain a bit more how they work? Am I right that: {name} is the standard file and will be used for everything as long as no other is used {display_name} will be used as unique (or additional?) tool tip on GPS/Mapsource as well as for routing instructions. {ref};{int_ref};{nat_ref};{ref_ref} will be used as additonal tooltip AND appended to the {name}. Is the appending to {name} somewhere in mkgmap code configurable? (the display_name patch did somthing like this) Or is the {display_name} actually written to one of theese ref* fields? > Cheers, > > Mark > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20091109/93d462e0/attachment.html
- Previous message: [mkgmap-dev] set display name problem ( Error in style: Error: (lines:14): Unrecognised command 'display_name', Could not open style null )
- Next message: [mkgmap-dev] set display name problem ( Error in style: Error: (lines:14): Unrecognised command 'display_name', Could not open style null )
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list