Earthcache Guidelines Updated

The Geoaware team has been working for a month or more on updates to the new guidelines.  There are not actually many changes on the surface.  If you are making your first Earthcache, and you are diving into things you will not have much to worry about.

This goes over some of the changes, and just to describe them.

Purpose

Ultimately the purpose was to clarify things.  Dealing with complaints from cachers, community, land managers, and the review team.  We have a lot of people repeating the same process, and the same errors.  Sometimes cache after cache.  I will toss a few of the small changes, and go through them here.  In the past things may have been interpreted more liberally, so you may hit some roadblocks.

1. Earthcaches must provide an earth science lesson.

This is the shortest guideline (now).  Yet it is the one that I see the most problems with.  What is your cache about?  Does it teach?  These are the core parts of an Earthcache.

Earthcaches focus on the solid earth and the processes that shape it.

That means that many of the things that are submitted do not fit.  Biology, Botany, Zoology, Ecology, Atmospheric observations, Oceanographic observations, Geodesy, Archeology, History, and Engineering, are normally not accepted.  They fall outside the solid earth.  Many get upset at the reviewers, or point at other caches, but currently we do not.

2. Earthcaches must be educational

I see many submissions that do not teach a lesson.  Taking someone to a pretty view, or showing them a cool site is not enough.  Education is the second most important part of an Earthcache.

I see two common errors. Many caches I received take people to a hillside and ask people to tell me the number of a sign.   There is not educational material on there.   The second would be one that someone writes a lot of information on the plants and animals in the marsh.  When the reviewer lets them know that they need to do more, they then add to the 2000 word document another 1000 words and diagrams.  We now have a massive document.

Hint.  Teach people, but stay on topic.  Oh, and don't write a book on it.

Also, if you are a geologist, or know a lot about the geology, look at it from the level of a 14 year old.  You may have to describe a few more things for that level.

3. Earthcaches must highlight a unique feature.

We see many listings that are something that is not unique.  If a cache is written about the erosion of an area, you may not be able to do one on the same cache 30 minutes away. You may be able to if you are teaching something different. 

That said, there can be a few Earthcaches at the same location.  A cache on the stones, and another on the erosion could be at the same location (depending on how they are written up).

The feature should also be unique.  A river stone is not necessarily unique.  In fact this is why waterfalls, glacial erratics, springs, etc are no longer accepted. They are not unique.

4. Earthcaches must have approval from the Land Manager prior to submission

Some parks, cites, forest, etc have developed policies about containerless caches. If they have that policy online please point to that in a log.  If you think that you do not need permission explain why.  Just because the location is public does not mean you do not need permission.

Note for a National Park, you will need written permission.  It is part of the agreement with the National Park Service in helping with the program.  The email should be sent directly to the reviewer. 

5. An Earthcache can be a single site or multiple sites.

You have to have visited to location.  Do not toss out a site that you have never been to.  You may have problems in the review if you have not.  You need to get the coordinates there, and make sure the area is open to the public.  

Your cache can be at one location, or ask people to visit  4-5 locations.  I do not think this means that you can pick one of a number of locations to actually answer the question.  But I would have to see on a case by case basis.

6. Logging an Earthcache requires visitors to undertake a site-specific task which provides a learning opportunity related to the topic.

You must use information from the cache page, and the location, to perform a task to help the person learn. Those tasks needs to be about the geology of the site.  A word off a sign, couning fence posts or stairs, pillars, etc does not have anything to do with geology and will not be accepted as an Earthcache logging task.

That task is the proof of a visit. Photos are still not allowed, and you have to be able to send your answers to the cache owner through the Geocaching profile.  That also means that auto-responders are not allowed.  Why?  You are not maintaining your cache.  You are creating something to take care of the work for you.  Also auto-responders do not allow you to have good logging tasks.  You want an answer like 7, or green.  Not a logging task that makes someone think, or educate.

Also when you submit your cache, place your answers in a reviewer note. 

7. The Earthcache text and logging tasks must be submitted in the local language.

I think the is obvious.

8. Respect Trademarks and Copyright and only use text, images or logos if you have permission.

We have seen more and more caches where someone is copying entire web pages, logo or diagrams without permission.  Many state agencies, or other organizations would like a reference to the book or website where you got the information.  Just because it is on the internet, does not mean you can copy it entirely. 

9. Earthcache sites adhere to the principles of geocaching and Leave No Trace outdoor ethics.

Don't dig a hole, tear up the ground, paint something, or leave a cache or other materials at the cache site.  Try and stay near trails/roads.  Stay away from fragile ecosystems.

10. Earthcaches are submitted through geocaching.com and must meet these guidelines and adhere to the Geocache Listing Requirements / Guidelines and geocaching.com Site Terms of Use Agreement.

Yep.  Simple.

Conclusion

We had a number of problems, small and repeated.  So some tweaks were made.  Sorry for those that wanted photos back. 

On that note.  I was one of the most vocal at first that the photos were needed. Taking them away was stupid. I think that was the term I used.  I now disagree.  This is not a virtual cache, it is an educational experience.  A photo means the person does not have to actually answer the questions, and the owner does not have to actually see that they learn.

Earthcaches is education about geology and this earth.  Not photography, not numbers.  Take some time, and enjoy the world around you.

My reviewer tips of the Day...

I have been tossing out my reviewer tips of the day. I thought i would toss them here as I reach groups of five.

So here they #1 to #5.

Tip from the reviewer #1:

If a reviewer tells you your cache is too close to another cache, then you move it to get it listed, only to move it back soon after publishing, you cache will take a quick trip to the archive bin.

Tip from the reviewer #2:

A summit log is not a cache, a State Park log is not a cache, a Wilderness access log is not a cache, and a guestbook is not a cache. A cache might be placed in, on, or near those, but they are not caches.

Tip from the reviewer #3:

Look at the map, preferably the satellite before submitting. Many times caches appear in the ocean, in a backyard, etc.
Best case scenario: You get a note asking for permission, or if you went swimming for 3000 miles to place the cache.
Worst case: The cache is in the hills and gets listed, people drive and hike for hours, then hate you when you meant W40° and not W41°

Tip from the reviewer #4:

Look before you place.
Nothing is more depressing than telling a cacher. "I am sorry you hiked 5,000 feet in altitude, and put a cache with travel bugs in it, but you are 55 feet from another cache."
or the variation.
"... your cache is in a wilderness area." There may be a reason there is no cache within five miles of that location. You might just want to check first.

Tip from the reviewer #5:

Be sneaky - sort of.
As sneaky as you want, or can possibly imagine with your hides. Try and figure out a way to torment other cachers. Make the hides memorable and thoughtful
Do not be sneaky with your reviewer. Slipping in an ALR, changing Earthcache logging requirements to a photo, not publishing where you say it is, or changing a waypoint of the final too close to another cache. All of these are ways to get your cache disabled, archived, or retracted.

How to annoy your geocache reviewer

This is not meant to be a "how to" but look at how to avoid annoying your reviewer. Some of the things that people do have no effect on me being annoyed, other things drive me insane.  Remember that if you place one cache to be reviewed, that you are only one of 10-60 that are there for me to look at in a single day.

The annoying list - the top 10 for me

10 - You Cheat

I used to like to do puzzle caches, they were fun, and it was great to be able to say, "Yep I found that horribly evil cache and solved the puzzle"  When people found out that I was the reviewer I got a few messages second hand where people accused me of cheating to solve the puzzle.  lt is soo hard, and I am so dumb, that I could not solve it on my own.

This took much of the fun of solving a puzzle away from me.  I have a number of them that i have solved, and I just drive by them.  Someday I will visit them, but I don't know when.

Another variation is that I told someone where the cache was.  I have never told anyone and don't plan that I ever will.  I have been offered money, and steaks, all in jest at events for answers, but I have never given them out.

9 - I was driving through Utah from Florida, and thought this spot looked good for a cache.

Oh crap, how do I deal with this.  When I ask about maintenance often I will get the following answer "I will just archive it when there are problems"  That is when I know I am in trouble.  That is not how the system works, and why we don't want a vacation caches.  It is actually a non-maintenance plan.

I have had a few situations where it was even worse.  Here is a nice exchange

"Yes I will have TomDick&Harry maintain it for me" - them

"Sorry you are within 528' of another cache" -me

"I can't move it, i live a long ways away, please list it, I will not let it happen again." them

"Why can't the person that will be maintaining it for you? - me

"They dont live near there either." - Them

"Sorry, if no one is nearby to move it then you obviously have no maintainer" - me

how can it be worse?

"But I have three travel bugs in there, they will be lost forever." - Them

>>Facepalm<<

8 - I have 20/30/40+ caches to list tomorrow morning - Here they are

It does not happen often but once and a while I get a pile of caches that the cache owner need to be listed for an event, or something special. Usually that "something special" is within 12 hours.  Note to cacher:  It takes time, and you are one cacher out of a dozen or more.  Why should others wait because of you.  Give it some time, plan ahead.

I have also had a cache that needed to be listed by a certain date.  Event caches are that way, or a cache for an event or a birthday, or anniversary.   Too often people don't check their emails when there were problems.  One sent me mean emails when I had not listed their cache, and they had not noticed until right before.  They had not seen my email with problems, did not check if it was listed, and never addressed problems, until it was too late to hit the deadline.

You may also consider your event.  Some like to wait until two weeks before to pop it on the schedule.  Then if I take the weekend to get back to reviewing, then there is a problem with the cache page, you can be too late to get it listed.

7 - I must be the reviewers best friend - At all costs

Don't call me, phone me, appear on my doorstep (except to find the cache there).  I like people, and I like caching.  Yet there are boundaries.  When I am teaching my scouts I dont want my scouts be caching time, or church to be caching time, shopping for grocieries to be caching time, or my family time to be caching.. wait, actually i do want that last one. 

Don't become my friend on every social media, and interject caching into everything.  Sometimes a picture of me and my Dog is just that, for fun.  If I am at dinner, don't ask my if that is a cache container at my plate (it is a glass).  If I am showing a picture of a scout troop, it is most likely not a cache run.  I enjoy talking caching when it is appropriate.  I also like photography, and really enjoy when they naturally go together.  However it is creepy when you turn everything into caching.

Don't read every log I ever made, check every geocaching.com photo, or just follow me around town.  Restraining orders are a pain to get.

6 - Get mad about hidden waypoints, or premium caches, or saturation

I did not place the multi-cache that fills the entire park, or make it a premium cache that you were not aware was there.  I did not place your cache 300' from one that is clearly marked.  I feel bad when that happens, I really do.  Especially to new people.  (I do however laugh mercilessly if it happens to Cold1) However there are rules in place.  I like to review.  If I just listed everything I got I would not be revieweing for long, groundspeak would find someone else.

5 - A long list of coords to check

Ok, you may not know this.  But when I need to check coords for hidden waypoints for others I have to make a cache page. I go through the process like you.  It may not take time to do 1 or 2.  But twenty is a pain in the butt.  Think of how long it takes for youj to make a cache page.  I do not have some magic program that makes them for me. Hmmmmm there is an idea.  This may not seem obvious, but it does annoy me.

Simple way to fix a test cache page is to label it that you are checking coords.  In the additional waypoints that you can add all the other coords that you want to check.  It makes it very simple for me.

4 - The commercial or agenda cache

I don't want to go into the argument of if they are ok or not.  Everyone has an agendas are dear to peoples hearts. Caches about breast cancer, veterans, Senator Charles, President Willy, puppy farms, gun control, or abortion are all troubled.  I don't like arguing the point.  Sometimes I support your agenda, but it is not the place. 

Note: Some get mad if the cache is accused of being an egenda, and we ask you to remove some text to make it ok.  Usually that anger makes it clear that it is an agenda.  For most non agenda caches, asking a needed change would not cause people to get upset.

3 - Complaining about powertrails, micros, hard caches, dangerous, etc.

I dont approve caches, I publish them.  I dont determine that power trails are cool, though I do enjoy them.  If you hate those go to the forums and start the argument.  Note the forum schedule for new complaint threads:

• Monday -  Micros
• Tuesday - Reviewers suck
• Wednesday - Power Trails
• Thursday - Groundspeak sucks
• Friday - Someone Deleted my Log or stole my travel bug
• Saturday - your choice
• Sunday - Bring back virtuals

If a cache is by a dumpster, dont go find it.  If the cache is by a stockyard, or rendering plant and the area smells bad, then drive away.  If it is on a cliff, under a rattlesnake, or hiddeen under broken glass and crack needles, avoid it.  I am not forcing you to get the cache. Complaining to me does little good.

2 - Offensive language

Calling me a whore, slut, or other language that is far more offensive does not make me love you more.  I am not more likely to take your side on that argument, or another argument in the future.  When I archive your cache because it has been ignored, disabled for eight months, or post a warning note, it does you no good to get mad. 

Sometimes I do make a mistake, or jump the gun on an archival.  A friendly email may make me see it from another angle, and angry email just makes me move on to the next email.  Or perhaps I am just testing you to see if you are paying attention, yes, I am sure that is it.

1 - The "I am the only person in the world" syndrome.

Reviewers do not take the job because one person is so great in their area they cannot wait to see their caches and publish them.   If you treat me like trash that is doing this all for you, thenI will ignore you. If you are a pain in the butt, I will look at your last.

When 30 caches come up I go through them one at a time.  If I see issues I come back to them.  If I am on my phone publishing, I will come back to problem caches later when I am at home.  If I am in a hurry, I will list the caches that are simple and easy.  That clears out my queue a little bit, and give people something to hunt for.

The goal is to do the first review of caches in 72 hours. You may see others listed, and yours may have issues.  Look at it closer. It is also possible that I may have also only reviewed 30 out of 100. Yours is still on the way.

If you have issues, you drop to the bottom of the pile.  If I find that there are problems, I leave a note.  Typcially the next day I open and go through new caches first, then go through the emails, and caches on hold.   Don't whine, complain, email hourly, text, call, IM, and post on my wall every few minutes. I go through those that have had issues one at a time.   Usually oldest to newest.

Please email me to remind me if it has taken a while.  It can get buried.  Just don't bombard me.

What people think annoys me that does not

Some people think these bug me.  They usually don't.

Take it to appeals

Does not bother me.  They make the rules, they can bend/break them.  Not me.  They say it is ok, then it is ok. I sometimes point people to appeals, most of the time with no luck.  I think they  believe I am offended by the idea.

Gentle Reminders

I have gone on vacations, walked away for a few days, been buried, forgot to click "watch" on a cache and see your notes.  A simple email does not bother me, and helps me get going.

Pointing out Mistakes

I have had people point to me caches where there are issues. Things that slip by me.  Sometimes they are not serious enough for me to archive, other times they are.  Thanks for letting me know.

-updated for fun- 5/16/13

Update on 2011-10-23 22:00 by firennice

By the numbers

Wow.  That is all i can say... wow....

I was rolling through the numbers and statistics of Utah caches, and all the work I have been doing.  I have not updated my stats page yet, but here is what I have.

In Oct 09-March 10 I looked at about 1950 caches 11 day

In Sept 10-April 11 I looked at 2500 caches 11 day

What is surprising is this year is with a second reviewer.  My first year I averaged about 14/day, this year 13/day.  But once again, two reviewers since last fall, and a busy May is still to go that I would guess will push that number up.

Since September (8 months) We have seen

• 2,000 more traditional caches in the state
• 300 more Mystery caches
• 50 more letterboxes
• 25 more multi caches
• A drop of 9 in the number of Earthcaches to 141
• A drop of 1 in wherigo caches to 4

The total is a total of 2400 new caches in the state, we are approaching 21500 now.   So many so fast.  I think we are seeing an increase in all types, back country, desert, city, and trails.  A mix of them all.

I remember starting and thinking, man there are a lot, and that was then.

Another idea of how much work we do is the number of notes we leave on caches.  My first year I  listed 1200 notes, I am at 1100 now.  Those are almost all caches that we are working on.  Caches that we respond to issues with, not counting emails, that i don't track.

In all, it is busy and fun, and only getting busier.  

I will update my stats soon. Enjoy all.

Update on 2011-04-29 22:12 by firennice

2nd reviewer for Utah

Soon you will see a new reviewer pop up in Utah.

Happily there will be another person to help with the load and share some of the fun.  I will let that person introduce themselves and surprise you when they are ready.   I gave a hint at the event today.. I will share with everyone now.  They have an E in their caching name or their reviewer name.   No it is not much, but I promised a hint, so there you go.