I see one interesting think on latest map edition. TYP file is ugly big. On this map the TYP is bigger map. May be for each object there is TYP in Herbew?!
And request for Copov. In mdr section of modified img replaced many HEX values like CP but it is not CP value actually. My friend have some problem with routing on modified map just on previous version.
CN Israel NT 2012.30 for GMPC, GMXT and Garmin device without Hebrew (cp1255 to cp1252)
In simple terms: what does it mean: "cp1255 to cp1252"?
Originally Posted by Giomen
TYP file is ugly big. On this map the TYP is bigger map. May be for each object there is TYP in Herbew?!
And request for Copov. In mdr section of modified img replaced many HEX values like CP but it is not CP value actually.
Just so I can learn from all this as well... can someone explain in understandable terms what the TYP file is about, what CP values are and how this affects the map?
In simple terms: what does it mean: "cp1255 to cp1252"?
Just so I can learn from all this as well... can someone explain in understandable terms what the TYP file is about, what CP values are and how this affects the map?
A code page tells how to parse the byte code to a character. Some sets may use multi-byte codes for Asian languages like Chinese and Japanese.
CP 1255 = Windows Code Page 1255 / Hebrew Alphabet / Superset of ISO 8859-8
TYP files are used to customize the look and feel of map elements (roads, trails, fields etc.). It's not all Garmin units that use the TYP info. The main purpose for editing TYP data would be to enhance readability of the preferred information for specific usage. It's also useful for differentiated usage on different GPS screens with different resolution and color capabilities. One map might look good on one type of unit but looks awful on another.
original vs. TYP altered
[Only registered and activated users can see links. ]
Bookmarks