DFS0-Format: Difference between revisions

From BlueM
Jump to navigation Jump to search
(added Dfs0 export (since Wave 1.12))
No edit summary
 
Line 1: Line 1:
{{Wave_nav}}
{{Wave_nav}}


The Dfs0 file format is a proprietary binary time series format developed by [https://www.dhigroup.com/ DHI] and is used in various [https://www.mikepoweredbydhi.com/ MIKE] products.
The DFS0 file format is a proprietary binary time series format developed by [https://www.dhigroup.com/ DHI] and is used in various [https://www.mikepoweredbydhi.com/ MIKE] products.


BlueM.Wave can read time series from Dfs0 files provided that the files use a calendar-based time axis and can also export to Dfs0 format.
File format documentation: https://docs.mikepoweredbydhi.com/core_libraries/dfs/dfs-file-formats/#dfs0-file


File format documentation: https://docs.mikepoweredbydhi.com/core_libraries/dfs/dfs-file-formats/#dfs0-file
BlueM.Wave can read time series from DFS0 files provided that the files use a calendar-based time axis.
 
BlueM.Wave can also export one or more time series to DFS0 format.
 
Automatic conversion between Wave Interpretations and DFS0 DataValueTypes:
{| class="wikitable"
! Interpretation !! DataValueType
|-
| Instantaneous || Instantaneous
|-
| BlockLeft || MeanStepBackward
|-
| BlockRight || MeanStepForward
|-
| CumulativePerTimestep || StepAccumulated
|-
| Cumulative || Accumulated
|-
| Undefined || Instantaneous
|}
 
==Notes==
* If more than one time series is exported to one DFS0 file, any missing timestamps in any of the time series are filled with NaN (DFS0 <code>DeleteValue</code>).
* Time series values are always exported with DataType <code>DfsSimpleType.Double</code>
* Most MIKE products only accept DFS0 files as input if the item type (e.g. "Discharge" or "Rainfall") corresponds to what it expects. As Wave cannot automatically derive the item type, the user has to manually set the item type (and corresponding unit) when exporting to DFS0. Item types and corresponding units for DFS0 files are managed using DHI's so-called EUM (Engineering Unit Management), which defines approx. 600 item types (<code>eumItem</code>) and another 600 units (<code>eumUnit</code>). In order to make item and unit selection usable, only a small subset of hydrology-related items and units can currently be selected when exporting to DFS0.


[[Category:BlueM.Wave]]
[[Category:BlueM.Wave]]
[[Category:Timeseries formats]]
[[Category:Timeseries formats]]

Latest revision as of 12:05, 13 January 2022

Wave.png Wave | Development

The DFS0 file format is a proprietary binary time series format developed by DHI and is used in various MIKE products.

File format documentation: https://docs.mikepoweredbydhi.com/core_libraries/dfs/dfs-file-formats/#dfs0-file

BlueM.Wave can read time series from DFS0 files provided that the files use a calendar-based time axis.

BlueM.Wave can also export one or more time series to DFS0 format.

Automatic conversion between Wave Interpretations and DFS0 DataValueTypes:

Interpretation DataValueType
Instantaneous Instantaneous
BlockLeft MeanStepBackward
BlockRight MeanStepForward
CumulativePerTimestep StepAccumulated
Cumulative Accumulated
Undefined Instantaneous

Notes

  • If more than one time series is exported to one DFS0 file, any missing timestamps in any of the time series are filled with NaN (DFS0 DeleteValue).
  • Time series values are always exported with DataType DfsSimpleType.Double
  • Most MIKE products only accept DFS0 files as input if the item type (e.g. "Discharge" or "Rainfall") corresponds to what it expects. As Wave cannot automatically derive the item type, the user has to manually set the item type (and corresponding unit) when exporting to DFS0. Item types and corresponding units for DFS0 files are managed using DHI's so-called EUM (Engineering Unit Management), which defines approx. 600 item types (eumItem) and another 600 units (eumUnit). In order to make item and unit selection usable, only a small subset of hydrology-related items and units can currently be selected when exporting to DFS0.