Register | Login
Attackpoint - performance and training tools for orienteering athletes

Training Log Archive: CleverSky

In the 1 days ending Mar 8, 2020:

activity # timemileskm+m
  orienteering1 1:30:41 5.2(17:26) 8.38(10:50) 23119 /21c90%
  Total1 1:30:41 5.2(17:26) 8.38(10:50) 23119 /21c90%

«»
1:30
0:00
» now
Su

Sunday Mar 8, 2020 #

10 AM

orienteering 1:30:41 [3] *** 8.38 km (10:50 / km) +231m 9:31 / km
spiked:19/21c shoes: Inov-8 Oroc 280 #1 (blue)

Ansonia, HVO/WCOC winter training, Red, 6.5 km, 290 m. Mostly pretty good the woods were nice as usual, except for being a little slow in some recently logged areas where there were a lot of branches on the ground. Visibility was outstanding, and the weather was basically perfect.

Two mistakes, and one clerical error. I was mentally distracted on #2 and missed by just a bit on the uphill side, but I failed to turn and see it; found it just fine on the way back, but the time loss was close to four minutes, moving slowly while relocating. On #17, I was off to the right coming into the logged area, and underestimated the challenge of spotting the stone wall. My first guess as to which was I was off was correct, but after going a little way, I second-guessed myself and went the other way, until I got a better look at the group of boulders in that direction and saw where I was. About three minutes on that one. Also kind of slow on #16 because I was reading the map poorly, and was wrong about where I was, but I kept going in the right direction and "spiked" it.

Then the clerical error. I spiked #11, but then on the short leg to #12, nothing made any sense. I was completely perplexed. I went back to #11 to confirm that it was the right control, but it was on a really unambiguous feature. Tried heading to #12 again, and was baffled in the same way. Adequate examination of the map finally clued me in to what was happening. The course did a little loop at 11-12-13, so that the 10-11 leg passed close to 13. After going to #13, I then tried to navigate as if I were going from #11, but of course that wasn't where I was. Once this dawned on me, I went to the real #11, and everything was fine from there. 7-8 minutes lost on those shenanigans. My split at "11" is therefore bogus, and all of the rest are shifted by one.

15 minutes lost is pretty pathetic. But it's just training.

splits
RouteGadget

« Earlier | Later »