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.
http://www.inlandempirecycling.com/HemetDC/index.htm
The route is much nicer than what I had in mind from my experience a few years ago. My poor idea of the ride may have been due to personal circumstances that day, and my general preference for winding roads with lots of trees. This is a relatively flat route, and it was a windy day, but the roads were evidently repaved late last year and the route seemed quite pleasant to me the majority of the time, my navigation errors and the wind notwithstanding.
I rode at a relatively easy pace most of the day and, together with the late start and the time lost due to going off-course (2x), I also rode solo all day. John Clare and Margaret left not too long before me and I caught them at the second rest stop where I also found Rob Kelly, who had just arrived at the start as I was ready to leave. However, I went off-route the first time not too long after they left that rest stop, and I never saw them again.
2 navigation errors, one during each of the 2 loops, cost me an estimated 1 hr 50 min, including at least 15.5 miles and 400' extra credit. A significant component of the lost time was used up while determining how to navigate back to the route.
I only decided at the last minute Friday night to ride this, and I was already not going to get enough sleep, so I did not have time to try and correct my route map from some years back (the ride's route has since been modified). I made a quick search for an updated map, and downloaded it to my Garmin Edge 800. With the two loops intersecting each other, the route should really be loaded as two different courses in order to avoid problems with the Garmin providing navigation, which is exactly what happened to me.
In fact, the Garmin froze and lost a lot of the data, so this track is what my iPhone 6 Plus recorded using the RWGPS app!
Data on Navigation Snafus:
1st loop, off-course: mile 81.4 (should have made left turn onto Railroad Cnyn Rd instead of continuing onto what became Mission Trail), to RS#3 at mile 93.8
- 12.33 mi; 1:07:20; +684'/-526' (incl. 15:54 stopped time to navigate way back to route: 12:46 initially, & another 1:10 a mile short of RS#3 to double-check position)
- correct route: 6.7 mi; +473'/-343'; est. 0:29:20
> lost approx. 38 min
> est. extra credit: 5.6 mi & 210'
2nd loop navigation error:
cost me 1:12:34 (115.0-133.9)
- this included 8.9 miles by car, which I deleted from the GPS track; by deleting the data from this track, the track now shows a straight line which only slightly reduced the mileage to 8.4 miles, so I manually entered the distance to deduct the 8.4 miles. The metrics include the 95' of elevation gain which I am unable to deduct manually.
- the car ride was 8.9 miles and took 9:12 driving time, plus time loading and unloading the bike, etc. [3:46 stopped to hitchhike and load (in car from mile 124.923 to mile 133.870); 3:30 unloading until peddling]
- stopped time before deleting car ride: 2:37:34
- deleting car ride data from GPS track: 8.9 mi; 246'/-155'; 9:26, including 0:18 stopped (red light)
- after deletion, segment shows 8.4 mi & +95'/-0'; 12:44 stopped time
More blather:
I "rode through" (i.e., all night with no sleep or nap stop) with Judy and Jeff on a 600k Wednesday & Thursday; my legs were sore from the 600k because I rode the end of the 600k hard when my legs finally kicked in, and my legs were quite sore still on Friday. I started the Hemet double last, excepting only Rob Kelly who arrived to register as I was ready to leave.
The first time I went off route, I took Bundy Canyon to cut over the hills to get to the third checkpoint.
In the second instance, I mistakenly recalled a right turn when it was actually a left turn and neither the Garmin nor the RWGPS app notified me that I was off course because the actual route used that stretch of road at other times in the ride. Unfortunately, I had lost the route slip before I made it to that turn so I rode 8-9 miles before RWGPS told me to make a turn that was clearly erroneous; it was actually the turn for home near the end of the ride, and I was going to have to retrace my steps to the route. I bought a Red Bull and actually hitchhiked back to the intersection where I went the wrong way. An extremely nice young lady picked me up on her way home from work as a customer service person at a Jiffy Lube. With her help I was back "on route" much more quickly than would otherwise have been the case, and I had started to catch other riders within 35 miles or so, making good on my promise to the office staff that I would not be the last person to finish the ride.
By: | dhartson@gmail.com |
Started in: | Hemet, CA, US |
Distance: | 219,5 mi. |
Selected: | 219,5 mi. |
Elevation: | + 7726 / - 7752 ft |
Moving Time: | 13:52:39 |
Page Views: | 61 |
Departed: | 16 apr 2016 06:37 |
Starts in: | Hemet, CA, US |
Distance: | 219,5 mi. |
Selected distance: | 219,5 mi. |
Elevation: | + 7726 / - 7752 ft |
Max Grade: | |
Avg Grade | |
Cat | |
FIETS | |
VAM | |
Ascent time | |
Descent time | |
Total Duration: | 16:39:21 |
Selection Duration: | 59961 |
Moving Time: | 13:52:39 |
Selection Moving Time: | 13:52:39 |
Stopped Time: | 02:46:42 |
Calories: | 11351 |
Max Watts: | |
Avg Watts: | 203 |
WR Power | |
Work | |
Max Speed: | 46,9 mph |
Avg Speed: | 15,8 mph |
Pace: | 00:04:33 |
Moving Pace: | 00:03:47 |
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.
Vertel ons iets over uzelf
Rock solid GPS logging, helpful navigation, live logging and more are all available when you install our app.