due esurge requirements baseline - storm surge · 1.3 document contributions table 1-2 indicates...

DUE eSurge

Requirements Baseline

Customer ESA / ESRIN

Author Logica

ESRIN Contract Number 4000103880/11/I-LG - e-Surge

Logica Project Reference UK EC 231827

Document Reference eSurge_D50

Version/Rev Issue 2.1

Date of Issue 08/12/2011

Category Approval

Prepared by:

Phillip Harwood and others

(See section 1.3)

Reviewed by: Geoff Busswell

Logica

Accepted by

Craig Donlon

ESA Technical Officer

eSurge Requirements Baseline

D-90, Issue 2.0 8 December 2011

/ 102

© 2011 Logica UK Ltd.

AMENDMENT HISTORY

Version Date Change Description Author

1.0 25/8/2011 Initial issue prior to SRR. Phillip Harwood and others

(See section 1.3)

2.0 31/10/2011 Updated in response to SRR RIDS:

RID Section(s) RID Section(s)

CD01 3.2 CD28 5.5.2

CD02 Figure 3-1 CD29 8.2

CD03 3.2 CD30 6 (all)

CD04 3.2 CD31 6 (all)

CD05 Throughout CD32 6 (all)



CD08 3.3.2, 3.3.3 CD35 6.5

CD09 3.3.2 CD36 6 (all)

CD10 3.3.3 CD37 7.1

CD11 4.1 CD38 7.1

CD12 9.4 CD39 7.2

CD13 4.1.2.2 CD40 7.6

CD14 4.1.2.7 CD41 9.4

CD15 4.4.1.2 CD42 8.2

CD16 No change CD43 8.5

CD17 Table 4-1 CD44 8.6

CD18 4.1.2.5 CD45 8.6

CD19 4.1.5 CD46 No change

CD20 4.1.7 CD47 8.1

CD21 4.2 CD48 8.2

CD22 5.2.1 CD49 No change

CD23 5.2.2 CD50 9

CD24 5.3.1 CD51 9

CD25 5.4.1 CD52 9.4

CD26 No change CD53 9.3

CD27 5.5.1 CD54 9.4

To support the responses to RIDs CD05 and CD06, all requirements have been renumbered.

As for issue 1.0

2.1 08/12/2011 Requirements 265, 315 and 725 added. Additional minor amendments and corrections.

Phillip Harwood


This document contains information which is confidential and of value to Logica. It may be used only for the

agreed purpose for which it has been provided.

eSurge Requirements Baseline D-90, Issue 2.0 8 December 2011


/ 102

DISTRIBUTION

Name Company

Craig Donlon ESA

Paolo Cipollini

Kevin Horsburgh

Helen Snaith

Maureen Pagnani

NOC

Ned Dwyer

Rory Scarrott

Declan Dunne

Anthony Patterson

CMRC

Jun She

Jacob Hoyer

Mikhail Dobrynin

Weiwei Fu

DMI

Tilly Driesenaar

Ad Stoffelen

KNMI

Phillip Harwood

Geoff Busswell

Anusha Chellappah

Logica



/ 102


Contents

1 INTRODUCTION ............................................................................... 6

1.1 Purpose and Scope ................................................................................................... 6 1.2 Document Structure .................................................................................................. 6 1.3 Document Contributions ............................................................................................ 8 1.4 Readership and Change Forecast ............................................................................ 8 1.5 Applicable and Reference Documents ...................................................................... 8 1.6 Definitions and Acronyms ......................................................................................... 9

2 SUMMARY OF ESURGE REQUIREMENTS ................................... 12

2.1 Overview ................................................................................................................. 12 2.2 Key Requirements and Objectives .......................................................................... 12 2.3 Trade-offs made for the Requirements Baseline .................................................... 14

3 SELECTION OF ESURGE AOI AND SEVS .................................... 16

3.1 Introduction.............................................................................................................. 16 3.2 eSurge AOI.............................................................................................................. 16 3.3 Catalogue of Case Study Events ............................................................................ 19 3.4 External Bathymetry Data for each AOI .................................................................. 23

4 ESURGE PRODUCTS PROVIDED ................................................. 24

4.1 eSurge Products ..................................................................................................... 24 4.2 Data Product Handbooks ........................................................................................ 32

5 SURGE EVENT ANALYSIS AND REPOSITORY SERVICE (SEARS) .......................................................................................... 34

5.1 Overview ................................................................................................................. 34 5.2 Data Types and Formats ......................................................................................... 34 5.3 Metadata Requirements .......................................................................................... 36 5.4 Product Delivery ...................................................................................................... 37 5.5 Data Access Tools .................................................................................................. 39 5.6 Interface Requirements ........................................................................................... 40

6 RE-ANALYSIS AND DATA ASSIMILATION EXPERIMENTS ......... 41

6.1 Aims and Objectives ............................................................................................... 41 6.2 Models and Inputs Used ......................................................................................... 41 6.3 Reanalysis Experiments .......................................................................................... 43 6.4 Data Assimilation Experiments ............................................................................... 44 6.5 Assesment of Reanalysis and Data Assimilation Experiments ............................... 46 6.6 Communication of Key Operational Benefits .......................................................... 46

7 ESURGE LIVE ................................................................................. 47

7.1 Overview ................................................................................................................. 47 7.2 eSurge Live Triggering and Notifications ................................................................ 48 7.3 eSurge Live NRT Data Products ............................................................................. 49 7.4 Interface Requirements with SEARS ...................................................................... 49 7.5 eSurge Live User Support ....................................................................................... 50 7.6 eSurge Live Service Availability .............................................................................. 50



/ 102

8 CONTENT AND FUNCTIONALITY OF THE ESURGE WEB PORTAL .......................................................................................... 51

8.1 Web Portal Overview .............................................................................................. 51 8.2 Portal Availability ..................................................................................................... 52 8.3 Project Documentation ............................................................................................ 53 8.4 Outreach ................................................................................................................. 53 8.5 Data Access ............................................................................................................ 54 8.6 Online Tools ............................................................................................................ 55

9 TRAINING AND OUTREACH .......................................................... 57

9.1 Overall Objectives of eSurge Training .................................................................... 57 9.2 Distance Learning Requirements ........................................................................... 57 9.3 Workshop Training Requirements .......................................................................... 59 9.4 Other Outreach Activities ........................................................................................ 61

ANNEX A USER QUESTIONNAIRE ................................................................ 62

A.1 About the User Questionnaire................................................................................. 62 A.2 Results of the User Questionnaire .......................................................................... 63

ANNEX B REQUIREMENTS MAPPING .......................................................... 80

B.1 Mapping to SOW Requirements ............................................................................. 80 B.2 Mapping to User Questionnaire .............................................................................. 85

ANNEX C DATA PRODUCT DESCRIPTIONS ................................................ 86

C.1 Coastal Altimetry ..................................................................................................... 86 C.2 Winds ...................................................................................................................... 86 C.3 Satellite SST ........................................................................................................... 87 C.4 Wave Products ........................................................................................................ 87 C.5 Ocean Colour .......................................................................................................... 89 C.6 Sediment Concentration ......................................................................................... 90 C.7 Additional Satellite Products ................................................................................... 90 C.8 In Situ Products ....................................................................................................... 91 C.9 Model Output Products ........................................................................................... 91 C.10 NRT Products.......................................................................................................... 93 C.11 Additional Products ................................................................................................. 96

ANNEX D SEVS UNDER CONSIDERATION FOR INCLUSION IN SEARS .... 99



/ 102


1 INTRODUCTION

1.1 Purpose and Scope

This document is the Requirements Baseline (RB) document for the eSurge project. Its purpose is to capture the requirements that will be used for the remainder of the project, and to record how these requirements were derived.

The requirements in this document will be used to define the scope of the eSurge project subsequent to the System Requirements Review (SRR).

1.2 Document Structure

This document is structured as follows:

Section 1 (this section) is the introduction.

Section 2 gives an overview of the key requirements and of the key trade-offs which have been made.

Section 3 gives the requirements for the Areas of Interest (AOI) and the surge events (SEVs) which eSurge will look at.

Section 4 gives the requirements for the eSurge products.

Section 5 gives the requirements for the SEARS database.

Section 6 gives the requirements for the Reanalysis and Data Assimilation experiments.

Section 7 gives the requirements for the eSurge Live service.

Section 8 gives the requirements for the content and functionality of the Surge web portal.

Section 9 gives the requirements for the training to be provided.

Annex A gives an overview of the results of our user questionnaire.

Annex B gives a mapping between the requirements in this document, those in the SOW, and the results of the user questionnaire.

Annex C gives full details of the data sets to be initially included in the SEARS database.

Annex D lists the SEVs currently under consideration for inclusion in SEARS.

This structure has been based on the document tables of contents provided in [TP], adapted to improve the document flow and to avoid duplication.

[SOW] section 5.2.2 defines the information to be provided in this RB document. Table 1-1 shows where this required content has been supplied.



/ 102

Table 1-1: Mapping between the RB contents required in [SOW] and the contents of this document

Required Content Section(s)

Summary and short discussion of all eSurge user requirements Section 2.2.2, Annex A.2.

Precise geographic locations and maps of eSurge AOIs Section 3.2.

A catalogue of storm surge events (SEVs) over the period 1991-present, their precise geographical locations and maps to be included in the SEARS system

Section 3.3.3, Annex D.

External bathymetric data and the source of this data required by the eSurge project. The eSurge project shall seek appropriate linkages and collaborations to access and improve existing bathymetric data required for storm surge applications within the scope of defined eSurge Areas of Interest (AOI)

Section 4.1.5.

A description of EO products required by the eSurge project Section 4.1.2, Annex C.

Data product format definition for all EO products starting from those described in Appendix-III Table 6

Annex C.

Delivery timeliness and preferred delivery mechanisms for all data sets Section 5.4.

Requirements for specific tools to access and manipulate data (e.g. read software, format conversion software, analysis and presentation of data).

Section 5.5.3.

Specific tools for SEV data analysis, visualisation and manipulation (e.g. diagnostic data set systems, web map server, online GIS tools, etc)

Section 5.5.4.

eSurge EO coastal product specification and accuracy Annex C.

eSurge EO non-coastal product specification and accuracy Annex C.

NWP/NOP/storm surge model system inputs and outputs required to conduct reanalysis and data assimilation experiments

Sections Error! Reference source not found., 6.4.3.

Socioeconomic data to be included in SEARS Section 4.1.6

Historical data products to be included in SEARS Section 4.1.

Storm surge model reanalysis and hindcast data to be included in SEARS Section 6.4.3.

NRT EO services required in support of storm surge systems Section 7.

Content and services of the eSurge web portal Section 8.

In situ data required by the eSurge project for validation and data assimilation by storm surge models

Section 4.1.3.

Validation data and methodology for all eSurge data products and services Section 4.1.7.

SEARS and eSurge-live (NRT) system and interfaces Section 5.

Proposal for reanalysis and data assimilation impact experiments to be conducted in phase 2 to be agreed with the Agency

Section 6.

Storm surge models (including ensemble models) and associated data assimilation systems that may be used in phase 2 of the project.

Section 6.2.2.

Product and system documentation Section 4.2.

Training requirements in the use of eSurge data products and services Section 9.

Other issues that are relevant to the specification of the eSurge project RB Section 2.



/ 102


1.3 Document Contributions

Table 1-2 indicates the people and organisations who have contributed to the writing of this document.

Table 1-2: Document Contributions

Section Primary Author(s) Additional Contributions

Section 1 Phillip Harwood, Logica Anusha Chellappah, Logica

Section 2 Phillip Harwood, Logica Paolo Cipollini, NOC

Helen Snaith, NOC

Section 3 Phillip Harwood, Logica Paolo Cipollini, NOC

Kevin Horsburgh, NOC

Section 4 Paolo Cipollini, NOC Phillip Harwood, Logica

Section 5 Helen Snaith, NOC Maureen Pagnani, NOC

Section 6 Kevin Horsburgh, NOC

Jacob Hoyer, DMI

Mikhail Dobrynen, DMI

Section 7 Mikhail Dobrynen, DMI Phillip Harwood, Logica

Section 8 Declan Dunne, CMRC

Section 9 Rory Scarrott, CMRC Ned Dwyer, CMRC

Annex A Anusha Chellappah, Logica Phillip Harwood, Logica

Annex B Phillip Harwood, Logica Anusha Chellappah, Logica

Annex C Paolo Cipollini, NOC

Helen Snaith, NOC

Jacob Hoyer, DMI

Maureen Pagnani, NOC

Tilly Driesenaar, KNMI

Ned Dwyer, CMRC

Annex D Phillip Harwood, Logica Defined in tables.

1.4 Readership and Change Forecast

This is the second issue of this document. It has been thoroughly revised based on comments and RIDs received from ESA at SRR ([SRR-MOM], [RB-RIDS]).

This document will then become the baseline for future development of the project. It will made available for user review, and we will incorporate user feedback where possible, however no further major changes are anticipated.

1.5 Applicable and Reference Documents

Table 1-3 lists the Applicable Documents.

No reference documents have been cited directly in this document. A list of reference documents which have been used in defining the scope of this project is given in [TP].



/ 102

Table 1-3: Applicable Documents

Document ID Document

[Contract] ESA contract for eSurge

Ref: 4000103880/11/I-LG - e-Surge

[SOW] Statement of Work, ref. EOP/SM2135, Issue 2, Revision 1, dated 21 October 2010

[TP] eSurge Technical Proposal,

Ref. UK_672_eSurge, Issue 1.1, dated 8 June 2011

[CLA-1]

[CLA-2]

[CLA-3]

Three sets of clarifications, ref. UK_672/Clarifications/01, UK_672/Clarifications /02 and UK_672/Clarifications /03

[KO-MOM] Minutes of the negotiation meeting held on 8 June 2011, ref. eSurge_MOM_KO, Issue 1.0, dated 8 June 2011

[SRR-MOM] Minutes of the SRR held on 8 September 2011, ref. eSurge_MOM_SRR, Issue 1.0, dated 8 June 2011

[RB-RIDS] Responses to ESA RIDS on the RB document, ESA-RIDS-eSurge-D50-RB-v1.1, dated 16/9/11.

1.6 Definitions and Acronyms

Table 1-4 lists the acronyms and abbreviations used within this document.

Table 1-4: Acronyms and Abbreviations

Acronym Meaning

AOI Area of Interest

AR Acceptance Review

ASAR Advanced Synthetic Aperture Radar (of ENVISAT)

ASCAT Advanced SCATterometer (of MetOp)

ASCLME Agulhas and Somali Current Large Marine Ecosystems

ATBD Algorithm Theoretical Basis Document

ATBD Algorithm Test Procedures Document

BODC British Oceanographic Data Centre

BOOS Baltic Operational Oceanographic System

CDR Critical Design Review

CF Climate and Forecast

CLS Collecte Localisation Satellites

CMRC Coastal & Marine Resources Centre, University College Cork

CNES Centre National d'Études Spatiales

COASTALT Development of Radar Altimetry Data Processing in the Coatal Zone (ESA Project)



/ 102


Acronym Meaning

DARD Data Access and Requirements Document

DEM Digital Elevation Model

DMI Danish Meteorological Institute

DUE Data User Element

ECMWF European Centre for Medium range Weather Forecasting

ENVISAT Environment Satellite

EO Earth Observation

ERS European Remote Sensing satellite

ESA European Space Agency

ESRIN European Space Research Institute

ESTEC European Space Research and Technology Centre

eSurge ESA Storm Surge Project

ETWS Expert Team on Wind Waves and Storm Surges

EU European Union

EUMETSAT European Organisation for the Exploitation of Meteorological Satellites

FAQ Frequently Asked Question(s)

FPS Full Processed Set (of Data)

FR Final Report

FTP File Transfer Protocol

GIS Geographical Information System

HBK Hand Book

HIRLAM High Resolution Limited Area Model

HIROMB High Resolution Operational Model for the Baltic Sea

ICD Interface Control Document

IIT Institute of Information Technology (of Delhi, India)

JCOMM Joint Commission for Oceanography and Marine Meteorology (of the UNESCO IOC and WMO)

KNMI Koninklijk Nederlands Meteorologisch Institut, Netherlands

KO Kick-Off

NASA National Aeronautics and Space Administration

NetCDF Network Common Data Format

NIO National Institute of Oceanography

NMCI National Maritime College of Ireland

NOAA National Oceanic and Atmospheric Administration

NOC National Oceanography Centre

NOP Numerical Ocean Prediction



/ 102

Acronym Meaning

NRT Near Real Time

NWP Numerical Weather Prediction

OpeNDap Open-source Project for a Network Data Access Protocol

PISTACH Prototype Innovant de Système de Traitement pour

l‟Altimétrie Côtière et ‟Hydrologie (CNES project)

PMP Project Management Plan

PSMSL Permanent Service for Mean Sea Level

QRT Quasi Real Time

RB Requirements Baseline

RID Review Item Discrepancy

SAR Synthetic Aperture RADAR

SAR Service Assessment Report (of eSurge)

SEARS Surge Event Analysis and Repository Service

SEV Storm Surge Event

SGDR Sensor Geophysical Data Records

SoW Statement of Work

SPOT Satellite Pour l'Observation de la Terre

SRR System Requirements Review

SSH Sea Surface Height

SSHA Sea Surface Height Anomaly

SST Sea Surface Temperature

TBC To Be Confirmed

TBD To Be Determined

TDS Test Data Set

TR Technical Report

TS Technical Specification

TWLE Total Water Level Elevation

UA User Assessment

UCM User Consultation Meeting

UM User Manual

UNOSAT United Nations Institute for Training and Research (UNITAR) Operational Satellite Applications Programme

WAM Wave Analysis Model

WMO World Meteorological Organisation

WMS Web Map Service



/ 102


2 SUMMARY OF ESURGE REQUIREMENTS

2.1 Overview

The requirements presented in this document have been driven from three main sources:

1. The original Statement of Work from ESA [SOW], which was the result of discussions between ESA and potential users.

2. A User Survey which was carried out by the eSurge project during July-August 2011.

3. Internal discussion within the eSurge project team.

In general, the multiple sources driving the requirements all lead to a consistent Requirements Baseline. However in some cases it is necessary to make trade-offs, either between the needs of different groups of users, or between users’ needs and what is practically achievable. These trade-offs are discussed in section 2.3.

Tradeoffs have been discussed with ESA, and an approach agreed, at SRR [SRR-MOM].

2.2 Key Requirements and Objectives

2.2.1 Key Requirements from ESA

Prior to issuing the ITT for eSurge, ESA extensively discussed the requirements for this project with potential users, culminating in a User Consultation Meeting (UCM) held in Venice in September 2009. These requirements were summarised in [SOW].

ESA’s high level objectives for eSurge are:

To develop, demonstrate and validate the latest advanced techniques for retrieving high-resolution information on TWLE, wind speed and waves in the coastal zone from EO measurements that address storm surge requirements.

To further develop and provide validated coastal altimetry products (based on mature and existing altimeter retracking systems) tuned to storm surge events in a number of user-defined Areas of Interest (AOI).

To provide access to other more general EO data products (e.g. SST, microwave wind and wave products and moderate resolution optical data for coastal inundation mapping) together with NWP, NOP and other socio-economic data that characterise ETC and TC storm surge case study events in a number of user defined Areas of Interest (AOI).

To develop an extensive and open-access database (called the eSurge Event Analysis and Repository Service, SEARS) of EO and other data for historical and contemporary storm surge event (SEV) case studies, with interface tools to access and use eSurge data products, in a number of user defined AOI.

To provide a demonstration NRT service of user defined EO data products and eSurge services in support of operational and experimental forecasting and warning systems.



/ 102

To design and implements, together with the eSurge user community, a number of reanalysis data assimilation and validation experiments for historical and contemporary storm surge events that demonstrate the impact of EO data on storm surge applications.

To encourage and assist the storm surge community to fully exploit the potential for satellite data for storm surge applications through dedicated training activities.

Annex B.1 shows how ESA’s numbered requirements from [SOW] map to the requirements presented in this document.

2.2.2 Key Requirements from Users

The requirements in [SOW] were originally derived by discussions with potential users. However as part of the user consultation exercise we have refined the user requirements, by means of a questionnaire (see Annex A), followed up by direct discussions with selected key users.

The key requirements to emerge from discussion with users are:

1. There is interest in studying storm surges across many areas worldwide, including some (e.g. the SW Atlantic) that were not foreseen in the original SOW. The areas with most interest are the North Sea, Atlantic coast (from the UK down to Spain), Irish Sea and Indian Ocean.

2. Although there is interest in many types of satellite and non-satellite data, there is a clear set of data sets with strong demand. These are:

Coastal altimetry,

Winds (i.e. vector winds),

Tide gauge data,

Bathymetry,

Scatterometry,

Wave spectra,

Flood extent maps,

Specific data sets have been mentioned by some users for specific purposes; for example Oceansat scatterometry data at 25km resolution.

3. There was a wide range of responses for desired service requirements. The most popular responses were “satellite data access”, “accurate forecasting” and “higher resolution models”. It should be noted that some responses are outside the scope of eSurge, and so it will be important to manage users’ expectations.

4. In general, users require data for a time period of 3-5 days before an event.

5. For data download mechanisms, there is a strong preference for ftp. (See the discussion in section 2.3.3 below.)

6. There is a high level of interest in both training courses and user meetings, as well as in having access to dedicated training material.



/ 102


These themes have been reflected in the requirements presented in this document.

Annex A gives more details about the results of the user questionnaire.

2.3 Trade-offs made for the Requirements Baseline

2.3.1 Areas of Interest

There is a worldwide interest in storm surges, with many areas of interest (AOI) among the community. Given that eSurge has finite resources, there is a choice to be made between having good resources for a few AOI, or covering a wide geographical range but with few resources for each area. We have chosen to focus on the following areas of interest:

The seas around the European coast (i.e. AOI-10, AOI-20, AOI-30, AOI-401, AOI-50, AOI-60 and AOI-70).

The North Indian Ocean, covering both sides of the Indian subcontinent (AOI-80 and AOI-90).

This does not mean that we will only include surge events (SEVs) in these areas; we will try to include a number of SEVs from other areas that have high user interest, AOI-130 in particular. However in the non-core areas, we will not be able to provide a comprehensive list of SEVs, relying instead on user input, nor will we necessarily be able to include all data sets.

This does not preclude more comprehensive work in these areas being done in the future, outside the scope of the current project. We are also open to the possibility of making additional data available via SEARS, should other parties be willing to carry out the appropriate processing and, where possible, provide the remote data access service.

This is discussed further in section 3.2.

2.3.2 Data captured for a Surge Event

We have defined each AOI such that, for a surge event within that AOI, the AOI encompasses the area for which relevant data should be captured. That is, for each surge event (SEV) we will capture data throughout the AOI in which the SEV is located, within the appropriate time window.

This approach does have the drawback that it involves making available more data than is strictly needed. For example for a SEV in the Gulf of Lyons, we will capture data throughout the Mediterranean, including areas such as the Ionian Sea that are of limited, or no, usefulness.

However we consider that the advantages of this approach outweigh the disadvantages: it does not require making a subjective judgement about the AOI to include for each

1 Data for AOI-40 (Venice Lagoon and Adriatic Sea) will be done in collaboration with the

eSurge Venice project.



/ 102

event, it simplifies the process of searching for data relevant to a given SEV, and it makes it easy for users to find all SEVs in a given region of interest.


2.3.3 Restrictions on Data Availability/Access

Requirement [REQ-20] of [SOW] called for data to be made available via ftp. This was moreover highlighted by users as their preferred delivery method (annex A.2.6).

However there are problems with ftp as a delivery source, due to the difficulties of securing and monitoring access and the lack of flexibility in the service, so ftp is becoming deprecated as a data access mechanism.

Our understanding is that users’ preference for ftp was driven by the following considerations:

General familiarity with ftp over other possible mechanisms.

A need for scriptable access to data, allowing data access to be automated or semi-automated.

As this is such a strong requirement we will make data available by ftp, however, we intend that the primary method of data delivery will be via an OpenDAP server. This will allow access to the data via a web portal, and also through command-line scripting for automated, or semi-automated processing. Command-line http access via OpenDAP is possible and provides benefits in terms of automated data aggregation, sub-setting and data format conversion, not possible via an ftp interface.


2.3.4 eSurge Live Notifications

For the eSurge Live service (section 7) to be useful, users must be aware that the data are being made available. There will be some mechanism for notifying users when new events are added to eSurge Live. However it is not part of eSurge’s remit to provide forecasts, as these are the responsibility of local agencies in each country. It must therefore be clear to all recipients that any notification from eSurge does not constitute a formal surge warning.

The exact approach to be adopted is still under discussion. This is discussed further in section 7.2.



/ 102


3 SELECTION OF ESURGE AOI AND SEVS

3.1 Introduction

This section looks at the requirements for the Surge Events (SEVs) for which the eSurge project will provide data.

The process of identifying the SEVs is:

1. Identify the Areas Of Interest (AOI) that the project will look at. Although ideally the project would collect data worldwide, in practice it is easier to limit ourselves to specific areas with clearly defined boundaries.

2. Identify the Surge Events within these areas of interest for which data will be collected. This involves specifying criteria to define a SEV, which is not necessarily a trivial task.

3. Identifying the time around an event for which data will be collected. Data are needed before an event to show the evolution of the storm, while some post-event data, especially inundation data, may also be relevant.

3.2 eSurge AOI

For the purposes of eSurge, an Area of Interest (AOI) is a geographical region chosen such that it includes locations or stretches of coast which are prone to coastal flooding, together with a region of sea or ocean adjoining this coast.

For each Surge Event (SEV) within a given AOI, we will look for all data available within the same AOI as the SEV. These data will be made available via the SEARS system.

To define the eSurge AOI, the following criteria are applied:

The region of sea or ocean contained in an AOI should be sufficiently large to allow the evolution of the storm to be studied using pre-event data sources, such as SST, which are available for large area.

To simplify the process of automatically collecting available data, the boundaries of the AOI should be defined as simply as possible. Ideally they should be simple “rectangular” areas whose boundaries are along lines of fixed longitude and latitude.

Given these criteria, we have defined the Areas of Interest listed in Table 3-1 and illustrated in Figure 3-1.



/ 102

Figure 3-1: eSurge Areas of Interest (Red=core, blue=non-core).

In several cases AOI overlap with each other, so that it is possible for a surge event to lie within two or more AOI. In such cases, it will need to be assessed on a case by case basis which AOI is most appropriate, or whether both are needed.

For example, a surge in the Kattegat may require data for both the North Sea (AOI-10) and Baltic Sea (AOI-50). However for a SEV in Cork, it is clear that the NE Atlantic (AOI-20) is more appropriate than the NW continental shelf (AOI-10).

Some AOI are nested within larger AOI, for example the Adriatic (AOI-40) is nested within the Mediterranean (AOI-70). In the case of a SEV within AOI-40, data would only be collected for the smaller area and not the larger.

For any given SEV, the data provided will be for the whole AOI, and so will include information which is not relevant to that event. For example if there was a storm surge in the Gulf of Lyons, for that event we would be collecting data across AOI-70 (the Mediterranean sea), including such areas as the Ionian sea which are of no interest for studying this surge.

Although this approach has the disadvantage that more data will be stored than strictly needed, it has the advantage of simplicity, since we do not need to make a subjective judgement about the AOI to include for each event.

It should be noted that the intended delivery mechanism for data will allow users to limit (both in time and in space) the data they choose to download to that which is appropriate for their own application (see section 5). This is especially applicable to users with low-bandwidth, for whom it would be a major issue if they were to be forced to download unnecessary data. For these users, the selection of data will also be possible without the use of a bandwidth intensive graphical interface.



/ 102


Table 3-1: Definition of the eSurge Areas of Interest

AOI General Area Boundaries Notes

AOI-10 NW European Continental shelf

47°N-62°N

12°W – 12°E

Includes Dutch, UK, German, Danish, Irish and French coasts.

This box has been extended to 62°N to include the full shelf and the Shetland Archipelago.

AOI-20 NE Atlantic Ocean 40°N-60°N

20°W – 3°E

Includes UK, Irish, French, Spanish and Portuguese coastlines.

AOI-30 Irish Sea 50°N-56°N

7°W – 2.5°W

This region overlaps with AOI-10 and AOI-20, see discussion above.

AOI-40 Venice Lagoon and Adriatic Sea 39°N – 46°N,

11°E – 21°E

This should be included in AOI-70 but is granted a specific effort given the importance of surges in the Venice area and the dedicated monitoring and modeling effort, in collaboration with eSurge Venice

AOI-50 Baltic Sea 52°N – 67°N,

8°E – 29°E

AOI-60 Black sea 40.5°N – 47.5°N,

27.5°E – 42°E

AOI-70 Mediterranean Sea 27°N – 47°N,

9°W – 37.5°E

AOI-80 Arabian sea and West Indian Coastline

0°N – 25°N

50° E-80°E

Coastal zones of Arabian sea, India, Pakistan, Oman.

AOI-90 Bay of Bengal 0°N – 25°N

80°E – 100°E

Coastal zones of Bay of Bengal, i.e. India

(Andhra Pradesh, Orissa, West Bengal, Tamil Nadu), Sri Lanka, Myanmar, Bangladesh

AOI-100 Coastal zones of Thailand and Malaysia

0°N – 16°N

95°E – 108°E

AOI-110 Coastal zones of Australia 45°S – 8.5°S

112°E – 155°E

AOI-120 East coast USA and Gulf of Mexico

17°N –33°N

101°W – 74°W

AOI-130 Yellow Sea and South China Sea

7°N – 40°N

105°E – 130°E

Yellow Sea and South China Sea coastal regions (Korean, Vietnam coastal zones)

During our discussions with users, we have discovered interest in all of the AOI listed in Table 3-1, as well as other areas. However, in order to give the project a focus, we propose to initially focus on the following areas:

The European coastlines, i.e. AOI-10, AOI-20, AOI-30, AOI-40, AOI-50, AOI-60 and AOI-70.

The North Indian Ocean, i.e. AOI-80 and AOI-90.

Within these core areas we will provide multiple data sets for a large number of SEVs, including non-satellite data such as flood maps and tide gauge data.



/ 102

eSurge-RB-REQ-010: eSurge Areas of Interest

SEVS shall be included for the following AOI:

a) AOI-10 (NW European Continental Shelf).

b) AOI-20 (NE Atlantic Ocean).

c) AOI-30 (Irish Sea).

d) AOI-40 (Adriatic Sea).

e) AOI-50 (Baltic Sea).

f) AOI-60 (Black Sea).

g) AOI-70 (Mediterranean Sea).

h) AOI-80 (West Indian Coastline).

i) AOI-90 (Bay of Bengal).

SEVs for other AOI may optionally be included.

Verification Method Inspection

We will aim to provide data for some SEVs within the non-core AOI. However we do not take this to be a requirement, as our primary requirement is to ensure data are provided reliably for the core areas. SEVs for these non-core AOIs will be identified based on user inputs, with data sets provided as far as is practical. We hope that, once we have demonstrated the usefulness of eSurge and SEARS, we will be able to establish collaborations to increase our coverage of other AOI.

In particular, for AOI-130 (Yellow and South China Seas), we fully intend to provide data for SEVS within this AOI, however this is dependent on being able to establish suitable partnerships.

3.3 Catalogue of Case Study Events

3.3.1 Definition of a Surge Event

A storm surge is a transient abnormally high sea level produced by atmospheric conditions. The surge is the difference between the expected sea level (due to predictable tidal factors) and the actual sea level resulting. There are different factors which could be used to define a surge event (SEV):

The Total Water Level Elevation (TWLE). A high TWLE determines whether flooding will occur, but may (in the case of exceptionally high tides) include only a small storm surge component. The TWLE at which significant flooding occurs will differ between locations depending on the landscape, but locally it is a fairly simple parameter to identify.

The storm surge amplitude, i.e. the difference between the TWLE and the expected water level as measured by the skew surge. These events are important as even if they did not themselves result in flooding they can be used to refine storm surge models to improve future flood forecasts. To define a SEV using the



/ 102


storm surge amplitude, it is necessary to define what the significant level is. This could for example be done by defining a return period, i.e. a surge that is only expected over to occur once over a given period.

Our preferred measure of sea level anomaly is skew surge (Figure 3-2), which is the difference between the predicted astronomical high tide and the nearest experienced high water. This removes all artefacts of phase-alteration and is the preferred surge diagnostic for operational forecasting systems. In many respects it is of greater practical and physical significance than the non-tidal residual. In practice, we expect to use a mixture of definitions in order to capture the needs of different groups of users.

Figure 3-2: Definition of Skew Surge

An additional type of “Surge Event” which needs to be included in the database is where a surge was predicted but did not in fact occur. Such false positive events are important for improving the forecast models.

3.3.2 SEV selection criteria

ESA have requested that a certain minimum number of SEVs be included in the data sets provided, as captured in the following requirement.

eSurge-RB-REQ-020: Number of SEVs

As a minimum, there shall be:

a) 50 SEVS in the Test Data Set.

b) 200 SEVS in the Full Product Data Set.


The selected SEVs shall primarily lie in the time frame 1991-present, to ensure availability of satellite data, though it may be desirable to include a few cases from earlier, if desired by users and if sufficient data are available.



/ 102

eSurge-RB-REQ-030: SEVs Time frame

The majority of SEVs chosen for inclusion shall lie in the time frame 1991-present.


Fundamentally our main criterion for a storm surge to be included is that the data should be useful to our users. Our intention is that the majority of cases shall be identified using users’ inputs. The criteria we will use for identifying SEVs to be included in the eSurge database are:

1. Have users requested data for this event?

In our user survey, we asked whether there were any particular events that users were interested in obtaining data for. All events for which users have expressed interest will be included providing that they fall within one of our core AOI and that suitable data are available.

2. Suitability for reanalysis experiments.

Within the eSurge project we intend to perform reanalysis experiments on a limited number of SEVs (including false positives). Any cases that we intend to study ourselves will obviously be prioritised.

3. Storm surges which resulted in flooding.

We will include at least some SEVs which resulted in significant flooding in each AOI. These may not be the most interesting from the users point of view, but are important for generating wider interest in the project.

4. Include False Positives.

We shall also identify, together with users, some cases where a storm surge was predicted, but either did not materialise or was substantially weaker than expected. These are important for improving surge models.

5. Storm surges recorded by tide gauge data

If our previous criteria do not produce the required number of SEVS, we will use tide gauge data to identify additional storm surges. The exact criteria used will be chosen in order to obtain the desired number of SEVs. See section 3.3.3 below.

An important subset of SEVs is the “false positives”, i.e. where a predicted surge did not materialise. Strictly speaking this should be “occasions where model predictions diverged significantly from observations”, as cases where the model predicted a lower surge than observed are also of interest, even if no flooding resulted. However we would expect such “false negative” cases to be captured by our other criteria, whereas we may need to specifically identify false positives.



/ 102


eSurge-RB-REQ-040: Number of False Positive Events

As a minimum, there shall be:

a) 3 false positive events in the Test Data Set.

b) 10 false positive events in the Full Product Data Set.


3.3.3 List of SEVs under consideration

Annex D lists the SEVs currently being considered for inclusion, given the criteria listed in section 3.3.2. At the moment, this list is incomplete as it contains fewer than the required 200 events (requirement eSurge-RB-REQ-020).

We will complete this list using the criteria laid out in section 3.3.2, in particular by asking users to identify SEVs which are of interest (including false positives). In particular:

1. For the Indian Ocean, SEVs will be selected from the draft JCOMM ETWS Storm Surge guide subject to review by users in the region.

2. False positives will be defined in consultation with the flood warning operational services of the UK, The Netherlands and Denmark.

There are various ways in which user feedback on SEVs can be sought: through working groups, through direct contacts, or by utilising the project website.

Should fewer than 200 events be identified this way, this list will be completed as follows:

1. Analyse tide gauge observational record from North Sea operational data collection (from UK, Denmark, The Netherlands). All real time tide gauge data are available from the IOC server at: http://www.sleac.org.

2. Rank order the top 50 skew surges at all gauge locations, and assign return period values if joint probability analyses are available.

3. Select the SEVs that exceed the 50 year return period at 3 non-adjacent locations.

4. Select the SEVs that exceed the 25 year return period at 3 non-adjacent locations.

5. Select the required number of SEVs from 3 and 4 above.

eSurge-RB-REQ-050: SEV identification

SEVS shall be primarily selected on the basis of the data being requested by users.

Should fewer than 200 events be identified, tide gauge observations in the North Sea area shall be used to complete the set.




/ 102

3.4 External Bathymetry Data for each AOI

One of the non-satellite data sets to be provided is bathymetry for each area of interest. Since the bathymetry is not expected to change significantly between surge events, this can be provided as a static data set per AOI.

See section 4.1.5 for details of the bathymetry data to be provided.



/ 102


4 ESURGE PRODUCTS PROVIDED

4.1 eSurge Products

4.1.1 Overview

Section 3 described the Surge Events (SEVs) that we will be studying, and the Areas of Interest over which we will look for each event. Each SEV must have several data products associated with it, which users can download for the SEVs that they are interested in.

In the context of eSurge, a data product is defined as being a set of data capturing one or more relevant physical parameters. The data may be raw or processed measurements, a blending of measurements by different instruments, or outputs of a numerical model. For a given SEV, data products will be made available within the AOI that the SEV falls into, and within a certain time range around the event itself.

Table 4-1 lists the data sets to be made available via SEARS. This is a minimum list which represents datasets covering the primary variables essential for storm surge forecasting and validation. The datasets clearly do not include all potentially useful products; we may be able to include other data sets should they be made available to the project, for example through collaboration with users or direct access to external data servers.

Note that where “All AOI” is stated under Areas of Interest, this should be interpreted as being “All AOI for which data are available”, as not all data sets are available for all AOI.

The focus of eSurge is on providing satellite EO data products via the SEARS system. The data products to be provided are determined by the needs of users, though there are also practical issues that need to be taken into account; for example not all desired data sets may be freely available. Most of the data products to be provided already exist, but will be made easier to access, while others will be created in the frame of this project.

Additional non-satellite data products (such as in-situ data and model outputs) will be included in SEARS, both for the convenience of users (making relevant data available in one place) and to assist with the validation and assimilation of satellite derived products.

The following sections describe in detail the requirements for data products to be included in the SEARS system.



/ 102

Table 4-1: Baseline Minimum list of Data Sets to be Included in SEARS. Additional data may be included through user collaboration or access to external data services.

Product ID Parameters Feature Area(s) of interest

BA1

Bathymetry GEBCO_08 global 30 arcsec (Regional

bathymetry at higher resolution possible on a case by case basis)

All AOI

DM1 Digital Elevation Model ACES global 30 arcsec DEM (regional DEM at higher resolution where available)

All AOI

WI1 Winds Scatterometer EU seas, North Indian

WI2 Winds (reanalysis) HIRHAM downscaled from ERA40, 0.11deg., hourly resolution

North Sea (incl. shelf)

SL1 Coastal altimetry improved quality All AOI

SL2 Tide gauge data 15/10minutes resolution NW EU shelf

WA1a Waves Altimeter (open-ocean) All AOI

WA1b Waves Altimeter (improved Coastal Altimetry) All AOI

WA2 Wave Spectra SAR Wave Mode Spectra All AOI

WA3 Waves Operational DMI WAM model North Sea and Baltic Sea

WA4 Waves Wave model (Scatterometry) All AOI

ST1 SST (multi-satellite) L4, daily, 5km resolution All AOI

IR1 Infrared imagery for storm tracking from Meteosat/MVIRI and MSG/SEVIRI

30 min intervals, 5-km All AOI

SD1 Sediment Concentration MERIS fine resolution suspended sediment concentration

All AOI

OC1 Ocean Colour MERIS L2 fine resolution imagery All AOI

HP1 Tropical Cyclone Heat Potential (TCHP)

From AOML/NOAA All AOI

BM1 Baseline model outputs 1 Standard simulation model results for North/Baltic sea

North Sea & Baltic Sea

BM2 Baseline model outputs 2 Standard simulation model results for North Indian Ocean

North Indian Ocean

BM3 Baseline model outputs 3 Standard simulation model results for UK waters

UK waters

SR1 Surge reanalysis model outputs Use WI2 North Sea & Baltic Sea

DA1 Reanalysis (with Data assimilation HC1+ assimilating SL1, added value from coastal altimetry and L4 (EnOI or 3DVAR)

North Sea, Baltic Sea

DA2 Reanalysis (with Data assimilation HC2+assimilating SL1 (EnOI or 3DVAR) North Indian Ocean

NRT1 NRT winds Scatterometer All AOI

NRT2 Blended water level L4 product (TG+altimetry), using NOC coastal altimetry as input

North Sea and Baltic Sea

NRT3 NRT wave Altimetry (open ocean) All AOI

NRT4 NRT wave spectra SAR wave mode spectra All AOI

NRT5 NRT SST L4 L4 Daily, 3-5 km resolution All AOI

NRT6 NRT Surge forecast Operational DMI HRB model

Yellow Sea, North Indian Ocean

NRT7 NRT surge forecast Operational DMI HRB model North Sea & Baltic Sea

NRT9 NRT Coastal Altimetry FDMAR coastal altimetry data from Envisat and Cryosat

Reprocessed coastal altimetry data from NRT Envisat and Cryosat waveforms

All AOI

NRT10 NRT Infrared imagery for storm tracking

As for IR1 All AOI

FM1 Flood (Inundation) Maps From available OC and SAR All AOI



/ 102


4.1.2 EO Products

4.1.2.1 Coastal Altimetry

Altimetry gives a direct measurement of the sea level (TWLE), which is also an output of the model. It is therefore highly suitable both for validation and assimilation. Altimeters measure the average sea level over a 2 to 15 km radius, and current operational altimetry products cannot measure within this distance of the coast, despite this being the most interesting region for storm surge models. Coastal altimetry research projects are addressing this problem using specialised algorithms.

Coastal altimetry is a data set attracting a great deal of user interest, and is therefore a key part of the eSurge project. The coastal altimetry product provided by eSurge will be an extension of the work previously done under COASTALT.

Other coastal altimetry products will be included if available.

Coastal altimetry techniques are also used in generating the wave products described in section 4.1.2.4; these are covered in that section and are not included in this requirement.

The coastal altimetry products are fully described in annex C.1.

See section 7.3 for coastal altimetry products available in NRT as part of the “eSurge Live” service.

eSurge-RB-REQ-060: Coastal Altimetry Data Products

The eSurge project shall make available the following coastal altimetry products, tuned to storm surge applications:

a) SL1: TWLE from Coastal Altimetry (altimeter heights retracked and reprocessed with specific coastal altimetry algorithms).


4.1.2.2 Ocean Surface Vector Winds

Scatterometry measures the surface wind speed and direction over the ocean, which has a major effect on storm surges and is therefore a very useful input to the models. There is high user interest in making scatterometer data available.

Strictly speaking, we are talking about Ocean Surface Vector Winds (OSVW), i.e. wind speed plus direction at the sea surface. However for brevity the term “winds” is generally preferred.

For eSurge, we will make available both winds information directly from scatterometry, and reanalysed wind data using DMI’s HIRLAM model.

We will look into making other scatterometry products available; for example there is strong interest in having OceanSat data available at 25km resolution. This has not been included in the requirements, but we will aim to include it.



/ 102

eSurge-RB-REQ-070 Scatterometry Wind Data Products

The eSurge project shall make available the following scatterometry vector wind products, tuned to storm surge applications:

a) WI1: Winds.

b) WI2: Winds (reanalysis).


Wave products using scatterometry are covered in section 4.1.2.4.

The scatterometry wind (OSVW) products are described in annex C.2.

See section 7.3 for scatterometry products available in NRT as part of the “eSurge Live” service.

4.1.2.3 Satellite SST

Sea surface temperature can be provided via the MyOcean TAC.

SST products are described in annex C.3.

See section 7.3 for SST products available in NRT as part of the “eSurge Live” service.

eSurge-RB-REQ-080: SST Data Products

The eSurge project shall make available the following SST products, tuned to storm surge applications:

a) ST1: SST (multi-satellite).


4.1.2.4 Wave Products

Wave products are largely obtained by using the outputs of the GlobWave project, however other sources of wave data are additionally used. There is high user interest in wave and wave spectra products for storm surge applications.

Wave products are described in annex C.4.

See section 7.3 for wave products available in NRT as part of the “eSurge Live” service.



/ 102


eSurge-RB-REQ-090: Wave Data Products

The eSurge project shall make available the following wave data products, tuned to storm surge applications:

a) WA1a: Waves (open-ocean altimetry).

b) WA1b: Waves (coastal altimetry).

c) WA2: Wave spectra.

d) WA3: Waves (operational model).

e) WA4: Waves (wave model with scatterometry input).


4.1.2.5 Ocean Colour

Ocean colour products are described in annex C.5. Note that ocean colour products are only relevant for a limited subset of storm surge cases.

eSurge-RB-REQ-100: Ocean Colour Data Products

The eSurge project shall, where relevant, make available the following ocean colour products, tuned to storm surge applications:

a) OC1: Ocean Colour (water leaving reflectance).


4.1.2.6 Sediment Concentration

Sediment concentration products are described in annex C.6.

eSurge-RB-REQ-110: Sediment Concentration Data Products

The eSurge project shall make available the following sediment concentration data products, tuned to storm surge applications:

a) SD1: Sediment concentration.


4.1.2.7 Other Satellite Products

There are two additional satellite products that do not fall into the categories above. One is Tropical Cyclone Heat Potential (TCHP), the other is Infrared data from a geostationary satellite, useful for tracking storms in the build up to a surge event. Infrared data from polar orbiting platforms (e.g., from AVHRR, AATSR, MODIS) are not excluded a priori, but they will be only considered in those cases where the geostationary data do not provide sufficient coverage and/or resolution.

Additional satellite products are described in annex C.7.



/ 102

eSurge-RB-REQ-120: Other Satellite Data Products

The eSurge project shall make available the following additional satellite data products, tuned to storm surge applications:

a) HP1: Tropical Cyclone Heat Potential (TCHP).

b) IR1: Infrared data from geostationary satellites for storm tracking purposes.


4.1.3 In-Situ Products

An essential element of the eSurge system is the inclusion of in-situ data, where available, for assimilation and for validation of surge models. In-situ tide gauge measurements will be used in validating storm surge forecasts, hindcasts and assimilation results, and be used to generate blended altimetry-gauge sea level products and for data assimilation. The in-situ gauge data are required in all relevant AOIs.

eSurge-RB-REQ-130: In-Situ Data Products

The eSurge project shall make available the following in-situ data products, tuned to storm surge applications:

a) SL2: Tide gauge data.


In-situ data products are described in annex C.8.

4.1.4 Model Products

SEARS will include several products which are the outputs of modelling, however these are listed separately as follows:

Several of the products listed in section 4.1.2, to be provided for historical SEVS, are the result of blending data using models. These are listed in the appropriate section and the details of the models given in Annex C.

As part of the reanalysis and data assimilation experiments described in section 6, we will make available model outputs from these experiments via SEARS. These are listed in section 7.3 and described in annex C.9. Additional model runs will be provided using the same models but outside the scope of the experiments; these are listed with the experiments for convenience.

In addition, some model output products will be available in NRT as part of the “eSurge Live” service, as described in section 7.3.



/ 102


4.1.5 Additional Data

In addition to those data products specified above, some additional data are needed for the convenience of users.

Some data (such as Bathymetry, Digital Elevation Models) do not change significantly between events, and so need to be provided only once for a given area.

eSurge-RB-REQ-140: Additional Data Products For AOIs

For each area of interest, the eSurge project shall as a minimum make available the following additional data products, tuned to storm surge applications:

a) BA1: Bathymetry.

b) DM1: Digital Elevation Models.


Other data sets are specific to a given SEV. However data for these products are not available for all surge events and so will be given for only a selected number of SEVs.

eSurge-RB-REQ-150: Additional Data Products for SEVs

For a selected number of SEVs, the eSurge project shall as a minimum make available the following additional data products, tuned to storm surge applications:

a) FM1: Flood (Inundation) maps.


These additional products are described in annex C.11.

It should be emphasises that the products listed in this section are the minimum that will be made available. Other products may be made available should they be shown to be relevant and readily available for incorporation.

4.1.6 Socioeconomic Data

The web interface will allow authorised users (including the project team) to associate supplementary data, such as images and reports related to a SEV, within SEARS. To be accessible from the web site the data must be certified to be freely available by the uploader. Once uploaded, all users shall be able to access this data.

eSurge-RB-REQ-160: Uploading Supplementary data

The web interface shall allow authorised users to upload supplementary data for association with a SEV, providing that they certify it to be freely available. Once uploaded all such data shall be available to all users.

Verification Method Testing



/ 102

eSurge-RB-REQ-170: Access to Supplementary data

Once uploaded, all supplementary data shall be available to all users.


4.1.7 Validation Methodology

Data products developed in this project will be validated as part of their development within the eSurge project.

The procedure for validating data products imported from elsewhere will depend upon the available information. We will attempt to use only fully validated products, however there may be cases where it is desirable to include products for which the validation evidence is less than ideal. It will not be possible to re-validate any products created outside of this project.

The product handbooks (see section 4.2) will include, or refer to, all available information relating to validation for that data product

eSurge-RB-REQ-180: Validation of new data products

All products created as part of this project shall be validated, and the validation approach detailed in the product handbooks.

Verification Method Inspection / Analysis

eSurge-RB-REQ-190: Validation of data products made available via SEARS

All available information on the validation approach shall be provided in the data product handbooks for all products which are made available, but which are not created as part of this project.


In addition, products shall be checked for ease of use and suitability. “Ease of use” is a subjective term, but in this context it means that, given the information available in the data product handbook, a reasonably experienced user should be able to use the product. Internal checking shall occur before the product is released to users. Once released, users will be able to give feedback on each product.

eSurge-RB-REQ-200: Data Product Checking

All products shall be checked for ease of use and suitability:

a) internally before release.

b) by means of user feedback after release.




/ 102


4.1.8 Accuracy of eSurge Products

The accuracy of each eSurge product is discussed in the data product description table for that product, as given in Annex C.

4.2 Data Product Handbooks

Accompanying each dataset product available in SEARS will be a product handbook. These shall be available as individual PDF documents. Nominally a handbook will be associated with each separate product, though to avoid duplication it may in some cases make sense to combine handbooks for related products.

The handbooks will aid users of the dataset to fully understand the nature of the product package they will receive, along with the origins and technical specifications of the dataset within the product package. Handbook content will be aimed at novice users, but will also contain sufficient detail to be useful to the advanced user.

Handbooks will be reviewed internally before being published on the eSurge web portal, where they will be made available to accompany product download from the SEARS system. Feedback from users will be incorporated into subsequent versions for the duration of the eSurge project, with the most updated current version being made available online for users to browse, or download to accompany a product.

The eSurge project will maintain tailored versions of the product handbooks for each eSurge product on the SEARS database.

Feedback on the product handbooks, collected during the User Consultation Meetings (UCM) will be used to guide revised versions, which will subsequently be made available on the web portal. User feedback via the online web-portal will also be incorporated.

eSurge-RB-REQ-210: Data Product Handbooks

The eSurge project shall develop tailored versions of EO product handbooks for each eSurge product.




/ 102

eSurge-RB-REQ-220: TOC for Product Handbooks

Each product handbook shall be tailored for the specific product in question. The TOC for each product handbook shall nominally include:

a) Glossary of terms, a table of acronyms.

b) Introduction and summary of product use in storm surge applications.

c) Relevant background material describing the product with links to ATBD and other reference material.

d) Description of the algorithms applied to generate the product.

e) Range of product accuracy, precision and links to validation information and validation evidence.

f) User guidance on the application of products.

g) A description of strengths and weakness of each data product for storm surge applications.

h) Relevant scientific and engineering journal paper and report references.

i) Detailed description of product format.

j) Estimates of file sizes.

k) Description of where and how to access/order products.

l) Contact points for each product.

m) Full visualisation (e.g., images, line plots etc.) of an example product.

n) Example read software and links to actual software code available on the eSurge web portal.

o) A product FAQ tailored to storm surge applications.

p) A feedback form and contact details to submit feedback allowing users to report problems and request further information.

q) Any other material required by beginner users to successfully understand, read and apply the product.

r) Appendices detailing any web sites, software tools, read software etc.

s) Any relevant external links.


eSurge-RB-REQ-230: Data Product Handbook Maintenance

TDS eSurge product handbooks shall be maintained and updated based on user feedback and product evolution for the duration of the eSurge project, with tailored versions of EO product handbooks to accompany any updated release of products.


eSurge-RB-REQ-240: Data Product Handbook Availability

The most updated versions of the handbooks shall be available online for users to browse, accompanying downloaded products.




/ 102


5 SURGE EVENT ANALYSIS AND REPOSITORY SERVICE (SEARS)

5.1 Overview

The SEARS system consists of:

A core database holding metadata describing the AOIs and SEVs, product handbooks, associated socioeconomic data and links to the data products listed in section 4.

The data themselves, in both local and, potentially, remote locations.

Interfaces for ingesting data and metadata.

Services to distribute data.

Services to provide interfaces to web portal and associated visualisation

SEARS will access data either through a local store or remotely; some non-changing, low volume, data such as bathymetry data, may be held within the database, data processed locally as part of the eSurge project will be held locally, while for other data it may make more sense to hold the data remotely. An assessment will be done on a case by case basis for each data set.

The SEARS database will act as the primary catalogue tool for eSurge, linking together information on the AOIs, SEVs and related data products. The interfaces to the database will allow users to identify and access the data products and all additional information for any specific SEV. It will also hold all the metadata regarding the various data products, including that required to generate data product handbooks.

A web interface will allow authorised users to create new SEVs, provide visualisation of the match-up between a SEV and eSurge products, and provide services to access eSurge products. The web interface is discussed further in section 8.5.

5.2 Data Types and Formats

5.2.1 Data Format Definition

The preferred distribution format for eSurge data products through SEARS will be NetCDF, as this is a format that is now suitably mature to have a number of “off the shelf” applications for reading and displaying the data, and is suitable for the full range of data to be included: EO, in situ, gridded, swath or point measurements. The data product handbooks will provide links to freely available software to access and visualise the data sets. Alternative data formats can be specified by the user as output from the OpenDAP server, but these will not be explicitly supported by eSurge.

Supplementary data associated with SEVs may be provided in an appropriate, preferably open source, format, but the definition and restriction of those formats is outside the remit of this document.

In addition, data and information will be available via the web portal using the Web GIS tools. These data will be in Web GIS compliant formats.



/ 102

5.2.2 Output Data

All of the data products generated by the eSurge project shall be made available in NetCDF format, consistent with the Climate Forecast Convention, unless there are specific reasons why this is not possible for this project. (For example if the data are supplied subject to constraints.)

eSurge-RB-REQ-250: NetCDF use

The eSurge project shall provide products in NetCDF format, consistent with the Climate Forecast Convention, unless there are specific constraints preventing this.


A height reference system common to all areas shall also be applied throughout the project. This will not be chosen arbitrarily, but will be done in discussions with users and with other projects, in order to be consistent with other activities in the field. The Height Unification for GOCE (HUG) project has been provisionally identified as a possible source of such a reference.

eSurge-RB-REQ-260: Common Height Reference

The eSurge project shall use a common orthometric height reference system for all products and services.

Verification Method Inspection / Testing

5.2.3 Source Data

The SEARS system will provide access to data products from a wide range of sources. Some of these data will be processed specifically for the eSurge project, whilst other data, already suitable for Storm Surge investigations, may simply be selected and re-distributed via SEARS. Data may be stored either locally or remotely as appropriate.

eSurge-RB-REQ-270: Links to External Data Sources

There shall be a mechanism for automatically checking for broken links to data which is held externally but which is referenced within SEARS, and to notify the administrator if any such are detected.


5.2.4 Format and File Naming

File naming for externally provided products will follow the convention used for that product, to allow users to readily match the eSurge products to information on the source data.



/ 102


eSurge-RB-REQ-280: Product file naming convention

Products generated within eSurge shall use a file naming convention that allows a simple recognition of the data type and unique identification of the location and time of the product.


5.2.5 Metadata content

The metadata for datasets will form an integral part of the SEARS system, and be incorporated into the SEARS database. In addition, the use of NetCDF as the primary data format, and compliance with the Climate Forecast (CF) conventions, will ensure that the essential metadata for access and interpretation of the data is included within the data files. Essential product metadata includes units, in udunits (www.unidata.ucar.edu/software/udunits/) recognised formats.

Another key source of metadata will be the product data handbooks, which will be stored within the SEARS database.

5.3 Metadata Requirements

NetCDF has been chosen as the distribution medium for eSurge output data sets as it may carry metadata encoded within each file.

eSurge-RB-REQ-290: Product metadata

The data product handbook will include metadata sufficient to:

a) Allow users to determine the inputs and processes used to create that Data Product.

b) Describe the access rights available to eSurge to those accessing or discovering data product through the eSurge portal.


5.3.1 Metadata and Cataloguing Requirements

The core SEARS database will provide the central cataloguing system for all AOIs and SEVs.

eSurge-RB-REQ-265: Cataloguing Requirements

The core SEARS database will provide the central cataloguing system for all AOIs and SEVs. The cataloguing system used shall

a) Define each SEV with a start and finish date.

b) Relate each SEV to an AOI.




/ 102

Each SEV will be defined as related to a single AOI with a start date and a finish date. The status of the SEV will be updateable manually by authorised users and will determine the data acquisition activities undertaken for that SEV. Metadata sufficient to complete the data product handbooks must be entered and maintained by authorised users (including the eSurge project team); see section 4.2.

5.4 Product Delivery

5.4.1 Overview of Delivery Mechanisms

The questionnaire results (annex A.2.6) showed that vast majority of users prefer to download data via the internet. A small number of users preferred a streaming / ‘push’ data distribution system, such as the WMO GTS. The implementation of a ‘time critical’ push service, such as the GTS, is not relevant to the data streams envisioned within eSurge. In addition, the “Timely Delivery Service” route of the emerging WMO Information System (WIS) is not feasible within this project. Instead, we will focus on pull (data request systems), as being the most appropriate for the eSurge requirements.

For internet download, the most popular requested protocol is FTP. For less scientific users, a user-friendly portal is especially required as a front-end to data access. Also, some users do not wish to search and download data files on an individual basis. In this case, a batch download mechanism was requested.

The primary method of data delivery will be via an OpenDAP server. OpenDAP provides a wealth of in-built user functionality, including sub setting, selection of specific variables or parameters, delivery in alternative formats, aggregation, access to Web Map Services for integration into Web-GIS functionality and simple HTTP delivery action. Hence the OpenDAP service will allow access to the data via a web portal, and also through command-line scripting for automated, or semi-automated processing.

It is also possible to configure OpenDAP to act as a central server for distributed OpenDAP services, allowing a single portal to access remote data. This allows new datasets to be added to the primary service very rapidly – without the overhead of developing data download and quality control protocols for each new dataset. As the number of OpenDAP services increases, it is anticipated that this type of portal activity will increase.

Although FTP was highlighted by users as the preferred delivery mechanism, this is becoming a deprecated delivery source, due to the difficulties in securing and monitoring FTP access as well as the inherent inflexibility of FTP as a delivery mechanism. In many instances, we understand the preference for FTP is driven by a requirement for scriptable (and hence automated or semi-automated) access to data. Hence access to command-line http interface via OpenDAP is a priority, providing benefits in terms of automated data aggregation, sub-setting and data format conversion, not possible via an FTP interface.

However despite this, we consider that the demand for FTP is sufficiently high that it is essential to provide it. A limited FTP service for all data held locally within SEARS will therefore be provided for users who decide not to take advantage of the additional functionality of the alternative delivery mechanisms.



/ 102


eSurge-RB-REQ-300: Primary access mechanisms

The primary method of data delivery shall be via an OpenDAP server.


eSurge-RB-REQ-310: Additional access mechanisms

A limited FTP service for all data held locally within SEARS shall be provided for users who prefer this method.


eSurge-RB-REQ-315: Limiting Data Downloads

The data download mechanisms shall allow users to limit the data they choose to download by selecting a subset of the available temporal and spatial ranges.


5.4.2 Summary of Delayed-mode Product Delivery

The delayed mode data will be provided, primarily, via an OpenDAP service, configured to allow access via a number of routes:

OpenDAP access, allowing both web based access and direct access from (eg) matlab, including sub setting, parameter selection, aggregation etc.

HTTPServer, to allow file download of the underlying NetCDF files (very similar to FTP access).

Integrated Web Coverage Service and / or Web Map Service to allow interfaces to Web GIS and other CS/WMS enables web tools.

The selection of the specific OpenDAP implementation, and configuration of the OpenDAP service and caching system shall ensure users have timely responses via web tools.

In addition, all local data will be accessible via a limited FTP server.

eSurge-RB-REQ-320: Delayed mode product delivery

Delayed mode data shall be provided via an OpenDAP service configured to allow access via:

a) OpenDAP access (both web based and direct).

b) HTTP server.

c) Web coverage service and/or web map service.

d) Limited FTP service.




/ 102

5.4.3 Summary of NRT Product Delivery

The delivery mechanisms for the NRT products will use the same services as the delayed mode data. Where remote data are available via an OpenDAP service, it is possible to interrogate the remote service at the time of the data request to ensure that the information held within the SEARS database is up to date. This ensures that the information and data products are available to users with the minimum possible delay.

5.5 Data Access Tools

5.5.1 Read Software

A basic NetCDF reading routine will be made available for matlab and octave (a readily available open-source alternative to matlab), and users will be directed to the (supported) NetCDF toolkits from UNICAR for reading NetCDF data, as well as existing software able to read CF compliant NetCDF files.

eSurge-RB-REQ-330: NetCDF reading routines

Basic NetCDF reading scripts shall be provided for:

a) Matlab.

b) Octave.


5.5.2 Format Conversion Tools

The primary delivery format will be NetCDF for all data files. As part of the product handbooks, users will be notified of appropriate software tools for reading and converting this format. The use of a standard format should preclude the necessity for the project to generate and distribute specific format conversion tools. Instead, the users will be directed to the wealth of freely available software tools for reading and manipulating NetCDF format data.

We will investigate the possibility of providing a user-contributed library of software tools or routines. However, this service might be more securely provided using existing software repositories.

5.5.3 Data Analysis Tools

Data analysis tool will be available via the web portal and are discussed in section 8.6.

5.5.4 SEV Visualisation and Manipulation Tools

An interactive geographical interface will be provided for SEV visualisation; see section 8.6 for this and other online tools.



/ 102


5.6 Interface Requirements

The SEARS requires interfaces for both metadata and data.

The primary interface for metadata will be via the eSurge web portal. The database will require interfaces to allow database searching and return output suitable for web display. The data will be accessed via an OpenDAP service, to allow both aggregation of datasets and data subsetting and delivery of data via a Web Map Service for display via Web GIS.

The SEARS portal will provide a user-friendly front-end capable of delivering data from distributed servers to the users machine. The web portal will also allow users to assemble command line scripts than be used for automated, or semi-automated, data access. The data will be delivered direct to the users target machine from the distributed servers.


There is a requirement for the project to provide delivery options for storm surge users with low bandwidth connections. Using the command-line interface to the OpenDAP service will allow users to specify only the data they need, limiting the download necessary, and using only limited overhead in terms of web graphic display. If this is still not sufficient, we will investigate methods for data request submission and potential offline distribution.

eSurge-RB-REQ-340: Access for Users with Low Download Rates

The eSurge project shall develop and provide appropriate and validated delivery options for EO products in support of storm surge users with low bandwidth data connections.




/ 102

6 RE-ANALYSIS AND DATA ASSIMILATION EXPERIMENTS

6.1 Aims and Objectives

During phase 2, reanalysis and data assimilation case studies will be carried out for a limited number of storm surge events and AOI. This supports the project objectives by demonstrating the value of using EO winds, EO SST and altimetry data on storm surge forecast and hindcast, and hence proving the value of eSurge products. The impacts of using EO data in storm surge modelling will be quantitatively assessed. This therefore meets the SOW requirements:

- To encourage and assist the storm surge community to fully exploit the potential of satellite data for storm surge applications and

- To increase user uptake of coastal altimetry and other satellite data products by demonstrating their value in storm surge applications

The experiments shall cover the North Sea / Baltic Sea region and the North Indian Ocean. Within the North Indian Ocean, the experiments depend upon the availability of tide gauge data to ensure that the technique of blending using coastal altimetry can be applied to this area. The data should be available through the Permanent Service for Mean Sea Level (PSMSL), and the project team is already active in ensuring that the data can be available for phase 2.

eSurge-RB-REQ-350: Agreement of Impact Assessment Experiments

All impact experiments shall be agreed with the Agency prior to implementation.

Verification Method Inspection.

6.2 Models and Inputs Used

6.2.1 Overview

Both the reanalysis and data assimilation experiments will be based on models for the North Sea and North Indian Ocean. Both DMI and NOC will perform experiments based on their knowledge of these areas.

The following subsections describe the inputs to the experiment campaigns in more detail. In general the same models are used for each experiment, with differences which are described later on. Differences between models and data used for each experiment will be tracked, with versions recorded.

6.2.2 North Sea Model Used

Two models are used for the North Sea. For the most part, DMI’s HRB model will be used, however to improve confidence in this model we will perform a limited number of experiments with the UK Met Office model, supplied by NOC.



/ 102


The 3D HIROMB-BOOS (HRB) model, provided by DMI, will be used for reanalysis and data assimilation experiments. The HRB model provides sea level and storm surge predictions covering the entire North Sea and Baltic Sea. It uses a storm surge height, calculated over the North Atlantic by a 2D model, as a boundary condition on top of tidal variations of sea level. The model requires hourly data on wind, pressure, air temperature, humidity, cloud and fresh water river discharges.

The UK operational surge modelling system (CS3X), provided by NOC, is described in detail in Flather (1994)2. The current tide-surge model covers the entire northwest European continental shelf at 12 km horizontal resolution. It is forced by the surface pressure and 10m wind fields from the Met Office NAE atmospheric model, at a similar spatial resolution. Tidal input at the model open boundaries consists of the largest 26 constituents.

6.2.3 Indian Ocean Model Used

NOC will run the storm surge model from the Indian Ocean operational warning system, which covers the whole of the Indian Ocean. As well as the regional system, there are local high-resolution models have been developed for Andhra, Orissa, Tamil Nadu, Gujarat coasts of India and for Bangladesh, Myanmar, Pakistan and Sri Lanka. The model was developed by the Indian Institute of Technology (IIT) and it is run operationally in the region with support from the Tropical Cyclone Programme (TCP) of the World Meteorological Organization (WMO). NOC has support and permission to use the model through the IOC/UNESCO project on “Enhancing regional capabilities for Coastal Hazards Forecasting and Data Portal Systems”.

The model is two-dimensional and depth-averaged, and fully non-linear. A semi explicit finite difference scheme is used for the numerical solutions. Fine resolution grids are 3.7km x 3.7km. Surface wind fields are derived from a dynamic storm model, and the surge model uses as input the radius of maximum wind and the pressure drop. The other main component of the storm model is a trajectory model.

6.2.4 Blended Water Level Product

The data used for the data assimilation experiments (at DMI) will include the demonstration product combining both tide gauge and coastal altimetry observations in a statistical sea level field3. The method combines the tide gauge observations through a statistical model derived using coastal altimetry observations. In addition, data from an algorithm using standard altimetry observations will be available for selected North Sea storm surges. The coastal altimetry derived blended product will be used to assimilate into the models to demonstrate the impact of using satellite observations.

Independent tide-gauge data will be used for the assessment and validation of the blended products. The improved performance of the blended product using coastal

2 Flather, R.A., 1994. “A storm surge prediction model for the northern Bay of Bengal with

application to the cyclone disaster in April 1991.” Journal of Physical Oceanography, 24, 172-

190.

3 Madsen, K. S., Høyer, J. L. and Tscherning, C. C.: Near-coastal satellite altimetry: Sea surface

height variability in the North Sea–Baltic Sea area. Geophysical Research Letters, 34, L14601,

doi:10.1029/2007GL029965, 2007.



/ 102

altimetry observations will demonstrate the importance of the coastal altimetry products.

For the assimilation of the blended altimetry-gauge sea level product the data from tide-gauge will be used. Independent tide-gauge data will be used for the assessment and validation.

6.3 Reanalysis Experiments

6.3.1 Experiments in the North and Baltic Sea

Reanalysis experiments are an important part of phase 2, as they allow us to demonstrate the usefulness of satellite data for eSurge. Reanalysi experiments will be performed for the North Sea area only.

DMI will perform reanalysis experiments in the North Sea using two different sets of wind forcings which differ in the amount of satellite data available. We plan to use the operational HIRLAM forcing as the reference, then to run the model again using a downscaled HIRHAM reanalysis run from the ERA-Interrim runs. The wind reanalysis run will include more satellite observations (Ascat, AIRS, IASI, SSMI/S) than the operational run, so that the difference between these two runs will demonstrate the impact of using satellite data in the forcing fields. (Though it is necessary to account for other parameters, such as spatial resolution, having an impact on the results.)

An alternative approach could be to compare the model runs using the 12 hour hindcast/analysis from each operational run (with some data assimilated) against using the 0-12 hour forecast fields from each operational run (without any data assimilated). In this way we use the same wind model, however there is still an impact of the assimilated data in the forecast. In general the first method is preferred.

eSurge-RB-REQ-360: Reanalysis Experiments

The eSurge project shall include reanalysis experiments (minimum of 5 cases) in the North / Baltic Sea area using eSurge data as baseline component of the eSurge Phase-2 project impact assessment.


We have provisionally identified the following storm events as being suitable for the reanalysis experiments:

1. 28.01.2002 - Westerly storm.

2. 21.02.2002 - Easterly storm.

3. 06.12.2003 - Northerly storm.

4. 20.03.2004 - Westerly storm.

5. 08.01.2005 - Westerly hurricane.

6. 01.11.2006 - Northerly storm.

The list of reanalysis experiments was selected as they include extreme events. However, the list can be modified based on users’ feedback and data availability.



/ 102


6.3.2 Model Outputs

All results from the reanalysis experiments shall be included in the SEARS database for users to freely access.

eSurge-RB-REQ-370: Model Output Data Products

The eSurge project shall make available the following model output data products, tuned to storm surge applications:

a) BM1: Baseline Model Outputs 1.

b) BM2: Baseline Model Outputs 2.

c) BM3: Baseline Model Outputs 3.

d) SR1: Surge Reanalysis Model Outputs 1


6.4 Data Assimilation Experiments

6.4.1 Experiments in the North and Baltic Sea

To demonstrate the usage of sea level data in improving the storm surge forecasts, An EnOI (or 3DVAR) method will be used to assimilate the sea level data during the period when some storm surge events happen.

Unlike the reanalysis experiments, we keep the wind forcing the same but run the model with and without assimilation of the blended water level. This is more straightforward since we use same model and wind forcing for the two experiments, allowing us to directly assess the impact of assimilating the sea level product.

We will select 3-5 cases for data assimilation experiments from the list of storm surges in the regions covered by the model.

eSurge-RB-REQ-380: Assimilation Experiments in the North Sea

The eSurge project shall include data assimilation experiments (minimum of 3 cases) in the North and Baltic Sea area using eSurge data as baseline component of the eSurge Phase-2 project impact assessment.


One key issue for data assimilation in the coastal zone is how to spread observational information given the complex topography and bathymetry. The assimilation experiments will be conducted for 3-5 storm surge events. Its effect on the 'forecasting' will be investigated and assessed. The storm surge events for the data assimilation experiments will be selected from the list of reanalysis experiments to make the assessment consistent.

In addition, a version of the blended algorithm using standard altimetry observations is available and this will be used for e.g. the North Sea storm surge on November 2006



/ 102

(suggested surge number 6 in section 6.3.1). For this event, both versions of the blended product will be assimilated to demonstrate the improvements using coastal altimetry observations.

6.4.2 Experiments in the North Indian Ocean

We will develop a suitable method (based on either EnOI or 3DVAR) to perform data assimilation within the Indian Ocean model, and then apply this to a number of tropical cyclone surges in the North Indian Ocean. As with the North Sea experiments (6.4.1) we will keep the wind forcing the same but run the model with and without assimilation of the blended water level in order to demonstrate whether there is an improvement in the model forecast/hindcast. For these experiments we will also derive a blended altimetry-gauge sea level product for the region. An outcome from this initiative might be a recommendation for a denser network of tide gauges in the region.

eSurge-RB-REQ-390: Assimilation Experiments in the North Indian Ocean

The eSurge project shall include data assimilation experiments (minimum of 3 cases) in the North Indian Ocean area using eSurge data as baseline component of the eSurge Phase-2 project impact assessment.


We have provisionally identified the following tropical cyclone events as being possible for the data assimilation experiments (subject to data availability):

1. 11-16 November 2007 – cyclone Sidr

2. 27 April – 3 May 2008 – cyclone Nargis

3. 23-26 May 2009 – cyclone Aila

4. 14-17 April 2009 – cyclone Bijli

5. 20-23 October 2009 – cyclone Giri

The list of experiments can be modified based on users’ feedback and the availability of altimetry data during the events.

6.4.3 Output Data from the Experiments

All results from the data assimilation experiments shall be included in the SEARS database for users to freely access.

The model output data products are described in annex C.9.

eSurge-RB-REQ-400: Model Output Data Products

The eSurge project shall make available the following model output data products, tuned to storm surge applications:

a) DA1: Reanalysis with data assimilation - 1.

b) DA2: Reanalysis with data assimilation - 2.




/ 102


6.5 Assesment of Reanalysis and Data Assimilation Experiments

The DMI national standard assessment procedure will be applied to the water level products for the North Sea and Baltic Sea. DMI has a standard validation tool for storm surge forecast, which has been developed in agreement with users and through national user meetings. Annual validation reports of the operational storm surge models have been made since 1997. The national assessment procedures consider important indexes, such as peak error (absolute and percentage), RMS errors and other error statistics derived from model versus tide gauge comparisons.

Assessment of the values of satellite data assimilation will include a feedback and evaluation of experiments results from DMI’s users working with storm surge forecast system on operational base at DMI.

Additional assessment indexes will be discussed at eSurge user meetings and will be included in the standard assessment reporting.

6.6 Communication of Key Operational Benefits

Once the experiments described in this section have been performed, for them to have real value their benefits must be communicated to the wider storm surge community. There are several means by which this could be achieved.

We will utilise our membership of existing projects and groups such as the IOC/WMO Indian Ocean project, the Coastal Inundation and Flooding Demonstration Project and the JCOMM Expert Team on Wind Waves and Storm Surges.

In addition, we will investigate creating an expert assimilation subgroup, within the eSurge user group, with whom we will work both to refine the experiments to be performed and to assess how the results should be communicated.

Our novel work on introducing data assimilation to the North Indian Ocean may well result in beneficial recommendations for the tide gauge network of the region, which we could carry forward through organisations such as JCOMM or IOC.

eSurge-RB-REQ-410: Communication of Operational Benefits

The eSurge project shall assess and evaluate the best means to communicated key operational benefits to the wider user community, by means of:

a) Utilising existing projects and groups.

b) Creating an expert user subgroup within the project.




/ 102

7 ESURGE LIVE

7.1 Overview

The eSurge system will be set up to provide near real time data during surge events, to service the storm surge modelling community. This is the “eSurge Live” service foreseen in [SOW].

The eSurge Live service shall as a minimum apply to the following geographical areas (AOIs):

North Sea, (AOI-10).

Baltic Sea, (AOI-50).

Adriatic Sea (AOI-40): to be confirmed4.

North Indian Ocean (AOI-80, AOI-90).

Within these areas, we will make available NRT wind and wave products, tide gauge observations, and SST L4 product. We will also provide NRT reprocessed coastal altimetry (sea level and significant wave height) from ESA missions. For non-ESA altimetric missions, NRT availability will require ESA to acquire direct access to the relevant NRT streams.

There will also be some data products provided which are specific to certain AOI:

The North and Baltic Seas (AOI-10, AOI-50). Within these areas, we shall make available the DMI-supplied statistical blending product (combining delayed mode open-ocean and coastal altimetry observations with real time tide gauge sea level observations) will be generated in near real-time providing hourly 2D fields of sea level, which is based purely upon observations. The sea level product is thus independent of the model (atmosphere/ocean) skill for the present storm surge.

North Indian Ocean (AOI-80, AOI-90). NOC will supply real time, high frequency tide gauge observations from a number of countries around the basin, including Bangladesh, Thailand and Sri Lanka. (Near real time tide gauge data from India are not available as yet but their addition continues to be sought by the PSMSL.) NOC will also supply delayed time coastal altimetry data and we will use the DMI blending scheme, described above, where the density of the TG observations allows. Furthermore, we will also link through the system near-real time SAR observations from GlobWave.

eSurge-RB-REQ-420: eSurge Live

Throughout Phase-2 of the eSurge project, a NRT service of EO data shall be provided to Storm Surge forecasting systems. This service shall be called eSurge Live.


4 Depending upon the final arrangements agreed between the eSurge and eSurge-Venice projects.



/ 102


eSurge-RB-REQ-430: eSurge Live access

eSurge Live data shall be an open access service available via the eSurge web portal.

Verification Method Testing / Inspection

eSurge-RB-REQ-440: eSurge Live AOI

eSurge Live shall apply to SEVS within the following AOI:

a) AOI-10,

b) AOI-40,

c) AOI-50,

d) AOI-80,

e) AOI-90.


Note that this is the minimum set of AOI to be covered by eSurge Live; we do not exclude the possibility of including data for other AOI on a case by case basis, and hope to be able to include several such data sets.

7.2 eSurge Live Triggering and Notifications

The trigger for eSurge Live is that the surge forecast models for these areas are indicating that a storm surge SEV is expected. It may be possible to also have a SEV triggered should authorised users with their own forecasting systems inform eSurge that an SEV is expected. There will be some mechanism for authorised users to flag an occurring SEV. It is not expected that SEVs will be triggered automatically by the forecasting systems.

The exact approach to be adopted is still under discussion.

For eSurge Live to be useful, users must be aware that the data is being made available. However it is not part of eSurge’s remit to provide forecasts, as these are the responsibility of local agencies in each country. It must therefore be clear to all recipients that any notification from eSurge does not constitute a formal surge warning.

eSurge-RB-REQ-450: eSurge Live Triggering

There shall be a mechanism for suitably authorised users to flag that an SEV is under way or expected.


eSurge-RB-REQ-460: eSurge Live Triggering

There shall be a means by which users may be notified that a SEV has been triggered.

Verification Method Inspection/ Testing



/ 102

7.3 eSurge Live NRT Data Products

All data for the eSurge Live service shall be made available via the SEARS database.

eSurge-RB-REQ-470: NRT Data Products Available via eSurge Live

During Storm Surge events, the following data shall be available via SEARS:

a) NRT1: NRT winds.

b) NRT2: NRT blended water level.

c) NRT3: NRT waves.

d) NRT4: NRT wave spectra.

e) NRT5: NRT SST L4.

f) NRT6: NRT surge forecast (Yellow sea, North Indian Ocean).

g) NRT7: NRT surge forecast ( North sea, Baltic sea).

h) NRT9: NRT Coastal Altimetry.

i) NRT10: NRT IR data.


Details of the data products to be included in eSurge Live are given in annex C.10.

These products shall be available in near real time, however the definition of what “near real time” means will depend upon what is possible for a given product:

Sea level tide gauge data for DMI stations (within the North and Baltic seas) will be available within 1-2 minutes, with other sea level data available within 1 hour. The blending product will be ready within 1.0-1.5 hour.

The time for other products is TBC but is expected to be of order a few hours.

7.4 Interface Requirements with SEARS

The eSurge Live data shall be provided to users via SEARS.

eSurge-RB-REQ-480: Access to eSurge Live Data Products

During Storm Surge events, the data available in SEARS shall have:

a) Appropriate NRT data access interfaces.

b) A browse catalogue of available data.

c) Online quick-look products

d) Information regarding the quality and availability for each service.




/ 102


7.5 eSurge Live User Support

As well as providing NRT data access, SEARS shall also make available information to help users make use of the data, i.e. a catalogue of data, quick look products and quality/reliability information.

eSurge-RB-REQ-490: eSurge Live User Support

During Storm Surge events, users shall be provided with:

a) An easy means to contact the eSurge project with feedback or advice.

b) Baseline support via email.


7.6 eSurge Live Service Availability

eSurge Live is intended as a demonstration of feasibility, and not as an operational service. For this reason we have not given a requirement on service availability.

Nevertheless we shall attempt to reach a target of 85% availability during phase 2 of the project, where availability is defined as in section 8.2.

The limiting factor in the service availability is expected to be the website availability, which is discussed in section 8.2. In the event that there is a failure of access to the Internet during a surge event, no data will be lost. Scheduled data acquisition will resume and data will be made available to users at the earliest opportunity following the restoration of service.

eSurge-RB-REQ-500: eSurge Live Target Availability

eSurge Live shall have a target availability of at least 85%.

Verification Method Analysis



/ 102

8 CONTENT AND FUNCTIONALITY OF THE ESURGE WEB PORTAL

8.1 Web Portal Overview

The aim of the eSurge web portal is to provide users with a resource to make full and easy use of the eSurge data products and services facilitating their application in storm surge activities.

This section outlines the user requirements for content and services of the eSurge portal, and for product and system documentation provided via the portal.

eSurge-RB-REQ-510: eSurge Web Portal

The eSurge project shall develop, operate and maintain a central web portal that shall provide a single entry point to all aspects of the project.


eSurge-RB-REQ-520: Web Portal Contents

The eSurge web portal shall contain at least the following content:

a) Information about the eSurge project, including background, objectives, work plan and schedule, latest project news and news archive, dates/venues/registration link/presentations of all open meetings, list of eSurge team members, contacts of the project manager and consortium partners.

b) Links to related activities and a page announcing future meetings.

c) A list of eSurge Champion users.

d) Links to international storm surge systems and contact details for those systems.

e) For each eSurge AOI, provide a summary review of Storm Surge Events (SEV).

f) A Distance Education section for eSurge data products and services for Storm surge applications.

g) Description and links to all sources all data used in the project.

h) Description and links to all satellite data sets used within the eSurge project including links to their ATBD and source processing systems.

i) Guides on how to access satellite data provided by the space agencies, and information on reprocessing activities.

j) Access to the Surge Event Analysis and Repository Service (SEARS).

k) Access to all public project documentation.

l) Provision for user feedback.

m) Any other service or function required to implement the eSurge project.




/ 102


eSurge-RB-REQ-530: eSurge Web Portal Maintenance

The web portal shall be maintained for the duration of the project, adding project deliverables as they become available and functionality as required by the SoW and/or user requests.


eSurge-RB-REQ-540: eSurge Web Portal User Management

The web portal shall provide facilities to support user management including user profiles with appropriate privileges.


8.2 Portal Availability

The portal shall be operated in a manner to achieve an expected availability of at least 95% of the time throughout Phase 2 of the project.

Note that the service availability shall be appropriate to a demonstration service, and as such the system is supported on a best efforts basis only outside normal business working hours.

Availability is defined as being the fraction of the time that the website is expected to be operational for which it is actually operational. As such, scheduled maintenance times are excluded, as are periods such as the Christmas vacation period during which support cannot be guaranteed.

Server and Network availability shall be monitored by software products such as Nagios or Ganglia.

eSurge-RB-REQ-550: Portal Availability

The eSurge portal shall be operated in a robust manner with an availability of more than 95%.

Verification Method Testing / Analysis

eSurge-RB-REQ-560: Portal Recovery

Offsite backup procedures shall be developed in order to facilitate quick restoration of the portal from events such as disk failure, fire, etc.


eSurge-RB-REQ-570: External Links Availability

Procedures shall be developed to report problems regarding potential unavailability of live links to remote sites.




/ 102

8.3 Project Documentation

All internal project documentation shall be made available on the website, however this should not be publically available.

eSurge-RB-REQ-580: eSurge Project Domain

The web portal shall provide a password protected eSurge project section containing project internal documentation, such as all draft document deliverables, RIDs, meeting minutes, actions database, monthly reports, project management plan, etc.


eSurge-RB-REQ-590: Access to the Project Domain

Access to internal sections of the eSurge web portal shall require registration.


8.4 Outreach

The web portal shall be the primary tool for engaging the user group and the wider storm surge community. It will be a unique point of access for users to the eSurge suite of information, data and products. It will be a focal point for the storm surge community and will play a key role in consolidating the outputs for all activities carried out in eSurge.

The website will be reviewed at least monthly, with updates(either new pages or news stories) being added at least once a month. News stories shall cover items related to the project, but also items of more general interest to the storm surge community.

Other types of outreach tools (twitter, facebook, etc) may additionally be used.

eSurge-RB-REQ-600: eSurge Web Portal Review

The web portal shall be reviewed at least once per month.


eSurge-RB-REQ-610: News Stories

The website shall be updated with news stories and new content at least monthly.




/ 102


8.5 Data Access

Users require access to, where feasible, freely and publicly available data products in order to support their relevant storm surge activities and responsibilities. The data access requirements are discussed in section 5.4.

User requirements in respect to NRT time delay for data access varies due to their experiences and realistic expectations in this area. Generally, what is nearest to real-time and reasonably feasible to implement is desired.

Users shall need to sign on in order to access data via SEARS. This should be a single sign on, i.e. no further registration shall be needed to access specific data sets, even if they are held remotely. However in some cases this may not be possible, as third party data providers may require registration. This is only expected to affect a small number, if any, of data sets.

eSurge-RB-REQ-620: eSurge Data Restrictions

Data and information accessible via the portal shall be provided publicly and without restriction, unless the conditions under which the data are made available impose such restrictions.


eSurge-RB-REQ-630: eSurge Data Sources

All sources of data and information products shall be fully acknowledged.


eSurge-RB-REQ-640: Access to SEARS Data

All information in SEARS shall be accessible via the web portal via commonly used interface tools that are community accepted


eSurge-RB-REQ-650: Login access to SEARS Data

A user login or email address shall be required for data access.


eSurge-RB-REQ-660: Single Sign On

Only a single user sign on shall be required for all data access, unless required by a third-party data provider.




/ 102

eSurge-RB-REQ-670: Access restrictions for SEARS Data

The data access system shall be designed in a way that will not restrict users from downloading data in an automated way via a script.


eSurge-RB-REQ-680: Batch downloads of SEARS Data

An option to easily batch download multiple data from the portal shall be provided.


eSurge-RB-REQ-690: Access formats for SEARS Data

Data access formats shall be open standards.


8.6 Online Tools

Users require online tools to manipulate and work with the information and data products available through SEARS.

Users have also stated that text based products are not wholly adequate regarding storm surge notifications. There is a need for better visualisation of surge predications.

We will continue to refine the baseline for the online tools needed during the Technical Specification phase in collaboration with users.

eSurge-RB-REQ-700: SEARS Geographical Interface

An interactive geographical interface shall be used based on standards compliant map server (or equivalent) architecture which will allow users to visualise data products from the SEARS system.

Verification Method Testing / Inspection

eSurge-RB-REQ-710: Online Tools

The portal shall provide access to standards based tools to manipulate and work with SEARS data. A diagnostic data set facility is required for extracting time series of all SEV products over a given geographical location, as well as statistics of match-ups with in-situ and other (e.g. model output) data held by eSurge.




/ 102


eSurge-RB-REQ-720: Online Tools - Bibliography

a) A geographically mapped bibliography of SEV for each AOI shall be developed.

b) A facility shall be provided for registered users to update the review and bibliography.

c) Access to the facility to update the review and bibliography shall require registration.


eSurge-RB-REQ-725: Responsiveness of Online tools

The online tools supplied through the portal shall have sufficient responsiveness to allow users to use them effectively.




/ 102

9 TRAINING AND OUTREACH

9.1 Overall Objectives of eSurge Training

To support uptake of the system, the consortium will encourage and assist the storm surge community by means of training. This training is a key aspect of building the relationship between potential service providers and the end-user community, of stimulating interest and awareness of the eSurge system and the developed operational products, and in improving the skills of professionals and operators in the field of storm surge forecasting.

Training will be provided via distance learning materials (available on the eSurge portal), via DVDs which will allow the training to be carried out off-line and via a two-day face-to-face workshop involving up to 50 end users and practitioners. All materials will be internally reviewed for completeness and consistency before publication.

Upon completion of the training, users are expected to be confident of how to use the web portal to its full potential, have a solid critical understanding of the datasets available and how to use them, and have a greater insight into how satellite derived information can assist in storm surge forecasting and assessment. Follow-up actions with those who take part in the training activities will be used to assess their impact and success.

9.2 Distance Learning Requirements

An important component of eSurge training is that it must be provided remotely, as not all users will be able to attend the training course.

Interaction with the eSurge web-GIS interface to SEARS will be required in order to complete the course. The materials will be accessible directly from a tab on the eSurge portal. Basic guidance on how to navigate the material including recommendations on browser type and screen size will be given.

The potential of employing webinars (seminars on the web) to deliver elements of the on-line training will be evaluated

Students will be required to register on the site and provide very basic information (e.g. country of access and email address) to access the training course. These registrations will be saved for statistical purposes.

In addition, a DVD training course will also be developed. This will be very similar to the on-line distance learning material, however direct interaction with SEARS will not be a pre-requisite. A sample of representative eSurge data and products will be provided on the DVD to ensure students complete the course using real data. The course will be suitable for a workshop or can be carried out by a student working independently. Orders for the DVD can be made via the eSurge portal.

When users register for the DVD they shall be advised that they are expected to complete and submit a completed questionnaire on completion of the training.



/ 102


eSurge-RB-REQ-730: Compilation of Online Distance Learning Material

Training material shall be compiled by T0+15 months.


eSurge-RB-REQ-740: Duration of Online Distance Learning Material

The training material shall take a minimum of 6 hours and a maximum of 12 hours to complete, split into a number of lessons.


eSurge-RB-REQ-750: Contents of Online Distance Learning Material

This series of lessons shall include

a) background information on storm surge events and their implications,

b) descriptions of the various remote and in-situ products and how they can be used in Storm surge forecasting and evaluation (e.g. altimeter, SAR, SST, tide gauges).

c) a lesson on modelling; assimilation of observations into the model and how to interpret the outputs;

d) a demonstration of applications using typical SEV processed in the project.

Each lesson will be coded with a difficulty level and will include a self-assessment section and an interactive quiz.


eSurge-RB-REQ-760: Materials for Online Distance Learning Material

The learning materials shall consist of short audio presentations, graphics (static and animated), explanatory text, and interactive forms.

Specifically designed exercises shall be provided to facilitate interaction with elements of the SEARS database and the eSurge Live facility.

Links shall be provided to additional relevant material both within the eSurge portal and on external web sites.


eSurge-RB-REQ-770: Availability of Online Distance Learning Material

The training material shall be available via the eSurge website, requiring only very basic registration information (e.g. country of access and email address) to access the training course.




/ 102

eSurge-RB-REQ-780: Follow up of Online Distance Learning Material

A follow-up questionnaire, tailored to the online training course, shall be prepared and sent by email to the supplied registration address.


eSurge-RB-REQ-790: Provision of Offline Distance Learning Material

A DVD training course shall be developed suitable for use as part of a workshop or for students working independently. This training course shall not require access to SEARS


eSurge-RB-REQ-800: Ordering of Offline Distance Learning Material DVD

Ordering of the DVD shall be possible via the eSurge portal.


eSurge-RB-REQ-810: Follow up of Offline Distance Learning Material

A follow-up questionnaire, tailored to the offline training course, shall be prepared and sent by email to the supplied registration address.


9.3 Workshop Training Requirements

The training course will be developed and delivered in a workshop run over two days, currently scheduled for K0+20, to an audience of up to 50 participants. The course instructors will be made up of experts from within the consortium and from the wider storm surge community where appropriate.

eSurge-RB-REQ-820: eSurge Training Course and Workshop

A training course shall be developed and delivered in a workshop run over two days to an audience of up to 50 participants.


eSurge-RB-REQ-830: eSurge Training Course Instructors

The course instructors shall be experts from within the consortium and from the wider storm surge community where appropriate.




/ 102


eSurge-RB-REQ-840: eSurge Training Course Material

The course activities shall include:

a) An overview of relevant ESA EO activities and the eSurge project.

b) A series of seminars introducing various relevant satellite and in-situ data products and how they can be used to improve storm surge prediction.

c) A hands-on session involving interaction with the SEARS database and eSurge Live held in a computer laboratory.

d) Self assessment exercises with experts on hand to assist.

e) A detailed look at specific applications and the benefits of eSurge products and how they can be used in operational scenarios.

f) A feedback and a question and answer session.


eSurge-RB-REQ-850: eSurge Training Course Feedback

Feedback from the course shall be compiled and analysed and presented at UCM-3 and form part of the reporting to ESA.


Although the content of the training course will be refined nearer the time, it is expected to take a form similar to previous courses run by CMRC:

The first morning will provide an overview of relevant ESA EO activities and the eSurge project followed by a series of seminars introducing various satellite and in-situ data products and how they can be used to improve storm surge prediction.

The first afternoon will be a hands-on session held in a computer laboratory where participants can view, interrogate and analyse different processed products using both proprietary software (e.g. ENVI/ERDAS) and the eSurge portal itself. A series of exercises will be developed in order to focus the training. Self assessment exercises will be included and experts will be on hand to assist.

The second morning will look more in detail at specific applications and the benefits of eSurge products and how they can be used in operational scenarios. The workshop will conclude with a feedback and a question and answer session. This feedback will be compiled and analysed and presented at UCM-3 and form part of the reporting to ESA.

The training course is currently planned to take place at the National Maritime College of Ireland (NMCI) in Cork. This state-of-the-art facility has lecture theatres, workshop rooms, computer laboratories and catering facilities, all easily accessible from Cork International airport (14 km).

NOC will contribute by designing training and outreach material for the community around the Indian Ocean, to be included in course modules already being delivered in



/ 102

the region or planned for the future, which maximises the impact of the material. In doing this regional links will be exploited (ASCLME, NIO, several East African research institutions, Mauritius Oceanography Institute) as well as some of the contacts and ideas that have been established through ALTICORE-Africa, in which NOC plays a leading role. DMI will contribute to training materials and give lectures in the eSurge training course.

As the North Indian Ocean is an important area of interest, input from the Indian Space Research Agency to training materials would be valuable. ISRO shall therefore be contacted in regard to training. Furthermore the experiences of the IOC/WMO Coastal Inundation Forecasting Demonstration Project (CIFDP) would be of value as part of the training. Appropriate contacts shall be made.

eSurge-RB-REQ-860: eSurge Training - External Contributions

a) ISRO shall be invited to input to the training activities. Any inputs forthcoming shall be evaluated and incorporated as appropriate

b) The IOC/WMO iin regard to the CIFDP project) shall be invited to input to the training activities. Any inputs forthcoming shall be evaluated and incorporated as appropriate.


9.4 Other Outreach Activities

In order to facilitate the use of eSurge services, in addition to the training and workshops, we will look into other ways to interact with users. These may include newsletters, User Consultations meetings, or ad hoc methods such as emails.

In addition, we will evaluate the feasibility of creating interactive groups, using blogs, wikis or social media sites (facebook, linkedin). Outreach activities must also consider non-standard users (e.g. media, insurance) as well as data users and modellers.

eSurge-RB-REQ-870: eSurge outreach

The following means shall additionally be used to communicate with users:

a) Newsletters.

b) User Consultation Meetings.

c) Ad hoc emails.


eSurge-RB-REQ-880: eSurge online communities

The establishment of interactive eSurge community groups using social networking services shall be evaluated.




/ 102


ANNEX A USER QUESTIONNAIRE

A.1 About the User Questionnaire

The original requirements baseline for eSurge, given in [SOW], was the outcome of a series of discussions between ESA and potential system users, culminating in a User Consultation Meeting (UCM) held in Venice in September 2009. However, in order to update and refine these requirements, the eSurge project carried out a user survey during its first 2 months. This consisted of a questionnaire, followed up by a series of phone interviews.

As a result, we received 28 completed questionnaires from users in 18 countries worldwide, as listed in Table A-1. These have been used to derive the final requirements for the project as given in this RB document.

Table A-1: Authors of received questionnaires

Name Institution Country

Begona Perez Puertos del Estado Spain

Boram Lee World Meteorological Organization (WMO)

Switzerland

Dongsheng Liu Jiangyin Marine Technology Co. Ltd China

Evelyn Murphy Met Éireann Ireland

Hans de Vries KNMI The Netherlands

Indiana Olbert National University of Ireland Galway Ireland

Jacob Nielson DMI Denmark

Jaiho Oh Pukyong National University Korea

Katherine Cronin Deltares The Netherlands

Vibeke Huess DMI Denmark

Jesse Feyen National Oceanic and Atmospheric Administration (U.S.)

U.S.A

Johan Stander South African Weather Service South Africa

John Sweeney Irish Climate Analysis and Research Units, National University of Ireland, Maynooth

Ireland

Jan-Rolf Hendriks RWS Zeeland (Hydro Meteo Centre Zeeland)

The Netherlands

Jesper Baasch-Larsen Danish Maritime Safety Administration Denmark

Leonardo Boato ICPSM - VE Italy

Lucy Wyatt Seaview Sensing UK

Michael Bruen University College Dublin Ireland

Mikhail Entel Bureau of Meteorology Australia



/ 102

Name Institution Country

Nadao Kohno Japan Meteorological Agency Japan

Nikoley Valchev Institute of Oceanology – Bulgarian Academy of Sciences Coastal Zone Dynamics Dep.

Bulgaria

Ohl Patrick Météo-France France

Paula Etala Naval Hydrographic Service (SHN) Argentina

Robert McCabe Commissioners of Irish Lights Ireland

Raj Kumar ISRO India

Shishir Dube Indian Institute of Technology Delhi India

Stefano Zechatto ICNR-ISAC Italy

Francesco De Biasio ICNR-ISAC Italy

Sarfraz Khan Pakistan Meteorological Department Pakistan

Sung Hyup You Korea Meteorological Administration (KMA)

Korea

Jang-Won Seo Korea Meteorological Administration (KMA)

Korea

A.2 Results of the User Questionnaire

User requirements are analysed in the following tables according to users and various categories. User requirements are derived for the following:

Data sets used.

Areas of interest.

Service requirements.

Required data.

Timeframe.

Downloading data.

Conference and User contribution.

Past events.



/ 102


A.2.1 DATA SETS

Table A-2 shows, that a majority of the users showed interest in data sets that were presented in the initial questionnaire i.e. Scatterometry, bathymetry etc. A few users identified additional data sets that they would make use of if available to them, such as DMI3D, Swell, QuickScat

Table A-2: Data Sets

Data Sets Used

Pu

ert

os

de

l Est

ado

(Sp

ain

)

WM

O (

Swit

zerl

and

)

JMT

(Ch

ina)

Me

t Éi

rean

n (

Ire

lan

d)

KN

MI (

The

Ne

ther

lan

ds)

DM

I (D

enm

ark)

NO

AA

(U

.S)

SAW

S (S

ou

th A

fric

a)

RW

S Ze

ela

nd

(Th

e N

eth

erla

nd

s)

ICP

SM -

VE

(Ita

ly)

UC

D (

Du

blin

)

BM

D (

Au

stra

lia)

Inst

itu

te o

f O

cean

olo

gy (

Bu

lgar

ia)

Nav

al H

ydro

grap

hic

Se

rvic

e

(Arg

en

tin

a)

ICN

R-I

SAC

(It

aly)

PM

D (

Pak

ista

n)

KM

A (

Ko

rea)

ISR

O (

Ind

ia)

Me

teo

Fra

nce

Jap

an M

ete

oro

logi

cal A

gen

cy

NU

I (M

ayn

oo

th, I

rela

nd

)

NU

IG (

Ire

lan

d)

De

ltar

es

(Th

e N

eth

erl

and

s)

Seav

iew

Se

nsi

ng

(UK

)

Dan

ish

Mar

itim

e S

afe

ty

Ad

min

istr

atio

n (

De

nm

ark)

Ind

ian

Inst

itu

te o

f Te

chn

olo

gy

De

lhi (

Ind

ia)

Scatterometry X X X X X X X X X X X X X X X X X X X X X

Coastal altimetry X X X X X X X X X X X X X X X X X X X X X X X X X X

Bathymetry X X X X X X X X X X X X X X X X X X X X X

Winds X X X X X X X X X X X X X X X X X X X X X X X X X

Visible / IR images of atmospheric conditions

X X X X X X X X X X X X X X

Tide gauge data X X X X X X X X X X X X X X X X X X X X X X X X X

Wave spectra X X X X X X X X X X X X X X X X X X X X

Flood extent maps X X X X X X X X X X X X X X X X X X

DMI3D X X

Swell X X

QuikSCAT X X X

Pressure maps X

Mtsat), A-SCAT X

Water level in offshore X

Sea surface temperature X

eSurge Requirements Baseline, D-90, Issue 2.0 8 December 2011


/ 102

Figure A-1: Total response for Data Sets

A.2.2 AREAS OF INTEREST (AOI)

Users limited their areas of interest according to their respective countries of residence and on the areas where their work was focused. There were a few exceptions, e.g. WMO have global interest and therefore displayed interest in most areas.



/ 102


Table A-3: Areas of Interest

Areas of Interest

Pu

erto

s d

el E

stad

o (

Spai

n)

WM

O (

Swit

zerl

and

)

JMT

(Ch

ina)

Met

Éir

ean

n (

Ire

lan

d)

KN

MI (

The

Net

her

lan

ds)

DM

I (D

enm

ark)

NO

AA

(U

.S)

SAW

S (S

ou

th A

fric

a)

RW

S Ze

elan

d (

The

Net

her

lan

ds)

ICP

SM -

VE

(Ita

ly)

Un

iver

sity

Co

llege

Du

blin

(Ir

elan

d)

BM

D (

Au

stra

lia)

Inst

itu

te o

f O

cean

olo

gy (

Bu

lgar

ia)

Nav

al H

ydro

grap

hic

Ser

vice

(A

rgen

tin

a)

ICN

R-I

SAC

(It

aly)

PM

D (

Pak

ista

n)

KM

A (

Ko

rea)

ISR

O (

Ind

ia)

Met

eo F

ran

ce

Jap

an M

eteo

rolo

gica

l Age

ncy

NU

I (M

ayn

oo

th, I

rela

nd

)

NU

IG (

Irel

and

)

Del

tare

s (T

he

Net

her

lan

ds)

Seav

iew

Sen

sin

g (U

K)

Dan

ish

Mar

itim

e Sa

fety

A

dm

inis

trat

ion

(D

enm

ark)

Ind

ian

Inst

itu

te o

f Te

chn

olo

gy D

elh

i (I

nd

ia)

North sea X X X X X X X X

Baltic Sea / Gulf of Bothnia X X X X X

Atlantic coast X X X X X X X X X X

Irish Sea / Celtic Sea X X X X X X X

Mediterranean Sea X X X X

Adriatic Sea X X X X X

Black Sea X X X

Indian Ocean X X X X X X X X X

Indonesian Sea X X X

Global X X

Yellow Sea / China Sea X

U.S. Coasts X

Asia-Australian region X X

Northwestern Pacific Ocean X X

English Channel X



/ 102

Figure A-2: Total response for Areas of Interest

A.2.3 SERVICE REQUIREMENTS

Users were asked to provide input of the requirements that they would wish to see as outcomes from the eSurge project. The most popular responses are summarised in Table A-4.

Users in general would like to see inclusion of higher resolution storm surge models and improved access to satellite data.



/ 102


Table A-4: Service Requirements

Service Requirements

Pu

ert

os

de

l Est

ado

(Sp

ain

)

WM

O (

Swit

zerl

and

)

JMT

(Ch

ina)

Me

t Éi

rean

n (

Ire

lan

d)

KN

MI (

The

Ne

ther

lan

ds)

DM

I (D

enm

ark)

NO

AA

(U

.S)

SAW

S (S

ou

th A

fric

a)

RW

S Ze

ela

nd

(Th

e N

eth

erla

nd

s)

ICP

SM -

VE

(Ita

ly)

Un

iver

sity

Co

llege

Du

blin

(Ir

ela

nd

)

BM

D (

Au

stra

lia)

Inst

itu

te o

f O

cean

olo

gy (

Bu

lgar

ia)

Nav

al H

ydro

grap

hic

Se

rvic

e (

Arg

en

tin

a)

Co

mm

issi

on

ers

of

Iris

h L

igh

ts (

Ire

lan

d)

ICN

R-I

SAC

(It

aly)

PM

D (

Pak

ista

n)

KM

A (

Ko

rea)

ISR

O (

Ind

ia)

Me

teo

Fra

nce

NU

IG (

Ire

lan

d)

De

ltar

es

(Th

e N

eth

erl

and

s)

Seav

iew

Se

nsi

ng

(UK

)

Pu

kyo

ng

Un

ive

rsit

y (K

ore

a)

Dan

ish

Mar

itim

e Sa

fety

Ad

min

istr

atio

n (

Den

mar

k)

Ind

ian

Inst

itu

te o

f Te

chn

olo

gy D

elh

i (In

dia

)

Coastal altimetry data for spatial validation of the models

X X X X

Storm-surge forecasts available from other institutions

X X

Improved access to satellite and in-situ data X X X X X X X X

Open-source tool for training and education X X X X

Real-time 3D ocean forecast X X

A database of past storm surge events X X X X

Inclusion of better and higher resolution storm surge models

X X X X X X X X X

Verify different storm surge forecast models X X X

Development of an accurate surge forecasting programme

X X X X X X X X

Wave model development for high tidal waves prediction

X X

Radar altimetry products X X X

Better estimates of sea levels for inundation modelling

X X X X X



/ 102

Figure A-3: Total response for Service Requirements

Other responses to the questionnaire included:

DMI 3D ocean prediction products (hourly), from 2007-now( T,S, water level and currents, hourly data).

Historical satellite winds and waves 2007-present.

An automatic alert from ESA.

BMA technique applied not only to harbour special points but also for 2D fields.

Inclusion of additional sources to ENSURF system for the South of Europe, especially in the Mediterranean.

Verify different storm surge forecast models.

Improved forecasting of surge heights.

Access to high performance computing.



/ 102


Benchmark tests, e.g. in NetCDF format.

Global tide gauge data access.

Oceansat 50/25km resolution Scatterometry data.

A publically available dataset.

Robust observation data providing (files and maps).

Storm surge values in the coast of Asian countries.

Estimations of storm surge magnitudes for emergency services approximately 48 before the onset.

Better estimates of atmospheric forcing by tropical cyclones affecting the Australian coastal areas.

Prediction of meteorological drivers.

Magnitude-Frequency of storm surges under changes climate conditions.

Mapping of vulnerability to specific hazards.

Recommendations to planning authorities.

All data and or information readily and 24/7 available.

Remotely sensed data showing advancement of surge through time.

Many of these responses are outside the scope of eSurge, so it is important to manage users’ expectations as to what the project will and will not provide.

A.2.4 REQUIRED DATA

Users were also asked which data and information was of value to them when studying a storm surge event. The most popular responses are listed in Table A-5.



/ 102

Table A-5: Required Data

Required Data

Pu

ert

os

de

l Est

ado

(Sp

ain

)

Me

t Éi

rean

n (

Ire

lan

d)

KN

MI (

The

Ne

ther

lan

ds)

SAW

S (S

ou

th A

fric

a)

RW

S Ze

ela

nd

(Th

e N

eth

erla

nd

s)

Un

iver

sity

Co

llege

Du

blin

(Ir

ela

nd

)

BM

D (

Au

stra

lia)

Inst

itu

te o

f O

cean

olo

gy (

Bu

lgar

ia)

Nav

al H

ydro

grap

hic

Se

rvic

e (

Arg

en

tin

a)

Co

mm

issi

on

ers

of

Iris

h L

igh

ts (

Ire

lan

d)

KM

A (

Ko

rea)

ISR

O (

Ind

ia)

Me

teo

Fra

nce

NU

I (M

ayn

oo

th, I

rela

nd

)

De

ltar

es

(Th

e N

eth

erl

and

s)

Seav

iew

Se

nsi

ng

(UK

)

Dan

ish

Mar

itim

e Sa

fety

Ad

min

istr

atio

n

(Den

mar

k)

Ind

ian

Inst

itu

te o

f Te

chn

olo

gy D

elh

i (In

dia

)

Tide gauge data X X X

Tide forecast X X X

Recorded Sea Level height X X X

Quality of meteorological information X X X

Real-time tide and storm surge level from tidal stations X X X

Wind wave information X X X X X X X X

SAR data X X X

Wave height X X X X

Sea level anomalies X X X

Gridded data of various atmospheric fields X X



/ 102


Figure A-4: Total response for required data

Other responses to the questionnaire included:

DMI Forecast data.

Regional and coastal storm surge model result.

Track and information for typhoon or low pressure.

In situ data.

Altimetry data (especially coastal altimetry).

Scatterometry data.

Model hindcast.

2D fields of wind, pressure (at least hourly time series).

Bathymetry and flood extent.



/ 102

Synoptic patterns.

Currents.

Sea surface temperature.

HF radar.

Pressure drop at the centre of the Cyclone.

Initiation and impact of storm surge.

A.2.5 TIME FRAME

Users were asked to provide a time frame of their typical outlook when studying a surge event after its occurrence. Most users would require information from 3-5 days, as shown in Table 9-6.

Table A-6: Time frame

How far in advance is information required

Pu

ert

os

de

l Est

ado

(Sp

ain

)

JMT

(Ch

ina)

Me

t Éi

rean

n (

Ire

lan

d)

KN

MI (

The

Ne

ther

lan

ds)

DM

I (D

enm

ark)

NO

AA

(U

.S)

SAW

S (S

ou

th A

fric

a)

RW

S Ze

ela

nd

(Th

e N

eth

erla

nd

s)

ICP

SM -

VE

(Ita

ly)

BM

D (

Au

stra

lia)

Co

mm

issi

on

ers

of

Iris

h L

igh

ts

(Ire

lan

d)

ICN

R-I

SAC

(It

aly)

PM

D (

Pak

ista

n)

KM

A (

Ko

rea)

Me

teo

Fra

nce

Jap

an M

ete

oro

logi

cal A

gen

cy

NU

I (M

ayn

oo

th, I

rela

nd

)

NU

IG (

Ire

lan

d)

De

ltar

es

(Th

e N

eth

erl

and

s)

Seav

iew

Se

nsi

ng

(UK

)

Pu

kyo

ng

Un

ive

rsit

y (K

ore

a)

Dan

ish

Mar

itim

e Sa

fety

Ad

min

istr

atio

n (

Den

mar

k)

Ind

ian

Inst

itu

te o

f Te

chn

olo

gy

Del

hi (

Ind

ia)

Weeks X

1-2 Days X X X X X X X X

3-5 Days X X X X X X X X X X X X X x X X X

Outlook up to 10 days X

Depends on acquired data X



/ 102


Figure A-5: Total response for Time frame

A.2.6 DATA DOWNLOAD

Users were asked how they would prefer to download available data. A majority of the responses showed that the first preference would be to download via FTP.



/ 102

Table A-7: Data download

Preference to download data

Pu

ert

os

de

l Est

ado

(Sp

ain

)

JMT

(Ch

ina)

Me

t Éi

rean

n (

Ire

lan

d)

RW

S Ze

ela

nd

(Th

e N

eth

erla

nd

s)

ICP

SM -

VE

(Ita

ly)

Un

iver

sity

Co

llege

Du

blin

(Ir

ela

nd

)

BM

D (

Au

stra

lia)

Inst

itu

te o

f O

cean

olo

gy (

Bu

lgar

ia)

Nav

al H

ydro

grap

hic

Se

rvic

e (

Arg

en

tin

a)

Co

mm

issi

on

ers

of

Iris

h L

igh

ts (

Ire

lan

d)

ICN

R-I

SAC

(It

aly)

PM

D (

Pak

ista

n)

KM

A (

Ko

rea)

Me

teo

Fra

nce

Jap

an M

ete

oro

logi

cal A

gen

cy

NU

I (M

ayn

oo

th, I

rela

nd

)

NU

IG (

Ire

lan

d)

De

ltar

es

(Th

e N

eth

erl

and

s)

Pu

kyo

ng

Un

ive

rsit

y (K

ore

a)

Dan

ish

Mar

itim

e Sa

fety

Ad

min

istr

atio

n

(Den

mar

k)

Ind

ian

Inst

itu

te o

f Te

chn

olo

gy D

elh

i (In

dia

)

FTP X X X X X X X X X X X

Web portal X X X X X X X

Authorised access X

Continuous data stream X

Data via GTS X X

Online repository as zip files X

Direct link to Eumetsat X



/ 102


Figure 9-6: Total response for downloading data

A.2.7 CONFERENCE AND USER CONTRIBUTION

Users were asked if they would be willing to contribute material for training and if they would like to participate in annual conferences. A majority of the users stated that they would be happy to contribute material and displayed an interest in annual conferences. However, some users did state that that attending conferences would also depend on whether a travel budget was available.



/ 102

Table A-8: Conference and Contribution

Contribution / Conference

Pu

ert

os

de

l Est

ado

(Sp

ain

)

WM

O (

Swit

zerl

and

)

JMT

(Ch

ina)

Me

t Éi

rean

n (

Ire

lan

d)

KN

MI (

The

Ne

ther

lan

ds)

DM

I (D

enm

ark)

NO

AA

(U

.S)

SAW

S (S

ou

th A

fric

a)

RW

S Ze

ela

nd

(Th

e N

eth

erla

nd

s)

ICP

SM -

VE

(Ita

ly)

Un

iver

sity

Co

llege

Du

blin

(Ir

ela

nd

)

BM

D (

Au

stra

lia)

Inst

itu

te o

f O

cean

olo

gy (

Bu

lgar

ia)

Nav

al H

ydro

grap

hic

Se

rvic

e (

Arg

en

tin

a)

Co

mm

issi

on

ers

of

Iris

h L

igh

ts (

Ire

lan

d)

ICN

R-I

SAC

(It

aly)

PM

D (

Pak

ista

n)

KM

A (

Ko

rea)

ISR

O (

Ind

ia)

Jap

an M

ete

oro

logi

cal A

gen

cy

NU

IG (

Ire

lan

d)

De

ltar

es

(Th

e N

eth

erl

and

s)

Seav

iew

Se

nsi

ng

(UK

)

Pu

kyo

ng

Un

ive

rsit

y (K

ore

a)

Dan

ish

Mar

itim

e Sa

fety

Ad

min

istr

atio

n

(Den

mar

k)

Ind

ian

Inst

itu

te o

f Te

chn

olo

gy D

elh

i (In

dia

)

Willing to contribute information for training materials

X X X X X X X X X X X X X X X X X X X

Attend annual conference

X X X X X X X X X X X X X X X X X X X X X X

Figure A-7: Total response for conference and contribution



/ 102


A.2.8 OUTREACH AND TRAINING

In order to learn about the eSurge system, users were asked how they would like to be trained i.e. offline training materials, attending a training course. Users in general preferred to be trained using online and offline materials.

Table A-9: Outreach and Training

Outreach and Training

Pu

ert

os

de

l Est

ado

(S

pai

n)

WM

O (

Swit

zerl

and

)

JMT

(Ch

ina)

Me

t Éi

rean

n (

Ire

lan

d)

KN

MI (

The

Ne

ther

lan

ds)

DM

I (D

enm

ark)

NO

AA

(U

.S)

SAW

S (S

ou

th A

fric

a)

RW

S Ze

ela

nd

(Th

e

Ne

the

rlan

ds)

ICP

SM -

VE

(Ita

ly)

Un

iver

sity

Co

llege

Du

blin

(Ir

ela

nd

)

BM

D (

Au

stra

lia)

Inst

itu

te o

f O

cean

olo

gy

(Bu

lgar

ia)

Nav

al H

ydro

grap

hic

Serv

ice

(A

rge

nti

na)

Me

teo

Fra

nce

PM

D (

Pak

ista

n)

ISR

O (

Ind

ia)

Jap

an M

ete

oro

logi

cal

Age

ncy

NU

IG (

Ire

lan

d)

De

ltar

es

(Th

e

Ne

the

rlan

ds)

Seav

iew

Se

nsi

ng

(UK

)

Pu

kyo

ng

Un

ive

rsit

y

(Ko

rea)

Dan

ish

Mar

itim

e Sa

fety

Ad

min

istr

atio

n

(Den

mar

k)

Attend a course

X X X X X X X X X X X X X X

online materials

X X X X X X X X X X X X X X X X X X X X

Offline training materials

X X X X X X X X X X X X X X X X X

Figure A-8: Outreach and Training


© 2010 Logica UK Ltd

/ 102

A.2.9 PAST EVENTS

Users were asked if there were any past events that they were interested in having satellite data for. The response to this question was of a similar nature to the response shown for areas of interest as users limited their interest in past events around their countries of residence.

The user defined SEVs have been included in the SEV list provided in Annex D.

eSurge Requirements Baseline D-90, Issue 2.0

8 December 2011

/ 102


ANNEX B REQUIREMENTS MAPPING

B.1 Mapping to SOW Requirements

The table below shows the mapping between the numbered requirements given in section 8.5 of [SOW] and the numbered requirements given in this document.

SOW requirement RB requirement Notes

ID Requirement Text ID

[REQ-10]

The eSurge project shall define and catalogue (as a minimum) ~2-300 historical Storm Surge Event (SEV) case studies (including positive and false positive forecast cases) from 1991- present in the AOI defined in SOW Table 3. Note that EO data may have most impact for storm surge applications and services in regions not well covered by traditional in situ infrastructures.

The eSurge SEV shall include both tropical cyclone (TC) and extra-tropical cyclone (ETC) storm surge cases as part of its baseline work and as a minimum requirement: a) SEV in the European Region defined by [AOI-10][AOI-20][AOI-30][AOI- 40][AOI-50][AOI-60][AOI-70] and, b) SEV in the North Indian Ocean/Bay of Bengal defined by [AOI-80][AOI-90]. Collaboration with Storm Surge activities in the Indian Ocean and Bay of Bengal shall be a key aspect of the eSurge project.

The Bidder is encouraged to consider other user specified AOI and SEV for approval by ESA.

eSurge-RB-REQ-010

This requirement has been directly flowed down from the SOW. The AOI definitions have been made more precise, see Table 3-1. SEVs from other AOI may optionally be included: this covers the remark “The Bidder is encouraged to consider other user specified AOI and SEV for approval by ESA.” See section 3.2.

eSurge-RB-REQ-020 This follows directly from the SOW requirement.

eSurge-RB-REQ-030 The option to have some SEVs from an earlier time has been allowed for.

eSurge-RB-REQ-040

This extends and quantifies the requirement to include false positive cases.

[REQ-20]

The eSurge project shall develop, operate and maintain a central web portal that shall provide a single entry point to all aspects of the project. The aim of the eSurge web portal is to provide users with a resource to make full and easy use of the eSurge data products and services facilitating their application in storm surge activities.

The eSurge web Portal shall conform to the following specification:

- Be operated in a robust manner with an availability of >95%.

- All data and information accessible via the portal shall by default be provided publicly and without restriction.

- All sources of data and information products shall be fully acknowledged.

- Access to all data products hosted on the web portal shall require the user to enter their email address, which shall then be added to the eSurge Directory.

- Contain introductory information about the eSurge project, including background,

eSurge-RB-REQ-510

eSurge-RB-REQ-520

eSurge-RB-REQ-530

eSurge-RB-REQ-540

eSurge-RB-REQ-550

eSurge-RB-REQ-560

eSurge-RB-REQ-570

eSurge-RB-REQ-580

eSurge-RB-REQ-580

This requirement has been flowed down into multiple requirements and made more precise. User feedback has also been included. See section 8.



/ 102



objectives, work plan and schedule, latest project news and news archive, dates/venues/registration link/presentations of all open meetings, list of eSurge team members, contacts of the project manager and consortium partners.

- Links to related activities (i.e. Table 5 and other activities) and a page announcing future meetings).

- A list of eSurge Champion users.

- Links to international storm surge systems and contact details for those systems.

- For each eSurge AOI, provide a summary review of Storm Surge Events (SEV). A geographically mapped bibliography of SEV for each AOI shall be developed. A facility shall be provided for registered users to update the review and bibliography. Access to the facility to update the review and bibliography shall require registration

- A Distance Education section for eSurge data products and services for Storm surge applications.

- Description and links to all sources all data used in the project.

- Description and links to all satellite data sets used within the eSurge project including links to their ATBD and source processing systems. Guides on how to access satellite data provided by the space agencies, and information on reprocessing activities described in [REQ-170]

- Access to the Surge Event Analysis and Repository Service (SEARS) described in [REQ-30]. An interactive geographical interface shall be used based on standards compliant map server (or equivalent) architecture as required by [REQ-40].

- Standards based tools to manipulate and work with SEARS data. A diagnostic data set facility is required for extracting time series of all SEV products over a given geographical location, as well as statistics of match-ups with in-situ and other (e.g., model output) data held by eSurge. Other tools shall be defined and implemented based on user requirements as required.

- FTP access to all eSurge products within eSurge AOIs. This section shall include all prototype and final eSurge products, as well as any relevant products contributed by the eSurge User Group as required by [REQ-50], [REQ-40], [REQ-160].

- Access to all public project documentation.

- A password protected eSurge project section containing project internal documentation, such as all draft document deliverables, RIDs, meeting minutes, actions database, monthly reports, project management plan, etc. Access to internal sections of the eSurge web portal shall require registration.


8 December 2011

/ 102




- Any other service or function required to implement the eSurge project.

[REQ-30]

The eSurge project shall compile a storm surge database and data catalogue of all SEV called the eSurge Event Analysis and Repository Service (SEARS).

SEARS shall include, for each SEV: - EO derived estimates of TWLE, Hs, Wind speed and preferably wind velocity, wave, swell, SST, Sediment load, - Optical high-moderate resolution image data to monitor and track the evolution of storms during the SEV. - Optical high-moderate resolution image data in the coastal zones (land and sea) for inundation mapping during the SEV. - NWP, NOP, wave and storm surge model outputs as a baseline for each storm surge case. - Impact assessment maps, inundation maps, socio-economic data and other data (ideally data should be available in each case for the whole chain down to evacuation models). - Validation data sets. - External bathymetry maps and coastal terrain maps. - In situ information suitable for data assimilation, verification and validation. - Other information and data relevant to the description and analysis of each SEV.

Information describing each SEARS SEV, all associated data, tools, documentation and any other relevant resource shall be accessible through an easy to use (verified by User Feedback) web-based user interface that allows the overlay products (in a quantitative GIS type interface).

eSurge-RB-REQ-050

eSurge-RB-REQ-060

eSurge-RB-REQ-070

eSurge-RB-REQ-080

eSurge-RB-REQ-090

eSurge-RB-REQ-100

eSurge-RB-REQ-110

eSurge-RB-REQ-120

eSurge-RB-REQ-130

eSurge-RB-REQ-140

eSurge-RB-REQ-150

eSurge-RB-REQ-160

This requirement overlaps with several other numbered requirements in the [SOW]. Between them, the requirements listed provide complete coverage of this SOW requirement.

[REQ-40]

The eSurge project shall include both re-analysis and data assimilation impact assessment experiments using eSurge satellite data as a baseline component of the eSurge Phase-2 project impact assessment.

The target outcomes of this work are: - To encourage and assist the storm surge community to fully exploit the potential of satellite data for storm surge applications and - To increase user uptake of coastal altimetry and other satellite data products by demonstrating their value in storm surge applications. - All results from these activities shall be included in the SEARS database.

All impact experiments shall be agreed with the Agency prior to implementation.

eSurge-RB-REQ-350

eSurge-RB-REQ-360

eSurge-RB-REQ-370

eSurge-RB-REQ-380

eSurge-RB-REQ-390

eSurge-RB-REQ-400


[REQ-50]

Throughout Phase-2 of the eSurge project, a NRT service of EO data shall be provided to Storm Surge forecasting systems. This service shall be called eSurge-live.

eSurge-live shall for all areas of [REQ-10]:

eSurge-RB-REQ-420

eSurge-RB-REQ-430

eSurge-RB-REQ-440




/ 102



- be available as an open access service via the eSurge web portal to encourage the widest possible use of EO data (i.e. academic, commercial and operational users) in support of storm surge applications,

- provide appropriate NRT data access interfaces,

- provide a browse catalogue of available NRT EO data including coastal altimetry products and scatterometer winds, and surface wave products relevant to storm surge applications,

- provide on-line quick-look products for NRT services,

- provide NRT information describing the quality and availability of service for each product,

- provide an easy means for NRT users to contact the eSurge project and leave feedback or seek advice in a timely (TBD with users) manner.

- provide baseline support to users during NRT SEV,

- provide other services requested by storm surge users within the scope of the eSurge project.

All eSurge-live data relevant to new SEV shall be included in the SEARS.

eSurge-RB-REQ-450

eSurge-RB-REQ-460

eSurge-RB-REQ-470

eSurge-RB-REQ-480

eSurge-RB-REQ-490

[REQ-60]

The eSurge project shall develop standards based (e.g., netCDF Climate Forecast convention) satellite products for storm surge applications and services with full endorsement from the eSurge user community.

eSurge-RB-REQ-250 This requirement has been made specific to the convention chosen. See section 5.2.1

[REQ-70]

The eSurge project shall develop and/or provide validated easy to use (verified by User Feedback) high resolution EO derived wind data products, particularly in the coastal zone, tuned to storm surge user requirements.

eSurge-RB-REQ-070

This requirement defines the specific products to be provided. See section 4.1.2.2.

[REQ-80]

The eSurge project shall and provide validated easy to use (verified by User Feedback) EO derived Total Water Level Envelope (TWLE) products tuned to storm surge applications particularly in the coastal zone. The Contractor shall start from the ESA COASTALT and/or other similar project processors and outcomes.

eSurge-RB-REQ-060


[REQ-90]

The eSurge project shall develop and/or use a common orthometric height reference system for all products and services. The project shall establish and demonstrate appropriate links, as a user, to other projects in this respect.

eSurge-RB-REQ-260

See section 5.2.1

[REQ-100]

The eSurge project shall develop and/or provide validated easy to use (verified by User Feedback) EO derived wave products tuned to storm surge applications particularly in the coastal zone.

eSurge-RB-REQ-090

This requirement defines the specific products to be provided. See section 4.1.2.4

[REQ-110]

The eSurge project shall develop and/or provide validated easy to use (verified by User Feedback) EO derived SST products tuned to storm surge applications particularly in the

eSurge-RB-REQ-080



8 December 2011

/ 102




coastal zone and tropical oceans.

[REQ-120]

The eSurge project shall develop and/or provide validated easy to use (verified by User Feedback) EO derived products tuned to monitor storm track development, intensity and impact (e.g., swell tracking, TCHP, etc)

eSurge-RB-REQ-120


eSurge-RB-REQ-100

New: ocean colour was mentioned elsewhere in the SOW but not in the numbered requirements. See section 4.1.2.5

[REQ-130]

The eSurge project shall develop and/or provide validated easy to use (verified by User Feedback) EO derived sediment load products tuned to storm surge applications particularly in the coastal zone as required by users.

eSurge-RB-REQ-110

This requirement defines the specific products to be provided. See section 4.1.2.6

[REQ-140]

The eSurge project shall provide access to easy to use (verified by User Feedback) EO derived flood mapping products (e.g., River/Estuary state, river stage from altimetry, flood state from optical and microwave data) tuned to storm surge applications particularly in the coastal zone. The use of existing products and services is encouraged.

eSurge-RB-REQ-150

The requirement has been made more precise. See section 4.1.5.

[REQ-150]

The eSurge project shall develop and/or provide validated easy to use (verified by User Feedback) EO derived nowcast products (e.g. winds, waves, coastal altimetry TWLE) tuned to storm surge applications particularly in the coastal zone. Nowcast products shall build on the complementary nature of EO measurements, in situ measurements and appropriate models and include L2, L3 and L4 products as required by users.

eSurge-RB-REQ-470

This requirement takes the data requirements in the SOW and makes it more precise, indicating exactly which products will be provided. See section 7.3.

eSurge-RB-REQ-130

New: tide gauge data was mentioned elsewhere in SOW but not in numbered requirements. See section 4.1.3.

eSurge-RB-REQ-150

New: DEM was mentioned elsewhere in SOW but not in numbered requirements. See section 4.1.5.

eSurge-RB-REQ-180

eSurge-RB-REQ-190

New: the requirement for validation was made in several places, so we have made it into separate requirements for convenience. See section 4.1.7.

eSurge-RB-REQ-200

New: the requirement for checking was made in several places, so we have made it into a separate requirement for convenience. See section 4.1.7.

[REQ-160]

The eSurge project shall develop and provide appropriate and validated delivery options for EO products in support of storm surge users with low bandwidth data connections.

eSurge-RB-REQ-340

No change. See section 5.6

[REQ-170]

The eSurge project shall develop and maintain tailored versions of EO product handbooks for each eSurge product and service.

Product handbooks shall include:

eSurge-RB-REQ-210

eSurge-RB-REQ-220

eSurge-RB-REQ-230

This has been flowed down from the SOW and split into separate requirements, with the following changes:

1) product handbooks are applicable to products, not to



/ 102



- Glossary of terms, a table of acronyms - Introduction and summary of product use in storm surge applications - Relevant background material describing the product with links to ATBD and other reference material, - Description of the algorithms applied to generate the product, - Range of product accuracy, precision and links to validation information and validation evidence - User guidance on the application of products, - A description of strengths and weakness of each data product for storm surge applications, - Relevant scientific and engineering journal paper and report references, - Detailed description of product format, - Estimates of file sizes, - Description of where and how to access/order products - Contact points for each product, - Full visualisation (e.g., images, line plots etc.) of an example product, - Example read software and links to actual software code available on the eSurge web portal, - A product FAQ tailored to storm surge applications. - A feedback form and contact details to submit feedback allowing users to report problems and request further information. - Any other material required by beginner users to successfully understand, read and apply the product. - Appendices detailing any web sites, software tools, read software etc.

eSurge product handbooks shall be maintained and updated based on user feedback and product/service evolution for the duration of the eSurge project.

eSurge-RB-REQ-240

services, which are documented separately.

2) We have noted that product handbooks may need tailoring for specific products, however the nominal TOC remains the same.

See section 4.2.

B.2 Mapping to User Questionnaire

The results of the user questionnaire have been use to map the SOW requirements into our new set of requirements. This has been discussed in the main text, and is indicated in the “Notes” column of the table in annex B.1.


8 December 2011

/ 102


ANNEX C DATA PRODUCT DESCRIPTIONS

This annex gives data product descriptions for all data products currently being proposed for inclusion in SEARS.

Note that these descriptions are being maintained in this document here for convenience, however following SRR they will be maintained as part of the DARD.

C.1 Coastal Altimetry

Product: SL1 Coastal altimetry (delayed-time)

Provider: NOC

Areas of Interest covered: AOI-10, AOI-20, AOI-30, AOI-40, AOI-50, AOI-60, AOI-70, AOI-80, AOI-90

Expected number of events: TDS: 50 FPDS: 200

Description: Altimeter data reprocessed by coastal altimetry processor, with specialized retracking and corrections, to obtain the TWLE.

Missions and time spans:

ERS-1: 01 Feb 1992 to 02 June 1996

ERS-2: 29 April 1996 to 22 June 2003

Envisat RA-2: 26 Aug 2002 onwards

Topex/Poseidon: Oct 1992 to Oct 2005

Jason-1: Jan 2002 onwards

Jason-2: 2008 onwards

Cryosat: 2010 onwards

Source Data: Sensor Geophysical Data Records (SGDRs) for all missions

ERS-1/ERS-2/Envisat /Cryosat: from ESA

J-1/J-2: from AVISO (T/P via DVD, J-1/s via FTP)

T/P: availability of SGDR data TBC with AVISO

Source Data Format ERS-1/2, Envisat, Cryosat: ESA custom (binary)

Jason-1/2: NetCDF


Reprocessing: SGDR hi-rate waveforms are retracked with suite of specialized retrackers. “Best” estimates of range (based on goodness of fit) are selected and output. Corrections to range are recomputed with techniques optimized for the coastal strip. The corrected heights (i.e orbital heights – corrected ranges) correspond to the TWLE

Source of Error Information: Goodness of Fit and Variance of estimation will be generated by coastal altimetry processor during waveform fitting

Expected accuracy: 5 cm at 10 km from coast, 10 cm at 3 km from coast (single 20-Hz measurements)

Expected Resolution: 350 m along-track for the high-rate (20-Hz) data

C.2 Winds

Product: WI1 Winds

Provider: KNMI


Estimated number of events: TDS: 50 FPDS: 200

Description: Scatterometer winds (equivalent neutral wind speed in m/s and direction (degrees) from Seawinds, ASCAT and OSCAT. OSCAT data is delivered on experimental demonstration basis.



/ 102

Product: WI1 Winds

Source Data: Seawinds, ASCAT and OSCAT raw satellite data

Source Data Format BUFR and netCDF (part of the data)

Reprocessing: No (unless for selected cases)

Source of Error Information: OSI SAF

Expected accuracy: Better than 2 m/s in wind component RMS with a bias of less than 0.5 m/s in wind speed

Expected Resolution: Seawinds 25 km and 100 km, ASCAT 25 km and 12,5 km, and OSCAT 50 km (plans exist for 25-km OSCAT)

Product: WI2 Winds (reanalysis)

Provider: DMI

Areas of Interest covered: North Sea including shelf


Description: Surface winds gridded data hindcasted from HIRHAM model with a dynamic downscaling method using ERA-40/interim as lateral boundary conditions and background fields.

Source Data: DMI HIRHAM hindcasted winds

Source Data Format NetCDF

Reprocessing: No

Source of Error Information: TBD

Expected accuracy: RMSE better than 2m/s

Expected Resolution: 12km

C.3 Satellite SST

Product: ST1 Sea Surface Temperature (Multi-satellite)

Provider: DMI

Areas of Interest covered: North Sea including shelf


Description: Global MyOcean Level 4 reanalysis of foundation SST (OSTIA)

Source Data: Level 2 SST observations from GHRSST and OSI-SAF. Sea ice concentration from OSI-SAF

Source Data Format Netcdf 3 files, CF 1.4 compliant in GHRSST GDS 1.7 format

Reprocessing: From 1985 to 2007 and NRT archive from 2008-present.

Source of Error Information: Analytical error fields are derived and included in file

Expected accuracy: 0.1-0.5 degrees C

Expected Resolution: 0.05 degrees resolution, daily

C.4 Wave Products

Product: WA1a Waves (open-ocean altimetry)

Provider: NOC via GlobWave




8 December 2011

/ 102


Product: WA1a Waves (open-ocean altimetry)

Description: Inter-calibrated wave related parameters from all available satellite altimetry missions including consistent quality flag and error characterization, together with ancillary data from ECMWF numerical models such as distance to coast, bathymetry and sea surface temperature

Source Data: ESA ERS-1: 01/02/1992 – 02/06/1996

ESA ERS-2: 15/05/1995 – 22/06/2003

ESA Envisat: 26/08/2002 onwards

CNES/NASA Topex/POSEIDON; 25/09/1992- 08/10/2005

CNES/NASA Jason-1: 15/01/2002 onwards

CNES/NASA Jason-2: 01/12/2008 onwards

US Navy GEOSAT: 31/03/1985-30/12/1989

US Navy/NOAA GEOSAT Follow On: 08/01/2000 - 23/07/2008

Source Data Format CF compliant NetCDF, as defined within the GlobWave project

Reprocessing: Subsetting of exisiing data for AOI and times of SEVs

Source of Error Information: GlobWave Validation reports (http://www.globwave.org)

Expected accuracy: Approx. 20 cm significant wave height– provided within data stream

Expected Resolution: Equal to the altimeter footprint, approc 5-10km, along-track

Product: WA1b Waves (coastal altimetry)

Provider: NOC



Description: Estimates of significant wave height from reprocessing of altimetric data with coastal altimetry processor

Source Data: Sensor Geophysical Data Records (SGDRs) for all missions

ERS-1/ERS-2/Envisat /Cryosat: from ESA

J-1/J-2: from AVISO (T/P via DVD, J-1/s via FTP)


Source Data Format ERS-1/2, Envisat, Cryosat: ESA custom (binary)

Jason-1/2: NetCDF


Reprocessing: SGDR hi-rate waveforms are retracked with suite of specialized retrackers. One of the fitted paramenters is the significant wave height

Source of Error Information: Goodness of Fit and Variance of estimation will be generated by coastal altimetry processor during waveform fitting

Expected accuracy: 1m at 10 km from coast, 1.5m at 3 km from coast (single 20-Hz measurements)


Product: WA2 Wave spectra




Description: SAR Wave Mode Spectra, as pre-processed by the GlobWave project to provide inter-calibrated and consistently partitioned and formatted data for ESA SAR missions



/ 102

Product: WA2 Wave spectra

Source Data: Expected data sources

ESA ERS-1: 01/01/1991– 01/12/1996

ESA ERS-2: 01/01/1996 onwards

ESA Envisat: 17/12/2002 onwards

NB currently only Envisat ASAR data available


Reprocessing: Subsetting of existing data for AOI and times of SEVs


Expected accuracy: approx. 1 s mean period rms and 0.35 m SWH (for periods > 12s) – provided within data stream

Expected Resolution: Each spectrum represents return from single wave mode image (5 km x 5 km every 100km along-track for ENVISAT)

Product: WA3 Waves (operational model)

Provider: DMI

Areas of Interest covered: North and Baltic Seas


Description: Hindcasted wave data from DMI Operational WAM model by using Wi2 forcing

Source Data: DMI WAM-cycle4.5

Source Data Format GRIB

Reprocessing: YES


Expected accuracy: Average RMSE less than 50cm


Product: WA4 Wave model (scatterometry)

Provider: KNMI

Areas of Interest covered: All AOI


Description: MyWave mesoscale NWP winds after scatterometer data assimilation

Source Data: HiRLAM project, OSI SAF

Source Data Format GRIB

Reprocessing: Yes, within MyWave project after specification


Expected accuracy: 3 m/s vector wind RMS

Expected Resolution: 5 km NWP model grid

C.5 Ocean Colour

Product: OC1 Ocean Colour

Provider: NOC



Description: MERIS L2 fine resolution imagery

L2R atmospherically corrected water leaving reflectances


8 December 2011

/ 102


Product: OC1 Ocean Colour

Source Data: ESA Earthnet MER_FR__2P products

Source Data Format ESA custom (binary)

Reprocessing: N/A

Source of Error Information: ESA and ocean colour community

Expected accuracy: Surface reflectance (ocean) <2 x 10 -4

Surface reflectance (Land) < 5%

Expected Resolution: 300 x 300 m

C.6 Sediment Concentration

Product: SD1 Sediment Concentration

Provider: NOC



Description: MERIS fine resolution suspended sediment concentration.

The MERIS suspended matter products is a measurement of the suspended sediments concentration in Log10(g/m

3).

Source Data: ESA Earthnet MER_FR__2P products

Source Data Format ESA custom (binary)

Reprocessing: N/A

Source of Error Information: ESA and ocean colour community

Expected accuracy: Suspended matter < 15 %

Expected Resolution: 300 x 300 m

C.7 Additional Satellite Products

Product: HP1 Tropical Cyclone Heat Potential

Provider: NOC

Areas of Interest covered: AOI-80, AOI-90


Description: Tropical Cyclone Heat Potential (a measure of the integrated vertical temperature from the sea surface to the depth of the 26°C isotherm) computed by AOML/NOAA.

Source Data: AOML/NOAA

Source Data Format TBC with AOML/NOAA

Reprocessing: N/A

Source of Error Information: TBC with AOML/NOAA

Expected accuracy: TBC with AOML/NOAA

Expected Resolution: TBC with AOML/NOAA

Product: IR1 Infrared data from satellites for storm tracking purposes

Provider: NOC

Areas of Interest covered: All AOI




/ 102

Product: IR1 Infrared data from satellites for storm tracking purposes

Description: Infrared imagery for storm tracking from Meteosat/MVIRI and MSG/SEVIRI, covering Atlantic and Indian Ocean. Data from polar orbiting satellites (like AVHRR and ATSR) are not excluded a priori but will only be considered in those cases where the geostationary data do not provide sufficient coverage and/or resolution.

Source Data: EUMETSAT HRI-IODC and HRSEVIRI

Source Data Format BUFR

Reprocessing: N/A

Source of Error Information: N/A

Expected accuracy: N/A

Expected Resolution: ~5 Km

C.8 In Situ Products

Product: SL2 Tide Gauge Data

Provider: NOC, DMI



Description: To be provided.

Source Data: To be provided.

Source Data Format To be provided.

Reprocessing: To be provided.

Source of Error Information: TG error characterization as in Miguez et al., 2008

Expected accuracy: To be provided.

Expected Resolution: Time: 15/10minutes resolution

C.9 Model Output Products

Product: BM1 Baseline Model Outputs 1

Provider: DMI

Areas of Interest covered: North Sea & Baltic Sea


Description: DMI storm surge model (unchanged)

Source Source Data: DMI Storm surge model (section 6.2.2)

Data Format GRIB or NetCDF

Reprocessing: Yes

Source of Error Information: Errors will be characterized from validation activities in WP5

Expected accuracy: Averaged peak bias less than 10%



Provider: NOC

Areas of Interest covered: North Indian Ocean


Description: NOC storm surge model (section 6.2.2)


8 December 2011

/ 102








Expected Resolution: To be provided.


Provider: NOC

Areas of Interest covered: UK waters


Description: NOC storm surge model (section 6.2)







Product: SR1 Surge Reanalysis Model Outputs 1

Provider: DMI

Areas of Interest covered: North Sea & Baltic Sea


Description: Surge hindcast data (water level) from DMI storm surge model by using WI2 forcing

Source Source Data: DMI Storm surge model (section 6.2.2)

Data Format GRIB or NetCDF

Reprocessing: Yes


Expected accuracy: Averaged peak bias less than 10%


Product: DA1 Reanalysis with data assimilation – 1

Provider: DMI

Areas of Interest covered: North Sea and Baltic sea


Description: Water level reanalysis for the selected surge events, generated by using DMI 3D surge model with assimilating SL1 water level data (En OI or 3DVAR assimilation scheme), forced by Wi2 hindcasted winds

Source Data: DMI storm surge reanalysis

Source Data Format GRIB or NetCDF

Reprocessing: YES


Expected accuracy: Better peak bias than HC1 product



/ 102




Provider: NOC

Areas of Interest covered: North Indian Ocean


Description: Reanalysis: HC1+ assimilating SL1







C.10 NRT Products

Product: NRT1 NRT winds

Provider: KNMI


Estimated number of events: TDS: 0 FPDS: Number of surge events during service demonstration

Description: Scatterometer winds (equivalent neutral wind speed in m/s and direction (degrees) from ASCAT and OSCAT. OSCAT data is delivered on experimental demonstration basis

Source Data: ASCAT and OSCAT raw satellite data

Source Data Format in BUFR via EUMETCAST, via GTS, on FTP server and in UMARF; NetCDF on FTP server and in UMARF.

Reprocessing: N/A, unless for selected cases

Source of Error Information: OSI-SAF

Expected accuracy: Better than 2 m/s in wind component RMS with a bias of less than 0.5 m/s in wind speed

Expected Resolution: ASCAT 12,5 and 25 km and OSCAT 50 km. Plans exist for OSCAT 25 km.

Product: NRT2 NRT Blended Water Level

Provider: DMI

Areas of Interest covered: North and Baltic seas


Description: Statistical blending product using TG + altimetry as input and providing hourly L4 sea level product

Source Data: Real time tide gauge observations, NRT coastal altimetry products

Source Data Format NetCDF


Source of Error Information: Analytical error estimates

Expected accuracy: 5-20 cm in RT sea level estimation.

Expected Resolution: about 5 km, hourly fields


8 December 2011

/ 102


Product: NRT3 NRT waves




Description: Inter-calibrated wave related parameters from all available NRT satellite altimetry missions including consistent quality flag and error characterization.

Source Data: Current active missions

ESA Envisat

CNES/NASA Jason-1

CNES/NASA Jason-2

Anticipated additional Missions

Cryosat 2

AltiKa




Expected accuracy: Approx. 20 cm significant wave height– provided within data stream

Expected Resolution: Equal to the altimeter footprint, approx 5-10km, along-track

Product: NRT4 NRT waves spectra




Description: SAR Wave Mode Spectra, as pre-processed by the GlobWave project to provide inter-calibrated and consistently partitioned and formatted data for ESA SAR missions

Source Data: Expected data sources

Envisat ASAR




Expected accuracy: approx. 1 s mean period rms and 0.35 m SWH (for periods > 12s) – provided within data stream

Expected Resolution: Each spectrum represents return from a single wave mode image (5 km x 5 km every 100km along-track for ENVISAT)

Product: NRT5 NRT SST L4

Provider: DMI



Description: L4 daily, 3-5km resolution

Global Level 4 SST product using multisensor satellite data.

A Regional 2 km MyOcean product will be used in the North Sea/Baltic Sea

Source Data: Level 2 SST observations from GHRSST and OSI-SAF. Sea ice concentration from OSI-SAF and MyOcean.

Source Data Format NetCDF, 3 files, CF 1.4 compliant in GHRSST GDS 1.7 format



/ 102

Product: NRT5 NRT SST L4


Source of Error Information: Analytical error fields are derived and included in file.

Expected accuracy: 0.1-0.5 deg C

Expected Resolution: 0.05 degrees for global and 0.02 degrees for regional North Sea Baltic Sea product, daily fields.

Product: NRT6 NRT Surge Forecast

Provider: DMI, NOC

Areas of Interest covered: Yellow sea, North Indian Ocean


Description: Surge forecast from Operational DMI HRB model for Yellow Sea

Surge forecast from NOC Surge model for North Indian Oceam

Source Data: DMI Surge forecast for Yellow Sea

NOC Surge forecast for North Indian Ocean


Reprocessing: Yes


Expected accuracy: TBD

Expected Resolution: 5km for Yellow Sea

TBD km for North Indian Ocean

Product: NRT7 NRT Surge Forecast

Provider: DMI, NOC

Areas of Interest covered: North sea, Baltic sea


Description: Surge forecast from Operational DMI HRB model

Surge forecast from NOC Surge model

Source Data: DMI Surge forecast

NOC Surge forecast


Reprocessing: Yes


Expected accuracy: TBD


Data set NRT8 has been removed.

Product: NRT9 NRT Coastal altimetry

Provider: NOC




8 December 2011

/ 102


Product: NRT9 NRT Coastal altimetry

Description: FDMAR coastal altimetry data from Envisat and Cryosat (plus Jason-2 if NRT waveforms are available through ESA)

Reprocessed coastal altimetry data from NRT Envisat and Cryosat waveforms

(plus Jason-2 if NRT waveforms are available through ESA)

Source Data: Envisat and Cryosat FDMAR from ESA

Jason-2 NRT waveforms if available through ESA

Source Data Format Envisat and Cryosat FDMAR: ESA custom (binary)

Jason-2 NRT: TBC

Reprocessing: NRT hi-rate waveforms are retracked with suite of specialized retrackers. “Best” estimates of range (based on goodness of fit) are selected and output. Corrections to range are recomputed with techniques optimized for the coastal strip.

Source of Error Information: NOC will provide variance of estimation from waveform fitting

Expected accuracy: 10 cm at 10 km from coast, 20 cm at 3 km from coast (single 20-Hz measurements)


Product: NRT10 NRT Infrared data from geostationary satellites for storm tracking purposes

Provider: NOC



Description: Infrared imagery for storm tracking from Meteosat/MVIRI and MSG/SEVIRI, covering Atlantic and Indian Ocean

Source Data: EUMETSAT HRI-IODC and HRSEVIRI (HRI Level 1.5 Image Data)

Source Data Format Binary image data

Reprocessing: N/A

Source of Error Information: N/A

Expected accuracy: N/A

Expected Resolution: TBC

C.11 Additional Products

Product: BA1 Bathymetry

Provider: NOC (via GEBCO/BODC)


Estimated number of events: TDS: N/A FPDS: N/A

Description: GEBCO_08 bathymetry is a deep ocean product, and does not include detailed bathymetry for shallow shelf waters. The bathymetric data are an interpretation based on random tracklines form many different sources. (From GEBCO disclaimer) References to the WGS-84 datum)

Source Data: GEBCO_08 global 30 arcsec

Regional bathymetry at higher resolution may be available e.g. via http://portal.emodnet-hydrography.eu/EmodnetPortal/

Source Data Format NetCDT

Reprocessing: N/A

Source of Error Information: NOC, by comparison with further public or unreleased data sets

Expected accuracy: GEBCO_08: Variable

http://portal.emodnet-hydrography.eu/EmodnetPortal/



/ 102

Product: BA1 Bathymetry

Expected Resolution: 30 arcsec or better if available

Product: DM1 Digital Elevation Models

Provider: NOC


Estimated number of events: TDS: N/A FPDS: N/A

Description: DEM data applicable to each AOI.

ACES global 30 arcsec DEM (regional DEM at higher resolution where available)




Source of Error Information: To be provided.



Product: FM1 Flood maps

Provider: CMRC, NOC

Areas of Interest covered: TBC5


Description: Inundation extent datasets, showing flood presence/absence per pixel, shall be provided to accompany a maximum of 25 SEVs in the FPDS. Five of these will be available for SEVs in the TDS, and up to 20 more made available for SEVs in the FPDS. These shall be available for comparison with model prediction outputs.

In the absence of existing post-event flood extent datasets and flood maps from sources both within and outside the eSurge consortium, satellite imagery (both multi-spectral and Synthetic Aperture Radar) will be utilised in a limited number of cases to derive a coastal inundation map from a time as close as possible following the actual event.

5 For the TDS, 5 flood maps will be derived corresponding to 5 surge events in the TDS. 20

more will be added for the FPS. The AOIs into which these SEVs fall is to be determined.


8 December 2011

/ 102


Product: FM1 Flood maps

Source Data: 1) Flood extent datasets which are already GIS compatible (in both vector or raster format)

potential sources :

government agencies

international crisis organisations (e.g. OCHA, UNOSAT)

disaster relief agency records

2) Flood extent maps which can be converted into a GIS compatible format

potential sources :

government agencies

international crisis organisations

disaster relief agency records

3) Flood extent datasets derived from satellite imagery

sources :

ESA and third party products

Optical (e.g. SPOT 4 & 5 imagery, MERIS multispectral imagery, MODIS multispectral imagery),

SAR Products (e.g. ENVISAT SAR Imagery)

Source Data Format Vector (e.g. shp) and/or raster (e.g. GeoTIFF), or images (e.g. jpg)

Reprocessing: 1) Flood extent datasets which are already GIS compatible

Datasets will be reprocessed into a format compatible with model outputs, using standard GIS vector/raster conversion techniques.

2) Flood extent maps which can be converted into a GIS compatible format

Flood extent datasets will be derived from flood extent maps, and will be reprocessed into a format compatible with model outputs, using standard GIS vector/raster conversion techniques.

3) Flood extent datasets derived from satellite imagery

Optical, or SAR imagery will be classified into “inundated” and “non inundated” areas. These will form the basis of the flood extent dataset which will be converted into a format compatible with model outputs using standard GIS raster conversion techniques.

Source of Error Information: Processing of optical and SAR data to delineate flood extents will include error statistics in regard to spatial accuracy and also standard estimates of classification accuracy. Processed data representing flood extent from 3

rd parties will be

reported with any associated error statistics, but no additional error analysis will be carried out.

Expected accuracy: Spatial accuracy - Dependant on the spatial resolution of the source dataset. Processed data representing flood extent from 3

rd parties will be reported with

any associated error statistics, but no additional error analysis will be carried out.

Thematic accuracy - Target thematic accuracy is 80% for thematic flood extent datasets derived from optical or SAR imagery. Processed data representing flood extent from 3

rd parties will be reported with any associated error statistics, but no

additional error analysis will be carried out.

Expected Resolution: Between 20m and 1km spatial resolution, dependant on the resolution of the source data and model output requirements.



/ 102

ANNEX D SEVS UNDER CONSIDERATION FOR INCLUSION IN SEARS

Table D-1 below shows the list of serge events (SEVs) currently being considered for inclusion in SEARS. See section 3.3.2 for discussion of the criteria which have been used to create this list. At the moment this list is incomplete, as it does not have sufficient SEVs to meet requirement eSurge-RB-REQ-020. Section 3.3.3 describes how this list will be completed.

Table D-2 lists additional SEVS in non-core AOI which have been identified by users. Data for these SEVs will be provided if practical.

These SEVs have not yet been assigned identifiers; these will be assigned once the list is closer to completion.

Table D-1: Surge Events (SEVs) currently identified

AOI Location Date Notes Reason for inclusion

AOI-10 /AOI-50

North/Baltic Seas.

28/01/2002 Westerly storm Identified by DMI as suitable for reanalysis.

AOI-10 /AOI-50

North/Baltic Seas.

21/02/2002 Easterly storm Identified by DMI as suitable for reanalysis.

AOI-10 /AOI-50

North/Baltic Seas.

06/12/2003 Northerly storm Identified by DMI as suitable for reanalysis.

AOI-10 /AOI-50

North/Baltic Seas.

20/03/2004 Westerly storm Identified by DMI as suitable for reanalysis.

AOI-10 /AOI-50

North/Baltic Seas.

08/01/2005 Westerly hurricane. A new high water record in the Limfjord

Identified by DMI as suitable for reanalysis.

AOI-10 /AOI-50

North/Baltic Seas.

01/11/2006 Northerly storm. A new high water record in Odense, 100-year event in the Great Belt, Southern Kattegat and a few other locations

Identified by DMI as suitable for reanalysis and in Deltares-KNMIstormlist (see description)

AOI-30 Dublin 01/02/2002 Identified by users (Met Éireann and UCD)

AOI-20 SE coast of Ireland

27/10/2004 - 29/10/2004

Identified by user (Met Éireann)

AOI-20 NE Atlantic, Irish coast

03/12/2005 -15/12/2005

Identified by user (Met Éireann)

AOI-20 NE Atlantic, Irish coast

01/01/2005 -15/01/2005

Idenitifed by user (NUIG, Ireland)

AOI-80 North Indian Ocean

May 1999 Tropical cyclone 02A Identified by user (PMD, Pakistan)


May 2001 Tropical cyclone 01A Identified by user (PMD, Pakistan)


June 2007 Tropical cyclone Yemyin Identified by user (PMD, Pakistan)


June 2010 Tropical cyclone Phet Identified by user (PMD, Pakistan)

http://www.knmi.nl/samenw/hydra/stormcatalogus/Cases/04_01-11-2006/Samenvatting/samenvatting.html


8 December 2011

/ 102




June 1964 Tropical cyclone (Unnamed)

Identified by user (PMD, Pakistan). Note: Outside nominal time range.


May 1985 Tropical cyclone (Unnamed)

Identified by user (PMD, Pakistan)

Outside time range?

AOI-40 Northern Adriatic

December 2008 Identified by user (ICNR-ISAC)

AOI-40 Northern Adriatic

24-25 Dec 2009 Identified by user (ICNR-ISAC)

AOI-20 Bay of Biscay 27-28 Feb 2010 Xynthia Identified by user (Meteo France)

AOI-20 Iroise Sea 9-11 March 2008 Johanna Identified by user (Meteo France)

AOI-70 NW Mediterranean

18-20 Feb 2010 Identified by user (Meteo France)

AOI-60 Western Black Sea

March 2010 Identified by user (Bulgarian Institute of Oceanography)

AOI-10 North Sea 11/10/2010 Identified by user (RWS Zeeland, NL)

AOI-10 North Sea 09/11/2007 NW storm, highest surge along the Dutch coast since 1953 see description

Identified by user (Hans de Vries KNMI) and in Deltares/KNMI stormlist

AOI-10 North Sea 4/02/2011 External surge, generated by storm West of Scotland

Identified by user (Hans de Vries) as intersting test case for data assimilation on the North Sea

A01-10 North Sea 18-1-2007 Triple storm in top 3 wind events (see description)

In Deltares/KNMI stormlist

A01-10 North Sea 27/10/2002 Rapid displacing storm low (see description)


A01-10 North Sea 28/05/2000 “Kanaalrat” small rapid developing low (see description)


A01-10 North Sea 19/02/1996 Rapid changing winter flow (see description)


A01-10 North Sea 28/01/1994 in top 3 hydraulic events (see description)

in Deltares/KNMI stormlist

A01-10 North Sea 14/11/1993 significant swell event, in top 3 in hydraulic events (see

description)

in Deltares/KNMI stormlist















/ 102

Table D-2: Additional Surge Events (SEVs) in non-core AOI


AOI-120 Texas, USA 13/09/2008 Hurricane Ike Identified by user (NOAA)

AOI-120 Louisiana, USA 29/08/2005 Hurricane Katrina Identified by user (NOAA)

AOI-130 NW Pacific 4/9/2003 -16/09/2003

Typhoon Maemi Identified by user (KMA, Korea)

AOI-130 NW Pacific 22/8/2002 – 03/9/2002

Typhoon Rusa Identified by user (KMA, Korea)

AOI-130 NW Pacific 29/6/2006 – 12/7/2002

Typhoon Ewinar Identified by user (KMA, Korea)

AOI-130 NW Pacific 6-19 July 2007 Typhoon Busan Identified by user (Pukyong University, Korea)

Outside current AOI

Argentinean coast

1-3 Sept 2010 Identified by user (NHS, Argentine)

AOI-110 Queensland 1-4/02/2011 Identified by user (BMD, Australia)



<End of Document>

Company Address

Logica UK Ltd.

Keats House

The Office Park

Springfield Drive

Leatherhead

Surrey

KT22 7LP

Contact person:

Phillip Harwood

eSurge Project Manager

P: +44 (0) 1372 759793

E: [email protected]

www.logica.com

http://www.logica.com/