Sorry Mate, I thought you had access since you already had one tagged. It's been attached to your GC. <a href="https://project-gc.com/Challenges/GCA3BEY/74026"><img src="https://cdn2.project-gc.com/Images/Checker/74026" title="Project-GC Challenge checker" alt="PGC Checker"></a> Cheers, -TGby travelingGeek - ARCHIVE Checker requests (completed)
VeteranTributes, let me know if you need anything else.by travelingGeek - ARCHIVE Checker requests (completed)
The script has been updated. I will support all of the standard filters now such as type and sizes. To configure it for Physicals only caches, add this to your configuration json: "types":["Letterbox Hybrid", "Multi-cache","Unknown Cache","Traditional Cache", "Project APE Cache", "Wherigo Cache", "Groundspeak HQ&quoby travelingGeek - ARCHIVE Checker requests (completed)
Hi VeteranTributes, I'll modify my script for you. Stay tuned.by travelingGeek - ARCHIVE Checker requests (completed)
The script has been updated to exclude locationless by type and the caches on HQ's "Caches Excluded from Souvenirs and Statistics" list. bluesnote you should be good now. Let me know if not. Thanks Pleu for the hint on how to test locationless. That helped a lot!by travelingGeek - ARCHIVE Checker requests (completed)
Thanks for pinging me on this vogelbird. I'll update my original script.by travelingGeek - ARCHIVE Checker requests (completed)
Sorry, I missed you message in May. I will give it a try.... although the need has long gone past. I'm still very curious about the virtuals.by travelingGeek - Method requests
They stated last week that the HQ Solution Checker script was complete... That didn't feel right to me. I found several examples where it didn't and posted to the release notes form on gc.com. HQ said: QuoteGeocaching HQ Thanks for reporting this! We have discovered the issue and are working on a fix. I hope they get that fixed up soon. I also looked at the power trails.... seby travelingGeek - Checker news
Groundspeak has run the script to add the "Geocaching HQ Solution Checker" attributes. Nykkole reported in the release notes thread that it may take a few days for the indexes to be fully updated.by travelingGeek - Checker news
Looks like HQ's Challenge Cache attribute script may have run. I spot checked a few of the local heavy hitters and their attribute count matches the Project-GC profile stats. I'm really surprised that HQ hasn't been more proactive with the Geocaching.com solution checker attribute. The data must be in one of their databases already. Seems like a simple join to me. But what dby travelingGeek - Checker news
I've got challenges in the queue just waiting for HQ to run their scripts so people can qualify for my new challenges.by travelingGeek - Checker news
Interesting. "first letter of attributes on caches" Does not appear to be in conflict with this (negative) criteria: "These cache page elements: cache titles, cache owner, GC Codes, publishing Reviewer, or cache page text." Vogelbird, did HQ say they would update the guidelines? I can see this coming up again. Ky, it would have been interesting. Thanks forby travelingGeek - ARCHIVE Checker requests (impossible)
> * Power trail - We hope that these will be added > to at least some trails, but we do not have a clue > of HQs plans. If they want it added to existing > trails, a helpful tool is a must in our > opinion. We do not know if that will exist. The release notes (perhaps updated) said: QuoteHQ Release notes Power trail attribute Note to cache owners: As a one-time communityby travelingGeek - Checker news
Good to know on the sizes. Look forward to hearing when HQ updates theirs.by travelingGeek - Checker news
So for those that are still using old school arrays for the attributes... to save you some typing, here's what you need to add: [69] = "Bonus cache", [70] = "Power trail", [71] = "Challenge cache", [72] = "Geocaching.com solution checker", [69] = "https://www.geocaching.com/images/attributes/bonuscache-yes.png", [70] = "httpsby travelingGeek - Checker news
I didn't think the challenge would be approved but the hider already had the reviewer's approval, so I went ahead with the checker. The Reviewer has since been informed and the cache has been archived.by travelingGeek - Miscellaneous
The bug has been fixed and the root cause identified. gc.com users can now opt out of providing their personal data. Normally, calls to PGC.ProfileId2Name(f.owner_id) will return the owner's geo nick name. Now however, it will return a string similar to the below if the user has "opted out" of sharing their info. §OPTOUT:1f4620331§ Any script that uses ProfileId2Nameby travelingGeek - ARCHIVE Checker requests (completed)
sorry for the delay in responding to this one. There was a similar problem on another checker that was caused by how Project GC implemented General Data Protection Regulation (GDPR). If you have found a cache published by someone who has chosen to hide their personal data then the pgc api will return their cacher ID renumbered above 2 billion integers to obscure who the original cacher is.by travelingGeek - ARCHIVE Checker requests (completed)
I have run that checker on cachers that have 18K and 36K finds successfully and then on DerLakaiMS (5K finds) and that times out. This is strange.by travelingGeek - ARCHIVE Checker requests (completed)
Hi rragan, Apologies this has taken so long to get done. My day job has been a bit crazy lately :) The script has been updated to include your suggestion and I've also updated the google spreadsheet. Good luck on completing this difficult challenge. I wrote the script years ago and just recently finally qualified. I'm going out to sign the log on the original earthcache chaby travelingGeek - ARCHIVE Checker requests (completed)
Hi rragan, I'll take a look. Just back from two weeks on the road so it may be a few days. Thanks for bring this to my attention. -Gregby travelingGeek - ARCHIVE Checker requests (completed)
Ah, yes, I see that that owning caches could pass muster to qualify. I'm looking forward to hearing what the reviewer has to say.by travelingGeek - ARCHIVE Checker requests (impossible)
Hi Katarn, This sounds like a cool challenge. To be sure we're on the same page, these are the requirements as I understand them: 1. Find 10 caches in Kern County California. 2. All 10 caches must <<at the time you claim a find on the challenge>> be one of the top 10 "loneliest caches" in Kern Count 3. The "loneliest cache" is is calculated byby travelingGeek - ARCHIVE Checker requests (impossible)
The cache has been published and found, so i think we can assume the CO was happy with the tag.by travelingGeek - ARCHIVE Checker requests (completed)
Hi, I know there is a ton on the plate, so feel free delaying your response. I was looking at GitLab today. Looks to me like it's just by Script number file name. I tracked down one of mine and tagged it with my project-gc username.... but i think it only tags the current version, so if i update it in the future, a tag search will return the old one. Any suggestion on how best to wby travelingGeek - Checker news
humm... yes I see your point. The fourms are OK, but seem somehow 1990s, eh? for example I replied two days late to your comment. I do not know if this is a symptom of the technology or of the community. Which comes first?? technology or community? I have no answers for you, but understand the delemia.by travelingGeek - Script development
The more I think about it, the more I think your attention is better served elsewhere :)by travelingGeek - Script development
Maybe I just got lucky, but i think it's within the spirit and specification of the new rules. I would add a stipulation that the hider of your finds can not be yourself... but who finds their own hides (exception of course of adopted caches) Would love to hear if someone tries to publish with this criteria.by travelingGeek - Script development
I think the "cache owner" as you list above would refer to me as the owner of the challenge cache. The intent with that rule is so that the owner can't change things so the searcher can/can't qualify. Since all of the finds have to be far in the past and archived caches are allowed, I think there is no way for the "cache owner" (of the challenge cache) to affect whby travelingGeek - Script development