Training Log Archive: ebuckleyIn the 1 days ending Mar 20, 2010:
| ||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||
| |||||||
| Sa |
Saturday Mar 20, 2010 #
7 AM
Orienteering (Woods) 5:53:00 [2] ***
202c shoes: Trail Attack 6
Yes, really, 202 controls at Cuivre River (1:15).
Because this is such a large area, I'm concerned that the vegetation will drift over the time I'm mapping it. Therefore, I decided I'd do a "snapshot" run. Basically went to every point and recorded the vegetation at that point. When I go back to do the real mapping, I'll have nearby reference points to make sure I'm staying consistent. Will do the same thing in the south half of the park next week.
Slower than competition pace, obviously given the distance, but fast enough to get a real read on the densitiy at each point. Of course, many were no brainers ("there it is 200m away - I'm thinking white woods"), but I adjusted by a shade at about 30 points and another dozen simply bear no resemblance to the map, so they'll have to be redone from scratch.
The unfortunate revelation of the run was that Eric Weyman was right - the contours at CR really aren't very good. I don't know why I haven't noticed that before. I guess I always use big feature navigation there, so it just hasn't been an issue. Anyway, I'm hoping I can find some LIDAR data, because adjusting 20KM^2 of contours by hand is going to take a really long time.
Because this is such a large area, I'm concerned that the vegetation will drift over the time I'm mapping it. Therefore, I decided I'd do a "snapshot" run. Basically went to every point and recorded the vegetation at that point. When I go back to do the real mapping, I'll have nearby reference points to make sure I'm staying consistent. Will do the same thing in the south half of the park next week.
Slower than competition pace, obviously given the distance, but fast enough to get a real read on the densitiy at each point. Of course, many were no brainers ("there it is 200m away - I'm thinking white woods"), but I adjusted by a shade at about 30 points and another dozen simply bear no resemblance to the map, so they'll have to be redone from scratch.
The unfortunate revelation of the run was that Eric Weyman was right - the contours at CR really aren't very good. I don't know why I haven't noticed that before. I guess I always use big feature navigation there, so it just hasn't been an issue. Anyway, I'm hoping I can find some LIDAR data, because adjusting 20KM^2 of contours by hand is going to take a really long time.