![]() ![]() Garmin G2 units don’t recognise custom objects so its necessary to use the correct codes at all times, which means reconfiguring the mapping for units which recognise custom objects (if you need them), such as the GPSMap 60Csx and 276C. This may not be true for all units, but it is better to be safe than sorry! ![]() It has been found that some marine objects haven’t worked on the particular G2 units tested unless there is also a code “marine=y” in every objects “polish” description. In order to produce a Garmin chart that will display on a G2 unit it is necessary to put a “marine=B” code into the header. ![]() The skin file also changes the colours of the land and water polygon objects to more accurately represent a regular nautical chart – which makes things more understandable and familiar to work with This enables us to see objects such as Facility points and Information points – instead of just a question mark We’ve made a custom skin file containing the extended marine objects that we use – it’s simply an edited version of an uncompiled TYP file bundled with cGPSMapper. They need to work with cGPSMapper to enable us to produce marine charts GPSMapedit does not have a graphics set for the Garmin extended marine objects – so it is necessary to make our own. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |