February 2018 - mkgmap-dev - The mkgmap lists

Error in style file relations?
by Gerd Petermann 03 Feb '18

03 Feb '18

Hi all, the default style contains this: # European E-Road network route=road & network=e-road { apply { add ref='${ref}'; add int_ref='${int_ref}'; add network='e-road' add mkgmap:fast_road=yes; } } If I got that right there should be a semicolon after add network='e-road' Or is this a very special syntax? Gerd

4 10

MapSource also sometimes crashes with DEM data produced by BuildDEMFile
by Gerd Petermann 03 Feb '18

03 Feb '18

Hi all, not sure what that means but I am also able to reproduce the problem when I create the DEM data with Franks program BuildDEMFile using my modified hgt file containing some voids. The voids are far from the route that causes the crash, somewhere around N52.24588 E10.50330. I've uploaded a new test set here: http://files.mkgmap.org.uk/download/412/baddem6b.7z I hope Frank has an idea where to fix this. ciao, Gerd

1 0

args input-file path issue
by nwillink 03 Feb '18

03 Feb '18

Hi Gerd Have come across this problem with input-file path names when creating and args file: It seems to be due to the spaces in feb 1 2018 The following creates errors: input-file:F:\mp5\backup\feb 1 2018\args\40526979.osm.pbf This doesn't work either (using quotes) input-file:"F:\mp5\backup\feb 1 2018\args\40526979.osm.pbf" nor (using shortpaths for the whole filename) input-file:F:\mp5\backup\FEB120~1\405269~2.PBF This does works: input-file:F:\mp5\backup\FEB120~1\40526979.osm.pbf r Nick -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

3 2

Commit r4101: pass original bounding polygon to HGTConverter
by svn commit 03 Feb '18

03 Feb '18

Version mkgmap-r4101 was committed by gerd on Fri, 02 Feb 2018 pass original bounding polygon to HGTConverter This reduce problems with --dem-polygon but doesn't solve them all. It seems that we always run into problems when the hasExtra flag is set http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4101

3 7

Why is mkgmap the option --country-name=name
by Eugeny_B 03 Feb '18

03 Feb '18

Why is mkgmap the option --country-name=name and --country-abbr=abbreviation, that it can not take the country name from --bounds=directory|zipfile with -code-page=number and -name-tag-list? -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

3 6

Problem with an empty CodePage key in TYP.txt
by Bernd Weigelt 02 Feb '18

02 Feb '18

Hello TYPwiz creates an empty key 'CodePage=' in my styles_typ.txt every time i had changed this file, this leads to an error message at the end of the build process. I don't know if this line is needed, but i can't see any problem, when i comment this key out, made it for very much builds. Should this problem fixed in MKGMAP or better in TYPwiz? Bernd ;generated by TYPWiz 5,82 ;created : 02-01-2018 ;------------------------------ [_id] ProductCode=46 FID=5 ;Header=5B CodePage= [end] II: building basemap Time started: Fri Feb 02 16:58:17 CET 2018 java.lang.ArrayIndexOutOfBoundsException: 1 at uk.me.parabola.mkgmap.main.TypCompiler $CharsetProbe.tryCharset(TypCompiler.java:252) at uk.me.parabola.mkgmap.main.TypCompiler $CharsetProbe.probeCharset(TypCompiler.java:222) at uk.me.parabola.mkgmap.main.TypCompiler$CharsetProbe.access $000(TypCompiler.java:205) at uk.me.parabola.mkgmap.main.TypCompiler.makeMap(TypCompiler.java:67) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:263) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:259) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: 1149) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Number of MapFailedExceptions: 0 Number of ExitExceptions: 0 Time finished: Fri Feb 02 17:01:42 CET 2018 Total time taken: 205566ms

3 2

Commit r4102: code refactoring, no functional change
by svn commit 02 Feb '18

02 Feb '18

Version mkgmap-r4102 was committed by gerd on Fri, 02 Feb 2018 code refactoring, no functional change http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4102

1 0

Remove option dem-polygon ?
by Gerd Petermann 02 Feb '18

02 Feb '18

Hi all, I did not get much feedback on this thread [1], maybe because I wrote -dem-profile instead of dem-polygon in the subject? It seems that MapSource simply cannot handle routes on maps created with that option. Basecamp is more robust but also shows problems as I stated in the first post. Does anybody use this option for a routable map and is able to produce height profiles for routes crossing tile borders in Mapsource? If yes there may be hope... Gerd [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q1/027970.html

4 4

Re: [mkgmap-dev] Style Manual
by Gerd Petermann 02 Feb '18

02 Feb '18

Mike, Henning, thanks for the comments, please check my changes in http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4098 and http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4099 I hope this is okay now? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Henning Scholland <osm(a)hscholland.de> Gesendet: Donnerstag, 1. Februar 2018 12:29 An: mkgmap-dev(a)lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Style Manual Hi Gerd, regarding tagisincomplete I would suggest to get rid of it. I can't imagine any use of it. For 2nd tagg it seems to be somehow useful. Maybe document it like ' Don't use in relation-style, is set to indicate line/poygon is part of MP-relation'. The usage in relation-styles should be checked during check-style. Henning On 01.02.2018 18:22, Gerd Petermann wrote: > Hi all, > > to be honest, I don't fully understand what mkgmap:tagsincomplete is about. > The tag is set by the OSM readers when a type=multipolygon or type=boundary relation has a tag that is NOT evaluated by the style, > this is probably the case for many of those relations. The effect is that a mp relation with a normal tag like name=* is treated the same as > one with exotic:unused:nonsense=*. The only case where this seems to matter is when a relation has only the type=mulitpolygon tag. > > See this svn log message: http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=2366 > The tag is evaluated before any style processing happens and I think it makes no sense to evaluate or change it in style rules. > > reg: mkgmap:stylefilter: > The tag is set in the MultipolygonRelation code. It is used to decide whether the rules in lines or in polygons should be used. > Without the tag it is likely that both are combined (rules in lines before those in polygons). > You should not see this tag in the relations style, only in lines or polygons, as long as you don't set it in the relations > rules. Doing this might cause trouble. > Maybe it makes sense to evaluate this tag in the lines rules, something like > # filter highways which are parts of multipolygon relations > highway=* & mkgmap:stylefilter=lines {...} > > tl;dr: > I can document these tags as e.g. "please don't set or change" > or I can try to get rid of them. What do you think? > > Gerd > ________________________________________ > Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen(a)hotmail.com> > Gesendet: Mittwoch, 31. Januar 2018 21:22 > An: Mike Baggaley; 'Development list for mkgmap' > Betreff: Re: [mkgmap-dev] Style Manual > > Hi Mike, > > I'd rather change the code so that you don't see those tags. They are for internal use only. > > Gerd > > ________________________________________ > Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von Mike Baggaley <mike(a)tvage.co.uk> > Gesendet: Mittwoch, 31. Januar 2018 20:20 > An: 'Development list for mkgmap' > Betreff: [mkgmap-dev] Style Manual > > I notice the style manual has no mention of mkgmap:stylefilter or > mkgmap:tagsincomplete in it. I see these in the output of the echotags > command when handling a relation. Can they be added to the documentation? > > Cheers, > Mike > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

2 1

Commit r4100: add missing semicolon in relations style
by svn commit 01 Feb '18

01 Feb '18

Version mkgmap-r4100 was committed by gerd on Thu, 01 Feb 2018 add missing semicolon in relations style No change in ouput expected, the error was "repaired" with a rule in the lines file. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4100

1 0