Re: [mkgmap-dev] Please help
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 im Auftrag von Gerd Petermann 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=576 and https://www.mkgmap.org.uk/websvn/listing.php?repname=display=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 im Auftrag von nick 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 +, 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: 03fa | 00 | aa 04 15 1b 15 08 cf 00 | record 0 (len: 300, 0x12c) Gerd Von: mkgmap-dev im Auftrag von nick 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 im Auftrag von nick 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
Re: [mkgmap-dev] Please help
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 im Auftrag von Gerd Petermann 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=576 and https://www.mkgmap.org.uk/websvn/listing.php?repname=display=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 im Auftrag von nick 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 +, 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: >>> 03fa | 00 | aa 04 15 1b 15 08 cf 00 | record 0 (len: 300, >>> 0x12c) >>> >>> Gerd >>> >>> >>> Von: mkgmap-dev im Auftrag >>> von nick >>> 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 im Auftrag von nick 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
Re: [mkgmap-dev] MDR header length and sections
Hi Ticker, thanks, committed with r578. Gerd Von: mkgmap-dev im Auftrag von Ticker Berkin Gesendet: Mittwoch, 29. Dezember 2021 19:55 An: mkgmap development Betreff: [mkgmap-dev] MDR header length and sections Hi Gerd Some of the old maps don't have Mdr sections after 19 and 29. Also some code didn't spot it should test after Mdr19, so Summary, Display and Check could give errors. I've added logic to stop getting sections after all the header lengths I've found in the various samples. Patch attached. Ticker ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] MDR header length and sections
Hi Gerd Some of the old maps don't have Mdr sections after 19 and 29. Also some code didn't spot it should test after Mdr19, so Summary, Display and Check could give errors. I've added logic to stop getting sections after all the header lengths I've found in the various samples. Patch attached. Ticker Index: src/test/display/MdrCheck.java === --- src/test/display/MdrCheck.java (revision 577) +++ src/test/display/MdrCheck.java (working copy) @@ -1606,61 +1606,76 @@ codepage = reader.get2u(); charSet = Sort.charsetFromCodepage(codepage); + // %%% TODO: might need to get the decoder if strings can be in Format6 Sort sort = SrtTextReader.sortForCodepage(codepage); isMulti = sort.isMulti(); collator = sort.getCollator(); collator.setStrength(Collator.SECONDARY); - reader.get2u(); - reader.get2u(); - reader.get2u(); + reader.get2u(); // id1 + reader.get2u(); // id2 + reader.get2u(); // unknown - Section sect = readSection(1, true, true); + Section sect = addSection(1, true, true); numberOfMaps = sect.getNumberOfRecords(); - readSection(2, true, true); - readSection(3, true, true); - readSection(4, true, true); - readSection(5, true, true); - readSection(6, true, true); - readSection(7, true, true); - readSection(8, true, true); - readSection(9, true, true); - readSection(10, false, true); - readSection(11, true, true); - readSection(12, true, true); - readSection(13, true, true); - readSection(14, true, true); - readSection(15, false, false); + addSection(2, true, true); + addSection(3, true, true); + addSection(4, true, true); + addSection(5, true, true); + addSection(6, true, true); + addSection(7, true, true); + addSection(8, true, true); + addSection(9, true, true); + addSection(10, false, true); + addSection(11, true, true); + addSection(12, true, true); + addSection(13, true, true); + addSection(14, true, true); + addSection(15, false, false); getSection(15).setMagic(reader.get()); - readSection(16, true, true); - readSection(17, false, true); - readSection(18, true, true); - readSection(19, true, true); - - if (getHeaderLen() > 286) { - readSection(20, true, true); - readSection(21, true, true); - readSection(22, true, true); - readSection(23, true, true); - readSection(24, true, true); - readSection(25, true, true); - readSection(26, true, true); - readSection(27, true, true); - readSection(28, true, true); - readSection(29, true, true); - readSection(30, true, true); - readSection(31, false, false); - readSection(32, true, true); - readSection(33, false, false); - readSection(34, true, true); - readSection(35, true, true); - readSection(36, true, true); - readSection(37, true, true); - readSection(38, true, true); - readSection(39, true, true); - readSection(40, true, true); - } + addSection(16, true, true); + addSection(17, false, true); + addSection(18, true, true); + addSection(19, true, true); + if (getHeaderLen() <= 286) // 0x011e + return; + addSection(20, true, true); + addSection(21, true, true); + addSection(22, true, true); + addSection(23, true, true); + addSection(24, true, true); + addSection(25, true, true); + addSection(26, true, true); + addSection(27, true, true); + addSection(28, true, true); + addSection(29, true, true); + if (getHeaderLen() <= 426) // 0x01aa + return; + addSection(30, true, true); + addSection(31, false, false); + addSection(32, true, true); + addSection(33, false, false); + addSection(34, true, true); + addSection(35, true, true); + addSection(36, true, true); + addSection(37, true, true); + addSection(38, true, true); + addSection(39, true, true); + addSection(40, true, true); + //if (getHeaderLen() <= 568) // 0x0238 + // return; + // looks like three sections, two with 4 ints, one with 5 ints + //if (getHeaderLen() <= 620) // 0x26c + // return; + // mostly zeros + //if (getHeaderLen() <= 668) // 0x029c + // return; +// possibly some sections, but mostly zeros so difficult to tell + //if (getHeaderLen() <= 700) // 0x02bc + // return; + // at 0x02dc, maybe 5 sections without magic or recsize + // haven't seen anything after 772 0x0304 } /** @@ -1672,7 +1687,7 @@ * @param hasMagic True if the section has a flags field of 4 bytes. It will be read and saved. * @return */ - private Section readSection(int number, boolean hasRecSize, boolean hasMagic) { + private Section addSection(int number, boolean hasRecSize, boolean hasMagic) { assert number != 0; int start = reader.get4(); Index: src/test/display/MdrDisplay.java === --- src/test/display/MdrDisplay.java (revision 577) +++ src/test/display/MdrDisplay.java (working copy) @@ -1782,6 +1782,9 @@ readSection(d, "MDR 27", 27, true, true); readSection(d, "MDR 28", 28, true, true);
Re: [mkgmap-dev] r4836 stops Hungary & Romania
Hi Ticker, BaseCamp show this: Palóc-Vasvár Írottko granite ?? or rovás feliratos kapu ?? I use "latin1" Greetz Arndt Ticker Berkinhat am 29.12.2021 10:17 geschrieben: Hi Arndt As a matter of interest, does any text show for https://www.openstreetmap.org/node/9122388694 or https://www.openstreetmap.org/node/9115233473 The text is mostly 'Old Hungarian' and I wonder if the java encoder tries any transliteration. What code-page are you using? Ticker On Tue, 2021-12-28 at 16:51 +0100, Arndt Röhrig wrote: Hi Gerd, Hungary and Romania work just fine. Thank you for your quick and uncomplicated help! Arndt ___ 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
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=576 and https://www.mkgmap.org.uk/websvn/listing.php?repname=display=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 im Auftrag von nick 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 +, 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: >>> 03fa | 00 | aa 04 15 1b 15 08 cf 00 | record 0 (len: 300, >>> 0x12c) >>> >>> Gerd >>> >>> >>> Von: mkgmap-dev im Auftrag >>> von nick >>> 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 im Auftrag von nick 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
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 +, 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: 03fa | 00 | aa 04 15 1b 15 08 cf 00 | record 0 (len: 300, 0x12c) Gerd Von: mkgmap-dev im Auftrag von nick 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 im Auftrag von nick 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
Re: [mkgmap-dev] Please help
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 +, 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: > > 03fa | 00 | aa 04 15 1b 15 08 cf 00 | record 0 (len: 300, > > 0x12c) > > > > Gerd > > > > > > Von: mkgmap-dev im Auftrag > > von nick > > 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 im > > > Auftrag von nick > > > 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
Re: [mkgmap-dev] r4836 stops Hungary & Romania
Hi Arndt As a matter of interest, does any text show for https://www.openstreetmap.org/node/9122388694 or https://www.openstreetmap.org/node/9115233473 The text is mostly 'Old Hungarian' and I wonder if the java encoder tries any transliteration. What code-page are you using? Ticker On Tue, 2021-12-28 at 16:51 +0100, Arndt Röhrig wrote: > Hi Gerd, > > Hungary and Romania work just fine. Thank you for your quick and > uncomplicated help! > > Arndt ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] r4836 stops Hungary & Romania
Hi Gerd I'll look at this sometime. I while ago I found something in one of the MDR sections (probably the short strings) that handled something like this. Ticker On Tue, 2021-12-28 at 13:22 +, Gerd Petermann wrote: > Hi Ticker, > > okay, maybe you find time to implement a better solution. > I've committed the patch with r4838. > > @Arndt: Please check if this solves the problems with your maps. > Not sure about this because you said mkgmap stops without any > reaction > while this problem was a loop. > > Gerd ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev