Proximity Alerts

Not with a CSV file.

Phil will probably be along to detail how you can do it with a GPX file which is probably the preferred method. (Well, maybe he'll be around tomorrow. It's late in the UK right now.)

Another way around this is to load the POIs that you want (setting the alert) with POI Loader. And then rename the GPI file on your GPS unit so that it won't get overwritten. I don't usually initially recommend this method because it doesn't work correctly on all units.

But for the ones that it does work (and it will work on the 660), if you for example load Starbucks and set a proximity alert of 2000 feet, you could rename the POI.GPI file to Starbuck.gpi. Then the next time you run POI Loader that GPI file wont' be overwritten and the POIs and the alerts that you set will be intact.

You can also use the special keywords in the file name (redlight, speed, etc) but you can't control the distance with these as it is preset.

OK, does this mean that I should load/rename POI categories one at a time, for example, if I load rest areas and starbucks in a single poi loader session there appears to be only one poi.gpi file, containing both rest areas and starbucks combined. By loading and renaming individually I'd be able to go in and change/delete one without affecting others?

also, I load to the SD card in my nuvi 660. in examining the files created on the card I see a "Garmin" folder and a "POI" folder. Within the "Garmin" folder is a "POI" folder and within that folder is a poi.gpi folder. Within the "POI" folder, that is at the same level as the "Garmin" folder just described, there is also a poi.gpi file. What is the difference?

1. Yes. If you want the files to remain intact with the settings you have loaded, then you would need to load each one separately. Then rename that POI.GPI file. Then load then next one, rename THAT poi.gpi file. Then when you load new files using POI Loader, they will get written to the POI.GPI file and the renamed GPI files won't be affected.

2. If you have the POI.GPI file in two different places, that means one of two things. Either you loaded the POIs using POI Loader once directing it to the SD card and once directing it to the unit. Or you loaded them to the SD card and then when the unit asked if you wanted to import the data, you selected "Yes" which creates a copy on the unit. If your intentions are to load them to the SD card, when you get the prompt, select "Yes" then select Skip this file, and you won't get the prompt again. Unless you intentionally loaded the POIs to both places, then you should delete the POI.GPI file that you don't want.

Good advice for programmers and others that understand the risks involved and probably have a backup anyway.

But it bothers me to have Joe Public renaming, deleting files, etc just because it's possible.

Unless I'm wrong Garmin doesn't give out this kind of information. On the other hand their CSV implementation sucks. They don't provide solutions to these type of situations, require unique text like redlight in file names etc. Very old school and very prone to errors and confusion. JMHO

Well, that's one reason why I don't recommend it at first to mosts user. I, personally, don't use the method, but many, many people here have reported using it with no ill affects.

And I don't necessarily think that it's a method beyond what Garmin has intended. This is evidenced in the fact that their new MadMap files are delivered as GPI files which contain a route and many Custom POIs. And also evidenced in their support of TourGuide files which use the GPI specification.

I don't think that there's too much risk involved as the simple remedy should there be a problem is to simply delete the GPI file and reload the Custom POIs.

Garmin also supply Travel Guides and their own 'Safety Camera' database as separately packaged .GPI files. Their 'Communicator' plug-in provides a mechanism for transferring discrete .GPI files to GPSrs.