TeraAirlift

TeraAirlift

Delivery checklist

LiDAR Dataset Delivery Checklist

Who it's for: Reality-capture crews, processing managers, and geospatial PMs.

When to use: Use when moving LAS, LAZ, E57, GeoTIFF, orthos, or scan project exports from field devices to office or client.

Field packaging

  • Confirm project ID and capture date on the root folder
  • Include CRS / CRS metadata notes with the package
  • Exclude unreleted flights/scans from this handoff
  • Estimate total TB and wireless/cellular constraints

Handoff queue

  • Queue jobs per crew/site so office can prioritize processing
  • Note battery/network windows for field machines
  • Assign office owner for acceptance before registration starts
  • Schedule a retry window if connectivity is intermittent

Failure / retry plan

  • Never assume a mid-field upload finished without confirmation
  • Retry with the same package ID; avoid duplicating confusing copies
  • Hold processing until integrity check passes
  • Document corruption or truncation symptoms for vendor/hardware follow-up

Recipient / access plan

  • Limit client access to the agreed deliverable subset
  • Expire client links after acceptance period
  • Keep internal processing shares separate from client reviews
  • Track which subcontractor received which tile set

Verification plan

  • Hash or integrity verify when the toolset supports it
  • Spot-open a sample of LAS/LAZ/E57 files on office systems
  • Confirm file counts match the field manifest
  • Only then kick off registration / classification compute

Send me the printable version

Soft gate — the checklist is already above. Share your details if you want a follow-up copy and workflow tips for your team.