Project-GC - User contributions [en]

FindBadLogs

2024-11-21T20:15:52Z

4523550: Added info about events and rewrote part of it.

[https://project-gc.com/Profile/FindBadLogs Find Bad Logs] is a tool that helps the user check for duplicate logs, both that the user has made and on caches the user owns. It also shows if the user has logged their own caches ([[event]]s are excluded). It's a known problem that adopted caches will show up as "Logged owned caches" even if they were logged before adoption. The tool also shows event that the user has logged on a date other than the hidden date of the event, and the amount of days that differ.

[[Category:Profile]][[Category:Tools]]

Map feature

2024-10-27T12:28:38Z

4523550: Adding category site info

==Description==
Most map-related [[Category:Tools|tools]] at [[Project-GC]] share the same standard '''map features''', the big exceptions are the [[TBRescue|TB rescue]], [[360 from home]] and the [[LiveMap|Live map]]. 360 from home-tool have a subset of the standard map features and some special settings, the Live map have all the standard map features and some extra filtering options. The TB rescue map lacks most of the standard map features.

==Maps==
The standard map that will show when opening a map-tool is [[OpenStreetMap]]. The button in the top right corner of the map allows the user to switch between different maps, users with a [[paid membership]] can use the quick button above it to enable Google Maps.

===Available maps===
* OpenStreetMap
* OpenStreetMap German Style
* Thunderforest OpenCycleMap
* Thunderforest Transport
* Thunderforest Landscape
* Hydda Full
* Esri WorldStreetMap
* Esri DeLorme
* Esri WorldTopoMap
* Esri WorldImagery
* Enrio Street
* Eniro Aerial
* Eniro Nautical

Additionally, users with a [[paid membership]] also have access to:
* Google Road
* Google Satellite
* Google Hybrid
* Google Terrain
* Lantmäteriet Topo (SE)
* Lantmäteriet Orto (SE)

Lantmäteriet however, are only relevant for Sweden<ref>[https://www.lantmateriet.se/ Lantmäteriet] is a Swedish authority for maps and properties.</ref> and only south of Haparanda. Different maps will be the best option for different areas. In the [[Map of challenge caches]] this button can be used to toggle between challenges with or without checkers, in most maps there are a setting to toggle all geocaches on or off here.

==Other buttons==
In the left corner there are a number of buttons that allows for different settings. Hoovering to show the tool tip will generally explain most of these like ''Full Screen'', ''Zoom in'', ''Zoom out'', and ''Measure distances''.

===PGC Controls===
This button is marked with the geocaching logo, this shows four different options and allows the user to choose to toggle these between 'on' and 'off'.

[[File:PGC Controls.png]]

The available options are:

* [[Corrected coordinates]] - this allows the user to show caches with corrected coordinates at the corrected coordinates or at their posted location.

* Owned - this shows or hides caches the user have hidden. Note that this is for the [[authenticate]]d user and not the user chosen in the [[Filters#Profile name|profile name filter]].

* Found - this shows or hides the caches the user have found. Note that this is for the [[authenticate]]d user and not the user chosen in the [[Filters#Profile name|profile name filter]].

* 161m circles - This creates circles of 161 meters/0.1 mile around the caches on the map. 161 meters is the minimum distance that physical stages of different caches must be apart, to avoid clustering.

===PGC VGPS Controls===
This button is marked with a slightly cropped version of the logo for the [[Virtual GPS]], it allows the user to add caches to the [[Virtual GPS]] or remove them from it.

[[File:PGC VGPS Controls.png]]

The first option from this button allows the user to draw a polygon on the map, multiple polygons can be drawn on the same map and does not have to be connected to each other. Polygons drawn on the map can be manipulated by moving the 'corners'/vertex with the cursor. The second option is a cross mark and can be used to remove a polygon.

The option with the Virtual GPS-logo and the plus sign adds all caches inside a polygon to the active Virtual GPS, the option with the minus sign removes all caches inside a polygon from it.

===Measure distance===
The button with a ruler-icon allows the user to measure distances on the map.

[[File:MeasureDistance.png]]

===Map Icons===
[[File:Pgc-cache-icon-corrected-cachenote.png]]
For more information about the cache icons on the maps and the different symbols shown on them, see [[MapIcons|map icons]].

==Notes==
<references/>

[[Category:Tools]][[Category:Site_Info]]

CustomFilters

2024-07-04T19:14:10Z

4523550: Added list of basic stats

{{FIXME|reason=WIP! Complete the documentation of the system.}}

==General==
[https://project-gc.com/User/CustomFilters Custom Filters] is a feature were users with a [[paid membership]] can create advanced pre-defined filters to use in some [[top list]]s and [[:Category:Tools|tools]]. Custom filters also include more filter options that are not always available in other filters, such as attributes and filters on recent logs. A pre-defined filter is created by the system as an example.

The page shows a list of the current filters the user has created, these can be edited by marking a filter and clicking the button labeled "Edit" or deleted by doing the same but using the button labeled "Delete". The button labeled "New" is used to create a new filter.

==Creation==
When creating a filter the user adds their own name to the box labeled "Filter name", the name is later used in the [[Filters#Custom_filter|filter-system]]. Next step is to add statements to the filter, added statements are listed under the name and can be edited or removed similar to how filters can be edited or deleted.

Adding multiple statements to a filter will give a filter that shows caches that match any of the different statement-rows. For example a statement that requires the attribute "Parking nearby" and a different statement that requires the attribute "Park and grab" would result in caches that have at least one of these attributes when used.

When all statements have been added the filter needs to be saved by using the button labeled "Save", this adds the filter to the list of filters and it's ready for use.

==Possible options==
When adding a new statement to a filter there are three tabs with different filtering options and a fourth [[NYI|not yet implemented]] option for Bookmark lists. Options from all different tabs can be combined into a single statement that can be added to the filter with the button "Add to filter".

===Basic stats===
This section includes some basic stats that are pretty self-explanatory.
* [[Premium member only|Premium only]] - Only premium caches
* No premium - Only basic caches
* Archived only
* No Archived
* [[Cache owner]]
* [[Favorite point]]s
* Percentage of favorite points
* [[Wilson score]]
* Location filter (Country/Region/County)
* [[Geocache#Geocache_types|Cache type]]
* [[Geocache#Geocache_sizes|Size]]
* [[D/T|Difficulty]]
* [[D/T|Terrain]]

===Attributes===
''Information to follow''

===Logs===
''Information to follow''

===Bookmark list===
This is a [[NYI|not yet implemented]] feature.

[[Category: Site Info]]

The Event Host

2024-06-15T16:05:49Z

4523550: /* Addons */ Correction regarding CCE/L&F-addons.

{{
Badge
|BadgeName=The Event Host
|MaxLoops=99
|BronzeRequirement=1
|SilverRequirement=2
|GoldRequirement=3
|PlatinumRequirement=5
|RubyRequirement=8
|SapphireRequirement=12
|EmeraldRequirement=18
|DiamondRequirement=30
|AddonsAvailable=366, Leapday, Mega, Giga, CITO, L&F
}}
{{Badge image|icon=TheEventHost|q=D}}
Host geocaching [[event|events]] to claim this badge. It's required that the events have happened, and have had at least one attendee.

== Loops ==
{{Badge image|icon=TheEventHost|q=D|loop=99}}
By doubling the amount required for ''Diamond'' the user will start looping this badge.

== Addons ==
{{Badge image|icon=TheEventHost|q=D|addons=366cal,leapday,mega,giga,cito,lostfound}}
* 366 - Host an event on every calendar day, including leap day, to enable this addon.
* Leapday - Host an event on Leap day to enable this addon. Any event type is sufficent.
* Mega - Host a Mega event to enable this addon.
* Giga - Host a Giga event to enable this addon.
* CITO - Host a CITO event to enable this addon.
* Community Celebration - Host a ''Community Celebration'' event to enable this addon. (Note that this does not appear if the L&F addon is also achieved)
* L&F - Host an event with the Lost and Found tour attribute to enable this addon.

== History ==
This Badge existed in BadgeGen v3.
* Addons were added.
* The events now requires attendees, an archived event that never happened doesn't count.
* Starting November 2021 the [[BadgeGen#Addons|addons]] also requires at least one attendee.

Profile Stats

2024-06-04T09:59:14Z

4523550: /* URL manipulation */ Reworded "at that date" -> "up to that date"+ added example of of how llh-manipulation can be used.

== What is it? ==
[https://project-gc.com/Statistics/ProfileStats Profile Stats] are the statistics of a profile. This is the place for checking out a user's [[BadgeGen]], a list of the profile's [[First to Find|FTF]]s, statistics about [[Challenges]] the profile has logged and much more. Profile Stats are strongly inspired by FindStatGen for GSAK.

A user can create a dynamic image of their '''Profile Stats''' to show them on their [[Geocaching.com]]-profile.

In [[Profile Stats settings]] the user can disable tabs, choose to include [[Lab cache]]s where applicable, hide their stats from others and more. Some of these settings are for [[Paying members only]].

== Tabs ==
Profile Stats consists of 61 modules spread across nine tabs. The tabs are:

*[[Finds tab]]
*[[Milestones tab]]
*[[FTF tab]]
*[[Hides tab]]
*[[Maps tab]]
*[[BadgeGen tab]]
*[[Challenges tab]]
*[[Souvenirs tab]]
*[[LabCaches tab]]

== Related paid membership features ==
For users with a [[paid membership]] the '''Profile Stats''' are generated daily. For non paying members they are generated weekly.

Users with a [[paid membership]] can choose to disable individual modules of the tabs in their Profile Stats, disabled modules are hidden both from the user and other players.

A [[paid membership]] lets the user include [[Lab cache]] finds in their Profile Stats where applicable.

==URL manipulation==
There are some 'hidden' features that can be accessed by manipulating the URL used to access the Profile Stats. For this to work the ''permanent'' link to the Profile Stats has to be used, the permanent link looks like this: <nowiki>https://project-gc.com/ProfileStats/Username</nowiki> where Username is a placeholder for the actual username.

If '''?bgv3''' is added to the URL, (i.e., making it <nowiki>https://project-gc.com/ProfileStats/Username?bgv3</nowiki>), the [[BadgeGen tab]] in the Profile Stats uses [[BadgeGen v3 vs v4|BadgeGen v3]] instead of the new [[All Badges|badges]].

If '''?llh=2012-05-09''' is added to the URL, (i.e., making it <nowiki>https://project-gc.com/ProfileStats/Username?llh=2012-05-09</nowiki>), the Profile Stats only uses the caches the user had found up to that date. The date is in year-month-day-format and any date could be used. For example this can be used to see how ones stats looked last year.

[[Category:Statistics]] [[Category: Profile Stats]]

File:Pgc-cache-icon-owned.png

2024-05-07T19:30:43Z

4523550: 4523550 uploaded a new version of File:Pgc-cache-icon-owned.png

== Summary ==
Unknown/mystery icon, with markers "owned" and "challenge fulfilled".

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

MapIcons

2024-05-07T19:28:24Z

4523550: Added icon with star. + rewrote the text in you-> the user style.

The geocache '''icons''' on the map-based tools in Project-GC contain a lot of information about the cache.

{| class="wikitable"
|-
|[[File:Pgc-cache-icon.png]]
|This is a basic geocache icon for a Traditional cache. The icon inside the plate will be different for different cache types.
|-
|[[File:Pgc-cache-icon-found.png]]
|The '''upper right corner''' will have a smiley in it on found caches.
|-
|[[File:Pgc-cache-icon-owned.png]]
| The '''upper right corner''' can also have a star in it. The star shows that the authenticated user is the owner of the cache. If the user has found the cache only the star will be shown. Here you can also see an example of when the cache icon is an Unknown cache instead of a Traditional cache.
|-
|[[File:Pgc-cache-icon-corrected-cachenote.png]]
|The '''lower right corner''' can have a small pencil in it. This indicates that the user has a [[personal cache note]] on the cache.
|-
|[[File:Pgc-cache-icon-corrected-cachenote.png]]
|The '''lower left corner''' can have a small green checkbox in it. This shows that the user has [[corrected coordinates]] on it. These can be either from the corrected coordinates field at [[Geocaching.com]], or parsed from a [[personal cache note]].
|-
|[[File:Pgc-cache-icon-success.png]]
|The '''lower left corner''' can also show if the user have fulfilled a [[challenge cache]] or not, in the case where Project-GC have a [[challenge checker]] for the cache in question. This is indicated by a different kind of green checkbox, with a circle around it. The checker indicators has higher priority than the corrected coordinates indicator.
|-
|[[File:Pgc-cache-icon-fail.png]]
|The third variant for the '''lower left corner''' is to show that the user has '''not''' fulfilled the requirements for a [[challenge cache]].
|-
|[[File:Pgc-cache-icon-notrun.png]]
|The fourth variant for the '''lower left corner''' is to show that the fulfilled/not fulfilled status of a [[challenge cache]] is not known yet.
|-
|[[File:Pgc-cache-icon-vgps.png]]
|The last corner, the '''upper left''' one, shows the user if the geocache has been added to their current [[Virtual GPS]].
|}

[[Category: Site Info]]

File:Pgc-cache-icon-owned.png

2024-05-07T19:21:40Z

4523550: Unknown/mystery icon, with markers "owned" and "challenge fulfilled". ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
Unknown/mystery icon, with markers "owned" and "challenge fulfilled".

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

MapIcons

2024-05-07T19:18:56Z

4523550: Added challenge cache result not known.

The geocache '''icons''' on the map-based tools in Project-GC contain a lot of information about the cache.

{| class="wikitable"
|-
|[[File:Pgc-cache-icon.png]]
|This is a basic geocache icon for a Traditional cache. The icon inside the plate will be different for different cache types.
|-
|[[File:Pgc-cache-icon-found.png]]
|The '''upper right corner''' can have either a star or a smiley in it. The star shows that you are the owner of it, and the smiley that you have found it. If both cases are true, only the star will be shown.
|-
|[[File:Pgc-cache-icon-corrected-cachenote.png]]
|The '''lower right corner''' can have a small pencil in it. This indicates that you have a [[personal cache note]] on the cache. Here you can also see an example of when the cache icon is an Unknown cache instead of a Traditional cache.
|-
|[[File:Pgc-cache-icon-corrected-cachenote.png]]
|The '''lower left corner''' can have a small green checkbox in it. This shows you that you have [[corrected coordinates]] on it. These can be either from the corrected coordinates field at [[Geocaching.com]], or parsed from your [[personal cache note]].
|-
|[[File:Pgc-cache-icon-success.png]]
|The '''lower left corner''' can also show you if you have fulfilled a [[challenge cache]] or not, in the case where Project-GC have a [[challenge checker]] for the cache in question. This is indicated by a different kind of green checkbox, with a circle around it. The checker indicators has higher priority than the corrected coordinates indicator.
|-
|[[File:Pgc-cache-icon-fail.png]]
|The third variant for the '''lower left corner''' is to show you that you have '''not''' fulfilled the requirements for a [[challenge cache]].
|-
|[[File:Pgc-cache-icon-notrun.png]]
|The fourth variant for the '''lower left corner''' is to show that the fulfilled/not fulfilled status of a [[challenge cache]] is not known yet.
|-
|[[File:Pgc-cache-icon-vgps.png]]
|The last corner, the '''upper left''' one, shows you if the geocache has been added to your current [[Virtual GPS]].
|}

[[Category: Site Info]]

File:Pgc-cache-icon-notrun.png

2024-05-07T19:16:24Z

4523550: Mystery/Unknown cache icon, marked for "challenge checker not ran". ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
Mystery/Unknown cache icon, marked for "challenge checker not ran".

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

LogCompare

2024-04-30T20:08:36Z

4523550: Added info about the image.

[[File:LogCompare.png|500px|thumb|right|Example of result from Log Compare-tool with identical logs being hidden. Names of compared cachers have been censored.]][https://project-gc.com/Tools/LogCompare Log Compare] is a tool for users with a [[paid membership]], the function of the tool is to double check that all members of a group that cached together have remembered to log all the caches found during the outing.

The tool uses the filters [[Filters#Profile name|Profile name]] with the "Compare with"-box and [[filters#From / To Log Date|Logdate]].

The result of running the tool is a list of caches logged in the period. The caches are presented with a country flag, the icon for the cache type, GCcode that links to the cache page and the name of the cache. For each user that is being compared an icon is displayed that shows the status of the cache. A found is marked with a yellow smiley, a previous found is marked with a grayed out smiley, a DNF is marked with a blue frown, a note is marked with the pencil-and-paper-icon. Owned caches are marked with a star.

Under the list of caches for each day there is a summary of the stats that lists number of finds, number of logs, number of owned caches and number of former finds.

Each date has a button labeled "Hide identical" that can be used to hide all caches from the list that have identical logs for all the participants being compared.

[[Category: Tools]]

LogCompare

2024-04-30T20:06:35Z

4523550: Added image.

[[File:LogCompare.png|500px|thumb|right|Example of result from Log Compare-tool with identical logs being hidden.]][https://project-gc.com/Tools/LogCompare Log Compare] is a tool for users with a [[paid membership]], the function of the tool is to double check that all members of a group that cached together have remembered to log all the caches found during the outing.

The tool uses the filters [[Filters#Profile name|Profile name]] with the "Compare with"-box and [[filters#From / To Log Date|Logdate]].

The result of running the tool is a list of caches logged in the period. The caches are presented with a country flag, the icon for the cache type, GCcode that links to the cache page and the name of the cache. For each user that is being compared an icon is displayed that shows the status of the cache. A found is marked with a yellow smiley, a previous found is marked with a grayed out smiley, a DNF is marked with a blue frown, a note is marked with the pencil-and-paper-icon. Owned caches are marked with a star.

Under the list of caches for each day there is a summary of the stats that lists number of finds, number of logs, number of owned caches and number of former finds.

Each date has a button labeled "Hide identical" that can be used to hide all caches from the list that have identical logs for all the participants being compared.

[[Category: Tools]]

File:LogCompare.png

2024-04-30T20:02:54Z

4523550: Image of an example of the LogCompare-tool. ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
Image of an example of the [[LogCompare]]-tool.

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

NewCacheNotifiers

2024-04-27T21:01:58Z

4523550: Added advantages/disadvantages-list + expanded the description. Added headers for sections that need to be added.

{{FIXME|reason=Explain the tool, list pros and cons, explain how to set up notifications etc}}

==Description==
[https://project-gc.com/User/NewCacheNotifiers New cache notifiers] is a tool available for users with a [[paid membership]]. It also requires that the user is a [[premium member]] at [[Geocaching.com]] This is an alternative to the Geocaching.com ''Instant Notification Service''.<ref>Available for premium members at [https://www.geocaching.com/notify/default.aspx https://www.geocaching.com/notify/default.aspx]</ref> The page shows some information about the notifiers, below that is information about the current email configured for the user, their current notifiers and a graf of how close they are to the limit of the notifiers.

When adding or removing notifiers it might take a few minutes for the system to recognize the changes.

==Advantages==
* A smoother interface.
* No distance limit.
* Filter on location such as country, region, county.
* Filter on other meta data such as difficulty, terrain, type and size.
* Get notified about every log up until the first Found it or equivalent. Additional notifications regarding logs might be very delayed. (Optional)
* A better formatted email with more information about the cache included in the email.
* Option (default) to get a daily digest instead of instant notifications.
* Can be based on dynamic locations provided by your smartphone.

==Disadvantages==
* Likely to be less stable than the official notifiers at [[Geocaching.com]].
* In most cases at least a minute slower than the official notifiers.
* Max 100 new cache notifications per day and max 500 per month. The limit is a rolling rate limit and not based on calendar months.

==How to set up==
''Information to be added.''

===Dynamic location===
''Information to be added.''

==Notes==
<references/>

Polygon definitions

2024-04-27T13:01:08Z

4523550: /* Historical data */ Description of new function.

== Page description ==
This is an admin/moderator page to which only specific users have access. The page is used to create rules used when importing polygon data from OpenStreetMap into [[Project-GC]]. More precisely, Project-GC imports from [[OSM-Boundaries.com]], which in turn has imported its data from OpenStreetMap. The data is then used for calculations regarding placing [[geocache]]s in their correct region/county. The data is also used for rendering maps, as for example the maps in [[Profile stats]].

== Country selector ==
The country selector lists every country available in the [[Geocaching LIVE api]]. By selecting a new entry the country is automatically loaded, allow it 1-2 seconds to retrieve its data.

== Data shown ==
In the first section there is basic metadata about the country shown, like the name of the country, and the ID in the [[Geocaching LIVE api|API]]. Then it shows who has created the last definitions of rules and when. On the right side there is a list of region names used by [[Geocaching.com]].

The region names in Project-GC '''must''' match those of [[Geocaching.com]]. Use relevant rule options to make this happen.

== Source site ==
[[Project-GC]] uses [[OSM-Boundaries.com]] as a source when importing its polygon data. This site is also a great source to use when building the import rules. [[OSM-Boundaries.com]] in turn has imported its data from data dumps of OpenStreetMap.

== Rules ==
For Project-GC to know where a country (or region/county) exists in the world it needs the borders. In the most simple cases we can just match a country with an ID in the [[OpenStreetMap]] database and it's done. However it's not always that simple, especially for countries. For example the polygon for Finland includes Aland Islands while Aland Islands is its own country according to [[Geocaching.com]]. In this case we need to make more advanced rules defining and calculating new polygons in [[Project-GC]].

The rule-set for countries differs a bit from regions/counties, the reason is that a country should always end with a single (multi)polygon, while regions and counties needs one (multi)polygon per region/county.

All import rules are created as JSON-strings. Generally it consists of a list of rules for the polygons itself, and the a list of rules for post-processing names. When the import tool runs it will first run all rules under ''polygons'', and then the rules under ''postprocessing''. Each rule within these two is executed in the order it's listed as.

You can look at already defined definitions to get an overall understanding how the definitions should look.

=== Base OSMB Database ===
This is the OSM-Boundaries database version that will be used as a basis for this country's polygon import. It can then be overridden for specific rules later on. It's not always using the latest since all data must be reviewed, it's not uncommon that OpenStreetMap has brooken or incompatible data. A typical use-case for overriding is when Openstreetmap has broken data.

=== Country rules ===
All countries '''must''' be defined in [[Project-GC]]. This is primarily used when rendering maps for [[Profile stats]], and the maps would look a bit funny if a country was missing.

The country rules are the simplest. There is no post-processing of names and there are only two types of rules available.
* '''includeOsmIds''' - List of integer IDs from [[OSM-Boundaries.com]]. These are IDs of polygons that will be included in the country.
* '''subtractOsmIds''' - List of integer IDs from [[OSM-Boundaries.com]]. The IDs listed here will be subtracted from the includeOsmIds. For example in the case of Finland, the ID of Finland can be chosen as the country and then Aland Island can be subtracted.

Each rule can also use the '''db''' attribute to specify another database than the ''base'' one.

Rather use one big polygon as include and a few subtract than a lot of includes. For example, USA either requires including the whole USA and then subtracting 3-5 polygons, or making a list of ~50 polygons for inclusion. There are two good reasons to rather include the whole country and then make a few subtracts.
* It's faster during the import phase.
* It makes a more readable definition.

The country polygons ignores the names in [[OpenStreetMap]], names from the [[Geocaching LIVE api|API]] will be used instead. This is also why the post-processing rule-set hasn't been implemented.

Example of how to define Norway:
{ "polygons": [ "includeOsmIds":[-2978650],"subtractOsmIds":[-2425963,-1337126,-1337397] ] }

=== Region rules ===
The best way to add rules is by using the ''Add rule'' button on the right side of the input form. This will help you keeping the syntax correct. All values that are defined as either 0 (zero) or empty strings ("") are required to fill in. Keys that has empty lists as values are optional.

There are several types of rules that can be used to import polygons, and they should be listed under the key ''polygons''. The rules are used by setting type to the ID of the rule, and then defining at least the required keys.
* '''adminLevel''' - This is the easiest and most common way to. In a perfect world this would be the only rule needed. Basically it includes everything with a specified ''adminLevel'' under a ''parentOsmId''.
** Required keys
*** '''parentOsmId'''
*** '''adminLevel'''
** Optional keys
*** '''excludeOsmIds''' - Exclude specific ''osmIds'' even though they match the ''parentOsmId'' and the ''adminLevel''.
*** '''excludeParentOsmIds''' - Exclude anything that has these ''osmIds'' as a parent in OSM-Boundaries tree-view.
*** '''subtractOsmIds''' - Subtract polygons listed here. This is a lot slower than ''excludeParentOsmIds'' and should only be used when we actually need to punch a whole into something.
*** '''allowNonAdministrative''' - By default the system requires that OSM's tag ''boundary'' is set to ''administrative''. If this is not wished for, set this to true (do not quote it).
*** '''db''' - Override the base database.
* '''immediateChildrenOf''' - Add all immediate children of this osmb-id, regardless of the admin-level.
** Required keys
*** '''parentOsmId''' - OSM ID from [[OSM-boundaries.com]].
** Optional keys
*** '''boundary''' - Require the OSM tag boundary to be set to this string value, for example ''administrative''.
*** '''db''' - Override the base OSMB database.
*** '''excludeOsmIds''' - Exclude these IDs. A list with IDs as shown on [[OSM-Boundaries.com]].
* '''osmIds''' - This rule allows adding a list of OSM-IDs as regions.
** Required keys
*** '''osmIds''' - List of osmIds
** Optional keys
*** '''subtractOsmIds''' - Subtract polygons from the ones that are being imported. If possible, try to split the rule into two rules, where only those needing the subtract are listed together with the subtract. And those not needing subtraction for themself. This will increase the import performance a lot.
*** '''fillHoles''' - Boolean, if true all holes inside the polygon will be filled as if there were no holes. If it was used on Sweden there would be no Vättern och Vänern for example.
*** '''db''' - Override the base database.
* '''union''' - If there aren't polygons available that works, but there are other polygons which could be joined together to create what's needed this rule-type can be used.** ** Required keys
*** '''osmIds''' - List of osmIds
** Optional keys
*** '''subtractOsmIds'''
*** '''fillHoles''' - Boolean, if true all holes inside the polygon will be filled as if there were no holes. If it was used on Sweden there would be no Vättern och Vänern for example.
*** '''db''' - Override the base database.
* '''file''' - This is a a special case option that shouldn't be used in general. But for Canada it has been used. Basically it uses stored geojson files instead of [[OSM-Boundaries.com]] as a source. Canada actually is a mix of Openstreetmap and Census data.
** Required keys
*** '''filename'''
*** '''propertyKey'''
** Optional keys
*** '''propertyValue'''
*** '''name'''
*** '''fillHoles''' - Boolean, if true all holes inside the polygon will be filled as if there were no holes. If it was used on Sweden there would be no Vättern och Vänern for example.

Then there are a number of rules for post-processing names as well. Since they are executed in the order they are listed the order might be important.
* '''renameOsmId'''
** Required keys
*** '''osmId'''
*** '''name'''
* '''removePrefixes'''
** Required keys
*** '''prefixes''' - List of strings.
* '''removeSuffixes'''
** Required keys
*** '''suffixes''' - List of strings.
* '''prefixToSuffix'''
** Required keys
*** '''prefix'''
*** '''suffix''' - Don't forget to start with a space character if wished for.
* '''suffixBasedOnRegionName'''
** Required keys
*** '''regionName'''
*** '''suffix'''
* '''removeMultiByteAbove''' - Will remove all characters in the string that has an utf8 value higher than ''maxValue''. Be aware that there might be some left-overs like dash after this rule has been run. Running a ''removeSuffix'' afterwards can help with that.
** Required keys
*** '''maxValue'''
* '''convertCase''' - Convert the casing using PHPs mb_convert_case() function, using the mode specified in the require mode option.
** Required keys
*** '''mode''' - Valid modes are: MB_CASE_UPPER, MB_CASE_LOWER, MB_CASE_TITLE, MB_CASE_FOLD, MB_CASE_UPPER_SIMPLE, MB_CASE_LOWER_SIMPLE, MB_CASE_TITLE_SIMPLE, MB_CASE_FOLD_SIMPLE.

Each rule can be repeated as many times as needed. Every rule can also include the optional key '''comment'''. It can be used to document why that specific rule exists, or why a specific osmId is subtracted for example.

Finally there is an option that can be set on the same level as ''polygons'' and ''postprocessing''
* '''internationalNames''' - The import scripts defaults to using local region and county names. But we also want to avoid using names that are impossible to write for users who are most familiar with the latin alphabet. So for example when the names are in Asian or Arabic variants we can use this parameter to override the default. But again, in cases where [[Geocaching.com]] has regions, it's most important that we match those. It's a boolean option, which defaults to false. Example:
{ "internationalNames": true }

When regions exists at [[Geocaching.com]] the region names in [[Project-GC]] must match these when possible. If they don't, it should clearly be stated in the #Notes -field, and why.

Note that '''subtractOsmIds''' is an expensive operation. When reasonable (not too much work), try to only use ''subtractOsmIds'' together with those ''osmIds'' that actually requires it. Example:
{ "type": "osmIds", "osmIds": [1,2,3,4,5,6,7,8,9], "subtractOsmIds": [1000] }
might be a lot faster as:
{ "type": "osmIds", "osmIds": [1,2,3,4,5,6,7,8] }
{ "type": "osmIds", "osmIds": [9], "subtractOsmIds": [1000] }
This of course requires that osmId 9 is the only polygon that needs to subtract. Similar solution could be used with adminLevel by using ''excludeOsmIds'' if there is only a handful of polygons needing a subtract. That handful number of polygons can then be added with an ''osmIds''-rule instead. Example:
{ "type": "adminLevel", "parentOsmId": 123, "adminLevel": 4, "subtractOsmIds": [1000] }
might be faster with this method:
{ "type": "adminLevel", "parentOsmId": 123, "adminLevel": 4, "excludeOsmIds": [100, 200] }
{ "type": "osmIds", "osmIds": [100, 200], "subtractOsmIds": [1000] }

Full example:
{
"internationalNames": true,
"polygons": [
{ "type": "osmIds", "osmIds": [123], "subtractOsmIds": [] },
{ "type": "osmIds", "osmIds": [456], "subtractOsmIds": [] },
{ "type": "adminLevel", "parentOsmId": 123, "adminLevel": 4, "excludeOsmIds": [], "subtractOsmIds": [] },
{ "type": "adminLevel", "parentOsmId": 123, "adminLevel": 6, "excludeOsmIds": [], "subtractOsmIds": [] },
{ "type": "union", "name": "Malmö", "osmIds": [123, 456], "subtractOsmIds": [] },
{ "type": "union", "name": "Lund", "osmIds": [321, 654], "subtractOsmIds": [] }
],
"postprocessing": [
{ "type": "renameOsmId", "osmId": -54409, "name": "Scania" },
{ "type": "removePrefixes", "prefixes": ["foo"] },
{ "type": "removeSuffixes", "suffixes": ["bar"] },
{ "type": "prefixToSuffix", "prefix": "Landkreis", "suffix": " (Lkr)" },
{ "type": "suffixBasedOnRegionName", "regionName": "California", "suffix": " (Ca)" }
]
}

=== County rules ===
The county rules works exactly like the region rules.

=== Notes ===
This is a free-text form where you have the option to leave some notes. If there is nothing to say, just leave it empty. But for example when making a subtract it can be worth mentioning what's being subtracted.

=== Saving errors ===
There isn't much feedback to the web-ui yet. If the input form turns red the JSON is invalid, and therefore couldn't be saved. Upon save the JSON is also verified in several ways. For example it looks for keys that shouldn't exist (where they exist), and that the values are of the correct type (list, integers, strings, ...).

=== Preview data ===
There is not yet any way to preview the data. Depending on how complex the definitions are it takes hours to calculate new polygons which makes it troublesome to show the moderator some form of preview. Ultimately we should also calculate the number of [[geocache]]s included in the polygons, both with old and new definitions - This would be even more expensive.

== Historical data ==
Historical definitions exists in the database and can be fetched with the restore-tool at the bottom of each page. Selecting an old definition in the drop down loads the old definition in the tool, to use the old definition it needs to be saved.

==Notes==
<references/>

[[Category:Moderation]]

Challenge difficulty

2024-04-26T21:40:19Z

4523550: Added info about the module in profile stats. Also changed every->most (as not all checkers have a difficulty).

==What is it?==
For most [[Challenge checker]]s 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 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. With this in mind we know that the result isn't representing the average geocacher, on the other hand, challenges generally aren't targeting the average geocacher either.

The [[Challenge checker]] results are dividing 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 fulfill 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 fourth 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 calculated [[challenge checker]] results 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 fulfill it.
* 40% of the [[Geocacher]]s in the other states of the United States fulfill it.
* 30% of the [[Geocacher]]s in the rest of the world fulfill it.
* The challenge is one year old (365 days) and have had 10 finds during this period.
* Then to weigh these differently using coefficients a sum is created like this: 3*80+5*40+10*30+((1-(10/365))*100).
* This sum is then divided by 19 (3+5+10+1, the last being related to findsPerDay).
* The ''Challenge difficulty'' ends up being 837.26/19 = 44.066, which is rounded down to 44. The values are always rounded down to the closest integer.

==Related statistics==
[[Challenge difficulty per rating interval]] shows the correlation between the [[D/T|difficulty rating]] of the geocache and the challenge difficulty.

The [[Challenges_tab#Challenge_difficulties|challenge tab]] in the profile stats has a module for challenge difficulties.

[[Category:Site Info]]

Challenges tab

2024-04-26T21:38:37Z

4523550: Added image.

The '''Challenges tab''' is a tab in a users [[Profile Stats]] and it is only available for users with a [[paid membership]], this tab shows the [[challenge cache]]s that a user has logged and consists of four modules.

== Challenges logged ==
This module is a list of all challenges the user has logged. The list shows the date the challenge was logged as found, the country, the [[D/T | D/T-rating]], the [[challenge difficulty]], the name and GCcode. If the user has found more than 30 challenges only the first 10 and the last 10 are shown with a link for showing the additional challenges in the middle of the list. Below is a link to the [[signed challenges tool]].

== Challenges by found date ==
This module is a calendar (also called [[366 grid]]), logging a challenge for each calendar date will award the user with the [[366 addon]] for their [[The Achiever| The Achiever badge]].

== Challenges D/T ==
This module is a [[D/T grid]] showing all 81 combinations of Difficulty and Terrain ratings, with the number of challenge caches found for each combination.

Below the grid is a summary of the number of the combinations, with a value and percentage of those with a difficulty or terrain rating of 3 or more.

== Challenge difficulties ==
[[File:ChallengeDifficultyGrid.png|500px|thumb|right|A Challenge difficulties grid.]]This module is a table showing the 101 possible [[Challenge difficulty|challenge difficulties]] and the number of challenges the user has logged for each challenge difficulty. The table should be read as the y-axis having the tens and the x-axis having the singular digit, for example the box where the row marked 40-49 and the column marked +7 meet would be challenge difficulty 47.
{{Clear}}

== Related Tools ==
*Use the [https://project-gc.com/Tools/Challenges?map Map of challenge caches] to find challenge caches in your area to fill the challenge-[[D/T grid]] or work on the [[366 addon]] for your [[The Achiever| The Achiever badge]].
*Use the [[Signed challenges tool]] to list all noted challenges which aren't logged, locked or owned<ref>News released [https://web.archive.org/web/20240420175028/https://project-gc.com/Home/News 2024-04-08] (archived at webarchive) informed that this module was moved out of the challenge tab.].</ref>.

== Notes ==
<references/>

[[Category:Statistics]] [[Category: Profile Stats]]

File:ChallengeDifficultyGrid.png

2024-04-26T21:35:11Z

4523550: An image of the challenge difficulty grid in the challenge tab of the Profile Stats. ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
An image of the challenge difficulty grid in the [[Challenges_tab#Challenge_difficulties|challenge tab]] of the [[Profile Stats]].

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

Template:Badge

2024-04-26T21:01:37Z

4523550: Added category

<includeOnly>
[[Category:BadgeGen]]
</includeOnly>
{| class="wikitable" style="float:right;"
|+ {{{BadgeName}}}
! colspan="2"|General data
|-
|Name||{{{BadgeName}}}
{{#IF:{{{MaxLoops|}}}|
{{!}}-
{{!}}Max loops{{!}}{{!}}{{{MaxLoops}}}}}
|-
! colspan="2"|Requirements
|-
|Bronze||{{{BronzeRequirement}}}
|-
|Silver||{{{SilverRequirement}}}
|-
|Gold||{{{GoldRequirement}}}
|-
|Platinum||{{{PlatinumRequirement}}}
|-
|Ruby||{{{RubyRequirement}}}
|-
|Sapphire||{{{SapphireRequirement}}}
|-
|Emerald||{{{EmeraldRequirement}}}
|-
|Diamond||{{{DiamondRequirement}}}
|-
{{#IF:{{{AddonsAvailable|}}}|
! colspan="2"{{!}}Addons available
{{!}}-
{{!}} colspan="2"{{!}}{{{AddonsAvailable}}}}}
|}

<h2> {{{BadgeName}}} </h2>

<noinclude>
TEMPLATE NOTES
* For variable AddonsAvailable, add a <br> after the four first (D/T, 366, Leapday, FTF), so that the others ends up on a new row.
* Suggested headers, besides Badge-name: Loop, Addons, Related tools, History
[[Category: Geocaching Templates]]
</noinclude>

Template:Badge image

2024-04-26T21:01:22Z

4523550: Added category

https://project-gc.com/dimages/badgegen-v4-badge.php?icon={{{icon|}}}&quality={{{q|D}}}&addons={{{addons|}}}&loop={{{loop|}}}&.png<noinclude>

Usage:<code><nowiki>{{Badge image|icon=badge icon|q=quality|addons=list|loop=number}}</nowiki></code>

This template creates an image of a given badge. Parameters are as follows:

*icon - the name of the badge as defined in the image url - e.g. TheTraditionalCacher. Default is blank.
*q - the quality, i.e. level, of the badge. Can be B, S, G, P, R, Sa, E or D for Bronze, Silver, etc. Default is D for Diamond.
*addons - any addons required, separated by commas (no spaces). Default is blank.
*loop - loop number. Default is blank.
[[Category: Geocaching Templates]]</noinclude>

Template:Banner

2024-04-26T21:00:49Z

4523550: Added category

<div style="background:{{{bg|#EBE7E4}}}; border-radius:9px; border:solid 3px #00008b; box-shadow:5px 5px 5px rgba(68,68,68,0.6); color:{{{fg|#00008b}}}; margin-bottom:10px; padding:8px; text-align:center">
<p style="text-align:center"><span style="font-family:Trebuchet MS,Helvetica,sans-serif">{{{text|Text goes here}}}</span></p></div><noinclude>

Produces a banner.

==Usage==

<nowiki>{{Banner | text = </nowiki>''text you want to appear.'' | bg = ''Background colour in RGB hex (optional)'' | fg = ''Font colour in RGB hex (optional)''<nowiki>}}</nowiki>

[[Category: Wiki Templates]]</noinclude>

Template:Clear

2024-04-26T21:00:30Z

4523550: Added category

<div style="clear:{{{1|both}}};"></div><noinclude>
== Description ==
It makes content wait until existing content is completed in all columns. It is often used to prevent text from flowing next to unrelated images.

== Usage ==
* <nowiki>{{clear}}</nowiki> — adds <code><div style="clear:both;"></div></code>
* <nowiki>{{clear|left}}</nowiki> — adds <code><div style="clear:left;"></div></code>
* <nowiki>{{clear|right}}</nowiki> — adds <code><div style="clear:right;"></div></code>

[[Category: Wiki Templates]]</noinclude>

Template:FIXME

2024-04-26T20:59:59Z

4523550: Added category

<noinclude>
== Usage ==
Use this template to tag articles which are far from complete, for example when there are only key words added, or the formatting isn't finished.
== Example outputs ==
* <nowiki>{{FIXME}}</nowiki>
** {{FIXME}}
* <nowiki>{{FIXME|reason=Example}}</nowiki>
** {{FIXME|reason=Example}}
</noinclude>

<includeonly>
<div style="margin-top: 0px; border:1px solid black; background-color: #ffa000; padding: 10px; margin-bottom: 20px;">
<p style="font-size:150%;">This page is a '''Work in progress''' and needs severe fixes.</p>
<p>Feel free to contribute by editing the page. When it has the information needed in a readable form and in a decent formatted way, remove the FIXME template-tag.</p>
{{#IF:{{{reason|}}}|<p>'''Reason:''' {{{reason|}}}</p>}}
</div>
{{#IFEQ: {{FULLPAGENAME}} | Template:FIXME || [[Category:FIXME]] }}
</includeonly>

<noinclude>[[Category: Wiki Templates]]</noinclude>

Template:From Wikipedia

2024-04-26T20:59:10Z

4523550: Added category

<includeonly>This template is copied from Wikipedia{{#IF:{{{1|}}}| on {{#time:r|{{{1}}}}}}}. [https://en.wikipedia.org/w/index.php?title={{urlencode:{{SUBJECTPAGENAME}}|WIKI}}{{#IF:{{{1|}}}|&offset={{#time:YmdHis|{{{1}}}}}}}&action=history Revision history]</includeonly><Noinclude>

==Usage==
<code><nowiki>{{From Wikipedia|</nowiki>''Optional time stamp''<nowiki>}}</nowiki></code>

This template should be added to the talk page of any template copied from Wikipedia to provide attribution, as required by the cc-by-sa licence.
[[Category: Wiki Templates]]
</Noinclude>

Template:GPBA entry

2024-04-26T20:58:29Z

4523550: Added category

Template:GPBA header

2024-04-26T20:58:19Z

4523550: Added category

{| class="wikitable sortable"
|+ Number of Geocachers per Badge/Addon
|-
! Badge
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">81matrix
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">lostfound
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">366cal
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">leapday
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">ftf
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">giga
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">boat
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">oldvirtual
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">cito
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">fieldpuzzle
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">partner
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">mega
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">climb
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">geotour
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">communitycelebration
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">ape
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">HQ
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">HQcelebration
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">blockparty
! class="nowrap" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl; writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic; display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg); -ms-transform: none; padding-left:1px; text-align:center">locationless

<noinclude>[[Category: Wiki Templates]]</noinclude>

Template:GPBQ entry

2024-04-26T20:58:08Z

4523550: Added category

|-
| {{{1}}}
| style="text-align:right;" | {{{2}}}<br><span style="color:gray;">{{{3}}}</span>
| style="text-align:right;" | {{{4}}}<br><span style="color:gray;">{{{5}}}</span>
| style="text-align:right;" | {{{6}}}<br><span style="color:gray;">{{{7}}}</span>
| style="text-align:right;" | {{{8}}}<br><span style="color:gray;">{{{9}}}</span>
| style="text-align:right;" | {{{10}}}<br><span style="color:gray;">{{{11}}}</span>
| style="text-align:right;" | {{{12}}}<br><span style="color:gray;">{{{13}}}</span>
| style="text-align:right;" | {{{14}}}<br><span style="color:gray;">{{{15}}}</span>
| style="text-align:right;" | {{{16}}}<br><span style="color:gray;">{{{17}}}</span>
| style="text-align:right;" | {{{18}}}<br><span style="color:gray;">{{{19}}}</span>
{{#SWITCH:{{{1}}}
|[[The Author]]
|[[The Diverse Cacher]]
|[[The High Altitude Cacher]]
|[[The Long-Distance Cacher]]
|[[The Low Altitude Cacher]]
|[[The Trackable Lover]] =
{{!}} style="text-align:right; border-left: 3px solid black;" {{!}} -
{{!}} style="text-align:right;" {{!}} -
{{!}} style="text-align:right;" {{!}} -
{{!}} style="text-align:right;" {{!}} -
|#default=
{{!}} style="text-align:right; border-left: 3px solid black;" {{!}} {{{20}}}<br><span style="color:gray;">{{{21}}}</span>
{{!}} style="text-align:right;" {{!}} {{{22}}}<br><span style="color:gray;">{{{23}}}</span>
{{!}} style="text-align:right;" {{!}} {{{24}}}<br><span style="color:gray;">{{{25}}}</span>
{{!}} style="text-align:right;" {{!}} {{{26}}}<br><span style="color:gray;"> </span>
}}

<noinclude>[[Category: Wiki Templates]]</noinclude>

Template:GPBQ header

2024-04-26T20:57:56Z

4523550: Added category

{| class="wikitable sortable"
|+ Number of Geocachers per Badge/Quality
|-
! Badge
! -
! Bronze
! Silver
! Gold
! Platinum
! Ruby
! Sapphire
! Emerald
! Diamond
! style="border-left: 3px solid black;" | D2
! D5
! D9
! Max loop reached

<noinclude>[[Category: Wiki Templates]]</noinclude>

Template:PGC-US-Name

2024-04-26T20:57:01Z

4523550: Added category

Project-GC Userscript

<noinclude>[[Category: Wiki Templates]]</noinclude>

Template:PGC-back-link

2024-04-26T20:55:41Z

4523550: Added category

<table style="width:100%;">
<tr>
<td style="width:70%; vertical-align:top;">{{{content}}}</td>
<td style="background-color: #ccc; border: 1px; text-align:center;>{{#if:{{{link|}}}|[[{{{link}}}|{{{link}}}]]|[[UserScript|<b>RETURN</b> to {{PGC-US-Name}} Main Page]]}}
</td>
</tr>
</table>
<br/>

<noinclude>[[Category: Wiki Templates]]</noinclude>

Template:PGC Screenshot

2024-04-26T20:54:16Z

4523550: Added category

This image is a screenshot of {{{1|a [[Project-GC]] page}}}.

Copyright © 2014-2024 Ground Zero Communications AB. All Rights Reserved.<includeonly>[[Category:PGC Screenshots]]</includeonly>

<noinclude>
This template is recommended to include on all screenshots of Project-GC.

[[Category: Wiki Templates]]</noinclude>

Template:Jasmer

2024-04-26T20:52:23Z

4523550: Added category

{{#expr: 216 + trunc ((12 * {{#time: y}} + {{#time: m}} - 221) * {{{1|100}}} / 100)}}<noinclude>

<code><nowiki>{{</nowiki>Jasmer|xx<nowiki>}}</nowiki></code> calculates the number of months currently required to gain a specific gemstone for the [[The Jasmer Cacher]] badge. xx should be set to one of the percentages required to get that badge - e.g. 70 for ruby.
[[Category: Geocaching Templates]]</noinclude>

Template:ScaleFile

2024-04-26T20:50:47Z

4523550: Formatting error

<div style="transform: scale({{{1|50}}}%)">{{{2|}}}{{{3|}}}{{{4|}}}{{{5|}}}{{{6|}}}{{{7|}}}{{{8|}}}{{{9|}}}{{{10|}}}{{{11|}}}</div><noinclude>

<code><nowiki>{{</nowiki>ScaleFile|''Scale percentage''|''External file 1''|''External file 2''|''External file 3''...<nowiki>}}</nowiki></code> displays external images (such as those used for [[BadgeGen]]) at a given percentage of their original size. Up to 10 images are supported, which are shown adjacent to each other in a single line. This is necessary as the usual wiki markup <nowiki>[[File:</nowiki>''filename''|''size''<nowiki>]]</nowiki> cannot be used for external images. The default scale is 50%. Do not add % to the scale size.
[[Category: Wiki Templates]]</noinclude>

Category:Wiki Templates

2024-04-26T20:46:45Z

4523550: Initial edit of category-page.

Templates related to more general formatting and styling of wiki, such as banners and image-styling.

Template:ScaleFile

2024-04-26T20:45:44Z

4523550: Added category

Template:Jasmer

2024-04-26T20:45:17Z

4523550: Added category

Category:Geocaching Templates

2024-04-26T20:44:52Z

4523550: Initial edit of category-page.

Templates for things only relevant for geocachers, such as related to the [[D/T grid]].

Template:DT

2024-04-26T20:43:13Z

4523550: Added category

{| class="wikitable" style="text-align: center"
|-
!scope="col" colspan=2 rowspan=2 style="background: yellow" | D/T
!colspan=9 style="background: yellow" |Terrain
!rowspan=2 style="width: 40px;background: yellow" |<div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl;writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic;display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg);;-ms-transform: none ;padding-left:1px;text-align:center">Total</div>
|-
|scope="col" style="width: 40px;background: yellow"|'''1'''
|scope="col" style="width: 40px;background: yellow"|'''1.5'''
|style="width: 40px;background: yellow"|'''2'''
|style="width: 40px;background: yellow"|'''2.5'''
|style="width: 40px;background: yellow"|'''3'''
|style="width: 40px;background: yellow"|'''3.5'''
|style="width: 40px;background: yellow"|'''4'''
|style="width: 40px;background: yellow"|'''4.5'''
|style="width: 40px;background: yellow"|'''5'''
|-
! rowspan=9 class = "nowrap" style="width: 20px;background: yellow" | <div style="-webkit-writing-mode: vertical-rl; -o-writing-mode: vertical-rl; -ms-writing-mode: tb-rl;writing-mode: tb-rl; writing-mode: vertical-rl; layout-flow: vertical-ideographic;display: inline-block; -ms-transform: rotate(180deg); -webkit-transform: rotate(180deg); transform: rotate(180deg);;-ms-transform: none ;padding-left:1px;text-align:center">Difficulty</div>
|style="width: 40px;background: yellow" |'''1'''||{{{1|-}}}||{{{2|-}}}||{{{3|-}}}||{{{4|-}}}||{{{5|-}}}||{{{6|-}}}||{{{7|-}}}||{{{8|-}}}||{{{9|-}}}||'''{{#expr:{{{1|0}}}+{{{2|0}}}+{{{3|0}}}+{{{4|0}}}+{{{5|0}}}+{{{6|0}}}+{{{7|0}}}+{{{8|0}}}+{{{9|0}}}}}'''
|-
|style="background: yellow"|'''1.5'''||{{{10|-}}}||{{{11|-}}}||{{{12|-}}}||{{{13|-}}}||{{{14|-}}}||{{{15|-}}}||{{{16|-}}}||{{{17|-}}}||{{{18|-}}}||'''{{#expr:{{{10|0}}}+{{{11|0}}}+{{{12|0}}}+{{{13|0}}}+{{{14|0}}}+{{{15|0}}}+{{{16|0}}}+{{{17|0}}}+{{{18|0}}}}}'''
|-
|style="background: yellow"|'''2'''||{{{19|-}}}||{{{20|-}}}||{{{21|-}}}||{{{22|-}}}||{{{23|-}}}||{{{24|-}}}||{{{25|-}}}||{{{26|-}}}||{{{27|-}}}||'''{{#expr:{{{19|0}}}+{{{20|0}}}+{{{21|0}}}+{{{22|0}}}+{{{23|0}}}+{{{24|0}}}+{{{25|0}}}+{{{26|0}}}+{{{27|0}}}}}'''
|-
|style="background: yellow"|'''2.5'''||{{{28|-}}}||{{{29|-}}}||{{{30|-}}}||{{{31|-}}}||{{{32|-}}}||{{{33|-}}}||{{{34|-}}}||{{{35|-}}}||{{{36|-}}}||'''{{#expr:{{{28|0}}}+{{{29|0}}}+{{{30|0}}}+{{{31|0}}}+{{{32|0}}}+{{{33|0}}}+{{{34|0}}}+{{{35|0}}}+{{{36|0}}}}}'''
|-
|style="background: yellow"|'''3'''||{{{37|-}}}||{{{38|-}}}||{{{39|-}}}||{{{40|-}}}||{{{41|-}}}||{{{42|-}}}||{{{43|-}}}||{{{44|-}}}||{{{45|-}}}||'''{{#expr:{{{37|0}}}+{{{38|0}}}+{{{39|0}}}+{{{40|0}}}+{{{41|0}}}+{{{42|0}}}+{{{43|0}}}+{{{44|0}}}+{{{45|0}}}}}'''
|-
|style="background: yellow"|'''3.5'''||{{{46|-}}}||{{{47|-}}}||{{{48|-}}}||{{{49|-}}}||{{{50|-}}}||{{{51|-}}}||{{{52|-}}}||{{{53|-}}}||{{{54|-}}}||'''{{#expr:{{{46|0}}}+{{{47|0}}}+{{{48|0}}}+{{{49|0}}}+{{{50|0}}}+{{{51|0}}}+{{{52|0}}}+{{{53|0}}}+{{{54|0}}}}}'''
|-
|style="background: yellow"|'''4'''||{{{55|-}}}||{{{56|-}}}||{{{57|-}}}||{{{58|-}}}||{{{59|-}}}||{{{60|-}}}||{{{61|-}}}||{{{62|-}}}||{{{63|-}}}||'''{{#expr:{{{55|0}}}+{{{56|0}}}+{{{57|0}}}+{{{58|0}}}+{{{59|0}}}+{{{60|0}}}+{{{61|0}}}+{{{62|0}}}+{{{63|0}}}}}'''
|-
|style="background: yellow"|'''4.5'''||{{{64|-}}}||{{{65|-}}}||{{{66|-}}}||{{{67|-}}}||{{{68|-}}}||{{{69|-}}}||{{{70|-}}}||{{{71|-}}}||{{{72|-}}}||'''{{#expr:{{{64|0}}}+{{{65|0}}}+{{{66|0}}}+{{{67|0}}}+{{{68|0}}}+{{{69|0}}}+{{{70|0}}}+{{{71|0}}}+{{{72|0}}}}}'''
|-
|style="background: yellow"|'''5'''||{{{73|-}}}||{{{74|-}}}||{{{75|-}}}||{{{76|-}}}||{{{77|-}}}||{{{78|-}}}||{{{79|-}}}||{{{80|-}}}||{{{81|-}}}||'''{{#expr:{{{73|0}}}+{{{74|0}}}+{{{75|0}}}+{{{76|0}}}+{{{77|0}}}+{{{78|0}}}+{{{79|0}}}+{{{80|0}}}+{{{81|0}}}}}'''
|-
|colspan=2 style="background: yellow"|'''Total'''
|'''{{#expr:{{{1|0}}}+{{{10|0}}}+{{{19|0}}}+{{{28|0}}}+{{{37|0}}}+{{{46|0}}}+{{{55|0}}}+{{{64|0}}}+{{{73|0}}}}}'''
|'''{{#expr:{{{2|0}}}+{{{11|0}}}+{{{20|0}}}+{{{29|0}}}+{{{38|0}}}+{{{47|0}}}+{{{56|0}}}+{{{65|0}}}+{{{74|0}}}}}'''
|'''{{#expr:{{{3|0}}}+{{{12|0}}}+{{{21|0}}}+{{{30|0}}}+{{{39|0}}}+{{{48|0}}}+{{{57|0}}}+{{{66|0}}}+{{{75|0}}}}}'''
|'''{{#expr:{{{4|0}}}+{{{13|0}}}+{{{22|0}}}+{{{31|0}}}+{{{40|0}}}+{{{49|0}}}+{{{58|0}}}+{{{67|0}}}+{{{76|0}}}}}'''
|'''{{#expr:{{{5|0}}}+{{{14|0}}}+{{{23|0}}}+{{{32|0}}}+{{{41|0}}}+{{{50|0}}}+{{{59|0}}}+{{{68|0}}}+{{{77|0}}}}}'''
|'''{{#expr:{{{6|0}}}+{{{15|0}}}+{{{24|0}}}+{{{33|0}}}+{{{42|0}}}+{{{51|0}}}+{{{60|0}}}+{{{69|0}}}+{{{78|0}}}}}'''
|'''{{#expr:{{{7|0}}}+{{{16|0}}}+{{{25|0}}}+{{{34|0}}}+{{{43|0}}}+{{{52|0}}}+{{{61|0}}}+{{{70|0}}}+{{{79|0}}}}}'''
|'''{{#expr:{{{8|0}}}+{{{17|0}}}+{{{26|0}}}+{{{35|0}}}+{{{44|0}}}+{{{53|0}}}+{{{62|0}}}+{{{71|0}}}+{{{80|0}}}}}'''
|'''{{#expr:{{{9|0}}}+{{{18|0}}}+{{{27|0}}}+{{{36|0}}}+{{{45|0}}}+{{{54|0}}}+{{{63|0}}}+{{{72|0}}}+{{{81|0}}}}}'''
|'''{{#expr:{{{1|0}}}+{{{2|0}}}+{{{3|0}}}+{{{4|0}}}+{{{5|0}}}+{{{6|0}}}+{{{7|0}}}+{{{8|0}}}+{{{9|0}}}+{{{10|0}}}+{{{11|0}}}+{{{12|0}}}+{{{13|0}}}+{{{14|0}}}+{{{15|0}}}+{{{16|0}}}+{{{17|0}}}+{{{18|0}}}+{{{19|0}}}+{{{20|0}}}+{{{21|0}}}+{{{22|0}}}+{{{23|0}}}+{{{24|0}}}+{{{25|0}}}+{{{26|0}}}+{{{27|0}}}+{{{28|0}}}+{{{29|0}}}+{{{30|0}}}+{{{31|0}}}+{{{32|0}}}+{{{33|0}}}+{{{34|0}}}+{{{35|0}}}+{{{36|0}}}+{{{37|0}}}+{{{38|0}}}+{{{39|0}}}+{{{40|0}}}+{{{41|0}}}+{{{42|0}}}+{{{43|0}}}+{{{44|0}}}+{{{45|0}}}+{{{46|0}}}+{{{47|0}}}+{{{48|0}}}+{{{49|0}}}+{{{50|0}}}+{{{51|0}}}+{{{52|0}}}+{{{53|0}}}+{{{54|0}}}+{{{55|0}}}+{{{56|0}}}+{{{57|0}}}+{{{58|0}}}+{{{59|0}}}+{{{60|0}}}+{{{61|0}}}+{{{62|0}}}+{{{63|0}}}+{{{64|0}}}+{{{65|0}}}+{{{66|0}}}+{{{67|0}}}+{{{68|0}}}+{{{69|0}}}+{{{70|0}}}+{{{71|0}}}+{{{72|0}}}+{{{73|0}}}+{{{74|0}}}+{{{75|0}}}+{{{76|0}}}+{{{77|0}}}+{{{78|0}}}+{{{79|0}}}+{{{80|0}}}+{{{81|0}}}}}'''

|}<noinclude>

==Usage==
Produces a D/T grid for all combinations. If an entry is left blank, a dash is indicated.

<code><nowiki>{{</nowiki>DT<BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
|t1|t1.5|t2|t2.5|t3|t3.5|t4|t4.5|t5 <nowiki></nowiki><BR>
}}

[[Category: Geocaching Templates]]

Project-GC UserScript

2024-04-26T20:35:18Z

4523550: Corrected headerlevels and added the "further documentation" section. Removed the empty/unused category "Power user tools".

<table style="width:100%;">
<tr>
<td style="width:70%; vertical-align:top;">
== Description ==
This tool is a user-enabled script that extends the user experience at the [https://geocaching.com Geocaching.com website], primarily by integrating Project-GC into it. The audience for this script are primarily geocaching power-users, however some of the basic features can make the novice or beginner experience better as well.

This script was originally written by Jonas "lillfiluren" Högström; and has been maintained and improved upon by various other [https://github.com/magma1447/greasemonkey-geocaching-projectgc/graphs/contributors geocaching community members].
== Prerequisites ==
* While ''not required'' - it is highly recommended that you have a [https://project-gc.com/Home/Membership Project-GC membership]. ''Many features will not be present without a membership.''
* You need to know how to install an extension<ref name="extension">Web browser extensions are also known as add-ons or plug-ins</ref> into your web browser.
* Familiarity with GreaseMonkey<ref name="greasemonkey">For more info about Greasemonkey, see [https://en.wikipedia.org/wiki/Greasemonkey Wikipedia article on Greasemonkey]</ref> or TamperMonkey<ref name="tampermonkey">For more info about TamperMonkey, see [https://en.wikipedia.org/wiki/Tampermonkey Wikipedia article on Tampermonkey]</ref>, or Firemonkey<ref name="firemonkey">For more info about Firemonkey, see [https://addons.mozilla.org/en-US/firefox/addon/firemonkey/ More information about Firemonkey]</ref> managers that enable the this tool and many others based on Userscripts<ref name="userscripts">For more info about Userscripts, see [https://en.wikipedia.org/wiki/Userscript Wikipedia article on Userscripts]</ref>.

== Further Documentation ==
Further documentation of the script has been done in the category [[:Category:Project-GC Userscript|Project-GC Userscript]].
</td>
<td style="width:30%; padding-left:25px;">__TOC__ <br><br/>
== Additional Sections ==
* [[Project-GC_Userscript/Development|Development]]
* [[Project-GC_Userscript/Feature_List|Feature List]]
</td>
</tr>
</table>

== Installation ==
There are TWO different things you must install:
# A userscript manager web browser extension.
# The script (userscript) itself.

=== Web browser extension installation ===

Depending on the web browser that you use, follow the directions below to install the extension<ref name="extension" />. Then proceed to the next section

==== Firefox ====
''These directions are for Firefox v104.* and might vary with older or newer versions.''
# From the "Tools" menu, choose "Add-ons and Themes".
# On the left, locate "Extensions" and click it.
# At the top of the window, look for "Find more add-ons" with a search-box next to it. Type in "greasemonkey" (one word) into the box and press return.
# A list of extensions will show up, choose the extension you wish to use (Greasemonkey<ref name="greasemonkey" />, Tampermonkey<ref name="tampermonkey" />, or Firemonkey<ref name="firemonkey" />)
# On the page describing the extension, looked for a <span style="color:blue;">blue</span> "Add to Firefox" button. Click it.
# A pop-up will appear to re-iterate what the extension will do, click "Add".

''At anytime, if you wish to change which extension you are using or want to remove the extension, repeat the steps above, and click the "Remove" button that will appear in place of the "Add" button.''

==== Chrome ====
''These directions are for Google Chrome v104.* and might vary with older or newer versions.''
# Open (launch) Google Chrome.
# Visit the following website: https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo
# Click the <span style="color:blue;">blue</span> "Add to Chrome" button.
# A page describing the extension after it is installed will appear, it is safe to close this tab/window.

''At anytime, if you wish to change which extension you are using or want to remove the extension, repeat the steps above, and click the "Remove from Chrome" button that will appear in place of the "Add" button.''

==== Other web browsers ====
Firefox and Chrome are recommended, however depending on the web browser, there may be a Userscript manager available for it. Tampermonkey<ref name="tampermonkey" /> is the only extension (as of 8/2022) that lists various other browsers that it supports.

=== Userscript installation ===
# Visit the [https://greasyfork.org/en/scripts/9713-geocaching-com-project-gc Greasy Fork] website.
# Find and click on the <span style="color:green;">green</span> "Install this script" button.
# A new window will appear, giving more information about the script. ''It is encourage to always read what the script will do before installing.''
# Find the "Install" button and click it.

Once the script is installed, you can view the script source code or enable/disable the script. Once a script is installed, most userscript managers will keep it up-to-date automatically as part of the default settings. Refer to additional pages regarding the various Userscript managers on their usage.

== Translations ==
The UserScript supports translations and is translated in the same way as the rest of [[Project-GC]], via [https://crowdin.com/project/Project-GC Crowdin]. Please note that the translations aren't done in real-time. Once translated at Crowdin they need to be manually fetched into Project-GC and pushed via a new release.

Also the UserScript fetches the translations from [[Project-GC]]. It has built-in caching so that it doesn't ask for translations upon every single page load, therefore further delay of new translations will exist.

<table style="width:100%;">
<tr>
<td style="width:50%; text-align:left; vertical-align:top; padding-right: 20px;">

== Notes ==
<references/>
== Credits ==
* Idea and initial work: Jonas "lillfiluren" Högström.
* Cleanup and actually make things work properly (cross browser compatible) by [https://github.com/Surfoo Surfoo].
* Smashing bugs and working with community: [https://github.com/jewettg Greg Jewett (jewettg)]
* Many other various [https://github.com/magma1447/greasemonkey-geocaching-projectgc/graphs/contributors contributors]. ''Thank you!''
</td>
<td style="width:50%; text-align:left; vertical-align:top; padding-left: 20px; padding-right: 20px;">
== Open Source ==
The UserScript is open source and the source code is available on Github. Please visit the [https://project-gc.com/w/Project-GC_Userscript/Development Development Section] for more information.
<br/>
=== Open Source Used (Citations)===
<table style="width:100%; border-spacing: 1px;">
<tr style="background-color: #000; color: #fff;">
<th>Software Title/Name</th>
<th>Author</th>
<th>Version / License</th>
<th>Links</th>
</tr>
<tr style="background-color: #ccc; color: #000;">
<td>exif-js/exif-js</td>
<td>(c)2008 Jacob Seidelin</td>
<td>The MIT License (MIT)<br/>v2.2.0</td>
<td>[https://github.com/exif-js/exif-js GitHub Repo]</td>
</tr>
</table>
=== License ===
Please read [https://github.com/magma1447/greasemonkey-geocaching-projectgc/blob/fbb9b106e26151ea3d93662bbcd4a6fd40d4f234/LICENSE LICENSE] within Repository.
</td></tr></table>

[[Category: Project-GC Userscript]]

TypeHistory

2024-04-26T20:18:42Z

4523550: Added image.

[https://project-gc.com/Tools/TypeHistory Type history] is in [[Beta|beta]]. '''Type history''' is a tool where users with a [[paid membership]] can find out if any of the caches found by a specific user have had their [[Geocache#geocache types|cache type]] changed during the time [[Project-GC]] tracked these changes. Project-GC have been tracking the various changes in metadata since October 2018.

Project-GC can not detect the update of a cache type in real-time, the dates in the table is from when Project-GC detected the change, not from when the actual change occurred.

This tool uses [[Filters#Profile name|Profile name]] only and the results start with information about how many unique geocaches the user have found which has changed their cache type. The table shows the date of the found, GCcode, name of the cache and current and previous cache type. The boxes for each cache type has the date of when the change was detected and the box for the cache type the cache had when the user logged it is tinted green.

[[File:TypeHistoryRowGiga.png|700px|thumb|left|A row of the result from the tool]]
{{Clear}}

Since post-publication changes of cache types is rare most users will just see a list of Mega-Events and Giga-Events that gained their status after publication.

[[Category:Tools]]

File:TypeHistoryRowGiga.png

2024-04-26T20:17:44Z

4523550: A row from the result of the Type History-tool. ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
A row from the result of the [[TypeHistory|Type History]]-tool.

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

DTHistory

2024-04-26T20:16:33Z

4523550: Formatting of image.

[https://project-gc.com/Tools/DTHistory D/T History] is in [[Beta|beta]]. '''D/T History''' is a tool where users with a [[paid membership]] can find out if any of the caches found by a specific user have had their [[D/T|D/T rating]] changed during the time [[Project-GC]] tracked these changes. Project-GC tracked the changes of D/T ratings between October 2015 and November 2017 and then started again in October 2018 and have been tracking the changes since.

Project-GC can not detect the update of a D/T rating in real-time, the dates in the table is from when Project-GC detected the change, not from when the actual change occurred.

This tool uses [[Filters#Profile name|Profile name]] only and the results start with information about how many unique geocaches the user have found which has changed their D/T ratings. The table shows cache type, date of the found, GCcode, name of the cache and current and previous D/T-ratings. The boxes for each D/T rating has the date of when the change was detected and the box for the [[D/T]] the cache had when the user logged it is tinted green.
[[File:DTHistoryRow.png|700px|thumb|left|A row of the result from the tool]]
{{Clear}}
[[Category:Tools]]

SizeHistory

2024-04-26T20:15:44Z

4523550: Added image.

[https://project-gc.com/Tools/SizeHistory Size history] is in [[Beta|beta]]. '''Size history''' is a tool where users with a [[paid membership]] can find out if any of the caches found by a specific user have had their [[Geocache#geocache sizes|cache size]] changed during the time [[Project-GC]] tracked these changes. Project-GC have been tracking the various changes in metadata since October 2018.

Project-GC can not detect the update of a cache size in real-time, the dates in the table is from when Project-GC detected the change, not from when the actual change occurred.

This tool uses [[Filters#Profile name|Profile name]] only and the results start with information about how many unique geocaches the user have found which has changed their cache type. The table shows the date of the found, GCcode, name of the cache and current and previous cache size. The boxes for each cache size has the date of when the change was detected and the box for the cache size the cache had when the user logged it is tinted green.

[[File:SizeHistoryRow.png|700px|thumb|left|A row of the result from the tool]]
{{Clear}}

[[Category:Tools]]

File:SizeHistoryRow.png

2024-04-26T20:13:48Z

4523550: Showing one row of result from Size History-tool. ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
Showing one row of result from [[SizeHistory|Size History]]-tool.

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

DTHistory

2024-04-26T20:07:51Z

4523550: Added image.

[https://project-gc.com/Tools/DTHistory D/T History] is in [[Beta|beta]]. '''D/T History''' is a tool where users with a [[paid membership]] can find out if any of the caches found by a specific user have had their [[D/T|D/T rating]] changed during the time [[Project-GC]] tracked these changes. Project-GC tracked the changes of D/T ratings between October 2015 and November 2017 and then started again in October 2018 and have been tracking the changes since.

Project-GC can not detect the update of a D/T rating in real-time, the dates in the table is from when Project-GC detected the change, not from when the actual change occurred.

This tool uses [[Filters#Profile name|Profile name]] only and the results start with information about how many unique geocaches the user have found which has changed their D/T ratings. The table shows cache type, date of the found, GCcode, name of the cache and current and previous D/T-ratings. The boxes for each D/T rating has the date of when the change was detected and the box for the [[D/T]] the cache had when the user logged it is tinted green.
[[File:DTHistoryRow.png|frame|left|A row of the result from the tool]]
{{Clear}}
[[Category:Tools]]

File:DTHistoryRow.png

2024-04-26T20:02:09Z

4523550: A row of the result of the D/T History-tool. ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
A row of the result of the [[DTHistory|D/T History]]-tool.

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

Challenge checker

2024-04-26T19:51:54Z

4523550: /* Challenge Checker image */ spelling

== What is it? ==
A '''Challenge checker''' uses program code that checks if a user has fullfilled 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. More general information about challenge caches is available in the article [[challenge cache]]s, for example information about [[Challenge cache#Challenge Exceptions|challenge exceptions]].

== How does it work? ==
A challenge checker consists of two parts: a challenge checker script and a tag. The script is a piece of program code written in the programming language Lua. The script checks for a certain condition, for example a script can check if the user has found 100 mystery caches. Another script can check if a user found a cache on 365 calendar days. A tag associates one or more scripts with a specific challenge cache, and defines (customizes) cache type and quantity for a script to match the challenge cache.

The tag links a checker script, a challenge cache, and (optionally) a set of parameters for the checker script. This means that the same 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.

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.

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

==Challenge Checker image==
It is preferred to link the challenge checker with the supplied image since it contains extra information for the users. An example of such an image can be seen below. The image linked in the wiki are static due to technical reasons, the images on cache pages are not and will be updated with current numbers automatically.

[[File:62346.png]] [[File:70522.png]] [[File:68127.png]]

In the top left corner is an icon of a skull and crossbones with a number, this is the calculated [[challenge difficulty]].

Below the challenge difficulty is a red circle for challenges were the saved result for the authenticated user is not fulfilled. For challenges that the user have ran the checker and fulfilled the challenge it is a green checkmark, the green checkmark can be a false positive in cases were the user has ran the checker previously but since lost their qualifications. If the user has found the challenge the result is replaced by an emoji.

To the right are the number of times the checker has been ran with a "fulfilled" or "not fulfilled" result. There are anti-spam measurements applied to these counters but it should not be viewed as number of people that have completed the challenge since both the green and red counters can increase multiple times by the same account.

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

==Disabled checkers==
Project-GC has a system for disabling the challenge checker if the cache lacks the Challenge-attribute, this is because the challenge-attribute is mandatory per the guidelines.

== 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 features ==
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.

== Notes ==
<references />

[[Category:Site Info]]

Map feature

2024-04-26T19:46:26Z

4523550: Updated list of maps and added images of some of the buttons.

File:PGC VGPS Controls.png

2024-04-26T19:40:05Z

4523550: Showing PGC VGPS Controls-button on Maps. ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
Showing PGC VGPS Controls-button on Maps.

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]

File:PGC Controls.png

2024-04-26T19:38:36Z

4523550: Showing PGC controls-button on Maps. ==Copyright== {{PGC Screenshot}} Category:PGC Screenshots

== Summary ==
Showing PGC controls-button on Maps.

==Copyright==
{{PGC Screenshot}}

[[Category:PGC Screenshots]]