Garmin H Owner's Manual
  1. Manuals
  2. Brands
  3. Garmin Manuals
  4. Software
  5. eTrex H - Hiking GPS Receiver
  6. Owner's manual
Garmin H Owner's Manual

Garmin H Owner's Manual

Vector maps creating
Hide thumbs Also See for H:
Table of Contents

Advertisement

Quick Links

cGPSmapper User Manual
First Published Date:
Version:
Published Date:
Total Page Count:
2005-04-01
2.1
2006-08-13
100

Advertisement

Table of Contents
loading

Related Manuals for Garmin H

Summary of Contents for Garmin H

  • Page 1 cGPSmapper User Manual First Published Date: 2005-04-01 Version: Published Date: 2006-08-13 Total Page Count:...

  • Page 2: Table Of Contents

    1 Contents CONTENTS ... 2 INTRODUCTION ... 5 URPOSE OF THIS DOCUMENT ... 5 ASIC ONCEPTS 2.2.1 What is Polish Format (PFM)? ... 5 2.2.2 What is cGPSmapper?... 5 2.2.3 What is sendmap?... 5 OCUMENT ONVENTIONS 2.3.1 PFM Code ... 5 2.3.2 cGPSmapper versions ...
  • Page 3 4.5.2 Concepts and Terminology... 45 4.5.3 Using Dictionary ... 45 CREATING CUSTOM TYPE FILE ... 47 REATING THE SOURCE FILE USTOM EFINITION UTTING IT ALL TOGETHER MAPSOURCE ... 61 OURCE ATA STRUCTURE REATING PREVIEW MAP FILES AKING THE REGISTRY ENTRIES OADING THE MAPS INTO THE FAQS ...
  • Page 4 cGPSmapper Manual Contents http://cgpsmapper.com/ 4 of 100...

  • Page 5: Introduction

    Feel free to e-mail your comments / contributions to the present document to manual@cgpsmapper.com. 2.1 Purpose of this document This manual explains how to create vector maps and then upload them to your Garmin GPS receiver (or see them in the MapSource software), utilizing the cGPSmapper / sendmap software.

  • Page 6: Cgpsmapper Versions

    preceded by a pair of statements with # metavariables, the whole pair should be repeated (see specific statements for examples). Text in orange colour (e.g. Name=) are mandatory statements in the given section. Text in olive colour (e.g. Label=) are optional statements. 2.3.2 cGPSmapper versions The table below contains the meaning of the different symbols used in this document to represent the cGPSmapper Version to which a certain concept applies.

  • Page 7: Overview

    Overview 3 Overview Creating a map to be uploaded to a GPS receiver may be compared to programming: you write a program (i.e. a map) in the programming language (i.e. in PFM) and then compile it. Alternatively - just as with programming - tools exist to generate the source code visually or semi-automatically or to assist in other ways in the code preparation.

  • Page 8: Map Project

    4 Map Project 4.1 Map Creation You write the source file in the PFM format (the .mp file) using any text editor. All map- related information is provided in relevant statements. Then the map is compiled with the cGPSmapper compiler and the resulting .img file is uploaded using sendmap or MapSource.

  • Page 9: Header

    Unique identifier (up to 8 decimal digits) for the map. May be only written in a decimal format 11000204 Map name to be displayed in the GPS receiver's Map Info menu. Refer to section 7.1 (on page 65) for details.
  • Page 10 Codepage=xx Datum=xxx Transparent=x MG=x π Numbering=x Routing=x http://cgpsmapper.com/ full-byte (8-bit) character coding with the specified codepage is used (depending on the GPS firmware) single-byte coding Note: All labels must be written in CAPITALS if a codepage is used Note: The delimiters for road numbers ( 4.2.6, on page 30, for details) are different if full-byte coding is used.
  • Page 11 Lock=x ProductCode=x τ CopyRight=xxxxxxx π Elevation=x POIOnly=x σ POIIndex=x τ π τ POINumberFirst=x π POIZipFirst=x τ π σ DefaultCityCountry =country_name τ π Same effect if switch -i is used. http://cgpsmapper.com/ Final IMG file will require unlock code specific for each GPS device.
  • Page 12 σ DefaultRegionCount τ ry=region_name π TreSize=n RgnLimit=n http://cgpsmapper.com/ Should be used in conjunction with DefaultCityCountry. Defines the default country name for automatic city indexing. If not defined, cities will be indexed only if city index info is explicitly provided. 80 characters maximum. Maximum allowed region size.
  • Page 13 PreProcess=x Levels=n Level#=g Zoom#=# http://cgpsmapper.com/ Kind of pre-processing: generalization only (faster method, but 'crossroad' nodes might be removed). Also the nodes from intersections may be removed. Data will be simplified using Douglas-Peucker polyline simplification algorithm which will ensure that the output is not jagged.

  • Page 14: Declarations

    Preview=x AlignMethod BlockSize LevelFill LevelLimit WorldMap DrawPriority=# Marine=x [END] 4.2.2 Declarations The DECLARATION elements must be in the order shown herewith. 4.2.2.1 Countries Although this section is obsolete, it is still supported. [COUNTRIES] Country#=country_n ame~[0x1d]abbrevia tion [END] 4.2.2.2 Regions Although this section is obsolete, it is still supported. [REGIONS] Region#=region_nam e~[0x1d]abbreviati...

  • Page 15: Cities

    CountryIdx#=countr y_index [END] 4.2.2.3 Cities Although this section is obsolete, it is still supported. [CITIES] City#=ciy_name RegionIdx#=region_ index [END] 4.2.2.4 Chart Info [CHART INFO] Name=xxx Number=xxx Projection=xxx Published=xxx Scale=### Unlikely, since each region normally is located in a single country. Unlikely, since each city normally is located in a single region.
  • Page 16 DeltaSN=### DeltaWE=### IALA=x Print=mmyyyy Edition=mmyyyy Correction=ddmmyyy σ Text=xxx τ π σ TextFile=file_name τ π http://cgpsmapper.com/ Longitude Delta. Latitude Delta. IALA system. The areas that use the 'B' system are the Americas, Japan and the Philippines. The remainder of the world uses the 'A' system. Default = A Paper chart print date.

  • Page 17: Advanced Declarations

    ReferenceEllipsoid =### [END] 4.2.3 Advanced Declarations The ADVANCED DECLARATIONS elements must be in the order shown herewith. 4.2.3.1 Background [BACKGROUND] Name=file_name [END] 4.2.3.2 Dictionary [DICTIONARY] http://cgpsmapper.com/ Reference Ellipsoid. Krassovsky Airy Modified Airy Australian National Bessel 1841 Bessel 1841 (Namibia) Clarke 1866 Clarke 1880 Everest (Brunei) Everest (India 1830)

  • Page 18: Highways

    Level#RGNnn=bitmas [END] 4.2.3.3 Highways This section will be further documented in a future version of this manual. [HIGHWAYS] [END] 4.2.3.4 ZIP Codes Although this section is obsolete, it is still supported. This section will be further documented in a future version of this manual. [ZIPCODES] [END] 4.2.3.5 Definitions...
  • Page 19 Name of the Highway. This name will be added to the list of available highways, so it can be searched in some GPS devices. Garmin does not support this feature. 80 characters maximum. has the same meaning as Label. [RGN20] CityName...

  • Page 20: Polygon

    σ CountryName=xxx τ π σ Zip=xxx τ π Exit#=(type_of_exi t_facility),(direc tion_to_facility), (facilities),(labe [END] 4.2.4.2 Polygon [POLYGON] Type=object_type SubType=object_typ Label=object_name EndLevel=# http://cgpsmapper.com/ Name of country to which the object belongs. Can be used only together with keys CityName. 80 characters maximum. Object Zip Code.
  • Page 21 Background=x Data#=(lat1,lon1), (lat2,lon2)... [END] Refer to section 4.2.1, on page 9, for further details. http://cgpsmapper.com/ Declare the custom shape of the map. The background object defines the area of the basemap which is covered by this map. It is recommended that background be only used with maps which have irregular boundaries.

  • Page 22: Polyline

    4.2.4.3 Polyline [POLYLINE] Type=object_type SubType=object_typ Label=object_name Label2=object_name EndLevel=# Data#=(lat1,lon1), (lat2,lon2)... StreetDesc=xxx DirIndicator=x σ CityName=xxx τ π σ RegionName=xxx τ π σ CountryName=xxx τ π σ Zip=xxx τ π RoadID=xxx π Numbers#=xxx http://cgpsmapper.com/ Polyline section identifier. [RGN40]may also be used instead. It is used to define linear objects such as streets, streams, etc.

  • Page 23: Point Of Interest From Oziexplorer

    Routeparam=xxx NodID#=xxx [END] 4.2.4.4 Point of Interest from OziExplorer [WPT] RgnType=object_cat egory Type=object_type EndLevel=# File#=file_name [END] 4.2.4.5 Polyline or Polygon from OziExplorer [PLT] RgnType=object_cat egory Type=object_type Label=object_name DirIndicator=# EndLevel=# http://cgpsmapper.com/ Section terminator. Point of interest section identifier, with data imported from an OziExplorer .wpt file.

  • Page 24: Shapes

    File#=file_name [END] 4.2.4.6 Shapes σ [SHP] τ π name=file_name Type=xxx LabelField=field_n Label2Field=field_ name TypeField=field_na SubTypeField=field _name http://cgpsmapper.com/ .plt file from which data will be imported to layer #. The path could be either absolute or relative to the current directory. For platform portability, it is recommended to use slashes "/"...
  • Page 25 DirField=field_nam Level=# EndLevel=# DefaultType=object _type σ CityName=field_nam τ π σ RegionName=field_n τ π σ CountryName=field_ name τ π τ HouseNumber=field_ name π τ StreetDesc=field_n π τ PhoneNumber=field_ name π http://cgpsmapper.com/ N or 0 Hide street direction on crossroads Y or 1 Show street direction on crossroads Default = N Level into which objects will be imported.
  • Page 26 - Can be adjusted in MapSource 40 km/h - Can be adjusted in MapSource 20 km/h 8 km/h (ferry) Used for routing. This attribute defines the importance of the road for routing. It is one of the most important attributes for routing.
  • Page 27 VehicleI=field_nam VehicleR=field_nam TextFileLines=fiel d_name TextStart=line_num TextEnd=line_numbe TextFile=file_name Color=field_name Style=field_name Height=field_name Depth=field_name DepthUnit=field_na HeightUnit=field_n Position=field_nam DepthFlag=field_na FoundationColor=fi eld_name Light=field_name LightType=field_na σ Note=field_name τ π σ LocalDesignator=fi eld_name τ π σ InternationalDesig nator=field_name τ π σ Period=field_name τ π http://cgpsmapper.com/ no bicycles allowed on the road. no trucks allowed on the road.

  • Page 28: Mapdekode File

    σ HeightAboveFoundat τ ion=field_name π σ HeightAboveDatum=f τ ield_name π σ HeightAboveFoundat τ ionUnit=field_name π σ HeightAboveDatumUn it=field_name τ π σ LeadingAngle=field _name τ π σ Racon=field_name τ π σ DoubleLights=field _name τ π σ DoubleLightsHorizo τ ntal=field_name π FacilityPoint=fiel d_name [END] 4.2.4.7 MapDekode file...

  • Page 29: File

    4.2.4.8 File [FILE] name=file_name [END] 4.2.5 Object elevation By default, the elevation is defined in feet in PFM. To define the elevation in metres, the Elevation=m statement should be defined in the header section ( 4.2.1 on page 9). Since this is a global definition, all elevations on a map must be in the same units (either all in feet or all in metres).

  • Page 30: Road Numbers

    [RGN10] Type=0x6616 Label=Table Mountain~[0x1f]1084 Origin0=(-33.96664,18.42569) [END-RGN10] 4.2.6 Road numbers Road numbers can be defined using NUMBERS# key within [RGN40] declaration. There could be up to 60 definitions of numbers for a single road. Each definition consist from the NumbersX definition where X is increasing value from 1 up to 60 [RGN40] Type=6...

  • Page 31: Marine Charts

    Numbering style can be: N,E,O,B – which suits to: None, Even, Odd, Both. 4.3 Marine Charts Marine charts are a special kind of cartography - similar to Garmin's BlueChart - that is used as navigational aid and contains its own set of marine elements.
  • Page 32 Label=object_name Data#=(lat,lon) EndLevel=# Marine objects may also have the following keys, depending on the object_type: σ Text=xxx τ π σ TextFile=file_name τ π Refer to section 4.2.1, on page 9, for further details. http://cgpsmapper.com/ Optional name of the object to be shown on the map. 80 characters maximum.
  • Page 33 Color=## Style=## Height=##.# http://cgpsmapper.com/ Object colour. Applies only to following marine types: polylines of types 0x04XX to 0x06XX points of types 0x0500 (coloured text) Valid values - sum of: 0x00 to 0x03 (basic styles) 0x10 to 0x30 (extended styles) 0x00 0x01 0x02 0x03...
  • Page 34 Warning: This value is not displayed if the “Spot Soundings” setting in the GPS receiver is set to “Off”. Please note also that this setting affects also some of the objects (mainly soundings): they will not be displayed at all (because they have no visual representation except the depth/height value).
  • Page 35 FoundationColor=# http://cgpsmapper.com/ Foundation colour. 0x00 (generic symbol) 0x01 0x02 green 0x03 yellow 0x04 white 0x05 black 0x06 black-yellow 0x07 white-red 0x08 black-red 0x09 white-green 0x0a red-yellow 0x0b red-green 0x0c orange 0x0d black-yellow-black 0x0e yellow-black 0x0f yellow-black-yellow 0x10 red-white 0x11 green-red-green 0x12 red-green-red 0x13...
  • Page 36 These are bearings of the light as seen from a vessel crossing the sector lines. Please note that you can change the “Light sectors” setting both in MapSource and in your GPS receiver to suit your needs. Applies only to following marine types:...
  • Page 37 LightType=xxx σ Note=xxx τ π http://cgpsmapper.com/ Definition of the light type. Can be a number (as decimal or hex) or a letter. If the value is a letter, then the light type is set to 0x0b (Morse code) and letter is used as a Morse code letter. Hex values: 0x00 unlit...
  • Page 38 σ LocalDesignator=xx τ π σ InternationalDesig nator=xxx τ π Period=xxx σ HeightAboveFoundat ion=## τ π σ HeightAboveDatum=# τ π σ HeightAboveFoundat ionUnit=## τ π σ HeightAboveDatumUn it=## τ π σ LeadingAngle=##.# τ π σ Racon=x τ π http://cgpsmapper.com/ Text visible in the properties window of the object. Applies only to following marine types: points of types 0x01XX and 0x02XX Text visible in the properties window of the object.

  • Page 39: Levels

    4.4 Levels 4.4.1 Introduction ® Every Garmin GPS with mapping capability gives you the option to zoom in or out on the map page, either displaying a small area in great detail, or a larger area in less detail. The selection of map objects which it is appropriate for the unit to display is dependent on the zoom level.

  • Page 40: Concepts And Terminology

    The approximate mapping of hardware zoom levels onto actual device zoom settings is shown in the table below. Note that this is only approximate. The matching of levels to ® Garmin display zoom levels is, unfortunately, not an exact science. Level no.
  • Page 41 EndLevel=n. The relationship between your chosen map zoom levels and the hardware zoom levels using a set of Levelm=h lines, where m is the map zoom level and h is the corresponding hardware zoom level.

  • Page 42: Using Levels When Defining Map Objects

    cGPSmapper Manual Map Project defining map objects. Map zoom level 3 is only used to dictate when our map replaces the base map. This means that you must always define one more map zoom level than you actually need for your map objects, and every map definition must therefore include at least two map zoom levels.

  • Page 43: Tailoring Shape According To Level

    cGPSmapper Manual Map Project [RGN10] Type=3328 Label=Remenham EndLevel=3 Data0=(51.551744,-0.889936) [END] What the EndLevel=n line says is that the coordinates in the highest numbered Datan= line apply up to the specified EndLevel=n, starting with the level number in the Datan= line. In our example, EndLevel=3, combined with Data0= means that the coordinates apply for three consecutive levels commending with level 0 (i.e.

  • Page 44: Idiosyncrasies Of Gps Hardware

    level. cGPSmapper automatically averages out consecutive points which are too close to be distinguishable on the GPS screen and discards unnecessary points. Nevertheless it is useful for the map author to understand how it is possible to take explicit control over the shape of map objects at different levels if and when necessary. 4.4.4 Idiosyncrasies of GPS hardware The foregoing sections have explained how the map author can control the levels at which map objects are displayed.

  • Page 45: Concepts And Terminology

    cGPSmapper Manual Map Project Fortunately the Polish file format has a solution called 'Dictionary' which allows you to switch map objects of the same type on or off for each level. [DICTIONARY] is an optional section and follows after the [IMG ID] section. 4.5.2 Concepts and Terminology [Dictionary] uses strings of 0's and 1's where the position of each digit in the string corresponds to a specific map object type and thus controls the display of that object type.
  • Page 46 The first two lines start with ';' indicating that these are comment lines and are ignored by cGPSmapper. They are there so that you do not need to actually count the digits to determine which one refers to which object code. [DICTIONARY] 1234567890123456789012345678901234567890123 Level1RGN40=1111110000000000000000000000000000000000000...

  • Page 47: Creating Custom Type File

    MyCustomTypes.txt Your custom .TYP file may be combined with .IMG files into GMAPSUPP.IMG for uploading into a compatible Garmin GPSr using SendMap 2.0 v3.3 or later, available at http://cgpsmapper.com/en/buy.htm. We believe that any Garmin receiver which works with Garmin’s POILoader may have custom type definitions installed with your .IMG file.
  • Page 48 cGPSmapper Manual Creating custom type file [_id] ProductCode=1 FID=888 [End] [_drawOrder] Section At a minimum, your input file must define the draw order for ALL polygon types – not just your custom ones. Even if you don’t define any custom polygon types in your source file, this section is mandatory.
  • Page 49 [_drawOrder] ;Type=POLYGON_CODE(HEX),PRIORITY Type=0x01,1 Type=0x02,1 Type=0x03,1 Type=0x04,1 Type=0x05,1 Type=0x06,1 Type=0x07,1 Type=0x08,3 Type=0x09,1 Type=0x0a,2 Type=0x0b,2 Type=0x0c,2 Type=0x0d,2 Type=0x0e,2 Type=0x13,2 Type=0x14,2 Type=0x15,2 Type=0x16,2 Type=0x17,3 Type=0x18,3 Type=0x19,3 Type=0x1a,4 Type=0x1e,2 Type=0x1f,2 Type=0x20,2 Type=0x28,1 Type=0x29,1 Type=0x32,1 Type=0x3b,1 Type=0x3c,8 Type=0x3d,8 Type=0x3e,8 Type=0x3f,8 Type=0x40,8 Type=0x41,8 Type=0x42,8 Type=0x43,8 Type=0x44,4 Type=0x45,2 Type=0x46,2 Type=0x47,2...

  • Page 50: Custom Type Definition

    Type=0x4e,5 Type=0x4f,5 Type=0x50,3 Type=0x51,6 Type=0x52,4 Type=0x53,5 [end] 5.2 Custom Type Definition Your custom type definitions will replace the default imagery on your GPSr or Mapsource. All other objects will be rendered with their default imagery. [_point] Definitions Points (POIs) define your replacement bitmap for the associated POI type using the XPM format.
  • Page 51 string1=0x04,Large city string2=0x08,Ciudad grande defines the string ‘Large city’ when the GPSr is set for English, and ‘Ciudad grande’ when the GPSr is set for Spanish. Refer to page 92 for more information about supported language types. Point bitmap definitions may be up to 24 x 24 pixels and 254 colors. There may be different definitions for the daytime bitmap and the nighttime bitmap.
  • Page 52 "X X" "X X" "XXXX" This definition describes a 4x4 rectangle with a black 1-pixel border and a transparent center. Refer to section 9.3.5 (How do I create XPM definitions?), on page 93 for a discussion of how to create XPM descriptions using a graphics editor and conversion tools. http://cgpsmapper.com/ 52 of 100...
  • Page 53 [_line] Definitions Line definitions are used to replace the standard polyline types, including roads. There are two ways to define a line. You may either declare the line’s color and thickness attributes for its interior and border, or you may provide a custom bitmap. Both methods allow transparency in the definitions.
  • Page 54 Line declaration method 2: Describe a bitmap using XPM. [_line] Type=0x0a Xpm="32 5 4 1" "= c #b0b0b0" " c none" "3 c #585858" "4 c none" "================================" " ======= " ======= " ======= "================================" ;12345678901234567890123456789012 string1=0x04,Unpaved string2=0x08,Camino revistida [end] The first line of the xpm declaration indicates a definition 32 pixels wide, 5 pixels tall, with 4 colors, using 1 character for the pixel representations in the bitmap.
  • Page 55 Manual Creating custom type file In this screen capture from a Garmin nüvi, four polygon types are shown. The one on the left is a custom definition (described below), and the following three are standard type 0x4F, 0x50 and 0x51. The black boxes show 32x32 tiles. Notice that the leftmost tile uses two colors, while the next three tiles use transparency.
  • Page 56 [_polygon] Type=0x4e string1=0x04,Wilderness string1=0x08,Yermo xpm="32 32 4 1" "! c #faf889" "# c #77c1c2" "3 c #77c1c2" "4 c #faf889" "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!" "#!!!!!!!!!!!!!!!!!!!#!!!!!!!!!!!" "#!!!!!!!!!!!!!!!!!!##!!!!!!!!!!!" "!!!!##!!!!!!!!!!!!!!!!!!!#!!!!!!" "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!" "!!!!!!!!!!!!!!#!!!!!!!!!!!!!!!!!" "#!!!!!!!!!!!!!!!!!##!!!!!!!!!!!!" "!!!##!!!!!!!!!!!!!!!!!!#!!!!!!!!" "!!!!#!!!##!!!!!!!!!!!!!#!!!!#!!!" "!!!!!!!!##!!!!!!!!!!!!!!!!!!!!!!" "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!" "!!!!!!!!!!!!!!!!!##!!!!!!!!!!!!!" "!!!!!!!!!!!!!!!!!!!!!!##!!!!!!!!" "!!!!!!!#!!!!!!!!!!!!!!#!!!!#!!!!" "!!!!!!!!!!!##!!!!!!!!!!!!!!!!!!!" "!!!!!!!!!!!!!!!!#!!!!!!!!!!!!!!!" "!!!!!!!!!!!!!!!!!!!!!#!!!!!!!!!!" "!!!!!##!!!!!!!!!!!!!##!!!!!!!!!!" "!!!!!!#!!!##!!!!!!!!!!!!!!!!!!!!" "!!!!!!!!!!##!!!!!!!!!!!!!!!!!!#!" "!!!!!!!!!!!!!!!#!!!!!!!!!!!!!!!!"...

  • Page 57: Putting It All Together

    5.3 Putting it all together If you are serious about creating custom types, I recommend that you prepare a small Polish format test file so that you can quickly check your work. Once you have things the way you want them, then you should apply your TYP file to your larger maps. I use MapSource to test my work in progress, as it is much quicker than making a GMAPSUPP.IMG file and downloading it to the unit.
  • Page 58 cGPSmapper Manual Creating custom type file Sample screens from MapEdit of CustomDemo.mp: http://cgpsmapper.com/ 58 of 100...
  • Page 59 cGPSmapper Manual Creating custom type file Sample screen from MapSource of CustomDemo.img: http://cgpsmapper.com/ 59 of 100...
  • Page 60 cGPSmapper Manual Sample screens from nüvi: Standard roads and cities Standard Scrub, camping, mountain range http://cgpsmapper.com/ Creating custom type file Custom roads and cities Custom scrub, camping, mountain range 60 of 100...

  • Page 61: Mapsource

    PC, and also uploading the map data to mapping-capable GPS units. The MapSource program is included with maps bought from Garmin. The same program is shared between the various map sets that Garmin supplies. Recently, Garmin have been supplying MapSource 'Trip and Waypoint manager' free with their mapping GPS units.
  • Page 62 If you plan on distributing your maps, it is NOT a good idea to use the default value - i.e. 66 for the product ID. Rob Mech runs an 'Unofficial Garmin Product ID Database - UGPID' on keenpeople.com - where you can register an ID that hopefully only you will use.

  • Page 63: Loading The Maps Into The Gps

    6.4 Loading the maps into the GPS 1. Choose the map(s) Once in MapSource, the map(s) to be loaded in the GPS must be chosen first. This is done via any of the following methods: Under Switch to Product, in the View menu. Via the corresponding combo located in the View Toolbar.
  • Page 64 2. Select the map(s) The map(s) to be loaded in the GPS must be selected. This is done via any of the following methods: Under Map, in the Tools menu. Via the respective button located in the Tools Toolbar. Once this is done, the map to be selected must be clicked (in order to select it). The maps to be transferred to the GPS (and the bytes they occupy) will be shown to the left of the screen.

  • Page 65: Faqs

    • sendmap options. There are various locations where the name data is displayed both on the GPS unit and in the Garmin MapSource software. Figure 4 shows the relationship between where the name data is specified and where it is displayed.

  • Page 66: Sendmap

    MapVersion=nnn Copy1=xxxxxxx Copy2=xxxxxxx Copy3=xxxxxxx 11.2.3 Sendmap The name data specified when using Sendmap is used to describe a collection of PFM files. The name data is specified as command line options. Sendmap –M "MapSetName" filename1.img [filename2.img] […] http://cgpsmapper.com/ The software version of the CDSetName. This field is not displayed on the GPS unit.
  • Page 67 cGPSmapper Manual FAQs Figure 4: How name variables are shown http://cgpsmapper.com/ 67 of 100...

  • Page 68: Activation Of Maps In The Gps

    7.2 Activation of maps in the GPS 1. Activation of the map(s) in the GPS If the map image is not shown in the GPS, check that the map is selected to be shown. The method for doing this depends on the GPS model. For example you may find it on the MapSource Info screen, accessed from the unit's main menu or on the information page of the Setup Map screen.

  • Page 69: Saving Objects As [Rgnx0] Vs. [Poi], [Polygon], [Polyline]

    7.3 Saving Objects as [RGNx0] vs. [POI], [POLYGON], [POLYLINE] 7.3.1 Equivalences Notation 1 Notation 2 [POLYLINE] [RGN40] [POLYGON] [RGN80] [POI] City=Y [RGN20] [END] [POI] City=N (or no city key) [RGN10] [END] [POI] covers both [RGN10] and [RGN20]. The difference is made with the 'City=y' key. 7.3.2 Impact of saving objects in one format or the other There is no impact.

  • Page 70: Filling (Gas) Stations Not Showing In The Find Function Of The Gps

    cGPSmapper Manual FAQs Level0=18 Level1=17 Zoom0=5 Zoom1=6 (Does not overlap with detail IMG file) 7.5 Filling (Gas) Stations not showing in the find function of the GPS Use 0x2F01 (instead of 0x4400) if you want to show it in the find function of your GPS receiver.

  • Page 71: Glossary

    Polish format map files cannot be sent directly to a GPS unit. First they must be converted into a format which is understandable to your GPS receiver. A program that performs this conversion is called a "map compiler".

  • Page 72: Appendices

    When the TreSize value in [IMG ID] is too big - the resulting map IMG file renders more and more slowly on a GPS receiver. This value should never be higher than 5000. If the value is larger than 5000, it is internally changed to 5000 and the warning is shown.
  • Page 73 V Code Warning / Error Text W018 ID of map should be larger than 0x10000 (65536) or may not work in MapSource. W019 More than ONE background object defined - switching to full manual background creation mode. E001 Could not open file with country name definitions.
  • Page 74 V Code Warning / Error Text E018 Type of element for RGN40/RGN80 cannot be higher than 128. E019 Street cannot intersect with itself! Split this element! E020 No more than 8 active layers allowed. E021 Grid definition for layers must be descending (check Level# keys in [IMG ID]).
  • Page 75 V Code Warning / Error Text E025 Zoom definition for layers must be ascending (check Zoom# keys in [IMG ID]). E026 More than 65535 Tre regions were created in a single layer - use bigger TRESIZE and RGNLIMIT or split your map.

  • Page 76: Exits

    V Code Warning / Error Text R007 Node reduction. R008 Too short road to be routable - coordinates were aligned to same place R010 No data for routing - remove 'ROUTING=Y' from [IMG for non routable maps! R011 NODID points cannot be closer than 5.4 meter! R012 NODID point defined for non...

  • Page 77: Facilities

    9.2.3 Facilities Facilities can be combined - i.e. facility with Car Wash + Open 24 Hours is 0x48 Mnemonic Description 0x01 HGV/RV Parking 0x02 Convenience Store 0x04 Diesel Fuel 0x08 Car Wash 0x10 Liquid Propane 0x20 HGV Scales 0x40 Open 24 Hours 0x80 not used 9.3 cGPSmapper object types list...
  • Page 78 Code Code (Hex) (Decimal) 0x2700-0x273F 9984-10047 0x2800-0x283F 10240-10303 0x2A00 10752 0x2A01 10753 0x2A02 10754 0x2A03 10755 0x2A04 10756 0x2A05 10757 0x2A06 10758 0x2A07 10759 0x2A08 10760 0x2A09 10761 0x2A0A 10762 0x2A0B 10763 0x2A0C 10764 0x2A0D 10765 0x2A0E 10766 0x2A0F 10767 0x2A10 10768 0x2A11...
  • Page 79 Car Repair Airport Post Office Bank Car Dealer (point) Bus Station Marina Wrecker Service Parking Restroom Automobile Club Car Wash Garmin Dealer Personal Service Business Service Communication Repair Service Social Service Utility Truck/Lorry Stop Generic Emergency/Government Police Station 79 of 100...
  • Page 80 Code Code (Hex) (Decimal) 0x3002 12290 0x3003 12291 0x3004 12292 0x3005 12293 0x3006 12294 0x4000-0x403F 16384-16447 0x4100-0x413F 16640-16703 0x4200-0x423F 16896-16959 0x4300-0x433F 17152-17215 0x4400-0x443F 17408-17471 0x4500-0x453F 17664-17727 0x4600-0x463F 17920-17983 0x4700-0x473F 18176-18239 0x4800-0x483F 18432-18495 0x4900-0x493F 18688-18751 0x4A00-0x4A3F 18944-19007 0x4B00-0x4B3F 19200-19263 0x4C00-0x4C3F 19456-19519 0x4D00-0x4D3F 19712-19775 0x4E00-0x4E3F 19968-20031...
  • Page 81 Code Code (Hex) (Decimal) 0x6403 25603 0x6404 25604 0x6405 25605 0x6406 25606 0x6407 25607 0x6408 25608 0x6409 25609 0x640A 25610 0x640B 25611 0x640C 25612 0x640D 25613 0x640E 25614 0x640F 25615 0x6410 25616 0x6411 25617 0x6412 25618 0x6413 25619 0x6414 25620 0x6415 25621 0x6416...
  • Page 82 Code Code (Hex) (Decimal) 0x6602 26114 0x6603 26115 0x6604 26116 0x6605 26117 0x6606 26118 0x6607 26119 0x6608 26120 0x6609 26121 0x660A 26122 0x660B 26123 0x660C 26124 0x660D 26125 0x660E 26126 0x660F 26127 0x6610 26128 0x6611 26129 0x6612 26130 0x6613 26131 0x6614 26132 0x6615...
  • Page 83 Code Code (Hex) (Decimal) 0x1B02 6914 0x1A02 6658 0x1902 6402 0x1802 6146 0x1702 5890 0x1602 5634 0x1B03 6915 0x1A03 6659 0x1903 6403 0x1803 6147 0x1703 5891 0x1603 5635 0x1B04 6916 0x1A04 6660 0x1904 6404 0x1804 6148 0x1704 5892 0x1604 5636 0x1B05 6917 0x1A05...
  • Page 84 Code Code (Hex) (Decimal) 0x1B09 6921 0x1A09 6665 0x1909 6409 0x1809 6153 0x1709 5897 0x1609 5641 0x1B0A 6922 0x1A0A 6666 0x190A 6410 0x180A 6154 0x170A 5898 0x160A 5642 0x1B0B 6923 0x1A0B 6667 0x190B 6411 0x180B 6155 0x170B 5899 0x160B 5643 0x1B0C 6924 0x1A0C...
  • Page 85 Code Code (Hex) (Decimal) 0x1B10 6928 0x1A10 6672 0x1910 6416 0x1810 6160 0x1710 5904 0x1610 5648 0x1B11 6929 0x1A11 6673 0x1911 6417 0x1811 6161 0x1711 5905 0x1611 5649 0x1B12 6930 0x1A12 6674 0x1912 6418 0x1812 6162 0x1712 5906 0x1612 5650 0x1B13 6931 0x1A13...
  • Page 86 Code Code (Hex) (Decimal) 0x0100 0x0102 0x0103 0x0104 0x0105 0x0106 0x0107 0x0108 0x0109 0x010a 0x0200 0x0201 0x0202 0x0203 0x0204 0x0205 0x0206 0x0207 0x0208 0x0209 0x020a 0x020b 0x020c 0x020d 0x020e 0x020f 0x0210 0x0211 0x0212 0x0213 0x0214 0x0215 0x0216 0x0217 0x0218 0x0300 0x0301 0x0302 0x0303...
  • Page 87 Code Code (Hex) (Decimal) 0x0307 0x0308 0x0309 0x030a 0x030b 0x0400 1024 0x0401 1025 0x0402 1026 0x0403 1027 0x0404 1028 0x0405 1029 0x0406 1030 0x0407 1031 0x0408 1032 0x0409 1033 0x040a 1034 0x040b 1035 0x040c 1036 0x040d 1037 0x040e 1038 0x040f 1039 0x0500 1280...

  • Page 88: Polyline] Types

    9.3.2 [POLYLINE] types Code Code (Hex) (Decimal) 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0a 0x0b 0x0c 0x14 0x15 0x16 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x1e 0x1f 0x20 0x21 0x22 0x23 0x24 0x25 0x26 0x27 0x28 0x29 0x2a 0x2b 0x0100...
  • Page 89 Code Code (Hex) (Decimal) 0x0106 0x0107 0x0108 0x0109 0x0300 0x0301 0x0307 0x0400 1024 0x0401 1025 0x0402 1026 0x0403 1027 0x0404 1028 0x0405 1029 0x0406 1030 0x0407 1031 0x0408 1032 0x0409 1033 0x040a 1034 0x040b 1035 0x040c 1036 0x0500 1280 0x0501 1281 0x0502 1282...

  • Page 90: Polygon] Types

    Code Code (Hex) (Decimal) 0x060d 1549 0x060e 1550 0x060f 1551 0x0610 1552 0x0611 1553 0x0701 1793 0x0702 1794 0x0706 1798 9.3.3 [POLYGON] types Code Code (Hex) (Decimal) 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0a 0x0b 0x0c 0x0d 0x0e 0x13 0x14...
  • Page 91 Code Code (Hex) (Decimal) 0x3d 0x3e 0x3f 0x40 0x41 0x42 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0x4b 0x4c 0x4d 0x4e 0x4f 0x50 0x51 0x52 0x53 0x0100 0x0101 0x0102 0x0103 0x0104 0x0105 0x0300 0x0301 0x0302 0x0303 0x0304 0x0305 0x0306 0x0307 0x0400 1024 0x0401...

  • Page 92: Custom Types Name Substitution

    Code Code (Hex) (Decimal) 0x0406 1030 0x0407 1031 0x0408 1032 0x0409 1033 0x040a 1034 0x040b 1035 0x040c 1036 0x0500 1280 0x0501 1281 0x0502 1282 0x0503 1283 0x0504 1284 0x0505 1285 0x0506 1286 0x0507 1287 0x0508 1288 0x0600 1536 0x0601 1537 0x0602 1538 0x0603...

  • Page 93: How Do I Create Xpm Definitions

    String3=0x04,Highway String4=0x08,Carretera LineWidth=5 BorderWidth=1 xpm="0 0 4 0" colors (4) "1 c #20c818" "2 c #309838" "3 c #20c818" "4 c #086808" [end] Code Language 0x00 Unspecified 0x01 French 0x02 German 0x03 Dutch 0x04 English 0x05 Italian 0x06 Finnish 0x07 Swedish 0x08 Spanish...

  • Page 94: Cgpsmapper Versions

    Resize as needed to your target dimensions. • Save in PNG-24 format with transparency. • IconXP steps: Go to http://www.aha-soft.com/iconxp/index.htm • of IconXP. (The registered version is $20US) Open your .PNG file from Photoshop. • Export As .XPM • Microsoft Word steps: Open the .xpm file.
  • Page 95 • Direct support for ESRI shape format • City and POI indexing is limited to 100 cities and POIs in standard maps. Indexing means that cities and POIs may be searched using the GPS receiver's "Find by name" function (subject to the receiver limitations).

  • Page 96: Cgpsmapper Files

    Version Routable Marine 9.5 cGPSmapper files This section will be further documented in a future version of this manual. The table below lists the contents of the main files that are distributed with the compiler. File cGPSmapper-Help .txt cgpsmapper.exe Datum_List.txt Readme.first Readme0080.txt RGNtype.txt...

  • Page 97: Index And Tables

    10 Index and Tables 10.1 Table of Figures IGURE LESS DETAIL MAP EXAMPLE IGURE MORE DETAIL MAP EXAMPLE 3: M IGURE ETAIL ETUP 4: H IGURE OW NAME VARIABLES ARE SHOWN 10.2 Version Control Log Ver# Date Edited by 2005-04-01 M. Zalba 2005-04-04 H.Scheffler...

  • Page 98: Index

    10.3 Index [_drawOrder] ... 47 [_ID] ... 46 [_line] ... 52 [_point] ... 49 [_polygon] ... 53 [CHART INFO]... 15 [CITIES] ... 14 [COUNTRIES] ... 13 [DICTIONARY]... 16, 44 [FILE] ... 28 [IMG ID] ... 9, 64 [MAP]... 64 [PLT] ... 22 [POI] ...
  • Page 99 valid exit facility types ... 75 Exit# ... 19 Exits... 75 FacilityPoint ... 27, 38 File ... 28 File# ... 22, 23 files shipped with cGPSmapper ... 95 FoundationColor... 26, 34 Gas Stations ... 69 Glossary... 70 Header... 9 Height ... 26, 32 HeightAboveDatum...

  • Page 100: Http://Cgpsmapper.com/ 3 Of

    PreProcess... 12 Print ... 15 Projection... 15 Published ... 15 Racon ... 27, 37 ReferenceEllipsoid... 16 Region... 14 RegionIdx ... 14 RegionName ... 18, 21, 24 Regions ... 14 RgnLimit... 12 RgnType ... 22 RoadClass ... 25 RoadID ... 25 Routing ...

This manual is also suitable for:

Cgpsmapper

Table of Contents