Chrysalides

It was indeed. I was glad I was able to experience it with a group of geocachers.

Part of the whole experience was a little confusing, but I did not encounter any major issues unlike others, got 6 souvenirs (including the bonus), as well as the trackable, so I guess I shouldn't complain. I tried to solve the final puzzle, apparently wrongly, and got a 8 letter nonsense word. I entered it anyway, and it appeared to be successful, saying I'll get my trackable code, but the email today said I didn't get the bounty, but here's the trackable anyway. An indication that I did not solve it correctly when I entered the code word would be nice, because I'm obsessive like that I also noticed that the special icon is not displayed on all pages. In fact, it's only displayed when I view the trackable from my public profile page. If I looked at my "owned trackable" page, it shows a generic icon. Assuming that this is just a caching issue for now.

You can buy small charms and make something interesting with them. They don't cost much, typically a few for a dollar. I have almost no artistic talent, so I just put them in a small baggie. Someone found butterfly charms I left and made ear-rings out of them. Those painted stones are really beautiful.

A very much anticipated feature, but definitely still buggy. At zoom level 17, I see the new icon if I tweak the coordinates a little, but if I make a larger change, it disappears off the map entirely. Using Firefox on Windows. At zoom level 15, I managed to get it so that only part of the icon appears. Might it be an issue with which map tile it appears in? (the "corrected" coordinates in this map is bogus) Edit to add: using corrected coordinates N 47° 35.500 W 122° 18.000 (somewhere in Seattle) for GC5BQKT if you need it for testing. And no, that is obviously not the correct final.

Glad that helped Happy geocaching!

1. Download the PQ ZIP file to your computer and open it. Inside you will find 2 GPX files. The one with "wpts" in the name is the additional waypoints. Copy both files to your desktop (or another folder). 2. Connect your Garmin Montana with USB cable to your computer. It may take up to a minute for your computer to detect it. Open up the device that appears on your computer. Go to the "GARMIN" folder, then the "GPX" folder that's inside "GARMIN". 3. Drag and drop the 2 files from step 1 into the "GPX" folder. 4. Wait until the files finished copying, then eject the Montana (same way you disconnect a flash drive safely). Unplug. Restart the Montana. It will load in the new caches. Depending on number of caches, this may take up to a few minutes. If you would like me to elaborate any of the steps in more detail, please let me know.

I just tried with the new app (latest version) on Android. I'm still seeing +16 h. <Groundspeak:log id="660602370"> <Groundspeak:date>2017-01-16T06:36:17Z</Groundspeak:date> <Groundspeak:type>Write note</Groundspeak:type> <Groundspeak:finder id="1933996">Chrysalides</Groundspeak:finder> <Groundspeak:text encoded="False">Note created at 2:36 p.m. Pacific Time for testing.</Groundspeak:text> </Groundspeak:log> I wonder if I log a cache late at night on phone, will it be logged as found on the next day?

Can you try the same thing I did and see if you're also seeing an 8 hour offset, since your time zone is UTC-5? If the offset is also 8 hours, then the next question is whether it changes to 7 hours during DST (which we can't test until March 12). If it does, then it is because someone is treating UTC as Pacific Time.

BenH, this is not a new issue, but something I've seen with the past few releases. There appears to be an issue with the date and time logged through the app. In Pacific time zone, when I log a note, the time recorded in the GPX is 8 hours in the future. Please see my post here for details: http://forums.Groundspeak.com/GC/index.php?showtopic=342638&view=findpost&p=5630662

Just for you, I did an experiment. I logged a note on my own cache using the Geocaching app and downloaded the GPX. My time zone is set to Pacific time in my profile. I created the log at 14:50. UTC time is 22:50. In the log, time is 2017-01-14T06:50:10Z. 2017-01-13T14:50:10-08 : log entered, local time 2017-01-13T22:50:10Z : log entered, UTC 2017-01-14T06:50:10Z : log time in GPX You can download the GPX and see for yourself here. Here's the log section: <Groundspeak:log id="660243949"> <Groundspeak:date>2017-01-14T06:50:10Z</Groundspeak:date> <Groundspeak:type>Write note</Groundspeak:type> <Groundspeak:finder id="1933996">Chrysalides</Groundspeak:finder> <Groundspeak:text encoded="False">Another experiment with date and time.</Groundspeak:text> </Groundspeak:log> Just for fun and giggles, I created another log with my time zone set to Samoa (UTC+13) and the time offset remains unchanged. Speculating, it appears that the app is sending UTC time with time zone to Groundspeak's server. The server then treated UTC as local time and adjusted it to UTC, resulting in me caching 8 hours in the future.

Last time I checked, the local time was being correctly converted to UTC and marked as 'Z'ulu time. Are you not seeing this? The last time I logged with app was in October - that was the example I gave a few posts above. It might have been fixed since then. When was the last time you logged using the app? Edit: still not fixed. See entry below.

No, it will not. Give it a try. Mark a cache as found. Then delete that file and restart your GPSr. It will still be marked as found. Garmin has an index of geocaches somewhere in internal memory not visible to the end user where the status is marked. The only way to reset it is to reload the GPX.

You mean like this one? Yes, but I was thinking of another one from at least 2 years ago. To be fair, Groundspeak only claims to be the language of location, not time

The Garmin's calendar app is reading that file and lists the number of finds. H. Really? My mistake then. But that file is definitely not used by the receiver to determine if you have already found a cache.

geocache_visits.txt is a write only file to Garmin GPS receivers. They don't read from it. It is there for our convenience only. Deleting all GPX containing geocaches from \garmin\gpx and starting over is the correct procedure.

Logs entered via web will always have time of 8 p.m. when daylight savings is not active, and 7 p.m. when daylight savings is active. They appear to take 12 noon Pacific time on that day, and convert it to UTC. Example: <Groundspeak:date>2013-12-28T20:00:00Z</Groundspeak:date> I'm more puzzled by the very strange time that's recorded when logging through app. I'm not sure if someone's doing something strange such as getting current time in UTC, changing the time zone to Pacific (without adjusting time), then saving it, or something like that. There used to be a bug with field notes with a very similar issue.

To answer the question in your title, there is no way to change the timestamp of logs except by relogging. To prevent this from happening in the future, I strongly advise against logging on the app. (the long rambling details appear after this) The last time I logged from the app was on October 13 2016 (Pacific time) because the website is down. I'm not 100% positive, but I believe I found this around 2 p.m. Since we were in DST during this time, I would expect the timestamp to show 2016-10-13T21:xx:xxZ. Instead, the GPX timestamp shows 2016-10-14T04:22:11Z, which would make the find at around 9 p.m. on Oct 13. I know I found this closer to lunchtime than dinner time, and it was still full daylight when I found it. If you log from the website, it is also kind of screwed up, but at least the madness is predictable. If you're logging when DST is in effect in Seattle, time is always 19:00:00Z. When DST is not in effect, time is always 20:00:00Z. I haven't verified this, but it would appear that on the web page, logs are sorted first by chronological order, then if the time is the same, it is sorted by log ID. I've seen log entries that were entered before I logged on the cache page, but when I log my find, my entry jumped in front of theirs (or, rather, since it is in reverse chronological, it appears below their log entry).

Thank you, appreciate it. Happy holidays!

Just because you don't have a Mr Fusion powered DeLorean doesn't mean that no one here has one. Jokes aside, this can cause a problem because the last time I tried, I couldn't enter dates before Jan 1 2000 in PQs unless I hack the form (and I don't know if it still works). When you're using date ranges to split an area into multiple sets of 1000 caches you'll miss those caches.

Seems like I'll get a faster resolution that way. Thought someone might want to fix it properly, but maybe they don't monitor the forums for bug reports. Thanks.

Looking at my country souvenirs, I was surprised to see Russia showing up, dated April 1 2016. I remember the joke caches, and I specifically logged a "write note" instead of a "Found It" so that it doesn't mess with my statistics. The "Found It"s logged by others were later converted to notes, but now I see that I have been given a country souvenir. Sure, I can (and did) hide it, but since this is a bug that probably affects the other players as well, can it be fixed? Edit to provide the only log entry I entered: https://www.geocaching.com/seek/log.aspx?LUID=28f21a2f-b586-4261-8975-b20962a05531

I think you're safe.

I don't know about you guys, but I'm running PQs for my immediate area in case the problem returns. I'm glad my prediction of "no solution till morning" is incorrect.

I've experiencing problems for the last couple of days, and today since about 8 p.m. Pacific time (same time zone as Groundspeak). Seeing that it is past midnight now, I don't expect a fix until the staff gets into office in the morning. Website availability has been generally good, but the IT folks not being able to fix this issue over the last few days worry me.

Odd numbered PQs came in, all 3 at the same time, 5 1/2 hours after the even numbered PQs. If someone restarted the server, thanks! If not, guess it's just a really slow day for the odd numbered server.