Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Nomex

  1. For the record, as the Publishing Reviewer, the Cache Owner gave me the first question to add to my Publish log. I gave them that option, or the option to post a Note on the Listing page. I have not personally visited the Virtual yet. I thought at the time, that there would be some finite number of questions that could be asked, but I did not concern myself with that issue, the same way I don't concern myself with the quality of a cache placement or say, how difficult or ridiculously hard a Puzzle cache is. As far as monitoring the Listing page, that's really up to the cache owner to resolve. Judging from their Profile, they still appear to be active (logged in yesterday). Out of curiosity, I put the Listing page on my Watchlist to see how it would be received, and judging from the Find logs, it appears folks are having a good time with it. Along similar lines, I own an Earthcache on my Player Account (different from my Reviewing Account) that requires a measurement as a Logging Requirement. In my instructions, I tell folks to use whatever is readily available, and as an example I used my son as a measuring tool. Since then, people have similarly used common objects like shoes, hats, hands and so forth to make the measurement.
  2. I just ran a CHS query for the last 30 days for your home area (based on your Finds and cache that you own), and came up with 17 Listings that have fallen below the CHS threshold, which doesn't sound too bad actually. In comparison, Oregon, in the United States, which is roughly the same size, has 60 Listings below the threshold (albeit, there are probably many more caches in the birthplace of Geocaching, than in your area), which is pretty typical for a relatively saturated Reviewing Territory like that. I would recommend, like RA mentioned above, to start utilizing the tools you have at your disposal and start posting some NA log types to alert the local Reviewer when you encounter these neglected Listings. Just glancing at the Review Queue, there's only half a dozen Listings waiting for Review in your area, so I can't really say there's much of a backlog of things to be done.
  3. I checked with my Reviewer account and didn't see any Published or Unpublished Listings near those coordinates or that fit the description. I saw 4 Puzzle caches within 2 miles, but the Finals are not really anywhere near those coordinates. I noticed a handful of caches in the area with Archived Notes by the local Reviewer mentioning that permission is required for that area, so it might be someone tried but failed to get permission, and never bothered to submit a Listing page, or did make up a page and ended up changing it and using it for another submission at another location.
  4. Taken care of. TOU violation and not tolerated in any territory.
  5. Thanks for asking winne62, and there's no problem with asking questions if you don't understand the process. If you go to your Listing page at the following link: https://coord.info/GC8C1DP You should see the following banner at the top of the page: Click on the "Respond" link on that banner, and that should take you to a form to fill out a Reviewer Note. Press "Submit Log Entry" towards the bottom of the page after you have finished typing your response, and that's it. The Reviewer should get back to you soon if they need additional information, or they'll just Publish the Listing if they are satisfied with your response.
  6. The Reviewer stated in their Disable Note to post a Reviewer Note on the Listing page. I prefer doing it that way myself, as it keeps the conversation all in one place, so it's easier to follow. Trying to keep track of email and Friend Requests merely slows down the process. Your Listing is already Enabled, so they should see any Notes that you add now.
  7. Actually, I have it scheduled for Archive in about a week, or 30 days from the Note that I posted. And yes, I have reminded the OP on 2 or 3 occasions since, as they continue to submit new Listings for Publication. I've also informed them that I will no longer honor any timed Publications from them if they are going to waste my time in this manner. Not condoning the other Users response to the request to save space on the logsheet (and I see it quite a bit), but deleting logs generally crosses the line between polite request and an ALR in my view.
  8. Your Listing page is created, but is in a Disabled state, so the Reviewer will not currently see it in the Review Queue. Aside from the issue you've encountered, I noticed a flag regarding some restrictions for physical caches that came up on your Listing page. You may want to resolve that issue before submitting your Listing for Review. Just to save you some time in the long run. Link to relevant State Park Policy: https://wiki.Groundspeak.com/display/GEO/Michigan+DNR+Lands
  9. No, although HQ Policy suggests to prioritize Events and CITO ahead of other cache types, due to the time sensitive nature of those cache types. Your Listing appears to be awaiting an additional review from the original Reviewer. Keep in mind, your area is covered by a worldwide Reviewer, so they have a number of areas to look through. Your patience is appreciated. Also looking at your Listing page, there are a number of complications involving external links which requires additional work to track down if the offsite websites are allowed or not. This sort of arrangement for a Multi is unusual, and creates some additional complexity to the Review process.
  10. I just went through the process twice without incident. I can see 3 Listing pages that you completed today, and are awaiting Review. Are you still having issues?
  11. I can't even begin to describe how many of your assumptions are so wrong on so many levels. The process is not about the cache, as much as it is about the cache owner. There are no "bad caches" (as you put it), only unresponsive cache owners, that seal the fate of the Listing page. I can't tell you the number of times cache owners have asked for more time, and I was happy to grant it. I can't tell you the number of times a previous Finder verified the cache placement, and I was happy that is was still there in spite of no response from the CO. Even after Archival, I can't tell you the number of times I've had CO's email me afterwards but due to [insert things in life more important than geocaching here] couldn't respond to my Note, and tell me the cache was there all along, with a polite request to Unarchive the Listing page, which I was happy to oblige. I'm sorry to say, that your two experiences (one in which you DID respond, and one in which you DID NOT), do not begin to demonstrate the entire spectrum of possible outcomes that are available to an active cache owner. Responding to my Note is the safest option to keep the Listing page active, and it has been that way for the nearly 15 years that I've been Reviewing. The only thing that has changed in those years has been the volume of Listing pages that have to be looked at.
  12. Just so there's no misunderstanding... No, I did not "work with these people', as you put it. These were just civic minded Community members that identified a problem and wanted it fixed. I guess you could construe some sort of coordination, in so much, as they would post an NA, and I would feel obliged (one might even say Required as part of my Volunteer duties) to respond. I'm not all that familiar with GSAK, but calling it "automated" might be a bit of a stretch. The filters and macro's are useful, but there sounds like some set up is required. To be honest, I'd rather use the website resources. I have no idea how GSAK compares to the CHS, other than what Keystone has offered in a prior post. Per my usual custom, I went through the last months of unresolved CHS flags that I passed over on my first look, as I thought the CHS was a bit too aggressive in some instances. I ended up Disabling a handful more, but generally, I've found the CHS to be useful, but that's not to say it's perfect. It still misses some things entirely. People who continue to post Finds after the cache is unusable or gone, throwdowns that last maybe a month, and then it reverts back to a string of DNF's. I'm not sure the CHS is going to catch all these sorts of issues, but it does a pretty decent job of catching the low hanging fruit, so to speak.
  13. How so? A few posts back you were saying how it was up to the Community to report these issues, and that’s exactly how I characterized it. I don’t use GSAK, so I’m not familiar with the development time line of the macro I mentioned. A “vigilante” is someone I would say has a bit more staying power to stay at the task for a sustained period of time. The small number of people that took it upon themselves to take on this task I wouldn’t characterize as being sufficiently dedicated to be labeled a vigilante, hence the need for a more automated method like the CHS.
  14. I'm with Keystone on this one. I can say categorically that the CHS has made a significant improvement on my workflow. I understand that YMMV, depending on the way certain Reviewers organize their work. As an example, as I stated earlier, I had a small number of Users in my area that would essentially do the work of the CHS (probably running GSAK/Cache Cop). They tended to post their NA's based on their searches once every month or two. This created quite a backlog of NA's to work through. Then at the end of 30 days, I would do the process again (sometimes over 100 Listings in a single day) to evaluate if the CO has apparently abandoned the Listing (e.g. non responsiveness), or has posted a plan to take care of the issue or provided some explanation. With the CHS, this work comes in 7 days a week, 24 hours a day. Instead of looking at 100's of Listings in a single sitting, I get maybe 6 to 12 in a day. Likewise the follow up is at a much more relaxed pace compared to before. Once a month, I can browse through the Listings where it seemed the CHS was a tad too aggressive in my opinion, where I decided not to take action, to see if there have been any changes or updates in the interim. Similarly, although I'm not sure why this is, the number of long Disabled Listings has decreased as well. This is a task I take on every other month or so. Previously, I had to run about 4 PQ's to cover my Reviewing territory. Nowadays, I can knock it out with 1 or 2 PQ's. I don't know if the CHS is to account for this change, but it's a very welcome side effect if so.
  15. I do a slightly different workflow than Keystone, but I average about 100 Archives a week for my area. Before the advent of the CHS, it was probably slightly less, but probably not by much. Perhaps the main reason for this, is the fact that prior to the CHS, we had a small group of individuals that were very active in either posting more NA's than they do now (I suspect they were utilizing GSAK/cache cop to do the sorting), or contacting me privately with a list of Archive candidates. That activity has essentially dried up since the CHS has been active. My apologies if you are still seeing problem caches in your area. Taking a suggestion from our Reviewing friends up North, I've recently started to scan through the Listings with active NM Attributes. I just finished up a PQ for your area, and on the first page alone, the radius was out more than 30 miles for active NM's, which doesn't sound all that bad to me for a densely populated urban area. Still, some things can fly under the radar for quite some time without any action (it's amazing what people will tolerate). If you have any specific Listings in mind, feel free to contact me privately with your concerns.
  16. That is correct. All but one of your Stages is less than 300 feet from TW's nearby Traditional. If you're pretty sure about where you were at the time, with respect to nearby caches, I'd suggest taking a look at your Stages and double check that the coordinates were entered correctly.
  17. Looking at your recently Archived submission, it looks like Stages 1-9 are too close to an existing Traditional cache (kind of looks like you basically made a circle around the Traditional). Like others have mentioned, you can have the Stages within your submission as close as you like, but all your Stages must be at least 528 feet from existing caches.
  18. I can see your two EC Listings in the queue, so rest assured that they have been submitted properly. As RA mentioned, EC Reviews can take a fair bit more time to get through the process.
  19. Sorry for the confusion bj. MNTA's suggestion of reusing the container for another submission, was the part I was concerned about. Groundspeak guidance to the Reviewers is to assure that the container being placed and represented on the Listing page, actually belongs to the person submitting the Listing page, and not purloined from some other cache location. This comes up once in a great while in my area, and I always have to ask if the User actually has permission from the original owner to reuse the container. If not, I'm required to reject the submission, and ask the submitter to contact the original owner for permission, and to make it clear on the Listing page what is going on, when it gets resubmitted. In your scenario, what a cache owner does to "tidy" up the area of duplicate (or more) containers, is not generally considered the concern of the local Reviewer.
  20. I don't know, a Smiley sounds like scant reward for public humiliation in the Forum to me Edit to add clarification so there's no misunderstanding. Reviewers do not have the admin privileges to take actions on individual accounts. Only the Staff at HQ can do that.
  21. Done. Ummmm....no. That would be called stealing.
  22. Citation needed. Geez! I thought I'd missed something, so I went back and checked the Volunteer Expectation page, and I didn't see any reference to the CHS or "quality".
  23. Done. Oddly enough, I did look around at previous Listings in the area, to see if there were any issues raised by the Land Manager in question. Two that were actually much closer to the lake, now Archived, didn't seem to have any problems with the Parks people (one Archived for non responsiveness to an NA request, and the other Archived voluntarily by the CO). The cache in this situation looks like its reachable from an adjacent paved pathway. Regarding the issue with the mass Archival on some lands managed by the same Park Agency, I was actually contacted directly by the Land Manager, after they gave a rather fruitless attempt to contact cache owners themselves, and wanted some help resolving the issue with the closed area. I had one or two emails following that episode, from cache owners telling me they had the best of intentions of talking with the Land Manager to work things out. I had to explain to them, that no, when you get contacted by a Land Manager, you Archive your Listing first, then you go have the conversation to get it reinstated, not the other way around.
  24. It would be kind of unusual to first to find on a cache in the Squaw Valley area, so my first thought was that you found an Unpublished Listing. Not that unusual for a popular vacation destination like Squaw to get a handful of vacationers dropping caches, submitting them on the website, and finding out that they won't get Published without some sort of maintenance plan. There was one such Listing that was rejected just West of High Camp, not to far from cache that kunarion mentioned. If it was an Unpublished Listing, you would not be able to log it online. The cache owner mentioned that there was a hot wheels, dice, little animal plastic chip clips, little parachute man toy in the cache container at the time of placement. If you could describe the route you took up to High Camp (looks like several possibilities), that might help narrow the search.
  25. Groundspeak guidance to Reviewers is to review Listings based upon their GC number, with the exception of Events/CITO's which can be time sensitive based on the 2 week limitation mentioned in the Guidelines. Looking at the Review Queue in my area, it appears that the Queue is sorted in this fashion as well, without regard to the Enabled date, although there are options available to sort by various headers in the Queue, if a Reviewer wants to sort it in some other fashion.
  • Create New...