Seeing a thermal-camera image is insufficient evidence that an application can read numerical temperature data. Procurement and development assessment should identify accessible data, format documentation and interface rights before discussing image analysis, temperature statistics or anomaly notifications. Display screenshots alone do not justify a promise to recover pixel temperatures.
Document the accessible data
| Data level | Required checks | Development implications |
|---|---|---|
| Display images | Color mapping, displayed range and overlays | Assess image regions and visible changes |
| Original numerical values | Meaning, bit depth, correction state and valid values | Determine whether manufacturer conversion and calibration information are needed |
| Temperature data | Units, scaling, invalid states and measurement parameters | Assess regional statistics and conditional temperature-difference rules |
| Device interfaces | Model, firmware, SDK or protocol and license | Define acquisition, configuration and distribution rights |
Verify that samples contain the required information
Provide original files exported directly by the device, interface samples and documentation rather than only screenshots or messaging-app recompressions. Check data layers and metadata using the manufacturer's software or documented method. A file opening in a normal image viewer may or may not contain additional measurement data. Check its data layers separately.
Scope image tasks separately from temperature tasks
Image tasks can cover region marking, displayed changes and human review. Temperature tasks need interpretable measurement data, units, parameters and reference verification. The manufacturer's temperature-measurement documentation explains measurement parameters and radiometric conditions. It does not establish adaptation or specified error for an arbitrary equipment combination.
Arrange a pilot under representative conditions
Check the camera, lens, target surface, mounting and equipment workload before evaluating the processing chain on representative data. Mark inaccessible or undefined data as unresolved. Specify software for device data acquisition, algorithms, parameter files, interfaces and verification records in the contract. Capabilities described in a device manual are not evidence of completed software work.
Related services: Vision hardware and embedded technology, vision algorithms and model engineering, project consultation.