Frequently Asked Questions

How do I generate the "my finds" pocket query?

Please see the instructions page for details.

Does CacheStats run on the Mac?

Sorry, not directly, however it will work if you have the Mono environment installed. The Mono environment allows some .NET applications (such as CacheStats) to run on different operating systems including Mac and Linux. If you want to give it a try, you'll want to download the zipped version of CacheStats so you don't have to monkey with the Windows installer.

Do I need to unzip my gpx files from the Pocket Query?

No, CacheStats can load either the .zip file or the .gpx file. But when you save the attachment from your pocket query, you should save it the same way each time you generate a new pocket query. By overwriting the old pocket query, CacheStats will automatically load the new one the next time you start it.

I decided to unzip my gpx files. Which file do I use?

CacheStats only uses the main one, the one without "-wpts" in the name (the one with wpts int the name only contains child waypoints such as parking coordinates).

Why didn't my statistics update even though I generated a new pocket query?

CacheStats is probably still loading your old gpx file from your previous pocket query. Check the date shown on the status and news tab of CacheStats to see if this is the case. If so, then you probably saved the gpx or zip file to a different folder than you did last time. Or you may have extracted the gpx files last time, but saved the zip file this time (or vice-versa). You can either re-save the pocket query from the email attachment (to overwrite your previous pocket query), or click on the open gpx file button to open the gpx file in the new location.

Why doesn't CacheStats start when I double click on the gpx file?

CacheStats purposely doesn't register itself to start when you double click on a .gpx file so as not to interfere with any existing programs you have that read .gpx files, such as GSAK. To open a .gpx file in CacheStats you must start CacheStats and click on the Open GPX File button near the bottom.

Can I use GSAK to generate a .gpx file?

Yes. When you export a GPX file from GSAK, in the Logs section of the export window, make sure you set "Limit the number of logs to export" to 0 and check the box that says "Always include my logs". In general, CacheStats requires that the .gpx file contain only your logs. If logs from others are mixed in, it doesn't know which one are yours.

Do my statistics update automatically?

No. CacheStats gets its data from the my finds pocket query, so you must regenerate the query to get updated statistics (note that geocaching.com prevents you from doing this more than once a week). After regenerating the pocket query, you will have to go through the same steps of getting the email and saving the attachment. Each time you do this, you should save the attachment to the same file name and folder so CacheStats will automatically read in the new data. If you save the attachment to a different name or folder, you will have to click open gpx file to read in the new file.

How are FTF's tracked?

Since geocaching.com doesn't keep track of FTF's, CacheStats can only assist you in finding and keeping track of them, but it has no way of knowing definitively whether you were FTF for a particular cache or not. To set your FTF's: first click on the Caches tab and enter "FTF" in the search box (or any other phrase that you want to search on) to search your logs. All caches that contain "FTF" somewhere in the log will show in the list. You should then click on each cache and read your log to decide if it's really an FTF and not something like "just missed FTF by 20 minutes". If it truly is an FTF, then click the FTF checkbox in the cache description area. When you are done, clear the text in the searchbox. If you were first to find on some caches but did not include "FTF" in your log, you can still click the FTF checkbox for those caches, but you will have to remember which ones they were. One final note: you can edit your logs by clicking on the edit link if you want to add or remove FTF in the log. Your next pocket query will then have those changes.

How do I move my settings such as FTF's and Favorites to a new computer?

Assuming you have a means to transfer files between the two systems, e.g. a network or a USB drive, you can transfer files using the following steps:

  1. On your old computer, start CacheStats and click on the About button
  2. Click on the Browse to data folder button
  3. Copy the data file (the data file is named the same as your gpx file plus Data after the name, e.g. 123456Data.xml). Transfer it to the new computer and paste it to the equivalent folder on your new computer (use the same trick to browse to the data folder).
  4. You can optionally transfer the settings.xml file (which contains the text to include when you export to HTML) to your new computer in the same manner. Note this file also stores the last gpx file opened, so if you store the gpx file in a different location on your new computer, you will need to click the Open GPX File button in CacheStats after copying the settings file.

I use multiple computers - any way to share my settings between them?

Yes. Install CacheStats to a flash drive (or you can copy the CacheStats folder from the \program files\logicweave folder and paste it to the flash drive). If you haven't already, run it once so that the settings files are created. Find the settings files as described in the question above and copy them to the same folder that CacheStats was installed to on the flash drive. When you run CacheStats from the flash drive, it will use the settings files stored on the flash drive.

Why is it showing a state that I never visited?

You may have found a moving cache which is now located in a different state. You can correct it by clicking on the show details button on the locations tab and excluding the incorrect state(s) so they won't show in your statistics.

Why is it showing an incorrect date for one of my cache finds?

CacheStats reports the date that you used when you logged the find. If you waited a few days to log some of your finds and forgot to change the date, then the date will reflect the date that you logged the find, not the date of the find. You can fix this by clicking on the incorrect cache in the caches tab and clicking the "edit" link next to the log entry which will take you to geocaching.com where you can change the date. The date will be corrected in your next pocket query.

How do I fix up a milestone?

CacheStats bases milestones first on the date of the log and then on the order that you logged finds for a given day. If you logged your finds out of order, you can fix milestones in CacheStats by doing the following:

  1. Click on the incorrect milestone
  2. Click on the "Make correction" button below the list of milestones
  3. Select the correct cache for the milestone

The other possibility for an incorrect milestone is if you accidentally logged the wrong date for a cache. If this is the case, you can change your log date on geocaching.com. Use the procedure above to find the cache with the incorrect date, then click on the "Edit log on geocaching.com" button. That will open your web browser and take you to your log entry on geocaching.com where you can change the date.

Why aren't all my "Did Not Find" logs (DNF's) listed?

The data file generated by geocaching.com only contains information for the caches that you have found. So if you logged a DNF and then later eventually found the cache, the DNF log would be included in the gpx file. But the GPX file won't have any data for caches that you logged a DNF for but haven't found yet.