POIs

P1.) Are POI name, description, category, address, email and phone fields supported? How many characters are supported in each of these fields?
P2.) Can I load geocaches as POI's? Can I create custom POI databases using GSAK on the Colorado?
P3.) Where are custom POI databases kept on the Colorado?
P4.) What if I want more than one custom POI database, can I do that?
P5.) I can't see POIs on the map screen. Can I fix this?
P6.) Can I create POI Proximity Alerts for Geocaches loaded to my GPSr?



General information and issues with waypoints, POIs (Points of Interest) and geocache handling can be found on the Waypoints page.

P1.) Are POI name, description, category, address, email and phone fields supported? How many characters are supported in each of these fields?


POI name, description, category, address, email and phone fields are supported and can contain up to 1023, 1023, 14, 150, 150 and 150 characters respectively. The Colorado automatically prefixes the phone and email field text with "Phone".

The limitation on the name and description field length may not be a Colorado limitation -- it appears to be a limit imposed by the POI loader when using CSV files. Users are reporting that the Colorado can display much more information that 1023 characters using GPX files.

P2.) Can I load geocaches as POI's? Can I create custom POI databases using GSAK on the Colorado?


Yes. Although you cannot use the Geocaching mode features of the Colorado with POIs, you can exceed the 2000 geocache limit by using a custom POI database. The easiest way to do this is use the procedure developed by pilotsnipes for Nuvi's as documented on his site. There is also an active thread on the groundspeak forums that shows screen shots of the Colorado in action using his GSAK-based tools.

There is also an advanced Nuvi POI GSAK macro written by jjreds for managing POIs on the Nuvi which applies to the Colorado (and Oregon). The download page for the macro is here and there is a groundspeak thread for support of the macro is here. Note the advanced version of the macro can be used to created custom POI databases for just about anything you can get into GSAK including waymarks, red light cams, speed cams, etc.

P3.) Where are custom POI databases kept on the Colorado?


The POI Loader installs the .gpi files into [drive]:\Garmin\POI\. By default it installs a file called poi.gpi.

P4.) What if I want more than one custom POI database, can I do that?


Yes. Just use the POI Loader to download the first poi.gpi file and rename the file so that the next download doesn't overwrite the first file. For more details see this FAQ.

P5.) I can't see POIs on the map screen. Can I fix this?


Yes. POIs are visible on the map based on your zoom level. Normally the more you zoom in the more detail you will see. You can change the zoom level settings by following the instructions below.

For custom POI's select Shortcuts->Setup->Map->Options->Advanced->Zoom Levels->User Waypoints-><n> Miles, where <n> is the zoom level below which you want custom POIs to show up. Note this setting will also change the Zoom Level where you can see waypoints.

For map POI's select Shortcuts->Setup->Map->Options->Advanced->Zoom Levels->Map Points-><n> Miles, where <n> is the zoom level below which you want map POIs to show up.

 

P6.) Can I create POI Proximity Alerts for Geocaches loaded to my GPSr?


Yes. See this Geocache Proximity Alert POIs tutorial so you never have to worry about accidentally missing another geocache again!.