ASTC15_28, flight day 168/2015, Albacete

[dac]

Data location: ~arsf/arsf_data/2015/flight_data/spain/ASTC15_28-2015_168_Albacete_summer_school

Data arrived from ARSF via SATA disk on 09/07/2015

Scientific objective: Flight for ATSC summer school

Priority: Unknown

PI: Alasdair Mac Arthur

CAMF Code N028

Sensors:

• Fenix (requested)
• LiDAR (flown, not requested)
• Owl (flown, not requested)

[gej]

Started Navigation Processing

GPS data doesn't have L2C so have to specify manually at -0.25 L2 cycles
Elevation mask set to 8.0 degrees
Kar maximum distance for dual frequency set to 120km due to distance of teru basestation

Using two base stations,
Alba data:
Lat: 38 58 40.51042
long: -1 51 23.03504
Ell Height: 751.655m
teru data:
Lat: 40 21 01.80637
Long: -1 07 27.46418
Ell. Height: 956.120m

Accuracy is within acceptable levels (below 0.35)
Combined Seperation: East -0.05 North -0.10

Navigation Processing Finished

[gej]

Fenix SCT values are

Flightline 1 couldn't be processed due to not having correct flight times (start and end identical).

use_nav false in config file due to issues with sync times. So had to use QGis for intial line ups of flightlines (using google sattelite data).

Flightline	FENIX
1
2	2.60
3	3.36
4	4.96
5	3.40
6	11.33
7	1.30

[gej]

Hyperspectral Ready for Delivery Check

[dac]

Fenix Processing

Waiting on updated calibration to process fenix data with.

[gej]

Fenix Processing

Reprocessed with updated calibration file. Creating new Delivery.

[gej]

Fenix Processing
Created delivery, Ready for DC.

[dac]

Fenix Delivery Check

Starting delivery check

[dac]

Fenix Delivery Check

Initial comments

• In readme change "Flightline 1 not processable". Line 1 wasn't a proper line, in the logsheet the file numbers start at 2. Don't need to say line 1 wasn't processed, but do need to say why the numbering starts at 2, something like: "The instrument was turned on before data collection started, therefore numbering starts at 2"
• Not quite sure what happened with the apl commands in the config file - most of the names were wrong (3b for 1b files), have fixed these so check_apl_cmd now runs.

Still need to check spectra so will do this on Monday.

[gej]

Fenix Processing

Have changed comment in Readme to the above.

[dac]

Fenix Delivery Check - continued

• Spectra look fine, good match to 6S simulated spectra.
• Different spectral VNIR binning was used for 2 - 5 and 6 - 7. This isn't noted anyware in the ticket. Should be added to Readme.

Once Readme has been updated can be delivered when updated data quality report is available.

[gej]

Fenix Processing

Updated Readme to mention that VNIR binning is different between flightlines 2-5 and 6-7.

Waiting on updated Data Quality Report.

[dac]

Fenix

Updated Readme is better. Have started zipping mapped files,

[dac]

Fenix

Copied updated data quality report. Delivered data to PI via FTP (arsf12).

[dac]

Archiving

Started archiving for distribution by NEODC

[dac]

Archiving

Data uploaded to NEODC.

[dac]

Archiving

Data now available at NEODC - leaving ticket open for atmospheric correction component.

[dac]

Re-generating IGM files for mapping atmospherically corrected data. Will remove once complete.

[dac]

The zipped version of f168023b_mapped looks like it has been corrupted, the write date is later than the rest.
Will regenerate and upload to NEODC.

[dac]

Regenerated zipped file. Version at NEODC is OK.

[dac]

Atmospherically corrected hyperspectral data using an empirical line correction and ATCOR have been copied to the server under: ~arsf/arsf_data/2015/misc/ATSC15_28_atmospheric_correction.

The files corrected using ATCOR are being uploaded to NEODC as part of the summer school.