Jones County geocaching policy and permit form

Jones County now has a geocaching policy, apparently since the beginning of 2009. So if you are placing a geocache there, you'll first need to obtain the permit from Jones County. Here's a link to the form. I also added this link in my list in the right column of this blog. My thanks to geocacher BlueDuece for drawing this to my attention.

Another Okoboji weekend

It's Memorial Day weekend so that means we're at Okoboji for the 24th consecutive year. While here, my wifi coverage is weak so don't expect at lot of caches to get published this weekend. I'll get caught up as the week progresses.

A great 10 years of geocaching event

I enjoyed my time at GC22TB1 10 Years! Cedar Rapids Area this past Saturday. I know everyone says this about geocaching events, but it truly is fun to put faces with the names that you see online. The group hike in the woods to find a couple of geocaches that afternoon was also a lot of fun. Thanks for Super Goober for organizing it and inviting me to tag along. Here are a few photos from the day.

Cache permanence: A lesson learned?

An interesting situation arose today that I want to write about because it highlights the section of the geocaching.com guidelines that deals with "cache permanence." I'm not going to name the cache owner because I don't want to embarrass anyone, but a cache was submitted yesterday for the purpose of giving grade schoolers a chance to try geocaching at their school.

First, let me explain that I have reviewed and approved other caches that are placed on school property. (I've found a few, too.) As long as the cache owner states that the cache is placed with the knowledge and permission of school officials, that's normally enough to get the cache approved -- even though it's possible that not every teacher, school administrator or facilities employee will be made aware of the geocache. As a result, geocachers may look suspicious and may be questioned if they're seen lurking around a school building during school hours, so it's up to each geocacher to decide if he or she wants to look for that particular cache.

Now, back to the cache in question. It was placed just outside the doors of an elementary school building by a teacher at the school. But what I did not know was that the teacher intended to leave the cache in place for just one day so his or her students could search for it and, in the process, learn about geocaching and how to use a GPS receiver. An admirable goal, to be sure. Teachers who make the extra effort to make school interesting and fun should be commended, and I do commend this teacher. However, the problem in this case is about cache permanence. Geocaches can't be listed on geocaching.com if the intent is to leave them in place for just one day. Quoting from the guidelines:

Cache Permanence

When you report a cache on the Geocaching.com web site, geocachers should (and will) expect the cache to be there for a realistic and extended period of time. Therefore, caches that have the goal to move ("traveling caches"), or temporary caches (caches hidden for less than 3 months or for events) most likely will not be published. If you wish to hide caches for an event, bring printouts to the event and hand them out there.
We realize that it is possible that a planned long-term cache occasionally becomes finite because of concerns with the environment, missing or plundered caches, or the owner’s decision to remove the cache for other valid reasons. Please do your best to research fully, hide wisely, and maintain properly for a long cache life.

So even though I didn't want to put a damper on this fun class project, I archived the cache this morning -- the very day that it was supposed to be in place for the students. I haven't heard for sure, but I assume the teacher was still able to conduct the geocaching demonstration with the kids, only without the element of looking up the coordinates on Geocaching.com.

Along the way, in addition to learning about navigation satellites and using a GPSR, my hope is that another valuable lesson was also imparted to the students. About reading directions.

Upcoming events

I have two events on my calendar that I'm looking forward to attending this spring and summer. Well, more than two actually, but these two are public events that other geocachers may be interested in as well. The first is

10 Years!: Cedar Rapids area, Iowa

on May 1. In case you haven't heard, geocachers around the world are hosting events to commemorate the 10th anniversary of geocaching. 

The other event happens on August 21 in the Quad Cities: 

Floatzilla 

Mary and I are planning to paddle the "advanced" route, which will be 9 miles from Ben Butterworth Parkway, Moline, to Rock Island's Lake Potter.

Will we see you at one of these events?

IGO's system to recommend caches for archiving

Back in the December, bucknuts (Dale), a member of the Iowa Geoachers Organization (IGO) board asked me my thoughts about working with IGO to get caches archived that may have passed their useful lives because the owners are no longer maintaining them. We agreed to give it a try. The IGO system for calling such caches to my attention has been in place for about a month. So far it's been working well, although there has been some questions and discussions about it among Iowa geocachers. To shed more light on the system, I'm posting (with permission) an email I received from Rlowtek (John), who raised valid concerns about the IGO system, followed by my response.

Ken, 

I have exchanged messages with the President of IGO over my concerns with the new IGO cache “Tagging” process.  Below I have provided my thoughts and would like to know your opinion and how in practice you use this process.

I believe this will not enhance geocaching (to the contrary) and that a proper, open method already exists to accomplish the desired result. In effect, this creates two parallel systems. Publicly, you, the administrator or other Groundspeak volunteer, warns the owner and they generally have 30 days.  The open system, governed by geocaching.com/Groundspeak, provides if someone publicly abuses the “Needs Maintenance” or “Needs Archived” logging,  the system will be self-correcting.  However, the underground, anonymous system, is not self-correcting and is without benefit of public exposure to the point of not requiring the "tagger" to have personally posted a "Needs Archived" log. Further, it appears that archiving is instantaneous.

While I share everyone’s frustration with caches that are not maintained, I believe this “cure” is worse than the disease. It will result in accusations, retaliations and misunderstandings. If one is concerned about caches needing justified attention – use the “Needs Maintenance” or “Needs Archived” logs. The IGO tagging will be influenced by individual personal bias and opinions of what geocaching is supposed to be – bias that we all carry. Even with the purest of intentions, hard feelings will be the result. 

I believe we have enough squabbles and misunderstandings in the caching community. We simply do not need more fuel for the fire. While at times we all feel the need to be the geo-police, it is ill-advised to give in to the temptation. I further submit there is a better system already in place that is reasonably impartial and is certainly in the open.

RLowtek/John

My response:

John,
    Thanks for your feedback.
    A few responses...
    First of all, archiving a cache is not a death sentence for a cache.
It's simply another method to take it off the books until the owner decides to do something about the DNFs, Needs Maintenance, or SBA logs. If, after archiving, the owner truly wants to keep the cache going, he or she needs to be prompt about getting it fixed before another cache takes its place. In most cases it can be brought back to life with a simple email to me explaining that it has been maintained and is ready to be unarchived.
    Second, I agree with you that there is already a system in place for dealing with caches that need attention. I don't view the IGO tagging process as a replacement for the geocaching.com system of logs. Rather, it's a useful supplement to that system because it gives the elected organization leaders a way to notify me about caches they feel need to be maintained. I view it as a useful aid to help me monitor caches that may be in need of TLC.
    Regarding whether there was a Needs Archived log on a cache before it is archived, I agreed that there should be.  In fact, I pointed this out to the IGO board -- requesting that they not forward to me requests for archiving unless there has been a SBA log posted on it for a reasonable amount of time -- say two weeks -- without a response from the cache owner.
    I hope this clears up the situation and the current interaction I have with IGO about its tagging system and how I respond to it.

Ken
IowaAdmin
volunteer reviewer

Remember locationless caches? They're still no longer allowed.

Here's email I received today, followed by my response. (Name withheld)

Is there any way that you would publish a mystery/puzzle cache without there being an actual container? The whole point would be to get pictures of Cachers from around the world without them having to travel to the actual cache. The one that I want to put out would be to get people to take a picture with there favorite rock or rock formation, and post it in there log, and then it would count as a find.  So it would be sort of like a virtual or locationless earth cache, but it would be posted as a mystery cache.
Hope to hear from you soon.

Thanks for your email. Sorry to say that this type of cache cannot be published on geocaching.com. There has to be a physical cache for people to find and a log for them to sign, as per the guidelines. I'm not sure how
long you have been geocaching, but a few years ago there was a category of geocaches called "locationless", which the cache you describe would fit into. The cache owner would stipulate what the requirement was to log a find: see a yellow Jeep, find a Kent Feed sign, etc., and then post the coordinates where you saw it. Those cache types are no longer allowed to be listed on geocaching.com.

Time to catch up on SBAs

To those of you who have posted SBA (Should Be Archived) logs lately, help is on the way. (Actually, to be precise, the log type is now called "Needs Archived") Expect to see action within the next few days to address many of those inactive disabled caches across the state. Owners of caches that may be in need of maintenance can expect to receive a note from fellow reviewer Nomex, who has graciously agreed to lend me a hand with this task.

A cold weekend in Iowa

We made it to Cherokee this past weekend and enjoyed a nice time with many of our relatives. However, we didn't do any geocaching -- it was just too darn cold and there was too much snow on the ground to spend time rooting around for geocaches. Friday night and early Saturday it got down to -24F. As we were driving home Saturday afternoon it was still only -12F. Just after 4 p.m. Saturday as we were driving on Hwy 20, we came upon the scene of a single car accident. A car had left the 4-lane roadway and rolled over several times in the median. It looked like no one could have survived, but I read online that there were three people in the car and they all survived. We had stopped for gas just a mile or two before arriving at the accident scene and I saw a state trooper whiz by while I was stopped at the gas station. It made me think what might have happened to us if we would not have stopped for gas and had been near the other car when it blew a tire. It's disheartening to see the chances some people take when they're driving without ever thinking about the consequences to themselves, their passengers or people in other vehicles.

To Grandma's house we go

We were hoping to make the drive to Grandma's house in Cherokee for Christmas but the snowstorm forced us to change our plans. The new plan is to go to Cherokee this weekend. Maybe we'll be able to find some Tonedog52 or Wonder Boy caches if we have time between family activities.

A nice Christmas thank-you

Here's an e-mail I received a few minutes ago. It's the nice notes and comments from geocachers I meet in person that make it all worthwhile.

We just wanted to thank you for all the time and effort you give so that we can put out and hunt caches. It is amazing how many you have approved this past year. We just started geocaching in June and are having such fun as a family. We appreciate all you do and we know we couldn't do it with out you. THANK YOU!
Merry Christmas to you and your family!

Who's not getting my vote for cachers of the month

File this one under the category of "Ya Think?"
Here's the cache they were going for: New Phila Ballfields in Ohio.
And here's the result, a story in their local newspaper:
Headline: Shortcut may cost geocachers

The DARPA balloon project

In case you haven't been following what's going on at Groundspeak today: http://www.10balloonies.com/  Looks like they're closing in on all 10 balloons, thanks to the nationwide network of geocachers.

Peak placement season seems to be over

It was a busy summer for new geocache placements in Iowa. Now that the leaves are nearly all down and the temperatures have dipped, the pace has definitely slowed, which it does every year about this time. Instead of opening my browser and seeing a queue of 20 to 40 new caches on weekend mornings, this morning there were only four... so far. However, if this year follows form, there will be a mini-spike of new caches just after the holidays when new GPSRs are doled out as Christmas gifts. By the way, my wife was at Garmin headquarters near Kansas City this past week (on business) and mentioned to them that her husband is a geocacher. They told her I should stop in sometime and meet with their geocaching team. Evidently Garmin has a designated team assigned to the geocaching market, which only makes sense considering how many GPS units must get purchased every year primarily for geocaching.

"Team" finds or "ghost" logs? What do you think?

This week two different cache owners wrote to me to ask my advice/opinion about how to respond when a geocacher posts a "find" on their cache page but did not sign the log. The first situation (messages are posted below with permission from the cache owner; names changed to protect identities) involves members of a geocaching "team" who all log a find even though only one of them is present at the cache. Here's the message I received:

Hello Ken,
You have been a wealth of information to me lately and because of that, I have a semi-hypothetical question for a real-life situation and how our geocaching guidelines apply to it....

Let's say you and I are good geocaching friends and we call ourselves "GeoPair". So maybe I go out and make a find today (by myself) and sign the log as "GeoPair". I let you know I found it, and BOTH OF US log a find. But since GeoPair is just a pseudonym for our partnership, we have to log our find individually using our separate usernames on geocaching.com. The owner of the cache does a log check and finds GeoPair signed the log, but you and I both posted finds. Perhaps it is well known that you and I together are "GeoPair", perhaps not. The general guideline is once you've signed the physical log, you can post the find on the internet. In this situation is it allowable for both of us to log a find? Is it acceptable (without repercussion) for the owner to delete both of our logs (due to the "bogus" nature of the logs)?

I ask these questions because I am aware of a situation that exactly mirrors my description of this hypothetical situation. What are the exact "rules" that apply here? If I had made this "find" today I could have just as easily signed my name and "forged" your name and the owner probably wouldn't/couldn't know the difference. I assure you, I am NOT doing this. I am aware of another geocacher that IS doing this (signing a pseudonym and/or signing for others). I am just looking for clarification of our geocaching guidelines and options/remedies for a situation such as this. I am relatively new to geocaching, but I believe in and insist on maintaining the integrity of this sport.

I would appreciate your insight and opinion regarding this matter. Thank you!

And here's my response...

I appreciate your efforts to protect the integrity of geocaching, but the geocaching logs are sometimes a mysterious place where one person's viewpoint conflicts with the next person's. As a volunteer reviewer, I have been instructed time and time again that reviewers are not the log police, so we shouldn't be editing or deleting logs on caches (other than those we own) unless a log violates terms of agreement that all geocachers "signed" when they created their account on geocaching.com.

Note: The rest of this email is my personal opinion and not necessarily that of geocaching.com. My personal opinion -- and I believe the widespread opinion of many long-time geocachers -- is that if you are not physically present for a find, you shouldn't claim it as a find.

In additon to my IowaAdmin account (which I rarely use to log finds), I have an account that I use when I cache hunt on my own and a third account that my wife and I use when we geocache together. Having said that, I know of many couples (usually husband and wife) who have just one account and log all their finds there regardless of whether they were both present. If a single account is shared by a nuclear family, there's seems to be widespread agreement among geocachers that it's OK for family members to log a find even if a spouse or kids were not present. To each his/her own.

Regarding the situation you describe, the cache owner IS the cache police for his/her own cache. I believe the cache owner is justified in deleting any logs he/she truly feels are not legitimate. Like any situation where there may be a difference of opinion, all actions by the cache owner should be done with tactful courtesy and not out of spite or nastiness. The cache owner should clearly explain why he or she is taking the action, such as deleting a log, and give the geocacher a chance to respond or revise the log. If the geocacher doesn't like the outcome, he/she can choose not to search for any more caches owned by that particular cache owner. But there's no need for public shouting matches about it. Just accept it and move on.

I hope this helps.

So what do you think?

Stats a lot of caches!

It's time once again for some stats about geocaches.

• I reviewed 3,053 new geocaches during the past year -- roughly from September 2008 through August 2009. All of these were in Iowa. That comes to an average of 8.36 caches reviewed per day.
• Worldwide, 391,742 new geocaches were reviewed during the past year.
• In the United States, 193,054 new geocaches were reviewed during the past year.
• Iowa now has 7,949 active geocaches (including event caches but not including EarthCaches) listed on geocaching.com.
• Worldwide, there are now 912,967 active geocaches.

What's your guess for the exact date that we'll hit 1 million?

Cemetery caches - what's the policy?

If you're a regular reader of the forums at geocaching.com, you may have noticed discussion about an update to the guidelines that mentions caches hidden in cemeteries. The discussion from Groundspeak is summarized in this posting from MissJenn. In a nutshell, the guidelines now include cemeteries as areas where geocaches might not be allowed. Quoting from the guidelines: "Caches placed in areas which are highly sensitive to the extra traffic that would be caused by vehicles and humans (examples may include archaeological or historic sites or cemeteries)." (Boldface added by me.) MissJenn's posting says, in part, "This is why we have local experts (your reviewers) who know the deal in their respective territories. They know the right thing to do. They have been doing that and they’ll continue to do the same."

My standard operating procedure for cemetery caches remains what it has been for several years. When a cache is submitted that is inside a cemetery in Iowa, I temporarily disable the cache and send this note to the cache owner:

"This cache appears to be in a cemetery. Because of complaints about geocachers
playing 'games' in cemeteries across the country, I need to make sure you
received permission from the cemetery owners or caretaker before this is listed.
Also, the cache needs to be placed away from graves so it doesn't upset mourners
who may accidentally find it or see geocachers in the cemetary. Please reply by
posting in a reviewer note the name and contact information of the person who
granted permission for this cache and then re-enable the cache so it reappears
in my review queue. If you don't plan to seek permission, please archive
the listing and remove the cache. Thanks for your understanding."

Therefore, if you are planning to place a cache in a cemetery in Iowa, you'll need to seek permission. Once you receive permission, please be sure to include that information somewhere on the cache page, either in a reviewer note or in the short or long description.

Occasionally, a cache owner will submit a new geocache and state that it is just outside of the cemetery. It happened just this morning. In those cases, I have not been asking the cache owner to seek permission. However, if the cache is hidden on the gate, fence or wall that surrounds a cemetery, I have been asking them to seek permission, because gates, fences and walls are part of the cemetery and owned/maintained by the cemetery owner/groundskeeper.

Submitting caches in advance for an event

Here's a recent question that has been asked of me at different times by different geocachers.

Ken,
Just a question regarding our upcoming event. For last years event,
you allowed us to submit caches "pre-approval" before the event and then
published them a few days after the event. We are already scoping out
places for this year's event and were hoping to do the same thing. A few
of the containers we make for a specific spot. How much extra work
is it for you to pre-approve these caches and then sit on them? Do you have a separate database of caches that have been approved
but are not yet published? As always, thanks for your time.

So that more geocachers can understand how I like to handle these situations, here's my answer. In general it's fine to submit caches for pre-approval that you don't want published until a specific date. I'll look them over and let you know if they appear to comply with all the guidelines, including the 528ft. proximity guideline. Rather than me setting some type of timer on them for publication on a specific date (a feature which is not available to me but which would be nice to have), I'll disable them and wait for you to re-enable them when you're ready for publication. That way they will to reappear in my review queue.

It's fine to submit caches several weeks in advance. Even a couple of months is OK if you're planning to submit a large number of them. However, it wouldn't be fair to other geocachers to let you submit geocaches more than a few months in advance, because that would be abusing the privilege of "reserving" geocaching locations.

Get out there and get 'em

I was at Okoboji at a family gathering this past weekend, so even though I logged on to approve a few caches a couple of times overe the weekend, I didn't want to spend much time reviewing caches while I was with the family. So, I just finished publishing about 50 new geocaches this evening -- catching up on those that were submitted over the weekend.Those are in addition to the 90 or so I published after last weekend. If you don't have a new geocache near you... well, maybe you haven't checked geocaching.com lately. :-) Here's a little video of fun on the water while at Okoboji...

Cherokee's Welcome Spring event

I had a great time in Cherokee last weekend attending the "Welcome Spring" geocaching event hosted by Tonedog52 and Wonderboy. The caches placed for the event that I found were worthy of standing on their own. By that I mean the organizers did a very nice job of hiding quality caches. Some of the parks where the geocaches were placed did not exist when I lived in Cherokee back in the late 1960s to mid 1970s. It was great to meet so many geocachers that I have corresponded with, and to renew a few aquaintences as well. Lots of people came up to me with questions about specific types of cache hides or specific caches that they were thinking about hiding, so it was enjoyable for me to offer guidance and encouragement. I especially enjoyed the Sunday morning paddle trip down the Little Sioux River as we found geocaches along the way that Tonedog52 and Wonderboy had placed for the river event. I wish every event included a paddling-while-caching aspect to it. Lots of fun, despite the fact that a few paddlers managed to dunk themselves that morning.