atlantos societal benefits from observing/information ...milestone title: first technical meeting of...
TRANSCRIPT
1
Project: AtlantOS – 633211
Work Package number: WP8
Work Package title: Societal benefits from observing/information systems
Milestone number: MS1
Milestone title: First Technical meeting of WP8
Description: First Technical meeting of WP8 to assess status of input data to, and design of, specific application products.
Related Work Packages:
Inflow: WP1 , WP6 & WP7
Outflow: WP1, WP2, WP3, WP4, WP9, WP10
Lead beneficiary: UniBO
Lead authors: Nadia Pinardi, Caroline Cusack & Augusto Sepp Neves
Contributors: All partners
Submitted by: Nadia Pinardi
Total number pages: 53
Dissemination Level: Public
A project funded by H2020
This project has received funding from the European Union’s Horizon 2020 Research and Innovation Programme under Grant Agreement No 633211 www.atlantos-h2020.eu
2
DOCUMENT FORM
DISSEMINATION LEVEL
DISTRIBUTION
PU PP RE CO Public
TITLE
First Technical meeting of WP8
OVERVIEW This document lists the outcomes of the First Technical WP8 meeting in relation to
1) The overall working strategy of WP8 2) The product specification template 3) The fitness for purpose assessment strategy 4) The definition of the stakeholder consultation strategy and the exchange between
WPs
TASK LEADER:
Laboratorio SINCEM Laboratori R.Sartori University of Bologna Via S.Alberto 163 48123 Ravenna, ITALY Web: wwww.sincem.unibo.it Email: [email protected]
AUTHOR(S): N. Pinardi1, C. Cusack2, A. A. Sepp Neves 1, T. Dabrowski2, J. Maguire3, M. Shorten3, F. Martins4, J. Janeiro4, T. Dale5, M. Ruiz6, J. Tinker7, P. Lehodey8, G. Mannarini9, C. Cesarini10
, K. J. Horsburgh11, R. Fernandes12
1
University of Bologna, Via S.Alberto 163, 48123 Ravenna, ITALY (UniBO) 2
Marine Institute, Rinville, Oranmore, Co. Galway, IRELAND (MI) 3
Daithi O'Murchu Marine Research Station, Cork, IRELAND (DOMMRC) 4
University of Algarve, Estrada da Penha, 8005-139 Faro, PORTUGAL (UALG) 5
Norwegian Institute for Water Research, Gaustadalléen 21, NO-0349, Oslo, NORWAY (NIVA)
6 Instituto Español de Oceanografía, Centro Oceanografico da Coruna, Muelle de Animas s/n, 15001 A Coruna, SPAIN (IEO)
7 Met Office, UK, FitzRoy Road, Exeter, Devon, EX1 3PB, UNITED KINGDOM (METO)
8 CLIOTOP SSC. Ex-officio, Collecte Localisation Satellite, FRANCE (CLS)
9 Centro Euro-Mediterraneo sui Cambiamenti Climatici, via Augusto Imperatore 16, I-73100 Lecce, ITLALY (CMCC)
10 CLU Ltd, Via Togliatti 17/c,41013 Castelfranco Emilia (MO), ITALY (CLU)
11 Marine Physics and Ocean Climate research group, Liverpool, National Oceanographic Centre, Natural Environment Research Council,, UK (NERC)
12 ActionModulers, PORTUGAL
DATE: 31 March 2016
3
Document Log
Date Author Changes Version Status
17/02/2016 Pinardi First Version V0 draft
18/03/2016 Sepp-Neves &
Cusack
Second Version V1 draft
21/03/2016 Pinardi Third Version V2 draft
29/03/2016 Mannarini Added Reference section + changes
in Task 8.3’s presentation
V3 draft
30/03/2016 Pinardi, Sepp Neves & Cusack
Added requested changes
V4 draft
4
Table of Contents ACRONYMS....................................................................................................................................... 5 GLOSSARY ........................................................................................................................................ 6 Executive Summary .......................................................................................................................... 8
General scope of the document .................................................................................................... 10 1. Overall aims of WP8 ................................................................................................................... 11
2. Presentations during the meeting ............................................................................................ 15 3. Meeting outcome # 1: overall working strategy ...................................................................... 19
4. Meeting outcome # 2: the product specification template .................................................... 20 5. Meeting outcome # 3: fitness for purpose assessment strategy ......................................... 22
6. Meeting outcome # 4: the definition of the stakeholder consultation strategy and the exchange between WPs ................................................................................................................ 24
References ....................................................................................................................................... 28
Annex A WP8 technical meeting agenda .................................................................................... 29
Annex B WP8 Tasks in the DoW of the Grant Agreement ....................................................... 32
Annex C Use Case Product Specification Document .............................................................. 38
Glossary ........................................................................................................................................ 41 Executive Summary .................................................................................................................... 42
General scope of the document ................................................................................................ 43
General scope of the Use Case ................................................................................................ 44
User requirement identifications ............................................................................................... 45
Target Users for the Use Case ................................................................................................. 45 Literature review of user needs ................................................................................................. 45
Targeted Product description .................................................................................................... 46 Use Case Targeted product specifications ............................................................................. 47
Description of input characteristics and data sources needed by Targeted products ...... 48
Description of methodology to produce the Targeted Products .......................................... 49
Targeted product # ...................................................................................................................... 49
Implementation Risk Table ........................................................................................................ 50 Identification of AtlantOS impacts ............................................................................................. 51
Annex 1 Nomenclature ............................................................................................................... 52
5
ACRONYMS
BOOS Baltic Operational Oceanographic System;
CMEMS MCS Copernicus Marine Environmental Monitoring Service (DG Growth) Marine Core Service
EEA European Environmental Agency
EMODnet European Marine Observation and Data network (DG Mare) with discipline based themes, an EU programme to support the further development of an Integrated Maritime Policy (Reg. EU 1255/2011)
EOV Essential Ocean Variable
EuroGOOS European Global Ocean Observing System
GEOSS Global Earth Observations System of Systems
GOOS Global Ocean Observing System
HABs Harmful Algal Blooms
IBIROOS Iberian-Biscay-Irish Regional Operational Oceanographic System
ISO International Organization for Standardization
MONGOOS Mediterranean Operational Network for the Global Ocean Observing System
MS Member States
NODC National Oceanographic Data Centres
NOOS North West Shelf Operational Oceanographic System
SeaDataNet pan-European infrastructure for Ocean and Marine data management (DG Research & Innovation)
WISE marine Water information System for Europe (DG Environment, European Environment Agency, Joint Research Centre and Eurostat
6
GLOSSARY
Name Meaning
Characteristic In this document, a “characteristic” is a distinguishing feature which refers to:
1. either to a variable derived from the observation, the measurement or the numerical model output of a phenomenon or of an object property in the environment
2. the geographical representation of an object on a map (i.e. a layer such as a protected area, a coastline or wrecks) by a set of vectors (polygon, curve, point) or a raster (a spatial data model that defines space as an array of equally sized cells such as a grid or an image).
Data Adequacy Report Report on the ability ‘sufficient to satisfy a requirement or meet a need’ of the end-users by the targeted-products.
EMODnet CHECKPOINTs for regional seas
Methodology to evaluate the quality of the data from current monitoring systems in terms of their accessibility, availability, multiple-use, efficiency, reliability, time consistency, space consistency, as well as the planning of technological advancements, new accessibility, new assembly protocols and observational priorities.
Environmental matrices This concept is introduced to avoid ambiguities when using a characteristic name such as “temperature”. The environment matrix is the environment to which a characteristic is related and we define them to be:
1. Air 2. Marine Waters 3. Fresh Waters 4. Biota/Biology 5. Seabed/Riverbed 6. Human Activities
Fitness for Purpose Rationale for creating a dataset
Fitness for Use Rationale for selecting the dataset
Indicator Measures that relate actual performance (results achieved) to the desired or aimed-at objectives
7
Quality principles
Completeness Degree of absence of data in a dataset
Logical consistency Degree of adherence to format required
Spatial accuracy Requested closeness of coordinate values to values accepted as or being true e.g. on the base of instrumentation used
Spatial extent Box or geographic region bounding the datasets
Spatial resolution Size of the smallest object that can be resolved on the ground. In a raster dataset, the resolution is limited by the cell size.
Thematic accuracy Requested closeness of characteristic values to values accepted as or being true (the so called attribute of a data entity eg "wave height"). It includes the correctness of the classification of features or of their associations...
Time accuracy Requested closeness of temporal values to values accepted as or being true.
Time extent Time interval represented by the dataset or by the collection.
Time resolution Size of the smallest interval of time that can be resolved
Usability The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.
Name Meaning
Product specification Describes the rationale for creating a dataset
Product/Service SOLUTION to an end-Users PROBLEM
Use Case / Pilot Action Synonymous of AtlantOS Task
Use Case Product Targeted Product
Value adding chain Cost effective end-to-end data delivery with maximum use for societal benefit
8
Executive Summary
The first meeting of the AtlantOS Workpackage 8 “Societal Benefits from
observing/information systems” was held at the University of Bologna in Ravenna (IT)
between 18 and 20 of January 2016. The meeting aims were to:
raise awareness of the AtlantOS overall strategy and its connection to WP8 work;
define and harmonise the working practices between the participants;
discuss the assessment criteria for the end-user products.
The meeting achieved all its aims and the conclusions are reported in this document.
First of all the overall general strategy for value-added, user-driven products was
elucidated and discussed among the partners. It was recognised that the reference
European framework where the monitoring assessment is carried out on the basis of end-
user products is EMODnet Checkpoints and the partnership decided to follow the Standard
Operating Practises that will emerge from these groups. The value adding chain from
observations to end-user products is long and requires traceability of the processes used
to develop the products and to devise careful assessment criteria that are already being
developed by EMODnet.
In order to align as much as possible with the EMODnet principles, the partners decided to
adopt ISO principles for product quality assessment. The work starts with the definition of
the inputs, data sets and the user requirements for each Pilot Action and ends with the
application of assessment criteria to the products (fitness for purpose indicators) and to the
input data sets (fitness for use). The main result of the discussion was the definition of a
standard Use Case Product Specification Document (Annex C) that will be completed in
April 2016 and then updated regularly to contain the description of the products, the input
data sets and the methodology to produce them in addition to the description of the
potential impacts.
9
Finally the meeting examined the general principles of the Data Adequacy Reporting that
is one of the important Deliverables of the Workpackage: it assesses the adequacy of the
input data sets, including AtlantOS in-situ data, by relating them to the quality of the 7 Use-
Case products developed in the project that are: 1) HABs mapping, 2) storm surge coastal
hazard mapping, 3) safe ship routing, 4) oil spill hazard mapping, 5) MSFD reporting
(Marine Strategy Framework Directive), 6) site selection for offshore mariculture, and 7)
forecast of North Atlantic albacore tuna populations. Again, in this case, AtlantOS will
develop innovative products and will use the assessment criteria defined in EMODnet.
10
General scope of the document
This Report overviews the outcomes of the first technical meeting of WP8. The aim was to
assess status of input data to, and design of, specific application products. The Report is
structured around four main topics:
1. The consolidation of the overall aims of WP8;
2. The structuring of product specifications;
3. The fitness for purpose assessment;
4. The definition of the stakeholder consultation strategy and the exchange
between WPs.
The general schedule of the meeting is given in Annex A, together with the Participant List.
11
1. Overall aims of WP8
The overall intention of this Work Package is to provide new information products in
several GEOSS societal benefit areas (i.e. climate, disasters, ecosystems, health and
fresh water, increased safety for offshore activities and coastal communities).
The ambition is to deliver a suite of products that are targeted at issues of societal concern
in European Member States. These products will enhance the safety of coastal
communities and promote economic development in key emerging marine and maritime
sectors through better decision support tools for Disaster Risk Reduction (flooding,
maritime safety, HAB) and resource assessment (offshore aquaculture, fisheries).
Reanalysis products will assist Member States in reporting under the MSFD and to
international entities such as ICES.
Integration of marine data from combined sources for end-user products has been a
challenge within the marine and maritime communities for several decades. The WP8 pilot
cases or actions will be tangible outputs from the integration of Earth observation, in-situ
data systems and model analyses, reanalysis and forecasts to form usable products for
the above-mentioned areas of societal benefit. These end-user focused products can also
be seen as a contribution to the EMODnet Atlantic Checkpoint Portal in terms of
development of the algorithms and basic tools to evaluate fitness for purpose of the
monitoring system.
Overarching measurable WP8 objectives are to:
provide leadership for Europe in the implementation of GEOSS in the Atlantic in
several areas of societal benefits
integrate data from the Copernicus Marine Service (DG Growth) and EMODnet
(DG Mare) in the Atlantic basin, augmented by new AtlantOS data (DG RTD), to
produce the information products for HABs mapping, storm surge coastal hazard
mapping, safe ship routing, oil spill hazard mapping, MSFD reporting (Marine
Strategy Framework Directive), site selection for mariculture, and forecast of North
Atlantic albacore tuna populations.
12
produce a Data Adequacy Report from each different Pilot Action documenting
the observational and model data accuracy, accessibility and fitness for
purpose of the products as well as the fitness for use of the data
The Pilot Actions are described in Annex B and the WP8 general structure of the work to
be carried out is summarised in Fig. 1.1
Fig. 1.1. WP8 Overview of the seven Pilot actions / end-use cases to be addressed in
AtlantOS
The general strategy for the marine data value adding chain in Europe at the time of
writing is schematised in Figure 1.1. This chain will contain and will probably provide more
interoperable services, but, at this time this is the high level representation of how to
generate products out of observations. It is expected that the Data Adequacy Report from
WP8 will trigger a more responsive data supply chain to provide the essetial information
required to enhance the quality of end-user products and services.
EU leadership in the implementation of GEOSS in the Atlantic
GEO/GEOSS Five societal benefits areas: climate, disasters, ecosystems, health & water
Fitness for use
of input
monitoring data
Fitness for purpose
of products
Data
Adequacy
reports
HABs
8.1
mapping
Oil
Spill
8.4
hazard
mapping
8.3
Ship
Routing
safety & cost
MSFD / ICES
RAN
8.6
reporting
Offshore
Aquaculture
8.5
site selection
Tuna
8.7
distributions
Coastal
Flooding
8.2
climatology
Decision Support Tools Resource
Assessment
MSFD
indicators
Resource
Assessment
Pilot Actions
Products &
ServicesBulletins
Dynamic
Maps
End
products
Tools for
users
Assessments
13
As in meteorology, the value adding chain is long, starting with essential satellite and in-
situ observations to practical products for societal benefit. AtlantOS will contribute in three
ways to the production system:
1) Coordinate new observing systems in the Atlantic;
2) Demonstrate the impact of such observations in monitoring and forecasting systems
of the Atlantic ocean at different scales;
3) Develop advanced user-oriented products from the observations and model
outputs.
In Europe, two major programmes provide marine data derived products that are of
relevance to AtlantOS:
1) CMEMS which in addition to core products (generic information) produces a
Climate Report and several ad-hoc products for EEA;
2) EMODnet CHECKPOINTS that develop applications and assessments of fitness for
use of input data sets and fitness for purpose of products.
WP8 legacy should flow into, and benefit from the progress already made in the EMODnet
CHECKPOINTS.
Societal issues can be complex and only resolved by the use of data from multiple
disciplines and streams. Therefore, WP8 will indirectly use observed EOVs (see GOOS,
http://ioc-goos-oopc.org/obs/ecv.php). For example, WP8 will use "value-added" derived
observation input data sets offered by CMEMS. WP8 will also consider data related to
human activities at sea (e.g. ship routes). This follows the EMODnet approach with
"characteristic" used to describe input data types. For the majority of WP8 use-cases, the
assessment of AtlantOS societal benefits will be addressed using value added products
from the Atlantic observing system. WP1 and WP8 are closely linked with WP1 developing
the high level EOV requirements. WP1 will also assess the degree of coverage and
accuracy required for each EOV in the observing system i.e. analyses, reconstructions,
reanalyses and forecasts.
14
EuroGOOS = European Global Ocean Observing System, IBIROOS = Iberian-Biscay-Irish Regional Operational Oceanographic System, MONGOOS = Mediterranean Operational Network for the Global Ocean Observing System; NOOS = North West Shelf Operational Oceanographic System; BOOS = Baltic Operational Oceanographic System; GOOS = Global Ocean Observing System; MS = Member States; SeaDatanet = pan-European infrastructure for Ocean and Marine data management (DG Research & Innovation), EMODnet = European Marine Observation and Data network (DG Mare), WISE marine = Water information System for Europe (DG Environment, European Environment Agency, Joint Research Centre and Eurostat), CMEMS = Copernicus Marine Environmental Monitoring Service (DG Growth), MCS = Marine Core Service,.
Fig. 1.2 Value adding chain in Europe: from observations to products of societal benefit.
Copernicus
Satellite Systems
EuroGOOS
IBIROOS
Argo
MONGOOS
NOOS
BOOS
Artic GOOS
Black Sea GOOS
Ocean Sites
MS in-situ networks
SeaDataNet
EMODnet
WISE marine
GO-SHIP
ICES fishery services
Information: Value Adding Knowledge Chain
Input Generic
Downstream
Services
User Customised
Products &
Services
Services
CMEMS MCS
SeaDataNet
EMODnet
1 = Global2 = Artic3 = Baltic
4 = NWS5 = IBI
6 = Med Sea7 = Black Sea
Data
Providers
Intermediate
Data Providers & Users
Downstream
Providers & Users
Societal
benefit
European “Standard” Framework to generate products out of observations
WP8
15
2. Presentations during the meeting The technical meeting started with an introductory talk by Nadia Pinardi (UNIBO) on “what AtlantOS actually stands for”, “where AtlantOS fits in the European landscape” and “where the WP8 fits into AtlantOS”. As clarified by Nadia, stakeholder engagement will play a major role in WP8. Julie Maguire (DOMMRS) presented her group experience in contacting and engaging with stakeholders in research projects and gave some advice on how to connect with and encourage stakeholders to collaborate and share their knowledge / needs. Methodologies on stakeholder engagement strategies were presented to the group and discussions held on how to implement these techniques taking the WP budget into consideration.
The theoretical background and previous experiences of use case #1, “Harmful Algal Blooms” were presented by Caroline Cusack (MI), Manuel Ruiz (IEO) and Trine Dale (NIVA). The three institutions have experience in the field, in national and international research projects and have established connections with the end users, especially in the MI case. The HAB monitoring system of each institution was presented, demonstrating how remote sensing, in-situ sampling, ocean and biogeochemical modelling can be used to generate operational bulletins to the end users.
16
Gianandrea Manarini (CMCC), responsible for the use case #3 “ship routing hazard mapping”, presented the latest results obtained with VISIR, the ship routing algorithm developed by CMCC. The algorithm defines the shortest and safest route based on meteo-oceanographic variables [Mannarini, 2015]. Gianandrea discussed a list of changes and new functionalities that need to be developed in order for VISIR to be applied to the Atlantic ocean. Regarding the stakeholders engagement, target users categories were listed, together with a few commercial ship routing products.
Use case #4 “Oil spill hazard mapping and disaster risk reduction best practices” was presented by Flavio Martins (Ualg) and Augusto Neves (UNIBO). The task group presented past experience in the field which include participation in international projects, development of an oil spill emergency web platform and assessments of the oil spill risk. The group plans to contact prospective end users in the near future.
According to the presentation of use case #5 “Offshore aquaculture siting”, delivered by Trine, Caroline and Manuel, offshore aquaculture is a concept “under development” and, as expected, there is still little information and experience in the field. An offshore
17
aquaculture site “selector” prototype has been developed by the MI using meteo-oceanographic data and good communication with prospective end-users has been established. A NIVA prototype was shown by Trine but does not ingest meteo-oceanographic information. According to Manuel, there is no offshore aquaculture in Spain at the moment.
Johnathan Tinker (UK Met Office) presented the use case #6 “Reanalyses for Marine Strategy Framework Directive and ICES assessments”. The UK Met Office has extensive experience in operational ensemble ocean modelling and data assimilation techniques. They expect that, in AtlantOS, they will be able to solve, at least partially, issues that make sampled data unappropriated for assimilation. They also expect to increase and improve methods to assimilate in-situ operational data into the global ocean circulation model. This should improve the quality of regional forecasts and, therefore, indicators used in the MSFD and ICES assessments.
18
Patrick Lehodey closed the technical sessions with use case #7 “Operational real-time and forecast modeling of North Atlantic albacore tuna populations”. Patrick demonstrated the strong experience they have in the field of fish population dynamics modeling with SEAPODYM. In the scope of AtlantOS, Patrick’s team is working on the implementation of an operational albacore model. Key stakeholders have been identified and contacted by Patrick.
Rodrigo Fernandes (ActionModulers, Portugal) joined our meeting as an AtlantOS member delivering a presentation on the latest achievements of his team. Within the scope of the WP8, the consortium ActionModulers and MARETEC (Insituto Superior Tecnico, Lisbon) has been actively working in the oil spill risk field mainly through the ARCOPOL project series, developing a tool for dynamic risk analysis. ActionModulers is now part of the +Atlantic, an EU-funded project aimed on gathering international efforts to monitor the Southern Atlantic.
19
3. Meeting outcome # 1: overall working strategy The meeting defined some strategic lines of development for the different Pilot Actions,
hereafter called “Use-cases”.
First a nomenclature was defined that reads as follows:
1. Use-case products can be called “Targeted products”
2. Targeted products are built from “input data sets” that are related to “characteristics”
(not simply state variables! / essential ocean variables)
Characteristics are:
a. either a variable derived from the observation, the measurement or the
numerical model output of a phenomenon or an object property in the
environment
or
b. the geographical representation of an object on a map (i.e. a layer such as a
protected area, a coastline or shipwreck) by a set of vectors (polygon, curve,
point) or a raster (a spatial data model that defines space as an array of
equally sized cells such as a grid or an image)
(from EMODnet Mediterranean Sea Checkpoint Literature Survey, see
http://www.emodnet-mediterranean.eu/reports_news/)
Each Use Case will follow this working procedure:
1. Describe the “targeted products” and their specifications (ISO standards)
2. Produce the “targeted products” and engage stakeholders
3. Produce a Data Adequacy Report following the EMODnet Checkpoint guidelines
4. Feed to WP1 and WP10 the outcomes
20
4. Meeting outcome # 2: the product specification template Following the work done in Mediterranean EMODnet Checkpoint, we decided to
standardise the Use Case Products (Targeted Products). Following ISO 19157 standards
(see Fig. 4.1) we first need to define “product specifications” or “user requirements”
together with the input datasets required. Since our products have been selected on the
basis of user requirements given in other projects, we now concentrate on “product
specifications”. This will allow us to define quality elements to assess the fitness for
purpose of the products and the fitness for use of the used datasets.
Fig. 4.1 Data product specification (ISO 19131).
21
To this end, we have decided to write a Use Case document for each targeted product
containing the following information:
Table 4.1 Table of content of a Use Case Product Specification Document
This will be a live document and regularly updated throughout the project. A commented
version of this document is presented in Annex C.
22
5. Meeting outcome # 3: fitness for purpose assessment strategy The EMODnet Checkpoints (http://www.emodnet.eu/) are defining a strategy for the
assessment of basin scale monitoring systems based on targeted products.
The EMODnet strategy adapted to AtlantOS is shown in Fig 5.1. Starting from the
Targeted products and the input data sets used for their production, product quality
elements will be evaluated by defining quality indicators and reporting them in a “Data
Adequacy Report”.
Fig. 5.1 The overall EMODnet Checkpoint Methodology
As listed in Fig. 4.1 the process goes through three different steps:
1) identify an applicable data quality element, data quality sub element;
2) identify a data quality measure;
3) Select and apply a data quality evaluation method.
The EMODnet “Mediterranean Checkpoint” is at a more advanced stage of development
and has already identified the applicable quality elements (listed in Table 5.1). The
EMODnet Mediterranean Checkpoint is now in the process of identifying the quality
measures and the full methodology. It is proposed that these EMODnet Sandard
Operating Procedures (SOPs) are adopted in AtlantOS.
Inadequate
Partially Adequate
Totally Adequate
WP8
Use Cases
Data
Adequacy
Report
Data Collection[Assembly Programmes]
Checkpoint
Indicators
1
2
3
Not relevant4
* Global Monitoring for Environment and Security ** European Marine Observation and Data Network Thematic Assembly Group
• (GMES*)
• TAGs**
• Fisheries Data Collection Framework
• National Databases
•
• HABs
• Coastal Flooding
• Ship Routing
• Oil Spill / Hazards
• Tuna Fishing
• Marine
Environment
• Mariculture Sites 1 = red, 2 = yellow, 3 = green
23
Table 5.1 EMODnet Quality elements used to evaluate fitness for purpose and use
24
6. Meeting outcome # 4: the definition of the stakeholder consultation strategy and the exchange between WPs In order to maximise the available budget, which is relatively-small in the context of user
requirements gathering work, a decision was taken to carry out a series of semi-structured
Interviews.
Semi-structured interviewing is a well-established research modality in the humanities and
social sciences, and DOMMRS has experience in implementing this methodology in other
EO-related research projects (e.g. SAFI, under FP7, and C-TEP, under ESA). The
advantages of this approach include not overly constraining the interviewees’ ideas, while
simultaneously giving enough structure to allow meaningful comparison of results between
subjects (for an overview of the semi-structured interview methodology see: Fylan, 2005).
The proposed idea is to engage workers to carry out such semi-structure interviews at a
number of large meetings/conferences where the attendance represents interested user
groups of the WP8 outputs, in order that there is a maximal return on time and resource
expenditure in carrying out the work. In order to minimise such costs, the suggestion was
made to recruit a number of student/postgraduate students to carry out relatively brief (to
encourage participation), semi-structured interviews of attendees at such events.
Examples (non-exhaustive list) of such events include:
EO observation research conferences
Events for relevant governmental/regulatory authorities
Industry Events (e.g. shipping, aquaculture, etc.)
There are a number of goals to this work, including:
To establish the weight of importance that potential users attach to each aspect of
AtlantOS’s research under WP8. This is in order that the correct emphasis (i.e.
user-driven) is achieved at an early stage in the project’s work.
To address any imbalances in user data availability across each country covered by
WP8
25
To discover if there are other, specific data across the topics under study in WP8,
which would be beneficial to end users of the results of WP8.
A ‘topic guide’ to guide the interview:
DOMMRS are experienced in drafting such a guide, and can do so in collaboration with
other WP8 partners. This topic guide provides a practical map for topics and themes to be
covered in the interview. It:
Has a flexible, responsive ‘structure’
Allows interviewers to formulate questions
Is a ‘public document’ which can be used to provide transparency
A Quiet Area
In order to:
Minimise Interruptions (to make environment more conducive to interview)
Minimise other people present during interview
DOMMRS will proceed to draft an outline Topic Guide if the general approach outlined
above is accepted.
26
Regarding the exchange between AtlantOS WPs, we identified the following “flows” with WP8:
Outflow:
WP 1 Two major communication channels were identified between WPs 1 and 8.
Past experiences have shown that end-user products can help identifying
major issues in the raw input data due to the fact that scientific data (e.g.
temperature profiles, significant wave height) are translated into variables
that we can easily observe, measure and compare to our past experiences
(e.g. fish catches, number of surfing days/year). Additionally, we expect
WP8 to bridge end-user requirements and data acquisition, orienting the
AtlantOS sampling towards effective measurements capable of generating
significant improvements in the targeted products.
WP 2,3 indirectly, the purpose is to test the adequacy of the system to provide that
data that can be used for product generation. If serious shortcomings will be
detected the WP2/3 networks shall be informed via WP9 (adequacy) WP1
(requirement)
WP 4 by ensuring that links are developed with coastal ocean observing systems
through EU FP7 JERICO (feeding in best practice activities already
developed), Forum for Coastal Technologies, EuroGOOS Working Groups
and Coastal GOOS. Possible additional links with IOOS (US).
WP 9 by evaluating stakeholder satisfaction with demonstrations provided and
recommending future steps and gaps that require filling in future versions.
We might as well establish a link to sustainability of service (Task 9.3)
WP 10 The demonstrators developed in WP8 will be the subject of discussion in
WP10 with a view to linking the specific experiences in AtlantOS with the
strategic planning of a sustainable IAOOS.
27
Inflow
WP 1 Delivers boundary conditions for shelf seas reanalyses.
WP 4 Task 4.3 Harmonised sea level data flow [Lead: NERC-NOC; Lesley
Rickards] will feed into WP7 and WP8 (specifically Task 8.2 – coastal
flooding).
WP 6 will provide success stories of economic impact through observing
technologies, but more importantly will underpin the ability to address
customer and stakeholder needs for products by providing underpinning
data – particularly for hard to measure biogeochemical and biological
variables.
WP 7 connect with the Atlantic integrated data system basic products in order to
develop the demonstrator products and tools.
Where WP1: Observing system requirements and design studies WP2: Enhancement of ship-based observing networks WP3: Enhancement of autonomous observing networks WP4: Interfaces with coastal ocean observing systems WP6: Cross-cutting issues and emerging networks WP7: Data flow and data integration WP8: Societal benefits from observing/information systems WP9: System evaluation and sustainability WP10: Engagement, Dissemination and Communication WP11: Management
28
References
Fylan, F. (2005) “Semi-Structured Interviewing”. In Miles, J. and Gilbert, P. (Eds.) A Handbook of Research Methods for Clinical and Health Psychology, Oxford: Oxford University Press.
Mannarini, G., Pinardi, N., Coppini, G., Oddo, P., and Iafrati, A. (2015) VISIR-I: small vessels, least-time nautical routes using wave forecasts, Geosci. Model Dev. Discuss., 8, 7911-7981, doi:10.5194/gmdd-8-7911-2015,.
29
Annex A WP8 technical meeting agenda
WP8 1st
Technical meeting Assess the status of input data to specific application products Assess the status of the design of specific application products
Proposed Agenda
Where? Via Tombesi dall’Ova, 55, Ravenna, Italy When?
18 to 20 of January 2016 Start time: 14:00hrs 18 January End Time: 12:30hrs 20 January Meeting Objectives
Get acquainted with the AtlantOS observing system / Discuss relations of applications in WP8 and cross-WP activites in AtlantOS
Identify key stakeholders regarding the application of the products under development and the way to approach them / User acceptance methodology
Demonstrate the value of products and services
Dissemination of our results (EMODnet Checkpoints + Copernicus + AtlantOS website)
Expected meeting outcomes
Status of the products & services (technical developments)
Clarity/update of workplans for each task team
Clear plan to engage with stakeholders
Milestone
Meeting report with decisions on work to be undertaken by WP8 will be made available on the AtlantOS website. Lodging
Please check the annex. How to get to Ravenna
The closest airport is located in Bologna, which is 1 ½ hour away from Ravenna by train. Public transport is available between the airport and the train station (Bologna Centrale),
30
taking approx. 30 min. The two cities are well connected and more information about train prices and timetables can be found at this weblink: http://www.trenitalia.com/tcom-en (in English)
In case you cannot find flights to Bologna, you may consider flying to Venice. However, please consider this as a second option as connections between Venice and Ravenna are not that frequent and involve train changes (weblink: http://www.trenitalia.com/tcom-en). Meeting activities
DAY 1 ---- January 18, 2016 14.00-14:15 Welcome & Housekeeping 14.15-14:45 AtlantOS General Overview, WP Links and Address specific WP8
questions (AtlantOS coordinator or deputy) 14:45-15:15 Overview of Objectives & Expected Outcomes, Address specific WP8
issues or questions (Pinardi) 15:30-16:15 Task 1: Harmful Algal Blooms 15:15-15:30 Coffee break 16:15-17:00 Task 2: Coastal flooding/storm surges 17:00-17:15 Tools for Spill Risk Assessment from ships: Implementation in the
Atlantic zone (Rodrigo Fernandes - ActionModulers) 17:15-18:00 Break out session (see note (1)) DAY 2 ---- January 19, 2016 08:30-09:15 Task 3: Ship routing hazard mapping 09:15-10:00 Task 4: Oil spill hazard mapping and disaster risk reduction best
practices 10:00-10:45 Task 5: Offshore aquaculture siting 10:45-11:00 Coffee break 11:00-11:45 Task 6: Reanalyses for MSFD and ICES assessments 11:45-12:30 Task 7: Operational real-time and forecast modelling of North Atlantic
albacore tuna populations
12:30‐14:00 Lunch break 14:00-14:45 Task 8: POGO-AtlantOS collaboration on ocean products 14:45-15:15 Action plan for Stakeholder engagement: How to identify key
stakeholders, communicate with them and ensure user satisfaction (Julie Maguire– DOMMRS (Ireland))
15:15-15:30 Coffee break 15:30-17.00 Round Table 1: Key stakeholders and how to approach them 17:00-18:00 Break out session (see note (1)) DAY 3 ---- January 20, 2016 08.30-10.00 Round Table 2: User acceptance methodology 10:00-10:15 Coffee break 10:15-11:45 Break out session 11:45-12:30 Wrapping up (what has been discussed in the conference +
deliverables + deadlines + next meetings)
31
Participant List
WP8 1st Technical Meeting (listed in alphabetical order)
Name Institution
Antonio Augusto Sepp-Neves University of Bologna (IT)
Caroline Cusack Marine Institute (IE)
Claudia Cesarini Clu Ltd. (IT)
Flavio Martins University of Algarve (PT)
Gianandrea Mannarini CMCC (IT)
Joao Janeiro University of Algarve (PT)
Johnanthan Tinker UK Met Office
Julie Maguire Daithi O'Murchu Marine Research Station (IE)
Manuel Ruiz Spanish Oceanographic Institute (SP)
Nadia Pinardi University of Bologna (IT)
Patrick Lehodey CLS (FR)
Trina Dale Norwegian Institute for Water Research (NO)
32
Annex B WP8 Tasks in the DoW of the Grant Agreement WP 8 and WP 9 aim to provide leadership for Europe in the implementation of GEOSS in
the Atlantic and to enhance the knowledge base necessary to cope with global challenges.
WP8 is designed to demonstrate the value and societal benefit of the existing observing
system in the Atlantic through pilot actions. It will deliver a suite of end-user focused
products that are targeted at issues of societal concern in European Member States, such
as climate, disasters, ecosystems, health and water.
Task 8.0 Scientific Coordination
[Lead: UNIBO, MI; Nadia Pinardi and Caroline Cusack]
The work package leaders will ensure that the planned work is carried out according to
plan and budget and that the deliverables are produced and milestones are attained on
time. Additionally the leader will ensure the establishment of the link with AtlantOS project
coordination and that the decisions taken at steering level are implemented in this work
package. This includes as well the management of risk registers and mitigation measures.
Task 8.1 Harmful Algal Blooms
[Lead: MI; Caroline Cusack]
Providing near real-time and forecast information for the aquaculture industry along
Europe’s Atlantic coast is of vital importance in mitigating the effects of Harmful Algal
Blooms (HABs). In this task in-situ and satellite data will be amalgamated in a decision
support system [MI, IEO, DOMMRS] [D8.6]. In-situ data include oceanographic data e.g.
water column structure, current speeds, biological samples (e.g. algal toxins,
phytoplankton cell counts, barcoding) and hydrographic and biogeochemical information
where possible. The in-situ data will be used to inform and validate biophysical models and
to produce circulation forecasts for the coming three to five days. These data will undergo
expert interpretation to produce an early warning bulletin to the aquaculture industry in
Spain, Norway and Ireland [D8.11] [MI, IEO, NIVA]. The bulletin will be distributed over a
specified production season in both countries to fish farmers and shellfish production
33
facilities so that husbandry and harvesting techniques can reflect the prevailing HAB
conditions at any point in time.
Task 8.2 Coastal flooding/storm surges
[Lead: NECR-NOC; Kevin Horsburgh]
Any increase in flood frequency or severity due to sea level rise or changes in storminess
would adversely impact society. It is crucial to understand the physical drivers of extreme
storm surges to have confidence in the datasets used for extreme sea level statistics. We
will refine and improve methods to the estimation of extreme sea levels around Europe
and more widely. We will do so by developing a comprehensive world map of storm surge
distribution (including extremes) for both tropical and extra-tropical cyclones. We will apply
statistical methods to both tide gauge data and multi-decadal runs of hydrodynamical
numerical models [NERC-NOC, MI]. We will also contribute to the development of a global
storm surge climatology, building on the work of the IOC/WMO JCOMM Expert Team for
Waves and Coastal Hazards [D8.1] [ NOC, MI] . The results will advance our scientific
knowledge of storm surges as well as provide valuable policy guidance to decision makers
and planners [D8.12] [NERC-NOC, MI].
Task 8.3 Ship routing hazard mapping
[Lead: CMCC; Gianandrea Mannarini]
This task will use outputs from WP7 and other sources for developing a system for ship
routing risk mapping. Starting from knowledge of the environmental fields affecting vessel
seakeeping, the system will estimate risk and cost associated to known routes in the
Atlantic Ocean. The system will employ model analysis or reanalysis of sea state (wave
height, period, and direction), hydrodynamics (near surface ocean currents), and
meteorological (wind) models. The system will produce an objective assessment of risk
and vessel operational cost for an ensemble of historical routes obtained from the
Automatic Information System database. The hazard assessment procedure will be based
on UNIBO experience in hazard mapping and probabilistic approaches. In particular, the
existing CMCC ship routing code will be refined and evolved for evaluating routes
compliant with IMO safety recommendations, for a class of large ocean-going vessels, a
34
collaborative work between CMCC and UNIBO. The same approach will be extended to
computation of vessel operational costs along the route. This information will build up a
database, queried by the end-user through a graphical interface for visualizing customised
maps of route risk and cost for user provided parameters [D8.10]. The fitness of AtlantOS
for ship routing will be analysed with a dedicated report [D8.14].
Task 8.4 Oil spill hazard mapping and disaster risk reduction best
practices
[Lead: UNIBO; Nadia Pinardi]
The MSFD, the new Directive on Safety of offshore oil and gas operations (2013) and the
European Maritime Safety Agency require robust tools, for oil spill hazard mapping, from
ad-hoc to operational. In this task the WP7 and Marine Core Service products will be
coupled to Medslik-II oil spill model in order to:
1. develop a methodology for oil spill hazard mapping from major commercial shipping
lines across the Atlantic and produce hazard maps to be made available to public
consultation [D8.4] [UNIBO, UALG]
2. produce on request an Oil Spill Hazard Bulletin [CLU] based upon the hazard mapping
data for a Targeted Operational Period [D8.7; UNIBO]. Finally an assessment of fitness for
purpose of the observing system for the Oil spill Hazard Bulletin will be produced [D8.15]
Task 8.5 Offshore aquaculture siting
[Lead: NIVA; Trine Dale]
European policy intends to expand the space available to aquaculture by cultivating sites
that are offshore. This presents challenges in terms of building structures e.g. fish cages
that withstand the effects of offshore weather conditions along the Atlantic coast. In order
to establish possible future sites for offshore aquaculture production we intend to gather
relevant wave, current velocity and water column structure measurements from the coasts
of Ireland, Norway and Spain and use these data to validate site assessment models at
ca. 200 m horizontal resolution of the potential new offshore aquaculture sites [D8.2] [
NIVA, IEO, MI] . This will result in a generic tool based on in-situ observations and model
35
output over a hindcast period, coupled to existing site decision tools, so that potential
license applicants can pinpoint sites for further exploration and site investigation. We will
also develop a weather window tool to give developers real-time access to observations
and model forecasts of seas state to plan day to day operations [D8.8] [NIVA, IEO, MI].
The AtlantOS fitness for purpose for the aquaculture economy will be assessed [D8.13;
NIVA].
Task 8.6 Reanalyses for MSFD and ICES assessments
[Lead: MET O; Richard Wood]
Environmental quality indicators for MSFD require the
best possible estimates of the three-dimensional state of the shelf seas, now and in the
recent past (reanalyses). In this pilot project we will demonstrate the value of IAOOS
observations in improving physical and biogeochemical reanalyses of the North West
European Shelf, using the North West European Shelf regional reanalysis system of the
Copernicus Marine Service [D8.5] [MET O]. In WP1, the influence of various Atlantic
Ocean observation types on reanalyses of the open ocean state will be assessed. Here,
we will take open ocean boundary conditions derived from WP1 to drive the Copernicus
North West Shelf model, and so demonstrate the impact of the different IAOOS
observation types in constraining the shelf seas state. As a by-product we will obtain
insight into the influence of the open ocean on the shelf seas, leading to more confident
attribution of the causes of observed changes on the shelf. We will work closely with
representative national and international end-users to assess the value of these enhanced
reanalysis products and attribution for managing MSFD compliance and fisheries [ 8.16].
36
Task 8.7 Operational real-time and forecast modelling of North Atlantic
albacore tuna populations
[Lead: CLS; Patrick Lehodey]
The model SEAPODYM simulates the spatial dynamics of tuna populations under the
influence of both fishing and environmental effects. The main features of the model are:
• Forcing through off-line coupling to environmental variables, such as temperature,
currents, primary production and dissolved oxygen concentration
• Prediction of the distributions of functional groups of micronektonic prey (Lehodey
et al 2010), and age-structured predator (tuna) populations (Lehodey et al 2008)
• Prediction of catch and size-frequency of catch by fleet
• Parameter optimization based on data assimilation techniques (Senina et al 2008)
This model has now reached a degree of maturity allowing to use it for testing
management scenarios (e.g., Sibert et al 2012) and to implement operational monitoring
(ongoing work for the Indonesian Ministry of fisheries). It is proposed to implement an
operational forecast system for the Atlantic albacore tuna [D8.3] based on the first
configuration optimised for the North Atlantic stock at coarse resolution over the historical
fishing period (EU FP7 project Euro-Basin (Lehodey et al., submitted). The system will use
physical fields from MyOcean (Mercator-Ocean 1/4°x7d; satellite derived primary
production and euphotic depth). The interest of this operational production of tuna stock
distributions will be evaluated in collaboration with colleagues involved in the management
of tuna fisheries at ICCAT and FAO, and the AtlantOS fitness for this modelling analysed
[D8.9].
Task 8.8 POGO-AtlantOS collaboration on ocean products
[Lead: AWI; Karen Helen Wiltshire]
Five to six fellowships of 5 months duration will be provided by AWI to facilitate the
interaction between Emerging Ocean Countries along the Atlantic Seaboard and ocean
research institutes in Europe [D8.17; AWI]. This will allow practical scientists the
opportunity to implement their expertise and views in modern ocean science
infrastructures, to develop “take home” sampling protocols and to the develop
assessments of “tool necessities” for specific applications. This will facilitate the trans-
37
national development of simpler, financially reasonable- knowledge based marine
products. These Fellowships will relate to an Atlantic observing and information
generation. A specific call will be made at the beginning of each year/ or in tune with
POGO deadlines in spring asking scientists for applications. The vetting of the applicants
will be carried out by a neutral committee with the help of POGO.
38
Annex C Use Case Product Specification Document
WP8 : Societal benefits from observing/information systems
Description of Targeted products from Use Cases
First version
Total number of pages:
Workpackage: 8 Task #: TITLE
Author(s): Author name Author institution
Author name Author institution
A project funded by H2020
Document Log
39
Date Author Changes Version Status
40
Table of Content
Glossary ....................................................................................................................................... 30 Executive Summary ...................................................................................................................... 31 General scope of the document .................................................................................................... 32 General scope of the Use Case .................................................................................................... 33 User requirement identifications .................................................................................................... 34 Target Users for the Use Case ...................................................................................................... 34 Literature review of user needs ..................................................................................................... 34 Targeted Product description ........................................................................................................ 35 Use Case Targeted product specifications .................................................................................... 36 Description of input characteristics and data sources needed by Targeted products ..................... 37 Description of methodology to produce the Targeted Products ..................................................... 38 Targeted product # ........................................................................................................................ 38 Targeted product # ........................................................................................................................ 38 Implementation Risk Table ............................................................................................................ 39 Identification of AtlantOS impacts ................................................................................................. 40 Annex 1 Nomenclature ................................................................................................................. 41
41
Glossary Please list your acronyms
Name Meaning
Use case The AtlantOS Task
42
Executive Summary Please overview the document content here
43
General scope of the document This document is for internal use only. It will be updated once a year and the first version has appeared in April 2016. It will:
1) drive the orderly production of Use Case Targeted products; 2) help to plan the Web based Portals on AtlantOS for WP8 Use Cases; 3) communicate across EU Projects, in particular EMODnet Atlantic Checkpoint.
Several versions of this document will be produced during AtlantOS to follow the life cycle of the Use Cases and their modifications. This is the first one, the second will be at the end of the second project year.
44
General scope of the Use Case The general scope of the Task/Use Case has been established in the DoW, here please enlarge the discussion of the overall scope of the Use Case and the “Societal Benefit” associated. Please add the description of similar Use Cases in the Literature, add references.
45
User requirement identifications Please input here the specifications for your Use Case
Target Users for the Use Case Table 1: Target Users and needs
Target User Name URL of User User needs (from previous work or literature)
Literature review of user needs Description of the top ten user needs, add references as much as possible
46
Targeted Product description Please list all the Targeted product components for the specific Use Case. There might be several product components out of one Use Case, for example: 1)in the HAB Task you might give indices for Oxygen depletion (first product) as well as distribution of HAB species (second product); or 2) in the ship routing task you might give shortest path with safety constraint (first product) or minimum cost path (second product). Table 2: Target Product components
Nb Name of Targeted product component
Short description
Format (pdf, GIS layers, code, excel Tables, NetCDF files, etc.)
Textual description Textual description
47
Use Case Targeted product specifications For each Targeted product components please make a Table that lists the quality elements (ISO nomenclature) required for their production. This is what is EXPECTED, probably NOT what will be achieved Table 3: Target Product specification
Targeted Product component specification
Product component name
From the previous Table
Product component description
From the previous Table
Geographic description
Use name of sea area or conventional name by users
Horizontal extent Give latitude, longitude of sea area bounding box
Horizontal resolution Give lat. long resolution (fraction of lat, long) of products if in a grid, station locations if stations, etc.
Horizontal accuracy Give an estimate of the accuracy in defining the product grid or the station locations or define the closeness of coordinate values to
values accepted as or being true e.g. on the base of instrumentation used
Vertical extent Approximate range of depth where the product is significant (surface if the product is only surface, surface-to-bottom if the product is defined in the whole water column, etc.)
Vertical resolution Give number of depth or layers where the product is defined if possible
Vertical accuracy Give an estimate of the accuracy in defining the product vertical grid (if the product is only surface or one layer please try to define what “surface” means or how the layer was defined)
Temporal extent Give an estimate of the time period where the product is defined to be relevant
Temporal resolution Give the time resolution (hourly, daily, weekly, monthly, annual, etc.) of the product
Temporal accuracy Give an estimate of the errors involved in the definition of the product time resolution
Spatial representation
Give a description of the specific graphical representation of the results
48
Description of input characteristics and data sources needed by Targeted products Each Targeted product component should list the input data sets used, followed by a short textual description. Please list also the source data policy. Table 4: Input data and sources
Nb Targeted product
component name
Input data characteristics(*)
Environmental Matrix (*)
Data source (URL)
Data Policy of the
sources (restricted, open, open
and free, etc.)
(*) see annex for definitions
49
Description of methodology to produce the Targeted Products Please insert here a scientific description of the product and the actual method to produce it, one sub-section for each product component is needed. Please be comprehensive as in a scientific paper, insert references to papers about the methodology.
Targeted product #
50
Implementation Risk Table Please fill in the following Table where an example of risks is given from the MPA MedSea Checkpoint Risk Table Table 5: Risk Table
N° RISK DEFINITION
PROBABILITY L=low,
M=Medium, H=High
CAUSE (C) EFFECT (E)
PREVENTION (P) CORRECTIVE (C) ACTION
1 Scarce availability of MPAs information
L C1: Data are not available from the provider. E1: Limited inventory, scarce Mediterranean basin coverage
P1: Network expansion C1: Widen search and enlarge sector-related information
2 Interactions with stakeholders difficult
L C1: Different viewpoints E1: Difficulties in enhancing cooperation E1: Limited understanding of impacts on blue economy
P1: Take into account a greater number of viewpoints and interact with a wider range of stakeholders C1: Joint approach with stakeholders in the database building process
3 WP9 Portal not properly adapted for the MPA display
L C1: Technical faults of WP9 portal E1: scarce visibility of MPA data sets
P1: Participate to the web portal and GOS use case definition. Define requirements. C1: Validate each web releases
51
Identification of AtlantOS impacts Questions to be addressed here are: 1) What is the most important characteristic and input data set impacting the quality, usability and fitness for purpose of your product? 2) How are you going to show impact of AtlantOS on your Use Case? 3) What is the readiness level of your product (please follow the EU scale) More…
52
Annex 1 Nomenclature In EMODnet Checkpoints we have defined the following nomenclature
Characteristic In this document, a “characteristic” is a distinguishing feature which refers to:
3. either to a variable derived from the observation, the measurement or the numerical model output of a phenomenon or of an object property in the environment
4. the geographical representation of an object on a map (i.e. a layer such as a protected area, a coastline or wrecks) by a set of vectors (polygon, curve, point) or a raster (a spatial data model that defines space as an array of equally sized cells such as a grid or an image).
Environmental matrices This concept is introduced to avoid ambiguities when using a characteristic name such as “temperature”. The environment matrix is the environment to which a characteristic is related and we define them to be:
7. Air 8. Marine Waters 9. Fresh Waters 10. Biota/Biology 11. Seabed/Riverbed 12. Human Activities
Quality principles Spatial extent
Box or geographic region bounding the datasets
Spatial resolution :
Size of the smallest object that can be resolved on the ground. In a raster dataset, the resolution is limited by the cell size.
Spatial Accuracy Requested closeness of coordinate values to values accepted as or being true e.g. on the base of instrumentation used
Time extent
Time interval represented by the dataset or by the collection.
Time resolution Size of the smallest interval of time that can be resolved.
Time Accuracy Requested closeness of temporal values to values accepted as or being true.
Usability The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.
Completeness
Degree of absence of data in a dataset
Logical Consistency
Degree of adherence to format required Thematic Accuracy
53
Requested closeness of characteristic values to values accepted as or being true (the so called attribute of a data entity eg "wave height"). It includes the correctness of the classification of features or of their associations...