In your letter dated Sat, 20 Sep 2025 11:40:51 +0100 you wrote: >Worth trying is to put back the -ea option and try option > --order-by-decreasing-area >which changes the behaviour the splitting algorithm. > >I've never looked at how contours work: eg. where the data comes from and how >it >is merged into the map generation process. Can you briefly explain your proces >s >and send your splitter & mkgmap options and, if not using the default style, >your style.
Adding --order-by-decreasing-area didn't seem to have any effect. The contour data comes from pyhgtmap. It generates osm files with data like this. I combine them with the map data and then run the splitter. <way id="10704556" version="1"><nd ref="1492605182"/> <nd ref="1492605183"/> <nd ref="1492605184"/> <nd ref="1492605185"/> <nd ref="1492605186"/> <nd ref="1492605187"/> <nd ref="1492605188"/> <nd ref="1492605182"/> <tag k="ele" v="130"/><tag k="contour" v="elevation"/><tag k="contour_ext" v="elevation_minor"/></way> For the splitter I only have --mapid For mkgmap, I have the following arguments: --order-by-decreasing-area --gmapsupp --verbose -c map.args $typ -c template.args And this in map.args: #style-file: /home/philip/gmap/styles style-file: /home/philip/mkgmap-r4923/examples/styles style: default description: Default (HR) product-id: 100 product-version: 2 family-name: mkgmap default croatia family-id: 62385 remove-short-arcs: 1 generate-sea: land-tag=natural=background generate-sea: multipolygon bounds: bounds location-autofill: nearest housenumbers latin1 code-page: 1252 show-profiles: 1 merge-lines add-pois-to-areas add-pois-to-lines link-pois-to-ways make-opposite-cycleways min-size-polygon: 4 preserve-element-order keep-going net route index #dem: hgt/VIEW1,hgt/VIEW3,hgt/SRTM3v3.0 _______________________________________________ mkgmap-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo/%(_internal_name)s
