Академический Документы
Профессиональный Документы
Культура Документы
Follow the steps below paying close attention to each step to create a custom mapset of tracks/waypoints:
1. 2. 3. 4. Convert your tracks to a .gpx file. (Mapsource works) Open Mapsource and resave your file as a .gpx file. Open GPSMapEdit program. Click File > Open and choose your gpx file. (NOTE: you can File > Add multiple gpx files into one session of GPSMapEdit.) Click on File > Map Properties and do the following: a. Change type set to Garmin b. Give the map an 8 digit ID number (must be all numbers, no spaces) c. Give the map a name d. Click on the Levels tab and Highlight the bottom or last Level in the series and then click on the Insert Before tab, do this until you have Level0= through Level4=. e. Click on Change and make the settings look like this: i. Level0=24 bits/Mapsource zoom=under1.2km ii. Level1=23 bits/Mapsource zoom=1.2-3km iii. Level2=22 bits/Mapsource zoom=3-8km iv. Level3=20 bits/Mapsource zoom=8-12km v. Level4=19 bits/Mapsource zoom=12-30km Click OK which takes you back to your tracks. Click on Edit > Select all tracks. Right click on any 1 of your tracks and select Convert to polylines. This will bring up a levels box. Check the levels 0,1,2 boxes and hit OK. (Note: If you want 1 or a few of your tracks to appear on your GPSr at zoom levels showing very large areas, zoom level 80 mi., then also check level 3 for those items. This makes your custom map easier to find on your GPSr screen.) Repeat Steps 6 & 7 if you want Waypoints on your map but instead of converting to polylines convert to Points. (NOTE: Be sure you want waypoints on your map because you may be duplicating points on your map with Waypoints you keep in your GPSr and this will clutter the viewing of your map. Also, the icons may not match each other.) The type box will come up. Select walkway/trails then OK. You can change this to anything you want to have the tracks appears as on the GPS different. I use International Boundary and is easier to see on my GPS (shows up deep blue). Primary Road shows up well (red in color), but will need to change it to level 0 in order to view it at the 0.3 mile scale on the GPS. The 0.3 mile scale on the GPS is the least detailed zoom size that will show your custom map features. (Garmin 60CSx - You can change the Main Menu > Setup > Map (Map Setup General) and change Detail from Normal to More and your tracks will appear at the 0.5 mile zoom level. Right click on the track and select Detach file. (This gets rid of your track file but keeps the converted file that you already did. If you want to see your file click on view, then levels and select level 0). If you right click on the track and nothing happens then go to Edit > All tracks and put cursor over any 1 of your tracks and right click. Then click Detach Files. Click on File > Map Properties and select the cGPSMapper Tab. Check the Map is transparent box and select Y transparent map without background object then click Apply and click OK. Click on File > Save map as and save your file in type Polish format (this is the default). Click on File > Export GarminIMG/cgpsmapper.exe. (This program has to be downloaded prior so look at the website in this step), name your file and save it, then search for the cgpsmapper.exe file that you saved earlier and click on run and wait until it says Export is complete and click Ok. Of GPSMapEdit Find your newly created .img file and change the name to the 8 digit number that you gave the map in step 4b. You can now send the map image to your GPS or Mapsource. Continue for Mapsource download capability.
5. 6. 7.
8.
9.
16.
17.
Create and compile your map using cGPSmapper. You must give it a name of all numbers: ex. 10000123.img. (You already did this in Step 14.) (Note: Your map name of all numbers must be an 8 digit number larger than 10000 or it may not appear correctly in Mapsource.) Create a folder named Custom under the C:/Garmin folder and copy your custom map to it. Copy cGPSmapper.exe to the same folder.
15. Click the START button to generate the TYP file. Name your file (a fairly short name without Spaces I like to use ex. number of colors 12Colors which is the number of elements in my TYP file). Save As a .txt file in your C:/Garmin/Custom folder. 16. A box with Generation complete will appear and click Ok. END of GenTYP
Start MapSetToolKit
Mapsource automatically makes the registry changes for you. See this link for the MapSetToolkit v1.40: http://cypherman1.googlepages.com/home (Thanks to Cypherman for simplifying this process) Note: Numbering of Steps purposely starts with Step 5 to correspond with other MapSetToolKit Instructions used when making Custom Topo Maps. 5. Open MapSetToolkit 1.40. Click on Select IMG files and click on folder C: > Garmin > Custom. 6. Select your .img file or files and click Add. 7. In Create MAPSET Box: A. For Mapset Directory click on and select the folder C: > Garmin > Custom. B. Enter a name in the Mapset Name field. (Spaces between characters is allowed) (This is what will show up in Mapsource in the Select a Product such as CN, Topo, Custom Maps, etc.) C. For Family ID enter a number between (1-65535). Make sure this number is not being used in any other Families ID. (Look at Uninstall Mapset box and verify your FID number is not used.) (After you have entered a FID number the Product Code is over written with 1.) D. In Product Code enter a number between (1-9999). Make sure this number is not being used in any other Mapset Product codes. E. In Map version enter your version such as 1.00. F. In Copyright info type Text. This field does not display on GPSr but this field is displayed in Mapsource when displaying Mapsource Product information. (If you want to use a .TYP file or registered your MapSet in families, continue to Step G, otherwise go to Step 8.) G. For TYP files, if you have a custom type definition (.TYP file), then click on and select your file. (You will only need to fill in this box if you created a .TYP file to customize lines, points, or polygons.) If you select .txt file, MapSetToolKit will compile this file when you click on START button. 8. Check the Install in Mapsource box and check the Blank overview maps box ((this will prevent seeing a double track (high resolution and low-resolution lines) when zoomed in close in Mapsource)). In the cgpsmapper box click on . Select cgpsmapper.exe program and click Open.
9.
10. Click on START. Then box will pop up saying Convert termined and click Ok. 11. Verify your Mapset name and Code you assigned in Step 7-B & C are now in the Uninstall Mapset list box. 12. Now you can go to Mapsource and install them to your GPSr with .TYP file. You dont need another program to send your .TYP file to you GPSr if your Product Code and FID in your .TYP file is the same as in Steps 7-C & 9-A. Mapsource will send your .TYP file for you with your selected maps. If you used the same values in your .TYP file and MapSetToolKit for Product Code and FID, Mapsource will send your maps and also your .TYP file to your GPSr. (Ignore this step if not using a .TYP file.) NOTE: If you want to add a new map to your existing Mapset you must first uninstall the existing Mapset using the MapSetToolKit, Uninstall Mapset list and create the same Mapset name again. END of MapSetToolKit 13. Open Mapsource, you should now see your mapset listed in MapSource along with your other Garmin maps in the Product list. 14. Select (click) on your map in the Product list and the preview map will show up in the map area on your screen. On the Mapsource Toolbar change your Detail Settings to Highest and zoom in to see your custom map. You may have to zoom in to a Map Scale/Zoom Level of 2 miles or less before your map starts to display. 15. You should now be able to use the Map Tool to select your custom map/s for uploading and upload it with your other maps such as U.S. Topo, City Navigator, and etc. maps. These instructions were prepared by EAParks. Thanks to Groundspeak members GeoBobC, Bus36, and Cypherman for their technical expertise. This process would not be possible without the time and dedication Cypherman has been willing to share with fellow GPSers. Rev.8; 7-30-2008