I decided to hike Camelback Mountain today — I’ll try to make this short (shorter than the 1 1/2 hour hike up & down the toughest mountain I’ve done in the Valley).
I couldn’t remember where to go so I looked it up on the internet & then dispatched myself via my Garmin from my PC:
Then I created a landmark as well, while I was at it (note I put the “route me here” address where it should go, but then I outlined the whole mountain) :
Then I routed myself there with my Garmin by wirelessly dispatching my vehicle’s Garmin to that location:
Turns out it was the wrong entrance — I go to the other one typically, so I drove around aimlessly finding that, plus the REI sports place where I bought a new water backpack (called a Camelbak, coincidentally…) .
Running an efficiency report, I ran 58% more time and 20% more miles (since the miles I went extra were on surface streets, not highways, this makes sense):
Here is my driving around aimlessly, wasting time & fuel (green dots, vs. blue “optimal path”):
Then I get to Camelback, and send a couple SMS notes when I start, get to the top, then get back to the bottom:
Here is my track of the 1 1/2 hour climb to the top and back (using an EZ-1000 at 10 second updates):
Here is an iPhone picture of me at the top, mapping both my iPhone GPS location (blue) and the EZ-1000 location (red pin):
But here is the good part:
Toward the bottom:
And at the top:
I’m a little sore after the 1 1/2 hour long trek up & back down, but the view is worth it.
And I even wore a GPS Insight hat…
Rob.
November 9th, 2009 10:00 am
[...] I decided to take my 9 year old, Jack, to Camelback mountain yesterday. I was curious how much longer it would take than the last time I went. [...]