September 30, 2014
August 07, 2014
Here is my .gpx file from last years RideLondon 100 in case anyone wants the route for their Garmin. Can’t guarantee it will be the same as this year but it looks like it will be.
Looking forward to this years event, although the weather forecast looks somewhat interesting at the moment!
July 01, 2009
Have been very lucky to get in some great mountain bike riding over the last few weeks. Couple of really good rides (albeit challenging and tiring ones!) in the Peaks including riding down Jacobs Ladder (which I was really pleased I managed to ride without coming off in a massive and very painful way!!).
Couple of nice loops nearer to home with friends over the weekend (photos), unfortunately Kat came off her bike recently and has bruised herself quite badly – which she is annoyed about as is having to hide her legs in the hot weather we are having at the moment!!.
Now back to the office and the realities of work (it would be nice to just do an epic day ride every sunny day in the summer wouldn’t it?!!!)
March 22, 2009
Filed Under (Mountain Biking) by Ollie Cronk on 22-03-2009
Discovered a great new route from Beedon up towards the Ridgeway and Wantage today that I thought I’d share on Google Maps (I just wish they included an OS layer so you can see the bridleways/byways). There’s loads of possible variation in this route including more of the ridgeway for example…
I’ve also recently found http://www.worldcommute.com/ which is worth checking out if you want to calculate and track cycling instead of driving to work and for other trips.
February 16, 2008
…plotted on Google. Really mixed terrain and views. Decided to extend a loop round the village out to Greenham Common (ex USAF base) which is now a Nature reserve/ex runway play area. Only annoying thing about google maps is that they don’t have RoW marked on them (just roads). Hopefully this will change soon (although maybe they’d have to switch to using to Ordance Survey cartography?)
p.s. Whilst putting this route together my laptop froze. Turns out firefox was using 1.5GB of RAM (yes just firefox – see screenshot below!) Turns out having Firebug switched on whilst using Google Maps isn’t the best of ideas!