[mkgmap-dev] Handling of Garmin magic label codes (highwayshields etc.) differs from mp-format input to osm-format ?
From Clinton Gladstone clinton.gladstone at googlemail.com on Tue Oct 6 10:06:35 BST 2009
On Mon, Oct 5, 2009 at 8:02 PM, Gert Münzel <Gert.Muenzel at netcologne.de> wrote: > Clinton wrote: >>highway=* {name '${ref|highway-symbol:oval}<0x1f>${name}' >>Where "<0x1f>" is the actual hex code 1f, inserted with a hex editor. >>This might be enough for Gert to test this out without requiring any >>modifications to mkgmap. > Maybe i missunderstood you, but you really mean that i should insert/modiy single > bytes with a hex editor in the imgfile? Yes, you did misunderstand (or I provided an inappropriate explanation): you need to insert the hex code directly into the style file. That means you need to open the style file with a hex editor, find the byte between ${ref|highway-symbol:oval} and ${name}, and change the byte to the hex equivalent of 1f. I don't know if it will work properly here, but it might be worth trying. As I said, this is how we initially tested out the highway symbols function. Cheers
- Previous message: [mkgmap-dev] Handling of Garmin magic label codes (highwayshields etc.) differs from mp-format input to osm-format ?
- Next message: [mkgmap-dev] Handling of Garmin magic label codes (highwayshields etc.) differs from mp-format input to osm-format ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list