When I first started using project-gc, I got a lot of fancy badges that I may not have deserved. In particular, I got diamond in both "Head in the ground" and "The long distance cacher" and platinum in "Head in the clouds". This, it seemed, was due to the stats calculator using data from the type "Reverse (Locationsless) cache". After a while, my stats dropped a few points, since the data from the reverse caches were now left out of the calculation of badges and maps. That is OK, since I have never physically been anywhere near the listed coordinate for those caches.
The places the location data from reverse caches was left out were:
-
BadgeGen
-
Finds
-
Most NSEW cache found
-
Highest and lowest elevations
-
Maps
The places where it did appearently not get fixed:
-
Elevation chart (finds) (lists 2 caches > 2500m - not listed on BadgeGen or any other place)
-
Stats compare (premium feature) - (lists 13 countries where the count listed all other places is currently 10 (maps, badgegen))
This concludes the bug-report portion of this post. How to handle it is essentially a feature-request. Read on for proposed solutions.
I realize that because of the special nature that surrounds the Reverse caches and the fact that people who have found them are relatively rare makes them a low priority when implementing functionality on the website. I just thought that it would be a good idea to address the problem of the locationless caches by doing one of the following:
1: Eleminate all location-based data from locationsless caches
Eliminate them from any statistics calculation that involves anything that has to do with location since they are locationless. That is:
-
Traveled distance (cache-to-cache distance)
-
Distance from home
-
All elevation-related
-
Visited areas (counties/states/countries)
2: Use actually visited location
An alternative that will require more work: Everybody logging a reverse cache had to post a coordinate along with their log. The whole point of those were to locate some object described in general in the cache description and then post its coordinates along with photos of the object. If you have full access to the logs, the coordinates that the individual finder has been to will be there along with his or her log.
I realize that this will be more work, but it will be more representative of where the caches has actually physically been to. Consider it another feature-request (hence the tag) for a week with multiple thursdays in it :)