A topographic survey provides a measured record of site features and terrain for planning, design or construction. The useful question is not simply whether a site has been surveyed. It is whether the available information supports the decision your team is about to make.
A concept layout, an access-road design and a check of completed earthworks may need different coverage, detail and quality evidence. Defining those requirements before commissioning the work makes proposals easier to compare and gives the receiving team a practical basis for accepting the deliverables.
Start with the decision and the survey boundary
Describe what the project team needs to resolve. For a proposed access, that might mean understanding the connection between the site and an existing road. For a development platform, it could mean reviewing the current terrain around the intended footprint. The required survey boundary may extend beyond the immediate work area.
State which features matter and which questions remain outside the assignment. A record of visible site features does not automatically establish underground utility locations, ground conditions or legal property boundaries. A fence can be mapped as an observed feature without being accepted as the legal boundary.
Identify the people who will use the information. A designer preparing a surface, a contractor reviewing quantities and a manager discussing access may need different files from the same survey. Agree on those outputs early, along with responsibility for checking them.
Specify horizontal detail and elevation information
Horizontal detail locates features in plan: roads, structures, edges and other agreed objects. Elevation information describes heights and changes in level against a stated reference. Many engineering surveys need both.
Depending on the scope, outputs can include a survey drawing, spot elevations, profiles, contours and a digital surface. These should form a coherent record. A dense point dataset is not a substitute for identifying the particular features the designer needs to understand.
Ask for the coordinate reference system, height reference and units to be stated. Also record the capture date and any relationship to the project's local reference. Data from different sources should not be combined merely because the files appear in approximately the same place on screen.
Match field methods to access and visibility
Total stations determine positions through angle and distance measurements. They can support detailed observations where the survey team has suitable sight lines and control. Levelling may be included where the work calls for a particular approach to establishing or transferring heights.
GNSS surveying uses satellite observations with the positioning method, correction arrangements and checks appropriate to the assignment. Sky visibility, obstructions and reference information affect how the work should be planned. A receiver specification alone does not establish the quality of every point collected on site.
Drone photogrammetry uses overlapping images to reconstruct visible surfaces. It can provide broad coverage together with imagery that helps a team understand the location of a question. Open earthworks, narrow spaces between structures and areas covered by vegetation present very different capture conditions.
These methods can be combined. Aerial data may cover a large open area while targeted ground observations capture obscured details or provide control and checks. Assess the complete workflow, including processing, review and any additional fieldwork, when comparing time and cost.
Agree on evidence for acceptance
A statement such as “high-resolution survey” does not fully specify positional quality. Ground sampling distance describes image sampling. Point density describes how many reconstructed points occupy an area. Neither is a direct measure of the error in the delivered coordinates.
The USGS guidance on drone imagery calibration discusses geometric control and data verification. Ask the survey provider how horizontal and vertical quality will be checked, what evidence will accompany the files and how areas with limited coverage will be identified.
Acceptance should relate to the intended task. A dataset suitable for a visual planning discussion may not support a detailed engineering measurement. Define the necessary evidence before capture so that an attractive model does not become the only basis for approval.
Check what the drone deliverables represent
An orthomosaic is useful for a plan view of visible features. A point cloud provides three-dimensional observations, while an elevation surface organizes height information for analysis. Confirm which products are included and why each is needed.
For terrain work, clarify whether the model represents the observed upper surface or an interpreted ground surface. Trees and buildings matter to that distinction. Where imagery does not reveal the ground, removing visible objects from a model does not create a new ground measurement. Additional observations may be required.
Record how features and gaps were handled. For example, if the project needs the edge of a channel, ask whether that edge was actually observed and represented in the deliverable. File size and visual detail do not answer that question.
Make handover part of the assignment
Open the proposed output formats in the tools used by the receiving team. Check that coordinates, units, layers and feature descriptions survive the transfer. For a repeated survey, include the information needed to distinguish a real site change from a change in processing or reference.
A useful handover should make the following clear:
- What area and features were surveyed, and on what date.
- Which coordinate and height references apply.
- Which measurements and derived products are included.
- What quality checks were completed and what they found.
- Where coverage or interpretation is limited.
- Who can resolve a question about the data.
Keep the survey record separate from the engineering decision it informs. Topographic information is an input to design; it does not, by itself, approve a drainage arrangement, establish foundation conditions or certify completed construction.
Evaluate the workflow with a representative task
The Maply platform supports drone image processing, map and model viewing, and measurements. Use a representative dataset to evaluate how those capabilities fit the work between your survey team and project reviewers.
To discuss a suitable workflow, contact Maply with the site conditions, intended decision and required outputs. A clear brief lets the team evaluate the complete path from field capture to a deliverable that can be reviewed and used.
