Importing SOBEK Network Data
Network data from SOBEK can be imported to InfoWorks ICM using files in the LIT format.
To import SOBEK network data:
- Open the network to be updated.
- Select Import | Model | from SOBEK network data from the Network menu, and the SOBEK Import dialog is displayed.
- In the SOBEK data folder field, enter the path to the folder which contains the network (LIT file) to be imported, or click to browse for the folder.
When selected, the Network dropdown list is populated with all the network files in the selected folder.
- Choose a network from the Network dropdown list.
When selected, the Version dropdown list is populated with all versions of the selected network file.
- Choose a version of the selected network from the Version dropdown list.
- Click OK to start the import.
An import log will be displayed with any import errors or warnings.
For details of the objects imported and any conversions made by the InfoWorks ICM Importer, see the Import Notes below.
Import Notes
The following files are read by the InfoWorks ICM Importer during the import process:
Layer or File | Type | Notes |
---|---|---|
Topography layer | net |
Base network topography (node and branch coordinates) Branches are split into multiple links according to information from other files |
cpt | Link geometry | |
dat | Node storage | |
Friction layer | bed | Bed friction |
exr | Extra friction | |
Cross section layer | dat |
Cross section list and elevations Cross section IDs |
def |
Cross section definitions |
|
net |
Cross section locations and storage nodes Cross section nodes |
The following sections provide information about the import of network objects from SOBEK to ICMLive Configuration Manager.
Nodes
Nodes may be imported from the SOBEK topography layer or cross section layer. See the Cross section section for information about nodes imported from the cross section layer.
SOBEK | InfoWorks ICM | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Element | Attribute | Parameter | Database name | |||||||||||
NODE | id | Node ID | node_id | |||||||||||
NODE | px | X | x | |||||||||||
NODE | py | Y | y | |||||||||||
NODE | nm | User text 1 | user_text_1 | Name of node. | ||||||||||
NODE | ty | Node type | node_type |
|
||||||||||
NODE | ty | Flood type | flood_type |
|
||||||||||
NODE | ws | Chamber plan area | chamber_area | If absent, the maximum from the manhole storage 'ct sw' table sub-element is used. | ||||||||||
NODE | ws | Shaft plan area | shaft_area | If absent, the maximum from the manhole storage 'ct sw' table sub-element is used. | ||||||||||
NODE | ss | Floodable area | floodable_area | If absent, the maximum from the street storage 'ct ss' table sub-element is used. | ||||||||||
NODE | wl | Chamber roof level | chamber_roof | |||||||||||
NODE | ct sw, ct ss | Storage array | storage_array |
Conduits
Conduits are created based on SOBEK branch information in the topography layer. Conduits may also be generated from nodes in the cross section layer. See the Cross section section for further information.
SOBEK | InfoWorks ICM | Notes | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Element | Attribute | Parameter | Database name | |||||||
BRCH | bn | US node ID | us_node_id | |||||||
BRCH | en | DS node ID | ds_node_id | |||||||
BRCH | al | Length | conduit_length | |||||||
Points | point_array | Calculated from the curving point 'ct bc' table in the cpt file. | ||||||||
BDFR | mf | Roughness type | roughness_type |
Other roughness types are not supported but will be recorded in import log. |
||||||
BDFR | mt cp | Top roughness Manning's n | top_roughness_N | When the 'mt cp' attribute is followed by a 0, then the following value is used as the friction value for N (Manning's N) (mf=1). | ||||||
BDFR | mt cp | Bottom roughness Manning's n | bottom_roughness_N | |||||||
BDFR | mt cp | Top roughness Colebrook-White | top_roughness_CW | When the 'mt cp' attribute is followed by a 0, then the following value is used as the friction value for CW (Colebrook-White) (mf=4). | ||||||
BDFR | mt cp | Bottom roughness Colebrook-White | bottom_roughness_CW |
Cross section
Cross section data is imported from SOBEK as nodes in InfoWorks ICM.Imported nodes have a either a downstream conduit or channel type of link. See the Links section for further information.
Nodes
SOBEK | InfoWorks ICM | Notes | ||
---|---|---|---|---|
Element | Attribute | Parameter | Database name | |
CRSN | id | Node ID | node_id | |
CRSN | nm | User text 1 | user_text_1 | The name of the cross section is imported to the User text 1 field in the node properties. |
CRSN | ci | X | x | Identifies which branch (from the net file) the node belongs to. |
CRSN | lc | Y | y | Distance along the branch. Together with the branch ID, node location and link geometry, provides the position of the node on the network. |
STON | id | Node ID | node_id |
If the version number is 1.1 or higher in the net file (i.e. the first line begins with CR_ followed by a number greater than 1.1), then the STON elements are considered as storage nodes in the nodes.dat file and are imported; all other storage nodes are ignored. If the version number is less than 1.1, then all storage nodes are imported. |
CRDS | id | Cross-section definition ID. Use for reference from the dat file. | ||
CRDS | ty |
Node type |
node_type |
Node type set to Manhole. |
Links
Cross section data is imported from SOBEK as nodes in InfoWorks ICM. Depending on the SOBEK CRDS element and type ('ty') attribute, imported nodes have a either a downstream conduit or downstream channel type of link. See the table below for further information.
SOBEK | InfoWorks ICM | Notes | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Element | Attribute | Parameter | Database name | |||||||||||||||||||||||||||||||||
CRSN | id | US node ID | us_node_id | Set for both conduit and channel types of links. | ||||||||||||||||||||||||||||||||
DS node ID | ds_node_id | Set for both conduit and channel types of links. | ||||||||||||||||||||||||||||||||||
CRDS | bl (bed level.) | US invert level | us_invert | The US invert level on the conduit or channel. | ||||||||||||||||||||||||||||||||
CRDS | ty |
Shape ID Width Height Springing height |
shape conduit_width conduit_height springing_height |
This is used to primarily determine type of downstream link (conduit or channel), and the shape and dimensions of the conduit or channel:
|
Shapes
If the SOBEK cross-section data is imported as a node with a downstream conduit with a user-defined shape, the following is imported into ICMLive Configuration Manager as shape data:
SOBEK | InfoWorks ICM | Notes | ||
---|---|---|---|---|
Element | Attribute | Parameter | Database name | |
CRDS |
ty =0 (tabulated) or 1 (trapezium) |
Shape ID | shape_id | |
Shape type | shape_type | Set to Symmetric. | ||
Geometry | geometry |
If SOBEK 'ty' is 0 (tabulated), the SOBEK attribute 'lt lw' is imported as the height and width for a symmetric user-defined non-normalised shape. If SOBEK 'ty' is 1 (trapezium), the geometry is calculated using the SOBEK bed width ('aw' attribute), bed width ('bw' attribute) and bank slope ('bs' attribute) for a symmetric user-defined shape. |
Channels
If the SOBEK cross-section data is imported as a node with a downstream channel type of link, the following is imported as ICMLive Configuration Manager channel data:
SOBEK | InfoWorks ICM | Notes | ||
---|---|---|---|---|
Element | Attribute | Parameter | Database name | |
CRDS |
ty = 10 (yz table ) or 11 (asymmetrical trapezoidal) |
Shape ID | shape_id |
Channel shape
If the SOBEK cross-section data is imported as a node with a downstream channel type of link, the following is imported as ICMLive Configuration Manager channel shape parameters:
SOBEK | InfoWorks ICM | Notes | ||
---|---|---|---|---|
Element | Attribute | Parameter | Database name | |
CRDS |
ty = 10 (yz table ) or 11 (asymmetrical trapezoidal) |
Shape ID | shape_id | |
Roughness type | roughness_type | If friction data exists, this will be set accordingly to either Manning's 1/n, Manning's N or Colebrook White. | ||
Channel profile | profile |
Pairs of offsets and levels (SOBEK 'lt yz' attributes) are converted into a channel profile, with extra datapoints added through linear interpolation if a given friction range references co-ordinates that do not exist directly in the table. The imported roughness value, if any, will be displayed in the appropriate roughness type column in the Sections editor. |