For BW, CW and RW channels, the flow width of weir (m) over the top of the B, C or R structure. If < 0.001 uses the top width of B or R channel, or the C channel diameter.
Float
24
EN2
For BW, CW and RW channels, the depth (m) of the bridge deck or culvert overlay.
Float
25
EN3
For BW, CW and RW channels, the depth of the hand rail (m). If < 0.001 assumes solid or no rail.
Float
26
EN4
For BW, CW and RW channels, % blockage of the rail (eg. 100 for solid rail, 50 for partially blocked, 0 for no rail).
Float
27
EN5
For BW, CW and RW channels, the weir calibration factor. Is set to 1.0 if < 0.001 is specified.
Float
28
EN6
Not yet used (leave as zero).
Float
29
EN7
Not yet used (leave as zero).
Float
30
EN8
Not yet used (leave as zero).
Float
3.12.5How are Nodes and Channels Processed?
The procedure for reading and compiling the network is:
Nodes: Read the location of any manually digitised nodes from the GIS layer(s) specified in the Read MI Network command(s). Each node must have a unique ID. The network can be split up into several layers if desired. Note that a manually digitised node must only occur once in all the layers combined.
Channels and Cross-Sections (Except CS Tables):
Read the details of all channels from the GIS layer(s) specified by the Read MI Network command(s). Any cross-section profiles, hydraulic properties or bridge loss coefficient tables linked via 1d_ta layer(s) (see Read MI Table Links and Section 3.13.3) are processed. Also, any channel cross-section processed data from MIKE 11, ISIS or other external source is read at this stage. Each channel must have a unique ID. Nodes are automatically created at the ends of any channels found to not have a manually digitised node. The network can be split up into several layers if desired. You can overwrite an existing channel provided it has the same ID, and is connected to the same nodes as the channel being overwritten.
Node Storages (Except NA Tables):
Any elevation versus surface area tables at nodes linked via 1d_ta layer(s) (see Read MI Table Links and Section 3.13.3) are processed.
Network Checks:
The network is checked for any incompatible node and/or channel IDs, connectivity, etc.
Any Fixed Field Formatted Cross-Sections (CS Tables):
Any cross-section processed data in the original fixed field format (see CS and CS Data) are read. If cross-section data is specified more than once for a channel the last cross-section data set read prevails (a “CHECK” message is provided in the .elf file when ever a channel’s cross-section data is overwritten). Every channel, except some hydraulic structures, must have a cross-section.
Any Fixed Field Formatted Node Storages (NA Tables):
Firstly, any node storages to be based on cross-section widths are calculated. Secondly, any node storage data in the original fixed field format is read. Note: if storage data is specified more than once for a node the last storage data read prevails.
Hydraulic Structures: Additional information required for some hydraulic structures is read.
Boundary Conditions:
Boundary condition locations and data are read (see Section 3.17).
