- mkgmap-dev - The mkgmap lists

Relation type=area
by demon.box 01 Mar '18

01 Mar '18

Hi, excuse me, I mapped some large steps-area with this proposed scheme https://wiki.openstreetmap.org/wiki/Relations/Proposed/Area like a relation with type=area and this is an example https://www.openstreetmap.org/relation/8013769 but with mkgmap I can not render it in any way.... What can I do? There is a way to render it like a simple polygon? Thanks very much. --enrico -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

4 8

Error building DEM map
by Carlos Dávila 28 Feb '18

28 Feb '18

I'm facing an error compiling Algeria map with DEM, using SRTM1 hgt files. In a first run I use splitter as follows: java -Xmx6G -jar splitter.jar --max-nodes=2000000 --geonames-file=geonames/cities15000_$ABR.zip --mapid=551${FID}001 --output=o5m algeria.o5m It gives 5 tiles and when I run mkgmap on them [1], it takes a very long time and finally it fails with "Number of MapFailedExceptions: 1" and a huge (+7GB) log file I could not read. I have manually split problematic tile to a half its original size and then both resulting tiles fail to compile. After dividing them /2, 3 of the 4 tiles fail, but then mkgmap gives the following error: Exception in thread "main" java.lang.NegativeArraySizeException at uk.me.parabola.mkgmap.reader.hgt.HGTConverter.<init>(HGTConverter.java:85) at uk.me.parabola.imgfmt.app.dem.DEMFile.calc(DEMFile.java:76) at uk.me.parabola.mkgmap.build.MapBuilder.makeMap(MapBuilder.java:341) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.writeOverviewMap(OverviewBuilder.java:191) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.onFinish(OverviewBuilder.java:104) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:679) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:128) at uk.me.parabola.mkgmap.main.Main.mainStart(Main.java:143) at uk.me.parabola.mkgmap.main.Main.main(Main.java:114) And log contains over 10⁷ lines like this: WARNING (HGTConverter): 55129161.o5m: height interpolation returns void at 30.837045,2.094557 After 2 more /2 divisions I could build all tiles. The smallest failing tile can be downloaded from http://alternativaslibres.org/tmp/55129083.o5m [1] java -Xmx4500m -ea -Dlog.config=logging.properties -jar mkgmap.jar --block-size=2048 --dem=hgt/VIEW1,hgt/SRTM1,hgt/EU-DEM,hgt/VIEW3,hgt --dem-poly=polygons/$pais.poly --dem-dists=3312,6624,9936,13248,26512 --overview-dem-dist=128000 --output-dir=./tmp --gmapi --show-profiles=1 --bounds=bounds.zip --precomp-sea=sea.zip --max-jobs --route --latin1 --code-page=1252 --country-name=$PAIS --country-abbr=$ABR --area-name=$MAPA --family-name="OSM $MAPA DEM" --family-id=5$FID --product-id=1 --product-version=$VERSION --series-name="OSM-$MAPA-DEM" --overview-mapname=$ABR-5$FID --overview-mapnumber=555${FID}000 --name-tag-list=$NAMETAG --index --process-destination --process-exits --housenumbers --reduce-point-density=4 --polygon-size-limits="24:12, 18:10, 16:0" --add-pois-to-areas --link-pois-to-ways --location-autofill=is_in,nearest --drive-on=detect,$DRIVEON --check-roundabouts --check-roundabout-flares --license-file=license_OSM_${HGT} --copyright-file=copyright $LANGUAGE --road-name-config=$CONFIG --x-mdr7-del=GRADE0,GRADE1,GRADE2,GRADE3,GRADE4,GRADE5,GRADE6,GRADE7,UNNAMED --style=mio --remove-ovm-work-files=true -c ${pais}-DEM.args

3 3

Found multiple points with equal coords
by Arndt Röhrig 27 Feb '18

27 Feb '18

2 2

line rule not being triggered
by Ticker Berkin 26 Feb '18

26 Feb '18

Hi I noticed that the default style was putting walkways around some piers because of the line rule: (man_made=pier | man_made=piste:halfpipe) & area!=yes {add highway=footway; name '${ref} ${name}' | '${ref}' | '${name}' } an example is: WAY: 469580183 (50.73379039764404/-1.2820744514465332) [man_made=pier, mkgmap:admin_level10=Whippingham, mkgmap:admin_level2=GBR, mkgmap:admin_level4=England, mkgmap:admin_level5=South East, mkgmap:admin_level6=Isle of Wight, name=Folly Pier] which is using a closed way to draw the pier (and also has a defined footpath along it) Earlier on in my lines file I have: # mark multipolygons as area mkgmap:mp_created=true {add area=yes} highway=* & area!=* & is_closed()=true {echotags 'closed() highway'; add area=yes} and so added the following to fix the problem: man_made=* & is_closed()=true {add area=yes; echotags 'mm'} but this rule isn't being triggered by my example, but if I replace it with: name="Folly Pier" & is_closed()=true {add area=yes; echotags 'fp'} Then it behaves as expected I'm using the latest svn trunk (4127) Any ideas? Thanks Ticker

5 6

Re: [mkgmap-dev] DEM test & artifacts
by David 25 Feb '18

25 Feb '18

Hello Gerd, Here is more information about how I obtained my result. I used mkgmap v4107 and splitter v590. My options for DEM are : dem=./MySrtm1Folder dem-dists=3312,13248,26512,53024,106048 dem-poly=./MyPolygon.poly dem-interpolation=auto overview-dem-dist=212096 I do not define any polygon option for splitter. As explained in my previous email, to avoid the generation of a shadow in plain ocean, I defined a new polygon inside the correct shadow rendering area and it solved my problem. For the artifacts I described, follow this link to see what I mean : http://emerald-island.eu/wikka/ShadowArtifacts It was made with mkgmap version 41067 and 4126 and splitter 590 with the same result. Again for your great work, chapeau bas, David

5 14

Commit r4129: correction: some rules with style functions were ignored
by svn commit 25 Feb '18

25 Feb '18

Version mkgmap-r4129 was committed by gerd on Sun, 25 Feb 2018 correction: some rules with style functions were ignored rules like a=* & is_closed()=true {...} were ignored because ExpressionArranger changed them to is_closed()=true & a=* {...} Style functions are not indexable and therefore must not come first. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4129

1 0

routing problems when style creates multiple routable ways for one OSM way
by Gerd Petermann 24 Feb '18

24 Feb '18

Hi all, in [1] Felix suggested to add a filter so that a style would not add too many routable ways for one OSM way. For those who are not familiar with that idea: Felix' style adds e.g. additional routable ways with other routing attributes when a way is very steep, e.g. one saying something like "nice to cycle" and the other with oneway=-1 and "not nice to cycle". The effect on NOD is that at some "RouteNodes" we find a lot more so called "RouteArcs", many of them with equal angles and lengths. Reg. the filter I see no problem to change mkgmap so that it detects the number of routable ways N which were added for one OSM way and if N > max_N (I think Felix says max_N is 4) ignore the last N - max_N ways. It might also be possible to add a style function which gives access to the number of previously added routable ways, if that is needed, but I see no need for that. I think the style rules could just add routable ways in order of importance. Right? Anyway, the question is if this will always help, as I think that the problem is probably the number of RouteArcs with equal angles in one RouteNode. Maybe we just have to make sure that we don't have exactly equal RouteArcs, maybe the overall number is the problem. The angles are stored with a rather poor resolution (max. 8 bits), but maybe we can manipulate the other attributes like length or curviness of an arc to avoid the crash. Maybe the problem is not the number of arcs in one RouteNode but the overall number of arcs that have to be checked when a route is calculated. @Felix: Maybe you have already found out more details? You wrote about "bsod", I know the meaning for Windows (Blue screen of Death), but what exactly happens with a device? Is it dangerous the play with this on my Oregon? What exactly do I have to do to to reproduce such a crash? Gerd [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q1/028256.html

1 0

Maps aspect ratio
by Carlos Dávila 23 Feb '18

23 Feb '18

One user of my maps has commented that in my maps longitude looks much shorter than latitude. Comparing the same area in three maps (CityNavigator, OpenFiestMap and my maps) they all show different aspect ratio [1]. Do you know reason for that? Any way to control it? [1] |http://files.mkgmap.org.uk/download/423/Screenshots.zip|

2 1

Rep: DEM & Artifacts
by David 22 Feb '18

22 Feb '18

Hello Gerd, About the tile N56W008, I made a mistake. This tile is a part of my own test. I took a look on your rectangular polygon. It includes some parts of Scotland and Wales whereas with my polygon I generate shadows only for Ireland. The result is now online at : http://emerald-island.eu/wikka/GpsMap Kind regards, David

1 0

Rép :⁨ DEM test & artifacts
by David 22 Feb '18

22 Feb '18

Hello Gerd, I was not able to download your polygon file but it is not a problem. My own polygon works like a charm and it is absolutely not a rectangular shape. It is contained in the area where there is no shadow applied on water surface. Is there a difference between a tile full of nan values like N56W008 and when the tile does not exist mkgmap writes a message about using 0m for elevation by default ? Ireland -9.0 55.5 -6.0 55.5 -5.25 54.6 -5.25 54.0 -5.75 54.0 -5.75 51.5 -8.0 51.5 -8.0 51.25 -10.75 51.25 -10.75 54.6 -9.0 54.6 -9.0 55.5 END END All the best, David

2 1