Question about naming conventions and 'Features'
Wed, 12/02/2009 - 7:43pm
 |
   16 years
|
The more I work with TourGuide, the more I like it...
Being able to use the same POI's for either "On this road" or "Near this road" is great....
Seeing that the naming convention is the way the Garmin determines how to treat this data.... The question seems to be needed to be asked:
Is there any other naming conventions that will change the way the Garmin will react for the same search data?
Example:
CrackerB.csv is treated as: "On this road"
CrackerB TourGuide.csv is treated as: "Near this road"
Is there any other naming conventions that will alter the way this data is treated by the Garmin?????
Thanks
This is stright from
This is stright from poiloader help.
POI Loader determines whether or not a file contains speed and proximity alert points based on specific criteria. Use the following information to help you create Custom POI files:
If a file name contains a valid speed number or if all records in a file have speed encoded in the name, then all records in the file will include speed and proximity alerts. For example, a data file with the file name "Speed_30" generates speed alerts of 30 mph (or kph, depending on the type of units selected in POI Loader) for each POI in the file.
If the file name contains "redlight", POI Loader assumes all records in the file have proximity alerts with a distance of 400m/0.25 miles.
If a file contains "GATSO," "mobile," "SPECS," "safety," "speed," or "camera," but does not have a speed, POI Loader uses a default alert speed of 0, which means you will always be alerted. You can override this default value by entering the speed in Manual mode.
You can also enter speeds for each POI individually by adding the @ symbol and a number after the name of the POI. For example, a Custom POI named "Ridgeview@25" would create a POI named "Ridgeview" with a 25 mph speed alert.
POI Loader calculates proximity alert distance based on speed. You can enter proximity alert distance for individual Custom POIs in a .gpx file. You can also enter proximity alert distance for all Custom POIs in a data file using Manual mode.
Proximity alert distance calculated by POI Loader based on speed information in the file name or in individual POI names. This calculation uses the following formula:
Prompt Distance = 36 seconds * Speed.
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. MapFactor Navigator - Offline Maps & GPS.
.
@JanJ:
You might find this post on TOurGuide files interesting:
http://www.poi-factory.com/node/13904
The "Creating TourGuide Files" section of POI Loader Help states that they must be saved in .gpx format (even though they work as .csv):
"TourGuide is a feature available on compatible Garmin devices. TourGuide files include Custom POIs with descriptive .mp3 audio files. When you approach a TourGuide point, the .mp3 file plays and provides you with information about that point, much like a guided tour. TourGuide files must be saved as .gpx files."
Nüvi 2595LMT