Revision as of 11:51, 25 October 2017 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,774 edits →Upstream and Downstream Boundaries ← Older edit		Revision as of 11:53, 25 October 2017 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,774 edits →Creating a Boundary Control Database from MIKE Newer edit →
Line 162: <font color='blue'><tt>Read GIS BC</tt></font> <font color='red'><tt>==</tt></font> <tt>..\model\gis\''<1D/2D boundary>''.shp</tt><br><br> =Creating a Boundary ~~Control~~Condition Database from MIKE= A Boundary ~~Control~~Condition Database (bc_dbase) consists of the values (time series or constant value) and the linking boundary names. The boundary names, constant values, and data source for time series, can be obtained from the steps outlined in: * [[#Creating_a_TUFLOW_Boundary_Control_File_from_MIKE21_and_MIKE_Flood\|Section 3]] - Creating a TUFLOW Boundary ~~Control~~Condition File from MIKE21 and MIKE Flood * [[#1D_Boundaries\|Section 5.2]] – 1D Boundaries The bc_dbase should be created in a comma delimited .csv file like the example shown below.<br>[[File: MIKE-bcdbase example.PNG]]

MIKE Flood to TUFLOW: Difference between revisions