Difference between revisions of "User access to satellite data"
Latest revision as of 17:52, July 11, 2007
- 1 Use Case AQ.SatelliteData.1.a
- 2 Purpose
- 3 Revision Information
- 4 Use Case Identification
- 5 Use Case Definition
- 6 Diagrams
- 7 Non-Functional Requirements (optional)
- 8 Selected Approach
- 9 References (optional)
Use Case AQ.SatelliteData.1.a
Earth Information Exchange
Access to satellite data using queries over a continuous space-time-parameter domain.
Prepared by: Rudolf Husar Washington University
Stefan Falke Washington University and Northrop Grumman IT - TASC
created: February 26, 2007
Modified by <Modifier Name/Affil>, <Date/time>, <Brief Description>
Use Case Identification
Use Case Designation
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.
Air quality analysts interested in using satellite data for assessing air pollution, comparing satellite and surface data, "ground-truthing" model results.
- 1. Satellite data are available through open interfaces
- 2. Data access service specifications, e.g. OGC Web Coverage Service (WCS), can be implemented by data provider or mediator
- 1. Satellite data in a numeric data format (as opposed to image format) covering the spatial area, time range, and parameters that were specified in the query.
Normal Flow (Process Model)
- 1) The user finds a WCS serving satellite data
- 2) The user submits a WCS GetCoverage request that includes bounding box, time, and parameter filters
- 3) The satellite data server provides the data that meets the query criteria. In the process, the data provider may need to execute swath mosaicking and data subsetting services.
- 1.Operation succeeds and user obtains satellite dataset adhering to the requested spatial, temporal, and parameter filters.
Special Functional Requirements
NASA GSFC DISC implementation of WCS for OMI NO2 access