Opened 7 years ago

Last modified 22 months ago

#449 new flight processing

RG12/10, flight day 206b/2012, Milton Keynes

Reported by: knpa Owned by:
Priority: alpha 4 medium Milestone: 2012 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by anhi)

Data location: /users/rsg/arsf/arsf_data/2012/flight_data/uk/RG12_10-2012_206b_Milton_Keynes

Data arrived from ARSF via SATA disk on 27/07/2012

RG12/10 Scientific objective:

RG12/10 Priority: 8 high

PI: Karen Anderson

Sensors:

Camera (11/09/2012)
Eagle (13/11/2012)
Hawk (13/11/2012)
LiDAR (13/11/2012)
LiDAR + FWF (07/01/2013)

Change History (30)

comment:1 Changed 7 years ago by knpa

Changed Hawk raw file names from 1, 2, 1.1, 1.2 etc to match the Eagle.

comment:2 Changed 7 years ago by knpa

  • Description modified (diff)

comment:3 Changed 7 years ago by anhi

Camera delivery created

comment:4 Changed 7 years ago by adbe

Camera Delivery Check: No problems, ready to deliver

comment:5 Changed 7 years ago by adbe

Hyperspectral delivery created

comment:6 Changed 7 years ago by knpa

Beginning HS delivery check.

comment:7 Changed 7 years ago by knpa

This is actually just an Eagle delivery as there was has been no boresight for the Hawk yet.

comment:8 Changed 7 years ago by knpa

Finished Eagle delivery check.

All looks good apart from:
-Do we need to include a OSTN02_NTV2.gsb file? If so, put in ReadMe contents too.
-No screenshot with vectors - don't think we've gotten vectors. Need to ask PI if they don't mind us skipping this step.
-Need to remove Hawk examples from ReadMe delivery contents.

comment:9 Changed 7 years ago by adbe

Removed OSTN02_NTV2.gsb file
Removed Hawk example from ReadMe contents
Renamed to eagle delivery

comment:10 Changed 7 years ago by adbe

  • Description modified (diff)

Delivered Camera to Karen Anderson on 11/09/2012 on disk 44

comment:11 Changed 7 years ago by anhi

LiDAR delivery created, no full waveform or vectors.
Altitude 4980 feet
Pitch:-0.0027
Roll:+0.00002

Last edited 7 years ago by anhi (previous) (diff)

comment:12 Changed 7 years ago by anhi

milton_x line remade due to being flown at a different altitude to the other lines.
Altitude 5170 feet
Pitch:-0.00295
Roll:0.0002

Last edited 7 years ago by anhi (previous) (diff)

comment:13 Changed 7 years ago by anhi

LiDAR delivery created

comment:14 Changed 7 years ago by besm

LiDAR delivery delivery-checked. I found the following issues:

  • The reported minimum and maximum values of Y for each of the flightlines under "Per flight line statistics" in the readme appear to be wrong, they don't reflect the values of the LiDAR data, and seem unrealistic.
  • proj_tidy.sh complains about the data quality report being missing, it's there but it's differently named. Either proj_tidy.sh or make_lidar_delivery.py probably needs to change. The exact filename of the data quality report probably isn't important.
  • The proj_tidy.sh script kicks up about lidar_intensity_vectors_screenshot.jpg being missing, I don't think this is a problem, but best check.

comment:15 Changed 7 years ago by anhi

  • Read_Me remade with the minimum and maximum Y values corrected.
  • LiDAR data quality report is named correctly, proj_tidy.sh probably should be updated.
  • We do not have the vectors to create the LiDAR intensity vector screenshot.

comment:16 Changed 7 years ago by besm

Looks okay now. proj_tidy.sh still complains about the logsheet being absent, but it's definitely there, so I'm marking this project as ready to deliver.

comment:17 Changed 7 years ago by anhi

Hawk delivery created, eagle vectors still not arrived so will create Hyperspectral delivery

comment:18 Changed 7 years ago by anhi

Hyperspectral delivery created

comment:19 Changed 7 years ago by anhi

Hawk line 1 level 1 file remade. Believe the error had something to do with the header and the bil file being made on different days before/after the boresight.

comment:20 Changed 7 years ago by besm

Appears to be ok. I found only one thing that didn't look right:

In FastQC, when opening the file h206b011b.bil, it warned that the file size of the bil in the header and the actual file size didn't match. The time of creation of the bil seemed completely wrong too. It's been re-made and there should be no problem now, BUT: We don't know what caused this.

Otherwise, all good.

comment:21 Changed 7 years ago by anhi

Vector screenshots created and added to delivery, ready to make delivery of everything except LiDAR FWF.

comment:22 Changed 7 years ago by besm

Redelivery checking, delivery has been remade with the vector overlays.

comment:23 Changed 7 years ago by besm

Updated LiDAR data quality report in all known copies of delivery to November 09 2012 version.

Delivered everything, camera (again), hawk, eagle, LiDAR (no FWF) to Karen Anderson on 13/11/2012 on disk 132.

Last edited 7 years ago by besm (previous) (diff)

comment:24 Changed 7 years ago by besm

  • Description modified (diff)

comment:25 Changed 7 years ago by anhi

SCT Values

LineEagle SCTHawk SCT
1 -0.02 -0.06
2 -0.02
3 -0.06 -0.02
4 -0.02 -0.06
5 -0.02 -0.05
6 -0.02 -0.05
7 -0.02 -0.06
8 -0.02 -0.05
9 -0.02 -0.06
10 -0.02 -0.06
11 -0.02 -0.06
12 -0.02 -0.06
13 -0.02 -0.02
14 -0.02 -0.06
15 -0.02 -0.06
16 -0.02 -0.06
17 -0.02 -0.06
18 -0.04 -0.06
19 -0.02 -0.04
20 -0.03 -0.06
21 -0.06 -0.05

comment:26 Changed 7 years ago by anhi

Delivered FWF LiDAR to Karen Anderson. Sent on disk 147 on 07/01/13.

Last edited 7 years ago by anhi (previous) (diff)

comment:27 Changed 7 years ago by anhi

  • Description modified (diff)

comment:28 Changed 7 years ago by anhi

Archiving - Made available to NEODC (17/04/13)

comment:29 Changed 5 years ago by dac

LAS files reexported from ALSPP with AGC value in point source ID field. Sent to Steve Hancock via FTP 09/02/2014.

comment:30 Changed 22 months ago by asm

Archiving

Reprocessed LiDAR data has been uploaded as well as hyperspectral delivery (not to be found in CEDA). JSON files created and uploaded as well and CEDA has been notified (31/01/2018).

Note: See TracTickets for help on using tickets.