Hi Joao, you probably have a large tile that contains rather few OSM details but a lot of DEM data. Mongolia would be a typical candidate. With your change of the --dem-dist option you removed several DEM levels and thus drastically reduced the number of bytes needed for that data. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joao Almeida <joaoha@gmail.com> Gesendet: Dienstag, 15. September 2020 01:22 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] DEM There is not enough room in a single garmin map for all the input data Reporting I found a fix for this. I stopped having the messages and being able to compile my maps after I changed the following options: Before: --dem-dists=3312,3312,9942,13248,26512,44176 --overview-dem-dist=88368 After: --overview-dem-dist=88888 --dem-dists=9942 I'm not sure why some tiles where throwing the error, because I was able to compile other areas with the original settings. Not sure if someone has an answer or wants to investigate. Cheers On 2/09/2020 8:18 pm, Joao Almeida wrote:
I was created from data from: http://geojson.io/#map=2/20.0/0.0 <http://geojson.io/#map=2/20.0/0.0> { "type": "FeatureCollection", "features": [ { "type": "Feature", "properties": {}, "geometry": { "type": "Polygon", "coordinates": [ [ [ 94.921875, -55.77657 ], [ 189.84375, -55.77657 ], [ 189.84375, -7.362466 ], [ 94.921875, -7.362466 ], [ 94.921875, -55.77657 ] ] ] } } ] }
Thanks for looking at this. Joao
---------- Forwarded message ---------- From: Gerd Petermann <gpetermann_muenchen@hotmail.com <mailto:gpetermann_muenchen@hotmail.com>> To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk>> Cc: Bcc: Date: Wed, 2 Sep 2020 07:48:52 +0000 Subject: Re: [mkgmap-dev] DEM There is not enough room in a single garmin map for all the input data Hi Joao,
how did you create this poly file? The value 189.84375 is obviously wrong and probably mkgmap / splitter fails to recognize that.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Joao Almeida <joaoha@gmail.com <mailto:joaoha@gmail.com>> Gesendet: Dienstag, 1. September 2020 13:34 An: mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: Re: [mkgmap-dev] DEM There is not enough room in a single garmin map for all the input data
For example.
This is the poly file with the areas. Title 1 -30.41875 45.18952 -30.20899 13.02443 -14.68754 13.38583 -7.346309 27.84205 1.043668 31.57658 0.4144224 37.2386 10.27264 38.32281 14.46764 35.3111 19.29187 39.64797 18.66261 49.64685 6.706903 48.20123 -1.473327 45.18952 -29.16025 45.79186 -30.41875 45.18952 END 2 44.8813 49.04451 53.48103 55.67028 67.11473 57.35684 78.23146 55.54981 88.29943 49.88779 97.10889 53.74279 101.5137 52.89951 114.5181 51.93576 118.9228 49.88779 120.8106 45.79186 106.3379 39.64797 91.23593 41.93687 86.83118 46.99655 78.23146 37.2386 62.29049 34.22689 54.52977 36.63626 44.8813 49.04451 END 3 94.921875 -55.77657 189.84375 -55.77657 189.84375 -7.362466 94.921875 -7.362466 94.921875 -55.77657 END END
If I use this poly file I get the map too big error for areas in:
3 94.921875 -55.77657 189.84375 -55.77657 189.84375 -7.362466 94.921875 -7.362466 94.921875 -55.77657 END
But if I only use the following poly file:
Title 1 94.921875 -55.77657 189.84375 -55.77657 189.84375 -7.362466 94.921875 -7.362466 94.921875 -55.77657 END
Note it is the same area as 3 in main file I don't get the map too big error.
Hope it clarifies
Thank you for the help.
On Tue, Sep 1, 2020 at 9:39 AM Joao Almeida <joaoha@gmail.com <mailto:joaoha@gmail.com><mailto:joaoha@gmail.com <mailto:joaoha@gmail.com>>> wrote: Help please, could not find a solution that works. I'm trying to build a map that includes DEM shading. I've tried splitting the map with max nodes 800000, 600000 and this last time 400000. For some reason I always get the following message on the same tile regardless of the split maxnodes option.
There is however a different behaviour, this only happens if I try to include different polygon areas, if I just try the same are by it self it does not throw the message about map too big.
I'm happy to provide poly file and splitter settings and map build options to see if we can overcome this problem.
Thanks a lot. Joao
SEVERE (MapFailedException): C:\Garmin\SPLITT~4\44161838.o5m: (thrown in BufferedImgFileWriter.ensureSize()) There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first. SEVERE (MapBuilder): C:\Garmin\SPLITT~4\44161838.o5m: exception while creating DEM file There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first. SEVERE (MapFailedException): C:\Garmin\SPLITT~4\44161838.o5m: (thrown in MapBuilder.buildDem()) DEM SEVERE (MapFailedException): C:\Garmin\SPLITT~4\44161841.o5m: (thrown in BufferedImgFileWriter.ensureSize()) There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first. SEVERE (MapBuilder): C:\Garmin\SPLITT~4\44161841.o5m: exception while creating DEM file There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first. SEVERE (MapFailedException): C:\Garmin\SPLITT~4\44161841.o5m: (thrown in MapBuilder.buildDem()) DEM
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev