1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2<html> 3<head> 4 5<title>Privacy Policy</title> 6 7<meta name="keywords" content="aspenweaver, Aspenweaver, dreamweaver, Dreamweaver, aspen trees, Aspentrees, geocache, geocaching"> 8<meta name="description" content="From Moab to geocaching, this site is an eclectic mix of adventures and hobbies."> 9 10<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head> 11 12<body bgcolor="#000033" text="#000000" link="#0033CC" vlink="#0099FF" alink="#FF0000"> 13 14 15<table width="740" border="0" align="center" cellpadding="0" cellspacing="0"> 16 <tr> 17 <td><img src="../aspenweaver_logo.gif" width="740" height="45"></td> 18 </tr> 19 <tr> 20 <td><table width="100%" border="0" cellspacing="0" cellpadding="0"> 21 <tr> 22 <td width="10" bgcolor="#f5f5f5"> </td> 23 <td width="130" valign="top" bgcolor="#f5f5f5"> 24 <p> </p> 25 <p class="leftnavbarbold"><a href="http://www.aspenweaver.com"><font size="2" face="Tahoma">Home</font></a></p> 26 <p class="leftnavbarbold"><a href="http://www.aspenweaver.com/geocache"><font size="2" face="Tahoma">Geocaching</font></a></p> 27 <p class="leftnavbarbold"><font size="2" face="Tahoma"><a href="http://www.aspenweaver.com/lavapit">Lava 28 Pit</a></font></p> 29 <p class="leftnavbarbold"><a href="http://www.aspenweaver.com/resources"><font size="2" face="Tahoma">Resources</font></a></p> 30 <p class="leftnavbarbold"><font size="2" face="Tahoma"><a href="http://www.aspenweaver.com/travels">Trips 31 and Travels</a></font></p> 32 <p class="leftnavbarbold"><font size="2" face="Tahoma"><a href="http://www.aspenweaver.com/blog/contact/">Contact 33 Us</a></font></p> 34 <p class="leftnavbarbold"><font size="2" face="Tahoma"><a href="http://www.aspenweaver.com/disclosure.htm">Disclosure</a></font></p> 35 <p class="leftnavbarbold"><font size="2" face="Tahoma"><a href="http://www.aspenweaver.com/policy.htm">Privacy 36 Policy</a></font></p> 37 38 <p class="aspenweaver"> </p> 39 <p class="aspenweaver"> </p></td> 40 <td width="10" bgcolor="#f5f5f5"> </td> 41 <td valign="top" bgcolor="#FFFFFF"> 42 <table width="100%" border="0" cellspacing="0" cellpadding="20"> 43 <tr> 44 <td><div align="center"> 45 <h1><font color="#FF0000" face="Verdana, Arial, Helvetica, sans-serif">Geocaching</font></h1> 46 </div></td> 47 </tr> 48 </table> 49 <table width="100%" border="0" cellspacing="0" cellpadding="20"> 50 <tr> 51 <td><p align="left"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">This 52 page is dedicated to <a href="geocache_build/index.htm"><strong>homemade 53 geocaches</strong></a> that I have stashed throughout the 54 state. As I start hiding them in other states, I will update 55 the page accordingly. </font></p> 56 <p align="left"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">So, 57 what is a geocache? Geocache is a derivative of 2 words- GEO 58 from geography, and CACHE, which is something that is hidden, 59 such as treasure, food, supplies, etc. The owner of a geocache, 60 sets out a cache with items placed inside, among which is 61 typically a notepad and pencil. Using a GPS, the coordinates 62 are noted and then placed on the internet, and geocache hunters 63 try to locate the geocache based on the coordinates given. 64 They then log their name in the notepad and take some of the 65 items left in the geocache and replace them with items they 66 brought. Here's more information on <a href="#" onClick="MM_openBrWindow('http://www.geocaching.com','Geocaching','scrollbars=yes,resizable=yes,width=600,height=600,left=100,top=100')"><strong>geocaching</strong></a>.</font></p> 67 <p align="left"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">My 68 geocaches are slighty different from the usual geocache. I 69 incorporate geocaching in with my 4-wheeling adventures. As 70 a result, most of the geocaches I have hidden require a 4-wheel 71 drive to get to. In some instances, a 4-wheel drive and a
72 hike. Also, I do not give directions on where to go to start 73 the hunt. All I will give are the GPS coordinates and the 74 elevation. With that having been said, I will post pictures 75 of the geocache site as well as the surrounding area. If you 76 can get to within 50 yards or so of the cache, the pictures 77 will help guide you in. No extreme 4-wheeling is required 78 to get to my caches. I have a stock Pathfinder that I use 79 on all my 4-wheeling outings. Most of the roads that I 4-wheel 80 on can be found in <a href="#" onClick="MM_openBrWindow('http://www.delorme.com/atlasgaz/','DeLorme','scrollbars=yes,resizable=yes,width=600,height=600,left=100,top=100')"><strong>DeLorme's 81 Colorado Atlas and Gazetteer</strong></a>. By locating the 82 coordinates I give on the geocache site, and looking in the 83 Atlas, you can figure out which road I went in on. That's 84 the only hint I will give you.</font></p> 85 <p align="left"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Another 86 difference between my caches and the typical geocache- the 87 typical geocache will use a plastic container such as Tupperware 88 to hide the cache in. They then hide the plastic container. 89 Not my geocaches. I build my geocaches to look like rocks 90 and boulders. Here's how I make <a href="geocache_build/index.htm"><strong>homemeade 91 geocaches</strong></a>. The inside of the boulder is a plastic 92 jar which is the cache container. Simply turn the boulder 93 upside down to access the screw-on lid. To me, just setting 94 out a Tupperware container doesn't seem much of a challenge. 95 Again, with that having been said, I will take many pictures 96 of the geocache boulder at various angles and of the surrounding 97 area and post them on the site. Simply print out the pages, 98 a color printer helps, and go hunting. You will know what 99 the boulder looks like and where it is. I want to make it 100 challenging, but still give you a sporting chance. </font></p> 101 <p align="left"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">If 102 you feel my caches are too tough or don't abide by the rules, 103 then please don't go looking for them. They aren't for you. 104 However, if you feel you're up for a challenging adventure, 105 please try to find them and leave the details of the find 106 in the logbook and send me an email. I'd love to hear of your 107 journey.</font></p> 108 <table width="100%" border="0" cellspacing="0" cellpadding="10"> 109 <tr> 110 <td bgcolor="#FFFFCC"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><strong>Disclaimer 111 - please read this...<br> 112 </strong>Use the information provided here at your own 113 risk. Hunt for a geocache at your own risk. I give no 114 guarantees as to the absolute accuracy of the information 115 presented here. This page contains my own personal description 116 of geocaches I've hidden and the locations, and so may 117 differ from your experience of the geocaches if you go 118 hunting for them. I try to place geocaches only on Federal 119 and Government owned land, but I can never be 100% sure 120 of the ownership of the land that I am on.</font></td> 121 </tr> 122 </table></td> 123 </tr> 124 </table> 125 <table width="100%" border="0" cellspacing="0" cellpadding="20"> 126 <tr> 127 <td width="200"><a href="geocache_01.jpg"><img src="cumberland/site1_01_tn.jpg" width="200" height="150" border="0"></a></td> 128 <td valign="top"><font size="2" face="Verdana, Arial, Helvetica, sans-serif">Here 129 is a picture of a homemeade geocache. All geocaches I have hidden
130 are homemade and no two geocaches look alike. Some are large, 131 some are small. I just make them up as I go. Here's how I <strong><a href="geocache_build/index.htm">build 132 geocaches</a></strong>.</font></td> 133 </tr> 134 </table> 135 <table width="100%" border="0" cellspacing="0" cellpadding="20"> 136 <tr> 137 <td><div align="center"> 138 <h2><font color="#000099" face="Verdana, Arial, Helvetica, sans-serif">Geocaches 139 I have hidden:</font></h2> 140 </div></td> 141 </tr> 142 <tr> 143 <td><div align="center"> 144 <p align="left"><font color="#FF0000" size="3" face="Tahoma"><strong><font face="Verdana, Arial, Helvetica, sans-serif">Colorado</font></strong></font></p> 145 </div> 146 <ul> 147 <li> 148 <div align="left"><font color="#000000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><strong><a href="../cumberland/index.htm">Cumberland 149 geocache</a></strong> Offroad vehicle required or 1/2 150 mile hike.</font></div> 151 </li> 152 <li><font color="#000000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><a href="../willowcreek/index.htm"><strong>Willow 153 Creek geocache</strong></a> No 4-wheel drive required. Watch 154 out for rattle snakes!</font></li> 155 </ul></td> 156 </tr> 157 </table> 158 <table width="100%" border="0" cellspacing="0" cellpadding="0"> 159 <tr> 160 <td><div align="center">
160<script language="JavaScript" src="http://lapi.ebay.com/ws/eBayISAPI.dll?EKServer&ai=alozqltvzl&bdrcolor=FFCC00&cid=0&eksize=1&encode=ISO-8859-1&endcolor=FF0000&endtime=y&fbgcolor=FFFFFF&fntcolor=000000&fs=3&hdrcolor=FFFFCC&hdrimage=1&hdrsrch=y&img=y&lnkcolor=0000FF&logo=3&num=25&numbid=y&paypal=y&popup=n&prvd=1&query=geocache&r0=3&shipcost=y&sid=aspenweaver+geocache&siteid=0&sort=MetaEndSort&sortby=endtime&sortdir=asc&srchdesc=n&tbgcolor=FFFFFF&title=Moab+Getaways&tlecolor=FFCE63&tlefs=1&tlfcolor=000000&track=2359316&width=570"></script>
160</div></td> 161 </tr> 162 </table> 163 <table width="100%" border="0" cellspacing="0" cellpadding="20"> 164 <tr> 165 <td> 166 <p align="center"><font size="2" face="Verdana, Arial, Helvetica, sans-serif"><strong>DISCLOSURE: 167 Aspenweaver is a participant in the Amazon Services LLC Associates 168 Program, an affiliate advertising program designed to provide 169 a means for sites to earn advertising fees by advertising 170 and linking to amazon.com. </strong></font></p></td> 171 </tr> 172 </table> 173 174 </td> 175 </tr> 176 </table></td> 177 </tr> 178 <tr> 179 <td><img src="../aspenweaver_footer.gif" width="740" height="24"></td> 180 </tr> 181</table> 182</body> 183
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.