Training Log Archive: cmorseIn the 1 days ending Nov 25, 2017:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||
| |||||||
| Sa |
Saturday Nov 25, 2017 #
6 AM
Note
rhr:37 weight:80.3kg
8 AM
Fieldwork 2:06:43 3.62 mi (35:00 / mi) +152m 30:58 / mi
ahr:86 max:127 shoes: Speed Cross Varios 2015
No running for a bit, so decided to get in the woods for some mapping. I have it in mind to make a map that is actually readable on the run by mere mortals (at 1:15000 & 5m contours). This means much more contour generalization and a higher point feature threshold than has been the trend for New England mapping of late. I want to run in the woods, not spend time deciphering a map at a standstill like the last few controls at the traverse last week. First test pretty good. I'll detail my methodology in a separate note.
12 PM
Note
Mapping notes: (mostly for my own reference)
Its all an experiment on my part, may never see the light of day for anything other than training runs.
Lidar data from 2010 NRCS archive. Processed using some LASTools modules and perl scripts under linux. Resulting in a dxf of 1m contours. Rather than importing and trying to smooth/clean the all the noise (or worse, including all the little wiggles like some recent maps), I brought it into OOM as a template and drafted all 5m contours by hand trying to interpret features that would actually be visible on the ground and smoothing out by hand all the little wiggles which are more likely noise than anything useful.
The result is a file that has smooth, generalized contours with appropriately spaced bezier handles for adjusting in the field. Attempting to clean noisy contours in the field was a waste of time a few months ago. Some additional info gleaned from 2016 CT ECO Orthophotography.
Total area - a little less than 16 sq km of usable area, plus another 3km or so if I include Porter/Howard & Longo Open Space areas which are adjacent, but not contiguous in any useful course setting way. The major downside to this area is lack of any arena worthy gathering areas. Any large meet to be held here would need to be bussed from a remote assembly area. This whole area is served by a series of small lots (5-10 car capacity)
Rock features - my threshold for small boulders is 1.5m or better - basically chest high or better, and large need to be 3m or more. More liberal use of boulder cluster or boulder field symbols rather than trying to accurately portray every single boulder in a rocky area.
Cliffs/rockfaces - if it can be readily run up, its not mapped, passable may be climbable but if you'd save a lot more time going around then I'll map it. But a lot of ~1m outcrops are going to be skipped.
More use of dot knolls and elongated knolls rather than form lines to try and depict every minor spot height between 5m contours. If the shape of the land between 5m contours significantly deviates from the suggestion of the contours, then a form line will be used.
All for now..
Its all an experiment on my part, may never see the light of day for anything other than training runs.
Lidar data from 2010 NRCS archive. Processed using some LASTools modules and perl scripts under linux. Resulting in a dxf of 1m contours. Rather than importing and trying to smooth/clean the all the noise (or worse, including all the little wiggles like some recent maps), I brought it into OOM as a template and drafted all 5m contours by hand trying to interpret features that would actually be visible on the ground and smoothing out by hand all the little wiggles which are more likely noise than anything useful.
The result is a file that has smooth, generalized contours with appropriately spaced bezier handles for adjusting in the field. Attempting to clean noisy contours in the field was a waste of time a few months ago. Some additional info gleaned from 2016 CT ECO Orthophotography.
Total area - a little less than 16 sq km of usable area, plus another 3km or so if I include Porter/Howard & Longo Open Space areas which are adjacent, but not contiguous in any useful course setting way. The major downside to this area is lack of any arena worthy gathering areas. Any large meet to be held here would need to be bussed from a remote assembly area. This whole area is served by a series of small lots (5-10 car capacity)
Rock features - my threshold for small boulders is 1.5m or better - basically chest high or better, and large need to be 3m or more. More liberal use of boulder cluster or boulder field symbols rather than trying to accurately portray every single boulder in a rocky area.
Cliffs/rockfaces - if it can be readily run up, its not mapped, passable may be climbable but if you'd save a lot more time going around then I'll map it. But a lot of ~1m outcrops are going to be skipped.
More use of dot knolls and elongated knolls rather than form lines to try and depict every minor spot height between 5m contours. If the shape of the land between 5m contours significantly deviates from the suggestion of the contours, then a form line will be used.
All for now..