Route to Christmas: Day 2 2009

We have got a really long and challenging leg from the USA in todays Route to Christmas – with a best time of around 18 minutes. Todays leg in Route to Christmas 2009 is leg 8 from the Blue course in Return to Boggs Mountain A-Meet at May 3rd 2009.

The leg is as usually first provided without routes – you may take a look at it and think about how you would attack this leg (if the image is too small, you may click on it to get it larger):

Webroute

Next you can draw your own route using the ‘Webroute’ below. Think through how you would attack this leg, and draw the route you would have made. Some comments about why you would choose a certain route are always nice for the other readers.

Routes from Routegadget

Finally you can take a look at how the runners who have drawn their route choice solved this leg:

Complete map in Omaps.worldofo.com

You find the complete map and Routegadget info in omaps.worldofo.com at this location. See also other events in Boggs Mountain in Omaps.worldofo.com.

Omaps.worldofo.com

The ‘Route to Christmas’ series at World of O was very popular the two last year – and I’ve therefore decided to continue the series this Christmas as well. If you have got any good legs in RouteGadget from 2009-competitions – or old forgotten ones which are still interesting – please email me the link at Jan@Kocbach.net, and I’ll include it in Route to Christmas if it looks good. Route to Christmas will not be interesting if YOU don’t contribute.

There will be no analysis about the best routechoice for each leg – you can provide that yourself in the comments or in the Webroute. Not all legs are taken for the interesting routechoice alternatives – some are also taken because the map is interesting – or because it is not straightforward to see what to do on a certain leg. Any comments are welcome – especially if you ran the event chosen for todays leg!

Note that there may be some errors in the Routegadget data (sometimes somebody draws a route for another runner just for fun). Please add a comment below if you spot en error.