To find my way I'd plotted the route into my GPS (Garmin Edge 500) which only offers very basic navigation (a "join the dots" type system that beeps if it senses you've missed a GPS way-mark). The route was estimated to be about 76miles each way and at an avg speed of 16mph should take between 4.5 and 5 hours.
Given the Arctic spring we've had this year I was avidly watching the weekend's forecast, which ultimately ended up being dry, bright, cold and head-windy. On the Friday night, Lily had missed the point of the trip a little (if there actually was one) and asked whether I would drive there instead if it was raining :)
Around 7:20am on Saturday morning I set off on my road bike with a rucksack of essentials and wearing nowhere near enough layers of clothing - although it was about 2 degrees at the time it was supposed to be nearer 10 later in the morning.
I've always been of the opinion that Lincolnshire is so flat that it makes Suffolk look like the Alps, unfortunately that's only true outside of the Lincolnshire Wolds! Admittedly there's nothing there to rival Alpe-d'Huez but my legs were soon woken up!
I'd planned to have only one rest and refuel stop which would be at the Humber Bridge (just over half way) and to regularly snack while riding to keep me going. The Garmin got me close to the Humber Bridge with minimal difficulty, but once in the urban metropolis of Barton-on-Humber I started to discover the flaws of its basic navigation. While it's fine through the open countryside it's hard to decipher when there are multiple turnings. For instance it will show that you need to turn left, however when there are 3 left turns up ahead it doesn't make it obvious which one to take. Also, the Garmin seemed to think I'd be able to use the service shafts inside the bridge supports (or scale them like Spiderman) and access the bridge that way. Having ignored it's frantic beeping and "OFF COURSE" messages I managed to find my way to the cycle path that crosses over it.
There...
- If you detect that I'm off course, don't blank the screen and replace the route with an "Off Course!" message! At the very least leave the route there, and if possible place an indicator showing where I am in relation to it.
- Also, you could draw the additional GPS points you've logged since I veered off course so I can easily retrace them.
- Trying to animate things on an LCD screen doesn't work well at all, the refresh rate isn't up to it. All I end up seeing is the route flashing on and off as I'm trying to work out which exit to take from a roundabout.
- When I've plotted a course you could identify where junctions are then look at other nearby junctions and add them as markers on the screen as features to help me navigate by.
The Garmin also has a ghost rider feature, this rides the course at your estimated average speed so you can see how far ahead or behind you are. Over the course of the ride we became enemies.
I'd accidentally plotted a bridleway, right at the start of the course. I couldn't pass that on my road bike, so right from the off he had a 2mile advantage. I'd managed to regain that distance by Barton-on-Humber, but while I'd maintained a higher average than him he never went off course so would overtake me every time I did. I regularly accused the cheating little sod of deliberately making the course changes vague so he could gain an advantage. Needless to say the little swine beat me to the finish - by just under 2 miles...
I like to think that, as the miles wound endlessly on, this little game helped to keep me sane but the evidence of the previous paragraph suggests otherwise.
The last 20miles to Selby were very hard psychologically. I've always thought of Gilberdyke and Howden as being quite close to Selby, but that stretch of road just went on and on and on for ever. Each time I looked at the trip computer, the distance didn't seem to have changed - something else I accused the ghost rider of tampering with.
I regularly ride 3/4s of this distance and have ridden much further so I was surprised at how hard I'd found it, I suspect it's because I'm usually on familiar roads and riding with other people.
I reached my parents' at 12:30 and a gigantic Mr C's fish and chips followed by a Doubtfires ice-cream made everything better again. The prospect of having to ride back the next day wasn't very appealing though; my legs were feeling drained and my back-side was very aware of the lack of padding in my cycling shorts.
For the return journey I'd decided to take more rest breaks and fluids, as well as to take it at a more steady pace rather than trying to get there as quick as possible - this time I'd be starting with the flat terrain and ending with the Wolds...
I set out around 7:45am on Sunday and despite taking it steady I was constantly aware that my leg muscles weren't wanting to do anything. Despite that, the distances didn't seem as ridiculously long as yesterday - I think that now I was more familiar with what was coming my expectations were more realistic.
As is the way with these things, the wind had turned overnight so I had a headwind again! Fortunately it was little more than a breeze this time.
And back again...
By the time I'd crossed the Humber my leg muscles had warmed up and although I wasn't exactly powering up the hills none of them stopped me in my tracks and I made it back to Aby around 1:15pm.
The routes and stats are here;
Aby to Selby: http://www.endomondo.com/workouts/173679935/234886
- Moving Time: 4hrs 54mins 21secs
- Total Time: 5hrs 09mins 49secs
Selby to Aby: http://www.endomondo.com/workouts/174100023/234886
- Moving Time: 4hrs 49mins 45secs
- Total Time: 5hrs 22mins 00secs
In the end there wasn't a lot in it time and speed-wise and the return leg only took 10-15 mins longer (including rests) so I'm pretty pleased with that.
Despite all my grumblings about the Garmin, it's a stunning bit of kit and I didn't need to resort to a real map once, I just feel they've made several stupid design decisions that could be very easily improved on.
