Problem with Nascar Race Track POI
Mon, 11/12/2007 - 2:59pm
 |
   17 years
|
There seems to be a problem with the updated Nascar POI. The last line is being rejected when importing the file into my unit. I think it was updated by Miss POI to include line #39 which is the line that is being rejected. It looks okay to me, but it still won't work...maybe Miss POI can look at it.
Line 38
Too many quotes in line 38.
RT
"Internet: As Yogi Berra would say, "Don't believe 90% of what you read, and verify the other half."
Nascar Race Track Problem Still Exists
I tried to load this poi onto my Garmin nuvi 200W using poi loader and it gave me an error with line 39 also. Apparently still not fixed...
File updated
I updated the file 1/8/08 adding two addresses. Used "POI File Verifier" too. Sorry for any trouble and thank you "FrankJR0401" for contacting me about this error.
POI Verifier comment
I updated the file 1/8/08 adding two addresses. Used "POI File Verifier" too. Sorry for any trouble and thank you "FrankJR0401" for contacting me about this error.
Just a comment on POI Verifier. Although POI Verifier corrects some formatting errors, it can't repair all of them. In that case the .log file contains information on the areas needing attention. That's why it's imperative that the log file is always reviewed when any type of error is indicated. POI Verifier found the problem (in this file) that I posted above, but it had to be repaired by the user.
RT
"Internet: As Yogi Berra would say, "Don't believe 90% of what you read, and verify the other half."
Update to my earlier comment
RT,
Thanks for the feedback for all. What i wrote early yesterday I see may have been misunderstood. I did use POI Verifier, and that IS how I found the error. GREAT program. We all thank you very much. It identified an error in line 38, and for some reasons extra columns had been added to the file. Easy fixes.
What I do ask of all is that we let the originator know of issues so fixes can be made quickly. I read my email daily, but unfortunately log onto this web site periodically, and I missed earlier posts noting the issue. My apologies.
John