ResultData Properties

Get the bridge that was used for loading/saving

List of catchments

Flag indicating whether data items are cleared when flushing to file

Default is false.

Holder of read/write information

List of custom types stored in the data object and that must be serialized.

A custom type is e.g. a user implemented structure or catchment model. In order to store information on the custom type in the .m1dx file, the system needs to know which custom types are being used, and they must be added to this list.

Get an iterator that iterates over all data items

Get an iterator that iterates over all data sets

Delete value for double variables. Any double data value with this value should be treated as a missing value.

Data coverage end

Holds data from an extended DataContract

Global data. Valid for entire network

The MaxBufferSize is the limit for how many time steps that may be held in memory during file generation.

Static data on the network.

Used for user defined markers from MIKE 11 and Critical Levels in MU.

Static data on the network.

Also used for user defined markers from MIKE 11

List of nodes

Number of time steps

Parameters to use when loading results

A WKT string for a spatial reference system.

List of the contained quantities. Note: This is a derived property

List of branches

Reader used for reading the result file.

Result specification

Result type

Seconds between flush to file. Set this lower if you need to read the result file while your calculations are running. WARNING: File flush is a potentially expensive operation. Use with care.

Data coverage start

List of the contained quantities. Note: This is a derived property

Resultdata subscribes to the TimeStepPerformed(DateTime) event. Set this to non-zero to control how often data are stored. For non-zero values there will be AT LEAST TimeBetweenUpdates between store times in ResultData

Time axis for the data.

Timers used for flushing

Timers used for flushing

Unit system of the simulation that produced the result data object.

When creating a result data object and storing: Properties of ResultData objects (coordinates, bottom levels etc.) must always be set in SI units.

When loading a result data object from storage: The UnitSystem and ConvertGeometry can be used to change units of data and properties in the Result Data object. This property will maintain the original value and will not be changed by updating the IResultDataParameters