Page History

...

Name of a location index set variable in the NetCDF file that contains the indices of the locations at which the data is defined. The location index set variable in the NetCDF file should point to a mesh topology variable and a (stagger) location within the mesh. This is only supported if the location index set variable in the NetCDF file contains coordinates (i.e. a coordinates attribute that points to coordinate variables that contain only coordinates for the index set, not for the entire mesh).

Using a UGRID NetCDF file as unstructured grid definition

To import/export unstructured grid/flexible mesh data in Delft-FEWS, use a timeSeriesImport/ExportRun with type "NETCDF-CF_GRID" or use a generalAdapter import/exportNetcdfActivity. For this to work you need to add an irregular grid definition to the grids.xml configuration file. The easiest way to do this, is by using the option "netcdfFile" (see above) that refers to a NetCDF file that contains a UGRID mesh topology (and no data).

It is possible to use a D-Flow flexible mesh (D-Flow FM) flowgeom UGRID NetCDF file, produced by a D-Flow FM model run, as grid definition in Delft-FEWS. If your D-Flow FM model run does not produce a flowgeom file, then add the following line in the D-Flow FM .mdu file in the output section, e.g.:

[output]
...
FlowGeomFile    = f34_flowgeom.nc    # *_flowgeom.nc Flow geometry file in NetCDF format.
...

If the produced flowgeom file is not in UGRID NetCDF format, then you can change the format to UGRID NetCDF by changing the MapFormat to 4 in the D-Flow FM .mdu file in the output section:

[output]
...
MapFormat    = 4    # Map file format, 1: netCDF, 2: Tecplot, 3: netCFD and Tecplot, 4: NetCDF-UGRID
...

The flowgeom file format matches the map file format.

Config Examples

<irregular locationId="meshLocation">
	<netcdfFile>
		<file>simplebox_hex7_map.nc</file>
		<meshTopologyVariableName>mesh2d</meshTopologyVariableName>
		<staggerLocation>face</staggerLocation>
	</netcdfFile>
</irregular>

...