I'm spending this year (2024) attempting to produce definitive maps for many of Cumbria's races. As a minimum, there will be a map for use on race day and a suggested route in gpx format for you to use on a recce (see note below).
When it's the 'full works' the map will show alternatives and route tips, there will be further route tips in a separate text file and sometimes a file of schedules for several target times derived from the results of previous races.
I've grouped the races by their length (Short, Medium and Long) plus a group for show races (including shows, shepherds' meets, sports days, etc.) and another for the Hodgson Brothers Mountain Relay. If you can't find a race in the distance categories have a look in the Shows group.
Many of the routes I've recced and raced myself but I've also used the ideas of other runners gleaned from Strava. I plot the route using Google Earth. Most of the time I can see the trods on the ground but there are areas where the resolution is too poor and I then have to approximate using the traces from my own runs and those of others. I'm sure there are times I'm following shadows rather than trods! Tree cover is also a problem but so will it be for your GPS receiver! I then import the route into Memory-Map to display it on the Ordnance Survey map. Note that there can be slight discrepancies between Google Earth and Memory-Map. For example, if the route is on the right of a fence in Google Earth it may appear on the left in Memory-Map. Another example, in the Kentmere Horseshoe race, you leave the Garburn Pass track just before a beck but in Memory-Map it appears to be just after. Usually, these differences are too small to see on the race map I produce, but if you import the gpx into a mapping app you may see similar differences. I've yet to determine if one is more accurate than the other!
The basic maps are produced using Memory-Map alone, which has a few foibles. The arrows shown on the route line appear in odd places or sometimes not at all and when a route returns along the same line the arrow heads can combine to look like crosses. For the more detailed maps the annotation is done using Microsoft Word.
I've sometimes given the bearing when leaving a summit, usually shown arrowless, which may only apply for a short distance and also bear in mind the checkpoint location may vary a little from one year to the next which will change the leaving direction.
Note on recces
Several races begin by crossing farmland which is not accessible except for the race so best not to cross this when on a recce to avoid jeopardising the race.
Darren Parker (CFR Statistician). Let me know if you spot any errors or have suggestions for lines worthy of a recce.
I've grouped the races by their length (Short, Medium and Long) plus a group for show races (including shows, shepherds' meets, sports days, etc.) and another for the Hodgson Brothers Mountain Relay. If you can't find a race in the distance categories have a look in the Shows group.
Many of the routes I've recced and raced myself but I've also used the ideas of other runners gleaned from Strava. I plot the route using Google Earth. Most of the time I can see the trods on the ground but there are areas where the resolution is too poor and I then have to approximate using the traces from my own runs and those of others. I'm sure there are times I'm following shadows rather than trods! Tree cover is also a problem but so will it be for your GPS receiver! I then import the route into Memory-Map to display it on the Ordnance Survey map. Note that there can be slight discrepancies between Google Earth and Memory-Map. For example, if the route is on the right of a fence in Google Earth it may appear on the left in Memory-Map. Another example, in the Kentmere Horseshoe race, you leave the Garburn Pass track just before a beck but in Memory-Map it appears to be just after. Usually, these differences are too small to see on the race map I produce, but if you import the gpx into a mapping app you may see similar differences. I've yet to determine if one is more accurate than the other!
The basic maps are produced using Memory-Map alone, which has a few foibles. The arrows shown on the route line appear in odd places or sometimes not at all and when a route returns along the same line the arrow heads can combine to look like crosses. For the more detailed maps the annotation is done using Microsoft Word.
I've sometimes given the bearing when leaving a summit, usually shown arrowless, which may only apply for a short distance and also bear in mind the checkpoint location may vary a little from one year to the next which will change the leaving direction.
Note on recces
Several races begin by crossing farmland which is not accessible except for the race so best not to cross this when on a recce to avoid jeopardising the race.
Darren Parker (CFR Statistician). Let me know if you spot any errors or have suggestions for lines worthy of a recce.
Here is a calendar containing most of the races in Cumbria, a few from just outside, plus some classics from around the country I should do at least once in my life, and some ultras I might try if I can get past the hype and expense. I've not included races in the winter leagues of Helm Hill or Black Combe. Don't take my word for it - check all the details yourself!
Non-CFR version - Race Calendar Cumbria non-CFR 2026
Note, the spreadsheet will always asked to be saved because race dates are compared with the current date and the colouring is modified.
The 'Help' sheet explains the contents of each column but a quick summary of what's included is:
Non-CFR version - Race Calendar Cumbria non-CFR 2026
Note, the spreadsheet will always asked to be saved because race dates are compared with the current date and the colouring is modified.
The 'Help' sheet explains the contents of each column but a quick summary of what's included is:
- Date/time, race name (links to FRA page), category, distance and height gain, record and predicted time.
- Organiser (links to their website), name of reg/start location, its grid reference (links to Streetmap) and its lat/lon (links to Google Maps showing the driving route from Cockermouth - you can change the starting location and copy the formula down), distance and drive time from Cockermouth (these won't update if you change the starting location).
- Entry details - costs of entry on day (EOD) or pre-entry (PE). If PE, entry platform (and link if available), date when entries open and close (if known or assumed from last year's).
- Conditional formatting - the first 3 columns are highlighted yellow if the race is within the next 30 days and the first 5 columns are highlighted grey if the race has already happened. The 'open' date is highlighted yellow if entries are open and the 'close' date is highlighted red if it's less than a month away and both are grey if the closing date (or race) has passed.
- Three different styles of calendar are available for printing off and putting on your fridge. You can choose which races to display.
- A graph of the cost per hour of running time verses the running time of a race - a measure of the race's value for money. By this metric, some of the ruinously expensive long races such as the Spine and Northern Traverse are quite good value! The Dragon's Back is in a league of its own. Making the axes logarithmic spreads the points out.