Discussion: Stupid Pullautin question

Does it expect x, y, z in meters in the .las?

yes. Or actually those are just numbers to it, so if those are in feet it ends up doing silly things like one feet DEM and consuming lots of memory. So better convert data to meters first.

I did. Next stupid question: It all came out as yellow. This must mean that the underlying LAS was ground-only, correct?

I believe yes.

Last stupid question: Looks like there is a small offset for Pullautin output, about 2 m. I am comparing with the DEM that was derived from the same lidar dataset and with photos. The photos line up with the DEM better than 2 m. Pullautin contours are essentially identical to DEM-derived contours, but with a somewhat consistent offset, about the thickness of a contour line, which is 2 m or so. The DEM was in lat/lon, the photos are in UTM, and the original lidar is in state plane/survey feet (I made triple sure these were survey feet and not regular). Any ideas? (It is still of course possible I am screwing something up.)

Pre-empting the "why would I care about 2 m?" quesiton: trail-O :) :) :)))

That's possible, even likely it's not exactly right since i have never checked it down to that accuracy. After all the generalization and knoll manipulation that 2m doesn't matter much really, but let me know what the direction is and I'll make them move right in the next version.

There's very little generalization evident in Pullautin output for the particular terrain type I am working with.