Ladybug Kids
-
Posts
1481 -
Joined
-
Last visited
Posts posted by Ladybug Kids
-
-
Sometimes Reviewers don't reply to e-mails because the sender unchecked the "I want to send my email address along with this message" box. If the cacher really wants a (quick) response, s/he will make it easy for the Reviewer to simply click "reply" then have to click to the cacher's profile and then send an e-mail from there. Making it easy to reply also keeps the entire "conversation" thread in one e-mail chain rather than scattered through a bunch of e-mails that say "Cacher X contacting Reviewer Y from Geocaching.com" and "Reviewer Y contacting Cacher X from Geocaching.com."
-
Sometimes cachers do e-mail the local Reviewer because of negative backlash in some communities for logging a "Needs Archived" or other log that while simply informative is viewed as negative by others.1423277968[/url]' post='5471066']Here is another one...
I am one of the last finder of this cache.
The last two DNF logs didnt get to GZ. Sigh...
The major problem of this cache is that the bridge is out(and still is as far I know) and you need to cross a dangerous creek to get to the other side.(best to cross it in the summer)
Is the cache still there? Very likely as long they didnt do any bridge work there. The cache is location at the footing of the bridge and its right where anyone can see it.
It might be that someone contacted the reviewer because they want to hide a cache on the accessible side of the trail but this inaccessible abandoned cache is blocking the placement.
In this case, the cache appears to be essentially abandonned because the Cache Owner has not been on the site since June 2014 and may not even be receiving the logs. The Cache Owner can very simply head off possible archival by proving s/he has a pulse and posting a note to the cache page about plans to check on the cache by hiking or driving in from the Kentucky Trailhead on NF-23 (longer hike, but not unreasonable for a day hike) or wading the creek (we don't have many bridges up here) or disabling the cache until the bridge is repaired.
-
A problem with using cliffs, rivers, ravines and other physical barriers as justification for an exemption to the 161m separation guideline is that the Reviewer gets stuck having to make a subjective call as to what is a sufficient barrier to justify the exemption. It's simply much easier to hold to the objective linear 161m guideline than sorting through many shades of grey.
-
I simply remind myself that logs like that say much more about the cache finder than the cache. The advent of the smart phone and the ability to preload a default log has led to a lot of this ("that's one more cache for me," "found it, the rest of the story later" (but the "story" rarely gets written) and other annoyingly short logs). One must also remember that "TNLNSL TFTC" and "DPM" were used by keyboard users long before smart phones took off.
-
There are (at least) two aspects to this issue:
1) Placement of a geocache on a piece of utility infrastructure, whether it be a transformer, high voltage tower, mile marker, telephone pole, or wind generator should be done only with permission from the utility that owns the said piece of infrastructure. I am unaware of any utility ever giving permission.
2) Placement of a geocache within a utility right-of-way should be done with permission of the Land Owner, who is most likely NOT the utility. Some examples given in here refer to municipal parklands that are crossed by the utility or were built in conjuction with the utility. In those cases, the municipality's geo-policy stipulates placement within the corridor (excluding items in #1, above). Another example exists in my own back yard. A high voltage transmission line and a natural gas line cross a corner of Chugach State Park. Placement of caches on transmission line or gas line infrastructure is not allowed because the owner of neither entity has granted permission, but placement everywhere else is covered by the Alaska State Parks statewide special use blanket permit.
Right of way (ROW) clearing is done for any number of maintenance and regulatory reasons. An electrical utility might learn over time it is cheaper, safer, and easier to clear-cut a ROW than to return annually to trim branches high in the air. A pipeline might be ordered by the Office of Pipeline Safety to clear the brush from its ROW to facilitate aerial inspection, even if said brush cutting results in permafrost degradation.
-
Supplies of the 2014 Alaska geocoin are dwindling as we begin to spool up efforts for our 2015 GeocacheAlaska! trackables.
-
I saw my first one at the 2014 Block Party and actually added one to my collection around Christmastime. These geocoins are wonderfully done in the Bev Doolittle style of hidden critters and predators. Nicely done!
-
I had a similar experience as the OP just last week. I wrote a "Note" log since it wasn't exactly DNF, but since I never even touched the container, nevermind signed the log, it certainly wasn't a find.
-
Thank you. I have made a proposal to our Board of Directors.GeocacheAlaska! may be interested in sending a geobling package. How will donors be acknowledged at the event?
~Ladybug Kids
Treasurer GeocacheAlaska!
I always have the name of each donor on each package we give away and mention them when we have the raffle . Some of the winners even take the time to send a little thank you message. When we have the opportunity we also take some pictures of the winners
-
GeocacheAlaska! may be interested in sending a geobling package. How will donors be acknowledged at the event?
~Ladybug Kids
Treasurer GeocacheAlaska!
-
The simple fact is that you'll never get people to stop placing crap caches in crap places. The solution to that is to be careful about selecting the caches you search for. You don't need to find every one.
While I haven't agreed with everything said in this discussion, I completely agree with all of the above.
That's pretty much what she's said in just about every post, with different wording.
Hey, the OP mentions the cache being near a honey bucket??? What is that? Is that what we in New Yawk call a Porta-Potty?
Not all crappy caches are crappy: Toilet Seat Island
-
My problem is this park has a special meaning to me, and I really wanted to put my cache there. There were PMO's all over the place, but if I could just see them I'm sure I could have found a nice little spit in between to deploy mine. But using the intro app I couldn't see them and it wouldn't tell me where to go to avoid them, so I was stuck unless I wanted to start paying 2.50 a month, which seems unfair.
Go to the geocaching map when not logged into the site, such as here: https://www.geocaching.com/map/default.aspx#?ll=28.09742,-80.64188&z=14 (I'm not sure where you are in FL) and look for your park; the PMO caches will show up. Granted, you cannot get very close to see exactly where they are, but you can zoom in a decent amount. And you can switch to aerial/satellite view as well. If you're on Firefox and install the Greasemonkey add-on and the script, "Geocaching Map Enhancements" (HERE), you can drop a marker on each of the caches and draw a 528 ft circle (err, half that, since you're looking at the radius) around them to get a good feel for where you cannot place a cache due to proximity guidelines. Any spot not covered with a circle should be OK.
There is also the Groundspeak Planning Map Tool. It won't show you the final stages for multis, puzzles, wherigos, letterboxes, etc., but it shows the location of all traditional caches, PMO or not.
-
OR, remember that Geocaching is about location and taking people to cool spots. If one area is "saturated," look at the map and find an uncached park or scenic overlook or forest trail. Take cachers someplace NEW!You are soooo right about that. We tend to plant a cache or two per year. In the last 3 years it's been 50/50 whether the spot we pick is really available. And we have 2 PM accounts and the $10 app. These days the reviewers are essential when trying to find a spot. Don't even bother putting too much work into it until you get the thumbs up from the reviewer. Be prepared to hear "your cache is too close to another cache". Be prepared to play Battleship for another spot.
I make it a point not to place a cache within half a mile of another cache unless there is a compelling reason to place one closer. Are there really than many cool, complelling places within 528' of someone else's cache? Hasn't been my experience.
-
I find it easy to understand Groundspeak's employee perks. Groundspeak is based in Seattle. They are competing directly with Google (right next door) and many other tech employers for recruitment and retention. They need quality developers and staff to keep up with the growth of the game. If they don't match their competitors' compensation and benefits packages, they won't attract the people with the required skillsets.So basically I pay $10 for an app and $2.50 a month so that Groundspeak can give their employees free ski lift tickets and free food? How can some of you honestly sit there and defend this company???
-
I prefer to host my images on the geocaching.com website and link to them. Other photo hosting sites come and go and the urls change, thereby breaking the links to the photos and rendering a white box with a "x" on the cache page.
-
It's not only possible, it's been done. I've moved at least two soccer-themed TBs from the U.S. to Europe, taking photos of the TB outside such locations at the Bremen, Germany, Stadium. Similarly, I've taken TBs wanting to visit NFL stadiums to locations such as the Cardinals Stadium in Phoenix.Just make it a request (not a demand) and that's it.
Your statement earlier (with a bit o change) "We'd be happy to see this travel to as many soccer fields/stadiums (youth, adult, professional, college, MLS, international etc) as possible. Pics a plus ! Thanks for helping it reach it's goals." might work.
-
Full disclosure: I have never had a Facebook account for a variety of reasons.
Forums have an important place for maintaining a record of discussion and information that can be retrieveable even years after the discussion. Facebook strikes me as an "in the moment" communication tool and once something slides off the front page, it's gone forever. This seems fine for people who want to post a photo or broadcast to the world they are going to the grocery store, but is isn't useful for storing useful information. Also, few people really seem interested in past history and live/work in the present, making Facebook more revelent for them, but next to useless for me.
Forums and other social media sites seem to have their own best uses and there can be powerful synergy if used properly together. However, most people seem to make an either/or choice, opting for for Facebook or other and leaving the forums, thereby hastening the demise of storing and maintaining institutional knowledge.
-
Off topic but relevant to recent posts: Some cachers seem to think a webcam photo is a selfie taken at the site rather than a screen capture of the actual webcam feed. There is quite the collection of non-webcam logs on that page...it appears the Cache Owner isn't requiring folks to log the cache in the original spirit of a webcam cache. If this continues and a Reviewer notices the lack of diligence, the webcam can get archived.I went down to San antonio, texas, and cruised the riverwalk. I found a virtual and two caches on Saturday, and a webcam, virtual, and earthcache, and two other caches on Sunday. That gave me lots of firsts Such as most cache types, first virtual, first webcam, first earthcache. There was also an event super close to my hotel, but my parents didnt want me to go since we were going to the alamo
Did they change the angle of that webcam?
We had it on a watch and yours looks like a ground-level pic to me.
Noticed a couple others similar too.
-
I don't think you're biased. Forums have a place for maintaining a record of discussion and information that can be retrieveable even years after the discussion. Facebook strikes me as an "in the moment" communication tool and once something slides off the front page, it's gone forever. For many people, it seems it's easier to just reask a question rather than be bothered with actually have to see what's available first. Also, few people really seem interested in past history and live/work in the present, making Facebook more revelent for them, but next to useless for me.Well, not everyone.
I still like the forums better than facebook for discussions. I'm an old fogey.
I prefer the forums but I play in both mediums. I think the forums are doomed over the next several years.
STOOPID facebook. 
I thought that at first, but now I prefer it. It's easier to post photos and have rapidly interacting discussions, you can create groups and pages for a club or interest area, and have photo galleries and club info as well as 'threads' (posts).
Being a mod, I'm probably biased.
-
I believe that if a baggie is required, the wrong container for the location has been chosen. Baggies don't stay intact for very long before the zipper no longer closes or they get holes in them. So, if a magnetic key holder is your container of choice, place it where it is sheltered from the rain/snow and skip the baggie. If you can't shelter the container from the elements, try a different container type.
-
-
I couldn't tell you if cell signal is available at any of my remote cache locations because when I go into the backcountry, my phone is turned off and sealed in a dry bag so in the unlikely event that I really need it and I have cell service, I will have a full battery available. Also, signal availability is dependent on carrier and cell phone model/brand. I've been in situations where I had no bars on a peak and my colleagues had four bars and vice-versa. As a result, I'd be reluctant to use the attribute even if it was available.
-
Shouldn't matter "why" if it complies with the current Guidelines and is going to be maintained.Yes, I see the timing issue.
I suppose I could archive it on Monday, on Tuesday someone contacts me to adopt it because they want to keep that GC code alive, Wednesday I ask the reviewer to unarchive it (not mentioning that I want to adopt it out to the challenge cache owner because I don't want to maintain it anymore) then the reviewer might unarchive it. But I can see them asking why? If the answer is, to keep the old GC# alive, would they unarchive it?
-
I see your point on this and agree with it. Requesting unarchival after a year has past is most likely a stretch. Requesting unarchival within a matter of days or weeks, not so much. There's nothing in the guidelines about a "statute of limitations" for unarchival, so the Reviewer's decision to unarchive does end up being subjective with respect to time elapsed since archival.I can see why they wouldn't.
I had an old cache, one of the first in the city. It was active for 11 years. I grew tired of maintaining it so I archived it last year when it became a chore. A year later the area that it's in is still cache-free.
Let's say an owner of a challenge cache for old active caches approaches me asking if they could adopt that archived cache because it has an old GC code (4 digits after the GC) which would mean new players would have one more old active cache to qualify. If I approached the reviewer with that reason, I think s/he should refuse. It opens a whole new can of worms. Archived caches would get resurrected simply for their valued GC code, not because someone cares about the geocache part of geocaching, otherwise they would just go ahead and plant a new cache in that spot.
I still like the forums better than facebook for discussions. I'm an old fogey.
STOOPID facebook. 
innappropriate log entries?
in General geocaching topics
Posted
You are responsible for the content on your cache page, so you can encrypt the content, delete it (a field will be provided for you to enter something like "please relog with more family-appropriate language" with a link to the appropriate Groundspeak reference), or let it go. If the inappropriate language continues on your and/or others' cache pages, you can bring the cacher(s) to the attention of Groundspeak via http://support.Groundspeak.com/index.php?pg=request