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

Training Log Archive: cedarcreek

In the 7 days ending Feb 28, 2015:

activity # timemileskm+m
  Orienteering1 55:42 2.17(25:42) 3.49(15:58) 120
  Course set-check-pick1 5:22 0.13(39:59) 0.22(24:51) 1
  Total2 1:01:04 2.3(26:32) 3.71(16:29) 121
  [1-5]1 55:42

«»
1:01
0:00
» now
SuMoTuWeThFrSa

Saturday Feb 28, 2015 #

1 PM

Orienteering race 55:42 [4] 3.49 km (15:58 / km) +120m 13:37 / km
shoes: Icebug MR2 Bugrip Snow

Miami-Whitewater, Yellow course, set by Mike Minium.

It was warmer than I had imagined it would be. The forecast was a bigger mental barrier than I'd like to admit. I was not looking forward to being at the computer in *that* kind of cold, so I had a plan: Do a course, no matter what.

Brown was the obvious choice. But Brown was more popular than expected and we ran out of maps. I could have copied the course onto a master, but O Joy did Yellow, and I inferred that she was a bit embarrassed. Now, I'm not embarrassed at doing the Yellow course, in fact I've done it twice at the Flying Pig to check out complaints. And both times were awesome. But I am embarrassed when I win it. So. Yeah.

We ate at the same Chinese place as last year or two years ago. I've been craving their vegetable Pad Thai, which was amazing last time. My praise got one or two other people to try it with me, and it wasn't as good as last time, but I still enjoyed it.

I've been staying up late processing lidar for various projects and people. Dave Waller has suggested that I write up something or plan to do a class. I'm surprised at how good other people are at working with lidar, who are basically in the same boat as me, picking it up a bit at a time.

A few recent successes:

Getting unclassified North Carolina data and running it through a lastools workflow to get data the software will recognize.

Converting lidar data out of a weird county-specific projection and having the data line up correctly. This was a success because the county projection wasn't pre-programmed in lastools. I had to type the projection definition parameters into the las2las GUI and convert it to UTM. It blows my mind when it works. Check this out. The GUI creates the command line input for you when you type in the numbers in the right places:

las2las -lof file_list.txt -target_utm 15N -olaz -tm 543000 0 survey_feet 44.03610992 -92.6333313 0.9999949932 -ellipsoid 11 -elevation_survey_feet -vertical_navd88

I discovered there is a difference in the lastools switches -keep_xy and -keep_XY. It took me hours to discover I needed xy not XY.

I still need to work on the last step of getting the processed lidar products (like contours and images) into an orienteering mapping package, like older OCAD versions or Open Orienteering Mapper. For some reason, I believe related to shortcomings in those packages, the contours don't like to line up.

My biggest want right now is a way to do unsharp mask processing of lidar. I'm slightly desperate.

Lots to do to prepare for this weekend. I'm in Louisville Friday and Saturday, then at Seven Hills on Sunday. I'm planning to go to the North American Handmade Bike Show on Friday (OMG OMG OMG), then (hopefully) ride a mountain bike at the Mega Cavern (I'm gonna say "meh", but I'm feeling "OMG."). I've also got to program and deliver three SI units to Jim Benton.
4 PM

Course set-check-pick 5:22 [0] 0.22 km (24:51 / km) +1m 24:17 / km

This is the track Mike made while searching for two lost SI units with Bruce Moore and Bill Donnelly. I suggested it in case they weren't found and we needed to come back when the snow melted. Luckily, they found them quickly.

« Earlier | Later »