The site decision and observation unit

This guide examines dsm and dtm selection when a mapping team needs to estimate supported stockpile geometry using an agreed base definition. The goal is to connect a specific technical choice to observable site evidence, an independently checkable comparison and a clear delivery decision.

Assign each stockpile an identifier, a visible boundary and an explicit base-surface convention. Adjacent piles, retaining walls and loading activity complicate separation. The measured top surface and the assumed base are different sources of evidence. Keep the observation time close to the inventory cut-off and record material movement during the mission.

Define the decision before choosing a processing configuration. State the target object, the observable surface, the required geographic reference and the evidence needed by the receiving user. Separate direct observations from inferred values. This prevents an attractive image from becoming an unsupported claim about conditions that the sensor did not observe. Preserve the project question in the run record so later quality review evaluates the intended use rather than a convenient software statistic.

The technical mechanism

A digital surface model represents visible surfaces, while a terrain model aims to represent ground. Optical reconstruction over closed vegetation commonly observes the canopy rather than the soil. Ground classification and interpolation cannot create direct ground observations where none exist. The choice must follow the physical surface needed by the intended calculation.

Site conditions that can mislead interpretation

Conveyors, dust and vehicles obscure portions of the pile. Shadows can hide toe lines, and a guessed base may dominate the volume difference between methods. A precise-looking number does not eliminate uncertainty in the pile boundary, material properties or conversion from volume to mass.

A complete terrain-looking raster may contain extensive assumptions beneath vegetation. Product names do not establish that the required ground surface was observed.

Geospatial processing and quality review at a workstation
Review the source observations, coordinate system and independent evidence alongside the visual result. Illustrative imagery; not a surveyed dataset or a performance benchmark.

Prepare the inputs and the controlled test

Define whether the task concerns canopy, roofs, exposed ground or bare terrain. Inspect source point support and classification evidence. Separate observed ground from inferred or interpolated ground. Preserve masks and reference measurements used to support a terrain interpretation. Avoid relabeling a surface model simply because the receiving task expects terrain.

Build the comparison around a preserved baseline. Use the same input inventory, geographic extent and independent reference observations whenever the experiment permits. Change one justified factor at a time and record any unavoidable difference. Select both a difficult inspection region and a stable control region before examining the candidate output. Compare on their common valid support, then report any gain or loss of total coverage separately. This distinguishes a local improvement from a result that merely excludes the hardest observations.

Independent verification in this setting

Verify representative toe positions and any independent base observations. Compare selected surface profiles and review areas hidden by equipment. Record operational changes between image capture and inventory acceptance. Density or moisture assumptions used for mass estimates require their own evidence and should not be attributed to the photogrammetric surface.

Compare representative locations with independent ground or surface observations appropriate to the product. Inspect profiles across vegetation, structures and open ground. Record coverage and confidence for each surface type. Check that the delivered metadata states what the elevations actually represent.

A linked check: Orthomosaic Seam Inspection

An orthomosaic combines image observations using reconstructed geometry and image selection. A visible seam can reflect exposure differences, moving objects, geometric inconsistency or source-image quality. Conversely, seamless color blending can hide a positional problem. Inspecting seams therefore requires both the stitched result and the original views that support the target features.

Select seams across representative surfaces and compare identifiable features on each side. Review original photographs, local surface support and capture timing. Separate radiometric discontinuity from geometric displacement. Preserve fixed viewing scales and reference locations when testing a blending or reconstruction change.

Check whether the candidate preserves feature position, edge continuity and valid coverage. Inspect stable control regions in addition to the most obvious seam. Compare independent evidence where geometry matters. Record whether the improvement concerns appearance, measurement support or both.

Aerial view of an urban mapping area
Review the source observations, coordinate system and independent evidence alongside the visual result. Illustrative imagery; not a surveyed dataset or a performance benchmark.

An illustrative decision example

Imagine a hypothetical quantity comparison in which two accepted top surfaces are almost identical, but the calculation uses different base assumptions near an uncertain boundary. The resulting volumes can differ materially even though both surfaces look smooth. Preserve the boundary and base definitions, inspect representative profiles and identify which assumptions change the result. Where ground support is missing, report the inferred component separately rather than calling it measured terrain. A candidate surface that fills every hole may increase apparent completeness while adding no independent observation. Compare common supported areas and describe the effect of any deliberate interpolation. This example illustrates sensitivity to evidence and reference definitions; it is not an inventory result. The receiving team should be able to reproduce the quantity and distinguish changes in the physical surface from changes in calculation assumptions, vertical reference or the chosen valid-area mask.

Interpret uncertainty before accepting the result

Write the acceptance rule before selecting the most attractive output. The actual threshold must follow the project purpose and the quality of the independent evidence. Inspect signed differences and spatial patterns as well as summaries. Investigate consequential outliers using their source observations instead of deleting them to improve a score. A result can be suitable for inspection planning while remaining unsuitable for a more demanding engineering or quantitative claim. State that intended-use boundary explicitly.

Deliver evidence that the next team can use

Provide pile identifiers, accepted boundaries, the base method and volume units. Include supported-area exclusions and a sensitivity note where the base is uncertain. Preserve the approved version so later inventory reconciliation compares the same geometry and cut-off.

Keep the accepted source dates, processing version, coordinate conventions, masks and reference evidence beside the delivered data. Reopen a representative output from a clean copy and confirm that the intended receiving application interprets it consistently. Identify any remaining unsupported areas and the additional observation that would resolve them. The next analyst should be able to reconstruct the decision without depending on a temporary browser session, an operator recollection or a file whose name merely says final.

Where a cloud workflow can help

Cloud Photogrammetry Software can simplify the transfer from an organized image collection to a shared review workflow, but it does not remove acquisition or validation responsibilities. Drone Collab can be considered as part of that workflow after the team checks the current published capabilities and the outputs required by the project. Start with a representative collection and evaluate the evidence, usability and handover together. Choose the workflow because it supports a defensible decision rather than because one preview looks particularly polished.

References and further reading