Hi Ticker, sorry, I must have done something wrong. NET3 order seems correct with the patch and wrong without.
Gerd ________________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Gerd Petermann <[email protected]> Gesendet: Donnerstag, 18. November 2021 14:22 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r4811: fix java.lang.AssertionError while building index from unicode tiles Hi Ticker, mdrUnicode_v9a.patch also changes the order in NET, esp. the "Roads as sorted in NET 3 ". The order in unicode with the patch is different to that with 1252 because highway symbols are now ignored. Is that intended? I don't remember where this order is important. Gerd ________________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Ticker Berkin <[email protected]> Gesendet: Donnerstag, 18. November 2021 13:16 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r4811: fix java.lang.AssertionError while building index from unicode tiles Hi Gerd Any map where there is a highway with a ref=* and it exists as more than one of {motorway/trunk}, {primary}, {secondary/tertiary}. The default style will apply different highway-symbols. Try with --code-page=1252 and code-page=65001 and see the differences in MdrCheck sections: mdr7 check: (r) vs (Rr) mdr20 check: ditto mdr11 check: 0x6616/Land-Summit points, when unnamed but with a height, change position in the list. mdr19 check: differences due to above. With mdrUnicode_v9a.patch, the Unicode behaviour for typical European maps should be the same as before r4809. Ticker On Thu, 2021-11-18 at 09:21 +0000, Gerd Petermann wrote: > Hi Ticker, > > please share your testdata so that I'm able to reproduce the > differences. > > Gerd > > ________________________________________ > Von: mkgmap-dev <[email protected]> im Auftrag > von Ticker Berkin <[email protected]> > Gesendet: Donnerstag, 18. November 2021 10:06 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r4811: fix > java.lang.AssertionError while building index from unicode tiles > > Hi Gerd > > While looking at the mdr output from Mapinstall and the differences > in > the street repeat flags, mainly where there are shield/road-ref > entries, I realised my change to Sort.java for undefined sortOrder > went > to far and it disrupts this ordering for Unicode. > > Missing or 0 sortOrder (anything before the first "<" in > sort/cp*.txt) > means the character is ignored by the key sort and > collator.compare(), > so TERTIARY and EQUAL can give different answers. > > Attached is mdrUnicode_v9a.patch that generates a fake sortOrder only > for rows where no sortOrders are defined, instead of for anything in > Unicode with no/0 sortOrder. > > With this patch it becomes possible for Unicode to trigger the > original > problem again. Attached is mdrUnicode_v9b.patch that has the fix for > this from the previous patch. > > Ticker _______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
