EUFAR10/02, 200/2010, Santander

[jb362]

Data location: ~arsf/arsf_data/2010/flight_data/western_europe/EUFAR10_02-2010_200_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 (21/12/2010)
• Hawk (Requested by PI)
• Leica LIDAR (21/12/2010)
• RCD Digital Photography (21/12/2010)

[jb362]

Awaiting logsheet

[ella]

Beginning navigation processing

[anch]

Starting Applanix (and probably IPAS) processing for this project.

[iopa]

Taking camera.

[emca]

Starting LiDAR processing

[emca]

There is a problem with the IPAS for this project. Moving on to a different project until this can be resolved.

[jb362]

There is also a problem with the applanix for this project which I do not know how to resolve. Because there is no IPAS .sol file or applanix .sbet file, none of the camera, Lidar, or hyperspectral data can be processed at present.

[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]

Applanix and IPAS have been completed.

[iopa]

Camera is ready to be checked.

Test images were images 1-8.

On a different note; eagle/hawk files were named 200a for no apparent reason, the logsheet too does not have a flight letter, so they were renamed with the 'a' removed.

[emca]

Starting LiDAR and Eagle

[emca]

Eagle data is ready for delivery check at
~airborne/workspace/EUFAR10_02-2010_200_Santander/delivery/20101125/

[emca]

Delivery checked the camera data at
~airborne/workspace/EUFAR10_02-2010_200_Santander/delivery/20101109

Data is good, ready to deliver.

[emca]

LiDAR data is ready for delivery check at
~airborne/workspace/EUFAR10_02-2010_200_Santander/delivery/20101126

[emca]

SCT (and GPT) offsets for Eagle data:

Line Number	SCT (GPT)
01	+0.03
02	0.00
03	-0.10 (-0.10)
04	0.00
05	0.00
06	-0.02
07	-0.12 (-0.08)
08	+0.03
09	+0.02
10	-0.08 (-0.12)
11	-0.01
12	+0.37

Notes on Eagle processing:

Line 05 had an incorrect GPS stop time in the raw header file so this was changed (original file kept as .hdr-original)
Line 08 had a bend in it so processed using -l 0 10100 in azspec (excluding the last ~400)
Line 12 had no sync information

[knpa]

Delivery Checking LiDAR

[knpa]

Delivery check complete.

All looks good and ready to deliver apart from:

• EUFAR10_02-2010_200.dem should be EUFAR10_02-2010-200.dem
• Low min Z values (~250m), is this due to water?
• Readme says DEM resolution is 2m, actually 5m.

[benj]

Fixed project ID in ticket (was down as EUFAR10/01)

[anch]

Eagle, Camera, and LiDAR all delivered 21/12/2010