What the DIY route actually involves
Every step below is doable with free tools. Together they are typically a half-day to several days the first time through, and each one can silently corrupt the result:
- Find the right collection. The USGS hosts thousands of overlapping lidar projects. You need the one covering your exact site, and when several overlap, the newest at the best quality level — flight dates and accuracy live in per-project metadata.
- Download the tiles. Collections ship as fixed tiles, so a site on a tile boundary means pulling two to four multi-gigabyte files to use a sliver of each.
- Install and learn the toolchain. PDAL or LAStools for clipping and reprojection, plus GDAL for rasters. Command-line tools with real learning curves.
- Clip and merge. Cut to your boundary and merge tiles without duplicating points in the overlap.
- Reproject — the step that bites hardest. Source data is typically EPSG:3857 with NAVD88 (Geoid18) heights; your project wants a specific State Plane or UTM zone. Get the vertical datum transformation wrong and every elevation is off by up to tens of feet, uniformly, so nothing looks broken.
- Build the surface. Filter to ground returns using the classification, then build a TIN or DEM at a resolution your CAD package can actually load.
- Import into Civil 3D. A DXF of loose points is not a surface; producing a file that imports as a surface object takes specific structure.
- Validate all of it. Spot-check elevations against known benchmarks, because after this many manual steps, errors are the default, not the exception.