EUFAR10/02, 199b/2010, Santander

[jb362]

Data location: ~arsf/arsf_data/2010/flight_data/western_europe/EUFAR10_02-2010_199b-Santander

Data arrived from ARSF via network transfer on 26/07/2010.

Scientific objectives:

1 Development of a reliable tool to estimate coastal water quality indicators by using remote sensing techniques, both airborne and satellite.

1.1. Development of a set of semi-empirical algorithms based on hyperspectral airborne and in-situ data for estimating the concentrations of the water constituents;
1.2. Migration of the developed algorithms into the satellite workflow.

2. Implementation of an automatic warning system based on satellite imagery processing;

3. Inclusion of the information obtained by means of remote sensing in the dataset used for the calibration of regional hydrodynamic models.

Priority: a4m - awaiting confirmation

PI: Castillo-Lopez

Sensors: ¶

• Eagle (27/08/2010)
• Hawk (21/12/2010)
• Leica LIDAR (21/12/2010)
• RCD Digital photography (27/08/2010)

[anch]

I'll start processing the Applanix for this now.

[anch]

Applanix and IPAS for this project completed.

[anch]

Because this project is not in the UK, and making a DEM using STRM data is a pain, I have started LiDAR processing which I will eventually use to produce a DEM to process the hyperspectral with.

[anch]

LiDAR has lots of noise (mainly over ocean) and may take a while to classify, so I have put the hyperspectral back on the processing list in case anyone is looking for a hyperspectral project to get on with.

[jb362]

Starting hyperspectral processing.

[iopa]

Processing camera.

[iopa]

Checking hyperspectral.

[iopa]

Hyperspectal delivery check report:

1) rename lev1's and screenshots to contain the lettered julian day 199b.

Otherwise all's well.

[jb362]

Delivery check fixes complete.

[jb362]

Checking camera

[jb362]

All good, but again PI needs to be Dr. Castillo-Lopez

[iopa]

Camera is ready to deliver.

[jb362]

Camera and Eagle data delivered.

[knpa]

Data moved from overflow to repository.
Can now be r-synced.

[benj]

Have downloaded 1s RINEX data from University of Cantabria and copied to repository. Relevant section of email from PI was as follows:

SANTANDER and TORRELAVEGA stations are in relation with the calibration site "Santander1" and the LAREDO station for the area of validation (Santander 2). Santander 1 data taken on 18th July and Santander2  data taken on 19th July.
In the corresponding tabs appear links to download RINEX data.
 
LINKS of interest:
 
http://www.gnss.unican.es/estaciones/cant.asp
 
http://www.gnss.unican.es/estaciones/trvg.asp
 
http://www.gnss.unican.es/estaciones/lare.asp
 
ftp://ftpgnss.digteg.unican.es/rinex
 
Access to real time corrections using the standard protocol NTRIP (Networked Transport of RTCM vía Internet Protocol):
 
URL 	http://ntrip.unican.es:2101/	 
IP:    	193.144.202.127	 
Port: 	21 
User: 	anonimous
 
link: http://www.gnss.unican.es/servicios/services.asp

[benj]

Note I believe the Santander station mentioned with code CANT is the data I have downloaded from REIN. This is because if you go to the first link given the title of the web page is "Estación de Reinosa"

[knpa]

Appears to be an issue with the bandset labels in the header files; they start at 900nm which is lower than it should be. Possibly incorrect bandset selected or none specified. Will leave this until end of the year and new Hawk calibration.

[iopa]

LiDAR data has been checked;

readme contains the DEM section title twice
in the data quality section it is written elipsoid with one l

dem/README...txt needs correcting for SRTM references

the data seems correct, ready to deliver.

[emca]

Eagle and Hawk SCT's

Line	Eagle	Hawk
1	-0.05	0.02
2	0.08	-0.06
3	0.03	0.01
4	0.05	-0.03
5	-0.05	-0.01
6	0.01	0.01
7	0.02	-0.03
8	-0.01	-0.01
9	-0.03	0.02
10	-0.07	0.02
11	0.01	-0.01
12	0.03	0.04
13	0.35	0.52
14	0.08	0.05
15	0.04	0.04
16	0.08	-0.05
17	-0.06	0.00
18	-0.01	0.00
19	0.00	-0.01

I used a LiDAR intensity image and the Eagle data to find the SCT's for the Hawk as the lines were not overlapping and most of them did not contain sufficient wobbles to correct the timing. Hawk line 13 had no sync. Lines 11 & 19 had bends so were processed using -l 0 7500 and -l 750 17968 respectively, cutting off ~ 200 lines of data.
Hawk delivery has been created.

[anch]

Hawk Delivery checked.

Looks fine to deliver.

[emca]

Hawk lev1 files reprocessed and saved in delivery folder

[anch]

Hawk lev1 re-checked: Ready for delivery

[anch]

Hawk and Lidar delivered 21/12/2010