February 2018 - mkgmap-dev - The mkgmap lists

Commit r4124: slightly modified maxjobs-v6.patch by Mike Baggaley
by svn commit 19 Feb '18

19 Feb '18

Version mkgmap-r4124 was committed by gerd on Mon, 19 Feb 2018 slightly modified maxjobs-v6.patch by Mike Baggaley -- if max-jobs option is not set, try to find a reasonable value -- further improve documentation of options -- report run time in hours, minutes and seconds instead of ms http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4124

3 2

Commit r4125: avoid division by zero
by svn commit 19 Feb '18

19 Feb '18

Version mkgmap-r4125 was committed by gerd on Mon, 19 Feb 2018 avoid division by zero http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4125

1 0

work in progress: new option dem-shrink-factors
by Gerd Petermann 19 Feb '18

19 Feb '18

Hi all, Frank Stinner found more about the meaning of the byte in DEM header at offset 0x12 of the zoom level header. This value gives a shrink factor that is used to minimize the deltas. All height delta values are divided by this factor, so that e.g. with a factor of 5 the values 12,19,20,10 become 2,4,4,2 before they are encoded. This reduces the number of bytes but also reduces precision. Garmin uses it in many maps, of with increasing value for each map level. I've started to implement this in DemDisplay but it seems that there is something else to change. Gerd

1 0

parameter for --transparent option
by Gerd Petermann 19 Feb '18

19 Feb '18

Hi all, I have no idea how to solve the problem with crashes in MapSource when --route is used with --transparent and --dem . Maybe there is another flag that has to be changed, maybe it is not supported by Garmin. So, the best work around seems to be using transparent background polygons (0x4b) in combination with new option --transparent=semi and a TYP file that makes 0x4b transparent. Attached is a patch that implements new options like this, please suggest improvements for the documentation, else I'll use the same description for the doc as well. --transparent=full|semi Make the map transparent, so that if two maps covering the same area are loaded, you can see through this map to see details from the other map too. Typically used for maps containing just contour lines. See --draw-priority as well. Note that the combination of options --transparent and --route often cause problems in MapSource and Basecamp, e.g. routing may not work well or MapSource may crash when pressing the "Show profile..." button. If not given mkgmap writes background polygons (type 0x4b) and doesn't set transparent flag in the TRE header. If parameter full is used or no parameter is given mkgmap does not write the background polygons and sets the transparent flag. If parameter semi is used mkgmap writes background polygons and sets the transparent flag. A type file is needded that sets the 0x4b polygon to transparent. This allows good routing in MapSource and Basecamp but still may cause crashes in MapSource. Gerd

1 0

Re: [mkgmap-dev] max-jobs patch
by Mike Baggaley 19 Feb '18

19 Feb '18

Hi Gerd, I misread the --max-jobs with no value functionality. Please find attached a revised patch that does function that way when the max-jobs option is specified with no value. Cheers, Mike -----Original Message----- From: Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] Sent: 16 February 2018 10:42 To: Mike Baggaley <mike(a)tvage.co.uk> Subject: AW: [mkgmap-dev] max-jobs patch Hi Mike, without the patch the option --max-jos means: use as many threads as cores. Since mkgmap is normally very silent I would not print an information that just confirms that anything is normal. My personal preference would be to print much more information about performance, but my understanding is that the mkgmap users are happy with the silent behaviour. BTW: I'd also print a message that tells the user how to activate logging if it is not already activated. Gerd ________________________________________ Von: Mike Baggaley <mike(a)tvage.co.uk> Gesendet: Freitag, 16. Februar 2018 11:20:03 An: 'Gerd Petermann' Betreff: RE: [mkgmap-dev] max-jobs patch Hi Gerd, as the functionality of --max-jobs without a value is the same as not specifying the parameter (i.e. it is the default), it seems to me to be better for them to function the same. If you have specified --max-jobs without a value, why would you not want to know how many threads had been assigned? Regards, Mike -----Original Message----- From: Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] Sent: 15 February 2018 08:54 To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] max-jobs patch Hi Mike, looks good to me. I am just not sure about the new stdout message "Setting max-jobs to 4" It appears when --max-jobs is not used (ok), but also when it is used without a parameter. In the latter case I would only print this message if the number of CPU cores is higher. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen(a)hotmail.com> Gesendet: Mittwoch, 14. Februar 2018 19:38:06 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] max-jobs patch Hi Mike, okay, I'll try it tomorrow. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Mike Baggaley <mike(a)tvage.co.uk> Gesendet: Mittwoch, 14. Februar 2018 18:30:28 An: 'Steve Ratcliffe'; mkgmap-dev(a)lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] max-jobs patch I tried renaming the java library to force a failure and got a java error "Error occurred during initialization of VM" before any mkgmap code was executed, so to be on the safe side, I have removed that code and amended the message in the attached patch. Regards, Mike -----Original Message----- From: Steve Ratcliffe [mailto:steve@parabola.me.uk] Sent: 13 February 2018 23:01 To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] max-jobs patch Hi Mike > I could take out that bit of code, which is just determining how > much physical memory is installed, so that mkgmap won't suggest that the > user increases the available heap too much. It isn't used in determining a > value for maxjobs. Since it is just used for an informational message, you could just surround it with a try/catch block. Then if it doesn't exist on a particular it isn't a problem when using the downloaded pre-compiled distribution. Of course it would fail to compile on such a platform, but then hopefully someone will let us know and we can decide what to do then. Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

2 2

--route and --transparent
by Gerd Petermann 16 Feb '18

16 Feb '18

Hi all, as pointed out here [1] those two options should not be used together. I first thought that mkgmap should simply stop when this combination is used, but maybe this will cause problems for those who use a standard options file containing the "route" option and use that also to create transparent maps with contour lines? I think those maps will have almost empty NET and NOD files, but probably they work well? So, maybe mkgmap should only stop when NOD really contains data and the transparent flag is set? Gerd [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q1/028169.html

6 13

Re: [mkgmap-dev] Need help with string handling in mkgmap
by Manfred Haiduk 16 Feb '18

16 Feb '18

Hi all after playing a little bit with the syntax of "conf" and "subst" i finally found a solution, which suits for my needs : power=generator & generator:source=wind { name '${manufacturer} (${ref},${height|subst:"m=>"} m)' | '${manufacturer} (${ref})' | '${manufacturer} (${height|subst:"m=>"} m)' | '${manufacturer}' | '${ref}' | '${height|subst:"m=>"} m' } [0x5912 level 2] A sentence like this works for me, thanks for your hints Am 15.02.2018 um 19:44 schrieb Gerd Petermann: > Hi Manfred, > > your rules work, but only when a lower case m is used in the OSM data. > Can't say much more because you did not post the rules which use the > tags mkgmap:ele or mkgmap:height. > > Gerd > > > ________________________________________ > Von: Manfred Haiduk <mhaiduk(a)t-online.de> > Gesendet: Donnerstag, 15. Februar 2018 18:40:54 > An: Gerd Petermann; Development list for mkgmap > Betreff: Re: [mkgmap-dev] Need help with string handling in mkgmap > > If you look at my screenshot, you will see the left power turbines will > be shown as "Senvion (153 Mm)" whilst the right power turbines will be > shown as "Senvion (143m)". So it seems to me, that there is no really > guide line how to put in the value of height or elevation in the osm > map. And i simply want to get rid of the letter "M", to have shown all > values in the same way. And i thought as it was suggested in the style > manual on page 15, use the substitution filter "subst" to delete the > letter "m", which is a part of the value for height or elevation. From > the manual i was not sure of the correct syntax ... > > I will use your other hint with the conv filter and see, what will be > the result from this. > > > Am 15.02.2018 um 15:30 schrieb Gerd Petermann: >> Hi Manfred, >> >> I've just noticed that you set tags mkgmap:height and mkgmap:ele . >> This looks strange. They are not used in mkgmap and therefore I think you >> should not use the mkgmap: prefix. >> Or maybe you expect something special by using this prefix? >> >> Gerd >> >> ________________________________________ >> Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Manfred Haiduk <mhaiduk(a)t-online.de> >> Gesendet: Donnerstag, 15. Februar 2018 15:01:21 >> An: mkgmap-dev(a)lists.mkgmap.org.uk >> Betreff: [mkgmap-dev] Need help with string handling in mkgmap >> >> Hi, i'm struggling with the following problem and until now, i didn't >> find a solution. It seems, that in osm sometimes the height or elevation >> tag is filled with the unit sign, i.e 'm' and sometimes not. So with my >> current point file i either get elevation without the unit letter or >> with double unit letter - i.e 'Mm'. How to handle this ? >> >> I tried with this >> >> height=* { set mkgmap:height='${height|subst:"m=>"}'} >> ele=* { set mkgmap:ele='${ele|subst:"m=>"}'} >> >> but it doesn't work >> >> -- >> >> Mit freundlichen Grüßen >> >> ##################################################### >> Manfred Haiduk, >> Zum Fischbach 9, >> 52393 Hürtgenwald >> e-mail mhaiduk(a)t-online.de >> ##################################################### >> >> _______________________________________________ >> mkgmap-dev mailing list >> mkgmap-dev(a)lists.mkgmap.org.uk >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >> > -- > > Mit freundlichen Grüßen > > ##################################################### > Manfred Haiduk, > Zum Fischbach 9, > 52393 Hürtgenwald > e-mail mhaiduk(a)t-online.de > ##################################################### > > -- Mit freundlichen Grüßen ##################################################### Manfred Haiduk, Zum Fischbach 9, 52393 Hürtgenwald e-mail mhaiduk(a)t-online.de #####################################################

1 0

Need help with string handling in mkgmap
by Manfred Haiduk 15 Feb '18

15 Feb '18

Hi, i'm struggling with the following problem and until now, i didn't find a solution. It seems, that in osm sometimes the height or elevation tag is filled with the unit sign, i.e 'm' and sometimes not. So with my current point file i either get elevation without the unit letter or with double unit letter - i.e 'Mm'. How to handle this ? I tried with this height=* { set mkgmap:height='${height|subst:"m=>"}'} ele=* { set mkgmap:ele='${ele|subst:"m=>"}'} but it doesn't work -- Mit freundlichen Grüßen ##################################################### Manfred Haiduk, Zum Fischbach 9, 52393 Hürtgenwald e-mail mhaiduk(a)t-online.de #####################################################

3 4

Creating a map with contour lines and DEM
by Bernhard Hiller 15 Feb '18

15 Feb '18

I was trying to create a map of Taiwan including DEM data and elevation contour lines. The DEM part was easy. But strangely, I cannot get elevation contourlines. I downloaded hgt data from Viewfinder Panoramas, and placed them into the cache directory of srtm2osm. I called srtm2osm in a batch file: SET SRTM="C:\Program Files (x86)\OpenStreetMap\Srtm2Osm\Srtm2Osm.exe" SET OUTPUTDIR=E:\Maps\Raw\Taiwan.DEM\ %SRTM% -bounds1 21.81 120 23.6 122.1 -o %OUTPUTDIR%TaiwanS.osm %SRTM% -bounds1 23.59 120 25.4 122.1 -o %OUTPUTDIR%TaiwanN.osm TaiwanS mearures 1554993 kB, TaiwanN 2249418 kB (I must do it in 2 parts, otherwise the program uses more than 7 GB of RAM and causes lots of paging). Next, I sorted one of the files with osmosis (originally I sorted and merged both of them, and then merged with an extract from Geofabrik; that's what I plan to do when I got things working...): SET OSMOSIS="C:\Program Files (x86)\OpenStreetMap\osmosis-0.46\bin\osmosis.bat" SET INPUTDIR=E:\Maps\Raw\Taiwan.DEM\ %OSMOSIS% --read-xml %INPUTDIR%TaiwanS.osm --sort --write-pbf %INPUTDIR%Taiwan_Ele.osm.pbf The output file measures 16670 kB. Next, I split it with SET JAVA="C:\Program Files\Java\jre1.8.0_121\bin\java.exe" SET SPLITTER="C:\Program Files (x86)\OpenStreetMap\splitter-r590\splitter.jar" SET INPUTDIR=E:\Maps\Raw\Taiwan.DEM\ SET INPUTDATA=Taiwan_Ele.osm.pbf SET NAME="BernieMap Bike Taiwan" %JAVA% -Xmx6G -jar %SPLITTER% ^ %INPUTDIR%\%INPUTDATA% ^ --description=%NAME% ^ --max-nodes=2500000 ^ --no-trim ^ --mapid=47120001 ^ --max-threads=4 ^ --keep-complete=true which creates 3 pbf-files. Finally, I build the map with SET JAVA="C:\Program Files\Java\jre1.8.0_121\bin\java.exe" SET MKGMAP="C:\Program Files (x86)\OpenStreetMap\mkgmap-r4107\mkgmap.jar" SET PREPROC=E:\Data\Projects\Projects.Net2\StylePreProcessor\bin\Debug\StylePreProcessor.exe SET STYLE=E:\Maps\Development\Style.Mapnik\Mapnik.Bike SET DEMPATH=E:\Maps\Raw\Taiwan.DEM SET NAME="BernieMap Bike Taiwan" SET TYP=M04712.TYP %PREPROC% /in=E:\Maps\Development\Style.Mapnik\Mapnik.Base /out=%STYLE% /defines=BIKE,THAI copy E:\Maps\Development\Style.Mapnik\%TYP% %TYP% copy "C:\Program Files (x86)\OpenStreetMap\GMT\gmt.exe" gmt.exe gmt.exe -wy 4712 %TYP% %JAVA% -Xmx6G -ea -jar %MKGMAP% ^ --style-file=%STYLE% ^ --family-name=BernieMapTaiwan ^ --family-id=04712 ^ --product-id=1 ^ --description=%NAME% ^ --series-name=%NAME% ^ --name-tag-list=name:en,int_name,name ^ --latin1 ^ --add-pois-to-areas ^ --route ^ --location-autofill=bounds,nearest ^ --preserve-element-order ^ --draw-priority=25 ^ --index ^ --nsis ^ --show-profiles=1 ^ --generate-sea=multipolygon,extend-sea-sectors,floodblocker ^ --max-jobs=4 ^ --dem-poly=areas.poly ^ --x-dem=%DEMPATH% ^ --x-dem-dists=3314,4000,6000,8000,10000,15000,20000,30000 ^ --gmapsupp 4*.osm.pbf ^ %TYP% move gmapsupp.img E:\Maps\Use\Taiwan.IMG which creates an IMG file of 18798 kB. It is recognized by my Oregon 600. In the demo mode, I navigate to a waypoint (Luigui, 22.99573 N, 120.63496 E). I expect to see a map of contourlines only. But I get a completely white map. Elevation from DEM is 250m directly adjacent to the waypoint, and other sensible values nearby. The style file contains: contour=elevation & contour_ext=elevation_major & (ele > 0 | ele < 0) { name '${ele|conv:m=>ft}'; } [0x20 level 4] contour=elevation & contour_ext=elevation_medium & (ele > 0 | ele < 0) { name '${ele|conv:m=>ft}'; } [0x21 level 2] contour=elevation & contour_ext=elevation_minor & (ele > 0 | ele < 0) { name '${ele|conv:m=>ft}'; } [0x22 level 0] The TYP file (created and compiled with MapTk) contains: [Polyline] Type=0x20 String=0,Höhenlinie String=4,Elevation Color=0,0x000000 Line=00..00 [END] [Polyline] Type=0x21 String=0,Höhenlinie String=4,Elevation Linewidth=1 Color=0,0x000000 [END] [Polyline] Type=0x22 String=0,Höhenlinie String=4,Elevation Linewidth=2 Color=0,0x000000 [END] which should cause black elevation contour lines. What do I do wrong? Thanks a lot for your hints. Kind regards, Bernhard

4 4

Commit r4123: DEM: add checks for tiles at 180 degrees
by svn commit 15 Feb '18

15 Feb '18

Version mkgmap-r4123 was committed by gerd on Thu, 15 Feb 2018 DEM: add checks for tiles at 180 degrees Old code crashed when creating DEM for tile with eastern border at 180 degrees. No problems at -180 degrees. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4123

1 0