poiedit issue

What are you editing these files with? Sounds like Extra POI Editor. Am I correct?

Which Field are you trying to change, I am guessing that it is the Proximity Field under Tour Guide?

Also, How are you saving the file (What Extension are you using?) If you are saving it as A CSV file, do you have the proper Fields Mapped to be saved? It should save fine if your saving it as a GPX file.

Let us know the procedure your using so that we can help better.

I use this program almost everyday for my POI files, and I save the files in many different formats so I know what to expect for each format.

You can't save distances in a CSV. It only supports speed as either in the file name or following an @ in each record.

Actually, you can save that information as a CSV. However it needs to be a M-Column CSV format, not a Garmin csv format. You just need to chose the proper format by doing the following:

Run EPE, Choose "Options", then Click on M-Columns Fields
Pick the fields you want to output (you can go up to 24 Col)

Once you do that, when you want to save this format you can go to File, Save As, then choose "M-Column CSV" as file type.

This is good for using a program such as Excel. You can also bring this back and re-save it as a GPX file.

EPE has so many features that Even I have not used yet!!

I learned something new!

A CSV file has no use for a distance variable. POI Loader won't recognize it nor will it create a distance based alert from the variable.

The only time a distance based alert is created is thriugh the use of specific keywords, and that distance cannot be changed.

Certain keywords included in the POI name or filename trigger proximity alerts. If a filename contains “GATSO,” “mobile,” "SPECS,” “safety,” “speed,” “redlight” or “camera” but does not have any speed information, the POI Loader uses an alert speed of 0 which always generates an alert at a distance of 400 meters or .25 miles. Proximity alert information can also be added to individual POIs using BaseCamp.