A blog by one of the volunteer reviewers for Geocaching.com. It's about geocaching and the review process -- what it takes to get your new caches listed on the world's most popular geocaching web site. ©Copyright 2012 by K.Braband. All rights reserved
Monday, October 17, 2011
IGO's annual Hike N Seek event
Thursday, October 13, 2011
River Action launches geocaching program
Friday, September 09, 2011
SuperGoober: One of Groundspeak's Featured Cachers of the Month
Saturday, August 06, 2011
Friday, July 01, 2011
Friday, May 13, 2011
Time for a cache clean-up and a thank you to Nomex
Monday, May 02, 2011
Website update coming Wednesday
Friday, April 08, 2011
Seed caches
Friday, March 25, 2011
The Lexicon of Geocaching
Saturday, March 19, 2011
Questions and Answers about Geocaching
Question:
Hey Ken!
We were wondering what exactly the rules would be if we had a cache that had a micro SD card in it so that cachers could simply insert it into their phone and save a video or photo to log their find. I'd think that that would be perfectly fine, but would we also NEED to have a paper log? It would be no trouble to include one, it's just that we think it would be a little cooler/high tech if it was only the SD card. Geocaching is a high tech sport/hobby/obsession and with the huge increase in popularity of smart phones or phones with cameras, this would be a really cool cache.
My Answer:
Thanks for your inquiry. It's cool to hear that you're thinking up new ways to make geocaching fun. As you have guessed, yes, you would also need to include a paper (or similar substrate) logbook that geocachers can sign. Using the SD card would have to be clearly marked as optional. In the past, geocachers have hidden USB drives in caches in hopes that geocachers would need to plug them into their laptop computers to obtain final coordinates of a multicache or unlock a code to find a puzzle cache, but Groundspeak has not allowed those to be a required part of finding a cache because of the potential for someone to introduce malware to the storage device. That same reasoning would apply to an SD card.
Question:
Hi Ken,
I was wondering if you could tell me the coords for the GCXXXX cache stage that is too close to the cache I placed today GCYYYY (40ft up a tree).
My Answer:
I'm not allowed to give you the coordinates of the second stage because you would need to find it on your own, but I can tell you that you would need to move your cache at least 290 ft east of where it is now to be at least 528 ft from stage 2 of GCXXXX. If you know the owner of GCXXXX, you may wish to ask him for the exact coordinates of his second stage. Thanks for working that out with him.
Question:
A geocacher could not find 3 of my caches and he took it upon himself to replace them. I take great pride in maintaining my caches. They are almost all local and as soon as someone says it needs attention, I am right there to do it. If there are several dnf's listed in a log I go out to check on it. Just because he didn't find it, does that mean it isn't there? That decision belongs to the owner. I went out and replaced the containers he left with my own and my own logs. Only one of these caches had a dnf before Sunday and it was only 1 dnf. I replied to him about replacing the one cache and he mentioned in his reply to me that he had also replaced the two others. He did not log that in his log entries. I would never have known he did that unless he had told me in the email. I deleted all 3 of his logs. What do you think of this and is there any way you can mention to him that it is not acceptable to do this?
My Answer:
I sympathize with the frustration you feel about having your caches replaced by another geocacher. I had the same thing happen to me in the past. Sometimes it was done with my permission because a geocacher asked me ahead of time if it would be OK. Other times it was done without my knowledge or permission. In your case, if your caches were replaced without your permission, then no, that is not OK. In my opinion, based on what you have told me about the situation, it sounds like you did the right thing by writing to the geocacher and then deleting the logs that you felt were not legitimate. That's your responsibility as the cache owner. Regarding your question about whether I should mention anything to them, with your permission, I may post this email conversation in my blog so more people become aware of the issue. But in the long run, there will always be behaviors displayed in geocaching that you, I, or other geocachers disagree with. Neither you nor I can stop everyone from doing things they shouldn't do. But in the case of geocaching, we CAN control how much the things they do affect us -- our attitudes and our lives. What I'm saying is, you should go ahead and delete the logs and maintain your caches in the correct manner, like you are apparently doing now. But don't let the actions of a few spoil geocaching for you.
Question:
Hello Ken,
I have a question regarding the new “chirp” accessory and the beacon attribute. First of all, I would like to know if the “chirp” is considered a “physical container”, and whether its placement falls under the 528ft saturation guideline. I would think not, since it would not be seen or handled by a geocacher.
My Answer:
Even though a Chirp is a physical waypoint, Groundspeak allows considerable "latitude" (if you'll pardon the pun) on the saturation guideline for the waypoint locations of the wireless beacons. The range of a Chirp is around 32 feet for an exposed chirp; inside objects, it's less than that, so that's why they allow them to be placed closer together than 528 ft and closer to existing geocaches and physical waypoints. So I'd say, yes you can place your Chirps closer than 528 ft, but you should probably place them at least 40 ft from each other. Does this answer your question?Their Response:
Yes, that answers my question. The stages I have in mind will be several hundred feet apart, so the 40ft suggestion you made is not an issue. But, it is possible the "virtual" waypoints of the hide I have in mind will be within a few hundred feet of other virtual and physical waypoints of nearby caches. I just wanted to verify if I had working room for my idea. I think you have verified that. I'd hate to set the whole thing up and have you deny it when I submitted, based on saturation rules. Thanks for your help and input. As always, you are a "wealth of information".
Wednesday, March 02, 2011
For the poker players
Tuesday, February 01, 2011
Des Moines Register blogs for geocaching
Thursday, January 27, 2011
Fun reviewer notes
Thursday, January 13, 2011
Behind the scenes with a geocaching reviewer
Monday, January 03, 2011
EarthCache guidelines updated
"Requests for photographs must be optional. Exceptions to this guideline will only be considered if the requested photograph is related to an Earth Science logging activity such as recording a phenomenon. This particular guidelines was updated on 1 January 2011. All EarthCaches must conform to this guideline as photo requests are considered "additional logging requirements" (ALRs) and follow the guidelines set forth by Geocaching.com. Existing EarthCaches that do not meet this guideline must be updated to comply. Cache owners may not delete the cacher's log based solely on optional tasks."
And in case you weren't aware of it, I don't review Earth Caches in Iowa. They're reviewed and published by a different group of reviewers. If you have questions about Earth Caches, you can address them to glewis@geosociety.org.
Friday, December 24, 2010
Merry Christmas!
Thursday, November 04, 2010
Chirping?
Any caches that use a Chirp (or any future similar device) should use the new "beacon" attribute. If you put a Chirp in a traditional cache and geocachers have an alternative method to find it without using the Chirp, then it's OK to be published. If for some reason you absolutely don't want to provide an alternative means of finding it, it must be listed as a "mystery" cache with the beacon attribute. Your cache description may mention the "Chirp"as long as the text doesn't go on and on with overtones of advertising, marketing, or promotion.
Sunday, October 31, 2010
Notifications are not part of my domain
Sunday, October 03, 2010
The end of new FTF series caches
Saturday, September 25, 2010
Hike N Seek Shelter
Saturday, September 18, 2010
Are you ready for some new geocaches?
Sunday, September 12, 2010
Friday, August 27, 2010
Thursday, August 19, 2010
Churning
Friday, July 23, 2010
Appreciation Event
http://www.youtube.com/watch?v=wlBEgETgWgI
And here are a few photos from the event.
Hiya,
I can't find a contact button on your blog, go figure.
I was wondering if you could post some photos on your blog of what the "reviewer interface" looks like and what all that cache reviewers do from when they get the cache to when they click the publish button.
And here's my response:
Thanks for your inquiry. Unfortunately, I can't share the type of information you're asking for. Groundspeak does not want its volunteer reviewers to reveal information about the reviewing web pages. I think it may be out of concern that the system might get hacked or otherwise abused. I can tell you that when a new cache is submitted, I look to make sure it complies with all the guidelines as published at geocaching.com, such as minimum distance from existing geocaches, that the geocacher lives close enough to the cache to maintain the cache or has indicated his/plan for regular maintenance, and has obtained permission when necessary (such as on Iowa DNR-managed land). If there are specific questions you have, let me know and I will answer those that I can.
Ken
IowaAdmin
volunteer reviewer
Tuesday, July 13, 2010
Iowa geocacher busterbabes in Groundspeak video
Did any other Iowa geocachers make the trip out there?
Monday, July 12, 2010
Door prizes
Thursday, July 01, 2010
A reviewer appreciation meet & greet in Des Moines
Thursday, June 03, 2010
Jones County geocaching policy and permit form
Sunday, May 30, 2010
Another Okoboji weekend
Thursday, May 06, 2010
A great 10 years of geocaching event
Friday, April 23, 2010
Cache permanence: A lesson learned?
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 PermanenceSo 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.
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.
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.
Monday, April 05, 2010
Upcoming events
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?
Sunday, March 21, 2010
IGO's system to recommend caches for archiving
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
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
Tuesday, February 09, 2010
Remember locationless caches? They're still no longer allowed.
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.
Tuesday, January 12, 2010
Time to catch up on SBAs
Tuesday, January 05, 2010
A cold weekend in Iowa
Tuesday, December 29, 2009
To Grandma's house we go
Tuesday, December 22, 2009
A nice Christmas thank-you
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!
Friday, December 18, 2009
Who's not getting my vote for cachers of the month
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
Saturday, December 05, 2009
The DARPA balloon project
Saturday, November 21, 2009
Peak placement season seems to be over
Thursday, October 22, 2009
"Team" finds or "ghost" logs? What do you think?
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.So what do you think?
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.
Friday, October 02, 2009
Stats a lot of caches!
- 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.
Friday, August 28, 2009
Cemetery caches - what's the policy?
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.
Monday, July 27, 2009
Submitting caches in advance for an event
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.
Tuesday, May 26, 2009
Get out there and get 'em
Thursday, May 21, 2009
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.
Thursday, May 14, 2009
Power Trails back in the discussion
Sunday, April 05, 2009
No more ALR caches
Logging of All Physical Caches
Geocaches can be logged online as Found once the physical log has been signed.
If it is appropriate for your cache location or theme, you may ask the cache seeker to accomplish an optional and simple task, either close to the cache site (normally within 0.1 miles or 161 meters) or when writing their online log. For example, wear the goofy hat inside the cache container and upload a photograph. Cache finders can choose whether or not to attempt or accomplish optional tasks. Cache owners may not delete the cache seeker's log based solely on optional tasks.
This guideline change applies immediately to all logs written from April 4, 2009 and going forward. Older caches with "additional logging requirements" (ALRs) are not grandfathered under the older guideline. If you own an existing cache with mandatory additional logging requirements, we request that you:
- Cease deleting logs based on additional logging requirements.
- Review your own cache listing to see if the ALR can be made into an optional and simple task, or whether it must be removed altogether.
- Adjust your geocache listing by editing the text then contact a reviewer to change the cache type, if appropriate.
What do you think? Do you (did you) love ALRs and think this is a terrible idea? Or did you hate them and think it's about time they were written out of the guidelines?
Thursday, April 02, 2009
Yesterday's blog post
But wouldn't it be nice?
My thanks to General Disarray, who reviews caches for Oklahoma, for letting me borrow the idea. I understand Heartland Cacher, who reviews for Nebraska, also played this prank in the Cornhusker state.
Wednesday, April 01, 2009
New guidelines take effect today
Cache Size: Cache containers must now be of the one quart size or larger. No “nanos”, matchstick containers, or film canisters will be published.
Cache Content: All caches must contain a logbook (not log sheet) and items for trade. Fast food toys will be added to the list of items disallowed inside caches.
Permissions: As all land is owned by someone, all cache owners must obtain permission from the landowner in writing and fax or email this to me. This will be kept on file for the duration of the caches existence. *fax number to be added to my profile*
New Saturation Guidelines: The .1 mile rule still applies to caches placed within public parks. There is a new guideline for “linear” trails (sometimes referred to as “power” trails). This guideline states that caches must be placed no closer than 3-4 miles apart and must be in a location that will “wow” your fellow cachers.
Logging Guidelines: 1. Physical logbook: your physical log must contain more than just a signature. 2. Online Log: Acronyms are no longer an acceptable way to log online. You must write a minimum of three sentences detailing your experience. Logs containing “TFTC”, “TFTH”, “SL”, etc will be deleted.
As more information becomes available to me I will make it available to you via this site and my profile. Let’s continue to make Iowa the best state to geocache in.

Thursday, March 12, 2009
Cherokee's "Welcome Spring" Event
Friday, February 27, 2009
Today is my anniversary
Thursday, February 26, 2009
Why do people cheat on virtuals?
Sunday, February 22, 2009
La première dérive

My daughter is undertaking an interesting GPS-based project today for one of her art school classes. She calls it Dérive, which is French for drift. Jacey has been geocaching with me a few times over the years, so it's interesting to me to see how she is applying her experience with GPS to create this project. You can read the blog she created for this here. I'm not sure I completely understand what's she's doing, but I'm looking forward to reading about it and viewing her photos.
Saturday, February 07, 2009
Heading home




Thursday, February 05, 2009
The day the music died
Thursday, January 29, 2009
Total caches published
This got me to thinking about how many geocaches I have published. In a post last September, I wrote that I had published close to 6,000 geocaches in my 5+ years of reviewing. I don't recall how I arrived at that figure, but upon checking this morning, IowaAdmin has officially published 6,491 caches since the summer of 2005, which is as early as the "published" log type goes back. I probably published an additional 1,000 in the 12 months before that. And for a year prior to creating my "IowaAdmin" I.D., I reviewed geocaches in Iowa and Wisconsin using the I.D. "WGA2". Because WGA2 is now owned by a different reviewer, I don't have an accurate way to know exactly what my total is. My best estimate is that it's now around 8,000 caches.
Thursday, January 01, 2009
Happy New Year's 2009!

On this first day of 2009, I know that some of my friends celebrated by going geocaching. However, I participated in a different outdoor activity to mark this first day of the year. My daughter and I went kayaking. The weather wasn't great -- 23 degrees, wind gusts up to 30 mph and snow falling -- but the challenging conditions seemed to make it that much more fun. And before you start thinking that we are completely nuts, I should tell you that the lake -- Columbia Lake near Portage, Wis. -- is a cooling lake for a coal-fired power plant so the water temperature is in the 70- to 80-degree range year round. That doesn't make the wind any less bitter when you're putting your kayaks back on top of the car, but it does make the paddling a little more bearable. How ever you celebrated today, I hope you had a good one. Here's to a great 2009! (It's got to be better than 2008, right?)

Friday, December 19, 2008
Iowa had largest cache % gain of any state!
Here are some details. We grew from 2,943 caches on May 30, 2007 to 6,260 caches on Dec. 7, 2008. That was a gain of 3,317 geocaches, which was a 113% increase during those 18 months. That equates to approximately 184 new active caches per month. If you clicked on the link above to my previous post, you saw that our previous rate was 155 new caches per month, so you have really picked up the pace during the past year.
In terms of population, we currently have 209.9 caches per 100,000 population, which ranks us 21st on the list of 143 worldwide regions. (Previously we were at 140.4 and in 28th place.)
Once again, the numbers included in the spreadsheet are ACTIVE cache figures. Reviewers have actually reviewed more caches than those numbers indicate. The numbers are the net of total caches submitted minus those that have been archived and minus those that were not approved for listing.
In case you're interested, the state with the most caches per 1,000 sq kilometers is Rhode Island, with 307.3. Alaska has the fewest caches per 1,000 sq kilometers with 1.6. The state with the most caches per 100,000 population is Utah with 523.5. New Jersey has the fewest caches per 100,000 population at 60.9.
Saturday, November 22, 2008
Roundabouts
Yesterday I reviewed a geocache that was placed in a roundabout (the first geocache in an Iowa roundabout submitted to www.geocaching.com that I can recall).

Think about it -- how distracting would it be to some drivers if they saw someone poking around in the bushes or rocks inside a roundabout when they're already trying to watch for merging vehicles while trying to find their exit? And it's not just me saying this. The Iowa DOT has a web site that gives advice about roundabouts. (I orignally wrote that previous sentence as "the IDOT gives roundabout advice" but that didn't sound quite right.) The IDOT says this: "Never walk though a roundabout or cross the center island."
Bottom line, unless you seek and obtain special permission for your specific geocache from the local governing municipality, I'm not going to publish geocaches that are placed inside roundabouts .
Tuesday, November 04, 2008
Useless hints
Monday, October 27, 2008
Paperwork -- sometimes it works!
ForbiddenYou don't have permission to access / on this server.
Additionally,
a 403 Forbidden error was encountered while trying to use an ErrorDocument to
handle the request.
It appears the ISP quickly realized that their customer was doing some bad things and so they took them down. I don't know if they will resurface on a different URL, but thanks to the power of Google searches, I'll be ready. :-)
Thursday, October 02, 2008
Ripping me off on the web
I feel like someone has broken into my house and stolen some of our stuff. Have any of you ever experienced anything similar?