How do you do it...


How can I create my own POI files for a Nuvi 350. Is there software out there.... i want to save like red light cameras or school zones in my area... can someone give me some advice on this since this is all new to me..



Check out the getting started and faqs & help tabs at the top of each page. There are some fairly detailed descriptions on those pages.

You don't really need any special software. You can create the files in Notepad or Excel and save them as a CSV (comma separated values) file. The best way to see how the files are supposed to look is to download one. Then you will see the format which is fairly simple.

If you click on the red light cameras tab at the top of the page, you will find out how you can get the red light camera file.

Also, if you search for the word "schools" on this site (the search box is at the top of the page), there is a file with all the school sites.

you can do it!

Here's how I learned.

Read all the getting started stuff, pay particular attention to the
Garmin CSV file format

Then practice. I used google earth and found the latitude and longitude of intersections around my neighborhood. Using Notepad, I entered my information, then using poi loader I loaded the file. I would then simulate the drive to see what would happen. That's why I use neighborhood spots. Once I got that figured out, I ventured into using proximity alerts. Then, I progressed to incorporating mp3's as the alert sound. Then into making TourGuide files with mp3's and jpg's.
I would also open a good working file in Excel to see how it looked, then created some files with Excel, as well as using Excel to edit some files.
It seems to be a natural progression you'll follow.
In a months time you'll be a pro.
I did a lot of reading on this site before, during and after attempting my first csv file, or posting an entry.

Basically, learn the fundamentals, proper syntax, then practice and check your work. When you get stuck (and you might) there is a growing community here to help you along the way.

If there is a particular thing that has you confuddled, you can probably find it by using the search feature here at the factory.

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

thanks for the info.... i

thanks for the info.... i tried one today using excel and i got it to work.... i have not seen a cvs file that opened in notes...but excel i seem to be able to get it to work and google earth is the bomb of a program to get info from for lat and long...thanks

why do some csv poi files have alerts and others do not?

two custom excel csv poi files i created and loaded onto my garmin nuvi 650 today have "alert information" displayed when I select one from the list. when poi is selected, it goes the the "GO" button page and displays the text from the "name" column top left, and the text from the "details" column bottom left. In between (middle-left of the screen) it now for the first time also displays text which reads:

Alert Information:
Distance: 1319ft

how did this text get there? does it mean that every time i get near one of these poi's my gps will sound off? did i inadvertently trigger this by the way i created the file? how do i get rid of it?

Check out the help file in POI Loader

POI Loader interprets numbers in the file name as speed information. Take a look at this excerpt.

Understanding Speed and Proximity Alert Information

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:

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.

Speed information entered in Manual mode.

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 criteria, listed from highest to lowest priority:

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

Proximity alert information entered in Manual mode.

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.

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

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.

POI Loader determines whether or not a file contains speed and proximity alert points based on specific criteria. Use the following information to help you create Custom POI files:

If a file name contains a valid speed number or if all records in a file have speed encoded in the name, then all records in the file will include speed and proximity alerts. For example, a data file with the file name "Speed_30" generates speed alerts of 30 mph (or kph, depending on the type of units selected in POI Loader) for each POI in the file.

If the file name contains "redlight", POI Loader assumes all records in the file have proximity alerts with a distance of 400m/0.25 miles.

If a file contains "GATSO," "mobile," "SPECS," "safety," "speed," or "camera," but does not have a speed, POI Loader uses a default alert speed of 0, which means you will always be alerted. You can override this default value by entering the speed in Manual mode.

You can also enter speeds for each POI individually by adding the @ symbol and a number after the name of the POI. For example, a Custom POI named "Ridgeview@25" would create a POI named "Ridgeview" with a 25 mph speed alert.

POI Loader calculates proximity alert distance based on speed. You can enter proximity alert distance for individual Custom POIs in a .gpx file. You can also enter proximity alert distance for all Custom POIs in a data file using Manual mode.

speed & prox alert coming from phone numbers in poi name

Thanks MM - I have phone numbers in the poi file names of both lists showing the speed and prox alert text on the "GO" screen. I used 202.445.6216 as my phone number written format as opposed to (202) 445-6216 or <202-445-6216>. Would changing the way I write the phone number prevent it from being read as speed? Would that then allow me to keep the phone number in the name of the individual poi file? I like having it there - I mean I guess I could just move the phone number to the ;details column with the address info but I'd rather not.
So my new question to the community is this: does anyone know how to include a phone number in the name of an individual poi without it being read by the device as speed info?


No, I don't think so. If you have a number in the filename, it will be read as speed information.

But you can overcome this by running POI Loader in MANUAL mode instead of EXPRESS. Then you can uncheck the box that comes up with the alert information in it. Bingo, no speed info will be created.