Jump to content

the Seagnoid

+Premium Members
  • Posts

    128
  • Joined

  • Last visited

Everything posted by the Seagnoid

  1. When editing a cache and clicking Save And Exit we now get the warning that changes may not have saved. Changes are actually saved, so its not a big problem, just annoyingly misleading. (Microsoft edge, Brave, probably others)
  2. I have a puzzle cache with a number of waypoints, GC3XWHY. A change at one of the waypoint locations requires me to make a change to the waypoint, but when I click Edit Cache or Add/Edit Waypoints no waypoints are listed. Clicking on Add Waypoint on the cache edit screen has no effect at all. (Microsoft Edge)
  3. "Rule" is exactly the word I meant to use. Logging ones own geocaches was frowned on so much that Groundspeak modified the API and website to prevent it. By specifically disallowing own logs they effectively made it a rule. I'm just surprised that they did not follow their own policy.
  4. Another area for improvement - please have the AL log emailed to the AL owner, same as happens with other geocaches.
  5. A standard geocaching rule implemented many years ago is that cache owners are not able to log finds on their own caches. The website and API were modified to enforce this . The Adventure Lab application allows lab cache owners to log finds on their own lab caches. Could we please get this fixed (and perhaps delete all those self logged logs as the adventure lab app came out well after the rule was introduced)
  6. A lab cache is a single find, an adventure lab is a set of five (sometimes more) lab caches. Lab caches have always been counted in statistics.
  7. Also the unpublished hides page - https://www.geocaching.com/play/owner/unpublished
  8. Also Unpublished hides - I have a cache ready to submit and now I can't! https://www.geocaching.com/play/owner/unpublished
  9. As Viajero Perdido says, it is obvious that pocket queries are working fine for the vast majority of people. Try a pocket query from a computer you have never used before. If that works then the problem is likely to be bad cookies. Delete them all and try again.
  10. At first I thought this was a bug in the Adventure Lab mobile application, but it looks like it is a website processing fault. For countries that are a long timezone away from Seattle, the date a lab cache is posted in Geocaching.com varies. Note that I live in New Zealand, 20 hours ahead of Seattle. I logged a lab cache approximately 8:30pm, New Zealand time, just after midnight of the same day, Seattle time. The date is correctly recorded in My profile > Geocaches > geocache finds > Lab caches, however the date here is not the date used to post the find into the general geocaching statistics. I am running a streak at the moment and and the streak was not updated after logging the adventure lab. Luckily I had found another cache so that my streak continues. Please correct the dates that adventure labs are logged into geocaching statistics to ensure that it uses the date on the mobile device.
  11. Why disable it if it is still findable and logable? Obviously if the maintenance needed is so extreme that the cache should be disabled then disable it.
  12. I logged an adventure lab in New Zealand at 4pm on 21 August New Zealand local time (equal to 9pm 20 August Seattle time), however looking at the activity report it shows my log at 22 August! A date that will not occur anywhere on the planet for at least another 8 hours. Please use the date on the local device for logging the activity reports, and confirm it carries the correct local time through to geocaching statistics. (Project-GC, for instance can also be a day out, I assume the dates it collects from Groundspeak are because lab cache finds are in Seattle time and not local time).
  13. Minor bug: Clicking on the detail (caches needing maintenance, caches disabled, etc) presents a number of pages of data equal to the number of caches in the listing. For example, if I have three caches needing maintenance, then clicking the Needs Maintenance button gives me three pages of detail. page one lists the three caches that need the maintenance, pages 2 and 3 are empty. Looks like the wrong variable got used for establishing number of pages needed! Corrections - an apparently unlimited number of pages!
  14. EXCELLENT!!! Groundspeak has not been great at keeping owners advised of the status of caches that need work, this does the job brilliantly. My only suggestion is to reduce the amount of space taken up be the cache listing in the main view on a PC browser. Ie reduce all the white space between lines. On a phone is fine.
  15. I like the idea if a sock puppet account - A Needs Maintenance Autobot that uses advanced AI (ie, me) to intelligently read Found logs to detect for maintence needed on my caches that are difficult to get to . The easy ones, of course get maintenance immediately, but as numerous others above state, needing maintenance does not necessarily mean the logbook is affected in such a way that the cache needs to be disabled.
  16. Yes. What is the point of a Needs Maintenance log except to alert the CO that they need to plan a maintenance trip? Going out on the day is not always feasible, especially where the caches require significant effort to reach. Given that, why can I not have a single list of ALL my caches that need maintenance?
  17. It is far easier to sort the problem myself, than to try to retrain the entire geocaching community! (or at least, all the ones that need training)
  18. @LOne.R - perhaps you should read the original post. Your suggested methods to not pull the complete list of caches needed maintenance.
  19. When the ability to log a find on your own caches was removed (and quite rightly, too) the ability to log a Needs Maintenance on your own cache was also removed. However many people who log a find and state that there is a problem that needs fixing, state that in their find log and do not log a Needs Maintenance. As a result Cache owners have to maintain a manual list in addition to the one that Groundspeak so nicely provides. The Groundspeak list can be accessed via a scheduled pocket query, or through Project GC's Needs Maintenance query. But the manual entries the cache owner needs to keep (or more likely, tries to remember) - is not so nicely stored, and certainly not in the same consolidated place. Could we please have just one list of all caches we have that need maintenance to help us manage our maintenance trips? Could cache owners please be able to log a needs maintenance on their own caches. This would help make managing maintenance easier, and so make cache maintenance more likely to happen, increasing the enjoyment for cache finders.
  20. Benchmarks start with what two letters? It's probably not "BM"
  21. I am working on a new puzzle geocache, and I am after the code identifiers that geocaching uses. These can be used to construct a URL directly to a particular item (eg by using https://coord.info/xxxxxxx). Another clue is that these are the codes that tracking IDs may not start with (you will never see a tracking id that starts with GC) For example: GC - GeoCache - a geocache description GL - Geocache log - an individual geocache log TB - Travel Bug - a trackable's description TL - Trackable Log - an individual log of a trackable retrieve, visit, etc. PR - Profile - a player profile (mine is PR5DMHT) BM - BookMark - an individual list GT - GeoTour There are also common travelbug tracking codes, such as OC - Oak Coins - I do not need these. Are there any others? Do drafts have one?
  22. Title says it all. I get an error. Others get the same error so it is not just me.
  23. Hey! The final waypoint came back! All fixed now, many thanks all.
×
×
  • Create New...