All resources

· New England Drone & Data

A Matching File Checksum Does Not Prove the Capture Was Complete

A property-data delivery may include large images, models or archives. A checksum can help compare a received file with a recorded version, but it answers a narrower question than whether the documentation covers the property correctly. Keep the transfer check and the assessment of the content as separate parts of the handoff.

Name the exact file and digest method

NIST’s Secure Hash Standard describes digests used to detect whether data has changed since a digest was generated. Ask which algorithm and exact file the supplied value describes. An archive and an extracted image are different files; an edited or re-exported version can legitimately have different bytes. Retain the original file name, size, version reference and supplied digest together rather than copying an unlabeled code into a project note.

Reconcile a difference before replacing the record

If a comparison does not match, preserve the received file and ask the provider which version should be checked. A mismatch alone does not identify the reason: the delivery may have changed, the wrong file may have been compared or transfer integrity may need review. Do not silently overwrite the original or treat a newly computed value as if it had been supplied earlier. Agree on the corrected delivery identity and retain the explanation.

Review content and usability separately

A matching digest is not proof of capture location, completeness, measurement accuracy or the source’s authenticity. Open the agreed deliverable in the recipient’s supported viewer and check its inventory and coverage notes through the normal project review. Request the actual deliverable and transfer-verification arrangements in scope; do not assume a particular automated integrity service is included. This separation allows an intact file to remain intact while a missing area or interpretation question is still investigated.

Copyable worksheet

Use one row for each field. Mark unknown information clearly and retain the original records.

FieldYour note
File name, size and delivery version____________________
Digest algorithm and supplied value____________________
Comparison outcome and date____________________
Unresolved transfer/version question____________________
Separate viewing and coverage review____________________

Worked example

Illustrative example: a fictional recipient compares an archive’s supplied digest with the digest of an extracted image. The values differ because they describe different files. The handoff identifies the correct archive before checking its contents; no checksum is presented as a survey or completeness certificate.

Request a documentation scope