1295days since
Demo Capture

Recent site activity

Beach & Shellfish Closure Scenario

Overview

Coastal managers make decisions to close shellfish beds to fishing and either close bathing beaches or issue warnings to swimmers as a result of water column bacterial content. Closure / warning decisions are based on bacterial growth models which in turn utilize a variety of observations such as rainfall, sea surface temperature, ocean color / chlorophyll content, and coastal water flows. Restriction-lifting decisions are based on either model results or analyzed bacterial counts. Analyses should also be used to validate / update the model and calibration.

Narrative

  1. A coastal zone manager designates a regional area of interest and one or more localities for closure / warning decision support. The manager also describes the statistical criteria for closure decisions and re-opening decisions.

  2. A coastal zone scientist develops a regional decision support workflow and specific workflow refinements for each of the localities, describing the general criteria for observation data to support each workflow.

  3. A coastal data manager searches for existing relevant data services and publishes additional data as needed to support the workflow.

  4. CZ scientist visualizes and analyzes published data to calibrate formulae for each locality

  5. CZ data manager publishes site closure formulae for use by DSS applications so that decision events can be published

  6. CZ manager subscribes to notifications.

  7. A decision event (e.g. precipitation) is communicated to CZ manager, who tasks an analyst to initiate decision support workflows for affected sites.

  8. Results of workflow are in turn published as observation predictions.

  9. CZ manager and others discover and visualize DS workflow output to make closure / warning decisions.

  10. This workflow is repeated for re-opening decisions in the case of implemented closures.

A

Scenario Steps

 Scenario Name
Engineering Use Cases
 Specialization of Use Cases
 CB-PD-01. Manager selects area of interest for beach and shellfish closure


01.1. Scientist uses IP3 client application to submit a query to the IP3 Mediation Service and discover the presence datasets for a given specie.
N°.      Name  Desc.
 04 Client Search of Metadata Register resources in the GEOSS OCS Registry

 A couple of specialized search metadata Use Cases related to "Biodiversity Data Discovery" in an IP3 Client Application shall describe here the search interface(s) of the IP3 Mediation Service, and the way to interact with those. So far, the IP3 Mediation Service Catalog interfaces are identified as:
- CS-W 2.0.2 CORE
- CS-W 2.0.2 ISO Metadata
- CS-W 2.0.2 ebRIM AP with EO extension Package
- CS-W 2.0.2 ebRIM AP with GBIF Ext. Package (tbd)
01.2. IP3 Mediation Service mediates the query request distributing it to the GBIF Web System.
 This seems to be a missing Transverse UC, or we need to work out something from the 06 Interact with Services
Shall refer to the SIF Standards Registry and Interoperability Arrangement that describes the GBIF Web system Service interface.
This Arrangement could be described as a preliminary step of this scenario, related to the GEOSS infrastructure setup.
01.3. Scientist selects one or more datasets returned by the query.
N°.      Name  Desc.
 05     Presentation of Reachable Services & Alerts User presentation of information about available services, workflows, and alerts
 
01.4. Scientist gets the selected dataset(s) using the IP3 Mediation Service, which mediates the access request distributing it to the GBIF Web System.
N°.  Name  Desc.
 06 Interact with Services Activity of client to consume services for datasets, sensors, models, workflows, etc
 
 CB-PD-02. Scientist uses GBIF IP3 Mediation Service to develop correlation model between species and environment.  TOPS data are used if available, otherwise other climate sources can be used.

cf. Pika Distribution high level use case :
Niche Model Generation:
(Transverse use cases are mapped in the detailed steps below)


 
02.1. Scientist uses client application to submit a query to the IP3 Distributed Catalog and discover historical climate data
UC n°4
A Geoportal ?
A specific client ?
 
02.2. IP3 Distributed Catalog mediates the query request distributing it to the TOPS/Climate Data Server
UC n°3
A couple of specialized use cases is anticipated for describing Catalog Federation Mechanisms (mappings).
 02.3. Scientist selects one or more datasets returned by the query
   
 02.4. Scientist gets the selected dataset(s) using the IP3 Distributed Catalog
   
 02.5. IP3 Distributed Catalog mediates the access request distributing it to the TOPS/Climate Data Server
   
 02.6. Scientist generates a niche model ingesting the selected biodiversity and climate data into the IP3 ENM (Ecological Niche Model) Server
   
 CB-PD-03. Scientist validates model using additional observations.

cf.
Pika Distribution high level use case :
Model Validation:



 
03.1. Scientist validates the generated niche model using additional observations
   
 CB-PD-04. Scientist uses known physiological limits of the species to direct the development of models relating predicted climate change to predicted change in species distribution.

Cf.Pika Distribution high level use case :
Model Prediction Generation




 
 CB-PD-05. Scientist uses GBIF IP3 system to predict how range distributions will contract in the future

cf.Pika Distribution high level use case :
Range Distribution Prediction


 

Legend:
AIP-2 Services in blue
AIP-2 Products in red
AIP-2 Actors in orange
Comments