|
Post by li1gray on Sept 26, 2008 9:17:25 GMT -9
Well I got an e-mail from the ARR police and and they have asked me to disable my cache along the new trail section "Quick keys"
I've not had any DNFs on this cache and have disabled it but am a little pived as I have called the officer back and he won't return my e-mails or phone calls.
I don't think the cache is really causing cachers to go down on the tracks... I have even updated the wording to tell people to stay on the trail and stay away from the railroad.
Any ideas or should I just go down and pull the whole series I have near the ARR.
|
|
|
Post by ladybugkids on Sept 26, 2008 12:58:37 GMT -9
That's an odd one...the cache is accessed from inside the fence of a municipal bike trail and the railroad has raised concerns?
I think your new wording in the first paragraph serves the purpose to keep people off the tracks. It seemed pretty obvious that one didn't have to leave the path to access the cache when I looked for it.
However, if you choose to remove it, I certainly wouldn't pull down the entire series. The other caches are well separated from the railroad right of way be either Ship Creek or fence along Ship Creek if I remember them all correctly. In fact, for "Quick Keys," if you decide to do anything, you could move it north or south a bit so it's not "on top of" the right of way. The feature where the cache is placed is worth showing off, so I'd keep cachers coming to check it out.
|
|
|
Post by ladybugkids on Oct 3, 2008 6:49:17 GMT -9
At least one other local cacher had a similar contact from the railroad about caches that are FAR outside what the railroad is saying is their 100' right of way, but where the right of way might be crossed or used to access the path to the cache. If you were contacted by the railroad, please send me a copy of their correspondence and a list of the cache(s) they raised a concern about at ladybugs at geocachealaska dot org. There may be a need to have a formal meeting with the railroad to explain Geocaching to them and get clarity on "appropriate" track crossing or right of way proximity. Such a meeting would be held to avoid having the railroad send Groundspeak a list of caches they have a concern about and having Groundspeak archive the whole group, just like happened recently between Groundspeak and the National Park Service in the Appalachian Park corridor in the Eastern states and in Anza Borego in California. See below for more details: Don't ask Don't Tell = bad idea!, Repurcussions for not asking permission on managed land.Appalachian Trail (AT)Caches ArchivedGroundspeak's synopsis of AT Archival--good reading...serves to illustrate how the land manager can and will always make the final call
|
|
|
Post by SSO JOAT on Jun 29, 2010 12:08:32 GMT -9
Is that ROW 100' total or 100' to either side of the tracks?
I noticed a new cache placed in the GeAK highway section that appears to be very close to, and on the other side of the tracks. Just the cache box on the GPSr map as I drove down the highway made me think it was right next to the active tracks and I wondered how it was published that way.
|
|
|
Post by ladybugkids on Jun 29, 2010 16:26:09 GMT -9
The following information is provided on the GeocacheAlaska! Land Manager webpage based on exchanges between cachers and the railroad. "The Alaska Railroad has a legal 100' Right of Way (ROW) on both sides of the centerline of the tracks. Geocaches should not be placed inside this ROW for safety reasons with the following exceptions (per Jim Adams, Alaska Railroad Security Agent): Land on the opposite side of the bicycle trail from the tracks where the bicycle trail falls within the 100' ROW. Land within the vehicle transportation corridor including pull outs that falls within the 100' ROW. These areas are usually delineated by a fence or guardrail. People are discouraged from crossing or walking along the tracks for safety reasons. Note: Groundspeak imposes a 150' buffer between caches and tracks unless specific exemptions are identified such as those above."
|
|