How can a poi file become corrupt it's an exel sheet with long/lat and a .cvs extension correct. I am having problems with the lakes and coves poi files they lock up my garmin 660 every time i access them. The poi loader also say's can only access or use half of the information in this file and reads the rest like it's corrupt. Any sugestions?
If you open a CSV file with Excel, it's pretty easy to damage the data if you're not careful with making changes.
Excel doesn't always show all of the data in the file, and it sometimes adds additional quotation marks and commas which can cause problems with POI Loader. That's why it's a good idea to look at the file with Notepad or Wordpad if you've made changes with Excel.
I'd recommend downloading lakes and coves again so that you're sure you have a clean file to work with.
Also, here's another post on nuvi 660 / larger poi files. http://www.poi-factory.com/node/66
Thanks for the info.
>How can a poi file become corrupt
There are infinite ways it can be wrong/corrupt, and very few ways to be right.
>it's an exel sheet with long/lat and
> a .cvs extension correct.
Incorrect. It is a textfile in a certain order, named with a .csv extension.
Your windows machine may associate .csv files with Excel, but that does not imply that it is an Excel file. You can open it nicely (and perhaps most clearly) with notepad.
>The poi loader also say's can only access or use half of the
>information in this file and reads the rest like it's
>corrupt. Any sugestions?
Open up the file and look at the halfway point. The problem may be obvious, or maybe not.
terms | privacy | contactCopyright © 2006-2019