Blue Hills Traverse in Blue Hills, south of Boston. 13.2km course, came in 10 out of about 35. Actually ran 16.1km, 534m climb.
Great fun race. Slightly rainy at first but warm (57 degrees), heavy rain about 30-45 minutes in, then it cleared up and became sunny and 10 degrees cooler. Nice conditions.
Mass start, I took off very quickly but for some reason legs felt quite sluggish on the way to 1. About 8 runners passed me, partly because I took a "shortcut" through some of the green which slowed me down a little.
#2, straight through with no issues, still felt sluggish.
#3, went around on the paths which I think was the better route choice. Slow going up hill...
#4 went W on the path which should have been faster, though I failed to see the path going straight through the green, probably would have been better. The approach was slow on the steep slope, then I hesitated. Lost some time, WinSplits reports 2.44 which surprises me, maybe also because going straight on the path I didn't see was faster.
#5 navigated using the rocky areas as handles and then caught the hill right before the control, no issues.
$6 was a quick sprint. #7 I lost some time on, WinSplits surprisingly doesn't report anything but I probably lost 2 mins, first by straying too far north and even across the stone wall without realizing it at first, then was very hesitant on the final approach to the small cliff, looked for the control for at least 1 minute before finding it practically right below my feet.
#8 was quick except for heavy traffic on the road, had to wait a little before being able to cross. Approached the control from the edge of the dense swamp but it was very runnable.
#9 was also a quick sprint, same with #10 (refreshments, I didn't feel I needed any, just said hi to Jeff who was there). No issues with #11 either, approached it from the path going slightly up the slope.
#12 I took the "tourist route" up the top of the hill, which rewarded me with a glorious view in the sunshine. Wish I could say that was the best route, but should have stayed north on the slope which would have saved me 25m climb. Clearly didn't analyze the contour lines enough. Plus the path up and especially down the hill was very rocky and slow. But the view was great! Tried to make up for it sprinting on the path and approaching the control, but no doubt lost a good 2 mins.
#13 and #14, tried to make up for lost time by sprinting which went well.
#15, had passed JJ somewhere around 13 or 14, and tried to keep up the pace to 15, but came too far to the right and picked the wrong boulder. Turned around and saw JJ at the control 50 m behind me...
#16, for some reason kept pulling right which meant I completely missed the path and had to struggle through some blueberry. JJ gained a minute on me from 14 to 16...
#17, after some initial hesitation decided to go on the paths to the right which turned out very fall, fast running past the lake and to the road. Looked for JJ but turns out I passed him by 2 minutes to 17.
#18 was straight forward. 19, went around on the paths to the north which was quick except for a lot of climb. Think faster than going all the way around to the south though.
#20 was a straight shot. #21 was mostly a road run, except I started cramping and had to slow down a lot.
#22 veered a little to the south and had to climb up the ridge, but not too much lost.
#23 had trouble reading the map due to the "alternate" scale on this section, but found the path which was rather big and then it was easy going into the control.
#24 slower than should have been as I had trouble reading the map, but no mistakes.
To the finish couldn't read the map at all but just aimed south and found big paths.
Overall a good race, not too many mistakes and running speed was "ok", certainly improved from Hudson Highlander - but still a long way to go before I am at what I would consider an acceptable speed. More intense training needed this winter...had some trouble with my eyes, they kept tearing up which is not unusual at the beginning of a race when it is a little cold, but today it kept happening and didn't help reading the detailed map towards the end. Maybe because of fairly strong winds.
Map with GPS track:https://s3.amazonaws.com/oxensnas/Archive/Archive/...