May 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

special case where splitting fails without a log message
by Gerd Petermann 03 Jun '21

03 Jun '21

Hi Ticker, while looking at the problems with sea I found this case where ShapeSplitter removes a small part of an island from a self-intersecting polygon in res 24. Compiled with mkgmap from trunk, default style and no options. Look at 67.6742611, 14.6783525 Found this with some check code that compares the area of the original polygon with that of sum of the parts. Gerd

4 44

Re: [mkgmap-dev] [mkgmap-svn] Commit r4749: remove/disable code to merge shapes to the max for now:
by Ticker Berkin 31 May '21

31 May '21

Hi Gerd Do you have an example of this triangle / concave shape? Are you sure there isn't a rotation through the connection point, resulting in something like a figure-of-8. Ticker On Mon, 2021-05-31 at 07:41 +0100, svn commit wrote: > Version mkgmap-r4749 was committed by gerd on Mon, 31 May 2021 > BRANCH: low-res-opt > remove/disable code to merge shapes to the max for now: > - hole detection was too simple, sometimes removed outer parts of > shapes > - ShapeSplitter doesn't handle some degenarated shapes well where > parts are connected in a single point, like a triangle connected to a > concave shape. > > Will try again with a different approach once ShapeSplitter is able > to handle these cases. > > http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4749 > _______________________________________________ > mkgmap-svn mailing list > To unsubscribe send an mail to mkgmap-svn-leave(a)lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-svn

2 1

Splitter only writes points, not ways on huge file?
by Felix Hartmann 29 May '21

29 May '21

I used phyghtmap to create a huge file (60GB) of 10m equidistance osm.pbf contourlines data. phyghtmap --jobs=2 --polygon=/home/contourlines/bounds/asia.poly --step=10 --no-zero-contour --void-range-max=-420 --output-prefix="Asia10m" --line-cat=500,100--start-node-id=10000000 --start-way-id=10000000 --source=view1,srtm1,view3,srtm3 --max-nodes-per-way=230 --max-nodes-per-tile=0 --pbf I am not fully sure that this pbf file is correct, but I created it exactly the same way as smaller countries. Maybe its also phyghtmap going wrong. But I doubt it with phyghtmaps incremental approach of just constantly writing out data. When splitting it with splitter - and opening up one of the osm.pbf files in JOSM - I noticed it contains only the contourline nodes, no lines. I think the Asia continent file spans 360 degrees - so maybe that causes problems with splitter? I have uploaded a splitted file here: https://openmtbmap.org/75400407.osm.pbf If you load it in Josm, you will notice it is alll the points but no lines... -- Felix Hartman - Openmtbmap.org & VeloMap.org

2 8

logging improvement
by Mike Baggaley 26 May '21

26 May '21

Hi Gerd, Please find attached a small patch that changes the logging of RoadDef when the original element is a relation. Currently it just says "generated way"; with the patch it gives the URL of the relation in the same way as it does for ways. Cheers, Mike

2 17

Commit r4745: fix possible wrong split with degenarated polygon (splitShapeFix.patch by Ticker Berkin, modified)
by svn commit 26 May '21

26 May '21

Version mkgmap-r4745 was committed by gerd on Wed, 26 May 2021 fix possible wrong split with degenarated polygon (splitShapeFix.patch by Ticker Berkin, modified) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4745

1 0

Re: [mkgmap-dev] rendering nested relations
by Alexis Lecanu 25 May '21

25 May '21

Hello, I'm contacting you because I have the same problem as described here: https://www.mkgmap.org.uk/pipermail/mkgmap-dev/2012q4/015775.html <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/2012q4/015775.html> The problem is that if the parent relationship has a higher id then I can't assign attributes to its child relationships. I may have misunderstood something for the relations I would like in my case to carry over the osmc:ref tag to the child relations. https://www.openstreetmap.org/relation/11999802 <https://www.openstreetmap.org/relation/11999802> Thank you in advance for your help. ---- Alexis LECANU https://www.facebook.com/Garmin-Connect-App-Alexis-Lecanu-395326794312827 If you want to pay me a beer to thank me: https://paypal.me/alecanu

2 1

Problems with sea in overview map
by Gerd Petermann 25 May '21

25 May '21

Hi all, I've identified a few problems with the handling of natural=sea in areas with lots of islands, e.g. coast of Norway. Thouands of rather small polygons are created, esp. when also natual=land is rendered. 1. Typical tiles are rather large, they span several precompiled sea tiles if --precomp-sea=sea.zip is used. As of now, the polygons from different sea-tiles are never merged. This might be improved to reduce file size and possibly also improve rendering 2. Even at resolution 12 the curent code distributes the thousands of tiles into multiple sub divisions before ShapeMerger is executed for each subdiv. Shapes (polygons) are only merged when the number of points for one shape stays inside the IMG limit of 256 points, so the merger cannot do much. 3. Douglas-Peucker (DP) filter is used for the merged shapes which contain holes. This gives weird results because the invisible lines which connect the holes are causing heavy self-intersections at low resolutions. I think this is one reason for white triangles in the sea. I am experimenting with these ideas: - At low resolutions the ShapeMerger could merge more so that shapes with more than > 256 points are produced, assuming that DP filter will remove many of them. Not sure if this works with shapes that have holes. - At low resolutions it is likely/wanted that small islands disappear, so we should remove those first, together with the lines that connect them with the outer ring. - The simplified sea polygons without holes should be merged as much as possible before using any filter, maybe DP should be executed first on the merged shapes so that fever subdivs are created. Each method has its own effects and I'm searching for the best combination and order. A lot of this is only possible because we now have Tickers code that allows multipolygon splitting without using java.awt.geom.Area.intersect() . Tickers code in ShapeSplitter seems to be able to handle the holes properly. Gerd

4 40

Unprocessed relationship.
by Alexis Lecanu 25 May '21

25 May '21

Hello, I have the impression that the relations which contain relations are not treated in the relations file. I have put in echo and I have the impression that it does not exist. My idea is to carry over tags a to ways but for the moment I only pass in relations that are on way types. I may be doing something wrong but I don't know what. Thanks in advance. ---- Alexis LECANU 06 20 31 01 56

1 0

Similar Arcs
by Mike Baggaley 24 May '21

24 May '21

Hi Gerd, Please find attached the patch for deleting similar arcs. It uses a new mkgmap:nooverlap tag which can be set to a number between 0 and 127 (default 0) in the lines file. If set to a number greater than zero then the overlapping part of the line will be deleted if it overlaps another line, providing the access of the other line is a superset of its access. If both lines have non zero values and have the same access then the line with the higher value will be deleted. In my style file I have the following: highway=service & (area=yes | mkgmap:mp_created=true) & (foot=yes | foot=designated | foot=official | foot=permissive | (foot!=* & (access!=* | access=yes | access=permissive))) {set mkgmap:car=no; set mkgmap:bicycle=no; set foot=yes; set mkgmap:flare-check=no; set mkgmap:numbers=false; set mkgmap:set_unconnected_type=none; set mkgmap:set_semi_connected_type=none; set mkgmap:nooverlap=1} [0x13 road_class=0 road_speed=0 resolution 22] highway=pedestrian & (area=yes | mkgmap:mp_created=true) & (foot=yes | foot=designated | foot=official | foot=permissive | (foot!=* & (access!=* | access=yes | access=permissive))) {set mkgmap:car=no; set mkgmap:bicycle=no; set foot=yes; set mkgmap:flare-check=no; set mkgmap:numbers=false; set mkgmap:set_unconnected_type=none; set mkgmap:set_semi_connected_type=none; set mkgmap:nooverlap=1} [0x0d road_class=0 road_speed=0 resolution 22] amenity=parking & (parking!=* | parking=surface) & (foot=yes | foot=designated | foot=official | foot=permissive | (foot!=* & (access!=* | access=yes | access=permissive))) {set mkgmap:car=no; set mkgmap:bicycle=no; set foot=yes; set mkgmap:numbers=false; set mkgmap:set_unconnected_type=none; set mkgmap:set_semi_connected_type=none; set mkgmap:nooverlap=2; set mkgmap:delivery=no; set mkgmap:truck=no; set mkgmap:bus=no; set mkgmap:taxi=no; set mkgmap:emergency=no } [0x08 road_class=0 road_speed=0 resolution 24 continue] and similar for railway=platform, man_made=pier, man_made=jetty and leisure=slipway. Cheers, Mike

3 4