What a point cloud is and why it matters
A point cloud is millions of individually measured 3D coordinates – each one a precise location on a surface captured during a drone survey. Whether from photogrammetry or LiDAR, the point cloud is the raw foundation. Everything else comes from it: surfaces, contours, cross-sections, volumes, 3D models.
For engineers working in Civil 3D, the point cloud is both a design reference and a data source for creating TIN surfaces, alignments, and profiles. Understanding how it flows from drone flight to usable deliverable helps you get more from the data and specify the right outputs.
Stage 1: Capture
Photogrammetric
Our survey-grade drones capture overlapping imagery at controlled altitude and speed. Typical parameters for engineering survey:
- Flight altitude: 50 to 80 m
- Image overlap: 75% frontal, 65% side
- GSD: 1.5 to 2.5 cm/pixel
- Positioning: RTK/PPK with GCP verification
LiDAR
The scanner records raw laser returns during flight:
- Pulse rate: 240,000 to 480,000 per second
- Multiple returns: up to 7 per pulse
- Scan angle: typically plus or minus 30 degrees
- Flight altitude: 50 to 100 m
Stage 2: Processing
Photogrammetric processing
The overlapping images go through Structure from Motion (SfM) processing:
- Software finds matching features across overlapping images (tie points)
- Calculates camera positions and orientations using bundle adjustment
- Brings in GCP coordinates to georeference and constrain the solution
- Generates a dense point cloud – 3D positions for every identifiable surface point
- Builds the orthomosaic from the oriented imagery
Result: a coloured (RGB) point cloud at 100 to 500 points per square metre.
LiDAR processing
Raw LiDAR data goes through:
- PPK corrections applied to the drone trajectory
- Trajectory, IMU, and laser range data combined to compute 3D coordinates for each return
- Strip adjustment to align overlapping flight lines
- Coordinate transformation to ITM
Stage 3: Classification
A raw point cloud has everything the sensor captured – ground, vegetation, buildings, vehicles, power lines, birds. For engineering use, you need each point tagged with what it’s on. Standard classes (ASPRS LAS spec):
- Class 2 – Ground: bare earth for DTM generation
- Class 3/4/5 – Vegetation: low, medium, high
- Class 6 – Buildings: roofs and structures
- Class 7 – Noise: erroneous points to discard
- Class 9 – Water
We use automated algorithms with manual quality checking. The classification quality directly affects the surfaces you build from it – sloppy ground classification means a sloppy DTM.
Stage 4: Getting it into Civil 3D
Import
Civil 3D reads point clouds via Autodesk ReCap (.RCP/.RCS files) or directly as .LAS (from Civil 3D 2021 onwards). For large datasets, we pre-process into project-ready tiles. Things to get right:
- Make sure the Civil 3D drawing is set to ITM before importing
- The point cloud attaches as an external reference, keeping the DWG file manageable
- Civil 3D can filter display by classification code – show only ground for surface creation, or only vegetation for clearance checks
Building surfaces
The most common Civil 3D output from drone data is a TIN surface:
- Filter the point cloud to ground-classified points
- Thin to appropriate density (Civil 3D bogs down with millions of points in one surface)
- Create TIN surface from the filtered dataset
- Add breaklines along features like road edges, ditch inverts, and embankment toes
- Generate contours at whatever intervals you need
We normally deliver this as a ready-made surface in .DWG, so you skip the processing steps. The source point cloud comes alongside for reference and additional analysis.
Sections and profiles
With a surface in Civil 3D, you can create alignments along any route and extract longitudinal and cross-sectional profiles straight from the drone data. That supports cut-and-fill work, road design, and drainage analysis without traditional chainage-based survey.
File sizes
Point clouds are big. A 10-hectare site at typical photogrammetric density produces roughly 2 to 5 GB. LiDAR is typically 30 to 50% smaller for the same area due to lower point density. We deliver in compressed .LAZ format (5 to 10 times smaller than .LAS) and can thin or tile to meet your data management needs.
Specifying what you need
If you need point cloud data for Civil 3D, be clear in your brief about coordinate system, classification requirements, format, and any file size constraints. Our guide on writing a drone survey specification covers this in detail.
For Trimble Business Center workflows, see our article on Civil 3D and TBC integration. To talk about your project, get in touch.