[Requests] WaterML 2.0 Hydrologic Time Series Encoding Standard Comments

Andy Rost andy.rost at noaa.gov
Fri Feb 17 17:22:20 EST 2012


See attached

-- 
Andrew Rost, Director
National Operational Hydrologic Remote Sensing Center (NOHRSC)
National Weather Service, NOAA
1735 Lake Dr. West, Chanhassen, MN 55317-8582
Voice: (952)368-2508
Cell: (952)412-9629
Fax: (952)361-6634
andy.rost at noaa.gov
http://www.nohrsc.noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20120217/69ed6e34/attachment.htm>
-------------- next part --------------
Part A to be completed once.  Iterate Part B as needed.


PART A


1. Evaluator:
Andrew Rost, Director
National Operational Hydrologic Remote Sensing Center (NOHRSC)
National Weather Service, NOAA
1735 Lake Dr. West, Chanhassen, MN 55317-8582
Voice: (952)368-2508
Email: andy.rost at noaa.gov
      

2. Submission: [OpenGIS Project Document Number, Name]
OGC 10-126r2 
http://www.opengis.net/doc/waterml/2.0 
Version: 2.0.0
OGC¨ WaterML 2.0: Part 1- Timeseries



PART B


1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Should be able to embed time series data NetCDF files within a WaterML time series file




1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Should not be forced to accept all metadata in each WaterML file. These data are relatively static, but 
may be voluminous. The client should be able to ask for a minimum set of metadata for locations that transmit data frequently. The client
should be able to ask for the full set of metadata periodically, or the server should inform the client when metadata for a given location
has changed (perhaps also sending the full set of metadata)
 



1. Requirement: General 


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Time series should indicate which observations have be revised, since first first transmittal.
The clients should be automatically informed of data revisions




1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Subsets of time series data that were subjected to data assimilation (or like process) should be indicated.
Perhaps this can be reported somehow in the process section of the message. But note that only subsets of the time series may be subject to data
assimilation.




1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Metadata for long time series may vary over time




1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Locations may not be points. For instance the mouth of the Mississippi River. The geometry for mouths of
rivers need to be characterized in order for river models to be coupled with 2D ocean models 




1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Location metadata must include horizontal and vertical datum information. The age of the data location data should
should be recorded as well, to allow the client to adjust for phenomena such as continental rebound




1. Requirement: General


2. Implementation Specification Section number: General


3. Criticality: Major


4. Comments/justifications for changes: Sampling feature collections should include full topology (reflecting discharge point (stream) order, for instance, in a collection of
basins in a National Weather Service forecast group) (island features, such as reservoirs w/in a basin) 




More information about the Requests mailing list