Signed up for red light cameras
Thu, 01/22/2009 - 7:11pm
 |
 15 years
|
Hi,
I just signed up for the RedLight and speed camera files. I downloaded them to my PC. Now I am going to load them to my custom POI folder.
One question: Will it hurt anything if I delete all previous Custom POI's with that POI loader tool? I have the ones backed up that I want to use with the camera files. My only concern is when I delete I don't want to delete any other POI content that is already loaded by the factory default and just want to make sure that it doesn't do anything like that before I use it.
The only reason I want to do it at all is because some of the POI's are outdated and it looks like there are new ones that might be better to use and I don't want to duplicate them on my Garmin 770.
Thanks for all you do!
POI
Hi,
I just signed up for the RedLight and speed camera files. I downloaded them to my PC. Now I am going to load them to my custom POI folder.
One question: Will it hurt anything if I delete all previous Custom POI's with that POI loader tool? I have the ones backed up that I want to use with the camera files.
Thanks for all you do!
Essentially the Garmin has two different databases for POI. The factory installed are part of the map data and are not accessible by the user. Custom POI are the other database and these files all have a GPI extension. The primary database for custom POI is POI.GPI and this file is overwritten everytime you run POI loader. If the other files you mention have GPI extensions, then running POI loader won't affect them. I don't think the delete POI function will do any thing with files other than POI.GPI, but then I don't want to try on my unit as I have created several POI files with .GPI extensions.
ɐ‾nsǝɹ Just one click away from the end of the Internet
You may want to read some
You may want to read some other posts, this has been covered many times before.
If your current POIs are in POI.gpi then you will delete them when you do a new download, like it or not. You can download multiple POI files at once, and the resulting poi.cgi replaces any existing POIs.
There is a workaround that involves renaming poi.gpi. I'm not going to retype all of the details and implications here, but you should be able to find several references to it with a simple search.