Describe the feature you'd like and what it will do
Currently, if a value fed through a rating curve transformation is out of bounds of the values defined in the table, the system sets the value to either the min or max value of this table. Instead, the value should be set to the user's defined no_data value and flagged with an out of bounds ResultQualifier.
Why is this feature important?
This approach is more explicit so the user never has to question if a value is actually the min or max of the rating curve or if something has happened to the sensor and impossible values are getting streamed into HydroServer.
Is your feature request related to a problem? Please describe.
No response
Any additional comments?
No response
Describe the feature you'd like and what it will do
Currently, if a value fed through a rating curve transformation is out of bounds of the values defined in the table, the system sets the value to either the min or max value of this table. Instead, the value should be set to the user's defined no_data value and flagged with an out of bounds ResultQualifier.
Why is this feature important?
This approach is more explicit so the user never has to question if a value is actually the min or max of the rating curve or if something has happened to the sensor and impossible values are getting streamed into HydroServer.
Is your feature request related to a problem? Please describe.
No response
Any additional comments?
No response