The MERis MAtchup In situ Database: MERMAID Kathryn Barker 1, Constant Mazeran 2, Christophe Lerebourg 2, Marc Bouvet 3, David Antoine 4, Michael Ondrusek 5, Guiseppe Zibordi 6, Samantha Lavender 1 With support from Brockmann Consult, Germany. 1 ARGANS Limited, UK. 2 ACRI ST, France. 3 ESA(ESTEC), Netherlands. 4 LOV, France. 5 NOAA, USA. 6 JRC, Ispra, Italy.
MERMAID: MERIS Matchup In situ Database Introduction and background: Several existing projects for ongoing radiometric measurement: BOUSSOLE (David Antoine) AAOT (Guiseppe Zibordi) MOBY (Michael Ondrusek) 2006: Data collation began with a few BOUSSOLE and AAOT marine spectra for atmospheric correction validation within the Quality Working Group (QWG) 2007: More in situ data and auxiliary data (aerosol etc) added, and inclusion of MOBY (NOAA). Also web interface developed (extraction page..) 2008: Importance increased, more protocol in data processing & availability to external people (incl. NASA now). Aim for MERMAID: To develop and maintain a database of coincident in situ data (marine) together with their MERIS product counterpart extractions To support and sustain Cal/Val activities: vicarious adjustment, test algorithms etc Ongoing effort Sentinel 3.
MERMAID: Access and Data policy Web site access: via CalVal Portal or directly from extraction page: http://calvalportal.ceos.org/calvalportal/mermaid Access: initially restricted to QWG members. Password protected: record kept of password recipients Data submission policy: access given to contributing PI s. Data access policy: in situ PI must be contacted and cited in within any publication. (data download signifies user agreement to these terms) CalVal Portal maintained by Brockmann Consult: http://www.brockmann consult.de/calvalportal/welcome.do Information, submissions and requests to: mermaid@esa.int
How MERMAID works: Format to MERMAID template MERIS matchups with in situ & extractions Normalisation of in situ and MERIS PI, site, date, time, lat, lon, θs, chl, rho(λ) e.g. τ(550), rho_toa, rho_aer... Normalised & corrected for bidirectionality
Retrieval of relevant in situ data from scientific institutes Invitation letter: Explains MERMAID project and invites PI to contribute data Primary datasets: L w (λ) and/or ρ w (λ) plus chlorophyll (Chl) and metadata Updated policy: offer contributing PI s access to MERMAID Examples of the extensive contacts database Pierre Yves Deschamps LOA, France Roland Doerffer GKSS Research Centre, Germany. Kevin Ruddick MUMM, Belgium Guiseppe Zibordi JRC, Italy (Oversees AERONET dataset) Dominique Durand NIVA, Norway Dr. David Antoine LOV, France Dr. Mira Morovic. Institute of Oceanography, Split. Croatia Dr. Oleg Kopelevich. Shirov Institute of Oceanology, Russia Dr. David McKee University of Strathclyde, Scotland Dr. Susanne Kratzer University of Stockholm, Sweden Jeremy Werdell NASA, USA (SeaBASS/NOMAD US archives) Dr. Arnold Dekker CSIRO, Australia Dr. Carlos Garcia Universidade Federal do Rio Grande, Brazil
Data acquired to date, for matchup with MERIS Several datasets have been submitted for inclusion in the database: Dataset Location Source No. of datapoints BOUSSOLE Ligurian Sea (W. Med) David Antoine (LOV) 13,893 AAOT (AERONET) Venice Tower Guiseppe Zibordi (JRC) 308 MOBY Lanai, Hawaii Michael Ondrusek (NOAA) ~1300 (NILU Adriatic Sea Dominique Durand (NIVA) 21) SIMBADA (in Prep.) Med, S. Pacific, Atlantic, Pierre Yves Deschamps (LOA) 1693 (2002 2004) Indian Ocean, NOMAD (in Prep) Widespread SeaBASS (Jeremy Werdell, NASA) 534 (2002 2004) Asko (in Prep.) Baltic Sea
How MERMAID works: Format in situ to MERMAID format MERIS matchups with in situ & extractions Normalisation of in situ and MERIS PI, site, date, time, lat, lon, θs, chl, rho(λ) e.g. τ(550), rho_toa, rho_aer... Normalised & corrected for bidirectionality
How MERMAID works: Format in situ to MERMAID template MERIS matchups with in situ & extractions Normalisation of in situ and MERIS PI, site, date, time, lat, lon, θs, chl, rho(λ) e.g. τ(550), rho_toa, rho_aer... Normalised & corrected for bidirectionality
How MERMAID works: Format in situ to MERMAID template MERIS matchups with in situ & extractions Normalisation of in situ and MERIS PI, site, date, time, lat, lon, θs, chl, rho(λ) e.g. τ(550), rho_toa, rho_aer... Normalised & corrected for bidirectionality
Formatting In situ processing: Consistent with MERIS (Look Up Table) processing For case 1 water: fully normalised ρ wn (λ) corrected for bidirectionality (f/q) For case 2 water: NN being tested for normalisation Spectral adjustment to be done if necessary Extraction includes: Matchups identification: site, PI, date, lat, lon contributing PI kept in the database Geometry Marine signal: in situ & MERIS both normalised using the same process Top of Atmosphere signal Intermediary data: glint corrected signal, aerosol reflectance models, optical thickness, case 2 waters residual reflectance. Either: 1, 3x3 or 5x5 pixels. Output is one file with all data & one file averaged Future inclusions: Other data possible happy to accept what is available from PI at time of submission and MERMAID can be expanded later to hold more
How MERMAID works: Format in situ to MERMAID template MERIS matchups with in situ & extractions Normalisation of in situ and MERIS PI, site, date, time, lat, lon, θs, chl, rho(λ) e.g. τ(550), rho_toa, rho_aer... Normalised & corrected for bidirectionality
MERMAID: Extraction page BOUSSOLE AAOT MOBY...more to add 2002 2008 Traceability of the data CSV: Extraction data Basic stats
Example uses of the data at present: Vicarious adjustment Atmospheric correction validation and verification, incl. Bright Pixel atmospheric correction Algorithm development and validation Future: Ongoing project: Continue to establish contacts, retrieve and process in situ data Extension to case 2 Potential expansion of database to other in situ measurements: short term possibilities include Chl (already used where available in the normalisation procedure), the aerosol optical thickness and Angstrom exponent (useful in atmospheric correction validation and the vicarious adjustment assessment). Will provide support products for Sentinel 3 On going logo development