Can you make selective proximity alerts on NUVI 680?

I believe that can be accomplished when using the POI Loader in Manual mode IIRC

You can't set separate proximity alerts for POI locations that are in the same file.

What you could do, however, it create separate files. Take the ones near you for which you don't want alerts out of the file and put them in their own file. Then when you reload them all with POI Loader, you can set the proximity for the other file (without the local locations) and not set one for the local locations.

How can you say that? M.M. -- you're obviously forgetting about .gpx files

Actually, I read the original query, as wanting to be able to switch alerts on & off dynamically, while out on the road...which short of having two differently setup .gpi files, on two different SD cards, I don't think is possible.

Yes, Hornbyp, you are correct. I would like to switch them off dynamically. That way, I can load them all once and be able to switch them off and on at will without having to reload the file. I don;t suppose the Nuvi 680 has this capability, does it?

I know that it isn't (or at least I haven't found a way) to do that on the 350. Now you can turn off/on the alerts on the fly (on the road), but it is all or nothing, can't pick and choose which POIs you want to turn off.

Not only gpx, but also csv Custom POI files. You can set proximity alerts selectively within a csv Custom POI file based on speed alerts entered in the lines where alerts are desired.

See POI Loader's help file:
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.

RT

Ah but these are not Proximity Alerts - these are Speed alerts. The distance at which it starts considering your speed, defaults to 36 * speed.

But that's not the same as always having it always alert at that distance, regardless of speed.

With gpx input, for every POI in a file, you can choose whether or not it alerts, if that is speed or proximity based and if speed, the distance at which it is considered. You can have a separate alert sound for each poi and a different icon.

(About the only application that springs to mind for having all those loaded at once, is maybe a tour of a golf course...)

Garmin's POI Loader calls them Proximity Alerts;
quote:

Proximity alert distance calculated by POI Loader based on speed information in the file name or in individual POI names..

"If it smells like a proximity alert and it acts like a proximity alert, it is a proximity alert"

The point is 'alerts CAN be set selectively within a csv file'. @0 to @25 will give a 1319 ft alert.

RT

Well, yes you are correct, but since the OP was talking about the redlight file which is a csv, that's what I used for my reference. But of course, oh master of GPX, you are the final authority on the GPX.

And I wouldn't include speed alerts in this category because they inherently work differently. But that's certainly a work around. I wouldn't do it that way (setting a speed alert in order to get a proximity alert) but to each his own.

You can turn TourGuide Alerts on and off independently ... so if you convert a group of files to TourGuides, you could control whether or not they alert, using the Nüvi's menu.

See also: http://www.poi-factory.com/node/7043

(just below Miss Poi's picture!)

I wonder what, if anything "@0" does? - I feel an experiment coming on
(in the gpx world, you can set a Proximity of "0", which it seems to take literally. Presumably you have to pass exactly through the point to trigger the alert...which could take some doing!

My error; I should have said @.00000000000000001 instead of @0.

As far as not using this method ... if one wants to use a csv file, wants to set alerts only on selective lines, and can accomplish this via this method, especially in light of the fact that Garmin's POI Loader says "Proximity alert distance calculated by POI Loader based on speed information in the file name or in individual POI names", why not?

RT