An elevation model needs a definition of the physical surface it represents. Before scoping a UG73 survey workflow, state whether buildings, vegetation, and other above-ground features should remain in the deliverable, be removed, or be identified as unresolved. An acronym such as DSM, DEM, or DTM does not replace that requirement or establish that the proposed configuration can produce it.

Picture a hypothetical review in which a model follows the roof of a building accurately, while the buyer expects ground elevations beneath the same footprint. The two parties are not necessarily disagreeing about image quality. They may have ordered and reviewed different surfaces. Resolve that question in the brief, before an attractive elevation display becomes evidence for a purpose it was never designed to serve.

Describe the decision that needs the surface

Begin with the downstream task. A buyer interested in the visible shape of a site may need a different representation from a buyer considering terrain beneath vegetation. Do not treat either as the default definition of a survey model. Ask the responsible technical reviewer to explain which surfaces matter to the decision and which exclusions would make the deliverable unusable.

Then translate that explanation into observable review questions. What should a reviewer see at a building footprint? What should be represented at a tree canopy? What happens where the required ground surface has not been established? These questions are easier to discuss than a general instruction to provide a clean model, which can hide disagreement about what clean actually means.

The aircraft choice does not settle this definition. A proposed survey workflow includes acquisition, processing, supporting evidence, and a delivery specification. This article addresses the last of those boundaries and the questions it raises for the others. It does not claim that UG73 includes a particular sensor or can recover any specified surface under particular site conditions.

Use terminology, but define it locally

The USGS Lidar Base Specification glossary distinguishes surface representations that include vegetation and structures from bare-earth elevation concepts. It also explains that DTM usage can differ by context, including different representations in US and other usage. The glossary is useful terminology evidence, not a certification of a UG73 output or a substitute for the buyer's project specification.

For a project involving US and Irish teams, agree a plain-language definition alongside any acronym. Do not assume a shared abbreviation resolves differences between reviewers. Nor should the USGS glossary be presented as an Irish procurement requirement. Use it to expose the question, then have the parties responsible for the actual project approve the vocabulary and acceptance conditions.

Create a surface-treatment schedule

List the feature classes that matter to the job. Against each, describe the intended treatment and the evidence needed to assess it. Keep this schedule specific enough to guide review without pretending that the buyer already knows the technical solution. The supplier should respond with supported capability, limitations, and any additional work needed to meet the requirement.

• Buildings: State whether roofs are part of the requested surface and how their footprints should be treated in other outputs.
• Vegetation: Distinguish the visible canopy from the ground representation needed for the task.
• Structures and temporary objects: Identify which classes should remain and which require separate treatment.
• Unresolved areas: Define how missing evidence or uncertain interpretation will be marked and explained.
• Review ownership: Name the role authorized to accept each treatment or request clarification.

A schedule can also reveal when the project needs more than one deliverable. The buyer may have a legitimate use for both a visible surface representation and a different terrain product. Ask whether those can be supplied and reviewed separately. Do not force multiple uses into one vaguely named file and expect every downstream user to discover its limitations independently.

Ask what supports an obscured area

The most important review question may concern an area that the chosen observations do not directly establish. Ask the supplier how the proposed workflow would describe such areas, what supporting evidence would be used, and where uncertainty would remain. Do not infer that a continuous-looking model means every location has equivalent evidence. The delivery explanation should make its boundaries visible.

For a hypothetical building footprint, the buyer might ask whether the delivered values represent a visible roof, an estimated underlying surface, separately supplied information, or an unresolved area. These are questions for the responsible survey specialist, not interchangeable options this article endorses. The correct response depends on the task and the evidence available for the particular site.

Keep any illustrative demonstration separate from project acceptance. A sample from an open site can explain an output format, but it does not establish performance in a different environment. Ask what the sample demonstrates and what remains to be confirmed. This protects the buyer from transferring confidence in a polished example to a condition the example never addressed.

Review meaning before appearance

A useful review begins by asking the reviewer to point to a feature and explain what the delivered elevation means there. At a tree, is the value intended to describe the canopy or the ground? At a roof, is it the roof or a separately defined terrain surface? This is editorial guidance for a buyer review, not a report of a UNITED UAV field operation.

Only after the representation is understood should the group judge whether it serves the agreed task. A visually smooth surface can still answer the wrong question. Conversely, an explicitly marked gap may be a more honest deliverable than an apparently complete surface whose unsupported portions are undocumented. Agree how such gaps affect acceptance rather than encouraging their concealment through presentation.

Record the file identity, the areas reviewed, and the specific treatment decisions. If a revised output changes the handling of vegetation or structures, identify that change rather than delivering it as an unexplained replacement. The reviewer should be able to tell whether the revision changes appearance, interpretation, supporting evidence, or the agreed scope of use.

For the separate issue of what a viewer actually displays, read the guide to raster overviews and full-resolution review. Viewing the right file at the intended resolution matters, but it cannot correct a surface definition that was wrong from the beginning. Keep display checks and surface-meaning checks as distinct entries in the acceptance record.

Compare proposals on the same definition

Ask a reviewer outside the original briefing to interpret one example area using only the delivery notes. If that person cannot tell which surface is represented, the documentation needs clarification even if the original team understands it. Capture the explanation in the package rather than relying on an informal conversation. This check concerns communication and traceability; it does not certify the technical quality of the elevation values.

When requesting quotations, send the same surface-treatment schedule to each supplier. Ask them to identify included outputs, excluded conditions, supporting information required from the buyer, and unresolved capabilities. This makes it harder for a short phrase such as terrain model included to conceal materially different scopes. It also gives the buyer a clearer basis for follow-up questions.

Do not equate more files with a better proposal. An additional deliverable is useful only when its meaning, intended use, and review method are clear. A smaller package with explicit boundaries may be easier to accept than a broad package with ambiguous labels. The purchasing decision should follow the required outcome and supported evidence, not the number of acronyms in the quotation.

If the downstream task involves reservoir capacity, the reservoir area and storage evidence guide raises another boundary: the requested conclusion may depend on geometry beyond what a visible surface record establishes. Do not allow an elevation product's name to stand in for the full input chain required by a later calculation.

Where UG73 belongs in the scope discussion

Use the UG73 product listing to identify the platform being discussed, then ask how the proposed configuration relates to the required surface deliverables. This article does not promise a particular mapping sensor, processing package, terrain extraction capability, or survey accuracy. For those product and integration questions, contact us for configuration details.

The VTOL and fixed-wing drone collection can support a broader platform discussion once the outcome is defined. Keep the technical brief consistent between models. Otherwise, a conversation about aircraft selection may distract from the more basic question of whether the offered workflow can deliver the physical surface the buyer needs.

Make the next inquiry about a surface, not an acronym

Prepare a brief with the intended downstream task, a sketch or annotated example of the site features that matter, and the treatment expected for each feature class. Identify who will review uncertain areas and which external inputs the buyer already has. Where a requirement is undecided, mark it for discussion rather than silently choosing the most reassuring interpretation.

Send UNITED UAV a UG73 surface-deliverable inquiry with that schedule. Ask which parts of the proposed workflow can be confirmed, what evidence would accompany the output, and what remains outside the offered scope. A clear answer about trees, roofs, ground, and unresolved areas is a stronger starting point than an unexplained promise to deliver a DTM.