Project-GC - User contributions [en]

Talk:Challenge checker

2020-12-29T17:29:28Z

212719: added

Does the challenge exceptions info really belong on this page? This page is about challenge checkers and not challenge caches and the info is already available at [[Challenge cache]]s?
--[[User:4523550|4523550]] ([[User talk:4523550|talk]]) 22:51, 28 December 2020 (CET)
:I guess it's a bit of perspective of who you are, and from where you come from. The one who added the information makes challenge checkers, since it's very/too common for them to get their checkers disabled due to these issues I assume he found it relevant to checkers. My suggestion would be to merge the information and have it on the [[Challenge cache]]s page, and leave a link in the [[Challenge checker]]s page. Regardless, better in two places than zero places. But one place is probably best, combined with links.
: Also I am not 100% certain that everyone can view the exception list, but I can be wrong. I don't think everyone can add an exception at least, that should be the same code as voting.
:--[[User:3305483|3305483]] ([[User talk:3305483|talk]]) 10:10, 29 December 2020 (CET)
:: Only voters can view the exceptions list as far as I know. Atleast I can only view it with the account that has voting access so unless there are added restrictions for not having paid membership I'd say it's voters only. A link to the info at [[challenge cache]]s does make more sense to me.
::--[[User:4523550|4523550]] ([[User talk:4523550|talk]]) 11:16, 29 December 2020 (CET)

Hi - I added this as I noted the article of exceptions was missing from the challenge checkers section - I added it to the 'checker' section as the 'Challenge exceptions' tab (used to be called 'moderators') is found when you click in the 'challenge checkers' tab under tools - so felt that was a logical place to put this article
I have always been under the impression that anyone could see the exception list but only 'moderators' could vote - I can be corrected on that and will amend the article if that is the case.
Also I hadn't spotted the duplicate article under challenges - I can delete my article if it is felt inappropriate
Also you'll realise I haven't worked out how to contribute to this 'Talk' section properly ;-)

Talk:Challenge checker

2020-12-29T17:21:01Z

212719: add comment

Does the challenge exceptions info really belong on this page? This page is about challenge checkers and not challenge caches and the info is already available at [[Challenge cache]]s?
--[[User:4523550|4523550]] ([[User talk:4523550|talk]]) 22:51, 28 December 2020 (CET)
:I guess it's a bit of perspective of who you are, and from where you come from. The one who added the information makes challenge checkers, since it's very/too common for them to get their checkers disabled due to these issues I assume he found it relevant to checkers. My suggestion would be to merge the information and have it on the [[Challenge cache]]s page, and leave a link in the [[Challenge checker]]s page. Regardless, better in two places than zero places. But one place is probably best, combined with links.
: Also I am not 100% certain that everyone can view the exception list, but I can be wrong. I don't think everyone can add an exception at least, that should be the same code as voting.
:--[[User:3305483|3305483]] ([[User talk:3305483|talk]]) 10:10, 29 December 2020 (CET)
:: Only voters can view the exceptions list as far as I know. Atleast I can only view it with the account that has voting access so unless there are added restrictions for not having paid membership I'd say it's voters only. A link to the info at [[challenge cache]]s does make more sense to me.
::--[[User:4523550|4523550]] ([[User talk:4523550|talk]]) 11:16, 29 December 2020 (CET)

Hi - I added this as I noted the article of exceptions was missing
I added it to the 'checker' section as the 'Challenge exceptions' tab (used to be called 'moderators') is found when you click in the challenge checkers tab under tools - so felt that was a logical place to put this article
I have always been under the impression that anyone could see the exception list but only 'moderators' could vote - I can be corrected on that and will amend the article if that is the case

Map of challenge caches

2020-12-29T17:07:31Z

212719: /* grammar edit */

[https://project-gc.com/Tools/Challenges?map Map of challenge caches] is a tool for user's with a [[paid membership]] that shows [[challenge cache]]s on a map.

Filters available are:

* Location - Country/Region/County
* [[D/T|Difficulty/Terrain]]
* Cache name contains
* Exclude: Disabled, Archived, Premium, Fulfilled, Not fulfilled.
* [[Challenge checker]]s in the format Show all/Has checker/Missing checker - If left at 'Show all' this can be toggled in the map.

The map has the standard [[map feature]]s, like for example hiding/showing your finds or owned geocaches. Under the map it shows how many [[challenge cache]]s the filtration resulted in, how many of them have a [[challenge checker]] and the percentage of caches with a challenge checker. The feature to toggle between Show all/Has checker/Missing checker is in the menu in the top right corner at the bottom of the list of possible maps to use.

[[Category:Tools]]

Overview

2020-12-29T16:58:10Z

212719: /* grammar edit */

The [https://project-gc.com/Statistics/Overview Overview] shows some general statistics per country. The data is calculated once per week.

One should be careful when interpreting this data, there are many reasons why a trend could look negative. For example geocachers who don't log their finds for several weeks in combination with the fact that this data is only updated once a week would have an impact on these statistics. The weather can also cause differences over the years. Fewer geocaches hidden could in many areas be to the fact that the area actually is more or less full already.

The tables available in the overview are:
*'''Cache data'''
**Unique caches - Enabled/Disabled/Archived/Total
**Unique caches found - Current year/Last year/Difference
**Caches hidden - Current year/Last year/Difference
*'''Cachers'''
**Active cachers from the area - Current year/Last year/Difference
**Active cachers in the area - Current year/Last year/Difference
**Active cachers in ''and'' from the area - Current year/Last year/Difference
*'''Caches per [[D/T]]'''
**All types
**Traditional caches
**Unknown caches
**Multi-caches

[[Category:Statistics]]

Statbar

2020-12-29T16:56:04Z

212719: /* Additional info */

[https://project-gc.com/Profile/Statbar Statbar] is a small sample of the user's statistics that can be used in forums or on other web pages. [[Project-GC]] provides two different kinds of statbars, one with the basic numbers and one based on the [[BadgeGen]].

==Basic statbar==

The basic statbar includes the numbers listed below, a custom quote can be added to the statbar. Users with a [[paid membership]] can choose to include [[lab cache]]s in their statbar.

*Found - How many caches this cacher has found
*Hidden - How many caches this cacher has hidden
*[[First to Find|FTF]] - How many caches this cacher has logged FTF
*Logs - This refers to the number of logs on the user's hidden caches.
*[[Karma]] - This is the caching karma = #finds on own hides/#finds by this cacher
*[[Favorite point]]s - How many favourite points on cachers own hides

==BadgeBar==
The "BadgeBar" is based on [[BadgeGen]], it shows [[All Badges|all badges]] the user have earned and their [[BadgeGen Belts|belt]]. [[Country Badges|Country badges]] are not shown.

[[Category:Profile]]

SolvedMysteries

2020-12-29T16:48:02Z

212719: /* grammar edit */

[https://project-gc.com/Profile/SolvedMysteries Solved Mysteries] is a tool for users with a [[paid membership]], the idea of the tool is to plot all caches that the user has solved on a map. There are some problems with this. The solutions or '[[corrected coordinates]]' are gathered by the site in two different ways, the first one is to parse them from the user's [[personal cache note]]s and the second is to find the actual [[corrected coordinates]]. Unfortunately the [[Geocaching Live API]] does not support the retrieval of all the corrected coordinates of a user with one single API-call and neither can it report which geocaches a user has corrected coordinates for, so [[Project-GC]] can not retrieve just those caches. However, it is possible to retrieve all the user's [[personal cache note]]s in this way, so that is the best way for a user to make sure that the tool finds all their solutions.

If a cache note has several coordinates, the first one will be used as the final coordinate. If a cache has both corrected coordinates and a cache note with coordinates in it, the corrected coordinates will be used.

Project-GC will look into methods to find all the corrected coordinates for selected areas for a user in the future.

The tool is map-based and have some of the standard [[filters]] available, the resulting map have the standard [[map feature]]s allowing a user to add selected geocaches to a [[Virtual GPS]] or turn of found or hidden caches for example.

[[Category:Tools]]

User:212719

2020-12-29T14:45:43Z

212719: /* update */

Deepdiggingmole (or '''ddm''') has been a user of PGC since 2014 - though as a finder of caches he began that way back in 2004.
'''ddm''' is a fan of challenge caches and enjoys the variety that there are out there and the extra spin that challenge caches have given the game of geocaching.
'''ddm''' joined the team of moderators who vote on caches that are placed on the challenge exception list and is quite vocal in the exception list forum ;-)

TopFav

2020-12-29T14:25:44Z

212719: /* grammar edit */

[https://project-gc.com/Statistics/TopFav Top Favorite Caches] is a [[top list]] of the geocaches with the most [[favorite point]]s, the normal [[filters]] can be applied. When the [[filters#Profile name|Profile name-filter]] is applied, the caches the user has logged are marked in green. There are buttons for creating a map of the first X number of caches or adding the first X number of caches to a [[Virtual GPS]].

[[Category: Statistics]]

Event

2020-12-29T12:21:11Z

212719: info edit

[[Project-GC]] considers the following geocache types to be '''Events''':
* Event Cache
* Mega-Event Cache
* Giga-Event Cache
* Cache In Trash Out Event
* Community Celebration Event (formerly ''Lost and Found Event Cache'')
* Geocaching HQ Celebration (formerly ''Groundspeak Lost and Found Celebration'')
* GPS Adventures Exhibit
* Geocaching HQ Block Party (formerly ''Groundspeak Block Party'')

[[Category:Site Info]]

Event

2020-12-29T12:19:31Z

212719: addition of information

[[Project-GC]] considers the following geocache types to be '''Events''':
* Event Cache
* Mega-Event Cache
* Giga-Event Cache
* Cache In Trash Out Event
* Community Celebration Event
* Geocaching HQ Celebration (former ''Groundspeak Lost and Found Celebration'')
* GPS Adventures Exhibit
* Geocaching HQ Block Party (former ''Groundspeak Block Party'')

[[Category:Site Info]]

Main Page

2020-12-29T12:13:57Z

212719: /* Special */ grammar edit

<nowiki /><indicator name="PGC return"><span style="font-size:20px" align="right">Return to [https://project-gc.com Project-GC]</span></indicator>

Welcome to [[Project-GC]]'s wiki! Every [[Geocacher]] is welcome to edit Wiki-pages here. If you are interested, checkout the [[Welcome]]-page for some additional information. This main page serves as a navigation tree for the wiki, when possible the navigation tree should mirror the menus at the main site.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Popular items ==
* [[Data synchronization]]
* [[BadgeGen]]
* [[Profile Stats]]
* [[360 from home]]
* [[Challenge checker]]s

== Main site ==
* [[Project-GC]] - An introduction to Project-GC
* [[Filters]] - A description of the common filter system Project-GC uses
* [[Advanced search]]

=== Home ===
This is the articles related to the menu labeled "Home" at the main site.

* [[PGCPoints|PGC Points]]
* [[paid membership|Membership]]
* [[UserScript|Web browser extension]]
* [[Community support]]

=== Special ===
* [[Antipode caches]]
* [[Continent]]s
* [[Event]]s
* [[Geocaching-country to OSM-ID mappings]]
* [[Tools in the checker system]]
* [[:Category:Site Info|Site Info]] - This is a wiki-category with general site info, explanations of words etc.

== Profile ==
These are tools related to the account that is currently [[authenticate]]d with Project-GC.
* [[SolvedMysteries|Solved Mysteries]]
* [[FTFList|FTF List]]
* [[FindBadLogs|Find Bad Logs]]
* [[Statbar]]
== Statistics ==
[[Top list]]s and other statistics.
===General===
* [[Overview]]
=== Profile ===
* [[Profile Stats]]
** [[Profile Stats settings]]
** [[Finds tab]]
*** [[Log similarity]]
** [[Milestones tab]]
** [[FTF tab]]
*** [[First to Find]]
** [[Hides tab]]
** [[Maps tab]]
** [[BadgeGen tab]]
*** [[BadgeGen]]
**** [[All Badges]]
**** [[Country Badges]]
**** [[BadgeGen Belts|Belts]]
**** [[BadgeGen v3 vs v4]]
** [[Challenges tab]]
** [[Souvenirs tab]]
** [[LabCaches tab]]
* [[Progress]]
* [[StatCompare|Stat Compare]]
* [[TopFavor|Who favors who?]]

=== Cache stats ===
* [[TopLoggedCaches|Top Logged Caches]]
* [[TopFav|Top Favorite Caches]]
* [[TopFavPct|Top Favorited Caches (%)]]
* [[TopFavWilson|Top Favorites (Wilson)]]
* [[TopMostLogImages|Top caches with most log images]]
* [[TopElevation|Top elevation caches]]
* [[TopElevationlowest|Top elevation caches (lowest)]]
* [[DaysSinceLastFound|Days since last found]]
* [[LonelyCaches|Lonely caches]]
* [[CachesPerArea|Caches per Area]]
* [[FPPerArea|Favorite Points per Area]]
* [[FPPerDT|Favorite Points per D/T]]

===Trackable stats===
* [[TopDiscoveredTrackables|Top discovered trackables]]

=== Find stats ===
* [[TopFavoritePointsLogged|Top Favorite Points cached]]
* [[TopSouvenirCollectors|Top Souvenir Collectors]]
* [[TopMDCachingPoints|Top MD Caching Points]]

===Hide stats===
* [[TopHidden|Top Geocaches Hidden]]
* [[TopLogsReceived|Top Logs Received]]
* [[FavGained|Top Favorite Points Received]]
* [[TopLogImagesReceived|Top Log Images Received]]
* [[TopKarma|Top Caching Karma]]

===Over time===
* [[LogsPerDate|Logs per date]]
* [[HiddenPerDate|Hidden per date]]
* [[LogsOverTime|Logs over time]]
* [[LogsReceivedOverTime|Logs received over time]]
* [[FPOverTime|FP over time]]

== Tools ==

=== Map based ===
* [[MapCompare|Map Compare]] - Compare your finds with other's on a map
* [[MapRegions|Map regions]]
* [[MapCounties|Map counties]]
* [[360 from home]]

=== Challenges ===
* [[Challenge checker]]s
* [[Map of challenge caches]]

=== Others ===
* [[DiscoverTrackables|Discover trackables]]
* [[PQSplit|PQ splitter]]
* [[NeededFoundDates|Needed found dates]]
* [[DTHistory|D/T History]]
* [[EventStatistics|Event statistics]]
* [[SouvenirList|Souvenir list]]
* [[MarkdownIncompatibleLogs|Markdown-incompatible logs]]

== User Profile ==
This is the menu that is found by clicking the username in the top right corner.

* [[User Settings]]
* [[NewCacheNotifiers|New cache notifiers]]
* [[EventNotifiers|Event notifiers]]
* [[CustomFilters|Custom filters]]
* [[Virtual GPS]]

Antipode cache

2020-12-29T12:13:09Z

212719: grammar edit

An '''Antipode cache''' is a specific kind of mystery that's plotted on one side of the earth, and has the final on the opposite side. These Geocaches are by default excluded from all Geographical statistics in the [[Profile Stats]] for example.

When Project-GC refers to '''Antipode caches''' it generally refers to both the above, and other geocaches with similar issues. Another example is traveling Geocaches, which actually shouldn't exist anymore, but they have existed. These geocaches generally don't follow the guidelines and the effect is that they cause statistical oddities.

Geocaching HQ maintains a [[bookmark list]] containing all these Geocaches<ref>[http://coord.info/BM1A6W6 Caches Excluded from Souvenirs and Statistics] at Geocaching.com</ref>, and we just follow their list where applicable.

==Notes==
<references />

[[Category:Site Info]]

Antipode cache

2020-12-29T12:11:59Z

212719: Grammar edit

'''Antipode caches''' is a specific kind of mystery that's plotted on one side of the earth, and have the final on the opposite side. These Geocaches are by default excluded from all Geographical statistics in the [[Profile Stats]] for example.

When Project-GC refers to '''Antipode caches''' it generally refers to both the above, and other geocaches with similar issues. Another example is traveling Geocaches, which actually shouldn't exist anymore, but they have existed. These geocaches generally don't follow the guidelines and the effect is that they cause statistical oddities.

Geocaching HQ maintains a [[bookmark list]] containing all these Geocaches<ref>[http://coord.info/BM1A6W6 Caches Excluded from Souvenirs and Statistics] at Geocaching.com</ref>, and we just follow their list where applicable.

==Notes==
<references />

[[Category:Site Info]]

Filters

2020-12-29T12:07:15Z

212719: /* grammar edit */

{{FIXME}}

==General Information==
Many [[Category:Tools|tools]] and [[top list]]s on [[Project-GC]] can have different filters applied to get different information. On some of them only a subsection of the filters can be used and some tools or top lists have filters that are only available for that specific tool or list.

==Profile name==
This filter highlights the user in a [[top list]], clicking the button with a blue silhouette and a pencil will fill the box with the user name of the [[authenticate]]d user. For the [[:Category:Tools|tools]] that can be used to compare something between two or more users, this filter has an extra box labeled ''Compare with'' for inputting other users who are to be compared. Users with a [[paid membership]] can use the button with a table on it to turn on ''multi compare''.

==Only people from==
''Details to follow''

==Cache location==
''Details to follow''

==None/One/Both/Owned found==
''Details to follow''

==Hide Disabled / Archived / Premium==
This filter allows a user to hide caches that are ''Disabled'', ''Archived'' or ''[[premium member only|Premium]]'' from the result. It is available in the [[top list]]s under [[Main Page#Cache stats|Cache stats]]. Checking the box for "found" will hide all the found caches for the user chosen in ''Profile name'' from the top list and so on.

==Hide Found / Owned / Not found==
This filter allows a user to hide caches they have found, caches that they own or caches they have not found. It is available in the [[top list]]s under [[Main Page#Cache stats|Cache stats]]. Checking the box for "found" will hide all the found caches for the user chosen in ''Profile name'' from the top list.

==Show Disabled / Archived==
''Details to follow''

==Center/Radius (km)==
''Details to follow''

==From/To Hidden date==
''Details to follow''

==From/To Log date==
''Details to follow''

==Cache type / size==
''Details to follow''

==Difficulty / Terrain ==
''Details to follow''

==Bookmark list==
''Details to follow''

==Ignore Bookmark list==
''Details to follow''

==Virtual GPS==
''Details to follow''

==Cache name==
''Details to follow''

==Custom filter==
''Details to follow''

==Route==
''Details to follow''

==Attribute required==
''Details to follow''

==Negative attribute required==
''Details to follow''

==D/T type / size==
''Details to follow''

==Loop==
''Details to follow''

Challenge difficulty

2020-12-29T12:00:16Z

212719: /* Grammar edit */

{{FIXME|reason=example not using findsPerDay}}

==What is it?==
For every [[Challenge checker]] in the system there is a ''Challenge difficulty'' calculated. The difficulty is based on on how many [[Geocacher]]s fulfill the challenge or not. Project-GC is running [[Challenge checker]]s in the background for tens of thousands of [[Geocacher]]s, this process is a part of the [[Auto-challenge-checkers|Auto-Challenge-Checker System]]. The result of these runs is used to calculate the ''Challenge difficulty''.

==How is it calculated?==
Basically the ''Challenge difficulty'' tells us what proportion of [[Geocacher]]s fulfil a challenge or not. The rating is an integer between 0 and 100, but should not be confused with percent. First off it's important to understand that the automatic challenge checker runs aren't automatically executed on the average [[Geocacher]], but more likely on the more hardcore [[Geocacher]]s. It's primarily executed on [[Geocacher]]s with more finds, regular users of [[Project-GC]] and also [[Paid membership|paid members]] of the site.

Then the [[Geocacher]]s the checker has been run on is divided into three categories:
* Region - [[Geocacher]]s that are determined to live in the same '''region''' as the [[Challenge]] itself.
* Country - [[Geocacher]]s that are determined to live in the same '''country''' as the [[Challenge]] itself, but not in the same region.
* World - All others

For each category a percentage of how many fulfil the [[Challenge]] is calculated. Then the results for each group is weighted different in the calculations, basically a list is created and the percentages are added into that list. A forth factor is also added into the mix, the number of finds per day.

The number of finds per day isn't used as the raw number itself, but rather as '(1-($numFinds/$daysOld))*100'.

Then the difficulty is calculated as '$difficulty = (3*$worldPercent + 5*$countryPercent + 10*$regionPercent + $findsPerDay) / (3+5+10+1)'.

It should also be noted that there are usually more cached checker runs in the system from more local [[Geocacher]]s than from those living far away.

==Example==
* The Challenge is placed in Texas, United States.
* 80% of the [[Geocacher]]s in Texas fulfil it.
* 40% of the [[Geocacher]]s in the other states of the United States fulfil it.
* 30% of the [[Geocacher]]s in the rest of the world fulfil it.
* Then to weigh these differently using coefficients a sum is created like this: 3*80+5*40+10*30.
* This sum is then divided by 18 (3+5+10).
* The ''Challenge difficulty'' ends up being 740/18 = 41.11, which is rounded down to 41. The values are always rounded down to the closest integer.

[[Category:Site Info]]

Challenge difficulty

2020-12-29T11:59:07Z

212719: /* How is it calculated? */ grammar edits

{{FIXME|reason=example not using findsPerDay}}

==What is it?==
For every [[Challenge checker]] in the system there is a ''Challenge difficulty'' calculated. The difficulty is based on on how many [[Geocacher]]s fulfill the challenge or not. Project-GC is running [[Challenge checker]]s in the background for tens of thousands of [[Geocacher]]s, this process is a part of the [[Auto-challenge-checkers|Auto-Challenge-Checker System]]. The result of these runs is used to calculate the ''Challenge difficulty''.

==How is it calculated?==
Basically the ''Challenge difficulty'' tells us what proportion of [[Geocacher]]s fulfil a challenge or not. The rating is an integer between 0 and 100, but should not be confused with percent. First off it's important to understand that the automatic challenge checker runs aren't automatically executed on the average [[Geocacher]], but more likely on the more hardcore [[Geocacher]]s. It's primarily executed on [[Geocacher]]s with more finds, regular users of [[Project-GC]] and also [[Paid membership|paid members]] of the site.

Then the [[Geocacher]]s the checker has been run on is divided into three categories:
* Region - [[Geocacher]]s that are determined to live in the same '''region''' as the [[Challenge]] itself.
* Country - [[Geocacher]]s that are determined to live in the same '''country''' as the [[Challenge]] itself, but not in the same region.
* World - All others

For each category a percentage of how many fulfil the [[Challenge]] is calculated. Then the results for each group is weighted different in the calculations, basically a list is created and the percentages are added into that list. A forth factor is also added into the mix, the number of finds per day.

The number of finds per day isn't used as the raw number itself, but rather as '(1-($numFinds/$daysOld))*100'.

Then the difficulty is calculated as '$difficulty = (3*$worldPercent + 5*$countryPercent + 10*$regionPercent + $findsPerDay) / (3+5+10+1)'.

It should also be noted that there are usually more cached checker runs in the system from more local [[Geocacher]]s than from those living far away.

==Example==
* The Challenge is placed in Texas, United States.
* 80% of the [[Geocacher]]s in Texas fulfills it.
* 40% of the [[Geocacher]]s in the other states of the United States fulfills it.
* 30% of the [[Geocacher]]s in the rest of the world fulfills it.
* Then to weigh these differently using coefficients a sum is created like this: 3*80+5*40+10*30.
* This sum is then divided by 18 (3+5+10).
* The ''Challenge difficulty'' ends up being 740/18 = 41.11, which is rounded down to 41. The values are always rounded down to the closest integer.

[[Category:Site Info]]

Challenge difficulty

2020-12-29T11:55:27Z

212719: /* What is it? */ grammar edits

{{FIXME|reason=example not using findsPerDay}}

==What is it?==
For every [[Challenge checker]] in the system there is a ''Challenge difficulty'' calculated. The difficulty is based on on how many [[Geocacher]]s fulfill the challenge or not. Project-GC is running [[Challenge checker]]s in the background for tens of thousands of [[Geocacher]]s, this process is a part of the [[Auto-challenge-checkers|Auto-Challenge-Checker System]]. The result of these runs is used to calculate the ''Challenge difficulty''.

==How is it calculated?==
Basically the ''Challenge difficulty'' tells us how big share of the [[Geocacher]]s fulfill a challenge or not. The rating is an integer between 0 and 100, but should not be confused with percent. First off it's important to understand that the automatic challenge checker runs aren't automatically executed on the average [[Geocacher]], but more likely on the more hardcore [[Geocacher]]s. It's primarily executed on [[Geocacher]]s with more finds, regular users of [[Project-GC]] and also [[Paid membership|paid members]] of the site.

Then the [[Geocacher]]s the checker has been run on is divided into three categories:
* Region - [[Geocacher]]s that are determined to live in the same '''region''' as the [[Challenge]] itself.
* Country - [[Geocacher]]s that are determined to live in the same '''country''' as the [[Challenge]] itself, but not in the same region.
* World - All others

For each category a percent of how many fulfills the [[Challenge]] is calculated. Then the results for each group is weighted different in the calculations, basically a list is created and the percentages are added into that list. A forth factor is also added into the mix, the number of finds per day.

The number of finds per day isn't used as the raw number itself, but rather as '(1-($numFinds/$daysOld))*100'.

Then the difficulty is calculated as '$difficulty = (3*$worldPercent + 5*$countryPercent + 10*$regionPercent + $findsPerDay) / (3+5+10+1)'.

It should also be noted that there usually are more cached checker runs in the system from more local [[Geocacher]]s than from those living far away.

==Example==
* The Challenge is placed in Texas, United States.
* 80% of the [[Geocacher]]s in Texas fulfills it.
* 40% of the [[Geocacher]]s in the other states of the United States fulfills it.
* 30% of the [[Geocacher]]s in the rest of the world fulfills it.
* Then to weigh these differently using coefficients a sum is created like this: 3*80+5*40+10*30.
* This sum is then divided by 18 (3+5+10).
* The ''Challenge difficulty'' ends up being 740/18 = 41.11, which is rounded down to 41. The values are always rounded down to the closest integer.

[[Category:Site Info]]

Challenge checker

2020-12-28T17:27:05Z

212719: Addition of Checker exception paragraph

== What is it? ==
A '''Challenge checker''' is a piece of program code that will check if a user have completed the requirements of a [[challenge cache]], per the guidelines of Geocaching.com a [[challenge cache]] published after April 21, 2015, must include a link to a web-based challenge checker. <ref>[https://www.geocaching.com/help/index.php?pg=kb.chapter&id=127&pgid=206 Guidelines for Challenge caches] at Geocaching.com's Help Center.</ref> So far Project-GC is the only allowed challenge checker.

== How does it work? ==
A challenge checker consists of two parts: a challenge checker script and a tag. The checker script is a piece of program code written in the programming language Lua. The same checker script can be used for multiple challenge caches (For instance, most calendar challenges are handled by the same checker script). The tag is what makes this possible. The tag links a checker script, a challenge cache, and (optionally) a set of parameters for the checker script. This means that the same checker script can be used both for a challenge that requires the user to have found 100 mystery caches and a challenge that requires the user to have found 1000 traditional caches, since the cache type and quantity of finds required is specified in the tag.

Project-GC also calculates how difficult a challenge is, more information at: [[Challenge difficulty]]

== Checker Requests ==
Challenge checkers are created by volunteers and can be requested in the [https://project-gc.com/forum/list?8 Checker request forums], make sure you read the READ FIRST-post before posting your request.

== FAQ ==
Visit [https://project-gc.com/Home/FAQ#3082063764 Project-GC's FAQ] to find answers to many of the most common questions.

== Related paid membership feature ==
If a user have a [[paid membership]] Project-GC automatically runs challenge checkers for the user in the background. See the article about [[Auto-challenge-checkers]] for more information.

With a paid membership there is no limit on how many challenge checkers you can run. Non paying users are only allowed to run 10 challenge checkers per 24 hours. The limit is a ''rolling rate limit''.

The [[Map of challenge caches]] is a tool that can show the [[challenge cache]]s of the world on a map. Different filters can be applied.

== Tools ==
The checker script system can be used to create different tools to check for statistics that are not otherwise available at the site. See [[Tools in the checker system]] for more information.

== Challenge Exceptions ==
By default all geocaches with the Challenge attribute will be considered as challenge caches. Exceptions to that rule can be added here [https://project-gc.com/Tools/Challenges?challengeExceptions Challenge Exceptions] Either by adding additional challenges, or by adding geocaches that shouldn't be listed as challenges. A group of cachers who have moderation rights vote on any caches that appear on the list.
A moderation team have been voting on caches for several years but when the introduction of the 'challenge cache attribute' was introduced it had been hoped that correct use of that would eliminate the need for moderation - however it soon became evident that moderation was still required and so this exception list continues to be used.

Though this list can be viewed by all, only the moderators have access to vote - The list is sorted on a confidence score, the more homogeneous votes, the higher the confidence. The order in the list is only updated on page load. Use the up-arrow to vote that it is a challenge, and the down-arrow if it's not a challenge.
The following was advice for moderators regarding voting consideration - Note that your vote shall not be based on today's Challenge guidelines but rather on the fact that the Geocache requires you to do something before/when logging it. You shall not take into consideration if it's a good challenge or not, neither if you like it as a challenge.

Only geocaches with a confidence score of at least 35% will be be considered as an exception. Three homogeneous votes should be enough for that, while for example 3 up-votes and 1 down-vote won't.

There is a forum available to discuss special cases and believes related to these exceptions. [https://project-gc.com/forum/list?12 Checker Exceptions Forum] The forum is readable by everyone, but only those with voting access can write in it.

== Notes ==
<references />

[[Category:Site Info]]