abcdmCachers

Is there a mailing list? If so, please add me. Thanks!

With CacheStats 3.0 unzipping the GPX files is optional since it can now read the zip file directly. I just sent you an email through your geocaching account. I'd like to help you figure out what's going on in case I introduced a new bug in 3.0.

Hi Galdrin, There are several PowerPoint presentations here, one of which I've presented at a couple of free seminars: http://www.wi-geocaching.com/modules.php?n...ion%20Resources Good luck with your presentation. Doug

Hi everyone, Some of you may be interested to know that I released CacheStats 3.0 last weekend. One of the new features is an enhanced cache listing page that makes it easier and more fun to browse your past finds. For example, you can now show your caches grouped by various attributes, such as by owner, or by the month and year the cache was placed. Once grouped you can order the groups alphabetically or by size of group. I also added a simple news reader so you can follow various geocaching blogs as well as this very forum from right within CacheStats. You can read about all the new features here. Hope you enjoy. Doug (abcdmCachers)

Hi. Make sure you are running the latest build (2699). There were a couple fixes made to adress this issue. You can find out which buildl you are running by clicking on the about button. If your build number is smaller, you can just download again from the website and install. If that doesn't address your issue, please send me your .gpx file via the support address listed on the website. Doug

Here's one that I thought was clever but unfortunately never got around to finding before it was archived: Watcher in the Woods Since I never found it, I kind of have to guess what it was all about, but based on the logs, I think it used the well-known online pick-a-card card trick (for example, http://www.timwike.dircon.co.uk/card.html). I'll bet this cache was a lot of fun for kids and even for those adults who aren't familiar with the trick. It's all in the presentation, right? Imagine a "watcher in the woods" running ahead to the final and removing the card you selected at the first waypoint. I think kids at the right age would love it.

If you maintain a GSAK database with just your finds, populated with .gpx files that you download from each cache page (not .loc files), then yes you can do this. (I'm assuming that non-premium members can download individual .gpx files from the cache page, but I don't know this for sure). Using GSAK, export to gpx file format from the file/export menu. On the export form, make sure you tell it to limit the number of logs to export to 0 and also check the box that says always include my logs. This is a little counter-intuitive, but it will create a gpx file that contains your log entries only, a requirement of CacheStats.

Hi, I see from your profile that you have uploaded your stats, so I assume it's working for you now? CacheStats sometimes fails when it finds unexpected items in the gpx file. For example, one known problem that I need to fix is if the gpx file is exported from GSAK and includes child waypoints, you will run into the error you mention. If you are still having problems, please email the gpx file (using the email address on the logicweave website) and I can take a look to see what the problem is. Thanks.

I'm reminded of this article in Today's Cacher from 2 years ago. Thanks to Google, was able to dig it up: http://www.todayscacher.com/2005/apr/caches2.asp Quote from the article: "It seems as time goes by the fine art of a quality cache page is dying" I tend to agree. I don't know if there is a correlation between the cache page length and cache quality, but I do like to see more than just the minimum. Especially if I'm from out of town: why might I want to visit this cache? What's special about the location? Is it nearby significant POI's? (But don't tell me what was in the cache when it was placed 3 years ago, but that's another topic).

Another possibility - are you exporting your gpx file from GSAK and then loading the exported file into CacheStats? Someone else ran into this same error when doing this. The problem was resolved by unchecking "export child waypoints" on the export page. Don't know if this is what's happening for you, but thought I'd at least mention it.

tbtroopers, It's possible the data file associated with your gpx file has become corrupted (this file saves your favorites, and FTFs for example). I would be happy to take a look at it for you if you would like to see if I can determine the problem. If so, click on the "About" button, then click on the button that says "browse to data folder". In that folder there will be a file that has the same name as your gpx file with Data appended to it (e.g. 123456Data.xml). Please send that file to me using the email link on the www.logicweave.com website. Or, if you don't want to go to the trouble, you could temporarily rename or permanently delete the data file to see if that clears up the problem. The next time you run, it would create a new empty file. This would be a reasonable solution if you haven't spent a lot of time setting up your FTFs or Favorites. If you go this route, let me know how it goes.

Chuck, Red90 is correct (about opening the gpx file ;-)), but let me know if you're still having problems and I can help you out.

The time of day that you logged shouldn't matter, only the date that you select when entering the log. But I don't know why it would show 12/30 in gc.com and 12/31 in cachestats. Presumably it contains 12/31 in the gpx file, so maybe gc.com pocket query generator extracts the dates differently? Feel free to send me your gpx file via the email address on logicweave.com and I can take a look to see if I can figure out what's going on. CacheStats orders caches first by find date, then by the order of caches logged on that date if there is more than 1. So if you logged your finds in a different order than you found them, you'll have a discrepancy. CacheStats lets you correct this: select the milestone, click on the "Make correction" button, then select the correct cache for that milestone. The correction will be saved in the CacheStats data file, so you should only have to do this once.

I found a little bug in CacheStats today. Just wanted to let CacheStats users know that on Jan. 1 your projected number of cache finds for 2007 will be way off (I mean waaaay off - it will take quite a new year's resolution and superhero stamina if you want to meet the projected value). But as soon as you generate a gpx file that has at least one cache find for 2007, the calculation will correct itself. Or you can download an update that has the fix for the problem here: http://www.logicweave.com/cachestats.html (Just need to download and install, previous version will automatically be uninstalled). A few other minor problems have been fixed since the initial release of 2.0 in November: - New goal values not shown in HTML export until program was exited and restarted - World map checkbox didn't stay checked - GC10C has no D/T values (!) causing CacheStats to choke. Not sure if there are any others like this one. - Nova Scotia and Czech Republic not filled in on maps If you're not familiar with CacheStats yet, it's a program that calculates statistics based on your my-finds pocket query. Click above to learn more.

Fixed this problem and the update is on the website now. If you decide to install the update, your previous version will automatically be updated, i.e. you don't need to manually uninstall the previous version first. This is true if you are upgrading from 1.0 too.

Received the first bug report - If you export your goal to HTML, it shows as 0. I haven't had time to look into this yet, but it appears that the correct value will be shown if you exit CacheStats and then export again. I'll look into getting this fixed when I get a bit more time. BTW, anyone notice that The Cheeseheads, creater of itsnotaboutthenumbers.com and I are both from Wisconsin? I guess SE Wisconsin is a little like California's high-tech Silicon Valley, although it might be more aptly named the Silicon Pasture .

Actually, you can use a GPX file exported from GSAK (assuming you have a GSAK database that contains only your finds). If the GSAK database includes logs from anyone other than you, you will need to make sure only your logs get exported by doing this: On the GSAK export page, select 0 for "limit number of logs to export", and check "Always include my logs". There's a screen shot of this on the original CacheStats 1.0 thread: http://forums.Groundspeak.com/GC/index.php...t&p=2292250 One thing to note concerning this is that CacheStats creates a data file to store information that isn't included with the gpx file (e.g. FTFs, favorites, etc.) based on the name of the GPX file. This means that if you export a GPX file using GSAK and give it a different name than your "my finds" GPX file, those settings won't be pulled over. So you should either give it the same name (probably after testing with a different name to make sure it works), or just use the GSAK export as a temporary until the next PQ comes in. Or, if you'd like to maintain two sets of data (this would apply if you want to run CacheStats on two speparate computers too), you can go to the data folder and copy the original data file to overwrite the GSAK data file. The data folder is accesible from the About button. Hopefully this makes at least some sense. If not, I can elaborate later.

CacheStats version 2.0 is now available. You can learn more about it and download here: http://www.logicweave.com/cachestats.html For those of you not yet familiar with CacheStats, this program analyzes your "My Finds" Pocket Query and reports lots of interesting facts like your find rate over the years, caching streaks, most finds in one day, most days cached in a month, etc. It also helps you find and record your FTFs, record your favorite caches in several categories, and provides a goal calculator. And if you want the whole world to know how much of a caching nut you are, you can export your statistics to HTML and paste them into your geocaching profile. New in 2.0: Lots more statistics including days cached (how often would you say you go caching on average? CacheStats will tell you), breakdowns of type, size difficulty and terrain, stats for current and previous month Improved HTML export - now that geocaching.com has increased the character limit in profile pages, you can export more data including your FTF list. Also, CacheStats will let you enter your other profile information (hobbies, etc.) so updating your profile is a snap. More maps are supported: US, Canada, Europe and World Milestone caches are now identified (not just the dates). You can make corrections if they were logged out of order Other features - browse your list of finds, easily find caches that you have logged multiple times, set a date for your goal, add custom categories for your favorites list, show caches by location and remove locations that may not be applicable (e.g. travelling caches), show changes since last gpx file, and more. Thanks to everyone who sent suggestions (sorry if your suggestion didn't make it into this release) and thanks to GlobalRat for help on the World maps. If you have more suggestions or run into problems, feel free to post here or send an email using the link on the logicweave website.

Sorry for the late reply, I haven't been monitoring the forums. The most likely problem is that you are saving the .gpx file using EasyGPS. EasyGPS strips out most of the important statistical information when it saves the .gpx file. When you open the zip file attachment in your email, simply extract or copy the file to the folder of your choice - don't start EasyGPS (i.e. don't double click on it). This should solve the problem, but if not, let me know. The next release will detect EasyGPS files and put up a more informative error message.

Could be due to the problem Clyde mentions in previous post, which apparently has been solved now. To address the missing found-it log problem and a few other issues, I released version 1.1 a couple of days ago which has the following fixes: - use current day's date instead of 1/1/2000 for caches that are missing found it logs - display warning if there are caches that have missing found it logs - longest streak with/without find not shown if streak still in progress - fix New Hampshire not being reported correctly - change wording of "event temps" to "multiple finds per cache" This is just a minor release (no new features yet) so you don't need to rush out and get it unless you are experiencing a problem listed above. If you do decide to install, it will automatically install over your existing version (in other words, you don't need to remove it first via add/remove programs).

No, that's my fault. That's the default date that is loaded for a cache and if there is no "found it" log for a cache, it never gets changed. I'll put out an update soon that handles this situation a little more gracefully. It sure looks like a problem with pocket queries to me. I don't expect Groundspeak is monitoring this thread, but if so could someone from Groundspeak please look into why the log section of the gpx file is sometimes empty in the my finds PQ?

In answer to the last 2 posts - There seems to be a problem with some pocket queries in that the cache is included in the pocket query, but not your log entry. So CacheStats counts the cache in the unique caches visited, but since there was no log the # of found logs will be wrong. When there is no log, it uses 1/1/2000. You can see which cache(s) are affected by clicking on the Favorites button - they will be at the top of the list. I'll try to handle this situation better in the next release. I'm guessing that this happens when generating a pocket query immediately or soon after logging finds, but I don't know for sure. Would appreciate it if someone could confirm this and let me know whether the next pocket query had it correct. For those that this has happened to, how soon after posting the find did you generate the PQ?

In addition to Parents of Sam's tip, I mention a couple ways to do this in post #26 of this topic: http://forums.Groundspeak.com/GC/index.php...dpost&p=2276536 - D

Just tried it myself and it worked (I'm using an older version of GSAK, 6.6.0). The key settings in the screen shot above are "limit number of logs to export: 0" and "always include my logs". CacheStats will stop loading as soon as it sees logs for different cachers since it doesn't know which one you want to gather statistics for.

CacheStats doesn't include locationless caches in the states-cached list, or at least it shouldn't be. If you find one that is included, please let me know which cache - perhaps there is a bug. To remove a state, you will have to remove it from your pasted HTML - once in the list of states, and once in the URL to world66 which generates the map. That URL ends with something like this: ...statemap?visited=COWIMIILUTINOHPAWVMD Each pair of letters designates a state. You will have to remove the 2 letter code of the state you no longer want to show. Hope this helps. Doug