Hi Gerd

The only thing I can add is that the large mdr file is part of the current Garmin NT file structure , ie Topo France V3 , which might explain the 2 additional bytes.

Nick

On 30/12/2021 07:19, Gerd Petermann wrote:
Hi Nick and Ticker,

there is another problem with the large mdr file.
The POI section (MDR 11) seems to contain 2 unexpected additional bytes 
before(!) the known bytes for city and MDR15 offset.
We should really try to find out the meaning of the magic number in MDR11 
instead of looking at the recsize only.
The current logic also fails with a gmapsupp index and tries to read MDR 15 
offsets :(
Maybe we can learn something for mkgmap there.

I'm working on an implementation of Huffman encoding in mkgmap first...

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Gerd 
Petermann <gpetermann_muenc...@hotmail.com>
Gesendet: Mittwoch, 29. Dezember 2021 12:29
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Please help

Hi all,

thanks for all the input.
It answered most of the open questions, display tool r577 should be able to 
analyse
all the files. Binary is here: https://files.mkgmap.org.uk/detail/543

See also https://www.mkgmap.org.uk/websvn/listing.php?repname=display&rev=576
and https://www.mkgmap.org.uk/websvn/listing.php?repname=display&rev=577

@Nick: the larger MDR seems to cause trouble when section 1 is displayed. Will 
look into this later.
r577 should work with option --print=!1
This option means that all but the 1st section should be printed, will cause
huge output for that file, but string decoding seems to work well

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von nick 
<o...@pinns.co.uk>
Gesendet: Mittwoch, 29. Dezember 2021 12:03
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help

Hi Ticker / Gerd

I've found another one which I think included mdr15 but second byte = 0x15

Also added a mdr.mdrfrom Topo France V3  which the display.jar couildn't
parse but might be of interest

Warning file  sz is large

https:\pinns.co.uk\2812\mdr2.zip

HTH

Nick

On 29/12/2021 09:31, Ticker Berkin wrote:
Hi Nick

Thanks.

Interesting, but not maybe not relevant to the Huffman stuff, in
mdr16austria.txt the MDR headers go out of sync after MDR30

Ticker


On Tue, 2021-12-28 at 18:28 +0000, nick wrote:
Hi Gerd

OK thanks will check that tomorrow.

I think it's amazing how far both of you got.

Nick

On 28/12/2021 18:26, Gerd Petermann wrote:
Hi Nick,

yes, and esp. those MDR 16 which do not have a 0x15 at offset 2
like in this example:
000003fa | 000000 | aa 04 15 1b 15 08 cf 00 | record 0 (len: 300,
0x12c)

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag
von nick <o...@pinns.co.uk>
Gesendet: Dienstag, 28. Dezember 2021 19:21
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help

Hi Gerd

Great but as you confusing, although typically Garmin  ;)

I noticed some are called map_mdr.img.

I'll check some other pc s tomorrow; I suppose you are specifically
looking for mdr16

Nick


On 28/12/2021 18:17, Gerd Petermann wrote:
Hi Nick,

thanks, the mdr file looks like a very early version with a very
different structure. Should help to understand the remaining bits
:)

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im
Auftrag von nick <o...@pinns.co.uk>
Gesendet: Dienstag, 28. Dezember 2021 19:00
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Please help

Hi Gerd

I have done a few for you, including one which causes a java
error so
added the mdr

https:\pinns.co.uk\2812\mdrmap.zip

Wishing you and Ticker  every success! Great Job !

r

Nick

On 28/12/2021 14:55, Gerd Petermann wrote:
java -ea  -Xmx6800m -cp
d:\display\dist\display.jar;d:\mkgmap\dist\mkgmap.jar
test.display.MdrDisplay MDRMAP.img   --print=16 > mdr16.txt
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to