November 2021 - mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] Embedding raster maps
by Oliver Eichler 25 Jan '22

25 Jan '22

Hi Steve, thanks for the file. On my device nothing is visible at all. But that's kind of an information, too. There is no way to circle down bugs by simply skipping the extended part. Probably it is still some missing encoding. In the Isle of Man map (and others) there is much more information in the RGN header. Note the values in the "filling bytes". And there seems to be an additional section after the extended point2 section. I called it offset1/length2. --- RGN header --- size 007D type 47 41 52 4D 49 4E 20 52 47 4E | GARMIN RGN byte0x0000000C 01 flag 00 year 2010 month 7 day 21 hour 9 minute 53 second 6 offset1 0000D54E length1 00000000 offset_polyg2 0000D54E length_polyg2 00001A1F byte0x00000025_0x00000038 02 00 00 00 00 00 00 00 FF 00 00 20 FD FC 03 00 00 00 00 00 offset_polyl2 0000EF6D length_polyl2 00000000 byte0x00000041_0x00000054 00 00 00 00 00 00 00 00 3F 00 00 20 FD 0F 00 00 00 00 00 00 offset_point2 0000EF6D length_point2 00000000 byte0x0000005D_0x00000070 00 00 00 00 00 00 00 00 FF 07 00 20 3F F7 3F 00 00 00 00 00 offset2 0000EF6D length2 0000020B unknown 000000E3 This section has a variable length in different sub-files. The unknown value E3 can be E5, too. It doesn't seem to be a record size. I had a look at several sections. They are not completely random, thus there seem to be no "compression". However the patterns do not ring a bell for me. I copied a couple of them into a file and loaded it into my cloud share: https://www.magentacloud.de/share/s429h1z-r6 Maybe one of you has an idea what it's about. I also uploaded my current version of the test map with a single raster map tile. It does not show. Top left coordinate is N46° 57.768 E011° 47.484. Sadly I am stuck here and I am running out of quality time to concentrate on the topic. I also have to update QMapShack's decoding. While reading the mkgmap source code I noticed a lot of new stuff that is not covered by the decoder. Cheers Oliver

4 6

Format6Encoder/Decoder
by Ticker Berkin 15 Dec '21

15 Dec '21

Hi Gerd 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. Patch attached Ticker

2 15

Exception in thread "main" java.lang.IllegalArgumentException . on Europe extract
by Felix Hartmann 10 Dec '21

10 Dec '21

Using mkgmap version 4808 - when compiling Europe. It went through fine on all geofabrik country extracts. I then upgraded to mkgmap 4819 and yesterday downloaded a new europe extract (4 days newer) from geofabrik to see if I can reproduce it again - and the error message is identical. I'm going to run with default style now again - to see if it makes a difference. C:\openmtbmap\mkgmap.jar --max-jobs=11 --order-by-decreasing-area "--generate-sea" --code-page=65001 "--precomp-sea=E:\OpenMTBMap\osmpbf_geofabrik\sea.zip" "--style-file=C:\openmtbmap\openmtbmap_style" --add-boundary-nodes-at-admin-boundaries --fix-roundabout-direction --improve-overview --drive-on=detect --allow-reverse-merge --lower-case --nsis --index --levels="0:24, 1:23, 2:22, 3:21, 4:20, 5:19, 6:18" --overview-levels="7:17, 8:16, 9:15, 10:14, 11:13, 12:12" --add-pois-to-areas --pois-to-areas-placement=entrance=main;entrance=yes;building=entrance;barrier=entrance --simplify-lines=23:2.6,22:4.2,21:5.4,20:6,19:7,18:7.5,17:4.5,16:5,15:5,14:6 --simplify-polygons=23:3.6,22:7,21:6,20:9,17:5.4 --add-boundary-nodes-at-admin-boundaries=2 --cycle-map --ignore-fixme-values --housenumbers --road-name-config=C:\openmtbmap\openmtbmap_svn\roadNameConfig.txt --split-name-index --link-pois-to-ways --ignore-turn-restrictions --polygon-size-limits="24:12, 23:14, 22:14, 21:20, 20:20, 19:20, 18:20, 17:20, 16:20, 15:20, 14:20, 13:25" --description=omtb_eu --show-profiles=1 --location-autofill=bounds,is_in,nearest --bounds=E:\OpenMTBMap\osmpbf_geofabrik\bounds.zip --route --country-abbr=eu --country-name=europe --mapname=65500000 --family-id=6550 --product-id=1 --series-name=omtb_europe_29.11.2021_UC_LOCAL --family-name=mtb_eu_29.11.2021_UC_LOCAL --tdbfile --x-gmapi-minimal --overview-mapname=mapsetc --keep-going --area-name="europe_29.11.2021_UC_LOCAL_omtb" -c D:\openmtbmap\maps\template.europe E:\OpenMTBMap\contourlines20\europe\7*.img typeu.TYP 1>NUL Number of MapFailedExceptions: 0 gmapi-minimal: Writing freshly compiled file C:\openmtbmap\maps\.\65500000.img gmapi-minimal: Writing freshly compiled file C:\openmtbmap\maps\.\65500001.img gmapi-minimal: Writing freshly compiled file C:\openmtbmap\maps\.\65500002.img gmapi-minimal: Writing freshly compiled file C:\openmtbmap\maps\.\65500003.img gmapi-minimal: Writing freshly compiled file C:\openmtbmap\maps\.\65500004.img ................ skipped ..................... long list of contourline files: ......... gmapi-minimal: Skipping file E:\OpenMTBMap\contourlines20\europe\75500447.img WARNING (global): Input file E:\OpenMTBMap\contourlines20\europe\75500448.img has different code page 1252 WARNING (global): Input file E:\OpenMTBMap\contourlines20\europe\75500448.img has different charset type 10 WARNING (global): Input files have different code pages gmapi-minimal: Skipping file E:\OpenMTBMap\contourlines20\europe\75500448.img .... 448 is the highest number contourlines file *............And here comes the error* it happens on writing the address index mdr file - mapset.img and mapset.tdb have already been created. Exception in thread "main" java.lang.IllegalArgumentException at java.base/sun.nio.ch.FileChannelImpl.position(FileChannelImpl.java:355) at uk.me.parabola.imgfmt.sys.ImgFS.sync(ImgFS.java:249) at uk.me.parabola.imgfmt.sys.ImgFS.close(ImgFS.java:325) at uk.me.parabola.mkgmap.combiners.MdrBuilder.onFinish(MdrBuilder.java:334) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:690) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126) at uk.me.parabola.mkgmap.main.Main.mainStart(Main.java:147) at uk.me.parabola.mkgmap.main.Main.main(Main.java:118) -- Felix Hartman - Openmtbmap.org & VeloMap.org

3 25

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 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

Commit r4819: relationlabel.patch by Mike Baggaley:
by svn commit 29 Nov '21

29 Nov '21

Version mkgmap-r4819 was committed by gerd on Mon, 29 Nov 2021 relationlabel.patch by Mike Baggaley: "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." http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4819

1 0

Small problem with global index
by Gerd Petermann 28 Nov '21

28 Nov '21

Hi Ticker, while experimenting with the index and unicode I found a rather simple case that doesn't work as expected. I've attached a small example file and a patch for the default style. A map produced with these options and the patched style --style-file=d:\mkgmap\resources\styles\default --lower-case --preserve-element-order --code-page=1252 --gmapi --index --housenumbers --bounds=bounds.zip bad-search.osm produces a map that shows an error in the POI search. I search for name=abc123x in region Bayern and get the correct result list of three different restaurants named abc123x. I search for name=abc123x in region reg1 and get the correct result list of three different restaurants named abc123x. Now I also fill the search field city with Burgpreppach. with name=abc123x in city Burgpreppach and region Bayern the result is still correct. with name=abc123x in city Burgpreppach and region reg1 the result is not correct, it also lists the objects in region Bayern So far I found no correction for this. It also doesn't seem to depend on the lower-case option. Any idea? Gerd

3 30