CarbonARA25, flight day 271/2025, Brazil boresight

[asm]

/users/rsg/arsf/arsf_data/2025/flight_data/brazil/CarbonARA25-2025_271_Tapajos

This is a boresight flight with highest priority

Data arrived on 5th March 2026
PI: Martin Wooster
Sensors:
-Owl
-Fenix1k
-IBIS

[asm]

Project Unpacking

Unpacked the files manually while we fix the scripts. Renamed the files accordingly. Please note:
-Navigation processing has been performed by NCEO (CM)
-A DEM was included in the delivery and has been copied to "processing/hyperspectral/dem"

Run the unpacked checks:
-No "fps_set" in any fenix1k file
-No .f98 files (these were for old fenix only?)
-All NAV files for fenix1k are throwing the error: "No date record ($GPZDA) found in nav file - will assume it is binary if cannot find a line starting with '$GPGGA' or '$PRDID'."

Everything else looks correct (sizes, GPS times recorded, sensor ids...)

[mark1]

Have renamed wavelengths in hdr files for Fenix lines using:

replace_wavscale.py -w /users/rsg/arsf/calibration/2021/fenix1k/wlcal2b_vnir_1b_swir.txt /users/rsg/arsf/arsf_data/2025/flight_data/Brazil/CarbonARA25-2025_271_Tapajos/hyperspectral/fenix/FENIX271-25-*/capture/*.hdr --final

Have generated a logsheet without image as there is an extra flightline miles away.

[mark1]

IBIS line 1 has no nav file and no nav synced to line (no gps start/stop locations). This is mentioned in the handwritten log sheet. Have removed from cfg so won't be processed.

[mark1]

Timing corrections required for Fenix.

I have used sct = 0.09 for all lines, looks good for the lines with runway along track, for other flight directions difficult to tell as no along track features to use, so have used the same as it looks OK.

Will start boresighting now.

[mark1]

ibis line 6 suspicious dropped frame?

[mark1]

For Ibis data I'm suspicious that it may be dropping frames without telling us. E.g. flight line 6, the specim log file says no dropped frames but there are a couple of points along flight line that look like there are dropped frames (see attached image).

This makes it difficult to check for timing corrections (as it looks wobbly with different corrections along track in different places). Also makes boresight difficult - the result appears to have some larger shifts than normal when comparing between lines.

[mark1]

No timing errors noted in Owl data nor Ibis. Ibis data have the caveat that dropped scanlines or instrument issues has made it more uncertain. Not many features to check timing other than runway, so can only use the lines which fly along runway to do this.

Boresights determined:

fenix_boresight = -0.542 0.145 -0.6203
ibis_boresight = 0.060 -0.036 -0.960
owl_boresight = -0.058 -0.429 -1.2