A drone LiDAR project has a pleasant asymmetry: the client’s work is almost all front-loaded, small, and easy — and doing it well shaves days off the schedule and real dollars off the quote. The capture itself is our job. Yours is mostly answered in an email.
Here is everything worth lining up before a drone LiDAR scanning flight, roughly in the order it comes up.
Define the boundary: the KML/KMZ
The single most useful thing you can send is a KML or KMZ file — a simple geographic file that draws your exact project boundary on a map. It removes all ambiguity about what “the site” means, and it is what a flight plan is actually built from.
If you have never made one, it takes about five minutes in the free version of Google Earth: draw a polygon around your site, save it as KML/KMZ, attach it to your quote request. A GIS or civil team can export one from nearly any software. No KML? A PDF exhibit, a parcel number, or even a marked-up aerial screenshot works — we will digitize it and send the boundary back for confirmation before anything flies.
Two boundary tips that prevent the most common revisions:
- Buffer generously. If you might need the adjacent ditch, the access road profile, or tie-ins beyond the property line, include them now. Extra acreage inside a planned flight is cheap; a second mobilization for a missed strip is not.
- Corridors: send the centerline. For pipelines, transmission lines, and roadways, a centerline KML plus your required corridor width is the ideal input — it is exactly how corridor and utility mapping is scoped and priced per mile.
Site access and permissions
The drone flies overhead, but the crew works from the ground: launch point, ground control targets, base station. Before flight day, think through:
- Legal access. Confirm we may enter the property, and arrange permission if launch or control points sit on a neighbor’s land. If written landowner authorization is needed, having it ready prevents the classic day-of stall.
- Gates, locks, and guards. A gate code or a name at the guard shack, sent the day before, is the difference between an 8:00 start and a 9:30 one.
- On-site hazards and rules. Active construction traffic, livestock, hunting seasons, required PPE or site inductions — flag them early so the pilot arrives compliant.
- A phone contact. One reachable person who can answer “is this gate supposed to be locked?” in real time is the cheapest insurance a project can buy.
Occupied or sensitive facilities benefit from a simple heads-up to staff and neighbors that a mapping drone will be operating — thirty seconds of communication that prevents most concerns before they start. On active jobsites, a line in the morning safety briefing does the same work: crews who expect the aircraft ignore it; crews surprised by it stop working to watch.
Timing: seasons, leaf-off, and weather
LiDAR is far more forgiving of conditions than photography — it needs no sunshine and flies happily under overcast — but two timing factors genuinely matter.
Vegetation state. LiDAR maps ground under canopy through gaps in the foliage, so the thinner the foliage, the better the bare-earth model. On deciduous wooded sites, leaf-off season (late fall through early spring) is meaningfully better for terrain work. Summer capture of a wooded site still works — it is LiDAR’s signature strength — but if your schedule has flexibility and the site is heavily treed, aim for leaf-off. Similarly, recently mowed or grazed fields beat chest-high grass, and if a site is being cleared anyway, flying after clearing is ideal. Our guide to drone LiDAR accuracy explains exactly why ground-point density under vegetation drives result quality.
Weather windows. The real constraints are strong winds, precipitation, and standing water on ground you need mapped (near-infrared LiDAR does not measure through water). Scheduling always carries a weather contingency day or two; rural sites often reschedule fastest.
Airspace rarely blocks a project but can add lead time. Sites near airports typically need FAA authorization — often near-instant through LAANC, occasionally a longer waiver. Mention any nearby airport, heliport, or military facility in your request and the authorization is handled invisibly.
What speeds up your quote
We return quotes within 24 hours; the requests that come back fastest — and sharpest — include:
- The boundary (KML/KMZ or best available substitute)
- The end use — “grading design,” “drainage study,” “as-built verification” — which drives accuracy and deliverable recommendations better than any format list
- Required deliverables, if known: classified LAS/LAZ, bare-earth DEM, contour interval, shapefiles (what each one is, explained here)
- Coordinate system and vertical datum, if your project has one established (State Plane zone, NAVD88)
- Whether certified survey control is required — if deliverables must carry a licensed land surveyor’s stamp, our surveyor partners join the scope, and knowing early keeps pricing honest
- Timeline, including any hard permit or closing dates
Missing pieces never block a conversation — the end use alone lets us propose the rest. And if the project involves repeat capture, such as monthly earthwork verification, say so up front: recurring construction progress tracking is priced differently, and better, than a series of one-offs.
What happens on flight day
For calibration of expectations, a typical capture day runs:
- Arrival and setup. The pilot walks the launch area, sets the GNSS base station, and places ground control targets at precisely measured points around the site.
- Airspace and safety checks. Authorization confirmed, equipment checks completed, weather verified.
- The flight. The drone flies pre-programmed lines in a methodical lawnmower pattern — unglamorous by design. Small sites finish in under an hour of flying; large ones run through battery cycles across the day.
- Field QA. Coverage and data integrity are verified on site before anyone leaves, so a gap becomes a ten-minute re-fly instead of a re-mobilization.
- Demobilization. Targets collected, site left as found. Nothing on your site is disturbed.
Then the data moves to processing — classification, surface generation, accuracy verification against checkpoints — which is where the remaining schedule lives. What lands in your inbox depends on the package you ordered, and the budget behind all of it is laid out honestly in our drone LiDAR cost guide.
The one-page checklist
Everything above, compressed to what you can forward to a project engineer:
| Item | Ideal | Acceptable minimum |
|---|---|---|
| Boundary | KML/KMZ polygon (buffered) | Marked-up aerial or parcel number |
| End use | One sentence (“grading design”) | — required |
| Deliverables | Format list + contour interval | “Recommend for the end use” |
| Coordinates | State Plane zone + NAVD88 | “No established control” |
| Access | Gate codes, contact name, hazards | Phone contact on flight day |
| Timing | Leaf-off window if wooded | Any weather-flexible window |
| Certification | Stated yes/no on surveyor stamp | Ask us — we will ask you anyway |
The pattern worth remembering: every hour a client spends on this list returns itself several times over in schedule and precision. Send a good boundary and a clear end use, and the rest is our job.