euromiss, eurodss and dms update of progress keiran millard ([email protected]) keiran...
TRANSCRIPT
EuroMISS, EuroDSS and DMSUpdate of Progress
Keiran Millard
Keiran Millard
© HR Wallingford 2007 Page 2
EuroMISS, EuroDSS and DMS
How these parts of ECOOP fit together• EuroMISS (WP8)
− Measurement Information System of Systems
• EuroDSS (WP9)− Decision Support System of Systems
• DMS (WP2)− Data Management Systems
Drivers for integration• Effective delivery and deployment in ECOOP• Response to INSPIRE Directive• Consensus on data and system standards
Excellent commitment from ECOOP partners to work together
ECOOP has facilitated voluntary clustering of related EC projects
© HR Wallingford 2007 Page 3
EuroMISS, EuroDSS, DMS and Drivers
Effective delivery and deployment in ECOOP• DMS supports EuroMISS that support EuroDESS
Consensus on data and system standards• Data Content Models
− GCMD, CF, OGC O&M, Community serialisations• Data Structure Models
− CF, ISO19115, ISO19123, ISO19101 • Data Encoding Models
− NetCDF, ISO 191136 (GML), KML, JPEG/PNG• Data Catalogue Implementations
− THREDDS, CSW• Data Server Implementations
− OpenDAP, Dapper, WFS, WCS, WMS
All these need to be considered in the context of the data representation:
Points, Grids, Profiles, Meshes, Trajectories – plus metadataConsensus workshop (March 5-6th) on data models
and services for observation data•Standards Community (OGC, ISO and INSPIRE)
EC Projects MarineXML, Motiive
•Operational Services CommunityEC Projects
MERSEA, ECOOP, Infrastructure Development Community
EC Projects SeaDataNet, Coriolis. SERPRIS
© HR Wallingford 2007 Page 4
EuroMISS, EuroDSS, DMS and INSPIRE
INSPIRE does provide (and mandate) some answers• Discovery Services
− CSW (Catalogue Services of the Web)− INSPIRE ISO 19115 Metadata Profile + ISO19136 encoding
• View services− WMS (Web Map Service)
• Note− INSPIRE view and discovery services unlikely to meet fully all the
needs of ECOOP. They are set up for “general purpose environmental services”
• Data product specification methodology− A structured approach for a community to define data models − To exchange within and outside their community
Common standards give access to common services
•Discovery services
•View services
•Processing services
Become more important at the DSS level
•Machine and human readable
© HR Wallingford 2007
ISO 19131 – Data Product Specification
Data product specification
Data product
0..*
+specifies
0..*
Dataset
0..*
+implemented as
0..*
Metadata
1..1
+described by
1..1
How the data should be How the data actually is
An “Ocean Weather” product to be delivered by ECOOP to Decision Support Systems
An dataset instance of an “ocean weather” product with accompanying metadata
© HR Wallingford 2007
MFC and TAC
EO FloatVessel Moored Other
MFC TAC
Observation and Measurement Networks- Various parameters (temperature, windspeed, chl-a)- Various sampling regime (fixed instrument, vessel, aircraft)- Various sampling features (point, trajectory, profile, grid)Results in variety of dataset models
Model Product
Obs ProductMFC takes a observation data as input to produce a ‘Model Product’. This is realised as a regular gridded datasets in NetCDF CF
TAC takes a observation data as input to produce a
harmonised ‘observation product (s)’. Realisation of
this to be determined as could contain a variety of
data models. Could result in several data sets
Future Path
1..*1..*
Data capture typically by FTP harvest
© HR Wallingford 2007
MFC and TAC Deployment
MFC TAC
Model Product Obs Product1..*
1..*
ROOS
1..*
EuroMiss common clients (search, view)Common services (CSW, WMS for INSPIRE)
EuuroMISS (WP8) provides a means to discover and access
model products
-THREDDS-OpenDAP
-NetCDF CF
DMS (WP2) provides a means to discover and
access observation products. Extends
SERPRIS
Technology to be determined.
ECOOP has 5 ROOS
ud Use ...
User
© HR Wallingford 2007
EuroMISS and EuroDSS Deployment
MFC TAC
Model Product Obs Product1..*
1..*
ROOS
1..*
EuroMiss common services (WMS, CSW)
EuroDESS comm
on services (search, view, get)
OceanWeather
MyDSS
Other Products
Find, view and get dataset instances of data
product
ud Use ...
User
© HR Wallingford 2007 Page 10
ECOOP WP 8
T8.1 - Definition and Development of EuroMISS• Pouliquen Sylvie (IFREMER) - CMRC, HCMR, HRW, IFREMER, MARIS, UREADES• Objectives
− Within the ECOOP project the task 8.1 is in charge of defining and developing the European Marine Information System of System (EUROMISS). This system aims to provide an integrated access to the products inside and outside ECOOP.
T8.2 - Regional management of Marine Information System of Systems for ECOOP. (EuroMISS-ECOOP)
• She Jun (DMI) - BIU, BSH, DMI, FIMR, IMEDEA-CSIC, IMS-METU, MERCATOR, OC-UCY, PdE, RBINS-MUMM, SMHI, UREADES
• Objectives: − The objective of WP8.2 is to provide a regional connection to the existing European thematic portals,
and to provide connection from the coastal systems to the regional thematic portals.T8.3 - Evaluation of the performance of the EuroMISS
• Durand Dominique (NIVA) - IMEDEA-CSIC, IMS-METU, METO, NIVA, OC-UCY, TECHWORKS, UNI-MALTA(IOI-MOC)
• Objectives: − The objective of task 8.3 is to provide assessment of the various versions of EuroMISS, and to
provide quality assurance of the specifications defined in task 8.1, from the perspective of both the intermediate user, and of the end-user of the ECOOP information services.
Presentations
Sylvie Pouliquen EuroMISS developments
Keirth Haines EuroMISS view services
© HR Wallingford 2007 Page 11
ECOOP WP 9
T9.1 - EuroDeSS specifications & standards• Millard Keiran (HRW) - HCMR, HRW, IMR, MET-NO, UREADES• Objectives:
- Formalise the requirements of the EuroDeSS- Develop a model for the deployment and operation of the EuroDeSS- Establish mechanisms of the deployment of a EuroDeSS application system
T9.2 - Development, management and demonstration of EuroDeSS for targeted applications/areas
• Hackett Bruce (MET-NO) - AZTI-Tecnalia, CEFAS, CMRC, FIMR, HCMR, IMR, INGV, IST MET-NO, METO, MF, NERSC, NIVA, OC-UCY, TECHWORKS, LIM/UPC, UREADES
• Objectives: − Develop targeted application elements of an integrated EuroDeSS according to the specifications
laid down in Task 9.1.− Demonstrate the usefulness and applicability of EuroDeSS through user-oriented demonstrations in
a representative range of European coastal areas.T9.3 - EuroDeSS evaluation including user perspectives
• O Tuama Eamonn (CMRC) - CMRC, HCMR, HRW, MET-NO, NERSC• Objectives:
- Establish metrics for the evaluation of EuroDeSS operations.- Apply evaluation criteria to EuroDeSS development and operations- Contribute the EuroDeSS to the overall ECOOP evaluation
Presentations
Kostas Nittis EuroDESS Overview
Keiran Millard / Bruce Hackett EuroDESS update
EuroDSS (WP9)Update of Progress
Keiran Millard
Keiran Millard
© HR Wallingford 2007
EuroDESS Scoping Document
• EuroDeSS is primarily a collection of resources that enable a DSS to be realised through EuroMISS. In essence, EuroDESS exists to supply ECOOP registered products (model and observations) in an harmonized way to MyDSS
• The EuroDSS needs to be persistent and reliable.• The EuroDSS needs to recognise that the thematic domains of
ecosystems, marine security and fisheries have different requirement for DSS operation.
• We are not concerned as to how good decisions are made by MyDSS or indeed if EuroDeSS improves this. The main criterion is that the existence of EuroDeSS enables improvements in the establishment of DSS.
− Easier deployment and maintenance of MyDSS
© HR Wallingford 2007
Data Products
• In the scope of ECOOP, EuroDeSS will address three main communities.
• Marine Ecosystem Health• Marine Security• Fisheries Management
• For each of these three communities we need to consider the information that needs to be provided as input to MyDSS.
• Identified some common ‘data patterns’ that could be used to establish a Data Product Specification for these communities.
“OceanWeather” product as a starting point
A common denominator product to test the EuroDSS concept
© HR Wallingford 2007 Page 15
DSS Scenario
•Find “Oceanweather @ XYZT”• Request from MyDSS to EuoDSS
•EuroDESS Query• Query EuroMISS catalogue• Query other catalogues (that may exist)
•EuroDESS Return• Catalogue with links to data or provider• If data, generic view service
•Download• Protocol for data access
© HR Wallingford 2007
MyDSS and EuroDSSud Use Case Model - Computational
MyDSS
EuroDSS
EuroMISS
DataCentre
GetData
DiscoverData
OrderData
ViewDataProductsThe key data product isthe OceanWeather data product
MyDSS actually liaises with a Data Centre for the actually supply anddelivery of data
EuroMISS catalogue enables MyDSS to identify who can supplyEuroDSS products suchas 'OceanWeather'
GetData means in practice:
Deliver me a dataset for DataProduct X (e.g. OceanWeather) which has:- Spatial boundaries X,Y,Z- Temporal boundaries T1 to T2- Parameter subset A,B,C
This 'get' could be realised throughan FTP-push or a call to a server
Discovery is of instances of DataProducts
ViewData
Liaises with
PublishData
Note:
MyDSS will wish to integrate OceanWeather data with other (non-ECOOP) data sources and services
© HR Wallingford 2007 Page 17
Next Steps (EuroDESS)
Established data product specification for OceanWeather
Determine architecture for deployment of EuroDESS services
• Integration with EuroMISS catalogue− What is possible?
• Extension of generic view services
Observation Feature TypesUpdate of Progress
Keiran Millard
Keiran Millard
© HR Wallingford 2007 Page 19
‘Observation’ Feature Types
•Data Product Specification related to measuring and observations requires Feature Types based on:
• Scientific utility of the sampling regime• Limitations of the observation process
•CSML (Climate Science Modelling Language)• Consistent with community practice
− ESRI, UniData, NOAA
• Feature types and storage descriptors− Binding to NetCDF, GRIB etc.
• Implemented in UML and GML
© HR Wallingford 2007 Page 20
CSML Feature Types
Includes wrapper for NetCDF, GRIB, NASAAmes
Seven Feature Types
CSML feature type principles:•offload semantics onto parameter type•offload semantics onto CRS•‘sensible plotting’ as useful discriminant
Climate Science Mark-Up Language has been developed for handling ‘measuremnt and modelling’ type Features.
© HR Wallingford 2007 Page 21
CSML Feature Types
CSML feature type Description Examples
TrajectoryFeature Discrete path in time and space of a platform or instrument.
ship’s cruise track, aircraft’s flight path
PointFeature Single point measurement. raingauge measurement
ProfileFeature Single ‘profile’ of some parameter along a directed line in space.
wind sounding, XBT, CTD, radiosonde
GridFeature Single time-snapshot of a gridded field. gridded analysis field
PointSeriesFeature Series of single datum measurements. tidegauge, rainfall timeseries
ProfileSeriesFeature Series of profile-type measurements.vertical or scanning radar, shipborne ADCP, thermistor chain timeseries
GridSeriesFeature Timeseries of gridded parameter fields.numerical weather prediction model, ocean general circulation model
Presently in Release 2
© HR Wallingford 2007 Page 22
‘Observation’ Feature Types
Motiive TestbedGeneric (CSML) Time Series
TidalWaterLevel
TimeSeries
Graph and Table
Service
© HR Wallingford 2007
WFS Implementation
WFS
© HR Wallingford 2007
WFS Implementation
• MCF• Can determine what products are made available
− Can have several products− Can decide which users can access these products− Need to look at standardising products and metadata
– DPS for EuroMISS
• ECCOP needs to provide implementation spec. for OpenDAP
− Can be used for 8.2 and others (e.g. in WP5)− 7.2 are looking at unsctructured, but out of scope.− Sylvie to circulate guidelines supplied by Daniel− XML code for configuration is sometimes − Projecta to act as reporistory for saving documents.