+elemay Posted August 3, 2009 Share Posted August 3, 2009 (edited) I have a Oregon 300 and I would like to personnalize the comments into the geocache_visits.txt file before uploading it (example : Cache # XXXX found at hh:mm). Anyone knows what is the format of the text file (character encoding) ? Edited August 3, 2009 by elemay Quote Link to comment
+fegan Posted August 3, 2009 Share Posted August 3, 2009 Perhaps I'm not understanding the question; otherwise, it's just a plain ASCII file. GC####,yyyy-mm-ddThh:mmZ,Found it,"your log here" GC####,yyyy-mm-ddThh:mmZ,Didn't find it,"your log here" GC####,yyyy-mm-ddThh:mmZ,Needs Maintenance,"your log here" Quote Link to comment
+Chris CA Posted August 3, 2009 Share Posted August 3, 2009 (edited) I have a Oregon 300 and I would like to personnalize the comments into the geocache_visits.txt file before uploading it (example : Cache # XXXX found at hh:mm). Anyone knows what is the format of the text file (character encoding) ? When you upload your field notes to geocaching.com, you still have to submit them for each cache and you can edit them when you actually submit each cache log. Edited August 3, 2009 by Chris CA Quote Link to comment
+LoveGPS Posted August 3, 2009 Share Posted August 3, 2009 I have a Oregon 300 and I would like to personnalize the comments into the geocache_visits.txt file before uploading it (example : Cache # XXXX found at hh:mm). Anyone knows what is the format of the text file (character encoding) ? File format of "UTF-16 No-BOM" works for me Quote Link to comment
+Maingray Posted August 3, 2009 Share Posted August 3, 2009 There is a very nice macro for GSAk that will do this for you, you can use a standard template text with the usual GSAK smartcodes and new codes, and then add the hand edits before you upload the final log to gc.com. Search for "gsak oregon export macro". Lotsa other features as well. Quote Link to comment
+elemay Posted August 4, 2009 Author Share Posted August 4, 2009 There is a very nice macro for GSAk that will do this for you, you can use a standard template text with the usual GSAK smartcodes and new codes, and then add the hand edits before you upload the final log to gc.com. Search for "gsak oregon export macro". Lotsa other features as well. I found that the Oergon .txt file is a unicode text file, but I prefer the easy option of using that macro! Thanks Maingray. 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.