[mkgmap-dev] Sorry, Google is being restrictive. Try 2 with the files.
From Ticker Berkin rwb-mkgmap at jagit.co.uk on Fri Jul 31 13:18:57 BST 2020
Hi Randolph I think your test.txt TYP file might be exceeding various device limitations and have a few other problems. I've just converted it with mkgmap and then using TYPViewer to examine the resultant .typ file, firstly it takes a couple of mins to open the file, then it seems to be missing some entries. I'd recommend: Don't have [end][_point] on same line Stick to Types in range 0x01 .. 0x7f. Be consistent with Type= and Subtype=; I think you have entries that resolve to the same thing. If Type >= 0x100, the bottom 8 bits are the sub-type and the rest is the type. Don't have sub-types for cities (ie 0x01 .. 0x0d). Anyway, test-map doesn't generate them which is why you see the single line of icons to the left of the big block. Have sub-types (up to 0x1f) for the ranges where they have definite significance, ie: 0x2a..0x30 and 0x64..0x66 There are a few other places where subtype also have meaning but this is manifest in the default icon. Ticker
- Previous message: [mkgmap-dev] [Fwd: Re: Changes that I made in a recent set of default style files and the reason I have for making those changes.]
- Next message: [mkgmap-dev] Sorry, Google is being restrictive. Try 2 with the files.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list