Photogrammetry software has to do something photogrammetry software alone does not: place a model on a defensible coordinate frame and document that placement well enough for someone else to check it later. This is a software-and-deliverables discussion, not a guide to hiring a pilot and not a summary of any drone regulation. A drone-derived point cloud or surface earns a place inside survey software only when its coordinate handling, control, and documentation meet what that software — and the surveyor of record — actually require.
A projection is not a detail to fix later
Every coordinate has to live in some projection, and picking the wrong one does not produce an obvious error message — it produces a model that looks fine on screen while carrying a systematic distortion across the site. A state plane zone and a UTM zone can both look like reasonable, similar-sized numbers and still disagree by a meaningful amount once real distances are computed between points. Survey software cares about the projection attached to the file itself as metadata, not a note in an email, because a CAD or GIS package will faithfully plot whatever coordinates it is given whether or not they were converted correctly on the way in.
Datums and EPSG codes are where handoffs quietly break
WGS84 and NAD83 are close enough to look interchangeable on a map and different enough, depending on realization and location, to matter once a surveyor tries to close a drone-derived point against an established control network. Vertical datums split the difference further: an ellipsoid height straight out of a GNSS receiver is not the same number as an orthometric height tied to a geoid model, and mixing the two without converting produces an elevation error that has nothing to do with the photogrammetry itself. EPSG:4326, for reference, is the well-known code for plain WGS84 latitude and longitude — a useful anchor for how specific these codes get, and a reminder that "the coordinates looked right" is not the same claim as "the coordinate system is documented." A drone processing report that lists numbers without a datum and an EPSG code attached is a report a surveyor cannot safely reuse without independently reconfirming it first.
A control network is not the same thing as a few tagged photos
A handful of ground control points identified in a set of aerial photos is not equivalent to a surveyed control network. A real network consists of monumented points with known, checkable relationships to each other and to the broader geodetic reference frame, established with enough redundancy that closure error can be measured rather than assumed. RTK- or PPK-tagged photo positions can initialize or densify a photogrammetric model efficiently, but they are a property of the aircraft's GNSS chain during one flight, not an independently verifiable network a future surveyor could re-observe and check against. Treating a tagged flight path as equivalent to a control survey is one of the more common — and more expensive — mistakes in this handoff.
Accuracy and precision are different questions, and drone reports tend to blur them
Precision describes how tightly a set of measurements agrees with itself; accuracy describes how close those measurements sit to the true, external position. A dense, visually sharp point cloud can be extremely precise — every point agreeing tightly with its neighbors — while still being systematically offset from the real world if the control tying it down was weak or absent. A tight internal residual reported by processing software is evidence of precision. It is not, by itself, evidence of accuracy, and treating the two as interchangeable is exactly the gap an independent checkpoint exists to close.
RTK, PPK, and PPP-OPUS: three ways to tie a flight to a known frame
Real-time kinematic positioning corrects each photo's location live, in the field, against a base station or a network service — useful, and only as good as that live correction link. Post-processed kinematic logging records raw satellite observations onboard and corrects them after the flight, which removes the dependence on a live link but delays the corrected positions until after landing. A static base receiver occupation, later processed against the national geodetic reference network through a precise-point-positioning service such as NGS's OPUS, is a third and different option: it independently establishes a base coordinate from the reference network itself, rather than trusting a previously assumed or unchecked benchmark on site. None of the three eliminates the need for an independent checkpoint once the model is built.
Contours are a derived product, not an observation
A contour line was never measured directly; it is generated from a DTM after that DTM has already been classified and edited to represent bare ground. That means a contour inherits every assumption baked into the classification step underneath it, and it is only as trustworthy as that step was careful. A contour file that omits its interval, vertical datum, and coordinate source is incomplete even if it opens cleanly and looks like a normal contour set — the numbers on the page mean nothing without the reference frame that gives them scale.
What a licensed surveyor will accept, and where the line sits
A surveyor may reasonably accept drone-derived surface or topographic data as supporting field information when the control, datum, and QA behind it are documented well enough to check independently. A surveyor will not accept an uncontrolled visualization as a boundary determination, a legal survey, or a substitute for a licensed professional's own certification. Establishing a property boundary is a legal act grounded in record research, monumentation, and adjoiner evidence — not an output any aerial reconstruction produces on its own, however sharp the imagery behind it looks. Topographic support work, as-built documentation, and volumetric or progress surfaces are the categories where drone data most often earns a legitimate place in a survey deliverable; boundary and legal determination are the categories where it does not.
Where drone data alone runs out
Dense canopy hides the true ground beneath it no matter how the point cloud is classified. Water surfaces reflect and refract rather than yielding a real elevation. Anything below grade, behind an overhang, or inside a structure was never photographed from the air in the first place. And legal boundary evidence — deeds, monuments, adjoiner agreement — is a record-research question that a reconstruction, however precise, cannot answer by itself. Recognizing where the aerial model stops being useful is as much a part of this software discussion as anything the processing pipeline does well.
If you are sorting out which checks belong in a surveying handoff, ask the follow-up on Ask Mav at pilotledger.com.