Try: Numbers1=2,E,100,200,O,101,199
I really hope that old cgpsmapper is not good enough to kick out of business 3-rd party map publishers like CarteBlanche.
Perhaps it has a bug when left or right are undefined (none).
I'll check.
But the roads numbers i checked, all are okay, but they have both sides defined left and right numbering.
example: Numbers1=1,E,100,200,O,101,199
Last edited by testlelelala; 6th August 2013 at 09:34 AM.
Try: Numbers1=2,E,100,200,O,101,199
I really hope that old cgpsmapper is not good enough to kick out of business 3-rd party map publishers like CarteBlanche.
I also hope that no one get kicked out of business.
But i do hope that old cgpsmapper do things right (as it seems to be for the moment.)
Internal structure of Garmin NT format is not known. This thread is not about revers engineering Garmin NT maps but about disassembling maps from independent publishers, who use cgpsmapper.
I don't really believe that people who reverse engineered non-NT IMG files can't do the same with NT IMG files There should be some other reasons... Like all of them being involved in some economic relations which make decompiling NT maps by others not desirable
Last edited by kunix; 6th August 2013 at 10:42 PM.
gimgtools is a very nice set of utilities. But they still don't help us convert NT maps to polish map format, while we can do this for non-NT maps using some utilities (gpsmapedit, for example). Also I don't see how to convert NT map to non-NT one using gimgtools.
In conclusion, gimgtools still doesn't help us decompile NT maps, even partially.
Last edited by kunix; 7th August 2013 at 10:19 AM.
Garmin, how much is 30 pieces of silver for Judas today? Were they worthy for crucifix of GPSPower?
As you have found out, the difference between two, say TRE, headers are the contained offset values pointing to data sections in the TRE data area. In a NT or pseudo-NT GMP subfile the offset is always relative to the start of GMP header. But in a non-NT TRE/RGN/LBL subfile, the offset is relative to the start of TRE/RGN/LBL header respectively. So, for example, after you join a TRE header with its TRE data area (both from a pseudo-NT file), you need to update those offsets in TRE header to be relative to the start of the TRE header.
The location of an offset within a non-NT subfile header can be found in the document below.
[Only registered and activated users can see links. ]
Bookmarks