Search the Community

That variable is subjective and varies from one person to the next. The models I listed can commonly be purchased for as little as $200 USD. The Oregon 7x0 series is beyond cost effective. It is quite a bargain and easily the best bang for your buck when it comes to GCLive equipped Garmin GPSr.

How do you search caches (or filter them) based on favorite point percentage (not total numbers of favorite points)? I have discovered that some of the best caches do NOT have the highest total number of favorite points, but DO have the highest favorite point percentage. For example, a cache that has been around since 2011 (10 years old) and has 200 favorites is probably pretty good, but may only have a percentage of 20% because 1,000 people have found it and only 1 in 5 have given it a favorite, yet it shows up in searches by favorite points. However, a cache that has only been around since 2020 (less than a year) with 40 favorites is amazing, favorited by almost everyone who has found it (say 90%), but doesn’t stand out in favorite searches because it has far fewer total favorites than much older caches. Is there a way to search by favorite points percentage to remove the cache age filter bias that total favorite points provides? If not, how do we get Groundspeak to add that feature?

Update: In order to test my idea and revive my caching in my home area, I have been revisiting over 200 caches during 2020! I do that with the rules that I have set up for myself: Must be at least 2 years since original find. Mysts and multis should be solved again. Only once per cache (or maybe after another 2 years, but that is irrelevant now). All revisits are properly recorded in a revisit history. Conclusion: In most cases, it feels like new! Caches are moved, vegetation has changed, I have often forgotten about the hiding place and/or the surroundings (especially when 7-8 years have passed). And I gave myself over 200 extra reasons to go out caching, often including cycling or walking long enough to be decent exercise. My own home area is suddenly fresh and new to explore as caching area. And I can do caching without travelling long distances to find ones I havn't logged.

My list was entirely revised during the year. The mega was cancelled, and I was not allowed to make the bathing event either. My archiving was modest, way lower than intended. Like the easy and unpopular tree climbing cache that I just liked too much to archive. So the intended 50 was more like 10. I better repeat that goal. But I did fulfill the goal of not letting any cache be archived by a reviewer. The last goal, caching more for exercise, was fulfilled far beyond my ambition, since I decided to start revisiting caches (logged 2 years back or more) on a regular basis. I have revisited more than 200 caches and it was very valuable for reviving my caching! Most were just like going to a new one, since they very often had changed over time. But I also put up two more goals later during the year, closely related: Reach 16% FPs. This meant archiving a few bad ones and publishing ambitious ones. (16% is not very high but a level I could reasonably hope for.) Beat the two biggest COs in Sweden on number of FPs. (This is questionable since it means comparing few with relatively much work put into them to mass-placement but it felt tempting.) This also means getting triple diamond on the "favorited owner" badge. Both were fulfilled. Of course this was very much a question of hoping for visitors to like my caches and waiting for some positive effect, but also about maintenance and keeping a high level on new caches. I have started making my caches with my 3D printer, initially with designs off the web but then moving mostly into custom designs, typically thematic. Some went very well, and they are definitely different from all the petlings and film canisters.

Height and Width attributes (but nor for example Advisory title) are lost when reediting a TB page. Recreate by this flow. Attaching some images for this recreation flow, steps marked with *). - Go to a TB page with an image in its description - Edit the TB page - Right click and image in the description and select Image Properties - Set width and/or height, (for example Height: 200) *) - "OK" to accept changes to image - "Submit Changes" to save the TB page edits - "Visit the Trackables Page" to view the changes. (Images has height 200) *) - Edit the TB page. - The image in the description is not any longer with height 200 (shown in original size). - Right click image and select Image Properties to verify that width and heigth attributes are lost. *) Testing done on first image on https://coord.info/TB4XD0E, the rest of the images had height/width which now are lost.

1210 days lonely, the longest per the script output. When I look at the +400 days caches in this output, I suspect many were simply missing for a long time before they got archived. This is not exactly an achievement on my part. A function of where I cache, I qualify at 100, 200, 300 and 400 days. This is about rarely sought, and poorly maintained paddle caches and multis. If no one hunts them, no one DNFs them and they ride the site for years before finally going away.

I posted this in the "Goals for 2021" thread, but will repost as an update in this "Goals for 2020" thread as well: Get my total find count to 2020. My goal for 2019 was to reach 2000 finds; I'm still over 200 away from that goal, and maybe 2020 in 2020 is attainable! I'm at 2050 finds right now, and 50 of those are from 10 Adventure Labs completed. Even without the AL's, I'm right at 2000 now, so this goal is done (unless I decide to go for 2020 finds! That means I need 20 more. Not sure I will accomplish that) Find a cache on Feb. 29 to finish my calendar grid. We filled every day in 2018 except for Feb. 29, and this will be our first opportunity to fill that day since we began geocaching in 2017. Done - we attended an event, found caches, and I even nabbed a FTF for this day! Host an event. We've attended events, but never hosted one. I applied for one of the Celebration events - we'll see if that comes through. I did get one of the Celebration Events, but unfortunately we are still unable to host events like that (there have been a couple of CITO events nearby). I'd still like to host an event, someday. Hide 12 more caches. Same goal as 2019, and I only got 6 hidden then. I'll go for 12 again! I'm not going to make this one - I've hidden 3 this year, plus 1 Adventure Lab, so that's 4 (or 8 depending on how you count it). Either way, I'm short of my goal of 12. Complete at least one Adventure Lab Cache. A few have popped up in reasonable driving distance, and I'm curious to see how it goes. I enjoy Wherigo caches, when they work! Done! I did 10 of these, and also created one that I was awarded.

Another page, left open all day. In the last minute, it went from 38 to 100 to 200 MB (!) simply by me scrolling a bit, up-and-down with the scroll-wheel click for smooth scrolling, entirely within the (moderately long-winded) cache description, and pointedly above the logs area which are loaded dynamically. (They were already fully loaded a while ago.) Stand back, she's gonna blow! 275. Yesterday I tried to diagnose this with the inspector, but trying to display a report (can't remember which) triggered a runaway page-file top-up, which I aborted just before the file filled (7GB of 8), and I aborted quickly, well as quickly as possible given the duress. Not sure how Linux handles a full page file; no app has ever taken me that high... PgDn, PgUp. 356. Anything I should look for in the inspector? This is incredibly repeatable. (Or are you sick of hearing from me?) 363. PgDn, PgUp. 450 MB. Aborting.

200 finds in 10 minutes. Maybe a time-stopping machine as well

Hello, It looks like you have done some machine translation on the Finnish language version of geocaching.com website. The most blatant errors are on the page Profile - (My) statistics,. but the errors seem to repeat all over the place. The new translations are incorrect, unprofessional, way below your previous high standard, and confusing. Can you please revert back to the old Finnish translations as soon as possible? The problems are: Incorrect translations for the word 'cache' (examples below) Multiple incorrect and misleading translations (e.g. for find stats and for the different cache types) (examples below) Incorrectly conjugated words (examples below) Mismatched conjugations, adjective-noun agreements and English langauge prepositions mixed in. 1. Incorrectly translated 'cache" The word Cache translates in Finnish as 'kätkö' (a hide) or geokätkö, instead of 'kontti' (a Docker container, or an ocean container, meaning the standardized transportation container) or a 'välimuisti' (the temporary cache file on your computer). Currently the profile page has interesting translations such as "Olet löytänyt 3500 välimuistia ensimmäisestä välimuistihakuistasi 08.04.20XX" . (=You have discovered 3500 temporary files since your first temporary file search 08.04.20XX.) or Löytämäni konttityypit = The types of ocean containers I have found. 2. Multiple incorrect translations The profile part describing the streaks, slumps, best days, etc. is now unreadable. Etsi hinta --> translates as "Find price" and is misleading. What price am I supposed to find? 1.1089 välimuistia / päivä --> translates as (xx temporary cache files / day) Pisin juova --> Now translates as "Longest stripe" and is meaningless 32 peräkkäistä päivää löytöillä 13.07.2017 - 13.08.2017 --> The word löytö is now incorrectly conjugated. Pisin romahdus --> Now translates as "Longest collapse" and is meaningless 361 peräkkäistä päivää ilman löytöä 17.04.2012 - 13.04.2013 Nykyinen juova --> Now translates as "Current stripe" and is meaningless 2 peräkkäistä päivää löytöillä 28.11.2020 lähtien Nykyinen romahdus --> Now translates as "Current collapse" and is meaningless. 0 peräkkäistä päivää ilman löytöä The profile part describing the finds nearest/farthest from home has multiple incorrect translations. E.g. "Löydä Kaukin itä (pääministeriltä)" now translates as "Find *remoteist (from the prime minister)" 3. Incorrect conjugations, mismatched conjugations, etc. The following serve as examples: 200 kätköt marraskuu of 2016 --> "Kätköt" is ungrammatical, should be "kätköä", and what's the English preposition "of" doing here? 2 peräkkäistä päivää löytöillä 28.11.2020 lähtien --> "Löytöillä" for the noun "löytö" is not grammatical. Cumulative finds per month --"Kumulatiiviset löydöt kuukaudessa" has mismatched adjective-noun agreement There are multiple other examples on this page, but currently the same problems seem to repeat on other Finnish language pages as well. As said, this is way below your (up until now) fluent everyday Finnish language. Please revert to the old translations, or have someone re-translate the pages properly using the old translations as reference. Thanks already in advance!

What I don't get is the need to put symbols there in the first place we all know the format by know I reckon without degrees and minutes symbols i.e. N51 23.200 W 1 42.000. Keep it simple and problems like this just will not happen.

Oregon 700 is fine if you dont want the camera, and is available for closer to $200 USD. A new Oregon is, as far as I can determine, at least a year or two away.

I like the idea. We just need someone who writes the virtual category and we have to think about the options we offer. I like option 2 (very unique ones and maybe super large ones about 200 items), I see no problem to combine these two criterias as long as the description state it clear.

GPSr prices have gone up, and it's getting harder to find something under $200 that isn't the Etrex 10... Oregon 700 or GPSMAP 64s is a good choice but around $250... Or upgrade your current phone to something like the Moto G8 or an Iphone 7, which is around $200 but accurate as any GPSr on the market. You'll get a much nicer cellphone that fully works with geocaching.

As it is a milestone for me I thought that it is time to update my stats. I now have 200 First-Category-Post-in-a-Country waymarks (Copyright by fi67 ). That's more than double of what I had 3 years ago. Also, due to our travels of the last few years, the number of different countries has increased from 9 to 15. The 200 waymarks per country: Austria - 113 Albania - 6 Bosnia and Herzegovina - 4 Croatia - 2 Hungary - 1 Italy - 1 Monaco - 14 Montenegro - 2 North Macedonia - 21 Norway - 2 Poland - 1 Serbia - 19 Slovakia - 4 Slovenia - 1 Sweden - 9 With these 200 waymarks I covered 183 different categories, which means that there are a few categories, where I have the first waymark in different countries. For example, I have the first "Official Local Tourism Attractions" waymark in Bosnia & Herzegovina, North Macedonia and Serbia.

Hi, I know this question gets asked a lot but I'm looking for recommendations on a GPS to use for geocaching. I'm still mostly new to this and used to use my phone but recently had to switch to a cheap $50 Samsung and it gets cranky and freezes a lot so geocaching wouldn't be the best for it. I don't ha routerloginve much money and I'm looking for something hopefully less than $200. Thanks in advance for any help y'all can provide. 192.168.0.1

Ich will jetzt da nicht der Naturschädigung das Wort reden -. aber was Du da schilderst, ist harmlos. Vielleicht sogar nützlich. Da gibts andere Dinge, die man meiden sollte. Zum Beispiel Astlöcher. Oder andere Löcher, die oft Unterschlupfe sind. Oder bergseitige Böschungen. Oder oder oder. Aber am wichtigsten ist, sich Gedanken zu machen. Auch über den Effekt, ob man nicht massenweise Leute herlockt (im Normalfall ist das ausserhalb von Schnellgreifrunden und 3 km weg vom Parkplatz eher nicht der Fall). Und dass es sinnvoll ist, Caches so zu verstecken, dass Cacher die einfach finden - was (von Versteckideen mit Mehrwert abgesehen) sowieso die Regel sein sollte. Aber die Challange, Caches naturverträglich zu verstecken bzw. die damit verbundenen Effekte zu minimieren, ist eine interne - wenn auch höchst lobenswerte - Challenge. Da sind wir bei bei den schlimmsten beim Grad 3 auf der Skala - der Forst und andere Naturnutzungen bei gefühlten 200 - jeden Tag. Das muss man auch einordnen. Höchsten Anspruch nach innen - realistische Betrachtungsweisen nach aussen. Gruss Zappo

It's because the Wherigo Foundation site is an alternate listing service. It was supposed to demonstrate to Groundspeak what we were intending to do with Wherigo so we could run Wherigo for Groundspeak, free of charge for everyone involved. The other Wherigo player apps and builders are on Groundspeak's ban list because of the same reason: they're an alternate to something else--their PocketPC app and their builder, respectively. Though I worked to get community work officially recognized, those at the top of Groundspeak never communicated any of their verbal support to those enforcing Groundspeak's guidelines. Throughout Wherigo's lifetime, regardless of individual intentions at the company, Groundspeak's apparent attitude has always felt one of apathy and passive hostility towards anyone attempting to make their product more accessible to the community. I coined the term "the Wherigo Foundation is Fight Club". They've always told their reviewers not to allow any mention of the Wherigo Foundation or other non-Groundspeak Wherigo applications in cache listings. It's just that the reviewers aren't consistent with each other that caches in some areas were published and others not. Part of the partnership agreement I was reviewing did state that, if the Wherigo Foundation site were to be discontinued, all cartridge files would be provided to Groundspeak for dispersal to community members. I was planning to do that, anyway, so that was fine. There was one other clause I haven't before talked openly about. Suffice it to say, the way I interpreted it, if I ever walked away from Wherigo and did not transition its running to others, the entire game would come to an end. I did not like that Wherigo would then seem to rely on one person's continued health, existence, and interest. The partnership agreement never panned out because Groundspeak took too long in replying, which further showed their apathy (I'd say nine months, several times, classifies as too long, regardless of how patient you are--while waiting for one such reply, I had a house built and moved into it). An odd quirk to all this is this Wherigo forum. Why can we openly talk about these applications? The answer is a combination of me and Groundspeak's apathy. Back when matejcik and charlenni first presented their applications, the forum rule was that moderators needed to clear through Groundspeak talk of new applications. So, as the moderator, I hid the threads and sought approval. Groundspeak did not reply for a month, so I unhid the thread. When that second application was announced, I hid the thread again and asked Groundspeak. I again didn't hear a reply and unhid the thread. Later, I did get a reply, saying it was fine and that there wasn't anyone at Groundspeak who could speak for authorizing these, so that's why it took so long. I asked, then, for something no other moderator has: the authority to make these decisions on my own. It was granted. Ever since then, so long as something wasn't commercial, I allowed it. Now, mind you, Groundspeak's employees have definitely changed since then, so no one there remembers that this responsibility was delegated, so would likely take it away. Another odd footnote is Wherigo\\kit. I am able to use Groundspeak's API for authentication, which does require approval and a review. More recently, when I had to submit an updated overview of this application, I was asked by someone at Groundspeak if I wanted Kit to appear in the list of official Groundspeak partners. I guffawed, pointing out that Groundspeak's reviewers do not allow caches to be published if they mention Kit, the Wherigo Foundation, or any other application, so listing Kit as an official Groundspeak partner would thoroughly confuse the situation, so Groundspeak should really consider its stance on the matter. This was about two years ago. Finally, something that irritates me. Groundspeak allows cachers to mention GSAK and Project GC in their cache listings. Both are commercial applications--GSAK was up until recently and Project GC pushes a subscription model. Groundspeak also allows mention of other commercial applications in cache listings. But, yet, when it comes to everything the community has done to help Groundspeak with Wherigo--and everything we have has always been free, with the individual developer shouldering 100% of the continued cost--Groundspeak has this as their official position. And, believe me, there are ongoing costs. I average about $200/month for hosting, storage, SSL/TLS license, and domain registrations between Kit, the Wherigo Foundation site, DevOps/TFS, and the staging areas I use when publishing. I could decrease the cost by doing a shared hosting plan, I suppose. I suppose I could have still continued to create things. But there comes a time when one needs a solid support group to provide feedback and motivation. I don't have that. And you'd figure people in my own area would be really supportive of my endeavors, be it Wherigo or having found almost 95K caches. They're not. There's a distinct anti-Wherigo feeling in my area. There have been some that would like it if I quit geocaching altogether. So, no support there. One can continue only so long against the flow and apathy before exhausting oneself. So, later, my job became the beneficiary of some of my free time. I worked uncompensated overtime 300 hours last year and 400 hours this year (and no time off). You'd think they'd be grateful, but instead I get managers telling me they're not asking me to work extra hours and they're apathetic about all the things I'm doing to fix their aging application single-handedly. No encouragement, no support, no appreciation from there. Sigh. So, anyway, that's my view on the matter. There are always other sides to it, though I've tried to be neutral.

The same user apparently visited two of my waymarks 200 km apart. Both without pictures. The first one stated that he/die walked by it, the second one simply "and another". I deleted the second visit.

One of my favorite caches had lat/long coordinates that would take you to a strip mall parking lot. There were quite a DNF logs which said that they search in the obvious spot (a light pole skirt...I know that you don't have them in the U.K.). Although the listing didn't include elevation, there were clues in the listing which suggested that it was not in the parking log, but under the parking lot. About 200' from the published coordinates was an entrance to a tunnel under the parking lot and a mostly dry creek bed. The surface of the earth was actually under the parking lot. There was also a heavily favorited cache in German that required one to get into an elevator (which also had room for a car) which took you down to a tunnel that went under a river. If one looked at an satellite map with the lat/long coordinates it would appear that the cache was in the middle of the river, instead of in the tunnel about half way through. Since elevation is not included in geocache metadata, the terrain rating can be used to give seekers a clue to where the container is hidden. For that cache in Germany, the fact that it didn't have a T5 rating indicated that it was not *in* the river and would require special equipment.

Wondering if anyone in the St. Louis area would mind hunting down a TB from a recently archived cache? It may not even be there, as it may have been muggled right before the cache was archived. Not sure. Cache is (was) the TB Chateau at GCRDJD. TB is TB7797W. She's travelled more than 20,000 miles from Missouri all the way to Hawaii and back, up through the east coast, only to make it within 200 miles of her goal to get back home to us before this happened. We'd love to see her again. She's a seahorse travelling with a froggy friend on the same chain. We know it's a long shot, but if there's even a slim chance that she might be able to make it home, we have to try!! Thanks!!

Fair enough. But there are limits to this when it just gets annoying too - I tend to have a common sentence or two/three for sections of a day or the day, depending on what we're doing. Then a unique sentence or ten for each find (depending on the find). Sometimes you see logs where someone on a trip writes out a full essay about the whole week or two, and that becomes the log for the 200 finds during that time, that's a definite irk....

I still don't understand it. How do you loop your AVERAGE? Do you loop it if the average is at least 200 words? I also aksed one guy why he does that nonsense. He even said that he might think about changig his way of logging. Sadly, but not surprisingly, he still logs the same way with impolite and inappropriate logs.

For statistical analysis - I started this thread 6 days ago. On that day I reached out to 15 finders of 8 of my ECs about not logging caches. Of those, 5 have gotten back to me. Of those 5, four were veteran players who either 1) forgot to send the email or 2) their email went to my spam folder on accident. The last was a newbie who responded to my email with "hi no." So of 15 players reached out to, 4/15 have supplied answers of 9/15 have not and 0/9 newbies* have responded to the messages with answers. *a self defined term based on number of caches and specifically earthcaches found, typically less than 200/5 split.

That's semantics, but it's hard to argue that averaging is not beneficial to improving accuracy. Let's run a simulation as an example. Take a random number. Say 57 value = 57 We have a hypothetical GPS device that isn't very accurate. In fact, that device can only tell you the coordinates to value within 50 places. It will return a value randomly anywhere between 7 and 107. Not very accurate at all. Now, let's take 200 random readings of "value" where the results can wildly range from 7 to 107 and average them together. If we run this simulation multiple times (just for fun!)... 57.020301980532984 56.60828961934022 58.36645537356805 Now, let's take a "precision" device. that gives us coordinates to within 15 feet and grab a single value that we think looks accurate. 70 66 52 My personal experience shows GPS averaging gives more accurate coordinates than trying to pick out a single reading. Is it possible that a single reading can be more accurate than the average? Yes, it can, but most of the time, it probably won't be as good as an average of many samples taken.