Engineers need surfaces they can design against. Project managers need clarity on who stamps what. LiDAR survey data sits in the middle of that conversation—and it goes wrong when vendors blur the line between dense aerial capture and licensed surveying practice.
This post states the line plainly: what you get from a LiDAR data flight, and what you still need a Professional Land Surveyor (PLS) for.
What LiDAR data typically gives the engineering team
A classified point cloud with ground and non-ground returns. A bare-earth digital terrain model suitable for grading, drainage, and corridor profile conversations. Optional canopy height information for clearing estimates. Contours or breakline candidates for refinement in your civil platform. Metadata: density, trajectory quality indicators, control/check residuals, coordinate system, and vertical datum.
Used well, that package shortens field time under brush, improves cut/fill realism on vegetated sites, and gives PE teams a current surface between formal survey milestones.
What still requires a PLS
Boundary determination and monumentation. Sealed topographic surveys where the jurisdiction or contract requires a licensee’s seal. ALTA/NSPS land title surveys. Legal descriptions and easement exhibits that carry legal weight. Any product your contract or AHJ explicitly calls a “survey” in the licensed sense.
Drones Inbound is not a licensed land surveying firm. We produce aerial and geospatial data that licensed surveyors and engineers work from. We do not pretend a point cloud is a boundary survey. When your project needs a seal, your PLS remains responsible for the sealed product—often using dense data we capture as an input.
That division is not a dodge. It is how professional liability and state practice laws actually work across Arkansas, Texas, Oklahoma, Missouri, Illinois, Colorado, Kansas, Louisiana, Mississippi, and beyond.
How engineers should specify the data
State the coordinate system and geoid/vertical datum in the RFP language. Require check points and residual reporting. Define ground classification expectations under partial canopy. Separate “design surface for engineering analysis” from “sealed survey deliverable.” If both are needed, budget both—and name who owns each.
Ask whether photogrammetry would suffice on open pads. LiDAR earns its keep under vegetation, in corridors, and where bare-earth fidelity drives quantities. It is not automatically better for every flat, open commercial pad.
Typical workflow (generic)
Civil scopes grading on a wooded site. DI captures LiDAR and delivers ground-classified products in the project CRS. The PE designs against the DTM. Separately, the owner’s PLS produces the sealed topo/boundary instruments the city or lender requires, using field methods and, where useful, the aerial dense data as supporting information. Nobody confuses the folders.
Related services
Mapping and survey, dense-site LiDAR discussions, site scouting, and services for quotes. Corridor-flavored state work (for example Oklahoma ROW contexts) follows the same licensing boundary.
Request engineering-ready data
Send acreage, canopy notes, CRS/datum, and whether a PLS is already under contract. Call 888.901.5150 or quote through services. You will get a clear scope: data for engineering—and an explicit reminder of what still needs a licensee’s seal.
Practical notes before you book
Share the decision you need to make, not just a request for “drone photos.” Acreage or building footprint, deadline, coordinate system preferences, and whether a licensed surveyor or engineer is already on the project all change how we scope capture and processing. If access, weather, or active operations constrain the window, say so early so the flight plan matches the site you actually have—not the site on last year’s drawing.
Clear communication on those points keeps the deliverable useful the week you receive it, not just impressive in a slide deck.
Field realities that affect quality
Sites are not laboratories. Wind, heat shimmer, standing water, active equipment, and last-minute access changes all show up in real capture windows. A professional crew plans around those constraints instead of pretending every flight looks like a demo reel. When conditions force a compromise, the deliverable notes should say so—so nobody treats a compromised surface like a sealed truth.
Communication before the flight prevents most of that drama. Gate codes, escort rules, and “do not fly over that tank farm” notes belong in the kickoff, not in a text message after batteries are already hot.
How deliverables get used after the handoff
The best aerial product is the one that shows up in a meeting the same week. That means file formats your team opens, naming that matches the project, and a short explanation of what was measured versus what still needs boots or a licensee. Archive the prior flight when you fly cadence work; comparison is often worth more than any single absolute number.
If your organization uses a shared drive or a common data environment, say how you want folders named. Small process habits prevent “which ortho is current?” arguments later.