rosebud55112

This past Saturday, 9/21, I made a trip across southern Minnesota to watch my daughter at a marching band competition, and of course I grabbed some caches along the way. In total, I found 17 caches on Saturday. When I got home on Sunday and was logging them, I accidentally logged some for Sunday, 9/22, forgetting to properly change the found date. After a bit, I realized I had the incorrect date, and edited the logs to show the right day. So now on my Geocaches tab, I can see all 17 caches as found on 9/21. However, on my statistics tab, it shows me as having only 13 caches found on 9/21 in my career. I had 2 9/21 caches before, and I correctly logged 11 caches (misdating 6), so I understand why the system would originally say 13, but I'm wondering why the stats tab is keeping those last 6 as finds on 9/22 instead of counting them as 9/21 finds? It's not a horrible thing to have those six caches showing up one day off, but it makes the stats tab less trustworthy.

I keep multiple lists, and any given cache may qualify to be on more than one list, which reduces the likelihood of missing something if I forget to download a list. I have a Solved But Unfound list for my home state, and another for outside of that. The home state one is downloaded to my GPSr relatively often. If I am going to travel, I put together a bookmark for that trip (or update a former one if I've made the trip before). This will include the route there if driving. I review the online map and add anything that interests me--ones that will help with challenges; ones with interesting D/T combos; highly favorited caches; etc. I usually wind up wind up with more caches than time to get them, so I don't worry about missing some intersecting caches. I just accept that will happen. I have lists for Challenges I qualify for; Challenges I've signed but don't qualify for, interesting Challenges I want to make progress on, and quite a few others. Overall though, don't worry about the ones you don't get--you'll drive yourself crazy doing that. Enjoy the ones you do getand be pleased with the progress you do make.

It can't be the case that there is a rule that posted coordinates = final coordinates implies Traditional cache. That rule would prevent Challenge caches from being at their posted coordinates, which most are, except perhaps those used in geo-art. K13 made this point above. It can be the case that "if the cache container could be replaced with a simple peanut butter jar and that would definitely be a trad, then the original is a trad" is a rule, but I don't think there's anything spelled out like that. It sounds as though that is the custom in some areas (perhaps even the CO's), but if the CO is being non-customary, that would make it non-traditional, no? In my mind, anything that makes the cache/cache container non-obvious as to how to open it should have the right to be called non-traditional (specifically unknown) left to the CO.

In a self-reported version of Hartman's Law, the above should read "but when it's the 10pm news". Irony noted.

Oh that drives me nuts when they don't run things like this past an editor who knows how to spell. I hate-watch our local news station because they are so bad at this type of thing. I'll give them a break for the occasional truly breaking news item, but when its the 10pm news on something that happened in the middle of the day (and then repeated on the next morning's 6am news!) I scream at the TV

I think this is nice. 24 hours in, and I already know I'm not going to qualify for it, so I don't get that angsty/antsy feeling as time ticks down.

I attended a breakfast event in the morning, then grabbed 5 newly published puzzle caches and one multi cache. Since I'd only had two caches in all of August before that, it was a nice break to a bit of a drought for me.

If we are worried that Joe is the type of person who would host an event just to get another country's souvenir, why are we not worried that Joe is the type of person who would set up a sock puppet account in said country, have that account "hide" a cache in that country, and then Joe can "find" that cache? Personally, I'd rather have an event that no one else showed up to on the map than a completely bogus cache on the map. I'm only affected if I am also in that country on the same day as the event, vs winding up looking for a cache that never existed.

I'd say you're jumping the gun a little bit if you're wondering about 2020 souvenirs, still more than 10 months away, but they actually have announced one, the Hello 2020 souvenir is earned by finding a cache or attending an event on January 1st, 2020. See the site Isonzo Karst linked to above.

I think jennergruhle means something along the lines of "I have put out some cool, creative caches that have already earned lots of favorite points, so people will target them during this promotion. When they find my caches, they will also add favorite points since they deserve them. In this way, I'll earn 25 points from each of these cachers."

Thanks. That's not the answer that I wanted to hear, but I guess it's the answer I get.

There is a set of caches in South Dakota which has all 81 D/T combinations, but I've heard from some people that some of those ratings are not as "precise" as they should be. I haven't tried them out, so not speaking from personal experience.

I have the Android App set up on my phone. When I open (or try to open) a cache on my phone, it defaults to using this app. That's all fine and good for when I'm out caching impromptu, but causes some issues when I'm trying to look at Archived caches. For example, if I look at the Geocaching Puzzle of the Day site, and I see a link to an interesting-sounding puzzle, and tap the link, the app tries to open it. However, if the cache has been archived, I get the GC# for the cache and the message "Invalid code. Please check the code and try again." I can check on my PC that it is the correct code, just an archived cache. Is there any way for me to change some settings so that the app will pull up these archived caches? (Example: 1/23/19--GCNB7Z- name that musical - archived 2/24/10) Thanks!

Oh, I've seen them and they are definitely on my list of targets for next year. I just need some Saturday free enough to head down to that corner of the Cities. I'm definitely interested!

1. Continue working on getting my Non-Traditionals/Total caches ratio up to 50% 2. Add 3+ countries 3. Add 12+ counties 4. Break 300 multi-caches 5. Hide 6+ new puzzle caches

And if it's a ten-year-old thread they're probably not expecting an update.

You may also want to look at GC2AC9K- Liesegang Bands ~ Hard Rock or Golden Oldies?

And then after you go out and find that cache, the smiley face will show up back at the original posted (not corrected) coordinates. This is good for solving geo-art that contains mysteries, but bad for using the map to brute force other mysteries

I've had this problem too, at different zoom levels. Usually zooming in or out fixes it temporarily.

I'm sorry on4bam. As I read my last response now, it seems rather snarky. It wasn't intended that way.

I did mention that. Every sentence in my original post that has a question mark is about how/why the system works the way it does.

Yes, I use GSAK and I know that I can do that. However, I was not at the computer where I have my GSAK data stored, so I went with the search function. My question isn't how do I answer my original question, but why does the Groundspeak search function sometimes return less results than it should, based on input.

I was just curious about how many of the 50 US state names I have accounted for in my finds, so I was using the Play/Search/Filters search function on the site. Since that would be a lot of searching, I set up the filter to be "Caches I've Found", and Geocache Name Contains fields. Trying to save myself some time, instead of entering the entire state name into the GNC field, I would just put in the first three letters. Also saving some time, I thought I'd check for both ND and SD by setting GNC equal to "DAK". My results were two caches I have that each have the word "Dakota" in them, but neither was a "North Dakota" or South Dakota". Fair enough. Then I checked on both NC and SC by making GNC equal to "CAR". I got back five caches, each with the word "car" in them. OK, but then it struck me, that I was pretty sure I did have, in fact both a NC and SC cache. So I set GNC="CARO", and yep, three caches were returned, including a NC and a SC cache. That didn't make any sense to me, but I thought maybe it was due to "CAR" being a common English word so I tried setting GNC equal to "PEN". This search returned a single cache called "Penalty Shot". When I put GNC equal to "PENN", however, I get three cache finds all with the word "Pennsylvania" in them. So why does the three letter search not give all results? The system isn't just looking only for a three-letter word, since DAK brought back 'Dakota' and PEN brought back 'Penalty', but why didn't CAR bring back my 'Carolina's or PEN bring back my 'Pennsylvania's? I realize that the system is only looking at the start of words--no internal strings-- but why were the CAR and PEN searches incomplete?

After I got to 100, it wasn't particularly fun anymore and then my daughter's wedding gave me a good reason to admit that there were other more important things to be doing.

Of course, Mar 14, 2016 made about 12.6 times more sense to be the pi day with the souvenir than Mar 14, 2015 did. And in Europe, they only get to celebrate pi day in years when there are 31 days in April.