well actually with Europe continent map the splitter produced area.poly (from splitting geofabrik osm.pbf) - is failing as well. I'm now decreasing max-nodes hope that will work.... Right now I'm at a bit of a loss concerning DEM and europe continent map.

On 30 April 2018 at 23:47, Felix Hartmann <extremecarver@gmail.com> wrote:
okay - well thanks for your reply. I also think now it mainly depends on the .poly file - however it can be that changing the dem-dist or the hgt imput files makes it work nonetheless (but not very likely) 
I think right now the best is to first try with the geofabrik poly file, if that does not work then use the area.poly file from mkgmap splitter after splitting the geofabrik extract. 

Except for the Europe map where I actually found breakage in the middle of the map - so far I've only found the error on the outside. The breakage in the Europe map made me believe it's not the poly`- but I think I got carried away because of this.
Need more time to rerender every broken contourline map and check.

The area.poly file produced by the splitter seems to work all the time - all my problem cases so far disappeared.



I have one more idea - Could it be possible that the polygon is not allowed to be too complex? Maybe if within a tile there is a certain limit on how many times the area.polygon may cut in?
 In general all poly files that are not very complex work very well.

What did actually work sometimes what splitting the tiles smaller, and then the map would work with all else equal. 

In general most countries with problems have very detailed area.poly file from geofabrik.
Felix

On 30 April 2018 at 21:39, Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:
Hi Felix,

typically it depends on tile boundaries , poly file and dem-dists. In some cases a combination seems to require a special encoding which
is not yet known. Also the transparent option might be special.
Anyhow, I don't have much time to look at it for the rest of the week, and I have no idea how to fix it.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com>
Gesendet: Montag, 30. April 2018 19:18:19
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] DEM/Contourlines causing grey (empty) squares at the border of maps

actually using the area.poly created by mkgmap splitting the switzerland.osm.pbf by geofabrik did work (the resulting map is much bigger then however) - so the poly file does seem to have something to do with it....

On 30 April 2018 at 19:09, Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>> wrote:
Hallo Peter,
Eher würden mich die Copernicus Daten der EU interessieren - hier bin ich aber noch nicht richtig dahintergekommen wie ich die konvertieren soll.

Also die hier: https://www.eea.europa.eu/data-and-maps/data/copernicus-land-monitoring-service-eu-dem
Oder sind dass genau jene die du mit OpenDEM meinst?

die besten Daten sind IMHO derzeit: http://data.opendataportal.at/dataset/dtm-germany
Aber die sind nur sehr begrenzt verfügbar.



Die Quelle:
http://dwtkns.com/srtm30m/

scheint mir irgendwie auf die alten SRTM1v2.0 Daten Zugriff zu haben, oder irre ich mich und es ist die v3.0??

On 30 April 2018 at 18:59, Peter Danninger <peter@danninger.eu<mailto:peter@danninger.eu>> wrote:
Servus Felix,

Ich hab auch mit diversen .hgt-Dateien experimentiert,
für meine Javascript-Anwendung:
http://peter.myds.me/HDS/Tipps_Tricks/GPS/GPXclean/GPXclean.html
http://peter.myds.me/HDS/Tipps_Tricks/GPS/GPXclean/GPXcleanAdvanced.html

Mein Ergebnis der .hgt-Tests:

OpenDEM 1sec (Europa):  sehr gut
USGS_NASA 1sec:         (sehr) gut
Viewfinderpanoramas 1sec:       relativ gut *)
Viewfinderpanoramas 3sec:       weniger gut *)

*) aber ganz im Norden keine Alternative ???

Falls Du mit USGS_NASA-Dateien bzw. OpenDEM-Dateien
testen willst .... fragen ....

Ich habe ALLE .hgt getestet auf "void", "tooLow",
"tooHigh", und fehlerhafte Werte auf Basis der
Nachbarwerte korrigiert.

Beispiel für den Alpenraum:

// Alpen: korrigierte Dateien wegen zu niedrigem Höhenwert (< -5m)
//
//  "N45E010.hgt", "N45E011.hgt", "N45E012.hgt", "N45E013.hgt",
//  "N45E014.hgt", "N44E008.hgt", "N44E009.hgt", "N44E010.hgt",
//  "N44E011.hgt", "N44E012.hgt", "N44E013.hgt", "N44E014.hgt",
//  "N43E005.hgt", "N43E006.hgt", "N43E007.hgt", "N43E009.hgt",
//  "N43E010.hgt", "N43E011.hgt", "N43E012.hgt", "N43E013.hgt"


LG Peter


Am 30.04.2018 um 17:19 schrieb Felix Hartmann:
But Europe continent map seems to be broken too... so it's not that simple... I really don't know why alps is working and switzerland broken. I'll try if the broken maps work if I exclude viewfinderpanoramas 1" data and only use 3" data.

On 30 April 2018 at 15:22, Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com> <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>> wrote:

    I'm not fully sure it's because of the poly file - but it's clearly
    not based on wrong/broken input data. I created the Alps and
    Switzerland equally, and all of Switzerland is part of the Alps map
    too. Alps work, Switzerland does not. Strangely though changing the
    style-file a little - it may mean a map does not have the problem -
    so I think it's maybe only partly related to the poly file?

    On 30 April 2018 at 15:04, Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>
    <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>> wrote:

        Hi Gerd - can you find a pattern here?
        Folllowing are the polygons of 10 broken (out of a sample of 94
        rather "small" countries) poly files.
        https://openmtbmap.orgbroken_contours.zip
        <https://openmtbmap.orgbroken_contours.zip>

        it's
        Germany, Bavaria, Czech, Finland, Niedersachsen,
        Nord-Rhein-Westfalen, Poland, Paraguay, Romania
        Switzerland, Sweden

        The remaining 84 countries work fine in Basecamp (leaves about
        60 countries which are usually pretty big and I did not care to
        check as it means zooming in to 30km, sometimes 50km and pan
        around all borders of the map in Basecamp to spot if it's
        working or not).

        On 27 April 2018 at 09:27, Gerd Petermann
        <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>
        <mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>>> wrote:

            Hi Felix,

            a convex polygons doesn't seem to solve it. I tried with the
            attached and still see those problems :-(

            Gerd

            ________________________________________
            Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>>> im Auftrag
            von Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>
            <mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>>>
            Gesendet: Freitag, 27. April 2018 08:53:28
            An: Development list for mkgmap
            Betreff: Re: [mkgmap-dev] DEM/Contourlines causing grey
            (empty) squares at the border of maps

            Hi Felix,

            I think it is the shape of the poly that matters. Triangular
            shapes seem to be problematic. Pattern in DEM would be
            something like
            UUUUUUUUUUUUU
            UUUUUUVUUUUUU
            UUUUUVVUUUUUU
            UUUUVVVUUUUUU
            UUUVVVVVUUUUU
            with U for undefined and V for knwon height.

            If you use the (rectilinear) area.poly created by splitter
            when splitting the geofabrik OSM files you will not see this
            pattern as often.
            Maybe it would be enough to change the poly so that it is
            convex, not concave:
            https://en.wikipedia.org/wiki/Concave_polygon
            <https://en.wikipedia.org/wiki/Concave_polygon>

            And yes, I can confirm the missing altitude values with gray
            squares.

            Gerd

            ________________________________________
            Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>>> im Auftrag
            von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>
            <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>>
            Gesendet: Freitag, 27. April 2018 08:42:52
            An: Development list for mkgmap
            Betreff: Re: [mkgmap-dev] DEM/Contourlines causing grey
            (empty) squares at the border of maps

            I guess if the poly is a bit bigger - it would not happen?
            Could you try by enlarging the poly 2km to the outside? Not
            using a poly at all would be really big or am I wrong? Which
            normal poly do you mean? The area.poly created while
            splitting the geofabrik osm files? Or the area.poly created
            while splitting the phyghtmap osm.pbf contourlines file?

            I also noticed that while any of that grey square is visible
            in Basecamp - Basecamp does not show altitude in the lower
            left corner anymore.

            On 27 April 2018 at 07:40, Gerd Petermann
            <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>
            <mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>><mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>
            <mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>>>> wrote:
            Hi Felix,

            hmm, yes, that really looks bad. At the moment I only have
            work-arounds:
            1) Add additional DEM layers so that the error only shows up
            in smaller rectangles.
            2) Don't use --dem-poly, I think this causes the trouble. Or
            maybe try the poly file created for the normal tiles.

            I guess that the encoder still doesn't work 100% correctly,
            but I have no idea how to fix that and Frank Stinner seems
            to have stopped his work on
            https://github.com/FSofTlpz/Garmin-DEM-Build
            <https://github.com/FSofTlpz/Garmin-DEM-Build>

            Gerd

            ________________________________________
            Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>>>> im Auftrag
            von Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>
            <mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>><mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>
            <mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>>>>
            Gesendet: Donnerstag, 26. April 2018 20:53:21
            An: Development list for mkgmap
            Betreff: Re: [mkgmap-dev] DEM/Contourlines causing grey
            (empty) squares at      the border of maps

            Hi Felix,

            I'll have a closer look tomorrow. IIRC this also happens
            with Garmin maps.

            Gerd

            ________________________________________
            Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>>>> im Auftrag
            von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>
            <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>
            <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>>>
            Gesendet: Donnerstag, 26. April 2018 20:23:11
            An: Development list for mkgmap
            Betreff: Re: [mkgmap-dev] DEM/Contourlines causing grey
            (empty) squares at      the border of maps

            well maybe it's more common - like in 1/5 maps if the
            include 1" DEM data - only happens if map includes DEM.

            On 26 April 2018 at 20:20, Felix Hartmann
            <extremecarver@gmail.com<mailto:extremecarver@gmail.com>
            <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>
            <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>

            <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>
            <mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>>>> wrote:
            In some cases at the borders of maps - there appear grey
            rectangles in Basecamp and Mapsource (well do not mind
            Mapsource much - it's very outdated) - this only appears if
            using a DEM/contourline overview...

            Sorry as Basecamp is windows only - only windows
            installer/Mac OSX gmap file here:
            https://openmtbmap.org/mtbbayern.exe
            <https://openmtbmap.org/mtbbayern.exe>
            or
            https://openmtbmap.org/mtbbayern_macosx.7z
            <https://openmtbmap.org/mtbbayern_macosx.7z>

            Without contourlines the map works fine (mapsetx.tdb...)
            Contourlines map alone also does not work (mapsetz.tdb...)


            So the bug is clearly in the transparent DEM/contourlines
            map. Sometimes simply rendering the contourlines map again
            and the bug is gone...


            Seems to be not that common but also not that rare (maybe in
            1 out of 20 maps)

            --
            Felix Hartman - Openmtbmap.org & VeloMap.org
            Schusterbergweg 32/8
            6020 Innsbruck
            Austria - Österreich



            --
            Felix Hartman - Openmtbmap.org & VeloMap.org
            Schusterbergweg 32/8
            6020 Innsbruck
            Austria - Österreich
            _______________________________________________
            mkgmap-dev mailing list
            mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>>
            http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
            <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>
            _______________________________________________
            mkgmap-dev mailing list
            mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>>
            http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
            <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>



            --
            Felix Hartman - Openmtbmap.org & VeloMap.org
            Schusterbergweg 32/8
            6020 Innsbruck
            Austria - Österreich
            _______________________________________________
            mkgmap-dev mailing list
            mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>
            http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
            <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>

            _______________________________________________
            mkgmap-dev mailing list
            mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
            <mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>
            http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
            <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>




        --         Felix Hartman - Openmtbmap.org & VeloMap.org
        Schusterbergweg 32/8
        6020 Innsbruck
        Austria - Österreich




    --     Felix Hartman - Openmtbmap.org & VeloMap.org
    Schusterbergweg 32/8
    6020 Innsbruck
    Austria - Österreich




--
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich


_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev





--
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich



--
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev



--
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich



--
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich