Jump to content

Search the Community

Showing results for '길음역청소년출입금지제주출장샵[katalk:ZA32]200%보장 전지역 모두 출장가능'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Geocaching HQ communications
    • Geocaching HQ communications
  • General geocaching discussions
    • How do I...?
    • General geocaching topics
    • Trackables
    • Geocache types and additional GPS-based gameplay
  • Adventure Lab® Discussions
    • Playing Adventures
    • Creating Adventures
  • Community
    • Geocaching Discussions by Country
  • Bug reports and feature discussions
    • Website
    • Official Geocaching® apps
    • Authorized Developer applications (API)
  • Geocaching and...
    • GPS technology and devices

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location

  1. The volunteer reviewers do not visit the hides as part of the review process. Your reviewer bases their evaluation on the information you provided in your reviewer notes. If you weren't forthcoming about the lack of a container, they don't know you are missing one. With 200+ hides under your belt, I am surprised you did not know that one is necessary. Those two older caches (from 2016/17) that you cited were probably published for the same reason. Your reviewer simply did not know about the lack of a container. Someone has already linked to the No Precedent guideline so I won't double down on that. Finally, it might just seem like semantics, but there are legal reasons why HQ changed the terminology from approved to published. Some volunteers modified their names to remove approver from them. My advice is to stop looking for community support to disregard the guidelines and update yours as requested by your reviewer.
  2. Out of 200+ LBH Finds, I can only remember one that wasn't at the posted coordinates. I agree that a puzzle LBH should clearly spell that out at the top of the description.
  3. If it helps...in early August, 2023...the US had 9,525 EarthCaches. As of late February, 2024 it now has 9,712. So...close to 200 were written in the past 6+ months. Many states saw an increase...but a few actually decreased in their total number.
  4. The number of caches has been further reduced from 500 to 200 caches. Thank you.
  5. We (hubby RattleSnack and I) have been numbering and time-stamping our finds since about #200 or so (now approaching 3000 finds). I really don't pay attention to the order they show online, but for my own records and review, I enjoy going back to see the #'s and time of day of the finds. It will often trigger a memory when someone asks a question about once of our finds. Andif I ever need to see/remember the order we found things, the time stamps are helpful.
  6. My goals: Reach 200 cache finds Find at least 1 cache in another 2 countries Find at least 1 cache in another 2 States (USA) Hide another 5 caches Attend at least 1 Event/CITO Create 50 custom swag Get 20 FP’s Not too big of goals, but should be fun!
  7. Hello - Approaching 200 finds and wanted to give back to the game that's given us enjoyment. Wanted to hide our first cache - a simple one - and following all the guidelines is important to me. Does anyone have a general template they use when looking to receive approval from the person/city/company that owns the land? What information do you normally include, assuming the owner has never heard about Geocaching? I didn't want to recreate the wheel if someone has a template that's worked for them on a regular basis when hiding a GC. Thank you!
  8. Sinds 2005 wordt er door de Nederlandse Geocache gemeenschap een geocoin ontworpen en gemaakt. Ook in 2024 zal dat weer gebeuren. Voor de twintigste keer. Dat maakt het de langstlopende serie geocoins ter wereld. Tot en met maart kunnen de ontwerpen worden ingestuurd. We roepen iedereen op om zijn of haar ontwerp in te sturen. In die periode zal Rogier in zijn vlogs ook aandacht aan de Dutch Geocoin besteden. Daarna zal een jury een voorselectie maken. De jury zal daarbij op de volgende punten letten: 2024 (Heeft het ontwerp betrekking op het jaar) Dutch (Is het een Nederlands onderwerp) Originaliteit (Liever een kaas, die we nog nooit gehad hebben, dan de derde molen of vierde tulp) Artistieke waarde (Liever een mooi ontwerp dan een lelijk) Kan het ontwerp ook echt gemaakt worden. We zullen dit jaar iets strenger zijn in de voorselectie, d.w.z. een kleiner aantal munten zal geselecteerd worden voor de stemrondes. Tijdens de vlog zullen de ingezonden munten besproken worden waarbij ook tips gegeven zullen worden om je ontwerp te verbeteren. In april kan er dan on-line op de geselecteerde ontwerpen gestemd worden. Met aan het einde van die maand een Stem Event waar persoonlijk gestemd kan worden. Het gekozen ontwerp zal dan gemaakt worden en via CreaCoins verkocht worden. Daar is nog steeds de munt van 2022 en 2023 te koop. Behalve het fantastische gevoel om je ontwerp uitgevoerd zien worden, ontvangt de inzend(st)er van het winnende ontwerp ook een set Dutch Geocoin 2024 munten. Alle reden dus om (digitale) potloden en kwasten tevoorschijn te halen en je creativiteit te laten vloeien. Suggesties voor onderwerpen voor 2024 zijn: KNRM 200 jaar Zonnebloem 75 jaar. Staatsbos beheer 125 jaar. 2024: Jaar van de Huismus LVBHB (Landelijke Vereniging tot Behoud van het Historisch Bedrijfsvaartuig ) 50 jaar Amsterdam 750, Hilversum 600, Zaanstad 50 Inzendingen kunnen gestuurd worden naar DutchGeocoin@gmail.com Tc
  9. My take on the above is that the replies misunderstood the post. No one suggested that cachers do the calcs themselves, I think, just that there's enough information on the page FOR Groundspeak to do the calcs and get it right. (Although I will suggest it in a sec. Listing caches for a trip I don't think shows % only FPs? Unless using an outside website I guess?) While I sort of agree here, the huge dip in %FPs for those caches that are basic and getting huge numbers of finds but maybe more from basic members than premium, the calc would be really unfair to the CO/cache. Here is an odd example btw: a cache with over 200 FPs and 8900+ finds... https://coord.info/GC26VRH Currently it says 5% FPs, but the actual calc if you include all logs is 2.7% (half!). So I suspect (but obvs am not going to count) it is calculating the % from the PM logs. And granted, people go to it because they see something with a LOT of FPs. And yet actually it has a low percentage. (And isn't that great of a cache to be honest!) My point is, I think, that there is no winning here. Nothing suggested by anyone is "perfect" and actually all are problematic. I understand that FPs can be valuable, but they are often over-hyped and over-used IMHO. I don't want to banish them, but honestly I would just get rid of the percentage thing. Let people look and figure from the FPs whether to go for something, or look at FPs vs number of finds, if so inclined. I think the % calc has made a lot of work for GS programmers with results that are unsatisfactory to most everyone in some way. Not to mention buggy as h*ll!
  10. Well , that will take some time when listing hundreds of caches for a trip. Not practical. Percentage is MUCH more important than number to judge a cache by. If people think that there is enough information already (I don't agree), then just have the percentage of favourite points instead, as that gives a far better idea of the cache quality. In some places caches are found almost every day. In Europe I found some caches that were found this often; in fact it wasn't uncommon for some to have several finds in a day. In other places a cache might only have one or two finds (maybe even less) a year. So someone comparing these caches, says look this one (with several thousand finds) has 200 favourites so it must be the best cache. In reality it only has 10% favourites, but most people won't want to waste time working this out. Most people haven't thought it worthy of a favourite. Meanwhile the other cache has a piddly 5 favourites, so in comparison it can't be a good can it. I mean only five favourites . That's nothing! In fact it has 100% favourites. As in many things in life percentage gives the truer picture.
  11. At one time attendees at an event could (mistakenly) log 'attended' on a date different from the event date. Now, the only option is to log the date of the event. GPS Adventures Maze Exhibit, TELUS World of Science (GC58J1B), Edmonton, Canada was open from 18-Jul-2014 to 11-Jun-2015. During those 11ish months 200+ people logged 'attended' on various dates while the event was open. I attended 25-Apr-2015. I know not whether this 'cache event' is still available, but I am wondering, if it still runs as it did then, how Groundspeak would square the enforced logging of the event on the day it opens, with cachers attending on subsequent dates?
  12. The naming convention has nothing to do with mathematics... The Oregon 200, 300 and 400 all use the same firmware, and were referenced by Garmin simple as "Oregon": https://www8.garmin.com/support/download_details.jsp?id=4051 The 450 and 550 had different hardware and software, and were referenced by Garmin as "Oregon x50": https://www8.garmin.com/support/download_details.jsp?id=4524 The Oregon 600 and 650 share the same firmware (the difference was the camera in the 650), and are referenced as "Oregon 6x0": https://www8.garmin.com/support/download_details.jsp?id=6157 The Oregon 700 and 750 are referenced as "Oregon 7xx": https://www8.garmin.com/support/download_details.jsp?id=10378 When the 450 and 550 arrived on the market, the x00 designation was used (by users, afaik not by Garmin) to differentiate between the older and newer device ranges. So the use of x00 and x50 does not simply refer to the last two digits, but to a specific generation. Well known for longtime Oregon users, but it can be confusing for others...
  13. The original Oregon 200/300/400 series was commonly referred to as the x00 series, while the update 450/550 models were known as the x50 series. None of these models will charge batteries inside the device. The 'second generation' 600 series, also known as the 6x0 series, a well as the third and final generation 700 series (7x0) can charge Garmin battery packs inside the device, as well as your own NiMH batteries when using something to press in on the button inside the battery compartment. All of this information is available at GPSrChive.
  14. Because geocaching isn't just a phone game. The only way a cache icon appears on your phone's map is because the cache owner entered the coordinates into the website, preferably after averaging them over several visits. Even when locatlities can be readily identified on maps or satellite images, those can sometimes be wildly inaccurate. For example, the walking tracks near my most recent cache appear quite differently on Google and OSM maps and neither is anything like the actual tracks on the ground, with the real track junction almost 200 metres from where either map puts it. On the satellite image all you can see is the tops of trees so that's of no help, so the only way to reliably locate anything there is with GPS coordinates.
  15. Main problem are foreign reviewers, like for example one cache had a very hard to open lit, but the cache is there and all fun and happy comments, BUT it was DISSABLED because the lit was hard to open, not a warning, not a maintenance request, instant disable by T Robot. so that kills the game in a young country that is starting to learn how to play for a simple thing like that. Well there are actually a lot of caches in india, you have to considere the dimensions of india, it is a huge country so the distances are not easy to digest by foreign reviewers who think that 200 km is far, is not, im from argentina and had the same issues when starting, the same for brazil, and any huge country, USA may be huge but you have local reviewers PER STATE, we have one for the entire country that says that you cant be further than 200km from your home and thats easy my way to work... Also india overpopulation makes it really hard to hide caches on cities and since there is no good reviewer on India you got to deal with problems for publication of new caches.
  16. I just got back into Geocaching after quite a few years and all of my trackable Icons are gone on my profile…I had probably found close to 200 TB’s or Coins….I have found a few TB’s in the last couple weeks, and listed them and they don’t show up on my profile either….That’s part of the fun of finding Geo Coins and TB’s…What has happened in the last few years?…🙁
  17. With my find count currently sitting on 1764, I have another official milestone drawing close although, with only just over 200 finds this year and an average rate of 150 a year, it probably won't happen until well into 2025. New local cache placements have almost dried up completely, with only one since July (plus 2 of my own), so I expect most of next year's caching will be on day trips away, either solo or with our small but enthusiastic group. Plans are already afoot for some higher terrain cache attempts once the weather cools down a bit. As a CO, I'm nervously awaiting the announcement of the Virtual Rewards 4.0 recipients next month. Having missed out on the first three, I'm hoping maybe lucky fourth, although by my reckoning there are some 120 eligible COs in New South Wales and, with the state receiving about 40 in each of the earlier Rewards, my chances aren't that good. I have a spot in Brisbane Water National Park in mind, as it's a pretty spectacular location and is one where I'd wanted to place a physical cache a few years back but the park management wouldn't allow it, although they said a virtual cache or EarthCache would be fine as they don't require formal approval under the NSW National Parks geocaching policy. If I miss out again, I might consider putting an EarthCache there if I can figure out what geological processes were behind the formation of the rock finger. I have a few vague ideas but nothing scientific to back them up, and so far everyone I've asked has just shrugged their shoulders. Last Sunday I received a pleasant surprise (well I was blown away, actually) when one of my 2022 hides (GC9M6X5) won the Geocaching New South Wales Cache of the Year in its category (multi or series). The prize for that was a large steel ammo can so I'm going to have to find a really special place where it can make a fitting container for a new cache. The National Parks policy limits cache size to 2 litres so it won't be able to go anywhere in those, and my preference is to keep it on the Central Coast, so over the coming months I'll keep my eyes open for anything suitable. I have two National Park cache proposals currently awaiting a response from the respective rangers, one locally in Brisbane Water National Park at a nice spot alongside the Great North Walk overlooking Patonga Beach, and the other at the bottom of the newly-reconstructed walking track to the base of Gap Creek Falls in Watagans National Park. I'd almost given up on the first, having made my initial approach in May 2022, but in a recent reply to an unrelated query, the ranger said she'd try to push it through in the new year. Time will tell, I guess. Other than those, I don't have any specific plans at the moment for new caches, but I said the same a year ago and ended up placing eight this year. For me, it's usually a location I come across that inspires the cache, rather than the other way around, and I'm sure to find some more inspiring locations in the year ahead. In a nutshell, then, my goal for 2024 is much the same as in previous years, to just have fun finding and placing caches and let the statistics take care of themselves.
  18. 2024 Goals: Place 10 caches Reach 200 geocaches Find a Mystery cache Find caches in 5 new states Place a Earth-cache Attend an event/cito Collect all 2024 souvenirs
  19. Photos aren't well supported in various software because Groundspeak doesn't make it easy to get a PQ that includes photos in any real way and getting access to the Groundspeak API to develop modern applications to survive the various API changes has been sub-awesome. So it's a pretty small pool of tools that even can do it. Hopefully, few of us here will tell you how YOU want to go geocaching, but a couple of us with long tenures and plenty of experience are saying it's not worth the bother. If you have a cache (try something the GeoWoodstock event pages...) that has a zillion photos, it will take forever to scrape the photos and write them to your SD card but worse, when you're in the field and you load that page and that tiny little ARM processor starts to load, resize, and render a zillion images to a 240 x 400 screen, it will pretty much cough up its skull. So they're painful to get, painful to load, painful to display, and not really that useful while you're hunting. Additionally, when we created GPX, we left it pretty loose how media might be associated with a GPX file. Unlike KMZ, for example, there's not a convenient way to associate additional files, like images or movies, with the GPX data itself. We left it open-ended whether they may be <img> or href targets or be resized or even how they might be named. So if you're putting images on an SD card that has to obey 8.3 filenames and start with 5 PQs that each have 1,000 images, it's up to the application generating the result to be sure that an image named "fire.jpg" or "IMG043.JPG" in files 1 and 3 each have to be stored and referenced correctly so now they're only somewhat independent. These are solvable problems, but it's just another peek into the sausage factory of how software gets made and one more reason that it can be frustrating. Oh, and there's an integrated photo viewer in some of the Garmins that gives you pan and zoom, but you have to jump through yet more hoops to get the photos into the right place/format to make them visible both withing the Geocaching "app" and the photo viewer. The Magellans that did this (the [567]10's from the early days of the Mio era) did all of this annoyingly differently, so if you were writing software to do this, that was another obstacle you had to justify at the time to see if it was even worth it. The technical challenges exist and are all solvable. I spent some effort on automating this in the Palm/OS era when I was an active hunter and lots of logs had pictures and didn't consider it a break-even on effort. I'm with Mr. Bike above - if the last log is "the hiding spot has been compromised, so I put it 200 feet away at the location in the picture", I'll take the time to load it from cell.
  20. By far away I mean 100-200 meters not very far but still a considerable distance (so you can't just search around in the area of a stage and find another container without solving the puzzle).
  21. One of my visitor’s logs contains the “owner maintenance requested” icon, which I hadn’t noticed when the log was made. I have over 1,200 logs by visitors, so searching for this log is difficult. I want to find this log to see what the visitor thought needed maintenance. Is there a way I can search for this particular log?
  22. It's pretty clearly not a device targeting the power geocacher market. If you're a multi-day backpacker or maybe long-haul cyclist that legitimately spends a few hundred hours of activity without access to electricity, but still needs orientation to nearby cities for help, preloaded waypoints, and/or just needs a breadcrumb trail to return you whence you came, they may make sense. Maybe you log a geocache along the way at the summit. Maybe. But it's not the primary purpose of the unit. It seems to have the same level of mapping that the eTrex of recent years has had - a very very limited (28MB? MEGAbyte) basemap that you can refresh from your phone. I'm not sure if your phone needs a signal to pull this off or if you can siphon over a preloaded map from when you had service. You're just not going to get a color screen and turn-by-turn directions and maps for a continent in a device that claims 200 hours from a single charge. If you need turn-by-turns, you have access to power. Knowing that flash memory that small really doesn't take less power (it's built on older process nodes) and probably commands a price premium just for being less popular, it does seem likely that a 28MB map is artificially restricted. A 64GB basemap doesn't make sense and if you had a GB of basemap, the first questions everyone would have would be "how do we load detailed maps or topo maps or birdseye or...", it'd all be distracting. So it's likely artificially 'dumbed down' to keep it on par with its namesake from 2001 or whatever. Like Astro or the various fitness or marine or aviation units, it serves a market. That market probably isn't driven by price and they don't always overlap with geocaching. If you're 200 hours from an electrical outlet, the weight of a spare power brick or a bucket of AA's is a big deal. They're probably on trails or paths and have paper maps just for survival, so detailed mapping with elevation contours and such just isn't necessary for them. I think the last posters reaction will be that of MOST geocachers, but that's OK. This unit wasn't built for geocachers. That's OK.
  23. Interesting. I just did more testing to see if anything had changed from my earlier attempts, and I can't get any images to upload to the cache listing. I even tried refreshing like you suggested, but it still gives that error. Then I considered what SawaSawa said above about different browsers. All of my testing has been in Firefox, and it simply doesn't work. I then tried Chrome, and got different results. On the first attempt in Chrome, the same image uploaded successfully on the first try. I then tried uploading another of my test images and got the error. After refreshing the upload page and trying that same image again, it worked. So, the upload page is buggy but sometimes works in Chrome, and doesn't seem to work at all in Firefox. Hopefully this helps the devs to narrow in on the cause. Edit to add: I'm using the latest version of each browser: FF 120.0.1 and Chrome 119.0.6045.200
  24. Retired Guy and Cute L'il Fuzzy monkey years ago set up a great trail of Puzzle caches south of Orlando, each of which has a challenge to complete before claiming the find. They have done a great job of maintaining these 200 or so caches, and they maintain a Leaderboard showing all the geocacher who have found and qualified for at least 25 of these challenges. No one has found and completed all the challenges (one requires a find at 3 miles elevation or more, for example), and as of November, 2023, the top finder has credit for 197 of them. There are a number of challenge cache groups around the USA, but I have found no such trails that are all along the same road, and none with the Leaderboard feature, which has to be updated periodically. Is anyone aware of similar trails anywhere in the world? Thanks. Charlie, IMGOIN2
  25. Komisch, versuche mal folgenden Link: https://www.geocaching.com/plan/lists/BM10TEA?sort=name&sortOrder=asc&skip=0&take=200
×
×
  • Create New...