Obviously this conclusions could be wrong, if you found one counter-example please provide it here so we can analyse it.
And YES the first two bytes in the header give you the size of the header. I'm not the only one saying this, see [Only registered and activated users can see links. ] and seacrh for "Header Length" string.
Also, there is not a "standard header size", you get the size from the first two bytes, it could change between different maps.
Regarding this i downloaded the Malsingmaps which are NT.(in this case this is the only one i analysed, no diversity here besides the several individual maps included)
What i found is that TRE, LBL and NET headers have a length as it is given in the first two bytes of each header, as in the non-NT/pseudo-nt maps.
On the contrary RGN and NOD headers don't. Further analysis make me to believe that the extra data for example in the RGN header, is in fact not part of the RGN header and is another header of x4a length (74 bytes) (info given in the first two bytes of this extra data). This extra header point to some "dictionary" data.
If you download Malsingmaps you will see what i mean.
It is difficult to explain here in a short comment, and it is useless to do so as i don't have any other relevant info.
The extra data in the NOD header doesn't seem to be another header.
From what i saw to convert from NT maps to non-NT maps it would take definitely more work and i think ¡'m not capable of doing this.
Last edited by testlelelala; 22nd August 2013 at 17:42.
That message number 0x1F78 ("The sub-map %s is in NT format which is not supported by GPSMapEdit.") can be shown from two different places.
One more patch
Code:Please Login or Register to see the links
Last edited by kunix; 25th September 2013 at 10:31.