I was able to correct some errors in some of the files from POI, most were either a comma in the wrong place or quotation marks that shouldn't have been there. v2.6.0 will not recognize a lot of lines of text for individual POIs that v2.5.4 will recognize v2.6.0 will give you hundreds of line errors that v2.5.4 never had a problem with. Total of just over 126,000 individual POIs. csv files, some I created myself and some from POI. "Just updated from POI Loader v2.5.4 that was working fine with many many custom POI. No need for v2.5.4 to work and v2.6.0 not to work on the exact same custom POI files. Thought others might be interested and want to reply to Garmin to correct the problems in POI Loader v2.6.0. Posted the following on Garmin's website in their POI Loader Forum. If I'm not mistaken Garmin looks for 4 values when it takes in a POI file, Long, Lat, Name, other, what I think they are doing is the Name value can no longer contain special characters. If you have any question try reading the file into excel, it treats the "field, field", value, as two values not three better yet, take in one of your poi file, change one of the columns to include a comma separating fields and see how excel saves it, open it in notepad and you see the column now enclosed in quotes. They get to "follow" the rules and a comma enclosed by double quotes is part of that standard.Ī comma in a value enclosed by quotes is just a comma(special character), not a value separator see your link. The way I see it, Garmin doesn't get to "set" the rules regarding the delimited text csv format. Seems like they might be making the editing more strict. I'm going to wait and see what Garmin does with the new POI Loader. So for right now, I am not going to change my file. That formatting should be legit (a comma inside double quotes). Visually, I could see nothing wrong with the formatting of the file.Īfter reading this post, I went back and looked at the file again and found the same thing - "The one error that occured apparently was caused by a comma in the name field even though the name was enclosed in quotation marks." He was also using the new version POI Loader. I received an email from that he had an error loading my Tampa Bay Area Attractions file. This edited line worked ok (notice the comma after Singer Subaru was deleted): This line (as downloaded from POI Factory) caused a POI Loader 2.6.0 error: The one error that occured apparently was caused by a comma in the name field even though the name was enclosed in quotation marks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |