- mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] DEM There is not enough room in a single garmin map for all the input data
by Joao Almeida 22 Sep '20

22 Sep '20

I was created from data from: 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(a)hotmail.com> > To: Development list for mkgmap <mkgmap-dev(a)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(a)lists.mkgmap.org.uk> im Auftrag von > Joao Almeida <joaoha(a)gmail.com> > Gesendet: Dienstag, 1. September 2020 13:34 > An: mkgmap-dev(a)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(a)gmail.com<mailto: > joaoha(a)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 > > >

2 4

Commit r4582: document special tag with prefix mkgmap:from-node:
by svn commit 21 Sep '20

21 Sep '20

Version mkgmap-r4582 was committed by gerd on Sat, 19 Sep 2020 document special tag with prefix mkgmap:from-node: (Patch by Marc Cousin, modified) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4582

3 3

Commit r4583: fix documentation syntax error
by svn commit 21 Sep '20

21 Sep '20

Version mkgmap-r4583 was committed by gerd on Mon, 21 Sep 2020 fix documentation syntax error http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4583

1 0

Commit r4581: remove java code which evaluates oneway=reverse (as a synonym for oneway=-1)
by svn commit 18 Sep '20

18 Sep '20

Version mkgmap-r4581 was committed by gerd on Fri, 18 Sep 2020 remove java code which evaluates oneway=reverse (as a synonym for oneway=-1) Also adapt style tests using this. oneway=reverse no longer appears in OSM data http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4581

1 0

Driving side warnings
by Ticker Berkin 18 Sep '20

18 Sep '20

Hi Gerd Attached is a patch that doesn't assign a driving side to more types of ways where it is not relevant. This speeds up processing slightly and, in some circumstances, stop the warning: "Tile contains both drive-on-left (#) and drive-on-right roads (#)" Previously ferries were ignored, this patch additional ignores one-way roads and roads that don't allow motor vehicles (eg footpaths & cycleways) Ticker

2 3

Commit r4580: improve driving side detection (drivingSide.patch by Ticker Berkin, modified)
by svn commit 18 Sep '20

18 Sep '20

Version mkgmap-r4580 was committed by gerd on Fri, 18 Sep 2020 improve driving side detection (drivingSide.patch by Ticker Berkin, modified) Attached is a patch that doesn't assign a driving side to more types of ways where it is not relevant. This speeds up processing slightly and, in some circumstances, stop the warning: "Tile contains both drive-on-left (#) and drive-on-right roads (#)" Previously ferries were ignored, this patch additional ignores one-way roads and roads that don't allow motor vehicles (eg footpaths & cycleways) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4580

1 0

Map display detail in basecamp.
by Joao Almeida 18 Sep '20

18 Sep '20

Hi, I'm not sure this is the fault behavior but I would like to ask anyway. At higher zoom levels my map is not defined at the edges (land-sea) please see attached screenshot. The definition only comes at lower zoom: Basecamp render quality is set to maximum. Thanks for your help. Joao

2 3

trying to match a point in a way (mountain pass)
by Marc Cousin 16 Sep '20

16 Sep '20

Hi, I'm working on a style to try to display mountain passes, but only those that are reachable on certain ways (either only pedestrian, or only motor_vehicle, for instance) But the mountain pass is a point in the way, and it seems that I cannot access the attributes of the way in the point style file. Is there a way around ? Regards

2 1

Display Zipfile
by Ticker Berkin 15 Sep '20

15 Sep '20

Hi Gerd Trying to use display/src/test/ZipFile.java to reconstitute a tile .img from the constituents in a .gmap directory tree or extracted from a gmapsupp.img so I could run other display diagnostics I found it was broken, probably due to blocksize optimisation project. I attach a patch that gets it working again and has some comments about how it might be used. Ticker

2 1

DEM There is not enough room in a single garmin map for all the input data
by Joao Almeida 15 Sep '20

15 Sep '20

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

3 7