|
This is version 3.
It is not the current version, and thus it cannot be edited.
[Back to current version]
[Restore this version]
Version: 1.0
Summary:
A match-up data set is obtained from the target data set and the comparison data sets. This data set consists of match-up data elements which consist of N+2 parts where N is 1 for point and line data sets and >1 for multiple field data sets (for example if there are 4 satellite-derived SST fields, on field of interpolated SST values and 3 model output fields, N would be 8): SST values and associated locational metadata for the target data set, SST values and associated locational metadata for N comparison data set (for some data comparison data sets, this will consist of one SST value and its location in space and time) and metadata further characterizing the match-up element such as the URL or name for the comparison data set, a match-up element sequence number, a space and time value for the element, etc.
- Input: The list of data sets identified by Use Case #2.
- Output: Match-up data set ==> input for the comparison use case (Use Case #4).
Preconditions:
Triggers:
Basic course of events:
- Provide match-up search parameters:
- Co-location (space and time) search radius to identify matchup
- Target data set buffer size -- size of the sub-array of the target data set to be returned as part of matchup element
- Comparison data set buffer size -- size of the sub-array of the comparison data set to be returned
- List of comparison data sets to be sampled at the same locations
- Build Matchup elements (iterate over comparison data objects and comparison data sets)
- determine match-up (space-time) location
- acquire target data set subset (data cube) extracted from the target data set
- acquire a comparison data set subset (one that meets the match-up criteria) for each of the N-2 comparison data sets to be sampled
- add additional metadata as needed
- package these data into a match-up element
- Construct integrated data set of match-up elements, and archive the result set
Alternative paths:
Postconditions:
Business rules:
Notes:
Author and date - SST Use Case Development Group 25 July 2007.
Back to the main Ocean SST page
|
