[mkgmap-dev] Polygon fill

Tue Oct 20 19:49:08 BST 2020

Hi Vuki,

the question is if the multipolygon for the lake is complete. Your screen shot shows an imcomplete area.
Check relation 1638031.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Vuki <vuki77 at gmail.com>
Gesendet: Dienstag, 20. Oktober 2020 20:38
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Polygon fill

Hi Gerd,

the OSM comes directly from overpass API, this is small enough not to split. It also looks good for me.

18.00x46.50 by 18.50x47.00

The arifact is somehow connected to the bounding box borders?

Example:
http://www.informatik.hu/balaton2.jpg

Köszi:
Vuki

On 2020.10.20. 11:32, Gerd Petermann wrote:

Hi Vuki,

flooded lakes are typically caused by incomplete multipolygons. Another reason can be that the OSM data itself is wrong. Do you use splitter with the keep-complete option enabled?

Best way to verify is to load a tile that contains a part of the lake in JOSM (use the pbf or o5m plugin). If JOSM shows a problem than mkgmap cannot be blamed.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Vuki <vuki77 at gmail.com><mailto:vuki77 at gmail.com>
Gesendet: Dienstag, 20. Oktober 2020 11:17
An: mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
Betreff: [mkgmap-dev] Polygon fill

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<mailto:mkgmap-dev at lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev