- mkgmap-dev - The mkgmap lists

Commit r4826: fix typo in method name, no functional change
by svn commit 02 Dec '21

02 Dec '21

Version mkgmap-r4826 was committed by gerd on Thu, 02 Dec 2021 fix typo in method name, no functional change http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4826

1 0

MapSource special behaviour with Chinese characters (unicode)
by Gerd Petermann 01 Dec '21

01 Dec '21

Hi all, it seems that the search in MapSource does something special when I search for road names with chinese characters. The result list contains all road names that match in the first 2 characters "八卦", as if MapSource simply ignores the rest. I've used these options: --lower-case --preserve-element-order --bounds=f:\osm\bounds.zip --gmapi --gmapsupp --index --code-page=65001 --net With German road names this doesn't happen. Gerd

3 3

Commit r4822: - use StandardCharsets.US_ASCII instead of "ascii" parameter where possible
by svn commit 01 Dec '21

01 Dec '21

Version mkgmap-r4822 was committed by gerd on Tue, 30 Nov 2021 - use StandardCharsets.US_ASCII instead of "ascii" parameter where possible - stop with error when --code-page option is not a number (instead of silently using 0) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4822

3 4

Commit r4825: 2nd try to throw exception when invalid --code-page parameter is given
by svn commit 01 Dec '21

01 Dec '21

Version mkgmap-r4825 was committed by gerd on Wed, 01 Dec 2021 2nd try to throw exception when invalid --code-page parameter is given http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4825

1 0

Commit r4824: partly revert r4822, it breaks unit tests (problem with junit?)
by svn commit 01 Dec '21

01 Dec '21

Version mkgmap-r4824 was committed by gerd on Wed, 01 Dec 2021 partly revert r4822, it breaks unit tests (problem with junit?) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4824

1 0

Commit r4823: minor fixes
by svn commit 01 Dec '21

01 Dec '21

Version mkgmap-r4823 was committed by gerd on Wed, 01 Dec 2021 minor fixes - remove extra line feed in some log messages - add missing cast http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4823

1 0

Commit r4821: revert changes from r4820, global index is wrong and search for roads on the device doesn't work
by svn commit 30 Nov '21

30 Nov '21

Version mkgmap-r4821 was committed by gerd on Tue, 30 Nov 2021 revert changes from r4820, global index is wrong and search for roads on the device doesn't work http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4821

1 0

index option
by 7770 30 Nov '21

30 Nov '21

Hi. I generate maps using the following options (among others) --net --route --index --split-name-index When loading the ready img file to a GPSMAP 66st it is very slow in searching for cities (FIND -> Cities). Searching for some location can take many minutes or even lock the unit in rare cases. The problem is present even if a specific map is selected and search is only conducted within that map. Loading the same img file on an old etrex vista hcx did show very fast city search. Does anyone know if the options given to mkgmap can impact negatively in this particular scenaio or if there can be some other option added to make city search faster? Side note: street name search is fast, but searching among All POIs is also slow. Regards Karl

4 6

Commit r4820: Modify default encoder (code-page=0)
by svn commit 30 Nov '21

30 Nov '21

Version mkgmap-r4820 was committed by gerd on Tue, 30 Nov 2021 Modify default encoder (code-page=0) format6-v6.patch by Ticker Berkin. Original description for the first version of the patch: "I was looking at encoders and noticed obvious mistake in Format6Decoder relating to lower-case, plus parts that can be simplified to be general and consistent with Format6Encoder. Format6Encoder can handle a bunch of other characters (the remains of the 'ascii' printables) + lower-case - I've implemented these." http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4820

1 0

relation label patch
by Mike Baggaley 29 Nov '21

29 Nov '21

Hi Gerd, Please find attached a small patch that allows a node tagged with a role of label or admin_centre to be still used if it has no name defined, rather than only if it matches the name on the relation. Also an improvement in the diagnostic message when a role label node is not being used. An example relation that has an unnamed role label is http://www.openstreetmap.org/relation/10090341 An example of a relation having a differently named label role node is : http://www.openstreetmap.org/relation/7218222 I'm getting a warning that role node http://www.openstreetmap.org/node/2642288017 is being ignored because it has a different name than http://www.openstreetmap.org/relation/58437 They both have name=Cymru / Wales, name:en=Wales and name:cy=Cymru, so should match. However, at the beginning of my points, lines and relations files I have statements to overwrite name with name:en. This gives me name=Wales for the relation, but because at the time of processing the label node it hasn't been processed by the points file, the name of the node is still Cymru / Wales, thus they don't match and the role label is ignored. It's only a minor problem, but I'm wondering whether the solution is to introduce an optional names file (or other named file) that could be read before reading points lines and relations and also when handling the admin_centre and label nodes. Not sure whether there are any other places that this approach would be beneficial. Cheers, Mike

2 5