In your letter dated Mon, 22 Sep 2025 17:35:49 +0100 you wrote: >Can you scan your contour input for, say: >Way 10687031 [contour=elevation, contour_ext=elevation_major, ele=1400] >which appears to have a length of 16139 km
I found it. Thanks so much for your help. What happened is that my script to handle contour lines is really old. To generate OSM data you need to pass in a starting node id. I picked a really high number. Now OSM has caught up. So after merging, I use osmosis for that, the result was complete chaos. I guess it was also chaos on the other maps I tried, but it was not obvious looking at the map. Though I did notice weird broken contour lines before. For testing, I just raised the starting node id, but I have to come up with a more permanent fix where I extract the highest node id from the input OSM data. Again, thanks very much for your effort. _______________________________________________ mkgmap-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo/%(_internal_name)s
