Search Website
This form does not yet contain any fields.
    Stuff - Wee links
    « Thoughts on Earthcaching | Main | Camp Hobe and Geocaching. »

    ET Returns

    Well after the sudden demise it looks like the ET Highway is on round two.

    With the listing of a new event, and a google doc explaining a few things, the ET powertrail looks to be returning.   There were a number of issues with the first one, and possilby some misunderstandings, that led to the archiving of the ET Powertrail. 

    Now that those issues appear to be worked through the trail looks to be returning in the next few months.

    How it came about

    It came about after a trip to Geocoinfest here in Utah about two years ago.  On the trip they decided to do the Shakespear/McGuiver powertrail.  (Now expanded a few hundred caches to the Seinfield series as well that makes up about 400+ Caches).

    They had so much fun they decided to do their own powertrail. So for their eight hour trip home they planned and worked out the bugs for their own powertrail.  So after a number of months they finally got things finished and the cache placed.

    International Visitors

    Like our local series there was an explosion of travelers.  Even more than we saw here.  The appeal of 1000 caches drew people in, from all over the world.  It is interesting to follow one cache in the trail and then look at where all the people are coming from.

    In fact the Nevada powertrail had so many visitors that the hotel that normally lays people off and has few  visitors during the winter months was still busy.  That was the ideal time for people to go and avoid the head of the summer.

    Problems and Archival

    As with everything a few people can ruin it for everyone else.  We know those, people that destroy and area to find the cache, or tear things up for fun.  The same was here.

    NDOT was having many problems.

    • Cachers not pulling completely off the road
    • Cachers not paying attention and pulling out in front of traffic
    • Cachers stopping IN construction zones while work was be done
    • Caches in blind spots or not optimal viewing for approaching cars
    • Caches in/on/near guard rails and mile markers. 

    There was a stretch of highway that went through a pass that didn’t have a long clear view of the road ahead.  When we placed the caches in this area, we were careful to make sure cachers could safely pull off the road and not to put caches on blind corners.  This was fine in the summer, however; in the winter, this is a much different story.  Due to the elevation, highway 375 gets snow.  The snow along with guardrails, windy roads, made a small stretch reason for concern.  There was an incident where a cacher’s vehicle and a snow plow had a close call in this area.  I received a call from the supervisor of NDOT telling me of the incident.  We archived the caches in that area within hours of the notification.  However, the supervisor also notified Groundspeak that day or the next...The day after I got the phone call, caches were being archived.

    New update

    They have had a number of complaints from geocaching, and the local businesses about the archival.  Leading NDOT to issue a statement that they had no issue with the trail they just wanted to solve some of the problems.

    So late august be ready for the arrival of 1500 caches.  They have worked with NDOT, County commissioners and the community to place these, safely.

    So those that want to go... enjoy and have fun.

    and be safe.


    Update 6/7/11

    If you are interested to place a trail.. some hints are in this story.


    PrintView Printer Friendly Version

    EmailEmail Article to Friend

    Reader Comments

    There are no comments for this journal entry. To create a new comment, use the form below.

    PostPost a New Comment

    Enter your information below to add a new comment.

    My response is on my own website »
    Author Email (optional):
    Author URL (optional):
    Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>