RGS activity register
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNO
1
Inlcuded as a requirement in specification?Approval process and status
2
Date proposed
Item IDStatusItem typeOwnerDescriptionDecision proposed dateReview period ends dateStatus after reviewResolutionSupported in information model?Tested in implementation (in IE)?Tested in IE?
3
21/6/2012rgs-01OngoingScope decision - RatingReading groupGeneralised conversion relationships are implemented rather than Stage/Flow only relationships. This enable relationships between user specified parameters to be defined.YYYYes. Existing structures are flexible for different parameter conversions.
4
21/6/2012rgs-02OngoingScope decision - RatingReading groupThe WML2 RGS implementation contains data used to complete the calculation of derived information. The definition of the process that would be employed to complete the transfer function / transformation is not currently in scope, my may be in scope at a later revisionYYYYes, current implementation reflects this.
5
21/6/2012rgs-03OngoingScope decision - RatingReading groupCommuncating the gaugings used in the creation of a rating is in scope. The gaugings if interest are
* Gaugings used that were taken in the period of application of the rating
* Gaugings not used that were taken in the period of application period of the rating
* Gaugings used that we taken outside the application period of the rating. - e.g. high flow rating
YYNThe information model supports this. However the implementations do not. This is becuase the underlying information systems currently do not tracl this information.
6
21/6/2012rgs-04OngoingScope decision - RatingReading groupThe inclusion of user specified user information that varies across the Y scale of a conversion is in scope. This would be used to give further information for the conversion. e.g. Control/Chanel/OverBankFlow Assessment of other sensor application rangeYNRANGE VALUES - TODO.
7
21/6/2012rgs-05OngoingScope decision - RatingReading groupRatings should always have a point table supplied that is expanded at a sufficient Y scale resolution to enable linear interpolation between the supplied points. The creator of the data file will choose the export resolution such that linear interpolation is appropriate.YYYYes. This has been tested and seems to be a reasonable solution. Do we need a metadata element indicating the resolution that they have been expanded at?
8
21/6/2012rgs-06OngoingScope decision - RatingReading groupRatings may have the equation that is the source system definition of the rating. This may be supplied using rgs-4.YCapability delivered though range value tablesYNYes, supported in the information model. No implementation examples exist, yet.
9
21/6/2012rgs-07OngoingScope decision - RatingReading groupA point rating table may have additional information that enables the source system to describe how it stored the table.YYNYes, supported in the information model. No implementation examples exist, yet.
10
21/6/2012rgs-08OngoingScope decision - RatingReading groupThe implementation of loop rating curves is out of scope. Methods of implementation are possible, however the practical uptake of loop ratings means the topic is very much an edge case. It is understood that issues of uncertainty outstrip the accuracy issues that loop ratings address. Technology has provided other solutions through the use of velocity index tables and velocity sensing hardware.NANAN/A - scoping.
11
21/6/2012rgs-09OngoingScope decision - RatingReading groupReverse conversions are not supported implicitly by either point or equations conversions. Reverse conversions can be defined explicitly.YYSupported by reverse tables.
12
21/6/2012rgs-10OngoingScope decision - RatingReading groupRatings are keyed to a Site / Point / ParameterFrom / ParameterTo.YYYYes. We changed this approach for a while but now key on MP/paramFrom/To.
13
21/6/2012rgs-11OngoingScope decision - RatingReading groupWhen defining stage as a parameter for a conversion, the stage datum must be supplied.YYNYes supported by information model. Not tested directly by the IE.
14
21/6/2012rgs-12OngoingScope decision - RatingReading groupScope decision : The ratings being communicated are the 'Active ratings'. The ratings that would be applied to determine ParameterTo value. It will have been shift corrected and will be the active rating at the time. Return should indicate the date and time for wich the data applied
15
21/6/2012rgs-13OngoingScope decision - RatingReading groupThe use of conversion transitions / phased change is in scopeYYNSupported by information model, but not tested directly in information model.
16
21/6/2012rgs-14OngoingScope decision - RatingReading groupThe use of start dates for a conversions period is agreed.YYYYes, conversion period start dates were the primary rating period approach.
17
21/6/2012rgs-15OngoingScope decision - RatingReading groupThe use of end dates for a conversions period is agreed. The end dates is purely used for describing a gap. Rating gap periods can be implemented by end dates a or a null rating.YYNYes implemented in the IE, but an explicit end date was not tested?
18
21/6/2012rgs-16OngoingScope decision - RatingReading groupRating point quality codes will be implemented at the point level. A rating quality can be defaulted with overrides for each point. Rating quality can be applied to equations. Rating quality can be communicated via an input range. YYYYes point quality for tables is supported in information model and implemented in the IE. A range values approach has not yet been tested.
19
22/6/2012rgs-17OpenAction ItemPaul SheahanComplete a first draft of the RGSWG activity schedule for the next 12 months.31/08/2012Key milestones have been noted as the most important part -- the underlying modelling will progress to deliver on these milestones. Identifying the key topics for review from RGS group is important (not just review the whole model).
20
22/6/2012rgs-18OpenDecisionReading groupGovernance details developed22-Jun-20126-Jul-2012
21
22/6/2012rgs-19ClosedAction ItemPeter TaylorCreate RGS WG email list
22
22/6/2012rgs-20OngoingScope decision - RatingReading groupConversions can specify Y scale range validated range (within rating), extrapolated range, beyond extrapolation.26/7/2012Should a range table wit ha predefined name be used to provide this functionality?YNSupported in information model, not tested in IE.
23
22/6/2012rgs-21OngoingScope decision - RatingReading groupThere is a need for defining an input range purpose. An input range purpose should be a controlled vocabulary, the semantic meaning of each input range purpose should be defined against the vocabulary. Input range contents may vary over time, so should be referenced by periods of applicability.YNPartially duplicating range values requirement.
24
22/6/2012rgs-22OngoingScope decision - RatingReading groupThe format should enable the inclusion of metadata to enable the communication ratings approval and review process YYN
25
22/6/2012rgs-23OngoingScope decision - RatingReading groupThe application of 3d ratings is a stretch gaol. As such it is out of scope until scope is reviewedNeeds review
26
22/6/2012rgs-24OngoingScope decision - RatingReading groupWe supply conversion information that is able to be used in simple or complex conversion chains. Communication of information that defines the 'chain conversion process' or 'work flow' of simple or complex chain conversions in not in scope. NANAScoping
27
22/6/2012rgs-25OngoingScope decision - RatingReading groupSpecific methods for the communication of uncertainty information are not currently agreed across the domain. This is an area of current domain development. The standard should be sufficiently extensible to enable incorporation when a direction is available.YY
28
22/6/2012rgs-26OngoingScope decision - GaugingReading groupA RatingObservation is a summary result of the gauging activity, it is not a detail of the measurements taken to determine the gauging result.
29
22/6/2012rgs-27OngoingScope decision - GaugingReading groupRatingObservations need to be connected to the rating for which they apply. This may be by direct, linked or other methods
30
22/6/2012rgs-28OngoingScope decision - GaugingReading groupThe rich suite of USGS site visit information is out of scope for this activity
31
22/6/2012rgs-29OngoingScope decision - GaugingReading groupRating type specialised metadata. Stream discharge RatingObservations have specific metadata that is of value and should be communicated. Other ratingObservations would not be required to contain this information.
32
22/6/2012rgs-30OngoingScope decision - GaugingReading groupRatingObservations may be used by one or many ratings.
33
22/6/2012rgs-31OngoingScope decision - GaugingReading groupRating type specialised metadata. A WQ sepecialsed type is in scope as a stretch gaol. External input would be required to determine the content
34
22/6/2012rgs-32OpenAction ItemPaul SheahanA high level description of the WML.P2 purpose should be written. This description will enable user to understand the WML2.P2 purpose and assess it against their needs to determine if it is appropriate to their usage.
35
22/6/2012rgs-33OngoingScope decision - GaugingReading groupA RatingObservation contains a definition of From and To parameters. The observations is not limited to stream discharge observations.
36
22/6/2012rgs-34OngoingScope decision - GaugingReading groupRatingObservations must be able to be delivered seperate from ratings. Rating observation may optionally be delivered inline with rating details
37
22/6/2012rgs-35OngoingScope decision - SectionsReading groupThe WDTF model can be used as a base definition of requirements.
38
17/8/2012rgs-36OngoingScope decision - RatingPaul SheahanThe conversion application period list may refer to a conversion table more than once. e.g. a conversion table is reused31/08/2012Accepted - 19/9/2012YY
39
17/6/2012rgs-37OpenScope decision - RatingPaul SheahanA range value may refer to to a specific value, rather than a range. An example is references to flood extent polygons, the flood extent relates to a specific Y scale value and is not valid for a ranged of Y values (the range is vary narrow).Next meeting
40
13/11/2012rgs-38OpenQuestion - RatingPeter TaylorDoes a coversion always apply to the same ParamFrom? /ParamTo and Site/MonitoringPoint? RGS 36. There was discussion of engineered structures and conversions that are re-used across sites, e.g. flume relationships. How do these get identified? For actual use they would be 'bound' to a site.

Response :
Next meetingAccepted 14/12/12 telconTying a conversion to a monitoring point is acceptable, the use of generalised conversions across several sites is not supported.
There is a need to get better defintion around a site(consists of several monitoring locations)
NANAScoping
41
13/11/12rgs-39ClosedAction ItemPeter TaylorNeed a glossary. What are: Conversions, Ratings, Gaugings and where do they differ? This should reflect in the class naming (that needs some refinement for consistency). created at http://external.opengis.org/twiki_public/HydrologyDWG/RGSGlossaryOfTerms
42
13/11/12rgs-40OpenQuestion - GaugingsPeter TaylorMetadata for including/excluding gauging observations as references. Do we need the reason they were excluded/included? Examples of this in practice? We modelled this but not currently shown in the above model.Out of scope 14/Dec/12 telconThis was considerd to be an stetch goal that may be included in a next version.
43
29/11/12rgs-41OpenQuestion - RatingsPeter TaylorRE : rgs-22
Should we define a vocabulary supporting conversion release status?
Do we want to harmonise an initial set of codes? NWIS ones here: http://water.usgs.gov/XML/NWIS/5.0/ReferenceLists/DataAgingList.xml
To be included - 14/Dec/12 TeleconA vocabularly should be defined.
44
29/11/12rgs-42OpenQuestion - RatingsPaul Sheahanre rgs-7.
Is there a need to implement shifts to enable the actual source system representation?
Is rgs-7 a free form extension point that would implement a specific data systems information model?
Out of scope 14/Dec/12 telconAny representation of shifts would need to completed within extension to enable a user system data to be communicated - out of scope for the core model.
45
30/8/13rgs-43ClosedQuestion ratingsPaul SheahanThe ratings model should support the ability to determine if a rating has changed since last acquired. e.g. Date of last modification stored against period?20/9/1327/9/13AgreedAgreed at telecon 27 Sep 2013
46
30/8/13rgs-44ClosedQuestion ratingsPaul SheahanShould a rating table have an optional element of 'UseByDate'? Where a web service call delivers the 'current' rating, how long should it be used before being considered to be stale?20/9/1327/9/13RejectedAgreed at telecon 27 Sep 2013
47
19/9/13rgs-45ClosedQuestion ratingsPaul SheahanChange RGS-12 to "The ratings being communicated are the 'Active ratings'. The ratings that would be applied to determine ParameterTo value. Return should indicate the date and time for which the data applied"27/9/13Change to include actinve + ActiveShiftedAgreed at telecon 27 Sep 2013Revised wording :

The modelling of ratings will support the capture of Ratings and Shifts. Transfer documents will support the transfer of this information, additionally, transfer documents will support web service calls that deliver the ‘current rating’. In an organisation that uses rating shifts, this would be a shifted rating. The document should have the ability to indicate that the latest rating has been provided along with its shift status.
48
19/9/13rgs-46ClosedQuestion ratingsPaul SheahanNew ratings requirement proposed : "The support of stage and time shifts is in scope for the Ratings model"27/9/13AgreedAgreed at telecon 27 Sep 2013
49
rgs-47
50
rgs-48
51
rgs-49
52
rgs-50
53
rgs-51
54
rgs-52
55
rgs-53
56
rgs-54
57
rgs-55
58
rgs-56
59
rgs-57
60
rgs-58
61
rgs-59
62
rgs-60
63
rgs-61
64
rgs-62
65
rgs-63
66
rgs-64
67
rgs-65
68
rgs-66
69
rgs-67
70
rgs-68
71
rgs-69
72
rgs-70
73
rgs-71
74
rgs-72
75
rgs-73
76
rgs-74
77
rgs-75
78
rgs-76
79
rgs-77
80
rgs-78
81
rgs-79
82
rgs-80
83
rgs-81
84
rgs-82
85
rgs-83
86
rgs-84
87
rgs-85
88
rgs-86
89
rgs-87
90
rgs-88
91
rgs-89
92
rgs-90
93
rgs-91
94
rgs-92
95
rgs-93
96
rgs-94
97
rgs-95
98
rgs-96
99
rgs-97
100
rgs-98
Loading...
Main menu