automatic proximity filenames

 

I am a bit confused......I would like automate my POILoader instead of manually entering alert settings all the time, by placing the setting in the filename for schools, redlights, speed cams, and rest areas. Reading Garmin's "Creating Custom POI Files" doc I get this:

The filename "school_safety_25.csv" will produce an alert for any POI in the file.

"the GPS will display an alert if the set speed is exceeded while approaching the POI. The alert will repeat until the speed drops below the set value or the POI is passed."

But there is no info about the distance when it will initiate. But following the next example it will be 0.25miles.

For the rest area, I am told that "rest area mobile_100.csv will produce an alert at 10,000 ft,

"Regardless of the approaching vehicles speed the alert distance will remain the same."

It is calculated from the given speed number. But according to the speed (school) alert above, if I am approaching at 70 MPH it won't trigger since I am below the set speed.

There is no example given for redlight or speed cams other than if I leave it blank it will trigger at ~ 1300 ft. So, I guess if I want it set to 500 ft, I need to do this. "redlight_5.csv"

What is bothering me is why the school (speed) alert is said to work different than the other alerts.

Can someone explain this?

POI Loader Help

The best info from Garmin on proximity names and alerts is POI Loader Help:

https://www8.garmin.com/products/poiloader/creating-custom-p...

dobs108 smile

A number in the filename creates a speed alert

ruggb wrote:

...The filename "school_safety_25.csv" will produce an alert for any POI in the file...

According to POI Loader help, any POI file filename that has a number in it will create a speed alert at the speed of that number.

school_safety 25.csv will create a speed alert of 25 mph. (I assume you are in the US)

That is not how POI Factory has the speed camera file set up. Speeds are different for every poi in the file, and the speed is in the text string for each poi. When you load Speed-Cameras.csv with no number in the filename, each poi will have its own speed. To have this happen, the word speed must be in the filename. (source - POI Loader Help)

dobs108 smile

never do this

ruggb wrote:

...There is no example given for redlight or speed cams other than if I leave it blank it will trigger at ~ 1300 ft. So, I guess if I want it set to 500 ft, I need to do this. "redlight_5.csv"...

If you want to load red light cameras or most other poi files, never include a number in the filename, because it will create a speed alert. This overrides all other actions.

redlight 5.csv will create an unwanted 5 mph speed alert. Even though the trigger word redlight is in the filename, the 5 overrides the red light camera function.

dobs108 smile

alert below the set speed

ruggb wrote:

...It is calculated from the given speed number. But according to the speed (school) alert above, if I am approaching at 70 MPH it won't trigger since I am below the set speed...

Using the POI Factory Speed-Cameras.csv and my nuvi 3597, all speed camera alerts have been activated whether or not the speed has been exceeded. I don't know why this is so and I don't know if other members' GPSs will act differently.

I disagree with "Creating Custom POI Files" on the idea of using a number in the filename to create a proximity alert.

dobs108 smile

@dobs - thanks for the

@dobs - thanks for the replies - let me address them individually (X.)

(1.) I mentioned that the reference I was/am using is Garmin's "Creating Custom POI Files" doc.

(2.) The ref says:
"Speed information in the individual POI name is preceded by the "@" sign: “Speed@20”. Speed information in the filename is preceded by an underscore, “Speed_30”." == if it is just the number " 30", as you wrote, it seems to be infering conflicted info. I did not realize ('cause I didn't look) that speed was included in each entry. Thanks. That would override anything placed in the filename or manually entered per the ref.:

"1. Speed information included in the individual POI name will retain the alert regardless of the filename or information entered in manual mode." == so "When you load Speed-Cameras.csv with no number in the filename,..." is irrelavent.

Any keyword: "If a filename contains “GATSO,” “mobile,” "SPECS,” “safety,” “speed,” “redlight” or “camera”.... " will work.

(3.) Obviously, there is some confusion here. Again, the 5 without the _ is not valid for a speed (or maybe there is something missing in the ref.) Also, the _5 in the filename will not override a number in the individual POIs. The ref says:

"The POI Loader prioritizes proximity alert information from highest to lowest priority:
• Proximity alert distance in individual POIs in a .gpx file. This information overrides all other proximity alert information.
• Proximity alert distance entered in manual mode. Maximum distance that can be entered in manual mode is 37.88 miles.
• Proximity alert distance calculated by POI Loader based on speed information in the individual or filename names. This calculation uses the following formula:
Prompt Distance = 36 seconds * Speed." Speed is (miles/second)

based on the third bullet a _5 in the filename will set the alert to trigger at 500 ft.

(4.) So, what you see in real life does not agree with what the ref says. IF "all speed camera alerts have been activated whether or not the speed has been exceeded." is correct, then the problem I see in setting "rest area _100.csv" is a none issue as it will trigger based on the calculated proximity and not the speed, and this statement in the ref is incorrect: "the GPS will display an alert if the set speed is exceeded while approaching the POI."

I do not have any speed cams in my area so I can't test this: Does a speed alert set for @25 trigger later than one set for @45? Logically, it should. Then it would agree with the calculation. The only disagreement would be the ref statement that "the GPS will display an alert if the set speed is exceeded while approaching the POI." which appears to be wrong.

If so, ALL alerts are the same and operate the same. For POI or file name entry you use a speed number. For manual entry you can select either a speed number (which gets converted to a proximity) or a proximity (ft). Now we can thank Garmin for the confusion and get on with our life.

number in the filename

In practice, it doesn't matter if an underscore or an @ is included in the filename. Numbers in the filename alone will create a speed alert. This has caused no end of difficulty for members who include a number while unaware of the consequences.

The number in the filename overrides all other actions such as the speed number for each poi.

My speed alerts work above and below the speed limit most likely because I load them in POI Loader in manual mode with the default zero as the speed. The GPS displays the speed limit at each particular speed camera I am approaching.

You have said, "All alerts are the same and operate the same." That is true. All alerts are proximity alerts. Even speed alerts are proximity alerts.

dobs108 smile

Try Extra POI Editor

I prefer using EPE to set either a proximity alert or speed alert.

Go to Edit-Replace Field. Click on the field list and scroll down and click on either Proximity or Speed.

Enter the value you want for either and click Replace All.

This way the values are imbedded in the file and you're set to go. A bit more work, but it ensures that the limit is always there.

I would expect that you only have certain files that you need these kinds if alerts. Don't get carried away and put alerts on things like fast food places and gas stations. Otherwise you'll have the GPS dinging constantly.

--
NUVI2555LMT, NUVI350

I too

use ÉPE to set proximity alerts, but only proximity alerts. To my way of thinking I drive on too many varieties of roads to be able to set a speed limit for any.
As an example I use a toll road in Texas with an 85 Mph speed limit. Even going the speed limit I'm one of the slower vehicles.

--
Nuvi 350 long gone, Nuvi 855LMT Retired now, Nuvi 2797LMT, SmartDrive 50 LMT-HD, 3790LMT now my daughters. Using Windows 10. DashCam A108C with GPS.

Feel the same on I76

Melaqueman wrote:

use ÉPE to set proximity alerts, but only proximity alerts. To my way of thinking I drive on too many varieties of roads to be able to set a speed limit for any.
As an example I use a toll road in Texas with an 85 Mph speed limit. Even going the speed limit I'm one of the slower vehicles.

I feel the same driving through Philadelphia on I 76.

55 MPH speed limit. I try to stay close to speed limit. I figure my Ontario plates make me look like a nice Speed Cop target. Everyone around me is doing 70.

--
NUVI2555LMT, NUVI350

If all speed alerts are

If all speed alerts are triggered regardless of speed, contrary to Garmin's tutorial, then all alerts are proximity alerts. Setting a speed alert for 25mph will trigger it at approx. 2500 ft. It doesn't matter how fast you are going. If you set an RLC for 5mph, it will trigger at ~500 ft.

I still have to verify this, but if someone else has personal experience, please chime in.

From my experience, speed

From my experience, speed alerts trigger based on the amount of time it will take to reach the point based on your current speed. If you are traveling above the alert speed, the alarm repeats until you are either at or below the alert speed. I believe the time used for the calculation is 36 seconds.

--
"In order to be old and wise, one first must have been young and stupid."

Good point

Good point