Hi Philip
I think a lot of the contour lines in this file are corrupt.
Trying to build with your options etc I get 117034 subdivisions.
Stripping out the style so only showing contour lines I get 116886 subdivisions.
Just choosing: contour=elevation & contour_ext=elevation_major I get 7381
subdivisions and so can make a displayable map.
This shows some meaningful contour lines but often with gaps where I'd expect
them to be closed. However there are many more straight (2 point) lines running
across the tile (most with start and end outside the map area). Generally these
seem to come in bunches and are not horizontal or vertical.
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
How did you merge the osm map and the contour input? I've found that putting any
extra .xml files after the main county osm.pbf on the splitter command line
works well.
A hack to ignore long contour lines is to add the line:
contour=elevation & length() > 10000 {deletealltags}
at the start of style /inc/contour_lines. This gives a reasonable looking, but
incomplete map and still has a few erroneous-looking contours.
Ticker
On Mon, 2025-09-22 at 14:33 +0200, Philip Homburg via mkgmap-dev wrote:
> In your letter dated Mon, 22 Sep 2025 09:01:33 +0100 you wrote:
> > Can you upload a failing tile .osm.pbf somewhere. Maybe files.mkgmap.org.uk
> > still works.
>
> Here it is: https://fx.hq.phicoh.net/62385001.osm.pbf
> _______________________________________________
> mkgmap-dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> %(web_page_url)slistinfo/%(_internal_name)s
_______________________________________________
mkgmap-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo/%(_internal_name)s
