CR11/04, flight day 223/2011, Castro Verde

[knpa]

Data location: /users/rsg/arsf/arsf_data/2011/flight_data/spain_portugal/CR11_04-2011_223_Castro_Verde/

Data arrived from ARSF via network transfer on 16/08/2011

CR11/04 Scientific objective:

CR11/04 Priority: a4h

PI: Patrick Hostert
PI: Patrick Osborne

Notes: This project is the same as EUFAR11/04.

Sensors:

Eagle (11/10/2011)
Hawk (11/10/2011)
LiDAR (11/10/2011)

[emca]

Processed the navigation data and created sol, camera sol and sbet files.

[adbe]

LiDAR processed using alspp, now checking difference between flightlines

[adbe]

Started to process hyperspectral

[adbe]

Have found difference between flightlines

[adbe]

Classified LiDAR, now making delivery directory

[adbe]

The intensity image of all LiDAR is poor, so I am splitting it into 2 intensity images: high and low altitude

[adbe]

LiDAR data ready for delivery check

[adbe]

Have made sct's for hyperspectral, running on correlator. The flightlines are very large

[adbe]

Got results from correlator and checked them, making hyperspectral delivery

[adbe]

Hyperspectral now ready for delivery check

[knpa]

Beginning delivery check.

[knpa]

Delivery check complete.

All looks good apart from the following:

1. DEM name should be in the format described on the project structure wiki page, specifically aster should be capitalized and if the DEM was formed from LiDAR too it should be lidar-ASTER.
2. If DEM is pure ASTER then you need to include a misc directory with a spheroid-geoid seperation grid (sphsep15lx.grd) - check this with Mark though.
3. I note from the screenshots that each flightline has a coloured streak on one side (purple for eagle, green for hawk). I don't know what could cause this but it might be worth looking into (ask Ben?).
4. Need to Unix2dos the hawk bad pixel text files (I think)
5. First and last bands blank for all Eagle files - need to mention in Readme if not mentioned elsewhere.

Note that two deliveries need to be made, to both Patricks.

[emca]

Delivery checked LiDAR data:

The high altitude flightlines are giving z values that are significantly lower than the low altitude lines. We had the same problem with day 097, ticket #392 (this project covers the same area). Can you try to manually adjust the height of the high altitude lines to compensate for the incorrect range correction (due to the low intensity values)?

Apl compatible DEM is only 317 bytes - I'm guessing something went wrong with the conversion, need to re-create this.
Logsheet is displaying altitude in feet, but it says it is in meters - this need fixing.
You should mention in Readme that the intensity values of the high flightlines are very low (due to the high altitude).

[adbe]

Hyper delivery

• I have capitalized ASTER
• Don't need to include sphsep15lx.grd as when dem was made it was elevated to wgs84 spheroid
• Done unix2dos on text files
• Mentioned in ReadeMe about eagle bands

Holding off delivery until we figure out what the coloured streak is caused by.

[adbe]

LiDAR delivery

• Corrected z value for high altitude flightlines
• Remade apl DEM
• Remade logsheet with correct altitudes
• Mentioned in readme about low intensity of high flightlines

[emca]

LiDAR delivery check:
Checked DEMs and Readme, all fine there.
The low and high altitude lines line up better now.

Ready to deliver.

[adbe]

LiDAR and Hyperspectral delivered to Patrick Hostert and Patrick Osbourne, on disks 76 and 59 respectively. Sent on 11/10/2011

[mark1]

Hyperspectral hawk bad pixel files and XML files have been re-created and re-delivered to PI (via email). This corrects sample number in bad pixel text files and Eagle IFOV value in XML and extra comments included.

[adbe]

Hyperspectral sct's

line	eagle	hawk
1	-0.06	-0.03
2	-0.10	-0.07
3	-0.06	-0.06
4	-0.06	0.00
5	-0.06	-0.03
6	-0.06	-0.05
7	-0.06	-0.05
8	-0.02	-0.01
9	-0.08	-0.07
10	-0.05	-0.06
11	-0.09	-0.09
12	-0.07	-0.07

[knpa]

Beginning archiving.