Rating conversion transitions / phased change

The reading workshop inclued a requirement for the inclusion of tranistions : rgs-13 - "The use of conversion transitions / phased change is in scope"

A change in applicable conversion table is controlled by adding records to the conversion period. The conversion period declares the table that is active and the date and time from which it is active. This means that there is an instantaneous switch from one conversion table to the next.

A transition is a method to define the change between two different conversion tables over a period of time rather than instantaneously.

In a stream flow context, conversion tables communicate the relationship between stream level and river flow. Changes in this relationship can be attributed to many things, for example:

1. Accumulation of algae or ice
2. Scouring and aggregation of river bed
3. Construction of a control structure
4. Destruction of a control structure

Item 4 of the change examples above could almost be considered to be an instantaneous event. Items 1-3 occur over a period of time ranging from hours to days. Representing these changes in a rating system that only allows for a change between tables at a specific date and time is problematic as it does not model the natural condition.

An example of this is a stream gauge that has high algae or aquatic weed growth during the warmer months, where the growth has a significant impact on the discharge relationship. Often the relationship can be defined for the ‘no growth’ and ‘full growth’ regimes, however definition of the relations in between these times is problematic from a resource perspective. In these instances the definition of the relationship at the extreme ends is completed and the derivation of flow from level requires a transition period to move in between the conversion tables. It is noted that alternative ultrasonic methods of flow measurement may be a better solution if available.

A common example of the impact of sudden rating changes is where a flood event has caused stream bed scour. The flood water has eroded loose sediment in the stream bed or bank, increasing the cross section area of the control section. This has the effect of ‘lowering’ the conversion table. I.e. the equivalent flow occurs at a lower stage height. Such a change in the control section will initiate a conversion table change. If this change were attributed to a single date and time during the flood event the resulting flow hydrograph would be nonsensical, thus transitioning between the tables during the event produces a more acceptable result. The following three images depict the flood event scenario and the impact on derived flow produced.

Figure 1 : Cross section change an impact on rating table

Figure 2 : Ratings applied without transition

Figure 3 : Ratings applied with transition

Below is a proposal for transitions and a comparison to the WDTF implementation for the concept.

In this diagram, the numbers in a triangle indicate a rating table number. The triangle is a conversion period entry. The WDTF model requires three converion period enties, the porposed model requires only two. The WDTF model has been confusing the some.

-- PaulSheahan - 08 Feb 2013
Topic attachments
I Attachment Action Size Date Who Comment
rating.transiton.applied.jpgjpg rating.transiton.applied.jpg manage 86.6 K 08 Feb 2013 - 05:09 PaulSheahan  
rating.transiton.change.jpgjpg rating.transiton.change.jpg manage 89.0 K 08 Feb 2013 - 05:09 PaulSheahan Flood event scours section - change in rating
rating.transiton.not-applied.jpgjpg rating.transiton.not-applied.jpg manage 74.9 K 08 Feb 2013 - 05:09 PaulSheahan  
trasnition.model.1.jpgjpg trasnition.model.1.jpg manage 31.4 K 08 Feb 2013 - 05:21 PaulSheahan  
trasnition.model.jpgjpg trasnition.model.jpg manage 31.4 K 08 Feb 2013 - 05:20 PaulSheahan  
Topic revision: r1 - 08 Feb 2013, PaulSheahan
 

This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback