.csv files, proximity alerts, and POI Loader (beta)

 

I have just finished creating several files for Radio Stations (will be posted shortly) and found a situation I cannot understand. I have several files (in folders) including one one for Radio Stations, a second for Texas (state parks, farmers mkts (all loaded from here), and another for Locations. Using the Beta POI Loader in manual mode, most of the folders and files do not have either proximity or speed checked. However, these new Radio Station files enter with proximity checked. (I am currently turning it off). What is different that would cause the proximity to be checked? I like it, I just want to know how to do it again.

Thanks

--
Garmin StreetPilot c530, Mapsource

Proximity alerts

Is it possible that the file meets one or more of the below conditions?

I took this from the help included with POI Loader.
---------------------------------------------------

POI Loader automatically scans .csv and .gpx data files for speed and proximity alert information.
You can also use Manual mode to specify default speed and proximity alert information as needed.

Speed Information

Speed information can be included in the file name or in the names of individual POIs within the file.
POI Loader determines speed information based on the following information, listed from highest to lowest priority:

1. Speed information included in the name of the individual Custom POI. For example, a POI named "SpeedZone@30" will have an alert speed of 30 regardless of the speed information specified in Manual mode or in the file name.

2. Speed information entered in Manual mode.

3. Speed information included in the file name. POI Loader interprets any numbers in the file name as speed information.

Proximity Alert Information

Proximity alert information can be calculated automatically based on speed information. It can also be included in .gpx data files or added in Manual mode.
POI Loader determines proximity alert information based on the following criteira, listed from highest to lowest priority:

1. Proximity alert information listed for individual POIs in a .gpx file. This information overrides all other proximity alert information.

2. Proximity alert information entered in Manual mode.

3. 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.

4. A default proximity alert distance of 400 meters/0.25 miles if the file name contains the word "redlight."

5. If there is a TourGuide audio file attached and no other proximity alert information is available, POI Loader assigns a proximity alert distance of 0.25 miles.

See Creating Custom POI Files for more information.

--
Garmin Nüvi 265WT,Software Ver. 7.00, City Navigator North America NT 2010.30

I didn't realize until

I ran across this while playing. I had been using a "test" csv file and a "test" bmp file and "test" mp3 file. At one point while testing with the mp3 I used the manual mode for the "test" file and set prox and speed alerts. After that test was over and a few days passed, here I am playing again. Using the express mode of the poi loader. I continued to get speed and prox alerts on the "test" file. I eventually went back through the manual mode and unchecked the alerts I had set previously. Even though I was using the express mode, the alerts that were set in manual mode were maintained until unchecked.

--
........Garmin StreetPilot c550 / Nüvi 765...........

Still Testing

Thanks weebl, however I don't believe any of those criteria meet my files. The files are located in the POI files under radio stations. They are the files loaded by rbrown3.

I will test reloading them to see if the criteria changed in POI Loader beta. I didn't think that it might remember previous settings and default to the check by proximity. Will try later.

--
Garmin StreetPilot c530, Mapsource

.csv files and proximity alerts

This is just FYI for anyone interested. As I stated in an early post, the Radio Station files we had created defalt to a proximity alert of 1 mile in manual, POI Loader. I needed to manually remove the checkmark in order to be sure I would not get a proximity alert.

After some testing, I believe I have the answer. It is a special character in the file name, however it does not seem to be one that Garmin mentions. In all of the files, I ended the name with v_1_xx_xx, signifying the date created. The 1 in proximity seems to be coming from the 1 representing January. I changed it to 2 and the proximity goes to 2. Further, I exchanged the underscore character with a dash and got the same result. However, when I merged the date as follows: v1xxxx, there is no proximity alert default. Therefore, it seems that the single number in the file name, perhaps surrounded by the underscore or dash, created the situation.

--
Garmin StreetPilot c530, Mapsource

as stated in a previous

as stated in the post by weebl:

(...)

POI Loader determines speed information based on the following information

(...)

POI Loader interprets any numbers in the file name as speed information.

(...)

Proximity alert distance calculated by POI Loader based on speed information in the file name

(...)

So i guess this applies to your files...

--
Fredrik Rødland, http://rodland.no, Garmin Quest, Garmin nüvi 660