A colored thermal picture does not prove that the delivered file contains usable radiometric measurement data. For a UVH2 inspection inquiry, state whether the buyer needs a visual record, an analyzable file, or both. Ask for an actual representative output and a supported analysis route before treating a report image as evidence of a file-level capability.

Suppose a hypothetical buyer receives a clear image in an inspection report. The image opens correctly and shows the area of interest. Weeks later, another reviewer wants to examine measurement information from the original observation, but the report contains only the rendered picture. Successful image delivery has answered one requirement while leaving the later analytical requirement unresolved.

Describe the task after the file is delivered

Begin with the action the recipient must perform. Viewing a picture, comparing a documented observation with another record, and examining measurement data are different tasks. A request for thermal images is too broad to tell the supplier which one matters. State the intended use and ask the proposed supplier which outputs can support it in the configuration under discussion.

Do not infer capability from a palette or an attractive display. Nor should a buyer assume that every file with a familiar image extension contains the same information. The requirement is about the delivered data and the supported workflow, not merely the appearance of the first preview. Keep the question open until a representative file has been examined with the appropriate documented tools.

This article does not identify the sensor supplier for UVH2, promise radiometric output, or establish temperature accuracy. It addresses a purchasing distinction. Any proposed sensor, file format, software compatibility, or measurement claim must be confirmed for the specific configuration rather than borrowed from a general description of thermal imaging.

A bounded example from a camera manual

The FLIR FC-Series ID Installation Manual, Version 130, March 2017, page 61, distinguishes normal JPEG output from radiometric JPEG output containing temperature data and associates the latter with a radiometric model. This historical, product-specific example illustrates the file distinction only. It does not establish UVH2 compatibility, sensor identity, measurement validity, or any relationship between UNITED UAV and FLIR.

The useful procurement question is therefore narrower than does it take thermal pictures. Ask what information is preserved in the actual delivered file and what documented application can read it. Then ask whether that output belongs to the configuration being quoted. A demonstration from a different camera can explain a concept without closing the requirement for the proposed system.

Separate the three objects in the handover

First identify the source output that the supplier proposes to retain or deliver. Second identify any rendered image intended for reports or communication. Third identify the analytical result or interpretation, if that is part of the scope. These may be connected, but they are not the same object. Ask how the handover preserves the relationship between them.

• Source file: Identify the proposed format, configuration, and supported reader without assuming capabilities from the extension.
• Report image: State its communication purpose and whether it is only a rendered representation.
• Analysis record: Identify the responsible reviewer, the source used, and the limitations of the stated conclusion.
• Provenance: Retain the identifiers needed to connect the delivered objects without relying on similar-looking filenames.

These are suggested handover categories, not a claim that a UVH2 purchase includes analysis services. If the buyer expects interpretation, ask whether it is separately offered and who is responsible for it. If only files are being supplied, identify who on the buyer's side will perform the required review and what information that person needs.

Test the intended file workflow before acceptance

Request a representative output that the supplier is authorized to share. It should be identified as a sample and linked to the configuration that produced it. Ask the responsible reviewer to attempt the agreed downstream task using the documented application. A successful picture preview is not the same test as successful access to the specific information required for analysis.

Record what the reviewer could and could not establish. If a reader does not expose the expected information, investigate the file and software requirements with the supplier rather than immediately concluding that the sensor lacks the capability. Equally, do not infer that the information must exist simply because somebody can display the picture. The result should remain unresolved until the evidence answers the question.

Use the actual delivery route where possible. A file passed directly from an engineer's workstation may not be identical to the item later embedded in a report or exported through another application. Ask whether the intended route preserves the required object, and retain a clear distinction between the original sample and any presentation derivative. Do not prescribe undocumented conversion steps.

The field-oriented lesson is to try the intended analysis on the delivered file before treating a screenshot as sufficient evidence. This is editorial guidance, not a claimed customer incident or a statement that UNITED UAV has tested the proposed configuration. It focuses the discussion on an observable handover result that both buyer and supplier can describe.

File capability is not measurement validity

Even after the required data can be read, the buyer has a separate question about whether a proposed measurement or interpretation is valid for the task. Put that question to the qualified technical reviewer and the supplier's documented process. This article does not provide operating settings, temperature correction instructions, or an acceptance threshold for an inspection.

Ask which conditions and supporting records the reviewer needs and who will supply them. Keep missing information visible in the result. A usable analytical file may still be insufficient for a particular conclusion, just as a report image may be sufficient for a narrowly defined visual communication task. The decision should follow the agreed scope, not a blanket assumption that one file category is always enough.

Where the workflow must connect observations across devices or records, the payload timestamp and clock-evidence guide addresses a related but independent issue. Knowing when an event was recorded does not establish what data the file contains. Likewise, a rich file does not automatically establish that its time fields can support the intended association.

Keep the review record understandable to the next person

Agree how a revised output will be identified. If the supplier replaces a sample or changes the proposed export route, the previous review should remain attached to the object actually examined. Ask whether the new item needs another file-level check and who will decide. Do not silently transfer an earlier approval to a package that only looks similar in a report.

Where the buyer requests both a report image and an analytical file, verify that both appear in the delivery list. A missing object should become a specific follow-up item. That is clearer than asking for more thermal data without explaining which handover requirement remains unmet.

Store the file identity, reader or analysis route, configuration context, and review outcome together. Avoid an acceptance note that says only image checked. A later reviewer should be able to tell whether that means the picture was visible, the required data was accessible, or a particular analytical conclusion was reviewed. Those are different levels of assurance.

If a report image is sent separately from the source file, label its role clearly. Do not imply that a recipient can recover all original information from the picture unless the supplied format and workflow actually support that. A concise handover statement can prevent a communication asset from being mistaken for the complete analytical record.

The raster preview and full-resolution review guide describes a similar distinction between convenient display and the object being accepted. The technical details differ, but the purchasing discipline is the same: identify the representation, state what was examined, and avoid transferring a successful visual check to an untested data requirement.

Scope the UVH2 configuration inquiry

Begin with the UVH2 product listing to identify the model under discussion. Do not treat the listing or the illustrations here as confirmation of a specific radiometric format, analysis program, calibration status, or temperature performance. For the proposed sensor and file workflow, contact us for configuration details.

A US inspection buyer and an Irish project team can use the same file-level questions without assuming identical local requirements. The appropriate professional and operating requirements remain project-specific. When comparing platforms in the VTOL and fixed-wing drone collection, send the same downstream task description so that suppliers are not answering different interpretations of thermal deliverables.

Ask for evidence that answers the file question

Prepare a short request describing the recipient's intended action, the output objects needed, the preferred review environment, and the person responsible for acceptance. State explicitly whether a rendered picture alone is sufficient. If measurement analysis is required, identify that requirement without inventing a sensor capability or promising that a particular application will support it.

Ask UNITED UAV about the proposed UVH2 output workflow with three concrete items: a representative file, the documented route for examining it, and explicit confirmation of the capability offered in the quoted configuration. Keep any remaining limitation attached to the inquiry. The goal is a usable, understood handover, not merely a colored image that opens successfully.