[mkgmap-dev] Polygon fill
From Ticker Berkin rwb-mkgmap at jagit.co.uk on Tue Oct 20 13:56:55 BST 2020
Hi Vuki Various possibilities / questions: Do you do anything particular with natural=background in your style. The default is natural=land and the default style doesn't need to generate anything for it because the device default background isn't sea. Do you have a typ file? Does it assign assign a hierarchy of [_drawOrder] levels to the different types of polygons. With --order-by-decreasing-area, it is assumed that you give everything except the background (0x4a/0x4b) the same value and that the device renders polygons in the the order they appear in the .img file. It is possible that your device doesn't do this. In your examples, I only see parts of lakes not showing as water. As far as I'm aware, these are not represented with coastline and sea processing. They should have natural=water tags and generate standard blue polygons (maybe 0x3c). It is possible that the resolution these lakes appear at is too high, but this is unlikely because it is showing the rivers within the lake. Regards Ticker On Tue, 2020-10-20 at 11:17 +0200, Vuki wrote: > > Hello Guys, > > I am brewing custom maps for my Garmin zumo 396. > > - get the OSM data from the overpass api (0.5 by 0.5 degree > > bounding box) > > - use splitter to split too large parts > > - use mkgmap to build the maps. > > The generated garmin maps have wrong filled polygons, lakes are > > filled with land and vice versa. > > Here are two examples (lake Balatom and lake Geneva) > > http://www.informatik.hu/balaton.jpg > > http://www.informatik.hu/geneva.jpg > > When I download the lake Balaton in one bounding box the artefacts > > are disappearing, thus there must be something merging the files. > > I have tried various mkgmap settings but could not solve the > > issues. Curret config is: > > levels: 0:24, 1:22, 2:20, 3:18, 4:16, 5:14, 6:12, 7:10 > > add-pois-to-areas > > add-pois-to-lines > > adjust-turn-headings > > bounds: ../bounds-latest.zip > > check-roundabout-flares > > check-roundabouts > > copyright-message: Map data © Openstreetmap.org > > drive-on=detect,right > > generate-sea: land-tag=natural=background > > gmapi > > gmapsupp > > housenumbers > > ignore-maxspeeds > > index > > keep-going > > latin1 > > link-pois-to-ways > > location-autofill: is_in,nearest > > make-opposite-cycleways > > merge-lines > > name-tag-list: int_name,name:en,name:hu,name,place_name > > #nsis > > order-by-decreasing-area > > precomp-sea: ../sea-latest.zip > > preserve-element-order > > process-destination > > process-exits > > reduce-point-density-polygon=8 > > reduce-point-density=3 > > remove-ovm-work-files > > remove-short-arcs > > road-name-pois > > route > > # show-profiles: 1 > > style-file: ../styles > > style: default > > tdbfile > > x-split-name-index > > verbose > > Do you have any ideas what can cause the issue? > > > > -- > > Br, > > Vuki > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
- Previous message: [mkgmap-dev] Polygon fill
- Next message: [mkgmap-dev] Polygon fill
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list