Choosing a TIN Simplification Threshold That Doesn't Erase Flow Channels
Simplification sounds harmless. Reduce the triangle count, keep the shape. But for topographic mapping errors , that one parameter — the threshold — c...
11 articles in this category
Simplification sounds harmless. Reduce the triangle count, keep the shape. But for topographic mapping errors , that one parameter — the threshold — c...
You've got a crisp 1-meter LiDAR DEM. Ridge crests are razor-sharp, exactly where the survey says they should be. Then you resample to 10 meters for a...
You're staring at a 0.5-meter gap between lidar strips. It's not huge—but it's not small either. For a survey that needs 10 cm accuracy, that's a red ...
Every contour line tells a story. But if you pick the wrong vertical datum, that story turns into a lie — one where slopes lean the wrong way. For sur...
You've got 10,000 LIDAR points per square kilometer. That's enough to see every bump, right? Wrong. The ground can hide a fault line so subtle that yo...
You have a beautiful lidar point cloud — billions of points, crisp returns from the ground, vegetation, and buildings. But when you rasterize the bare...
You stare at the screen. Blue stream lines cut across brown contour lines like they own the place—runn uphill, skipping valley, ignoring every rule of...
You just pulled a slope map from a LiDAR-derived DEM. It looks crisp. But something is off: a ridge you know by heart shows as a dark valley. Another ...
Every topographic map tells a story about elevation. But if the vertical datum is off, the story is fiction. Systematic errors—consistent bias across ...
You stare at the slope raster. A pixel that should show 5% grade instead reads 120%. Something is off. This isn't just a button-push issue. It's a geo...
Every floor surveyor I know has a story about the ridge that just vanished. They processed the data, generated contours, and the landform they needed ...