A dramatic 3D terrain view may use vertical exaggeration to make relief easier to see. Before interpreting that view as the ground's actual shape, ask for the display factor and an unexaggerated companion view. In a UG73 survey inquiry, specify the evidence needed for review separately from the presentation: a convincing rendering is not proof of survey accuracy, engineering suitability or an included processing service.

The ridge that looks steeper in the meeting

A project team opens two presentations of the same proposed site. One landscape looks almost flat; the other has striking ridges and deep channels. The second presentation attracts attention, and the conversation quickly turns to access difficulty and construction implications. Yet the meeting notes do not say whether both scenes use the same display settings. A visual impression has started to carry more weight than the documented evidence.

This is an illustrative review scenario, not a customer story or a claim about a UG73 survey. It shows why a buyer should ask a simple question before comparing rendered terrain: are we looking at different data, different display choices or both? That question can keep a useful visualization from being mistaken for an independent engineering conclusion.

What vertical exaggeration means here

Esri's surface-animation documentation explains that vertical exaggeration changes the displayed height of a 3D surface. A factor of one represents the unexaggerated surface; larger factors emphasize relief. This is a statement about a visualization setting in the documented software, not a verification of the underlying elevation data or a guarantee about every export format.

For procurement, the useful distinction is between the evidence being delivered and the way a reviewer sees it. An emphasized view may help a discussion, but it needs an explanation of its purpose. An unexaggerated view may be a better companion for comparing presentations. Neither one replaces the measurements, definitions and professional interpretation required for a consequential site decision.

Three files can serve three different jobs

Consider asking a supplier to distinguish the analytical dataset, the reusable scene and the presentation output. The dataset supports whatever analysis has actually been commissioned. The reusable scene carries a particular viewing setup. The presentation output is what a meeting participant receives as a screenshot, slide or video. This is a proposed purchasing structure, not a claim that every system supplies all three.

The buyer should name which of these is required and which is optional. If only an image is delivered, ask what information accompanies it and who can explain the settings. If a scene is delivered, confirm that the receiving team can open it in an agreed environment. If a dataset is delivered, define the separate acceptance criteria for that dataset rather than relying on its appearance in a screenshot.

Set up a fair side-by-side review

A helpful comparison brief identifies the same area, the same data version and a shared review question. For example, the team may want to discuss where a drainage feature needs closer professional assessment. Ask for a normal presentation and, if useful, a clearly labeled emphasized presentation. Keep the intended question visible so the review does not become a contest over which image looks more impressive.

Also record the viewpoint and any other presentation choices that materially affect the comparison. This is not an instruction to modify survey data. It is a request for enough context to understand the supplied views. When a supplier changes a presentation, ask whether only the view changed or whether a new dataset is involved. Those situations deserve different version notes and different review effort.

Use cautious language in the meeting record. A participant can say that a feature is visually prominent in the supplied view without calling it a measured hazard. If the discussion requires slope values, clearances or engineering acceptance, route it to the relevant qualified reviewer with the appropriate underlying evidence. The aircraft model and the attractiveness of a scene do not provide that professional judgment.

A presentation note that survives forwarding

A view can leave its original context when somebody forwards a slide. The buyer can reduce that ambiguity by requesting a short visible note identifying the dataset version, the view's purpose, whether vertical exaggeration is applied and where the unexaggerated companion can be found. The note should remain understandable outside the original presentation meeting.

Ask the supplier how that information will travel with each agreed output. A separate technical document may be useful, but a recipient who receives only one image may never see it. Conversely, crowding a figure with small print can make the information unreadable. Agree on a concise caption and a traceable reference to fuller documentation, then inspect a representative output before accepting the delivery format.

• Name the source dataset and revision used for the view.
• State whether the surface is vertically exaggerated and record the factor.
• Identify the corresponding unexaggerated review view.
• Separate visual observations from measured or professionally assessed conclusions.
• Keep the owner of any unresolved interpretation question visible.

What to ask when comparing quotations

Two quotations may both promise a 3D deliverable while offering very different review experiences. One could include a reusable scene and a documented handover; another could include only rendered images. Ask each supplier to describe exactly what the buyer receives, what software or access is required and which explanation or revision work is included. Do not infer those services from the word mapping.

Request a bounded example of the proposed handover format. The example need not disclose another client's data. An invented or supplier-owned scene can show the documentation arrangement and the difference between presentation and analytical outputs. The purpose is to inspect how the supplier communicates scope, not to treat an example scene as evidence of performance on the buyer's site.

Assign responsibility for later changes. If a reviewer wants a new viewpoint, who prepares it? If the underlying dataset changes, who confirms which presentations are affected? If the receiving team cannot open the scene, what was actually promised? These questions turn an attractive file into a manageable deliverable without assuming a particular software license or support arrangement.

Keep local context factual and bounded

A US buyer and a United Arab Emirates buyer can use the same display-disclosure questions while having different receiving organizations, project documents and approval processes. Describe those actual project requirements in the inquiry. Do not infer a local engineering rule, a permit condition or an environmental capability from the country name or from the landscape used in a product illustration.

Where a project requires a professional interpretation, identify who supplies it and which records they need. This article does not provide legal or engineering advice. It offers a procurement distinction: a presentation can support a discussion while still needing a separate evidentiary basis for the decisions made during that discussion.

UG73 is the configuration starting point

The UG73 fixed-wing VTOL drone for surveying and route inspection is a product to discuss in relation to the intended project. Its identity does not establish a particular sensor, terrain-processing workflow, software license or deliverable accuracy. Contact us for configuration details and confirmation of the proposed service boundaries before treating any of those items as included.

Start with the review task: who will use the terrain information, which outputs they need and what they must be able to verify. Then discuss the proposed aircraft and supporting configuration. The VTOL and fixed-wing collection provides a wider product context, but no model choice removes the need for a clear distinction between data and display.

Related handover ambiguities deserve their own checks. A spatial-join row count may differ from an asset count, while RGB display channels may not identify the underlying raster bands. These are not interchangeable problems. Together, they remind a reviewer to ask what a technical output represents before using its visible form as a decision shortcut.

Short answers for the review team

Is an exaggerated view necessarily misleading? No. It can serve a declared presentation purpose. The problem is an undisclosed setting or an interpretation that goes beyond the evidence. Ask for context and a companion view rather than rejecting a useful visualization simply because it emphasizes relief.

Does an unexaggerated view prove the terrain is correct? No. Display choice and data quality are separate. The buyer still needs the agreed dataset documentation, acceptance evidence and professional review for the intended use.

Should the buyer alter the delivered elevations? This article does not recommend altering survey data. Ask the responsible supplier or reviewer for the appropriate presentation and its documentation. Keep any analytical transformation outside an informal attempt to make a meeting slide look better.

Request the view you actually need

Prepare a reference screenshot, describe the decision your team wants to discuss and request an unexaggerated companion view with documented settings. Include the receiving software environment if it is known, and mark it as unresolved if it is not. That gives the configuration conversation a clear target.

Bring that brief to the UNITED UAV contact team when discussing UG73. Ask for configuration and delivery-scope clarification, with responsibility for interpretation stated separately. A useful survey review begins when everyone knows which parts of the picture are evidence, which are presentation choices and which questions remain open.