Difference between revisions of "Template Format"
Line 57: | Line 57: | ||
===Preconditions=== | ===Preconditions=== | ||
− | *1. | + | *1. Satellite data are available through open interfaces |
− | *2. | + | *2. |
*3. | *3. | ||
Revision as of 09:28, February 27, 2007
Use Case AQ.SatelliteData.1.a
Purpose
Earth Information Exchange
Access to satellite data using queries over a continuous space-time-parameter domain.
Revision Information
Version 0.1.a
Prepared by: Rudolf Husar Washington University
and
Stefan Falke Washington University and Northrop Grumman IT - TASC
created: February 26, 2007
Revision History
Modified by <Modifier Name/Affil>, <Date/time>, <Brief Description>
Use Case Identification
Use Case Designation
AQ.SatelliteData.1.a
Use Case Name
Short name: Satellite data access
Long name: Air quality user-access to satellite data by space-time-parameter queries
Use Case Definition
The AQ cluster has a fundamental need for a set of CORE web services that allow meaningful user-access to satellite data. These services include:
- Data access by space-time-parameter query on granules
- Subsetting that clips the data to user-specified BBOX
- Mosaicing that splices granule mosaic into a coherent dataset
The proper chaining of these services results in a higher order service, WCS, that returns the requested satellite data for the BBOX, Time, Parameter. Not more not less. Such a WCS service was in fact used in the Web service chaining experiment. Extending that service to return numeric satellite data (not just images) is the goal.
Actors
Primary Actors
Air quality analysts interested in using satellite data for assessing air pollution, comparing satellite and surface data, "ground-truthing" model results.
Other Actors
Preconditions
- 1. Satellite data are available through open interfaces
- 2.
- 3.
Postconditions
- 1.
- 2.
- 3.
Normal Flow (Process Model)
- 1)
- 2)
- 3)
- 4)
Alternative Flows
Successful Outcomes
- 1.Operation succeeds and user obtains satellite dataset adhering to the requested spatial, temporal, and parameter filters.
Failure Outcomes
- 1.
- 2.
Special Functional Requirements
None
Extension Points
- <Cluster>.<SubArea>.<number>.<letter+1> something added or a variant.
E.g. AQ.Smoke.1.b something added or a variant
- <Cluster>.<SubArea>.<number>.<letter+2> something added or a variant
- <Cluster>.<SubArea>.<number>.<letter+3> something added or a variant