Opened 10 years ago
Closed 10 years ago
#527 closed flight processing (fixed)
BGS12/01, flight day 163c/2014, Merthyr
Reported by: | knpa | Owned by: | benj |
---|---|---|---|
Priority: | alpha 4 medium | Milestone: | 2014 data processing completion |
Component: | Archiving | Keywords: | |
Cc: | dap | Other processors: | tec |
Description (last modified by tec)
Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/BGS12_01-2014_163c_Merthyr/
Data arrived from ARSF via network transfer on 13/06/2014
BGS12/01 Scientific objective: unknown
BGS12/01 Priority: 8
PI: Colm Jordan
Sensors:
Camera (22/10/2014), Archvied 13/05/2015
LiDAR (22/10/2014), Archvied 13/05/2015
FW LiDAR (22/10/2014), Archvied 13/05/2015
Change History (28)
comment:1 Changed 10 years ago by knpa
comment:2 Changed 10 years ago by knpa
- Description modified (diff)
comment:3 Changed 10 years ago by tec
Started RCD processing.
comment:4 Changed 10 years ago by tec
Started nav processing
comment:5 Changed 10 years ago by tec
Basestation Data | |
---|---|
Latitude | 51 57 10.38483 |
Longitude | -3 22 54.24611 |
El Height | 242.211m |
comment:6 Changed 10 years ago by tec
CARI Basestation not used.
Processed the GPS time from 388920.000 till 393600.000
Set the elevation mask to 13.5 degrees to achieve the best possible results with an L2C phase correction of 0.25 cycles.
There is a spike in the latitude seperation which goes above a seperation of 0.1m this spike could affect upto the first 10 seconds of flightline number 8.
comment:7 Changed 10 years ago by tec
Finished Nav processing.
Started RCD processing.
comment:8 Changed 10 years ago by tec
Finished RCD processing
comment:9 Changed 10 years ago by dap
Started delivery checking RCD
comment:10 Changed 10 years ago by dap
RCD delivery check complete. No problems were found.
comment:11 Changed 10 years ago by tec
Starting LiDAR processing.
comment:12 Changed 10 years ago by tec
Having a range gate problem with the LiDAR.
comment:13 Changed 10 years ago by tec
Continuing LiDAR processing.
comment:14 Changed 10 years ago by tec
LiDAR
Flight line | Roll | Pitch |
---|---|---|
120614 | -0.005809263 | -0.000857190 |
121418 | -0.005809263 | -0.000857190 |
122250 | -0.005809263 | -0.001157190 |
123045 | -0.005609263 | -0.000857190 |
123819 | -0.005889263 | -0.001157190 |
124552 | -0.005509263 | -0.000857190 |
125347 | -0.005709263 | -0.000857190 |
130115 | -0.005609263 | -0.000857190 |
131410 | -0.005609263 | -0.000857190 |
comment:15 Changed 10 years ago by tec
Ready for DC
comment:16 Changed 10 years ago by dap
Beginning LiDAR Delivery Check
comment:17 Changed 10 years ago by dap
LiDAR Delivery Check
Complete. Found the following minor problems:
- Weather notes, altitude and speed not present on typed up logsheet
- PI has not been emailed about vectors yet - ask before data are sent.
- Both documents in doc/ are named wrong - I've renamed these.
- sup file does not need to be delivered - I've removed this.
- incase in "Data details" section is two words.
- Data quality remarks - be more specific (say which flightline has the hole) and, if you know why it has the hole, say why and what this means. Instead of "There is cloud at the end of most flight lines.", I would write something more detailed like "This dataset was severely affected by cloud coverage. This has been classified as noise (classification 7)."
- Dan's surname is spelt wrong in the readme, page 11 ("Clewly" should be "Clewley").
- Discrete ASCII flightlines should have CRLF line terminators
- Too much foliage has been classified as noise. This will need to be classified to classification 1 before the data are sent. Will then need to re-sort the LAS files using lassort, convert them to ascii and copy the classification over to the las1.3 files.
Dataset will need to be rechecked when the LAS files have been reclassified.
comment:18 Changed 10 years ago by tec
LiDAR
Disregarding stuff about weather notes, logsheet is fine. Data quality says the first flightline has the hole, that is sufficient.
comment:19 Changed 10 years ago by tec
LiDAR
Ready for DC
comment:20 Changed 10 years ago by dap
LiDAR Delivery Check
- Pre-vector email still needs to be sent to PI - ensure this is done before delivery of data.
- Typos still existed in read me document with Dan's surname and the word "incase" - I have fixed these.
- Have also removed knpa from the contact details section in read me (not a problem in first quality check as he was still at PML at this point).
- las1.0/ was incorrectly named - have renamed this to las1.2.
- ascii las file line endings needed to be converted to CRLF line terminators - I've done this using unix2dos * in ascii directory.
Full waveform data has not yet been checked - waiting for Windows machine to become free.
comment:21 Changed 10 years ago by dap
LiDAR Delivery Check
laszip completed, created 9 wdz files and 9 laz files, as expected. Will check las 1.3 files in Wave Viewer when Windows machine becomes available.
comment:22 Changed 10 years ago by dap
LiDAR Delivery Check
Checked files in Wave Viewer. The following records don't have waveforms:
- File 01: the first ~10,000
- File 02: the first ~11,000
- File 04: the first ~50,000
- File 07: the first ~45,000
- File 08: the first ~16,000
comment:23 Changed 10 years ago by tec
So the delivery is ok?
comment:24 Changed 10 years ago by dap
LiDAR Delivery Check
Spoken to mark1 regarding the missing waveforms, this is a known issue. Data at
BGS12_01-163c-lidar-20140926 is therefore ready to be delivered.
comment:25 Changed 10 years ago by dap
Copying LiDAR data and photography to hard drive for delivery.
comment:26 Changed 10 years ago by dap
- Cc dap added
- Component changed from Processing: general to Archiving
- Description modified (diff)
- Other processors set to tec
- Owner set to benj
LiDAR data and photography delivered to Dr Colm, 22/10/2014.
comment:27 Changed 10 years ago by tec
Archiving
Starting Archiving
comment:28 Changed 10 years ago by tec
- Description modified (diff)
- Resolution set to fixed
- Status changed from new to closed
Archiving
Done confirmed as of 13/05/2015 12:10
Deleted corrupted webcam image 124333