MIKE Zero Toolbox: User Guide
MIKE Zero Toolbox: User Guide
User Guide
MIKE 2017
2
PLEASE NOTE
LIMITED LIABILITY The liability of DHI is limited as specified in Section III of your 'DHI
Software Licence Agreement':
3
4 MIKE Zero Toolbox - © DHI
CONTENTS
MZ Tools: Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 Select Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2 Subseries Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3 Item Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
MZ Tools: Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2 Extraction of Time Series from 1D Data . . . . . . . . . . . . . . . . . . . . . 17
2.1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Subseries Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3 Item Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4 Point Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.5 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3 Extraction of Time Series from 2D Data . . . . . . . . . . . . . . . . . . . . . 19
3.1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2 Subseries Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Item Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.4 Item Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.5 Point Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.7 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4 Extraction of Time Series from 3D Data . . . . . . . . . . . . . . . . . . . . . 23
4.1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2 Subseries Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3 Item Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.4 Point Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.5 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5 Extraction of Profile series from 2D Data . . . . . . . . . . . . . . . . . . . . 27
5.1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5
5.2 Subseries Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Item Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.4 Line Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.5 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6 Extraction of Profile series from 3D Data . . . . . . . . . . . . . . . . . . . . 29
6.1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2 Subseries Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.3 Item Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.4 Line Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.5 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7 Extraction of 2D time series from 3D Data . . . . . . . . . . . . . . . . . . . 31
7.1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.2 Subseries Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.3 Matrix Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MZ Tools: Hydrology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
15 Maximum Rainfall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
15.1 Input File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
15.2 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7
15.3 Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
15.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
16 Mean Area Weighting Algoritm . . . . . . . . . . . . . . . . . . . . . . . . . . 67
16.1 Weighted Average dfs File Input . . . . . . . . . . . . . . . . . . . . . . . . . 67
16.2 Weighted Average Weight Combination . . . . . . . . . . . . . . . . . . . . . 67
16.3 Temporal Distribution dfs Input File . . . . . . . . . . . . . . . . . . . . . . . 67
16.4 Temporal Distribution Weight Combinations . . . . . . . . . . . . . . . . . . 67
16.5 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
16.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
17 Normalize Rainfall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
17.1 Normalize Rainfall Input Files . . . . . . . . . . . . . . . . . . . . . . . . . . 69
17.2 Normalize Rainfall Output File . . . . . . . . . . . . . . . . . . . . . . . . . . 69
17.3 Normalize Rainfall Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 69
18 Runoff Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
18.1 Input Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
18.2 Accumulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
18.3 Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
18.4 Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
18.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
9
24.6 Data Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
24.7 Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
24.8 Save Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
24.9 Output Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
24.10 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
24.11 Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
24.12 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
24.12.1 ASCII to dfs0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
24.12.2 Excel to dfs0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
11
The CONCATENATION Tools in the MZ Toolbox include the facility:
Concatenation
1 Concatenation
You can use this tool to concatenate files in dfs format, i.e. items from N dif-
ferent files will be joined in a single output file.
The input files that lies in this period will be concatenated in the output. You
may set a time step (in an integer number of time steps) for the concatenated
output.
The item numbers must be ascending and each item number can only be
used once.
1.4 Options
On this page you may specify three options.
13
Concatenation
1.6 Overview
The overview page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
15
The EXTRACTION Tools in the MZ Toolbox include the facilities:
2.1 Input
On this page you select the file with 1D data from which you want to extract
point values.
You can also specify a decimal point and the program will interpolate between
values in the file.
NOTE: If you want to write the output to an old format time series file (exten-
sion .dt0), you should limit the number of output items to a maximum of 16.
That is the number points times the number of selected input items should be
less than 16.
17
Extraction of Time Series from 1D Data
2.6 Overview
The overview page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
Given an input 2D data file and a number of discrete points (in the figure just
one), the tool extracts the values from the 2D data set at the points within a
given period.
3.1 Input
On this page you select the file with 2D data from which you want to extract
point values.
NOTE: This functionality must be used with care for MIKE SHE files as the
values from a MIKE SHE grid is grid centred.
19
Extraction of Time Series from 2D Data
If you choose to extract vectors, you can choose between the following
options:
Magnitude = V x2 + V y2 (3.1)
Vy
Direction = 90 – tan– 1 ------ + TrueNorth (3.2)
V x
If you chose to extract the components as scalars, the points are extracted in
the coordinates (j,k) you specify in the list on this page.
If you chose to extract items as vectors, the points are not extracted in the
exact coordinate that is specified in the list, but from a location placed half a
grid cell down and to the left, respectively, see image below. If you for
instance extract the magnitude and direction in a point with the coordinates
(j,k), you will get the magnitude and direction based on model results in the
points P(j,k) and Q(j,k) as illustrated below.
NOTE: If you want to write the output to an old format time series file (exten-
sion .dt0), you should limit the number of output items to a maximum of 16.
That is, the number of points times the number of selected input items should
be less than 17.
3.7 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or execute the set-up.
21
Extraction of Time Series from 2D Data
4.1 Input
On this page you select the file with 3D data from which you want to extract
point values.
If you choose to extract vectors, you can choose between the following
options:
Magnitude = V x2 + V y2 + V z2 (4.1)
V
DirectionXY = tan– 1 -----y- (4.2)
V x
Vz
DirectionZ = tan–1 ----------------------- (4.3)
V x2 + V y2
23
Extraction of Time Series from 3D Data
If you chose to extract the components as scalars, the points are extracted in
the coordinates that you specify in the list on this page.
If you chose to extract some of the items as vectors, the points are not
extracted in the exact coordinate that is specified in the list on this page, but
in the points in between the grid points of the original file. e.g if you specified
that you want ex. the magnitude and direction in the coordinates P on
Figure 4.1, you will get the magnitude and direction in the points u, v and w.
On a staggered grid, that is.
NOTE: In the present version you can only select point at the exact grid
points, i.e. the tool cannot do any spatial interpolation
NOTE: If you want to write the output to an old format time series file (exten-
sion .dt0), you should limit the number of output items to a maximum of 16.
That is the number points times the number of selected input items should be
less than 16.
4.6 Overview
The overview page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
25
Extraction of Time Series from 3D Data
5.1 Input
On this page you select the file with 2D data from which you want to extract
profile series.
NOTE: This functionality must be used with care for MIKE SHE files as the
values from a MIKE SHE grid is grid centred.
Specifying the line spacing is specifying how many points you want the line to
be split in, e.g. how many points between "start point" and "end point".
If you have specified to extract some of the items as vectors, the points are
not extracted in the exact coordinates on the line that you specified, but in
points in between the grid points. e.g if you specified that you want a line
going through the coordinates (j,k) in Figure 5.1, the program will calculate
the vector components in the points P(j,k) and Q(j,k), which are afterwards
projected on the line you specified.
27
Extraction of Profile series from 2D Data
NOTE: If you have specified one line only the geographical position of the ori-
gin and the direction of the line is saved in the dfs1 file for GIS purposes.
NOTE: If you want to write the output to an old format profile series file
(extension .dt1), you should limit the number of output items to a maximum of
16. That is the number lines times the number of selected input items should
be less than 16.
5.6 Overview
The overview page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
6.1 Input
On this page you select the file with 3D data from which you want to extract
profile series.
Specifying the line spacing is specifying how many points you want the line to
be split in, e.g. how many points between "start point" and "end point".
If you have specified to extract some of the items as vectors, the points are
not extracted in the exact coordinates on the line that you specified, but in
points in between the grid points. e.g if you specified that you want a line
going through the point P on the picture below, the program will calculate the
vector components in the points u, v and w, which are afterwards projected
on the line you specified.
29
Extraction of Profile series from 3D Data
NOTE: If you want to write the output to an old format profile series file
(extension .dt1), you should limit the number of output items to a maximum of
16. That is the number lines times the number of selected input items should
be less than 16.
6.6 Overview
The overview page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
7.1 Input
On this page you select the file with 3D data from which you want to extract
2D time series.
The "Data Information" on the right hand side of the dialogue is the size of the
3D matrix in your input file.
You can define your own subarea, to be extracted to your output file, on the
left-hand side.
NOTE: If you want to write the output to an old format 2D time series file
(extension .dt2), you should limit the number of output items to a maximum of
16. That is the number lines times the number of selected input items should
be less than 16.
7.5 Overview
The overview page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
31
Extraction of 2D time series from 3D Data
33
The FILE CONVERTER Tools in the MZ Toolbox include the facilities:
This tool has been implemented to create a DHI world file that contains the
geo-referencing parameters for a given image file.
Bitmap (.bmp)
JPEG (.jpg)
GIF (.gif)
PNG (.png)
TIF (.tif)
The image file chosen may already be accompanied by a world file. Sup-
ported formats are:
35
Geo-Referencing Image File
In all cases, the tool will use the information contained in the world file to cal-
culate the geo-referencing information.
Note that ESRI world files may contain rotation information, which is not sup-
ported by the tool.
NOTE: If a geo-referencing file already exists for the image, you only get the
option to change the map projection.
8.3 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or Execute the set-up.
The created DHI World file with the geo-referencing information will have the
same name as the image file with an additional ‘w’ in the end of the exten-
sion, i.e. bmpw, jpgw, gifw, pngw or tifw.
9 Mesh Converter
This tool imports bathymetry information in specific formats and converts the
information into a MIKE Zero mesh file that can readily be used in the MIKE
Powered by DHI software models.
For Non-MZ bathymetry data it is necessary to define the map projection that
the (X,Y) coordinates in the input data file is referring to.
NOTE: The nodes in the input file needs to be saved in increasing order. E.g.
when converting a .2dm file to a .mesh file, the .2dm file’s nodes need to be
renumbered first in the SMS, so the Mesh Converter tool can find the correct
information about the elements and nodes when the format changes.
Only the node information for nodes on external boundaries are in transferred
to the resulting mesh file. The attribute for nodes within the mesh are per
default set to 0.
37
Mesh Converter
In case the bathymetry data is from a curvilinear grid, enable the Curvilinear
grid check-box and browse and select the dfs2 file containing the (X,Y) coor-
dinates relating to the bathymetry data.
The geographical information for the mesh file is derived from the input
bathymetry file.
NOTE: In case the bathymetry file contains a M21_Misc custom block, only
elements containing values below the land value are included in the gener-
ated mesh.
NOTE: The bathymetry data is per default derived from the first time step and
the first dynamic item in the dfs2 file. In the special case where the dfs2 file
contains one, and only one, static item (e.g. as for a MIKE 21 HD output file)
the bathymetry data is derived from the static item.
Specify the units of the (X,Y) coordinate and the Z-value, respectively.
Meter
Feet
US survey feet
Meter
Feet
US survey feet
Specify the units of the (X,Y) coordinate and the Z-value, respectively.
The geographical (X,Y) coordinate must be specified using one of two units:
Degree
Radians
Meter
Feet
US survey feet
Triangular
Quadrilateral
Note that grid cells containing land values will not be included in the resulting
mesh file.
9.8 Overview
Setup status: review the parameters. If you want to change any settings, go
back; if you are satisfied with the settings click Execute, or just Finish to save
the setup for later.
39
Mesh Converter
9.9 Examples
You can access the tool from the MIKE Zero toolbox.
.\MIKE Zero\Examples\MIKE_Zero\Toolbox\FileConverter\MeshConverter.
The resulting meshes are shown below.
41
Mesh Converter
The input file is an ASCII file containing bathymetry data in ADCIRC format
(.14). The file first defines the location of the individual node points, next the
elements with associated node numbers.
The mesh is created using map projection UTM-32 and the (X,Y) coordi-
nate unit and the unit for the z-values in the input are specified as meter.
Note that for an ADCIRC bathymetry the depth values are automatically mul-
tiplied with -1 before the mesh is saved.
43
Mesh Converter
The input file is an ASCII file containing bathymetry data in SMS/TuFlow for-
mat (.2dm). The file first defines the elements with associated node numbers,
next the location of the individual node points.
The input file is a dfsu result file from a MIKE 21 FM simulation. The original
bathymetry information is extracted from the static item along with information
about code values.
45
Mesh Converter
47
The GIS Tools in the MZ Toolbox include the facilities:
GIS - Grd2Mike
GIS - Mike2Grd
GIS - Mike2Shp
GIS - Mike2Txt
GIS - Shp2xyz
10 GIS - Grd2Mike
This tool has been implemented to transform ESRI’s Ascii Grid files (*.asc)
into MIKE21 grid data files (.dfs2).
Figure 10.1 Example of input asc file. Only part of file (the top) is shown)
The tool assumes that the levels and grid spacing units are in metres.
10.1 Input
On this page the ArcView Ascii Grid file (*.asc format) where data should be
extracted from is selected. To select the file either type the full path or browse
for the file.
NOTE: The tool assumes that the levels and grid spacing units are in metres.
49
GIS - Grd2Mike
10.4 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or Execute the set-up.
11 GIS - Mike2Grd
This tool has been implemented to transform MIKE 21 grid data files into
ASCII data in ESRI’s Grid format.
Note: Import of raw ASCII data as a layer using ‘Add Data’ in ArcGIS may
result in a misleading color ramp. Optionally use instead
ArcGIS Toolbox->Conversion->To Raster->ASCII to Raster.
Note: This tool only works correctly with a grid-orientation of 0 deg.N and a
grid spacing that is the same in both X- and Y-direction.
Figure 11.1 Example of resulting asc file. Only part of file (the top) is shown)
11.1 Input
On this page the MIKE 21 (*.dt2 or *.dfs2 formats) file where data should be
extracted from is selected. To select the file either type the full path or browse
for the file.
Once the input file has been specified, the program requires the user to
define only one item which will be transformed.
Note: This tool only works correctly with a grid-orientation of 0 deg.N and a
grid spacing that is the same in both X- and Y-direction.
51
GIS - Mike2Grd
Beware that there will be generated one output file for each selected Time
Step. Each file will be postfixed with the Time Step number, e.g. having spec-
ified the output file C:\output.asc and selected time step 1 and 112 will cause
the generation of the two output files C:\output001.asc and C:\output112.asc.
11.4 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or Execute the set-up.
12 GIS - Mike2Shp
This tool has been implemented to transform dfs files into ESRI’s ArcView
shapefile format files.
12.1 Input
On this page you specify the dfs file and item(s) from where data should be
extracted. The input file may be one of three types
dfs2 file
dfsu file
mesh file
Once the input file and item(s) has been specified, the selected items is
shown for reference.
NOTE: The field name for each item in the resulting shape file will be created
using maximum 10 characters. Special characters such as ‘.’ and ‘,’ in the
item name will be omitted.
NOTE: In case the 3D dfsu file is defined by a sigma-Z level grid, each layer
must be extracted beforehand, e.g. by Data Extraction FM, and converted
individually to shape files.
The applied domain area and map projection is shown for reference.
Note that each combination of selected time step (and layer number) will be
handled individually and the output will be saved in separate output files,
postfixed with the Time Step number (and layer number).
A shape file (.shp), also called the main file, containing the geometric
objects (points or polygons)
53
GIS - Mike2Shp
An index file (.shx), containing file positions of the records in the main file
A database file, (.dbf), containing the actual data values extracted from
the data of the input data file
The output files will be postfixed with the Time Step number (and layer num-
ber)
The actual number of output files depends on type of input file and the
selected number of time steps (and layers).
1. A shape file (and accompanying index, projection and DBF files) describ-
ing the cell values by a point feature layer. The points are positioned in
the centre of each grid cell.
(naming convention: globalname_nodes_timestepnumber.*)
2. A shape file (and accompanying index, projection and DBF files) describ-
ing the cell values by a polygon feature layer. The polygons represent
the extension of each grid cell.
(naming convention: globalname_cells_timestepnumber.*)
For a 2D dfsu file the node values and element values in the dfsu file are
saved in separate shape files.
1. One shape file (and accompanying index, projection and DBF files) con-
taining the bathymetry of the nodes by a point feature layer.
(naming convention: globalname_Nodes.*)
2. A shape file (and accompanying index, projection and DBF files) for each
selected time step containing the selected element values by a polygon
feature layer.
(naming convention: globalname_elements_timestepnumber.*)
For a 3D dfsu file the node values and element values in the dfsu file are
saved in separate shape files.
1. A shape file (and accompanying index, projection and DBF files) for each
selected layer containing the level of the nodes by a point feature layer.
(naming convention: globalname_Nodes_Layerlayernumber.*)
2. A shape file (and accompanying index, projection and DBF files) for each
selected time step and each selected layer containing the selected ele-
ment values by a polygon feature layer.
(naming convention: globalname_elements_Layerlayernumber_time-
stepnumber.*)
For a mesh file the node values and element values in the dfsu file are saved
in separate shape files.
1. One shape file (and accompanying index, projection and DBF files) con-
taining the bathymetry of the node points in the mesh by a point feature
layer.
(naming convention: globalname_Nodes.*)
2. One shape file (and accompanying index, projection and DBF files) con-
taining the bathymetry of the elements by a polygon feature layer.
(naming convention: globalname_Elements.*)
12.4 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or Execute the set-up.
55
GIS - Mike2Shp
13 GIS - Mike2Txt
This tool has been implemented to transform MIKE 21 grid data files into
ESRI’s ArcView txt format.
Figure 13.1 Example of resulting txt file (derived from Donegal bay bathymetry).
Only part of file (the top) is shown.
13.1 Input
On this page the MIKE 21 (*.dt2 or *.dfs2 formats) file where data should be
extracted from is selected. To select the file either type the full path or browse
for the file.
Once the input file has been specified, the program requires the user to
define the items which will be transformed.
Beware that there will be generated one output file for each selected Time
Step. Each file will be postfixed with the Time Step number, e.g. having spec-
ified the output file C:\output.txt and selected time step 1 and 112 will cause
the generation of the two output files C:\output001.txt and C:\output112.txt.
57
GIS - Mike2Txt
13.4 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or Execute the set-up.
14 GIS - Shp2xyz
This tool has been implemented to extract spatial feature data from a shape
file and store the values in an ascii file as xyz data.
Point
Polyline
Polygon
Per default the z-values are derived from the chosen geographical feature.
You have the option to specify the name of a field in the shape file that con-
tains the values to be saved in the z-column of the output data.
1. X-coordinate
2. Y-coordinate
3. Z-level
If the feature data contains a z-value (type PointZ), this value is written to the
third column, otherwise the third column contains 0.
If a optional z-field has been chosen, the z-value is derived from this.
59
GIS - Shp2xyz
Each polyline will be represented by the position of the connection points and
the connectivity information. The output file will contain four columns:
1. X-coordinate
2. Y-coordinate
3. Z-level
4. Connectivity information (1: connected to next point, 0: end of line)
If the feature data contains a z-value (type PolylineZ), this value is written to
the third column, otherwise the third column contains 0.
If a optional z-field has been chosen, the z-value is derived from this.
Each polygon will be represented by the position of the connection points and
the connectivity information. The output file will contain four columns:
1. X-coordinate
2. Y-coordinate
3. Z-level
4. Connectivity information (1: connected to next point, 0: end of line)
If the feature data contains a z-value (type PolygonZ), this value is written to
the third column, otherwise the third column contains 0.
If a optional z-field has been chosen, the z-value is derived from this.
14.4 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or Execute the set-up.
14.5 Example
14.5.1 Purpose
For the purpose of investigating flooding in a small town the municipality has
provided shape files describing various features such as houses, roads and
lights.
The Shp2Xyz tool is used to extract the geographic position of the various
shape file data into xyz files. The resulting xyz data files can then be imported
into the Mesh Generator as scatter data or boundary arcs.
Figure 14.2 shows how the imported data may look in Mesh Generator.
61
GIS - Shp2xyz
63
The HYDROLOGY Tools in the MZ Toolbox include the facilities:
Maximum Rainfall
Mean Area Weighting Algoritm
Normalize Rainfall
Runoff Analysis
15 Maximum Rainfall
This tool extracts maximum rainfall for a number of periods from a range of
historical rainfall events.
15.2 Parameters
Extraction time step
Event periods
Extraction periods
Extract values
15.4 Summary
Summary, or setup status: review parameter spec's. And if you want change
any settings, go back; if you are satisfied with the settings click Execute, or
just Finish to save the setup for later.
65
Maximum Rainfall
16.6 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or execute the set-up.
67
Mean Area Weighting Algoritm
17 Normalize Rainfall
This tool normalises rainfall data measured eg every 10 min, 30 min or 1 hour
with rainfall data measured over eg 24 hours. The starting time in both files
must match, eg 9:00 AM, both, or 00:00, both, and both files must begin with
a "delete value".
69
Normalize Rainfall
18 Runoff Analysis
Effective rainfall analysis: this tool generates as output a meta file from two
time series files, one with average rainfall data and one with observed dis-
charge data.
18.2 Accumulation
Parameters:
18.3 Plot
Plot page.
18.5 Summary
Summary, or setup status: review parameter spec's. And if you want change
any settings, go back; if you are satisfied with the settings click Execute, or
just Finish to save the setup for later.
71
Runoff Analysis
73
The Statistics Tools in the MZ Toolbox include the facility:
The output will be written to either an ascii file (in the time series case) or a
standard dfs file.
19.1 Dimension
Here you select which type of file (Dimension) you want to do statistics on.
If you choose to do statistics on a time series file, the output will be written to
an *.out file in the same directory as your input data. The name of the output
file will be the setup name specified on the previous page. You will get Mini-
mum, Maximum, Median, Mean, Root mean square, Standard deviation and
Skewness for a time series file.
If you choose to do statistics on a line series file, you may choose up to six
statistical parameters as output. You will choose these later on the Statistics
dialogue.
If you choose to do statistics on a grid series file, you will have to choose one
of six statistical parameters as output due to space limitations. You will
choose these later on the Statistics dialogue.
If you choose to do statistics on a line, matrix or volume series file, you will
have to choose one of six statistical parameters as output due to space limita-
tions. You will choose these later on the Statistics dialogue.
19.2 Input
On this page you select your input file. When you choose the file, you also
choose the items that you want to do statistics on.
75
Statistics for DFS Data Files
If the data file is a standard output file from MIKE 21 HD, i.e. containing the
items H Water depth, P-flux and Q-flux and with Data type = 1, you get the
additional option of selecting one or more of the following derived items: Sur-
face Elevation, Current Speed, and Vx and Vy (current velocities). These
items are calculated from h, p and q by the program as described below.
Figure 19.1 shows the definition of the grid items with respect to the position
in the grid. The saved h, p and q values in the file are positioned in the grid as
shown to the left, the derived items are all positioned in the center point of the
grid element as shown to the right.
The equations used for the calculation of the derived items are as follows:
W j k = h j k + z j k (19.1)
p j k p j – 1 k
Vx j k = -----------------------------
- + -----------------------------
- (19.2)
h j + 1 k + h j k h j k + h j – 1 k
q j k q j k – 1
Vy j ,k = -----------------------------
- + -----------------------------
- (19.3)
h j k + 1 + h j k h j k + h j k – 1
2 2
S j k = Vx j k + Vy j k (19.4)
However, for a time series file it is possible to give any constant reference
level which is substracted from the time series values before the statistics are
calculated.
Another possibility is to give the reference level as a time series covering the
whole period. In this way it is possible to compute statistics on e.g. the differ-
ence between a simulated and a measured time series in water levels, i.e. on
the error. In addition you can specify a lower and upper reference level limit.
In this case only time steps for which the reference level is inside this range
gives a contribution to the statistics. Thus, if only a minimum reference level
is given and the time series are again water levels, statistics on the error dur-
ing periods of high level can be calculated.
Note: Delete values in the file are not considered when calculating statistics.
E.g. you can have an exceedance percentage of 100 percent, even if the grid
point is not flooded at all time steps.
19.5 1D Line
Here you select the part of the line for which you want to calculate statistics.
19.6 2D Area
Here you select the subarea in which you want to calculate statistics.
19.7 3D Area
Here you select the subarea in which you want to calculate statistics.
19.8 Statistics
This is where you choose what type of statistics you want to calculate on your
1D, 2D or 3D data file. Due to memory constrains, you will only be able to
77
Statistics for DFS Data Files
choose one type of statistics for your output file, when you are generating sta-
tistics for matrix or volume series.
Maximum value
Maximum value of all data
Minimum value
Minimum value of all data
Mean value
Mean value of all data, calculated by Eq. (19.5)
Standard deviation
Standard deviation of all data, calculated by Eq. (19.7)
Median value
Value below which 50% of the data fall
Exceedance percentage
Percentage of exceedance given a threshold value
19.10 Status
The Status page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
The Median value: Value below which 50% of the data fall
X
X = ---------- (19.5)
N
RMS =
X
------------ (19.6)
N
X-X
2
S = ------------------------ (19.7)
N
The Skewness:
Skewness = X
– mode-
------------------------- (19.8)
S
79
Statistics for DFS Data Files
81
The TIME SERIES Tools in the MZ Toolbox include the facilities:
20.1 Input
Here one specifies the full path name of the input file, i.e. the file holding the
time series data to be interpolated. The input file must be a dfs0 file. One
must either type the full path name or browse for the file.
Figure 20.1 outlines the parameters needed for interpolating the value in
point A.
The linear interpolation basically takes two consecutive points and draws a
straight line between them. Furthermore, this procedure is performed to each
pair of consecutive points within the output period as shown below. This set of
straight lines contains all interpolated values for the output time series. The
formula for linear interpolation is:
x – x1
y = y 1 + y 2 – y 1 ---------------- (20.1)
x2 – x1
The piecewise cubic interpolation takes four consecutive points, and per-
form an interpolation by a cubic polynomial between the two central points
(out of the four consecutive points). By performing a cubic interpolation, it is
possible to smooth the interpolated function with respect to the linear interpo-
lation. Drawing a line passing through the four interpolated points you see a
curve following the trend of the data variation.
83
Interpolation of Time Series
x2 – x1
s 0 = y 2 – y 0 ---------------
-
x2 – x0
x2 – x1
s 1 = y 3 – y 1 ----------------
x3 – x1 (20.2)
a = s 1 – 2y 2 + s 0 + 2y 1
b = y2 – a – s0 – y1
y = y 1 + x s 0 + x b + xa
From the page you can either Finish the set-up, which will transfer the setup
definition to the current toolbox file, or execute the set-up.
21.1 Welcome
One year summary.
21.3 Summary
Summary, or setup status: review parameter spec's. And if you want change
any settings, go back; if you are satisfied with the settings click Execute, or
just Finish to save the setup for later.
85
One Year Summary
For each station a name is supplied if it has not been provided from the shape
file along with a dfs0 file holding the data. The tool does not modify the data in
the input dfs0 files and thus the data from the various input files must be com-
patible i.e. the same type of data and the same unit e.g. rainfall all in millime-
tres.
Once the table has been filled out the next button may be clicked. This action
will validate the data more specifically
Please note that the x,y name file has the extension *.xyz and the values are
space delimited.
87
Pre-Processing Temporal Data
When selecting the former a mesh or a dfs2 bathymetry file must be pro-
vided. The file will define the grid or the mesh used for the output i.e. the file
must be created prior to using the tool. Note that the file must use the same
projection as selected for the stations. In the case of the weighted time series
a polygon shape file must be provided. This shape file may contain multiple
polygons and a weighted time series will be produced for every non empty
polygon (i.e. containing at least one station).
22.10 Overview
Setup status: review the parameters. If you want to change any settings, go
back; if you are satisfied with the settings click Execute, or just Finish to save
the setup for later.
The Thiessen polygon method assigns the value of any point to the meas-
ured value from the nearest measuring station. If this station does not contain
values at the specific time step then the nearest measuring with actual data
will be used instead.
Figure 22.1 Three catchments (polygons) with a number of stations within each.
The calculation of Thiessen polygon is confined to only take place within the
individual catchment. Thus in the above figure the average value within
catchment C3 is only affected by the values at the stations P4, P5 and P6.
89
Pre-Processing Temporal Data
The area of interest is the non-shaded part. The Thiessen polygons for catch-
ment C3 are illustrated below with the area of influence of station point P4 as
further been shaded.
Figure 22.2 The Thiessen polygon associated with point P4 within Catchment C3.
N
1
N
- w i x y v i
v x y = --------------------------- (22.1)
w j x y
i=1
j=1
where N is the number of stations. The weighting values in the case of Thies-
sen polygons are unity or zero where unity is used for the nearest station and
zero for the remaining.
To obtain an average value for the whole catchment the above equation is
integrated over the whole catchment and divided by the catchment area i.e.
N N N
1 1
v = ---------------------------
N
- w i x y v i dA = ---- A i v i = Wi vi (22.2)
A
A
w j x y i = 1 i=1 i=1
j=1
Thus the weights for calculating the mean area weighting value per catch-
ment is given by
A
W i = -----i (22.3)
A
N
1
N
- w i x y v i
v x y = --------------------------- (22.4)
w j x y
i=1
j=1
1
w i x y = ------------------------------------------
p
-
p
(22.5)
x – xi + y – yi
Where the index i refers to the station index and p is the power parameter
taking on a positive value. The larger the power parameter value the more
peaky the interpolated surface will be at the station values. Note that at the
measurement locations the station value is always used.
The catchment wide weights used for the inverse distance method are
N N N
1 1 w i x y
v = ---------------------------
N
- w i x y v i dA = ---A- ---------------------------
N
- dAv i = Wi v (22.6)
A A
w j x y
i=1 i=1 i=1
w j x y
j=1 j=1
1 w i x y
W i = ---- ---------------------------
- dA (22.7)
A N
A
w j x y
j=1
91
Pre-Processing Temporal Data
22.12 Examples
The purpose of this example is to illustrate how to generate a map with spa-
tially and temporally distributed data. The generated map may be used in
connection with modelling rainfall runoff in a mountain region.
Model input
The selected area is as displayed in Figure 22.3. Rainfall data has been col-
lected from three stations in the region and syncronised to a common equi-
distant calender reference.
Figure 22.3 Selected area. Points indicate location of stations with rainfall data.
Parameters
Two setups are created using Thiessen polygons and Inverse distance
method, respectively, to create the map. The output type is selected as spa-
tially and temporally distributed data saved every hour during the first 50
hours of the rainfall event.
Results
The generated rainfall maps are shown in Figure 22.4.
Figure 22.4 Example of resulting rainfall maps for a certain time step.
Left: Created using Thiessen polygons
Right: Created using Inverse distance method
93
Pre-Processing Temporal Data
You have the option to specify an additional item in the containing a duration
for each event in the analysis. The resulting duration of each each class is
then reflecting the number of seconds the class properties is taking place
instead of the number of timesteps in the input file.
NOTE:
The time series file is assumed to have an equidistant time step interval.
Minimum value
The minimum value to consider for the analysis.
Maximum value
The maximum value to consider for the analysis.
No. Interval
The number of intervals defines the number of classes within each dimen-
sion.
95
Sorting Temporal Data
The default output file is a time series file containing the duration and repre-
sentative value of each valid event class obtained by the analysis.
As an option you can choose to create an additional ascii file containing the
results from the analysis written as scatter diagrams.
23.5 Overview
The overview page presents you a summary of all the input parameters you
have specified. You should inspect that the parameters are correct and if not
go back and change them.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
All values below the minimum value, Min, or above or equal to the maximum
value, Max, will be considered as invalid.
Note:
Each class is defined by a representative value, classrep(i), in the output:
23.7 Examples
The following figures describe the process on how to sort data from wind
measurements where all the events has the same duration.
97
Sorting Temporal Data
Figure 23.3 Define number of items in analysis, select input file and both input items
99
Sorting Temporal Data
The following figures describe the process and result when you sort a time
series file containing a wave climate where each event is defined by an indi-
vidual duration.
Consider a case where a harbour experience severe seiching for waves with
wave periods above 10 s that comes from SE (120 degrees -150 degrees).
By sorting the available data using only 2 items and relevant class intervals it
is possible to easy determine how often the seiching will occur.
The results in Figure 23.15 shows that during a total period of 35064 hours,
expressed by 11333 time steps in the input time series, seiching will occur
only during 7 hours, i.e. for 0.02% of a year.
101
Sorting Temporal Data
Figure 23.11 Define number of items in analysis, enable duration and select input file
and input items
103
Sorting Temporal Data
The basic time series tool, Time Series Editor, in MIKE Zero can import and
export time series data in ascii format, however it can only handle one time
series at a time and the format of the ASCII input file is restricted to a DHI
standard for the Time Series Editor. It is thus not feasible for handling large
amounts of data files.
24.1.1 dfs0
Files in dfs0 format are per default defined by an equidistant calendar axis
with a number of items, see Figure 24.1.
105
Time Series Batch Conversion
24.1.2 ASCII
Files in ASCII format must contain information with an increasing time record
and subsequent item information.
NOTE: The default layout for files in ASCII format is not the same as the lay-
out necessary for importing ASCII files into the Time Series Editor.
24.1.3 Excel
Files in Excel format must contain information with an increasing time record
and subsequent item information. The time specification may be defined in
one or several columns.
107
Time Series Batch Conversion
You can choose to convert one file or a number of similar files contained
within a folder.
dfs0
ASCII
Excel
NOTE: If you select ASCII or Excel format you will have to define a template
in the next dialog
If you have selected one of the first two options you must specity the template
file to use.
When creating a new template the initial settings correspond to the default
layout for input file type (ASCII or Excel).
Comma
Semi-colon
Space
Tab
User defined
In this case define the delimiter string in the box to the right
Comma
Dot
User locale
I.e. the seperator is defined by the local system settings
The format is specified by year (YY), month (MM), day (DD), hour (HH), min-
ute (mm) and second (ss).
In case the input file format is Excel the date and time may be defined over
several columns and you have to specify how the data is represented in the
individual columns by using the ‘|’ symbol.
109
Time Series Batch Conversion
The individual items are described by a title, an item type, an item unit and a
value type, selected among the available parameters in the pre-defined MIKE
Zero item groups. Generally you can define the number of the row in which
the specific parameter is stored or define the parameter manually, for each
item individually or the same parameter for all items at once.
You have to define the row number from which the actual values are stored.
Per default an empty value denotes the delete value. You may specify the
delete value otherwise by defining a specific value or the number of the row
containing the delete value.
NOTE: In case you have chosen to convert a folder of data files and the input
format is dfs0, the number of selectable items is determined by the number of
items in the first valid dfs0 file in the folder.
NOTE: The template file will be saved when you press Next.
dfs0
ASCII (default layout)
Excel (default layout)
NOTE: If you are converting files from a folder, the names of the files will be
derived from the input file names.
24.10 Overview
The overview page presents you with a summary of all the input parameters
you have specified. You should inspect the parameters to check they are cor-
rect, - and if not go back and change them.
You have the option to specify the location of an eventual log-file from the
conversion. If the conversion is successful no log-file is created, otherwise a
logfile with a list of the files not matching the template is saved.
From the page you can either Finish the set-up, which will transfer your set-
up definition to the current toolbox file, or Execute the set-up.
24.11 Preview
The preview button shows how the program will interprete the input data on
basis of the given settings. The first column shows the time whereas the
remaining columns show the items(s).
In case the given settings don’t allow for an interpretation of the input data a
message box will appear with a informative error message before the preview
is shown.
NOTE: In case the conversion is carried out on several files in a folder one of
the files in the folder will be selected as representative and shown in the dis-
play.
24.12 Examples
The following figures describe the process on how to prepare a template file
for converting an ASCII file to a dfs0 file and the subsequent use of this tem-
plate to batch-convert a number of ascii files with the same format from the
same folder.
The time series data files used in this example contains measured water lev-
els. The files are installed as a part of the MIKE Zero Example ‘Sound’
located in e.g.
.\Examples\MIKE_Zero\Projects\Sound\External Data\Measurements.
111
Time Series Batch Conversion
Figure 24.7 Define the ASCII input data file for template
113
Time Series Batch Conversion
115
Time Series Batch Conversion
NOTE: The template file will be saved when you press Next.
117
Time Series Batch Conversion
Press Next and Execute to convert the ASCII file to a dfs0 file.
Figure 24.18 Define the folder containing the ASCII input data files
119
Time Series Batch Conversion
Figure 24.21 Specify format type and folder for output data files.
Press Next and Execute to convert the ASCII files to dfs0 files.
The following figures describe the process on how to prepare a template file
for converting an Excel file to a dfs0 file. The subsequent use of this template
to batch-convert a number of Excel files work in similary way to a batch con-
version of ASCII files.
The time series data file used in this example contains measured water levels
in four tidal station. The file ‘Sound_WL.xlsx’ is installed as a part of the MIKE
Zero Example ‘Sound’ located in e.g.
.\Examples\MIKE_Zero\Projects\Sound\External Data\Measurements.
121
Time Series Batch Conversion
Figure 24.25 Define the ASCII input data file for template
123
Time Series Batch Conversion
125
Time Series Batch Conversion
Press Next and Execute to convert the Excel file to a dfs0 file.
127
The TRANSFORMATION Tools in the MZ Toolbox include the facility:
Rotate Grid
25 Rotate Grid
This transformation tool can interpolate and rotate scalar fields (e.g.
bathymetries), vector fields (e.g. wind velocity components) and tensor fields
(e.g. radiation stresses) stored in dfs2 data files.
The output is a new dfs2 data file with spatially interpolated values.
Items are disabled by selecting 'Not Used', and scalar items are specified as
'Scalar'.
If some of the items constitute a vector field you have to specify which item is
the 'Vector X'-component and which is the 'Vector Y'-component. Also, if
some of the items constitute a 2. order tensor field, e.g. a stress tensor, you
should specify the two normal components 'Tensor XX' and 'Tensor YY' and
the shear component 'Tensor XY'.
If the data file is a standard output file from MIKE 21 HD, i.e. containing the
items H Water depth, P-flux and Q-flux and with Data type = 1, you get the
additional option of selecting one or more of the following derived items: W
Surface Elevation, S Current Speed, and Vx and Vy (current velocities).
These items are calculated from h, p and q by the program as described
below.
129
Rotate Grid
NOTE: The calculations of derived items are based on the assumption of the
absolute delete value being very small, e.g. -10-30. The use of other delete
values may lead to incorrect derived results in grid cells next to cells holding
delete values.
Figure 25.1 shows the definition of the grid items with respect to the position
in the grid. The saved h, p and q values in the file are positioned in the grid as
shown to the left, the derived items are all positioned in the center point of the
grid element as shown to the right.
The equations used for the calculation of the derived items are as follows:
W j k = h j k + z j k (25.1)
p j k p j – 1 k
Vx j k = -----------------------------
- + -----------------------------
- (25.2)
h j + 1 k + h j k h j k + h j – 1 k
q j k q j k – 1
Vy j ,k = -----------------------------
- + -----------------------------
- (25.3)
h j k + 1 + h j k h j k + h j k – 1
2 2
S j k = Vx j k + Vy j k (25.4)
You must specify the extent of the new grid, i.e. the number of grid points
and the grid spacing.
The origin of the new grid relative to the old one must be specified. The
shift in the origin is expressed in grid cell units, and it can be a float num-
ber. Note that the origin of the new grid can be placed outside the old grid
domain.
The rotation angle - measured positive clockwise from new grid to old
grid - must be specified.
If your data does not have any land-water boundaries you should choose
the first option,
131
Rotate Grid
If you are interpolating a bathymetry you choose the second option, and
If the data has the bathymetry written as a prefix item (e.g. simulation
results) you should choose the last option.
The 'zland: Minimum value for true land' value is the value that separates
land from water. The value is only relevant if land-water interpolation option is
the second or third alternative. All grid points in the new grid which are placed
within the land area of the old grid will be given the "zland" value.
If the new grid is not fully enclosed in the old grid, you can specify a value
which will be uniformly set at all the exterior points of the old grid, in the new
grid. This can either be the delete value, or a user specified value. Finally its
also possible to specify values of exterior points relative to the old grid, in the
new grid through a .dfs2-file. The file should in that case represent a grid hav-
ing the same dimensions as the new grid which you specified earlier, but the
file can contain any values for the exterior points of the old grid which you
need to specify.
From the page you can either Finish the setup which will transfer your setup
definition to the current toolbox file or execute the setup.
133
Index
A
ADCIRC . . . . . . . . . . . . . . . . 43
ASCII format . . . . . . . . . . . . . . 106
D
Delete value . . . . . . . . . . . . . . 130
Delimiter . . . . . . . . . . . . . . . . 109
Derived item . . . . . . . . . . . . . . 129
Derived items . . . . . . . . . . . . 76, 129
dfs0 format . . . . . . . . . . . . . . . 105
E
ESRI world file . . . . . . . . . . . . . 35
Excel format . . . . . . . . . . . . . . 107
G
Geo-referencing . . . . . . . . . . . . 35
I
inverse distance weighting . . . . . . . 91
M
M21_Misc . . . . . . . . . . . . . . . . 38
P
Polygon . . . . . . . . . . . . . . . 59, 60
Polyline . . . . . . . . . . . . . . . 59, 60
S
Shape file . . . . . . . . . . . . . . . . 59
SMS . . . . . . . . . . . . . . . . . . 44
Station location . . . . . . . . . . . . . 87
Statistics . . . . . . . . . . . . . . . . 75
T
Template . . . . . . . . . . . . . . . . 108
Thiessen polygon . . . . . . . . . . 87, 89
Time description . . . . . . . . . . . . 109
TUFLOW . . . . . . . . . . . . . . . . 44
X
XYZ data . . . . . . . . . . . . . . . . 59