From what I can see there is nothing wrong with the script itself, but some of the tags needs to be adjusted. From what I can see there are two affected tags, I can fix those. https://project-gc.com/Challenges/GC8G93J/46763 { "attr" : ["NOT Difficult climbing"] } will update to { "attr" : ["NOT Difficult climb"] } https://project-gc.com/Challenges/by magma1447 - Checker news
I'll look into this in 1-2 weeks. There are a few upstream changes coming "soon". These attributes should never exist as negative by the way. At least not according to the API data. | 2 | 2 | Access/parking fee | 0 | fee | | 3 | 2 | Climbing gear required | 0 | rappelling | | 4 | 2 | Boatby magma1447 - Checker news
It only lists the "positive names" because there are no negative ones. Project-GC never uses a name like "No parking available", if needed it would just say/show that the "Parking available" is unset. Neither does Geocaching.com? I am not sure this is data that should come from Project-GC since it's not Geocaching data. A good example would have to be shown tby magma1447 - Checker news
I don't think there are any official negative names? There are none listed in the api. From what I remember Project-GC doesn't express them differently when being negative.by magma1447 - Checker news
I might take a chance to make a global change using code. At least all attributes except "Boat" seems to have long names enough to not get any false positives. But if you find that something to change that shouldn't, you know why. Correction: No need to update them. It's just their text output that's affected.by magma1447 - Checker news
Correction: There is no need to update these. They can use old names in their output. UPDATED: 2 Access or parking fee => Access/parking fee Potentially affected challenge checker scripts: 551, 1190, 2599 UPDATED: 3 Climbing gear => Climbing gear required Potentially affected challenge checker scripts: 204, 551, 559, 596, 606, 607, 648, 696, 749, 892, 958, 975, 1048, 1050, 1100, 1by magma1447 - Checker news
We have seen reasons to update the attributes in the back-end a bit. With that we will also update them to the latest names used by HQ. These 40 attributes will have their names changed: (ID: X, old-name => new-name) ID: 2 Access or parking fee => Access/parking fee ID: 3 Climbing gear => Climbing gear required ID: 4 Boat => Boat required ID: 5 Scuba gear => Scuba gear requiby magma1447 - Checker news
The "quick" response was pure luck. I was looking for something else here and noticed it. Then I also had a task for today that included some waiting time, so I could jump a bit between the tasks. I just hope it works as it should. There is always a risk of missing something when copy/pasting too much.by magma1447 - Method requests
I have spent some time trying to track down where I read it. I can't find it. I did however get a confirm from a Geocacher that had asked HQ, who said it was ok.by magma1447 - Checker news
Two new methods added, I'll release them in a minute. GetHighestCaches() GetLowestCaches() They work more or less identical to GetOldestCaches(). I hope I didn't break anything with that one, moved quite a lot of code around. I have been running a checker using it in both Dev and Live, the result hasn't changed.by magma1447 - Method requests
If I recall correctly - Their documentation even says that you could/should log your own. Even sillier.by magma1447 - Checker news
Coordinates doesn't automatically get you the country, that's fairly complex and I am not sure that's a good route to walk either. However, it's likely that Project-GC will try to handle that at some point. But as long as they don't have a country field in HQs DB I don't think it's a good idea to use it. Mostly because it's not HQs intent. Yes, they mayby magma1447 - Checker news
I can't find that post either, even though I actually saw it this morning. I know I posted the DB schema definitions of the tables. There currently are no changes. I hope to be able to get the owner of them in the future, and maybe even coordinates. I don't know if they have coordinates for all or just some. Also, I don't know how relevant the coordinates actually are. Also,by magma1447 - Checker news
I have received "indications" on that Elevation generally/in some cases/in some forms are accepted for Challenges - Even though it's in direct violation of the Guidelines. In my opinion they should add a written exception, but there isn't. Anyway, that makes this request very reasonable. I'll see if I manage to get to the bottom of it today or tomorrow. Currently workiby magma1447 - Method requests
I could also ask HQ about their opinion. If they say that it shouldn't be allowed, elevation challenges can be denied already here in the process. Also they could make it clearer to their reviewers. What's your opinions on that? From my point of view - I am afraid to get more complaints about inaccurate elevation levels for mountains. They will never be exact without manually enteby magma1447 - Method requests
That's probably the reviewers fault, and maybe due to how the description is created. Continents isn't a real problem, if the description actually holds a full list of countries. Or at least it shouldn't be a problem then, in my opinion. Similar with Badges. A Challenge to get Diamond Rugged without further explanation I can understand a deny on. But if it's also describedby magma1447 - Method requests
Is this meant primarily for new Challenges? Challenge based on elevation would be against the guidelines. Source of criteria Challenge cache criteria - must come from information broadly available on Geocaching.com such as on the statistics page, cache placement dates, types, attributes, souvenirs, etc. - must be verifiable through information on Geocaching.com. Geocaching.com doesn'by magma1447 - Method requests
As vogelbird says. It's against the Guidelines to create such challenge. It has been tried, including appeals. HQ does not approve.by magma1447 - Method requests
I have an update from HQ. Challenges affected by this are considered "old" and were allowed when they got published. Therefore they have decided that they are allowed to keep using the old polygon data, just as their cache descriptions says. So, for those where it's possible, we can convert the checkers into using a polygon script, if we have the polygon data. I still have Prby magma1447 - Checker news
That's actually quite good in my opinion. That's how I expect most of these Challenges will be solved. I haven't heard from HQ yet though. I expect that to take at least a week. Therefore I think that script developer had a smart approach on things. The question is if it should have been allowed by the reviewer though, but that's a bit off topic here, not really our concern.by magma1447 - Checker news
I have asked HQ regarding Challenges that uses the old definitions. As I see it we have two options: 1) Force-archive Challenges using counties that doesn't exist anymore. 2) Create new Challenge checker using user-defined polygons. User-defined polygons aren't allowed for new Challenges. But as I see it, this is a different case. The Challenges already exists. We'll see hoby magma1447 - Checker news
Scripts 731 Left enabled Defaults to county = 'Ski' Affected tags: https://project-gc.com/Challenges/GC6JZGH/21077 https://project-gc.com/Challenges/GC5E54W/5917 The first is unused, the second is used by an active challenge. I will disable the second challenge and leave a comment.by magma1447 - Checker news
Scripts 826, 1463, 1495, 2486, 2489 Left enabled Not using county "Re", it's chemistry elements.by magma1447 - Checker news
Script 535 https://project-gc.com/Tools/Challenges?edit&scriptId=494 Left enabled Not using county "Re", it's chemistry elements.by magma1447 - Checker news
Script 494 https://project-gc.com/Tools/Challenges?edit&scriptId=494 Left enabled Not using county "Re", it's chemistry elements.by magma1447 - Checker news
Script 1004 https://project-gc.com/Tools/Challenges?edit&scriptId=1004 Left enabled Using its own polygon data so won't be affected. It's likely that the related Challenge actually is against the Guidelines though. It would fall with user-defined polygons.by magma1447 - Checker news
Script 578 https://project-gc.com/Tools/Challenges?edit&scriptId=578 Left enabled The script has a default setting for region which will become unusable. The following tags rely on this default setting: https://project-gc.com/Challenges/GC52WBF/1729 https://project-gc.com/Challenges/GC52WMN/1731 https://project-gc.com/Challenges/GC52WMZ/1732 The related challenges are archived so I wiby magma1447 - Checker news
Script 873 https://project-gc.com/Tools/Challenges?edit&scriptId=873 Disabled Needs a new checker that requires the Geocacher to have found all geocaches in a county within a list of counties. That list should be the counties that used to be in Hordaland. Hordaland-counties: * Askøy * Austevoll * Austrheim * Bergen * Bømlo * Eidfjord * Etne * Fedje * Fitjar * Fjell * Fusa * Grby magma1447 - Checker news
Potentially affected tags (config matches a region/county that has been added/removed): tagId:5140 creator:Target. gccode:GC51QTB matches: tagId:16983 creator:vogelbird gccode:GC5FD2Q matches: tagId:16984 creator:vogelbird gccode:GC5FYZD matches: tagId:17002 creator:vogelbird gccode:GC568Q7 matches:by magma1447 - Checker news
Potentially affected scripts (source code matches a region/county that has been added/removed): scriptId:873 creator:kro8 scriptName:Alle cacher i en kommune i Hordaland matches: scriptId:578 creator:Draupne scriptName:Generic number of finds in region matches: [Østfold] scriptId:1004 creator:bjoff scriptName:SognOgFjordane, using boundaries from 31.12.2019 matches:by magma1447 - Checker news