One accepted state unlocks the next

00–01Retrieve + preserve

Move evidence off source media without altering it.

02–06eMotion + PPK

Match mission time/images and correct camera geotags.

07–09Pix4D start

Configure cameras/CRS and build initial geometry.

10–14Survey control

Export, import, mark, reoptimize and audit GCPs.

15–19Products + QA

Build dense products and read the Quality Report.

20Handoff

Inventory, inspect and archive analysis-ready evidence.

The complete operational SOP

WHAT

Retrieve the camera media and aircraft logs as two distinct evidence sources.

INPUTRecovered aircraft→ACTIONUse the approved eBee X procedure. Images and basic flight data are on the camera SD card. For internal drone logs: remove the camera, power the aircraft on, wait about 20 seconds, then attach mini-USB to the computer. Keep the two retrieval paths distinct.→OUTPUTReadable camera media plus the required mission log files.

ACTION

Use the approved eBee X procedure. Images and basic flight data are on the camera SD card. For internal drone logs: remove the camera, power the aircraft on, wait about 20 seconds, then attach mini-USB to the computer. Keep the two retrieval paths distinct.

WHERE

Physical eBee X/camera data-access station.

WHY

The camera media and aircraft internal log store contain different evidence.

INPUT

Recovered aircraft
Camera media
Approved eBee X access procedure

OUTPUT

Readable camera media plus the required mission log files.

CHECK

Confirm aircraft generation, payload, supported cable and storage before access.

IF THIS FAILS

The hardware procedure, power state or media identity is uncertain.

NEXT

Copy first, process second

Printable operational checklist

eBee Postflight Checklist

Download Markdown checklist

Copy logs and all sensor imagery
Preserve raw data
Start eMotion Postflight
Verify mission, date, UTC/local-time conversion and image count
Load the correct logs and image folder
Load PPK/RINEX and verify the solution
Export corrected imagery and processing evidence
Start Pix4D and add the required camera groups
Verify camera model and EPSG:3301 where applicable
Run Initial Processing only
Export/import GCP CSV if control is used
Mark every GCP and reoptimize
Inspect residuals, distribution and Quality Report
Run Point Cloud and Mesh
Run DSM, Orthomosaic and Index
Generate and verify reflectance maps
Archive products, metadata and QA

Open only the support you need

Source-media retrieval and project foldersCamera media · aircraft logs · immutable raw copy

CAMERA MEDIASD card

RGB, multispectral or thermal imagery plus basic flight data.

INTERNAL AIRCRAFT LOGSeBee X mini-USB branch

Remove camera, power on, wait about 20 seconds, then attach mini-USB—only under the approved eBee X procedure.

PROJECT DRIVEVerified copy

Never process from the SD card. Preserve original files unchanged.

site/
  raw/
    logs/  rgb/  multispectral/  thermal/  gnss/
  processing/
    emotion/  pix4d/
  outputs/
  qa/

Twenty annotated procedure diagramsOpen the visual index instead of scrolling past a card wall

Use this diagram index to revisit a handoff without repeating the full SOP. Each card summarizes the input, operation, check and resulting product.

Physical retrieval

Camera SDraw imageryarchive

Internal logs use the approved remove-camera → power-on → wait → mini-USB branch.

Copy workflow

source mediaverified copyread-only raw

Counts and sizes agree before processing.

eMotion Postflight

flight logimage timesGNSS / PPK

Associates mission evidence and corrected geotags.

Time and RINEX

UTC flight+3 h summerlocal request

Request full mission coverage plus margin.

PPK concept

roverbasecorrected geotags

Overlap in observation time is mandatory.

Before / after

≈0.806 mPPK≈0.049 m

Documented 2024 project example, not a guarantee.

Image–log matching

capture timeflight eventimage coordinate

Different from image feature matching.

Trimble to Pix4D

approved jobGCP CSVGCP/MTP

Verify schema, units and EPSG:3301.

GCP/MTP Manager

importplotinspect

Imported does not mean correctly identified.

Manual image marking

one targetmany imagesreprojection

Mark the same physical point precisely.

Reoptimization loop

markreoptimizeaudit residuals

Correct and repeat until defensible.

Stage toggles

Step 1 onlycontrol QASteps 2 + 3

Do not hide failed geometry under dense outputs.

Point cloud

matched raysdense samples3-D surface

Density is not positional accuracy.

DSM

dense surfacegridupper elevation

Includes vegetation and objects; not a DEM.

Orthomosaic

imagesDSM geometrymap mosaic

Perspective and scale are corrected.

Reflectance maps

calibrationfour bandsGeoTIFFs

Radiometry and geometry must both pass.

Three evidence types

RGBmultispectralthermal

Visible, reflected narrow bands and emitted infrared.

Band stack

GreenRed + Red EdgeNIR

Align identity, scale, grid and masks.

Output structure

rawprocessingoutputs + QA

Keep provenance beside products.

Final QA

quality reportproduct auditaccept / block

Completed is not automatically valid.

Processing-stage controls and final productsStep 1 → GCP → reoptimize → steps 2 + 3

FIRST RUN✓ Initial Processing□ Point Cloud and Mesh
□ DSM, Orthomosaic and Index

GCP import → mark → reoptimize → QA

FINAL RUN□ Initial Processing✓ Point Cloud and Mesh
✓ DSM, Orthomosaic and Index

RGBorthomosaic · point cloud · DSM

MULTISPECTRALGreen · Red · Red Edge · NIR reflectance · indices

THERMALthermal product plus RGB companion evidence

Similar words do not make equivalent evidence

SD card ≠ working directoryImage geolocation ≠ photogrammetric matchingPPK ≠ GCPPPK ≠ perfect positionGCP import ≠ GCP correctly markedCRS present ≠ CRS correctPoint cloud ≠ orthomosaicDSM ≠ DEMOrthomosaic ≠ reflectance mapThermal palette ≠ thermal measurementProcessing completed ≠ scientifically valid

Prepare the eBee, then process the mission

Prepare, document, then fly