Thanks vogelbird. Both works. I think I'll go for Pleu's this time due to the list. 50 is long, but not too long I think. It's nice with some extra data. But feel free to leave yours. Maybe I'll switch at some point and get the more collapsed output.by magma1447 - ARCHIVE Checker requests (completed)
That works. Thanks!by magma1447 - ARCHIVE Checker requests (completed)
GC-Code: GC9RJVQ Quoting the description. QuoteThe requirement is to have logged at least 50 geocaches which each have at least 1,000 favorite points. The when and where doesn't matter.by magma1447 - ARCHIVE Checker requests (completed)
GC-Code: GC9RJVH Quoting the description. QuoteThe requirement is to have logged five geocaches with at least 1,000 favorite points. The catch is that they need to be in different countries. You are of course allowed to log more geocaches with such amount of favorite points, and in more countries. But five of them must be in unique countries.by magma1447 - ARCHIVE Checker requests (completed)
GC-Code: GC9RJTF From the description: QuoteThe requirement is to have logged a sum of at least 10,000 favorite points in 5 different countries. Calculate this by summarizing all current favorite points of the geocaches you have found, per country (the challenge checker does it for you). Your existing finds will normally keep accumulating favorite points as long as they don't get archiveby magma1447 - ARCHIVE Checker requests (completed)
It's only ~3 months since last time, but Netherlands has been updated again. County Weesp is no more, it has been merged with Amsterdam. That should be the only change. The import and updating of data is in progress, and will be finished today.by magma1447 - Checker news
There is a double dot in the end of the sentence after "name". Besides that it seems to do what it should. Thanks.by magma1447 - ARCHIVE Checker requests (completed)
GC-Code: GC9R14B I thought this was going to be easy, but didn't find a good solution. Requirement: Log at least one challenge which has at least 50 FP. In more technical terms, count number of finds where: * Type = Unknown Cache * Attribute 71 set * favorite_points >= 50 1 find is enough.by magma1447 - ARCHIVE Checker requests (completed)
Perfect, thank you again.by magma1447 - ARCHIVE Checker requests (completed)
I need a checker that requires the geocacher to have a sum of (at least) 10,000 FP on Challenges logged. "Challenges" should be checked by being of type Unknown Cache and having the Challenge attribute set. So in short: * Filter on Unknown * Filter on Challenge attribute * Calculate sum of FP * OK if sum >= 10000 The GC-code is GC9R165.by magma1447 - ARCHIVE Checker requests (completed)
Approved. Thank you again. I am working on published over 50 challenges the coming weeks, so I might come with more requests. I am trying to do most of them myself though. :)by magma1447 - ARCHIVE Checker requests (completed)
You are probably right. I'll scratch that one! Thanks for reminding me.by magma1447 - ARCHIVE Checker requests (impossible)
The year has 12 months. I am creating two challenges which requires the geocacher to have logged full D/T in 3 respective 3 out of the 6 months. GC9R1B7: 3 months GC9R1B9: 6 months I have 12 months myself, but I seem to be the only one in Sweden having that, so I won't be able to publish a challenge that requires that much. A part of the description from one of them: QuoteThe requby magma1447 - ARCHIVE Checker requests (completed)
I am preparing to queue GC9R1A0. The description has this sentence, which I hope is clear enough: QuoteThe requirement is to have at least one date, for each month, where you have at least 100 finds. The year is irrelevant so you can work on this over multiple years. So in total 1200 finds is required, and is the minimum to complete it. In theory this would fulfill the requirement: 100 finby magma1447 - ARCHIVE Checker requests (impossible)
It works, thanks!by magma1447 - ARCHIVE Checker requests (completed)
Hi heroes! I am looking for a checker that requires the geocacher to have logged Full D/T on Monday + Tuesday + Wednesday ... Sunday. So in total a minimum of 7*81 finds. My GC-Code is: GC9R13J Here is a copy/paste of the requirement from the cache description: Quote The requirement is to have logged full D/T (81 unique difficulty/terrain combinations) for each of the seven weekdays (moby magma1447 - ARCHIVE Checker requests (completed)
I have added a new option to GetFinds(), it's still undocumented, but it's coming. excludeDupFinds = true can now be set in the second argument of PGC.GetFinds(). It will then remove all duplicate Found logs of the same Geocache, keeping only the first. Sorted by visitdate, log_id. Example: PGC.GetFinds(12345678, { "excludeDupFinds": true }) This makes it easier to solvby magma1447 - Checker news
Importing the new polygons now, to get the name corrections in there. I will have to do another import in a week to get a proper polygon for the country itself, but that shouldn't affect anything but visuals on maps. And probably not even possible to see the difference anyway.by magma1447 - Checker news
There are also these name changes, that are more of corrections. It must be some form of mistake on my part that they have a double suffix today. [*] Carroll County (IL) (Illinois) -> Carroll County (IL) [*] Carroll County (MD) (Maryland) -> Carroll County (MD) [*] Lee County (IL) (Illinois) -> Lee County (IL) [*] Morgan County (WV) (West Virginia) -> Morgan County (WV) [*] Souby magma1447 - Checker news
It's done. Project-GC is in progress of updating. Meanwhile both version will exist and create weird cases. Everything should be in place within 24h.by magma1447 - Checker news
I have a qualified guess that Bergen in Limburg was named "Bergen" only before. It's not perfect, but I can do it like that again.by magma1447 - Checker news
There seems to be one more difference. The site currently has these two: [*] Bergen (Limburg) [*] Bergen (Noord-Holland) Do you know what they were called before? I can dig up a backup configuration and figure it out. But maybe you can see it in some checker config? If I rename the second one to "Bergen (NH)" as suggested, the first one can be named "Bergen" only. Bby magma1447 - Checker news
Not sure how I could have missed that. If you wish, I could also update the name so that it's the same as earlier. A bit late since you already updated all your tags. But if there are many others it might be a smoother solution. The new name sounds slightly clearer though. I let you decide. :)by magma1447 - Checker news
I will update the polygon data for USA as well. There has been some renames in OSM, but I will rename them in Project-GC when importing, to make it easier for everyone. The only change I can see is that county Valdez-Cordova (AK) in Alaska will be split into two: [*] Chugach (AK) [*] Copper River (AK) The final import will take at least one more week until it happens. Waiting on polygon dby magma1447 - Checker news
Received this by a support ticket: Quote Changes as of 1-1-2022: -Heerhugowaard, Langedijk merged into Dijk en Waard -Boxmeer, Cuijk, Grave, Mill en Sint Hubert, Sint Anthonis, merged into Land van Cuijk -Landerd, Uden merged into Maashorst -Beemster has merged into the already existing Purmerend. OSM seems to do exactly what the above says. Import is in progress.by magma1447 - Checker news
This QA thread told us that Latvia has been updating their administrative borders. It turns out the difference is huge. Around 50 counties removed, and 3 new ones. Regions not affected. I used this search to find all Challenges in Latvia. If I didn't miss any, it's these two that are likely to be affected: https://www.geocaching.com/geocache/GC6PPPX_latgale-challenge-cache-lielaby magma1447 - Checker news
HQ has removed the old exception list with traveling geocaches and similar (BM1A6W6). A new list (with same/similar) content has been created on another account (BMAFMJR). In the future, make sure you refer to the correct list with the Challenge checkers. Tomorrow I will try to search and replace all occurrences of the old BM-code to the new one. Both inside the scripts, and the tags. There arby magma1447 - Checker news
The documentation for the distance callbacks (DistanceVincenty and DistanceHaversine) used to say that the script had to handle nil values for latitude longitude, which will happen with premium only geocaches for non premium users. However, latitude and longitude is in that case FALSE and not NIL. I have corrected the documentation (with the coming release). I have also added so that the distaby magma1447 - Checker news
We could also consider moving the data to the Wiki pages where anyone can edit them, and replace Targets sticky post with a post that links relevant Wiki-posts.by magma1447 - Checker news