Apply current USGS 3DEP lidar specifications and point-cloud classification requirements
domain: usgs.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the current Lidar Base Specification (LBS) revision on usgs.gov/ngp-standards-and-specifications before writing or accepting a scope — the LBS has been revised multiple times (e.g., 2022 rev. A, then a 2025 rev. A), so cite the version actually in force at proposal time.
Require point deliverables in LAS format per the current LBS version requirement (recent revisions specify LAS 1.4-R15 using Point Data Record Format 6, 7, 8, 9, or 10).
Classify points using at minimum the LBS's required classification scheme (found in the specification's classification table) — ground, unclassified, noise, water, etc. — noting that USGS only quality-assesses accuracy for the minimum required classes, not any extended custom classes a vendor adds.
Confirm the contracted Quality Level (QL) for the project (QL0–QL2 point densities are common for 3DEP work) and ensure the vertical/horizontal accuracy requirements tied to that QL are met and documented.
Review the specification's data processing and handling requirements section for calibration, void-filling, and breakline requirements applicable to the specific QL and end-use before final delivery.
Known gotchas
Citing an old LBS version (e.g., 2014 or 2020) in a current contract can create a mismatch with what USGS or a state partner actually expects for a 3DEP-funded project — always verify the currently effective revision.
Extended/custom classification beyond the minimum required scheme is not accuracy-checked by USGS, so don't rely on non-minimum classes (e.g., a vendor's custom building class) as if they carry the same QA rigor as ground classification.
Quality Level and point density are independent of raster DEM resolution — confirm both are specified, since a client may say '1-meter DEM' without realizing that maps to a specific required point-cloud QL.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?