Navigation

Recent site activity

UC5: Presentation of reachable Services and Alerts

Back to the Transverse Technology Use Cases list.


Brief description

Role and purpose: this use case describes the conditions and steps for portals and application clients to present to the GEOSS User the reachable services and alerts discovered by searching the GEOSS Clearinghouses and/or Community Catalogs.

Basic flow of events

 Title

 Presentation of reachable Services and Alerts

 Overview

 

 Actors and Interfaces

  • GEOSS User
  • Client application able to support the presentation of the selected services and/or alerts of interest (including GEO Portal, Community Portal, Desktop Application, portlet, etc)- Note that a GEO Portal may act as a client only to a reduced set of services
  • GEOSS Service Providers

Initial Status and preconditions

  • GEOSS User has discovered and/or selected services or alerts of interest
  • Client has established reachability of discovered registered services or alerts (e.g. Client has established that the services of interest are running and responding to requests)
  • Client can support the presentation of the selected services or alerts of interest

 Evolution

(basic flow steps

  1. For OGC Web Services
    1. Client issues GetCapabilities request to receive further metadata about the capabilities provided by the service
    2. Depending on the type of service, the Client presents the GEOSS User with more information on the service offerings such as layers, features, coverages, sensor parameters, portrayal rules, etc served by the selected service
    3. The GEOSS User can choose to get additional information about each offering (if available via DescribeFeature, DescribeCoverage, DescribeSensor, etc)
  2. For Alert Services
    1. The GEOSS User is presented with subscription options (e.g. frequency of alerts, geographic extent, etc)
    2. The GEOSS User can choose subscription options
    3. See here for a "specialized use case" candidate document for Alerts
  3. After selection of resources (service offerings and/or alert options), Client provides options for
    1. displaying/portrayal of maps (in time and in space)
    2. zooming in to results,
    3. adding results to the viewing map, 
    4. saving current view/selections as GeoRSS, html, KML, context document, etc
  4. For each selected resource, Client provides options for
    1. downloading/exploring resource in case of files, documents, web sites
    2. displaying alerts in case of alert services
    3. viewing resource in case of OGC Web Service
      • Client formulates GetMap, GetFeature or GetGoverage request
      • This could involve launching a third-party visualiation client such as Google Earth
    4. parametrizing and executing workflow


 Post Condition

The Client application has an information representation for the GEOSS User to use for interacting with reachable services and alerts of interest.


Alternative flows of events

TBD

Special Requirements

TBD



Comments