A construction team evaluating drone mapping needs to understand how the data will enter its daily work. A documented case can show the connection between field capture, processing and project decisions. It is most useful when the circumstances and limits remain visible alongside the applications.
A 2021 undergraduate civil engineering thesis by Stéfano Antonelli at Universidade Presbiteriana Mackenzie in Campinas, Brazil, examines this process. Supervised by Larissa Ferrer Branco, it describes drone photogrammetry on a construction project in Itupeva, São Paulo state. The full thesis is available in Portuguese; this article interprets the case for an international project audience.
Read the evidence in its project context
The thesis is exploratory and descriptive, combining a literature review, a site where the author worked and interviews. Its case chapter examines products from the first ten flights, which took place from May to September 2020. There were 22 flights at the project overall. The separate questionnaire reproduced in the appendix contains six responses.
This is a record of implementation and participant experience. It does not provide a controlled comparison of all survey methods or a representative industry sample. Treat reported benefits as observations to investigate in your own operation, rather than guaranteed savings or a universal accuracy benchmark.
Look at how the outputs were used
The project examples include comparisons between survey dates, area and distance measurements, coordinate queries and design overlays. They connect aerial mapping to progress reporting and checking completed work. Volume and elevation-profile examples are also shown, although the thesis notes that the main earthworks had already finished, limiting use during that stage.
One drainage example is particularly informative: the team first identified a construction discrepancy during a site visit, then confirmed it using a design overlay. The evidence supports a workflow in which field observation and mapping complement each other. It does not demonstrate automatic defect detection or establish that every construction detail can be checked from aerial imagery.
For a project team, the useful question is how a finding moves into an action. Identify the drawing revision, the work package under review and the person responsible for following up. A visual difference needs interpretation before it becomes an instruction to change the work. Our guide to construction progress monitoring develops that ongoing review process.
Establish ownership across the capture and processing handoff
In the documented case, construction management firm DOX handled the fieldwork. Maply provided the processing and training described in the thesis, and the flights were planned with Mission Planner. The setup included a DJI Phantom 4 Pro and surveyed ground control. Orthomosaics, digital surface models and processing reports were made available for the team to use.
Those details describe the historical implementation, not a current hardware recommendation. Their broader value is the allocation of work: capture, reference measurements, processing and acceptance each need an owner. An automated flight does not remove the need for someone to review coverage and explain exceptions to the processing team.
When testing a similar arrangement, agree what the recipient needs before collecting imagery. Specify the required surfaces, delivery format, coordinate reference and intended measurements. Record the capture date so that a useful historical survey is not mistaken for current site conditions.
Separate a detailed model from verified measurement quality
The study discusses practical difficulties in protecting and managing ground control targets on an active site. This matters because the quality of reference data depends on what happens in the field. A target that moves or becomes obscured cannot simply be treated as unchanged in later surveys.
Processing statistics also need context. Residuals at points used to adjust a model are not, on their own, an independent assessment of the delivered product. The USGS guidelines on UAS imagery calibration provide further background on geometric quality, control and validation.
For that reason, the thesis's GSD and RMS figures are not presented here as a Maply performance guarantee. Before using new survey data for engineering measurements, agree the evaluation method and confirm the horizontal and vertical references. Review the actual areas that matter to the task, including gaps and surfaces that the camera could not observe adequately.
Turn the case into a practical evaluation brief
A useful pilot starts with a defined task. It might assess whether repeated imagery helps review a particular work area, whether the deliverables can be used by the engineering team, or how much effort the complete workflow requires. Decide what evidence will support acceptance before the first capture.
Include field preparation, reference measurements, processing, review and any necessary repeat visit when assessing cost or time. The benefits reported in a case study cannot replace those measurements for a different site. Keep technical suitability and economic evaluation connected, but evaluate each with appropriate evidence.
The flight planning guide explains how to translate output requirements into a capture brief. Historical regulations and commercial references in the thesis should also be checked against current requirements before planning an operation.
The Maply platform brings processing, viewing, measurement and survey comparison into one environment. To evaluate a workflow for your project, request a demonstration with a representative site, the intended deliverables and the decisions your team needs to support.
