WIOL #5(ish) at Shoreview
This race was ok, I was just slow.
In the beginning, I was outrunning my navigation, so I'd have to slow down for a couple steps to figure out where I was going next. (1, 2 and 3 were all less than ~100m of the previous.) Towards the end, I was slowing down, a lot. I was winded after the first 3 or 4 controls. I need to be less of a pansy when it comes to running in cold weather; not running because it's cold isn't going to be an option next year. I need to pay more attention to contours where the trails aren't clear; this is especially true after big storms, like the one we just had. Both of the two controls that I didn't spike were because I was confused by what the paths were doing.
Control by control:
Start to one, one to two were fine. Very short legs. I could've saved a couple seconds by reading more ahead after I had seen one and was running down the path towards it. Two to three, I decided to climb up the steepest hill in the park, and had to bodily haul myself up by grabbing on to the roots of the ferns. I'm not sure if there's a better route choice... the thing is, on the map that section doesn't look that steep - you're supposed to gain 10m over 50 or 75 meters, in reality it was steeper than that. None of the other routes look significantly less steep. I think this may have been made worse by all of the rain we've had recently. Other people (including Huw) had problems with this on this leg, so moving on. After I got to the top, I was completely disoriented, and had to stop and figure out where I was. I passed Steven here, and used contours to reasonably quickly figure out what was going on, and press forward. I spiked four and five, you ran along the trail, took a left, and it was there, turned around, followed the trail back, and you're at five. Six was harder, I ended up just not paying attention to the trails, running to the parking lot, and then running back to the trail that 6 was on. Going straight there would've saved me... maybe 100m? But I think this was faster because I didn't have to worry about navigation. 6-7 I just ran down into the parking lot, ran to the first staircase, ran up it, got on the trail (passed Max), spiked 7, ran up the next staircase and across the parking lot and spiked 8, ran across to 9 (I elected to climb over a small wall instead of going up two flights of stairs. It looks like there's a route around that's slightly longer but avoids both of these; I'm not sure if it's better.) 9 to 10, ten to eleven no problem, just ran across the campus to 10, and ran across the parking lots and down the road to 11. 11 to 12 I ran down the parking lot, got on the small trail, and followed it. 12 to 13 I tried to cut through, got slightly confused as to which trail I was on, then remembered to look at the contours, and figured out where I was going, got to 13, but I thought it was the wrong number, so I ran down a bit to the trail, determined I was exactly at the right spot, looked again and saw I had looked at the wrong control code and I was in the right spot, punched it and continued on to 14. 14 I just ran there on the trail. I got to fifteen by following the parking lot to the end, getting on that trail, and then barreling down to the baseball field, and then ran south, picked up 15, and started to 16. I ran halfway along the enclosed area, ran through the path in the middle, hit 16, and then ran to the finish. Done! But very, very slow.
Three and 13 were the ones I failed to spike.
My definition of to spike is "carry out your planned route (as long as it's a reasonable route) without hesitating." Do other people require that it has to be the optimal route? or have other definitions?