Training Log Archive: Spike

Shuffling around in the woods at Lexington Lake. It is tiring, mentally especially, to be bashing through Kansas forest. There are still some leaves out. The woods will be nicer when we have a good hard freeze (maybe tonight) and then some precipitation and wind.

I took a decent fall early on. I smacked my left shin and went tumbling.

I checked out a couple of places where I expected I might find some building remains (based on old USGS maps). One spot had a couple of stone foundations remaining. The other had a large barn. I was surprised none of those showed up in the KP map.

I learned a new word today - hinking. I didn't do any hinking.

2

C • Hinking 6

Easy run, nearly all of it in the terrain, at Lexington Lake. I carried a map, but mostly didn't navigate so much as just pick out a general area to visit and then look for less-crappy vegetation to run through. Overall, I'd say the forest is slightly better than average for around here.

At one point, I was just day dreaming and following the deer trails. Without realizing it, I'd slowly turned about 90 degrees. I saw a big clearing ahead of me in the distance...then I noticed that the sun was setting on my left. The setting sun made me realize that I was running 90 degrees off and that it would be dark soon. So, I turned around and headed back to a place where I knew I'd pick up the trail.

Fun.

2

C • KU 5

Interesting tutorial video on using Open Orienteering Mapper:

https://youtu.be/n9ilQu1sBdo

I'm pretty sure he made a couple of mistakes. First, I think he put 18S in as UTM zone when it should have been 18N. Second, I think he used 10.?? for declination when he should have used -10.??. I'm not sure about the photos, but I haven't had to adjust those. Instead, I just open them with an associated world file and they pop into place (maybe the wrong UTM zone would cause that trouble).

Oh, and there's got to be a better way to use USGS maps for base contours than using the map as an image and just adjusting it.

If I get inspired, I'll watch it and pay more attention to see if the things that look like mistakes are mistakes.

Also, would be interesting to use Lidar data for contours, but that just adds another layer of complexity to a short tutorial.

Also, he draws lots of straight line segments instead of curves. That doesn't seem very good.

C • Straight Line Segments 4

This is a bit of running/jogging between areas I was field checking at Perry. Most of my mapping runs are a lot of running and a little bit of mapping. Today was more mapping and a bit of running. So the hour of running was split into maybe 6 10+ minute sessions of jogging through the woods (not so bad) and on trails.

I went out and looked at a bunch of areas where the lidar ground data showed something interesting. I found a few things that need to be added to the map.

1

After mapping, I returned my map board to the car and went out for a 24 minute run. Felt ok, but my legs are tired from yesterday and the mapping.

1

Long and mostly easy run on the trails at Perry. I carried my current map and did a good bit of map reading. The current map is KP + trails added from lidar data (using a ground slope image to get a lot of the trails). I'm going to add more trails, initially from GPS tracks and then go back and adjust them as needed. The vegetation from the newer lidar is good. I plan to just start by using polygonize to add the vegetation and then tweak it over time.

I did 3x HU/ML/HE.

I saw Blair and Carrie out there. They were mountain biking.

Fun session and I felt pretty good.

3

Rolling around on my MTB on the pavement until it started seeming like I'd better get home before it was dark.

1