@Challengers I just checked the stats, and we’re only 20.9 miles from 15K miles run!!! Who lives close to courses and can log a few miles before midnight?!?
So close! I think we can round up in informal speech—I’m sure we all logged enough extra miles getting lost to account for the missing distance.
After I cleaned up some spurious duplicate entries to make sure they didn’t affect the team standings (they didn’t), the total dropped a little to 14,959.2. But I’m still calling it 15,000!
1 Like
@adamengst What is the actual distance of Lick Brook/Treman FLT?!? I bet we made to 15K with that!
I don’t know—we’d need to take a measuring wheel out on the course to know for sure. The problem is that everyone’s GPS claimed it was more than 13.1, but I built the RunGo directions from Pete Kresock’s longer GPS track and by the time I had finished smoothing it—bringing all the outlying points back onto the trail—it had dropped back to 13.1. So I don’t really trust the GPS distances.
Wow, I had no idea what went into measuring these courses! I was just trying to come up with a way to make it ‘officially’ 15K, but in the grand scheme of things, it really doesn’t matter.
Heh. We do adjust the distances after people have gotten out on a course if it seems that there’s a consensus that the mapping software is off, but it’s mostly just a matter of getting close. 
I’ve tried measuring it out using the official FLT interactive map. There’s no way to pinpoint an exact distance, but my best estimate is 9.5 miles for the Treman side + 4.0 for the Lick Brook side = 13.5 total.
My Suunto 9 watch consistently measures it at 14.0 to 14.1, but it’s definitely been measuring about 5% long since a software update last year.
Bummer, we still wouldn’t have made it.