The following functions must be set: Set(String, eumQuantity, DfsSimpleType), SetAxis(IDfsSpatialAxis).

The builder works in two stages. The first stage all header information and information of the dynamic items are provided. In the second stage static items are added. Then a dfs file is ready, and data for the dynamic items can be added.

To go from the first to the second stage by calling CreateFile(String), which will actually create a file on the disc.

To get the final file, call GetFile. After GetFile has been called, no more static items can be added to the file.

Stage 1: The following must be set during stage 1: SetGeographicalProjection(IDfsProjection), SetDataType(Int32), SetTemporalAxis(IDfsTemporalAxis). Furthermore, a number of dynamic items must be added.

Stage 2: Any number of static items can be added. Create the item by using one of the AddStaticItem(String, Array) functions. To create a new static item from scratch, use CreateStaticItemBuilder together with AddStaticItem(IDfsStaticItem).

Translates generic lists to non-generic lists that can be used through COM

With any

ref IntPtr

The following functions must be set: Set(String, eumQuantity, DfsSimpleType), SetAxis(IDfsSpatialAxis), SetValueType(DataValueType).

All methods are implemented virtual. Hence you can override just one method, if just that is to be changed, and the remainder will work as always.

It contains functionality for creating classes that are to be used when building a new file, e.g. the DfsBuilder.

This dfs file is of the type: all items, fixed space.

All methods are implemented virtual. Hence you can override just one method, if just that is to be changed, and the remainder will work as always.

Used by DfsDynamicItemDecoratorBase and Used by DfsStaticItemDecoratorBase and

The following functions must be set: Set(String, eumQuantity, DfsSimpleType), SetAxis(IDfsSpatialAxis), SetData(Array).

All methods are implemented virtual. Hence you can override just one method, if just that is to be changed, and the remainder will work as always.

Matlab issue: If having an IDfsFile then you can not cast that to IDfsFileIO in Matlab. You can only cast if having the COM class but not if having the COM interface.

The number of coordinates in each dimension is one larger than the number of data values, i.e. datavalue[i,j] belongs within the element xy(i,j)-xy(i,j+1)-xy(i+1,j)-xy(i+1,j+1) (element values)

The number of coordinates in each dimension is one larger than the number of data values, i.e. datavalue[i,j,k] belongs within the cubic element with corners xyz(i,j,k)-xy(i+1,j+1,k+1) (element values)

The user must know whether the data values are based on the coordinates (node values) or between coordinates (element values)

The user must know whether the data values are based on the coordinates (node values) or between coordinates (element values)

The user must know whether the data values are based on the coordinates (node values) or between coordinates (element values)

The user must know whether the data values are based on the coordinates (node values) or between coordinates (element values)

The number of coordinates is the same as the number of data values, i.e. each data value belongs on the coordinate (node values).

The number of coordinates in each dimension is one larger than the number of data values, i.e. datavalue[i,j] belongs within the element x[i]-x[i+1] and y[j]-y[j+1] (element values)

The number of coordinates in each dimension is one larger than the number of data values, i.e. datavalue[i,j,k] belongs within the element x[i]-x[i+1], y[j]-y[j+1], z[k]-z[k+1] (element values)

The functionality is based on a file pointer pointing into the file on the disk.

Whenever calling one of the read or write methods, the file pointer will move to the next static item or dynamic item-timestep in the file.

The methods reading the next static or dynamic item will depend on previous calls to any of the read and write methods.

The two ReadStaticItemNext and ReadItemTimeStepNext are the most efficient way of iterating through the data in the file. If iterating in another way, for example over all the time steps of one item, and then the next item, this will imply a performance hit, since the file pointer needs to be repositioned at each read. Especially fro dfs0 files this is noticable; not very much data is being read for one item timestep, and it is faster reading data sequentially than moving the file pointer.

See DfsBuilder for details

Interface containing the raw read and write functions of the dynamic items in a dfs file.

The functionality is based on a file pointer pointing into the file on the disk.

Whenever calling one of the read or write methods, the file pointer will move to the next static item or dynamic item-timestep in the file.

The methods reading the next static or dynamic item will depend on previous calls to any of the read and write methods.

The ReadItemTimeStepNext is the most efficient way of iterating through the data in the file. If iterating in another way, for example over all the time steps of one item, and then the next item, this will imply a performance hit, since the file pointer needs to be repositioned at each read.

Depending on the DataType this can be cast to a similar IDfsItemDataT and the Data can be cast to its raw array data type.

The underlying data is still stored as a 1D array and returned by the Data

Depending on the DataType this can be cast to a similar IDfsItemData2DT and the Data can be cast to its raw array data type.

The underlying data is still stored as a 1D array and returned by the Data

The underlying data is still stored as a 1D array and returned by the Data

Depending on the DataType this can be cast to a similar IDfsItemData3DT and the Data can be cast to its raw array data type.

The underlying data is still stored as a 1D array and returned by the Data

You can use the

DHI.Projections

The WKTString is a WKT string for a spatial reference system. A number of abbreviated strings also exists, i.e., "UTM-33" for a WGS-84 UTM zone 33 projection, and "LONG/LAT" for WGS-84 geographical coordinates.

There are 3 levels of coordinates: Geographical coordinates (longitude, latitude) in degrees, projection coordinates (easting, northing), and model/user defined coordinates (x,y).

All coordinates in a dfs file are stored in model coordinates.

The WKTString defines which ellipsoid the geographical coordinates use (example: WGS-84).

The WKTString defines the mapping from geographical coordinates to projection coordinates.

The Longitude, Latitude and Orientation defines the origin and the orientation of the model coordinates. It is used to move and rotate the model coordinates, i.e., a dfs2 file with a 2D equidistant axis defines its model coordinate origin and orientation here (and not in its axis definition, though that would also be possible).

See Orientation for the definition of the orientation. The model coordinates are rotated around its origin.

If Orientation is zero, and Longitude and Latitude matches the origin of the projection coordinate system, then projection coordinates equals model coordinates. Example: UTM-31 has projection origin at (lon,lat) = (3,0).

Use the TimeAxisType to get the exact type. Depending on this type, the temporal axis can be cast to one of: IDfsNonEqCalendarAxisIDfsEqCalendarAxisIDfsNonEqTimeAxisIDfsEqTimeAxis

If the time axis in the file is Undefined indicates an illegally written file, and should not happen. An exception will/should be thrown when reading the file.

The unit of the time axis can vary. To convert between a time value in the unit of the time axis and a time value in seconds, there is a number of convenience static extension methods in the DfsExtensions class, as e.g. the method ToSecondsFactor(IDfsTemporalAxis) will return a factor to use when converting a value from the specified unit to seconds.

Currently only the EqtimeFixedspaceAllitems and the NeqtimeFixedspaceAllitems is supported.