A lot of checker tags had been missed so I did a couple of more today. modified: tags/00000000-00000999/976.json modified: tags/00010000-00010999/10386.json modified: tags/00011000-00011999/11020.json modified: tags/00011000-00011999/11021.json modified: tags/00011000-00011999/11023.json modified: tags/00011000-00011999/11024.json modified: tags/00011000-00011999/1by magma1447 - Checker news
Geocaching HQ recently announced that they had updated polygon data for three countries. Forum thread Project-GC today attacked this "problem". For Finland and Norway there are no changes in Project-GC due to this. But since we were looking at it we also updated our data to the latest OpenStreetMap polygon data. There should be zero name changes, but could be slight border changes.by magma1447 - Checker news
I am not surprised that reviewers rejected it. Or, they should at least ask HQ. But I am actually surprised that HQ rejected it. I'm my opinion it's within Guidelines. But I guess they didn't like the concept then, or are afraid of where it will head. A lot of time wasted then. :(by magma1447 - Checker news
All events should be refreshed now. It went faster than I hoped for.by magma1447 - Checker news
There are ~120,000 (25%) events left to refresh the data for. Since the newest ones have been refreshed first I would assume that the date you have found is the break point for when this feature was added by HQ, and that there won't be any new ones found.by magma1447 - Checker news
If you do, and remember, please post the outcome. I have a personal interest as well.by magma1447 - Checker news
This is this far undocumented, but there has just been added technical support in challenge checkers to retrieve information of which time events start and ends. The event start/end times can be retrieved by adding either event_start_end as a field to GetFinds(). Or event_start and/or event_end. The data will then be returned in the fields event_start_date, event_start_time, event_end_date, evby magma1447 - Checker news
We are currently in the process of updating the polygon data for Canada. Besides fresher and more correct data there shouldn't be many changes that will be noticed. Only one in fact. Greater Vancouver has been renamed to Metro Vancouver to match reality. I have only found one affected challenge checker and I have updated its configuration. tagId:39668 creator:pieterix gccode:GC82by magma1447 - Checker news
I don't think it can be told in a way that a human can for sure guess what's smartest. It's best to test. When set to true it's using a fully indexed data set. It's a column based database engine. It's just as fast regardless of how your query is more or less. It means that it will be slower than a normal row based database is (when using false) when those indexesby magma1447 - Checker news
Today I will be adding 2474 counties to Mexico (0 before). With this two regions are being renamed. From: * Coahuila de Zaragoza * Michoacán de Ocampo To: * Coahuila * Michoacán The only affected checker I found is: tagId:73779 creator:vogelbird gccode:GCA35JE scriptEnabled:1 tagEnabled:1 country:United States I will fix that config.by magma1447 - Checker news
It was actually unrelated to the above change. We recently added support for imperial units in BadgeGen. It was a required parameter when calling its "get data" function, but not such parameter was provided from the LUA callback. I have now fixed that. The LUA callback always uses imperial=false. Metric is the base unit for the rules, so imperials are just estimates. If a checkerby magma1447 - Checker news
I will release a change to GetFavorites() the coming days. A while back I made changes to GetOldestCaches/GetHighestCaches/GetLowestCaches so that the script writer can choose which DB cluster to use, by setting alternativeDBCluster to true (false is default). When setting it to true a DB cluster better at digging deep and processing lots of data will be used. But leaving it to false is betby magma1447 - Checker news
A while back we released version 4 of BadgeGen. We however left the old V3 ruleset so that it can be accessed in different ways. For example when loading Profile stats one can add the get parameter &bgv3. But also regarding LUA callbacks we didn't touch the existing api method GetBadgeGenData(). Instead we added a new one called GetBadgeGenDataV4(). For clarity I will today (in a fewby magma1447 - Checker news
I will push the updates now. This is the output from the compare script: LIVE Country areas: count=1 geom4326=41,281 km² geom4326_landonly=412,812 km² TEST Country areas: count=1 geom4326=41,281 km² geom4326_landonly=412,812 km² LIVE Region areas: count=26 geom4326=41,281 km² geom4326_landonly=412,812 km² TEST Region areas: count=26 geom4326=41,281 km² geom4326_landonly=412,81by magma1447 - Checker news
I forgot to update here. I didn't happen last week, for two reasons. The second oldest DB didn't have the data needed. The newest didn't have a working coastline in OSM. So we waited for the next OSM release which was just 2-3 days away. That was available to us late yesterday and since the three test imports have been made. It's starting to shape up and what's left isby magma1447 - Checker news
Next country to get new polygon data is Switzerland. We have two support tickets regarding changes for this country. Hopefully it will happen this week.by magma1447 - Checker news
All checkers except one has been tested. Waiting on a data update for that one. It's not like they are thoroughly tested, but at least they work and seem to give a correct result. These changes should be fully propagated on the servers within an hour from now.by magma1447 - Checker news
Checker tags are now enabled again. The modified checkers haven't been tested yet. The servers are still assigning new regions and counties on the geocaches.by magma1447 - Checker news
Import is in progress. Meanwhile these tags have been disabled: 16608 21198 22294 29101 29102 29103 38958 38982 45815 52262 52306 52332 52614 59057 62187 65589 68589 70863 All those also have new configurations, and out of those these have been linked a new script: 52614 59057 62187 65589 68589 70863 When the import is done I will enable those tags again, and @Pleu wby magma1447 - Checker news
@Pleu have done a tremendous work (hopefully) and prepared a lot of fixes for Challenge checkers. Hopefully we'll import the new polygon data today. During that import I will disable all challenge checker tags that needs fixing. Then we will apply fixes after the import is done, and also test them. In some cases it's changes in the tag config, in some cases we'll have to replaceby magma1447 - Checker news
Norway have had some major changes on the 1st of January this year. They are not implemented in Project-GC yet, but it's in progress. See this is a warning. Challenges that will be affected should probably be held of for a week or so. Norway is going from 11 to 15 regions. Norway is going from 356 to 357 counties. These regions won't exist anymore: * Viken * Troms og Finnmarkby magma1447 - Checker news
It will affect those two as well. It's the same code, just different fields it filters/sorts on. How big the effect is one those I do not know though.by magma1447 - ARCHIVE Checker requests (completed)
It's probably a smart way to do it. Because querying for a single country probably is ~1 second per country. The number of countries can be reduced from 250 by looking at which unique countries the profile name has logged, but it might still be more than a hundred. Anyway, read my latest post. Using the other DB cluster makes it run fast enough, with lots of marginal. 6-7 seconds for oneby magma1447 - ARCHIVE Checker requests (completed)
Actually, I changed that. I added a new optional parameter to GetOldest/Lowest/Highest. alternativeDBCluster (bool) defaults to false. I edited this script to use it and set it to true. That should solve this issue. I can't explain exactly when it's faster to use it or not, since I don't always know myself. But the more data that needs to be processed and the less the DB indby magma1447 - ARCHIVE Checker requests (completed)
Found the issue. GetFinds() and GetHides() returned the region in field <i>region_pgc</i> instead of <i>region</i> as before. I have updated the api callbacks since the change wasn't intentional. Today's update of Project-GC was actually triggered by challenge checker scripts that uses the GetOldestCaches/GetHighestCaches/GetLowestCaches callbacks. I had someby magma1447 - ARCHIVE Checker requests (completed)
@arisoft I was made aware of this one today. Is it because today's PGC updates that the script returns 0/48 for everyone I test (including the cache owner)? Or is it some changes you have made? I will try to understand it, but I have tested other scripts that uses PGC.GetOldestCaches, and they seem to work. Also, today's update is all about regions (as in the area size between countrby magma1447 - ARCHIVE Checker requests (completed)
Elevations of all geocaches will be updated the coming two weeks. The service provider we use has made major improvements and we therefore chose to update all our data. Primarily they have new sources which much better accuracy, but there is also some improvements in math for interpolations. The countries that will be improved the most are: * Denmark * Finland * France * Germany * Hong Koby magma1447 - Checker news
Adding 5 regions to this country. Formerly there was none according to Project-GC. Nothing should be affected by that I assume.by magma1447 - Checker news
If the beams/colored sectors doesn't extend to the border it is because there are no geocaches. The checker works as its intended to.by magma1447 - Miscellaneous
Updated polygons for South Korea. I let the names change to the latest in OSM since I don't think it affects anything. Otherwise I sometimes rename them to the old names to make it easier for the challenge checkers and such. There are three half relevant changes: * Ansan-si renamed to Ansan * Gwangmyeong-si renamed to Gwangmyeong * County moved from region (id=73311,osmId:-7816959) tby magma1447 - Checker news
