ProcessingLevelsSpecs Properties | 
The ProcessingLevelsSpecs type exposes the following members.
| Name | Description | |
|---|---|---|
| ExtensionData | 
            Holds data from an extended DataContract
              | |
| MaxLevel | 
            if ProcessingOption is Equidistant or UserDefined, the upper end of range, 
            or NotANumber if not applicable or set
             MaxLevel is relative to raw data, and must not include any datum offset  | |
| MinLevel | 
            if ProcessingOption is Equidistant or UserDefined, the lower end of range, 
            or NotANumber if not applicable or set
             MinLevel is relative to raw data, and must not include any datum offset  | |
| NoOfLevels | 
            careful: there can be a value for the number of levels to use, which, if 
            ProcessingOption is UserDefined, will be equal to the Length of
            UserDefLevels - but this number can also be set independently.
              | |
| Option | 
            how to do pre-processing
              | |
| ProcessedLevelsStartAtZero | 
             True if the processed levels should be forced to start at zero (MU approach)
             even if the raw data does not do so.
              | |
| TopExtension | 
             Type of top extension of processed data.
              | |
| UserDefLevels | 
            the levels for user-defined processing (absolute elevations in [m]!), or
            null if none. Must be strictly monotonically increasing.
            Apart from these, the relative min and max levels, plus the datum, from
            the raw data will also be part of the processed levels. NOTE: if you set
            an individual value within the array, you must re-process the hydraulic data.
             Levels are relative to raw data, and must not include any datum offset  |