Search the Community

Ja, leider. Die D/T-Matrix 27* füllen oder 365 Tage am Stück cachen (was für alte Hasen die schon alles in der Gegend gefunden haben eine fürchterliche Ressourcenverschwendung darstellt) ist erlaubt, kreative Lösungen die den Grips anstrengen sollen sind verboten.

Let me offer a recently reincarnated challenge trail we put out around here. A few pre-moratorium caches are in it but most are under the new guidelines. The goal was to make interesting ones under the new guidelines. Feel free to crib ideas as some of these were cribbed from other creative folks. GC3F12D Neglected Cache Challenge GC55XPN The Bigcall Challenge: A Baker's Dozen GC55XP0 The Bigcall Challenge: Nifty Fifty GC980EH 365 Unknown Dates Hidden Challenge GC980EK Feet Under the Sea, Head In the Clouds Challenge GC980EJ All The Attributes Challenge GC9838K The Golden State Challenge GC9839B The Best Finds Challenge GC9838Z The Perfect Country & Western Song Challenge GC9834G Globetrotter Challenge GC9834D The Island Life Is For Me Challenge GC9838F Virtual 👻 Border to Border Challenge GC98388 5 states*100 Finds Iconic Challenge GC9838P Iconic Traveler Challenge GC9834N Every Day Hidden Challenge GC98396 The Bay Area Puzzlers Challenge GC98393 The Taking a Long Lunch Challenge GC98341 Largest Counties Challenge GC9839N Road Less Traveled Challenge! GC9833X Wherigo Quarter Century Challenge GC98347 So Easy a Child Could Do It Challenge GC9838D It's Five O'Clock Somewhere Challenge GC995K7 Mysteries Across The USA Challenge GC995K2 5 Types x 10 States Challenge GC99842 Historic Alameda County Caches Challenge GC99A3G The Demented Diminishing Dozen Challenge GC99AD4 1000 km Altitude Challenge GC99ACQ The Blue or the Gray Challenge GC9986G Hazards of Geocaching Attributes CHALLENGE 313 GC9986J Accessible Attainable Attributes CHALLENGE 1313 GC99X8B The Lazy Cacher Challenge GC9A2N2 The Good N.E.W.S. or Bad N.E.W.S. Challenge GC99EMN The 3.5 Billion Year Challenge GC99AE7 Well-Traveled Cacher: Degree Squares

Was ist denn mit type of log genau gemeint? Ich habe z.B. mal einen Challenge gesehen, da musste man 20 Logs haben, wo im Cache-Namen das Wort Hütte vorkam (Zwillbrocker Venn). Ein Arche-Noah-Cache (Hamm oder Unna) verlangt von den Loggern, dass sie 40 Caches mit Tiernamen geloggt haben (ohne dass sich ein Tier wiederholt bzw. GCSchwein, GCEber, GCSau, GCFerkel als vier Tiere gewertet werden. Manche verlangen, dass man an allen 365/6 Kalendertagen je mindestens einen Cache (oder vielleicht sogar in einer verschärften Version je einen Multi oder Mystery) geloggt haben muss. Es gibt jede Menge Challenge-Caches mit teils absurden, teils interessanten Anforderungen an die Community (wobei sich absurd und interessant nicht gegenseitig ausschließen müssen).

Found a lot of challenge caches a while ago. Some of them I qualified immidiatly and I could log them as found. And for some of them I logged at the cache and logged a write note online. Later, all of them were archived without written down a reason, just a small note were it looked like the CO was annoyed by the situation. Today, finally, after a long time, I qualified for a challenge I had logged before. 365 days of the calender full with a found of a traditional. And now I wanted to log it as found, or change my write note in a found, but now it seems to be locked. I can't find a way to log it now, even when I think I am allowed according the rules. Is there a new rule that archived challenges are not allowed to log? Or was there a situation with the CO all geocaches that found a cache are now suffering from? Why isn't there a note that explains this situation?? The cache I wanted to log is http://coord.info/ GC8JG9W

Right, it’s not like an urgent and stressful activity... that’s why I really like it! I’m trying to get 365 caches this year though so I can say that I got one cache everyday for a year! So maybe I’ve got a little stress but it’s definitely a type of stress that I like

Someone let me know I was mentioned in this topic. If you have any questions, I'll answer them. Here are some answers to start out with: I started a streak just because I noticed I had found caches each day of the month, save for the first where I DNFed one and didn't find another. Before then, I believe my longest was 28 days. I wondered for how long I could keep it up, so decided to see. This was before I heard of the term "streak". I called it "cache-a-day". I'm single, don't have a family, never dated, and don't have much of a social life. I feel most people wonder how a streak is possible because they're thinking in that context. That's not to say I don't have my own challenges. For example, during haunted attraction season, I work 7AM - 4:30 PM, cache 5PM - 6PM, shoot a haunt 6:30PM - 1:30AM, and edit photos 2AM - 4AM. If a convenient cache to a haunt is published in February, I just don't find it until October that year or the next or the year after. It's that simple. When I worked basketball games and tournaments, I usually finished around 9:30PM, so I'd find a cache somewhat convenient after that. There was one time I had to work until 2AM with the team. I took a slightly longer supper and found a convenient cache I was saving. If it's forecast to snow, I'll drive somewhere and sit in the car until after midnight before I get out and look for the cache (were I to see the cache from the car, I'd have to count it at the time I saw it). So I do have my challenges. These days, the streak has a few purposes: force myself to get out and do something and make sure I continue to play the game. For me, geocaching is synonymous to going out every day and finding something (since, even before the streak, I never missed too many days). I could do a streak at first because it fit with my original rule: leave caches to find on a rainy day. I believed caching out my area was a failure because I wouldn't have anything left to do if I wanted to find something and either not drive far or the weather was bad. On average, I spend one to two hours every day to find one cache due to driving. I likely have around fifty to a hundred convenient caches I could find and not spend too long. However, those must be saved for a rainy day--in other words, when I either don't have time, don't want to spend the time, or there's bad weather. Every now and then, I have really annoying days where I DNF three to five caches in a row because I attempt to look for neglected caches. When that happens, I just want to find something to be done and over with it. But I don't see the streak as a burden because it's forcing me to get outside and do something other than work. So even when I'm frustrated about that and just want to have a relaxed evening and do nothing, I know what I'm actually doing is good for me. I can get upset all I want, but it's good medicine, both for physical and mental health, so it must be taken. I've never traveled across an ocean, so I've no need of my personal rule about that. However, I created that rule to be fair. I want my rule set to be as hard, demanding, and constraining as possible, but fair. I don't hold anyone to anything because I don't care about anyone else's streak. (To impress me, tell me a story.) Remember, I'm doing this to force myself to get outside and continue being involved in this game, so I see the streak as part of my internal game-playing infrastructure--a means to an end. Its value lies in what it does for me, not in its being an achievement. Besides, there is someone in my area who wants to garner acknowledgement and praise for his streak. I'll let him have that since he needs something to make him feel good. He can keep up with the day numbers. I can barely find the motivation to set aside time once a week or two or three to slog through the process of logging the finds. Forget the streak: I'm impressed people can consistently log caches on the same day they found them. By the time I'm done finding caches for a day, I'm done with caching. I will not ever have a logging streak. I came up with my rule set by talking to people and finding out what their rules and beliefs were. If they came up with a sensible rule more restrictive than mine, I'd adopt it. I'm bored enough that I want to play on hard mode. That part about its being a physical cache came from this. Later, someone suggested I write out all these rules I had acquired for myself. I shrugged and said perhaps, some day, I would. There was a time my area didn't even average 365 caches published a year. That was hard. It used to be some 1000/year, I'd guess. These past four or five years have been skimpy. I get by. Do I want to stop the streak? Well, there's a reason I'm doing this, so the answer would be if I wanted to stop forcing myself to leave work and go somewhere every evening. No, I believe it's healthy to force oneself to disengage from things and just to do something relaxing for an hour or so every day even if you don't think you have time to do so. I hope this answers some questions. Though I'm slow to reply to topics outside the Wherigo forum, I'll reply if anyone asks something. I hope I can either help or inspire someone if you really want to do something like this. Other than that, a streak is nothing but simple strategy. It's not that difficult to pull off in a somewhat active area--that's the part you can't control. But I do feel like most people will fail if all you're getting out of it is a number of days for a streak. Since there's a personal point to mine, I feel it's easier to do even on days when I want to be downright lazy.

SPOT devices are hardly similar to Garmin inReach devices. SPOT devices offer the user a one-way outgoing emergency distress call option, that once initiated, the user can only hope and/or assume was received and help is on the way, and the emergency responders have no way ascertaining any information related to the nature of the distress call. Garmin inReach devices, which the Montana 700i and 750i are, offer bi-directional communication 24 hrs a day, 7 days a week, 365 days a year. Garmin inReach devices allow the user to transmit pertinent information to the responding crew while receiving instructions that can help save lives while keeping everyone on the same page, in real time. Garmin inReach devices allow users to automatically send a bread-crumb trail of there location to the cloud where friends, family members and other authorized individuals can keep track of their location and progress, in real time, without requiring any other action on the users part. Garmin inReach devices allow users to communicate bi-directionally with the entire outside world via direct messaging, sms, and email. This means you can not only send regular detailed updates to family and friends to reassure them of your condition or any specific needs, or changes in schedule etc, but so can they send you the same types of information, available directly on your inReach device, anywhere in the world, 24/7/365. Garmin inReach devices can provide the user with highly detailed hour by hour weather forecasts for any location on Earth, from any location on Earth, at any time desired, 24/7/365, assisting the user in adapting their trip in such a way they can avoid inclement weather conditions that may otherwise leave someone stranded and/or worse. Garmin inReach devices also allow users to post timely updates about their trip to their Facebook and Twitter accounts, 24/7/365. Remember, with a SPOT, you just push a button, and then wait, hoping the signal went out and was received and someone is on the way. With a Garmin inReach device, you are always in contact with the entire world, from anywhere in the world, so you and your loved one never have to wonder or guess about your status.

Yep! And this is another reason for some of the post-moratorium guidelines on what constitutes an acceptable and/or reasonable challenge. When it comes to streaks they capped it at 1 year without requiring Feb 29. To HQ, I suppose after polling reviewers and observing general community, one year was determined the maximum reasonable period to have to 'start over' if necessary. But if I recall, that length for streaking is only allowed for general find counts, not with additional parameters, like 1 year of a specific cache type, eg. All this is laid out in the guidelines for challenge caches, and the reasons they chose the rules they did (with examples). If I was going for a one year streak, and I really wanted it, I might consider starting over if I missed a day; mainly because there are still thousands for me to find within an hour drive. But those 555, 1000, or higher streak challenges - those were one-attempts. They're in my "too hard, won't finish" List. Might find it and sign (because hey, geocache), but almost certainly won't ever qualify. And those are the ones that HQ doesn't want to allow published any more, for that very reason. Too many people simply don't want to do or find it. My streak cap was an intentional 366 consecutive unique days (Mar 1 - Feb 29) and I'm happy with that. Anyway, this has drifted to challenges - and those are what I'd call "statistical streaks". Regardless of logging ethic, it's a pure number analysis. One person's 365-day streak qualification may have been much easier than another person's, if their logging ethics were vastly different. Direct/competitive comparison will benefit no one in those cases. The person who did it more strictly can't/shouldn't say the other objectively "cheated" because (assuming all logs are fundamentally valid) they didn't. They just accomplished the same challenge goal a different way.

Do adventure lab caches count for streaks? They work for filling up yout 365 days matrix (not on project-gc.com but on the geocaching.com website) so they should work for streaks, too? If so they might help with honest streaks if you only do one lab cache at a time. You do not have to complete the full adventure to score the daily find. There is another way for a non-honest streak no one has mentioned so far. Look out for caches with an inactive owner and simply log those. No danger of your log being deleted. I've heard of cachers that found logged caches with an old date soon after they disppeared and deactivated. What a coincidence, the lobbook has been stolen? They found it only two days before it vanished or can someone proof the contrary? That's another way for an easy find if you have missed a day. Jochen

There is a guideline, which says that a challenge must be attainable be enough local cachers (whatever "local" means in that context). So a 365-day-streak challenge somewhere far away from any cache-dense area should not be published.

Challenge Caches cannot require Lab cache finds, but challengers can choose to use them towards qualifications, if they are allowed. For example, "find 1,000 caches" or "maintain a 365-day streak."

Atualização mensal da atividade geocaching no Brasil (1 de janeiro de 2021) Total de caches publicadas 7842* Não arquivadas 5118 Caches sem nenhum Found 749 das quais 368 já foram arquivadas ou despublicadas Caches aguardando FTF 365 Caches com 5 Founds ou menos 3908 Caches com 6 a 10 Founds 1550 Caches com 11 a 50 Founds 1830 Caches com 51 a 100 Founds 169 Caches com mais de 100 Founds 216 Total de Founds 119148 Cache com mais Founds 928 - Frederico Engel Caches com Favoritos 1952 sendo que 280 já estão arquivadas Caches até 5 Favoritos 1728 Caches com 6 a 10 Favoritos 91 Caches com mais de 10 Favoritos 112 Total de Favoritos 6895 Cache com mais Favoritos 495 - Mission 4: Southern Bowl * Estão incluídas as Adventure Labs.

I'm curious, then, because there's a mystery cache with Challenge in the title and a Project-GC challenge checker requiring finds on five caches that have been unfound for 365+ days. It was published today but it doesn't have the Challenge Cache attribute (or any attributes at all for that matter). So is it a challenge cache or just a mystery with an unenforcable ALR?

Atualização mensal da atividade geocaching no Brasil (1 de setembro de 2020) Total de caches publicadas 7700* Não arquivadas 4987 Caches sem nenhum Found 768 das quais 365 já foram arquivadas Caches aguardando FTF 401 Caches com 5 Founds ou menos 3960 Caches com 6 a 10 Founds 1503 Caches com 11 a 50 Founds 1846 Caches com 51 a 100 Founds 176 Caches com mais de 100 Founds 216 Total de Founds 118283 Cache com mais Founds 925 - Frederico Engel Caches com Favoritos 1926 sendo que 280 já estão arquivadas Caches até 5 Favoritos 1721 Caches com 6 a 10 Favoritos 92 Caches com mais de 10 Favoritos 113 Total de Favoritos 6887 Cache com mais Favoritos 494 - Mission 4: Southern Bowl * Estão incluídas as Adventure Labs.

Reading others' online logs made me think of this challenge: Log similarity less than 40(?) %. Another idea could be: Last 365 days averages: Less than 5(?) finds per caching day.

Vielleicht würde es als Option sogar gehen? Longest Streak oder Longest Slump >= 250 Wenn eine Challenge "250 Tage jeden Tag einen Cache" veröffentlicht wird (ich glaube, bis 365 oder 366 ist möglich?), dann sollte das eigentlich genauso erlaubt sein - vielleicht muss man aber auch einen Reviewer finden, der das mit Humor nimmt. Nur die Slump >= 250 würde ich persönlich auch doof finden. Eine Herausforderung ist es auch nicht, eher ein Gag. Ich kann aber mit genug Challenges leben, die ich nicht erfülle - habe da selbst vier Stück im Umkreis von 10 Kilometern.... Von dem her: Die "Corona-Challenge" darf kommen, bitte aber mit genau dem Namen. :-)

I maintain several Lonely Cache bookmark lists for Florida. In the several years I've been doing that, there have been 2000-5000 lonely caches (at least 1 year / 365 days without a logged Find). There is community interest in seeking these, especially when people are made aware of them. It's a very mixed bag: remote hides, limited access, missing caches (lots of DNFs), hard puzzles, long multis. But the majority are fairly normal Traditionals still in place, just a bit out of the way. Often more than one in the same general area. Challenge Caches are what made me aware of the concept. Florida has I think 4 scattered around the state. But I understand Groundspeak's logic as to why they're no longer allowed. Hunting them is often more rewarding than qualifying for a challenge cache or earning a souvenir. Focus on that.

Atualização mensal da atividade geocaching no Brasil (1 de março de 2020) Total de caches publicadas 7579* Não arquivadas 4970 Caches sem nenhum Found 750 das quais 365 já foram arquivadas Caches aguardando FTF 378 Caches com 5 Founds ou menos 3898 Caches com 6 a 10 Founds 1492 Caches com 11 a 50 Founds 1799 Caches com 51 a 100 Founds 177 Caches com mais de 100 Founds 213 Cache com mais Founds 920 - Frederico Engel Caches com Favoritos 1913 sendo que 280 já estão arquivadas Caches até 5 Favoritos 1708 Caches com 6 a 10 Favoritos 92 Caches com mais de 10 Favoritos 113 Cache com mais Favoritos 492 - Mission 4: Southern Bowl * A partir deste mês estarão incluídas as Adventures Lab.

My husband and I began geocaching in March, 2017. We enjoyed it, and set ourselves a goal to find at least one cache a day in 2018. We gave ourselves some rules - it had to be a container we found and signed the log. Events, EC's, Virtuals would not count (even though it would give us the smilie - we wanted to see if we could go out and find a container and sign a log every day of 2018!) All was going well, till we decided on a whim to take a 4 day cruise in October. After booking it and looking things over in more detail, planning for caching on Catalina Island and in Ensenada, Mexico (a new country, yay!), we realized there would be one day at sea, with no place to find a cache! Our "streak" would be at around 300 days, probably something we would never do again as it was a lot of work as the days went by and caches close to home were getting fewer and fewer, and how could we do this, legitimately?? Our solution is similar to what you suggested: ( "I did wonder about 'banking' some earthcaches - visiting the locations, just photographing them in detail and then only answering the questions when I'm out at sea. But that feels like cheating.") We visited an Earthcache where the cruise ship docked in Ensenada, got a few details as we left the ship and gathered more info as we got back on board at the end of the day. Then, did our research and submitted answers while we were at sea the next day, effectively logging it on the "sea day". So, we stretched our own rules about signing the logsheet for a physical cache every day, and we claimed the EC find on the day at sea when we submitted our answers, keeping the streak alive on our stats. Yes, it did feel a bit like cheating, but only ourselves and our own rules. We just delayed logging until we had done our research and submitted our answers, one day. Your situation, doing a lot of cruising as a job with many days at sea with no place to physically find a geocache, probably makes our solution untenable for more than a couple of ports that may have an Earthcache to log. It was our one anomaly in the 400 + days, and stats notwithstanding, we still feel we accomplished what we set out to do in 2018. YMMV Side note: We were able to finish the year, then kept going for another month + a few days for another challenge (400 day streak) - we knew we'd never do it again, so while we were at 365 we just continued on and ended it at 404 (seemed appropriate!)

My previous posts compared consecutive one-year trackable data sets followed for the index year and the following two calendar years. I used this approach to determine if there were discernable differences in survivorship from changes made over the years in either trackable assembly, changing the mission statement, or selectively releasing trackables. It has been made clear that there is little this trackable owner can do to increase longevity beyond using durable materials. The fate of trackables is wholly in the hands their finders. This post, and at least two others to follow, draw from a data set consisting of all my 1,710 trackables released in the five calendar years 2010 through 2014. Their activity was monitored for the next five calendar years, ending 31 Dec 2019. Thus, the youngest trackables would be at least five years old, and the oldest could be near ten, assuming survival. I maintain separate spreadsheets for each series of trackables I have released…poker chips, art, patches, beads, etc. For this project, I pooled all the first-five-year trackables into a single spreadsheet, a portion of which is shown in the figure below. The release date is either when I placed the trackable in a cache or when I handed if off to another cacher…it is when the trackable is released to its fate. The release date is not the same as the activation date, which can occur days or even months earlier. The red column displays the dates subsequent Drops occurred. The E columns are the Elapsed days from the previous drop. The C columns are the Cumulative days from the release date. All of the values in the columns will be summarized in later reports, but this post is focused on the E columns, where we can begin to address questions about trackable movement. First, I must provide some context. The survivorship curve for this 5-10 year data set is shown below. The point to be made is that despite starting with a substantial sample size of 1,710 trackables, only about a quarter of the potential intervals were available to contribute to the data in the table that follows. All the space above the blue columns represents missing trackables, whereas the area defined by the blue columns represents only those trackables that provided information. Thus, every outcome from the data must be prefaced with the words “Among the trackables that survived…” The number of intervals contributed by Individual trackables equals the number of drops and ranged from one to 67 among the trackables, with an average was around 12 drops per trackable. Consulting the bottom of the small table below, we see there were 15,150 drop intervals recorded among the trackables that could be studied. The intervals were measured in days and range from 0 (for consecutive drops occurring on the same day) to one trackable that had an interval over seven years. The table also show that most (66%) consecutive drops were within 2 months (60 days) of each other. Consecutive drops averaging 60 days will yield an outstanding six drops per year, in my opinion. However, I will show in a later post that only a few bugs in Europe have actually maintained that pace. Approximately 31 percent of the intervals fell within the range of two to 12 months, which, combined with the 60-day percentage, shows that 96 percent of the intervals are at less than 365 days (1 year). I will note in passing that a suspicious number of the trackables whose last intervals were above two years were never active again. This suggests that no small number of cachers use phantom drops to remove lost or stolen trackables from their inventories. Therefore, these data go on to suggest that, while not quite probability, if a bug is inactive for more than a year, there is only small chance to continue traveling. Once again, these data are derived solely from my collection of trackables. The extent to which their activity mimics that of the collections of other cachers is unknown. I accept there may well be differences based on regional patterns of husbandry and access to high-traffic caches, but I would bet that any other US-based collection of trackables would produce results very like these.

Yep, and they drew the line at 1 year length. However the streaks are for any cache so it doesn't technically discourage you from finding a specific (property of) cache to save for another day. In a sense, the time period is 1 week instead of 1 year, but these challenges above are much more limited in qualifiers than a find-a-day streak. (acknowledging that some areas don't have over 365 caches in reasonable distance, but that's a different concern for streak challenges themselves) IIRC streak challenges can't be restricted to cache properties, so it's much much less likely that you'll hold off finding a specific cache, to the degree that a cache-property-restricted challenge would. Again I'm just guessing that these are some of the reasonings for the denial, not that I agree with them

Just define it as 365 days streak with option to skip all other days except one thursday.

Yeah I always found strange they allowed 365 days streak challenge but finding a cache on a Wednesday is a big no-no

We have just a debate about attainability. There was an opinion that event caches are not attainable because you may need to wait for a while until the next event. The issue was solved by HQ by allowing events desipite that they are not available 24/7/365.

As GS stated, challenge caches need to be attainable at any time. While there will come a time when the number of webcam caches is less than the number of mega events in a year, the remaining webcam caches will still be attainable 365 days of the year. The mega event lasts a day or two, and is not attainable for 314 days out of the next 365. Heck, even the remaining APE cache is available 365 days of the year. The only thing stopping me from going and finding it on any particular day of the year is me. Which is more rare? It depends on your definition of rare. To me, rare has multiple meanings, and your statement that webcam caches will be rarer than mega events is mixing the meanings. Rare as in few remaining, versus rare as in having limited availability.