logo separator

[mkgmap-dev] Feature Request: mkgmap able to create gmap archive (BaseCamp)

From Carlos Dávila cdavilam at orangecorreo.es on Sun Dec 4 15:21:25 GMT 2016

I've been using gmapi-builder.py for years within my tool chain without 
such block warning. I don't remember where I got it from nor when, file 
is dated February 2011. I have placed a copy of it at [1] in case you 
want to try it.
[1] http://mapas.alternativaslibres.es/gmapi-builder.py

El 04/12/16 a las 11:58, Steve Ratcliffe escribió:
> Hi, thanks for testing. I believe you can ignore that error.
>
> On 4 December 2016 10:38:27 GMT+00:00, Patrik Brunner <patrik.brunner at gmx.net> wrote:
>> thomas,
>>
>> thanks for the explanation.
>>
>> Source files (map itself and typ files) handed over to gmapi-builder.py
>>
>> have just been created one step before by mkgmap.
>>
>> I've just made the same process with another Perimeter, Switzerland,
>> and
>> the same thing happens.
>>
>> But as stated originally: I'm not sure how bad this error is as:
>>
>>   * the image directory with these tbd file is useable in BaseCamp
>>   * the created gmap directory is usable in BaseCamp
>>   * the created gmapsupp.img out of the same source files is usable too
>>
>> Either a misinterpretation of gmapi-builder.py or something which is
>> handled wrongly in mkgmap, but as it appears without doing too much
>> damage.
>> But that's just a rough guess from what I see from the outside..... I'm
>>
>> the wrong person to track that down to the root cause.
>>
>> But I'm always willing and able to test and provide results.
>>
>> Cheers
>> Patrik
>>
>> On 04.12.2016 11:13, Thomas Morgenstern wrote:
>>> In tdb file exists such block 0x54. And it must have 20 byte. in your
>>> example i see only 18 byte ? Block 0x54 contains  CRC sum of the tdb
>>> file ( without the 0x54 block) the crc is stored in byte 0x54+5,
>>> 0x54+12, 0x54+15, 0x54+20.
>>>
>>> 0x54+5=Int(nCRCSum / 16777216)  'vByteD
>>>
>>> 0x54+12=Int((nCRCSum - vByteD * 16777216) / 65536) ' vByteC
>>>
>>> 0x54+15=Int((nCRCSum - vByteD * 16777216 - vByteC * 65536) / 256)
>>> 'vByteB
>>>
>>> 0x54+20=Int(nCRCSum - vByteD * 16777216 - vByteC * 65536 - vByteB *
>> 256)
>>> all other bytes=0
>>>
>>> thomas
>>>
>>>
>>> Am 04.12.2016 um 10:40 schrieb Patrik Brunner:
>>>> Steve,
>>>>
>>>> I've downloaded both versions of gmapi-builder.py, the one from
>>>> bitbucket and the one from the mkgmap code base. They're bit
>>>> different and I couldn't find a version number when checking
>> quickly,
>>>> but only the mkgmap version supports -i for mdx files. Therefore I
>>>> continued with the mkgmap codebase version only.
>>>>
>>>> The tool runs through and creates a loadable gmap directory for
>>>> BaseCamp (tested only on Windows).
>>>>
>>>> But it also give out an 'error' or 'warning' about an unknown block,
>>>> possibly to be checked further when implementing in mkgmap:
>>>>
>>>>      Unknown Block: 54, length: 20,
>>>>     
>> '\x00\x00\xf7\x00\x00\x00\x00\x00\x00j\x00\x00\x99\x00\x00\x00\x00`\x00\x00'
>>>> Attached the complete command output ran with -v.... please ignore
>>>> the copyright/license output... the strange content is testing stuff
>>>> from another construction area, as you know... license information
>>>> and unicode  ;-)
>>>>
>>>> Testing inside this construction area will be next on my list for
>>>> today...
>>>>
>>>> Thanks and regards
>>>> Patrik
>>>>
>>>> On 03.12.2016 23:26, Steve Ratcliffe wrote:
>>>>> Hi
>>>>>
>>>>>> I'm wondering if it would be possible that mkgmap is able to
>>>>>> create/convert maps also in the gmap (gmapi) format used for
>>>>>> BaseCamp on
>>>>>> Windows and Macintosh.
>>>>> Yes, this seems a reasonable thing to do.
>>>>>
>>>>> In the mkgmap code base there is a python program called
>>>>> gmapi-builder.py in the scripts directory.
>>>>>
>>>>> See also https://bitbucket.org/berteun/gmapibuilder/overview
>>>>> and http://wiki.openstreetmap.org/wiki/Gmapibuilder.
>>>>>
>>>>> This is a converter, but should work on all platforms with python
>>>>> installed, or could be made to do so...
>>>>> The first step is to verify that it works; then it should
>>>>> be easy enough to implement within mkgmap itself.
>>>>>
>>>>> ..Steve



More information about the mkgmap-dev mailing list