Join Ride with GPS and discover even more new routes and riding buddies. Print turn-by-turn cue sheets so you know where you are heading. And then, log your rides and watch your progress.
The ride started off well, although it is necessary to pay attention if keeping up near the front as a "peleton" forms behind the pace car and not everyone is giving due care to riding a consistent line.
I had an odd mechanical problem an hour into the ride (at mile 21.5) when my chain came off to the outside of my big chain ring and wedged in against the crank. I cut my index finger trying to tug it out, and fortunately a couple of old timers in a SAG vehicle came by and took over for me. It looks like I was only waylaid for a little over 7 minutes, but it felt a lot longer as the group I had hoped to work with were long gone, and many riders passed me by.
Rode solo much of the time, basically after getting to the climb up Geysers Rd. at mile 74. However, notwithstanding having lost the group with which I had hoped to ride, I did get into a reasonable pace line for the nearly 40 miles of relative flat riding in Napa County after descending from the Trinity climb (ending with the climb up Geyers Rd), averaging just over 20 mph. (A smaller, slower group after the rest stop at mile 53.6.)
Before lunch, I only had 5 min of stopped time, not including the 7 min. for the chain mechanical; an avg. of 16.5 mph for 110 mi & 8200' of elevation gain.
20.5 min stopped at Geyserville lunch stop on Skaggs Srings Rd; it appears that the temperature went up about 10°F there; I wanted to leave more quickly, but I felt I was low on calories and drank 2 cokes and had some sandwich meat and cheese. A good athletic tube-sock with ice around the neck is needed here.
I did not do too badly with the heat, and I took LOTS of Endurolytes, but I should probably have had some of my cal-mag supplements as I felt the hints of leg cramps on The Wall and the climb up from Ft. Ross. I still had leg strength but it felt like I had to spin easy to avoid serious cramping. The bigger problem was I felt a little bonkish, too. I was able to peddle at a reasonable speed on the flats, but I was not able to power over rollers on CA-1.
So, following the lunch stop, there was 90 miles and 9700' of elevation gain, and I managed an average of only 12.5 mph and had a whopping 31 min. of additional stopped time!
When climbing on the first half, my avg heart rate was consistently around 155 bpm on both Trinity and Geyers Rd, but dropped to 145 on the first part of Skaggs, and 135 on the second part. 145 bpm on the segment of my best effort on "The Wall", but I started looking for the outside of the ramps on curves there, a practice I continued on the climb from Ft. Ross. My avg. pulse was more like 135 bpm on the climb from Ft. Ross; I even resorted to walking a couple of particularly steep pitches, and doing some serpentine climbing. Clearly I was losing the ability to sustain power later in the ride. I don't know how much of that I can blame on "de-training", with only having a couple of rides in the preceding 3 weeks following the Eastern Sierra Double (short and easy on June 1, and the Son of Death route unsupported the week before, which kicked my butt). (See: http://www.cyclingweekly.co.uk/fitness/training/detraining-the-truth-about-losing-fitness-22330)
I did not start my Garmin until 0.37 miles after the start.
I have saved many "segments" of the ride for ease of reference of different sections of the ride, and the location of some of the rest stops. (Scroll down the left panel of the screen.) I suggest that care should be given to coordinate with the core members of a suitable pace line to get in and out of the rest stop in Calistoga together.
By: | dhartson@gmail.com |
Started in: | Sonoma County, CA, US |
Distance: | 199.2 mi |
Selected: | 199.2 mi |
Elevation: | + 17932 / - 17931 ft |
Moving Time: | 13:47:15 |
Page Views: | 83 |
Departed: | Jun 20, 2015, 5:29 am |
Starts in: | Sonoma County, CA, US |
Distance: | 199.2 mi |
Selected distance: | 199.2 mi |
Elevation: | + 17932 / - 17931 ft |
Max Grade: | |
Avg Grade | |
Cat | |
FIETS | |
VAM | |
Ascent time | |
Descent time | |
Total Duration: | 14:50:29 |
Selection Duration: | 53429 |
Moving Time: | 13:47:15 |
Selection Moving Time: | 13:47:15 |
Stopped Time: | 01:03:14 |
Calories: | 11784 |
Max Watts: | |
Avg Watts: | 234 |
WR Power | |
Work | |
Max Speed: | 52.1 mph |
Avg Speed: | 14.4 mph |
Pace: | 00:04:28 |
Moving Pace: | 00:04:09 |
Max Cadence: | 218 rpm |
Min Cadence: | 10 rpm |
Avg Cadence: | 62 rpm |
Max HR: | 167 bpm |
Min HR: | 86 bpm |
Avg HR: | 130 bpm |
Heartrate zones: | |
Zone 1: | 3 hours 30 minutes |
Zone 2: | 3 hours 47 minutes |
Zone 3: | 2 hours 36 minutes |
Zone 4: | 41 minutes |
Zone 5: | 0 minutes |
Best format for turn-by-turn directions on modern Garmin Edge Devices
Best format for turn by turn directions on Edge 500, 510. Will provide true turn by turn navigation on Edge 800, 810, 1000, Touring including custom cue entries. Great for training when we release those features. Not currently optimal for Virtual Partner.
Useful for uploading your activity to another service, keeping records on your own computer etc.
Useful for any GPS unit. Contains no cuesheet entries, only track information (breadcrumb trail). Will provide turn by turn directions (true navigation) on the Edge 705/800/810/1000/Touring, but will not have any custom cues. Works great for Mio Cyclo. Find GPS specific help in our help system.
Estimated Time shows a prediction of how long it would take you to ride a given route. This number is based on your recent riding history, and represents an estimate of moving time. Each time you upload a new ride, your Estimated Time profile will adjust to reflect your most recent riding. Only rides exceeding 10 miles (16 km) will affect these estimates.
Go BasicOur Basic members have unrestricted access to everything we offer in our mobile apps. Learn more by visiting our Compare Plans page.
Tell us a little about yourself
Rock solid GPS logging, helpful navigation, live logging and more are all available when you install our app.