July 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

signed maps / new device
by Marek Greško 04 Aug '21

04 Aug '21

Hello, my Colorado just broke (the Rock and Roller). I got offer from Garmin to replace the device by Oregon 700 or GPSmap65. Is it possible to use gpsmap compiled maps in any of these device? Or only Garmin signed maps are available for it? Thanks Marek

6 13

Echange .typ-file in gmapsupp.img on Mac OS x 11 or newer?
by Felix Hartmann 27 Jul '21

27 Jul '21

Hi - is there any tool available to change the .typ-file in a gmapsupp.img on the Mac OS X Big Sur or newer? As gmt_osx is not gonna be updated to x64 - I wonder if there is an alternative. Or maybe could this function be added to mkgmap? I would imagine a call java mkgmap.jar --change-typ gmapsupp.img newtyp.typ (so remove all existing .typfiles in the gmapsupp.img and replace them with newtyp.typ - for gmapsupp.img consisting of several maps this would be more complicated - I do not feel that is needed). Plus maybe the option to join several gmapsupp.img files into a new bigger one (only important for very old devices). -- Felix Hartman - Openmtbmap.org & VeloMap.org

4 12

What is this error actually telling me.
by Randolph J. Herber 24 Jul '21

24 Jul '21

SEVERE (global): The RGN section of the map or tile is too big. The maximum size is 16777215 bytes. Try splitting the map into smaller tiles or reducing the amount of information included in the map. With last year's versions, this worked. What is the fix? I osmosis combined the pbf files from geofabrik.de for north, central, and south America using osmosis, which appeared to have worked without problems. The pbfs were down loaded in the last two weeks. There were some roundabout errors from splitter. I get the error message above from mkgmap. E:\OSMMaps>type combineAmericas.bat files\osmosis\bin\osmosis.bat ^ --read-pbf data\central-america-latest.osm.pbf ^ --read-pbf data\south-america-latest.osm.pbf ^ --merge ^ --read-pbf data\north-america-latest.osm.pbf ^ --merge ^ --write-pbf data\americas.osm.pbf E:\OSMMaps>type splitterAmericasUC.bat java -Xmx6G -jar files\splitter\splitter.jar ^ --description="AmericasUC" ^ --geonames-file=files\cities1000.zip ^ --keep-complete=true ^ --mapid=99970001 ^ --max-areas=9999 ^ --max-nodes=1000000 ^ --max-threads=7 ^ --output=pbf ^ --output-dir=AmericasUC ^ --precomp-sea=files\sea.zip ^ --resolution=13 ^ --status-freq=30 ^ --wanted-admin-level=10 ^ --write-kml=AmericasUC\split.kml ^ data\americas.osm.pbf E:\OSMMaps>type mkgmapAmericasUC.bat java -Xmx6G -jar files\mkgmap\mkgmap.jar ^ --output-dir="AmericasUC"\map ^ --nsis ^ --tdbfile ^ --overview-mapname=99970000 ^ --mapname=99970001 ^ --family-id=9997 ^ --description="AmericasUC" ^ --series-name="AmericasUC" ^ --family-name="AmericasUC" ^ --gmapi ^ --gmapsupp ^ --draw-priority=1 ^ --latin1 ^ --index ^ --housenumbers ^ --bounds=files\bounds.zip ^ --precomp-sea=files\sea.zip ^ --location-autofill=is_in,nearest ^ --name-tag-list=name:en,int_name,name ^ --add-pois-to-lines ^ --add-pois-to-areas ^ --pois-to-areas-placement ^ --preserve-element-order ^ --road-name-pois ^ --remove-ovm-work-files ^ --route ^ --remove-short-arcs ^ --adjust-turn-headings ^ --process-destination ^ --process-exits ^ --reduce-point-density=3 ^ --reduce-point-density-polygon=4 ^ --merge-lines ^ --drive-on=detect,right ^ --report-roundabout-issues ^ --max-jobs=7 ^ --verbose ^ --order-by-decreasing-area ^ --style-file=style2 ^ --check-styles ^ -c AmericasUC\template.args ^ typ\Symbols.typ E:\OSMMaps>

2 3

Re: [mkgmap-dev] Change in Garmin IMG format?
by Craig Durkin 19 Jul '21

19 Jul '21

Has anyone had to make changes to their TYP file to make things look better with the high-contrast map? I make maps where I draw a bunch of red lines on roads, they appear very muted and gray in the high-contrast map. Thanks, Craig

2 3

Re: [mkgmap-dev] Change in Garmin IMG format?
by ET Commands 13 Jul '21

13 Jul '21

The issue exists for me on my Edge 1030 even in classic mode, and with the popularity layer turned off. I checked it twice to be sure. I am going to revert to the previous firmware version so I can get my custom symbology back. Mark > Date: Tue, 13 Jul 2021 09:50:40 +0100 > From: nick <osm(a)pinns.co.uk> > To: mkgmap-dev(a)lists.mkgmap.org.uk > Subject: Re: [mkgmap-dev] Change in Garmin IMG format? > Message-ID: <d1c9e3cd-e20d-0961-7388-95a14dec8581(a)pinns.co.uk> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > That is very interesting and somewhat disturbing. There is one unknown > byte (at 0x65) in a typ file's header which might be worth investigating > . The header is higher than mkgmap's? 0x5B? with values ranging between > 0 and 1F.(In TYPWiz6 you can change this in Settings,Advanced,Region) > > Topo Austria has 0x0e and Topo Italia 0x0F > > However,this may have nothing to do with the issue. > > On 13/07/2021 07:30, Felix Hartmann wrote: >> No they haven't changed the img format, what they did is that for >> years they designed the maps in layout for desktop size displays, and >> finally discovered maps should be much higher contrast on small >> displays. So they introduced (already sind 2-3 years) a high contrast >> layout that is more and more independent of the .typ-file layout. >> Since the newest update this is even more?noticeable. >> >> It can be deactivated by selecting classic map design or similar. >> While high contrast or mountainbike or whatever will use the new layout. >> >> On Tue, 13 Jul 2021 at 04:44, ET Commands <etcommands(a)gmail.com >> <mailto:etcommands@gmail.com>> wrote: >> >> I'm not sure if my message is relevant to this discussion list or not. >> >> I own an Edge 1030 and I use mkgmap to make custom maps for it. >> Recently >> Garmin provided a firmware update for the 1030 (ver. 12.0). After I >> installed it none of my custom POI symbols appear on the map. In >> addition, the default Garmin POI symbols have been updated by Garmin. >> All my custom line and polygon symbols still display.? I saw comments >> from some users in the Garmin forums that TOPO maps will no longer >> work >> with the firmware update either. >> >> It appears Garmin may have revised the format of their IMG files, if >> only slightly.? I don't know if this affects all Garmin models or >> only >> certain ones. >> >> >> Mark >> >> _______________________________________________ >> mkgmap-dev mailing list >> mkgmap-dev(a)lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> >> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >> <https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev> >> >> >> >> -- >> Felix Hartman - Openmtbmap.org & VeloMap.org >> >> >> _______________________________________________ >> mkgmap-dev mailing list >> mkgmap-dev(a)lists.mkgmap.org.uk >> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >

1 0

Change in Garmin IMG format?
by ET Commands 13 Jul '21

13 Jul '21

I'm not sure if my message is relevant to this discussion list or not. I own an Edge 1030 and I use mkgmap to make custom maps for it. Recently Garmin provided a firmware update for the 1030 (ver. 12.0). After I installed it none of my custom POI symbols appear on the map. In addition, the default Garmin POI symbols have been updated by Garmin. All my custom line and polygon symbols still display. I saw comments from some users in the Garmin forums that TOPO maps will no longer work with the firmware update either. It appears Garmin may have revised the format of their IMG files, if only slightly. I don't know if this affects all Garmin models or only certain ones. Mark

3 2

faster-mp r4797 and a question on style for amenity=emergency_phone
by 7770 11 Jul '21

11 Jul '21

Hi. One observation with faster-mp-r4797. After running, it leaves a directory called e: with subdirectires such as: ld/H121664384_29910 ld/V-3407872_1992959 It's ok i presume, these correlate to SEVERE message that are created during processing: (ShapeSplitter): 77800027.osm.pbf: Horizontal split 121664384 failed on shape at 40.777236,0.641794 Possibly a self-intersecting polygon Second, a question. In the style for points there is a line for emergacy phone (and later phone). amenity=emergency_phone [0x2f12 resolution 24 default_name 'Emergency Phone'] I have added a specific image in the TYP file, which compiles well, but nothing seems to show on the map (even checked with qmapshack). Is there something specific to this tag or this number 0x2f12 that supresses it from being displayed? Regards Karl

3 3

Commit r4802: lower severity level for ShapeSplitter "split failed" message
by svn commit 08 Jul '21

08 Jul '21

Version mkgmap-r4802 was committed by gerd on Thu, 08 Jul 2021 lower severity level for ShapeSplitter "split failed" message http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4802

1 0

Misplaced boundary POI
by dfjkman＠gmail.com 08 Jul '21

08 Jul '21

Hi Gerd, The other day I noticed that the country name along the boundary between Zambia and Zimbabwe was misplaced in 2 regions, see the attached images. The name also switches at different detail levels in BaseCamp, at Medium and High it shows Zimbabwe north of the border and at Higher and Highest it shows Zambia. The POI to the east would appear to have both Zambia and Zimbabwe assigned to it while to the west, near Livingstone, would appear to be 2 separate POIs. I have created a map with only the boundaries to show this clearly as it is missed when the map has more detail in it. The map was created from zambia-latest.osm.pbf from Geofabrik and split using Splitter version 615 with the following options: java -jar -Xmx2g C:\Users\Dave\Documents\Maps\Utils\splitter\splitter.jar --output=pbf --resolution=13 --description="ZM_OSM Map" --wanted-admin-level=5 --mapid=2635 --max-nodes=2600000 The map was created with mkgmap-r4801, although I have noticed it with earlier versions. Options as follows: Java -jar -Xmx7g C:\Users\Dave\Documents\Maps\Utils\mkgmap\mkgmap.jar --keep-going --latin1 --add-pois-to-areas --gmapi --style-file='C:\Users\Dave\Documents\Maps\Styles\boundaries' -c C:\Users\Dave\Documents\Maps\Zambia\Split_Files\template.args In the basic boundary style I have the following files: Options levels = 0:24, 1:22, 2:20, 3:18 overview-levels = 4:17, 5:16, 6:15, 7:14, 8:13 Lines boundary=administrative & admin_level<3 [0x1e resolution 12] Points boundary = administrative & mkgmap:area2poi = true & admin_level = 2 [0x1400 resolution 16-20] <finalize> name = * {name '${name}'} This is not something that overly worries me but if it happens here it may happen elsewhere and be missed. I have not analysed my maps to see if it happens with other provincial or district boundaries. Kind regards, Dave

2 2