Does the produced map display correctly for you? I don't get any errors either but the produced map does not display properly as I tried showing in the attached screenshots in my earlier messages. I too use the hgt files from viewfinderanoramas. On 24/09/2020 9:12 pm, Gerd Petermann wrote:
Hi Joao,
sorry, I was not able to reproduce the problem. I've downloaded the hgt files from http://www.viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org3... and tried with java -jar d:\mkgmap\dist\mkgmap.jar --gmapi --dem=f:\srtm3_1_comp --dem-dists=9942 --overview-dem-dist=88888 --dem-poly=f:\dwnload\temp\areas(1).poly 67301053.osm.pbf No error message and DEM data looks good.
Please try the same command with attached (empty) osm file and your data paths. If you can reproduce the crash I'd try to replace the hgt files.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joao Almeida <joaoha@gmail.com> Gesendet: Donnerstag, 24. September 2020 12:17 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] DEM file Number too big for binary encoding with 14 bits
Done.
On 24/09/2020 7:43 pm, Gerd Petermann wrote:
Hi Joao,
I need the poly file as well dem-poly=C:\Garmin\SplitterTemp\areas.poly
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joao Almeida <joaoha@gmail.com> Gesendet: Donnerstag, 24. September 2020 11:42 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] DEM file Number too big for binary encoding with 14 bits
Thanks Gerd,
Files attached.
Joao
On 24/09/2020 6:13 pm, Gerd Petermann wrote:
Hi Joao,
Please attach the areas.list produced by splitter. Maybe I'll be able to reproduce the error here. BTW: DEM calculation errors don't depend on the style or the objects in the OSM files.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joao Almeida <joaoha@gmail.com> Gesendet: Mittwoch, 23. September 2020 14:47 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] DEM file Number too big for binary encoding with 14 bits
Thank you Gerd,
So I narrowed it down a bit more. I'm getting a similar behavior when trying to build Russia with DEM. But because it is quite a big file I'm doing it with ANZ.
Here are my findings. It seems to be related to DEM and only affecting New Zealand. If I build Australia using the same settings/options/style I get a working map.
If I build New Zealand without DEM and only contours I get a working map. Note the contours are created from the same HGT files, so I would assume the HGT files are correct. If I build New Zealand without DEM or contours I also get a working map, so I would say that would eliminate a TYP or Style issue.
Also I mentioned I can create a DEM map for Australia without a problem with the same DEM options so I would say the DEM settings would not be a problem but I don't know for sure.
Here are the settings:
--overview-dem-dist=88888 --dem-dists=9942
Build command line: java -Xmx8192m -ea -jar C:\Garmin\MKGMAP~2\mkgmap.jar --mapname=37406557 --family-id=5979 C:\Garmin\Typs\jbm52dwl.typ --series-name="JBT New Zealand" --family-name="JBT New Zealand" --overview-mapname="JBT New Zealand" --style-file=C:\Garmin\styles --style="Style-Jbm5.2.0a-Merge" --gmapi --keep-going --output-dir=C:\Garmin\MAPUPL~1 --index --nsis --tdbfile --draw-priority=10 --remove-short-arcs --check-roundabouts --drive-on=left --route --name-tag-list=int_name,name --location-autofill=is_in,nearest --index --housenumbers --copyright-message="Map data © openstreetmap.org" --check-styles --bounds="c:\Garmin\Sources\bounds-latest.zip" --precomp-sea="c:\Garmin\Sources\sea-latest.zip" --show-profiles=1 --latin1 --code-page=1252 --name-tag-list=name --add-pois-to-areas --pois-to-areas-placement=always=middle --add-pois-to-lines --link-pois-to-ways --make-poi-index --x-split-name-index --nearby-poi-rules-config="c:\Garmin\Styles\Style-Jbm5.2.0a-Merge\config.nearbypoi" --check-roundabout-flares --add-boundary-nodes-at-admin-boundaries=4 --drive-on=detect --merge-lines --remove-ovm-work-files --verbose -c C:\Garmin\SPLITT~4\DEM~1.ARG -c C:\Garmin\SPLITT~4\TEMPLA~2.ARG PAUSE
When I build the New Zealand map I only get a map at zoom level 30km or below with Basecamp set to map detail High. The output from this build command line is attached.
screenshot NZ1 -- no map at all except for some islands New zealand should be where the tracks are. screenshot NZ2 -- we have some parts of the map but the east side of New Zealand is cut.
screenshot NZ3 -- a lower zoom level the east side of New Zealand appears.
Thanks for the help.
Joao
On 23/09/2020 3:00 am, Gerd Petermann wrote:
Hi Joao,
difficult. Seems the algorithm to encode DEM data is wrong. All the DEM data in your screenshot looks bad, so maybe the problem is in the hgt input files or in the DEM options. Maybe try to use slightly different dem-dist value(s). If this doesn't help I need the *.hgt files that are used for this tile and the file C:\Garmin\SPLITT~4\67301053.o5m and the DEM options to be able to reproduce the problem.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joao Almeida <joaoha@gmail.com> Gesendet: Freitag, 18. September 2020 03:41 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] DEM file Number too big for binary encoding with 14 bits
Hi,
Any idea how I can diagnose this issue?
SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301057.o5m: Attention: Tile contains both drive-on-left (81) and drive-on-right roads (1031) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301054.o5m: Attention: Tile contains both drive-on-left (4817) and drive-on-right roads (4982) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301053.o5m: Attention: Tile contains both drive-on-left (3133) and drive-on-right roads (1255) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301052.o5m: Attention: Tile contains both drive-on-left (5668) and drive-on-right roads (603) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301061.o5m: Attention: Tile contains both drive-on-left (2381) and drive-on-right roads (81) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301065.o5m: Attention: Tile contains both drive-on-left (745) and drive-on-right roads (18) SEVERE (MapFailedException): C:\Garmin\SPLITT~4\67301053.o5m: (thrown in DEMTile.writeValAsBin()) Number too big for binary encoding with 14 bits:32559 SEVERE (MapBuilder): C:\Garmin\SPLITT~4\67301053.o5m: exception while creating DEM file Number too big for binary encoding with 14 bits:32559 SEVERE (MapFailedException): C:\Garmin\SPLITT~4\67301053.o5m: (thrown in MapBuilder.buildDem()) DEM SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301069.o5m: Attention: Tile contains both drive-on-left (4648) and drive-on-right roads (227) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301070.o5m: Attention: Tile contains both drive-on-left (6416) and drive-on-right roads (2) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301097.o5m: Attention: Tile contains both drive-on-left (19) and drive-on-right roads (2) SEVERE (StyledConverter): C:\Garmin\SPLITT~4\67301099.o5m: Attention: Tile contains both drive-on-left (2) and drive-on-right roads (2) Number of MapFailedExceptions: 1 Number of ExitExceptions: 0
Getting this while trying to build the map with DEM
The result is attached.
Thanks a lot Joao