Difference between revisions of "User access to satellite data"
From Earth Science Information Partners (ESIP)
Line 1: | Line 1: | ||
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: | 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. | 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. |
Revision as of 16:30, January 15, 2007
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.