+Dread_Pirate_Bruce Posted April 19, 2009 Share Posted April 19, 2009 Yesterday I re-ran some PQs. I have always had them output as ".loc" files because I can transfer them to my GPS from my Mac with the driver I have. It has always worked in the past. Yesterday's run produced files that would not load properly. When I looked at the files, I noticed that there were no carriage returns in the new file. I also noticed the new file was coded as "UTF-8" while the old ones were coded as "ISO-8859-1." What gives? Is there any way to correct/change the coding? Quote Link to comment
+BM & BM Posted April 20, 2009 Share Posted April 20, 2009 (edited) Yesterday I re-ran some PQs. I have always had them output as ".loc" files because I can transfer them to my GPS from my Mac with the driver I have. It has always worked in the past. Yesterday's run produced files that would not load properly. When I looked at the files, I noticed that there were no carriage returns in the new file. I also noticed the new file was coded as "UTF-8" while the old ones were coded as "ISO-8859-1." What gives? Is there any way to correct/change the coding? I tried some old pq's yesterday would not download to e-mail, tried a new one this morning same issue using gpx code. Edited April 20, 2009 by BM & BM Quote Link to comment
+J-Way Posted April 20, 2009 Share Posted April 20, 2009 You should probably post this in the Geocaching.com Web Site forum. That forum is watched by various web lackeys. Quote Link to comment
+Dread_Pirate_Bruce Posted April 21, 2009 Author Share Posted April 21, 2009 I actually figured out what happened. (Gosh, I'm good at troubleshooting computer glittches.) It seems that at least in the ".loc" files someone changed the spelling for the slang term for coordinate. It had been "coord" as in "<coord lat ...>" and now is "cord" as in "<cord lat ...>" Opening the file in Word and going a global search and replace seems to fix things just fine. Quote Link to comment
+beejay&esskay Posted April 21, 2009 Share Posted April 21, 2009 I just downloaded a single LOC file and see <coord lat="39.85805" lon="-84.890733" I never get LOC PQs, but are you SURE they have <cord lat= .... ? Quote Link to comment
+Dread_Pirate_Bruce Posted April 23, 2009 Author Share Posted April 23, 2009 I just downloaded a single LOC file and see <coord lat="39.85805" lon="-84.890733" I never get LOC PQs, but are you SURE they have <cord lat= .... ? Absolutely sure. I did it again today (4/22/09). I don't mind the added step of a global search & replace, but I am perplexed ... and that you got <coord lat, really makes it odd. Quote Link to comment
+beejay&esskay Posted April 23, 2009 Share Posted April 23, 2009 If you download a single LOC from a cache page, you get the "coord" that I see, right? It is only in PQs that you get "cord"? It's enough to make me consider burning a PQ run to see. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.