Opened 6 years ago
Closed 3 years ago
#644 closed flight processing (fixed)
CA18/208, flight day 232/2018, Ontario, Canada
Reported by: | dac | Owned by: | |
---|---|---|---|
Priority: | immediate | Milestone: | |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description
Data location: /users/rsg/arsf/arsf_data/2018/flight_data/canada/CA18_207-2018_232_Ontario
Data arrived from NERC-ARF via hard driver on 12/09/2018
Scientific objective: Canadian Wildfire Observations with SLSTR & Aircraft: Directional Effects of Thermally Emitted Radiation & Exploration of Flaming/Smouldering Partitioning and Plume Trace Gas Emission Ratios. Fenix and Owl data are being processed to aid geocorrection of other thermal sensors flown on the aircraft.
PI: Martin Wooster
BAS Project Code: D207
- Missing log file for Fenix line 2, created a dummy one for renaming
- Navigation data (.sol format) and level1b (unmapped) data to be delivered first. The level1b data will be used to determine which lines map.
Sensors:
- Fenix (requested, flown)
- Owl (requested, flown)
Change History (20)
comment:1 Changed 6 years ago by dac
- Summary changed from CA18/208, flight day 229/2018, Ontario, Canada232 to CA18/208, flight day 232/2018, Ontario, Canada
comment:2 Changed 6 years ago by asm
comment:3 Changed 6 years ago by dac
Fenix
Generated Level 1b files.
comment:4 Changed 6 years ago by asm
Owl Processing
Started in order to create the level1b files.
comment:5 Changed 6 years ago by wja
Navigation Processing
Basestation PPP:
Latitude | 51°04'01.40101" |
Longitude | -93°48'14.26798" |
Ellipsoid Height | 346.745 |
All GNSS / IMU data processed with generated data put in the associated project locations.
Generated SOL has a good solution.
comment:6 Changed 6 years ago by wja
Hyperspectral Processing
SRTM DEM created.
comment:7 Changed 6 years ago by wja
Hyperspectral Processing
Starting Fenix processing.
comment:8 Changed 6 years ago by wja
Hyperspecteral Processing
New SRTM DEM created due to receiving errors about extent whilst generating APL config.
SCT Values Identified:
Flightline | SCT |
1 | 2.00 |
2 | 1.00 |
3 | 1.00 |
4 | 2.00 |
5 | 2.00 |
6 | 2.00 |
7 | 2.00 |
8 | 3.00 |
9 | 2.00 |
comment:9 Changed 6 years ago by wja
Hyperspectral Processing
All bands mapped for all nine lines.
Creating delivery.
Owl Processing
Finding SCT values.
Flightline 7 is very short (847 lines) and will not be processed further.
Errors have been encountered whe processing flightlines 1 & 5. Flightline 1 needs a larger DEM extent. Time is apparently going backwards for flightline 5. Investigating.
comment:10 Changed 6 years ago by wja
Owl Processing
Flightline 1 is very short (~1000 lines) and wont be processed further.
Flightline 5 has been processed without the navsync (use_nav = false). This resolved the issues with navigation timestamps going backwards.
SCT values identified:
Flightline | SCT (') |
1 | N/A |
2 | 2.00 |
3 | 2.00 |
4 | 2.00 |
5 | 5.00 |
6 | 2.00 |
7 | N/A |
8 | 2.00 |
9 | 2.00 |
10 | 3.00 |
11 | 2.00 |
All bands have been mapped.
Creating delivery.
comment:11 Changed 6 years ago by wja
Hyperspectral Delivery
Fenix delivery created. Ready for checking.
comment:12 Changed 6 years ago by wja
Owl Delivery
Owl delivery created. Ready for checking.
comment:13 Changed 6 years ago by dac
Fenix Delivery Check
Starting delivery check
comment:14 Changed 6 years ago by dac
Fenix Delivery Check
- check_apl_cmd outputs look good. SCTs are all OK.
- Times in logsheet all look OK
- Lots of clouds in the data, should mention in the readme.
- The masked out cloud looks really odd in the mosaic as it is blue. In a similar one I've done the mosaic without masking so it looks more natural, I think this will be better for the PI's application.
- Mosaic should be named f232_3b_mapped_utm15n_3band.tif
- Spectral look good.
After mosaic is fixed and cloud mentioned in readme, ready to deliver.
comment:15 Changed 6 years ago by dac
Owl Delivery Check
Starting Delivery Check
comment:16 Changed 6 years ago by dac
Owl Delivery Check
- Files in readme don't match up with loghseet file names, should be 1 - 9.
- check_apl_cmd runs through and SCT values look good.
- Spectral looks a bit odd but states in readme settings were to capture forest fires.
Stated zipping files. Once readme is fixed ready to deliver.
comment:17 Changed 6 years ago by wja
Hyperspectral Delivery Check
- Cloud and smoke is mentioned in ReadMe.
- Correctly named unmasked mosaic added to delivery (including ReadMe screenshot)
- Zipping mapped data.
Owl Delivery Check
- ReadMe line numbers have been corrected.
comment:18 Changed 6 years ago by wja
Hyperspectral & Owl Delivery
Data placed on FTP slot 1. Notification e-mail sent to PI. Delivery finalised. Processing directory tidied.
comment:19 Changed 6 years ago by wja
Archiving
Upload to CEDA complete (18/01/2019)
comment:20 Changed 3 years ago by dac
- Resolution set to fixed
- Status changed from new to closed
Unpacking checks
-There are 9 owl lines and 9 fenix.
-All owl lines have T1 and T2 calibration files