Difference between revisions of "Milestones tab"

From Project-GC
Jump to: navigation, search
m (grammar)
(currently four modules)
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The '''Milestones tab''' is the second tab in a users [[Profile Stats]], as the name suggest this tab shows a users milestones. This tab has three modules.  
+
{{TabNav}}
 +
The '''Milestones tab''' is the second tab in a user's [[Profile Stats]]. As the name suggest, this tab shows a user's milestones. This tab has four [[module]]s.  
  
 
== Milestones ==
 
== Milestones ==
The first module shows a list of the users milestones. The first milestones are 1, 10, 50 and 100 caches, after that and up to 1000 caches every hundred cache is considered a milestone. After 1000 every five hundred cache is considered a milestone. At the bottom of the list the users most recent cache is shown, even if it is not a milestone.  
+
The first module shows a list of the user's milestones. The first milestones are 1, 10, 50 and 100 caches, after that and up to 1000 caches every hundredth cache is considered a milestone. Between 1000 and 5000 caches every five hundredth cache is considered a milestone, and beyond that every thousandth cache is listed. At the bottom of the list the users most recent cache is shown, even if it is not a milestone.  
  
===Different milestones at Project-GC vs Geocaching.com===
+
=== Order ===
 +
Project-GC orders the logs by three fields in ascending order.
 +
# The date of the found log.
 +
# The full timestamp of when the log was created.
 +
# The ID of the log. Since logs of geocaches and logs of lab caches are from different systems their log-ids are not compatible. In this case labs are sorted last. But this will only be an issue if a log for a geocache is created on the same second as one for a lab cache.
  
The milestones on this tab may not match the milestones shown in the user's Geocaching.com profile for multiple reasons. The milestones at Project-GC are calculated and not fetched from Geocaching.com. At Geocaching.com the user can chose to lock their milestones to a specific cache even if it's not the milestone that is calculated by Geocaching.com, this is not possible to do at Project-GC. An other reason is that the data provided for geocaches in the [[Geocaching LIVE api‏‎]] and the data provided for [[Lab cache]]s in the [[Enterprise API]] does not match, this means that Project-GC does not have enough information to determine the order between Lab cache finds and other geocaches if they are made on the same day which might cause problems when planning a special cache for a milestone.
+
Before 2024-02-19 Project-GC sorted the milestones based on log dates and log-ids only. Lab caches were always sorted last on every day.
  
The specific problem is that each geocache log has a date and log ID which is a number, this identifies which log belongs on what date and in which order they come on that day. For Lab caches, a timestamp is provided. This identifies which date the lab cache was logged on, but it also has the exact time. The result is that Lab Cache finds can be sorted in the proper order, but since there is no timestamp for other geocaches it is not possible to know which way the sequence of all cache finds occurred on a particular day.  
+
=== Different milestones at Project-GC vs Geocaching.com ===
 +
 
 +
The milestones on this tab may not match the milestones shown in the user's Geocaching.com profile for multiple reasons. The milestones at Project-GC are calculated and not fetched from Geocaching.com. At Geocaching.com, the user can chose to lock their milestones to a specific cache even if it's not the milestone that is calculated by Geocaching.com, this is not possible to do at Project-GC. Geocaching.com also includes retracted geocaches, which aren't even known to Project-GC. This should not be an issue in the future since new guidelines say that logged geocaches shouldn't be retracted (but the effect for previous loggers of already-retracted cacher will remain, though).
  
 
== First cache by country ==
 
== First cache by country ==
This is a list of the first cache the user found in each country they have found caches in. The list shows date, country, cache type, GCcode and the milestone of that cache.  
+
This is a list of the first cache the user found in each country they have found caches in. The list shows date, country, cache type, GC code and the milestone of that cache.
 +
 
 +
== First cache by region in home country ==
 +
This is a list of the first cache the user found in each region they have found caches in. Only regions in the user's [[home location|home country]] are shown. The list shows date, region, cache type, GC code and the milestone of that cache. Under the list it's shown how many of the regions of the home country the user have found a cache in.
  
 
== First cache by cache type ==
 
== First cache by cache type ==
This is a list of the first cache the user found of each cache type they have found. The list shows date, country, cache type, GCcode and the milestone of that cache.
+
This is a list of the first cache the user found of each cache type they have found. The list shows date, country, cache type, GC code and the milestone of that cache.
  
[[Category:Statistics]]
+
[[Category:Statistics]] [[Category: Profile Stats]]

Latest revision as of 14:24, 20 September 2024

The Milestones tab is the second tab in a user's Profile Stats. As the name suggest, this tab shows a user's milestones. This tab has four modules.

Milestones

The first module shows a list of the user's milestones. The first milestones are 1, 10, 50 and 100 caches, after that and up to 1000 caches every hundredth cache is considered a milestone. Between 1000 and 5000 caches every five hundredth cache is considered a milestone, and beyond that every thousandth cache is listed. At the bottom of the list the users most recent cache is shown, even if it is not a milestone.

Order

Project-GC orders the logs by three fields in ascending order.

  1. The date of the found log.
  2. The full timestamp of when the log was created.
  3. The ID of the log. Since logs of geocaches and logs of lab caches are from different systems their log-ids are not compatible. In this case labs are sorted last. But this will only be an issue if a log for a geocache is created on the same second as one for a lab cache.

Before 2024-02-19 Project-GC sorted the milestones based on log dates and log-ids only. Lab caches were always sorted last on every day.

Different milestones at Project-GC vs Geocaching.com

The milestones on this tab may not match the milestones shown in the user's Geocaching.com profile for multiple reasons. The milestones at Project-GC are calculated and not fetched from Geocaching.com. At Geocaching.com, the user can chose to lock their milestones to a specific cache even if it's not the milestone that is calculated by Geocaching.com, this is not possible to do at Project-GC. Geocaching.com also includes retracted geocaches, which aren't even known to Project-GC. This should not be an issue in the future since new guidelines say that logged geocaches shouldn't be retracted (but the effect for previous loggers of already-retracted cacher will remain, though).

First cache by country

This is a list of the first cache the user found in each country they have found caches in. The list shows date, country, cache type, GC code and the milestone of that cache.

First cache by region in home country

This is a list of the first cache the user found in each region they have found caches in. Only regions in the user's home country are shown. The list shows date, region, cache type, GC code and the milestone of that cache. Under the list it's shown how many of the regions of the home country the user have found a cache in.

First cache by cache type

This is a list of the first cache the user found of each cache type they have found. The list shows date, country, cache type, GC code and the milestone of that cache.