Hi all,
thanks for the input. I still have no idea what this size value might be but I
agree that it doesn't seem to have
an influence on the crash.
I also tried changing several other of the unknown fields and found no change.
I also tried to change the tdb to version 411, no change reg. crash.
Hi Gerd,
> I only have one routable map with DEM data
See this nice post by moderator on Garmin Forum:
https://forum.garmin.de/showthread.php?49979-TopV7-Routen-aus-markierten-Wegen&p=247707#post247707
These maps work in BaseCamp, when placed on pendrive.
--
Best regards,
Andrzej
_
Hi all,
I am wondering why the DEM-features are titled „Hillshading Options“. The most
valuable function of DEM (which I was missing for a long time) is the 3d-View
in Basecamp when planning trips.
This should be promoted with a appropriate headline :)
Andreas
> Am 03.02.2018 um 11:21 schri
Hi Gerd,
I think it's even more in combination with DEM. I usually use 6 of my 8
cores and ending up with 10 to 12 GB of heap. So I definitely agree with
you available heap somehow needs to be considered as well. Not only CPU
cores. Btw. for CFD/FEM analysis the simulation is usually is faster if
y
Hi
It seems that mkgmap writes some constants that might be important, e.g.
MapDetailBlock.java contains
//01 c3 00 ff
os.write4(0xff00c301);
os.write(0);
os.write(0);
os.write(0);
I've just looke
Hi Gerd,
> The wiki [1] describes these 7 bytes as
> "byte:0 has copyright text,byte 1: has 0x53 text : byte 2:if 1 then
> bytes 3_7: an unknown total (density) "
For gmaptool I have assumed following meaning of these data:
byte 0 - always 1
byte 1 - region (always 1)
byte 2 - subregion (always
Hi Gerd
Have been checking a few garmin tdbs and it appears that
while the first 3 bytes remain the same for each, ie 01 00 00,
the last four bytes are always different and never zero !
also ,except with mkgmap tiles, I have not come across C3 in the second
byte ie a 01 *c3 *00
Nick
On 05
Hi,
Ive discussed with Frank if there might be a field in the tdb file that has to
be changed.
Maybe there is a value that tells MapSource something about the alignment of
DEM data?
I don't have a single original Garmin tdb file :-(
It seems that mkgmap writes some constants that might be impo
