Most articles about drone LiDAR stop at the flight. The drone takes off, the laser fires, the point cloud comes home. That is the easy part. The work that actually drives engineering decisions starts after we land. This page covers what shows up on your engineer's screen Monday morning. The models, the file formats, the CAD integration, the interactive viewer, and how the deliverable plugs into the design and construction decisions you are already making.
"LiDAR models" is shorthand for the family of 3D and 2D data products we generate from a drone LiDAR mission. Each model serves a different decision in your workflow:
What you order depends on what decisions the data needs to support. We start every job by asking what design tools you use and what the engineering question is. Then we deliver the right model in the right format.
The deliverable is only useful if your engineers can open it in the tools they already use. We deliver in the formats your design environment expects, and we test the imports before we send the data.
The most common destination for our deliverables. Point clouds import via Autodesk ReCap as RCP/RCS files referenced into the drawing. DTMs come in as TIN surfaces ready for grading and earthwork analysis. Topographic contours arrive as DWG or DXF with 3D polylines, layered and ready to plot. Cross sections and channel profiles import as ground definitions for corridor models. Engineers run cut/fill, alignment design, and grading directly off the LiDAR-derived surface.
For BIM teams, we provide point clouds in formats Revit can reference (RCP/RCS) for as-built modeling and existing-conditions documentation. The point cloud overlays the design model so structural and MEP teams see exactly where the new work meets the existing site. For coordination across disciplines, we can export to IFC for handoff into Navisworks, Revizto, and other clash detection platforms.
For ArcGIS Pro, QGIS, and Global Mapper users we provide GeoTIFF rasters (DTM and DSM), shapefiles for vector deliverables, and projected point clouds in your preferred coordinate reference system. NAD83 Texas State Plane North Central, WGS84, and project-specific CRSs are all supported.
HEC-RAS, ICPR4, AutoCAD SSA, and similar tools accept the DTMs and cross sections we produce. The bare-earth elevation data is the input these models need, and we tune the point cloud classification so the ground surface inside channels and under bridges is clean.
Not everyone on the project team has AutoCAD on their machine. Owners, project managers, regulators, contractors, and clients often need to see the data without installing software or opening a drawing. We solve that with Stitch3D, a browser-based 3D viewer designed for reality capture deliverables.
What you and your stakeholders get with a Stitch3D delivery:
For stakeholders this changes the conversation. A project manager who used to wait two days for the surveyor to send a PDF can now open the live point cloud, drop a measurement, and answer the question on the call.
The model is a means, not an end. The point is the decision the model unlocks. A few of the calls we hear:
We do not ship a generic data package and walk away. Every deliverable starts with a conversation about your design tools, the engineering question, and the format your team needs.
Most jobs deliver inside 48 hours of the flight. Larger projects (200+ acres) deliver in 3 to 5 business days.
If the question on your desk is whether drone LiDAR data will plug into your specific design tools, the answer is almost always yes. We have delivered into Civil 3D, Revit, ArcGIS, Global Mapper, HEC-RAS, Trimble Business Center, Carlson, and others. Tell us your stack and we will match the deliverables to it.
For a quote on a specific project, see our drone LiDAR mapping service page.
Need LiDAR models that drop into your CAD workflow?
Call 972-314-9500 or email info@collincountydrone.com.
Talk to a LiDAR Pilot