Jump to content

Ladybug Kids

+Premium Members
  • Posts

    1481
  • Joined

  • Last visited

Posts posted by Ladybug Kids

  1. Hello GAGB Members:

     

    Balloting for the 2019-2020 GAGB Executive Committee election is currently under way.  Ballots may be cast until midnight, Sunday, 24 November 2019.

     

    Full details about the election may be found in the GAGB Forums here.

     

    If you are a member of GAGB, you should have received an electronic Survey Monkey ballot in your e-mail.   Please check your spam folder if you do not see the ballot in your Inbox. The ballot came from "ladybugs@geocachealaska.org via SurveyMonkey <member@surveymonkeyuser.com>" with the subject line "Ballot for GAGB 2019-2020 Committee Election."

     

    If you do not find your ballot, please contact me at ladybugs@geocachealaska.org with "GAGB Election" in the subject line.

     

    Regards,

     

    Mike/Ladybug Kids

    GAGB Returning Officer

    • Love 2
  2. I used NiMh rechargeables since I started playing.  To assure a more complete charge cycle, once my Garmin Oregon is done with them, they get moved to my digital pocket camera, and then ultimately to my headlamp, before they return to the charger.  Doing this helps the batteries maintain 12-hours per charge for a couple of years before they start to fade.

  3. On ‎12‎/‎14‎/‎2017 at 3:59 AM, redsox_mark said:

    Personally I think the "might be missing" flag is useful, to distinguish those few times where I have reasons to believe the cache is likely missing vs. the 95% (or more like 99%) where I have no idea; only that I couldn't find it.  

    I do agree with this and I have done this, but in rare instances (probably fewer than a couple dozen times out of nearly 1000 DNFs).  I chose not to describe it to keep my post simple.

  4. On ‎12‎/‎7‎/‎2017 at 4:03 PM, barefootjeff said:

    Yes, you can, like if the hint says it's in a stump and the only stump within cooee of GZ is devoid of cache, then it's a pretty fair bet it's missing. But even so, the canned NM is "the cache might be missing", not is missing - you're allowed to be wrong, that's perfectly fine. Not logging an NM when you're reasonably sure the cache is missing is just passing responsibility onto that great Somebody Else to clean up all those abandoned missing caches cluttering up the map.

    I don't have enough hubris to assume that just because I didn't find the cache at what appears to be the hint location, that the cache isn't there. 

    Logging a DNF does not pass the buck to "Somebody Else to clean up all those abandoned missing caches cluttering up the map."  Reviewers use growing DNF log strings to identify problems with caches.  Because some cachers use "Needs Maintenance" in lieu of "DNF," when they didn't find the cache, some Reviewers have resorted to filtering on "DNF" and "Needs Maintenance" logs in order to capture those caches that may be missing.  Prior to adopting this filtering strategy, the "Needs Maintenance" logs broke up the DNF strings and as a result, "reset" the DNF clock.

    • Upvote 2
  5. When my family and I travel, I filter my PQs through GSAK and remove any cache with the "Needs Maintenance" (NM) attribute or a string of three or more DNFs because I simply don't want to spend my and my family's time looking for something that may not be there or needs Cache Owner attention.  I have subsequently modified my GSAK filter to eliminate caches with any combination of three or more DNFs and NM logs because of the trend to use the NM log rather than the DNF log type by a visiting Cacher who does not find the cache. 

    Every cache we attempt receives at least either a "Found It" or a "Didn't Find It" log from us because we either found the cache AND signed the log, or we didn't.  The only time we use the "Needs Maintenance" log is in conjunction with a "Found It" log when we've actually put our hands on the cache and have determined maintenance is required.  If we didn't find the cache, we don't know if we simply missed the container or if the cache is missing, so we can't possibly know if maintenance is required.

    • Upvote 1
  6. 6 hours ago, briansnat said:

     I wish I could find his Soapy Boy Rinsy Boy log.

    https://www.geocaching.com/seek/log.aspx?LUID=f49a7af1-cc6c-45c9-b9e8-e0ef52f2ae47

    I think one reason logging has changed is that "back in the day," a "busy" day involved finding one to three caches at truly memorable locations and one had to sit down at a computer to log the caches.  Now, ten finds an hour are possible in some urban areas without even trying hard and more than a thousand finds a day are possible along some power trails. Cachers are so racking up numbers, they no longer have the time to write meaningful logs and/or "thumbing" logs into a smartphone app simply isn't as conducive to writing a long log as sitting down at a keyboard and using ten fingers to type many times faster.

     

  7. Hello GAGB Members:

     

    Nominations for GAGB Committee for 2016/2017 will be accepted Friday-Monday, 11-14 November 2016.

    All GAGB members who joined before 1 October 2016 are eligible to nominate another member or second a nomination. Members who have been nominated and seconded are asked to accept or decline their nomination in this thread in the GAGB Forums.

     

    The thread will be closed at the end of the nominations period and anyone who has not been seconded and accepted during this period will not be considered as a candidate for election.

     

    The Election for the Committee will be held during Tuesday-Sunday, 22-27, November 2016.

     

    Candidates for the Committee are requested to send their manifesto, photo (passport style, I can crop the photo for you if you need help) and geocaching avatar (if you have one) to me, Michael Malvick (Ladybug Kids), GAGB Independent Returning Officer (ladybugs@geocachealaska.org) by midnight, Tuesday, 15 November 2016.

     

    After the nomination period has closed, nominee manifestos, photos, and avatars will be posted in a locked Candidates for 2016/2017 Committee Elections thread as well as on the ballot so you may read about why each candidate is standing for election and the skills they would bring to the Committee if elected.

     

    A Committee Candidates(2016/2017) - Q&A thread will be open during the week leading up to the election where Members may ask the Candidates about their GAGB goals.

     

    More information about the annual elections can be found in the GAGB Constitution (Section N) and Seeker Issue 30.

     

    In the meantime, it is important that you work with your internet service provider (ISP) to white list e-mails coming from the gagb.org.uk, geocachealaska.org and surveymonkey.com domains so you receive election news and ballots.

     

    At your service,

     

    Michael Malvick/LadybugKids

    GAGB Returning Officer

  8. 2016/2017 GAGB Chairman Nominations are now closed.

     

    Sharon Reid/Sharant was the only candidate to be nominated and seconded for GAGB Chairman and she accepted the nomination.

     

    Because Sharon is standing unopposed, the election for Chairman will not go to ballot.

     

    Stay tuned for news in a new thread regarding the nominations for the 2016/2017 GAGB Committee, which will open on Friday, 11 November.

  9. Hello GAGB Members:

     

    The nomination period for the position of GAGB Chair for 2016/2017 is now open. Nominations will be accepted from Wednesday 26th through to Saturday, 29th October 2016.

    All GAGB members who joined before 1st October 2016, are eligible to nominate another member or second a nomination. Members who have been nominated and seconded are asked to accept or decline their nomination in this thread.

    This thread will be closed at the end of the nominations period and anyone who has not been seconded and accepted during this period will not be considered as a candidate for election.

     

    The Election for Chair will be held during Sunday 6th to Wednesday 9th November 2016.

    Candidates for the Chair position are requested to send their manifesto, photo (passport style), and geocaching avatar (if they have one) to me, Michael Malvick (Ladybug Kids), GAGB Independent Returning Officer (ladybugs@geocachealaska.org) by midnight, Sunday, 30th October 2016.

    After the nomination period has closed nominee manifestos, photos, and avatars will be posted in a locked Candidates for 2016/2017 Chair Elections thread as well as on the ballot so you may read about why each candidate is standing for election and the skills they would bring to the Committee if elected.

    A Chair Candidates (2016/2017) - Q&A thread will be opened during the week leading up to the election where Members may ask the Candidates about their GAGB goals.

    More information about the annual elections can be found in the GAGB Constitution (Section N) and Seeker Issue 30

    In the meantime, it is important that you work with your internet service provider (ISP) to white list e-mails coming from the gagb.org.uk, gagb.co.uk, geocachealaska.org and surveymonkey.com domains so you receive election news and ballots.

    At your service,

    Michael Malvick/Ladybug Kids

    GAGB Returning Officer

  10. Based on the logs on Kougarok it really looks to me like two people were able to reach GZ, neither found the original cache, and both placed throwdowns. There is also reason to believe that it's been gone a long time or even that it never existed in the first place.

    Both people who reached Kougarok GZ used a helicopter. Clever Monkey himself stated that "time is money when you're renting a chopper" in his DNF log for "Pilgrim River Cache" and "Mindful of time on the ground $$$" in this Kougarok log, so I doubt either seeker spent much time looking for the original cache before deciding they'd burned enough money or pilot duty time and placed their respective throwdowns.

     

    As a "local," I don't feel there is reason to believe that the cache has been gone a long time or that it never existed in the first place. Tundra grows slowly, but persistently. In fifteen year, the tundra could easily have enveloped a micro cache, so slow, persistent probing around the large boulder and other hiding spots within 100m or so (consider the accuracy of some GPS models from that era) could be required. Rodent burial or movement could also be a factor, so digging in rodent piles might also be required. I've had to be persistent to find "lonely" caches that were placed only three or four years earlier. As I said before, if/when I go to GZ, I would go with one or more cachers and be prepared to spend a significant amount of time looking. It doesn't get dark up there at this time of year, so a long day trip or an overnight stay would work. There is an ATV trail only 50m away, so hauling in gear would be easy.

     

    Clever Monkey's possible throwdown and subsequent "found it" log will take Kougarok off the "unfound" list. His log states "The cache is now a write in the rain a4 bit of paper and I placed the cache inside a bright yellow pelican type case I had with me for my camera gear." So, what isn't clear is what besides the a4 bit of paper is inside the yellow case; Throwdown #1 or the original cache or nothing? If throwdown #1 or nothing, a DNF is still the appropriate log. If the original container, then history was made.

     

    Cleaver Monkey's states in his log, "Is this the oldest unfounded cache ? Some will say yes, some will say no. I won't argue either way." If he truly isn't going to argue either way, he would have logged a "note." Instead, he logged a "found it" which indicates he believes he found the cache, thought it is unclear what he actually found.

     

    From that log, there is no way of knowing whether the original container or throwdown #1 were found, and had I been the one to visit the site and found throwdown #1, but not the original, I would have logged a DNF and CITOed out throwdown #1. That would have left the Reviewer in the position of tracking the DNF logs and taking action when he felt it is appropropriate. On the other hand, having Kougarok come off the "unfound" list will take the pressure and attention off the cache until a party prepared to actually spend some time at the site deploys, thoroughly searches the area, and CITOs all throwdowns. In the process, that party may or may not actually find the original container. If they find the original container, they will make history. If they don't find It and log a DNF, the stage will be set for archival without geolitter being left behind.

  11. The cache description contains a bit of hyperbole. There are many, many, much more remote locations in Alaska. Accessing this cache does not require use of a helicopter or technical skills. It's just a long day trip from Nome. See post #53 for details.

     

    Given the location, it is highly unlikely the original container was muggled by humans. However, the tundra growth could have encompassed the original cache and perhaps even throw-down number one in a very thick vegetation mat or the local rodents may have buried it during their burrowing activities.

     

    If/when I get to make the trek, I will go with cachers committed to a thorough search, plan enough time for said thorough search, and perhaps even be equipped to spend the night to allow time to check a very large area. The last two visitors to ground zero flew there with helicopters which are expensive to just park on standby, so I doubt either past seeker was able to hunt and probe thoroughly at their leisure.

     

    The cachers who placed throw downs rather than simply logging a DNF have continued to tie the local Reviewer's hands. If the DNF string would grow, the Reviewer could act on that. If the thrown down caches had not been left behind, geolitter would not result from an archival.

     

    I don't understand why visiting cachers drop throwdown caches when they should DNF. A very prominent cacher dropped a throwdown north of the Arctic Circle a few years ago. Two months ago, I visited ground zero and found the original container and log in a matter of minutes. Ironically, I could not find the throwdown so I could remove it.

     

    I also don't understand the entitlement to logging a "found it" some people have just because they took a long or expensive journey. Caching is about the journey, so a DNF can be as much fun/rewarding to write as a "found it" with the right mindset.

  12. But isn't the reviewer supposed to check the satellite images and confirm that the location is legal and correct before publishing?

    Yes, but per jholly's post, some/many reviewer's are dogs (Alaska is reviewed by six dogs),, and they don't care which hemisphere they are in.

     

    Also, sometimes at the default map zoom level, even when "E" and "W" are swapped, the cache location looks legitimate and it's not until one zooms out several levels that the error becomes apparent.

  13. That's only happened once to me. I posted an NA on a cache that was still there but the lid had lost all 4 of it's tabs and was not doing anything to protect the contents. The CO was non-responsive to all the found logs that mentioned the problem and several NMs.

    A reason a Reviewer won't archive a cache like this is that once archived, the container becomes geolitter, likely never to be picked up. Some Reviewers will post a Reviewer Note to the page asking the Cache Owner to fix the cache. If, after a period of time (a month in some cases), there is no response from the Cache Owner, the Reviewer will post a second Reviewer Note requesting the next finder to pick up what has for all intents and purposes become geolitter and to include that information in his/her log. The Reviewer will then archive the cache.
  14. What Project-GC does not differentiate between is "collecting" countries and actually caching in countries.

     

    There are some multi-caches and puzzle caches out there where the first stage coordinates might be built, say in the Solomon Islands, to determine the final location in Germany. Google Street View can be used to scope things out in the Solomon Islands and build the final coordinates in Germany without leaving the comfort of the living room couch. Because the cache's starting location is in the Solomon Islands, cachers who log a "found it" light up the islands, without ever leaving the continent of Europe.

  15. One problem is defining the line between a commercial and a non-profit business. Some museums are owned by for profit entities. Many are non-profit. Some charge an entrance fee. Some do not. Rather than have the Reviewer try to sort out whether an establishment is a commercial business, it's better to consistently review caches from the perspective of "can the cache be accessed without interacting with staff?"

  16. Yes, I have found caches with vulgar things written and drawn in the logs. I have also found ammo cans that were used as latrines. There is simply a segment of the population (fortunately, a small segment), that does not know how to behave in polite society.

     

    The cache could be placed somewhere in the museum where cachers can access the cache without interacting with staff. There are several caches in Southcentral Alaska at public lands visitor centers (State Park, National Forest, National Parks, etc.) where the container is next to/under/near the guest book. I have seen the same done in at chamber of commerce visitor centers. If this is done, the cache page clearly needs to state the hours of availability and there are attributes that can be added to the cache page to indicated limited hours of availability.

  17. Reviewers that share a territory (such as the state of Minnesota) work closely together to assure they are consistent in applying local caching policy and so they don't "step on each others' toes." If one Reviewer is already working on a cache, the other Reviewer won't step in and take over unless asked by the first. This allows for efficient execution of the volunteer Reviewer duties and prevents cachers from attempting end runs around the volunteer Reviewers. There is enough volunteer work to do without two volunteers working on the same cache.

     

    Reviewers do not blacklist cachers. Instead, they do their best to work with cachers to publish their caches because they like to publish caches. When a cacher and a Reviewer reach an impasse, an appeal can be filed with Groundspeak via the Help Center.

     

    If you have read any local land manager policies and described your compliance in a Reviewer Note posted on the cache page, be certain to click the "Submit for Review" button in the upper left corner of the cache page to return the cache to the Review Queue. If you don't do that, the Reviewer won't know if you are ready for another review cycle.

  18. When used correctly, the various log types go a long ways toward improving the quality of the game and cachers should not feel reluctant to post accordingly. Cache Owners and Reviewers cannot do what they are supposed to do if they do not know there is a problem.

     

    Didn't Find It (DNF): Use this log type to describe a cache hunt that did not result in finding of the cache. No five minute or fifteen minutes rule or waiting until the second or third visit (I shake my head when I read, found it on the third try, yet when I scroll down the log history, I don't see documentation of the prior DNFs). A cacher either found the cache or did not find the cache when s/he visited ground zero. I'm on my way to 1000 DNFs (921 and counting) and it doesn't bother me a bit to continue incrementally adding to the count. A string of DNFs can cause a cache to come to the attention of a reviewer who can then nudge the cache owner to verify the cache is still viable.

     

    Needs Maintenance (NM): Used for when one FINDS a cache and the cache has issues such as a cracked container, soggy logbook, etc. A cacher doesn't know if a cache needs maintenance if they didn't actually find the cache. The one possible exception to this could be IF someone in the group KNOWS where the cache used to be and is no longer there. Otherwise, if the cache isn't found, the DNF log is appropriate. Reviewers don't usually get involved with NM logs because they are meant to be a means of cacher to cache owner communication.

     

    Needs Archived: Used by many reviewers as "Needs Reviewer Attention." In many cases, the reviewer merely needs to nudge the cache owner into action. In others, the cache may get archived if there are multiple issues with the cache. For egregious guideline violations, including irate land owner matters, prompt archival may occur.

  19. Here are images of these striking coins with their proxies:

     

    Shiny Gold

    2015EagleCoin-Gold.jpg

     

    Shiny Silver

    2015EagleCoin-Silver.jpg

     

    Black Nickel

    2015EagleCoin-Black.jpg

     

    These large geocoins are 2" (50mm) in diameter and 4mm thick. They are trackable of geocaching.com and have a custom 2015 icon: EagleIcon32x32.gifEagleIcon16x16.gif

     

    The geocoins are priced at $17 each and $47 for the set of three. Discounts are available to those who join GeocacheAlaska! at the Sourdough level.

     

    GeocacheAlaska! has produced geocoins annually since 2005, so don't miss out on filling in or starting a new set!

×
×
  • Create New...