1949Sidewinder

This sounds like a really lame excuse to get rid of one of the few features on the site that I find very useful. I like to hide caches out in the back-country that can be extremely difficult to access. Very few have the interest and gumption to actually go find them so it is important (to me) to know if anybody is even looking at the listings. It is interesting to see whom is looking at your listing, but it is important to know if "anybody" is looking. It would be nice to see a more imaginative solution to the problematic nature of the audit log!

Thanks to arisoft and vpdj for their responses. There seems to have been no action whatsoever on this problem. I am leaving on my first big geocaching trip of 2017 one week from today. I have solved 172 puzzle caches to look for. I have gone through many gyrations to get corrected coordinates loaded into the CacheSense app. Creating that many individual waypoints is a bit overwhelming. It takes multiple import/export operations between the ProjectGC VirtualGPS and GSAK to get the corrected coordinates loaded onto my device. It has always "just worked" from the time I started using CacheSense until this problem started. Some help from the people that can help would be very nice. Michael

I can see that posting problems here is total waste of time!

Update: While testing alternate methods of getting "corrected coordinates" to show up in CacheSense I tried the "Virtual GPS" function on the ProjectGC live map. Making sure that the "use corrected coordinates" box is checked and that the cache data had just been refreshed I see that the corrected coordinates for the solved puzzles are not showing up there either. The puzzles that I was looking at have been solved for some time and the corrected coordinates are already on my device. My sense is that something in the operation of the "Live API" has changed and I wish someone would fix it. Thanks, Michael

Thanks JohnCNA, I am glad to hear that I am not the only one with the problem.

Thanks Spurges, I have been following this same procedure for the last two years. I correct the coordinates on the website. Then I either fetch or refresh the cache information (via the API,) whichever is applicable. Now that has stopped working. I only tried the PQ because the normal method did not work. I only care about having the corrected coordinates in the device. Michael

Thanks Walter, I refreshed those caches in GSAK via "refresh cache data" and it did indeed result in the "corrected coordinates" flag being set. However, that does not explain why updating the device (via the API) all of a sudden does not correct the coordinates on the device. That is the only important thing to me. I included the information about the GSAK experience because I thought it might help in troubleshooting. Michael

I have been solving a bunch of puzzles lately. When I obtain the solution I correct the coordinates on the website and then update the cache listing on my device-CacheSense on Android running on my Nexus 7 Tablet. The day before yesterday (December 18) things changed: the coordinate update on the website works, but the update to the device does not. I used the website search function to list all of my California puzzle caches with corrected coordinates-looks good. Added them to a bookmark list and used that to generate a pocket query. When I import said pocket query into GSAK the new coordinates show, but the corrected coordinates flag is not set (as it is on all the other caches with corrected coordinates.) When I import the PQ into the device the cache listings in question do not change. I just tried again on another puzzle cache and got the same result. The caches from the day before yesterday: A log at the base of 3 trees and What is my pet centipede doing? (YGR 1406) The one from today is Rhymes with Pi This is a very big deal to me as I have several hundred puzzles solved with the intention of finding them on several cross country trips next spring and summer. I plan on solving several hundred more before then. Having the corrected coordinates listed on the website does not do much good if I cannot get them loaded into the device that I use to find them. Help would be welcome. Thanks, Michael PS there have been no updates to the device and no settings have been changed.

"Should Mission 9: Tunnel of Light be returned to its original location and reactivated?" I voted yes! - I Believe that this pastime is called geocaching. If the cache can be returned to it's original location and reactivated then that is what should be done. I have absolutely no interest in going to Geocaching HQ to see an old ammo can, but I would love to go find the A.P.E. cache. Is that not what geocaching is all about?

I was at an event this evening and I noticed one of my trackables on the table. It had been in a supposedly un-found mystery cache of mine. I now realize that I am not getting notifications for found-it logs on my caches. I have no idea how many have been missed and I am not going to dig through every cache to find out. The one that I do know about is for GC6Q1K8 - The Girls from YC -found by user Alamogul today (8/17/2016.) Things are getting worse, not better.

No notification for GC6PVKE this afternoon, but did get notification of another cache shortly thereafter. This also happened a few days ago. Hard to get those FTFs when you don't even know about the cache! How does a feature that has seemingly been working perfectly for at least three and a half years (as long as I have been using it) suddenly turn to poop?

I have been having the same problem on a regular basis lately. Today it is really bad. It is rather difficult to plan a caching trip when the website does not provide its most basic function!