1D Pits: Difference between revisions
Content deleted Content added
Chris Huxley (talk | contribs) |
Chris Huxley (talk | contribs) |
||
Line 65:
==Pit Search Distance==
Some agency pit dataset may not have all point pit features snapped to the associated line pipe features. The *.ecf command <font color="blue"><tt>"Pit Search Distance</tt></font> can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends:<br>
<font color="blue"><tt>Pit Search Distance</tt></font> <font color="red"><tt>==</tt></font><tt>xxx</tt><br>
<font color="blue"><tt>Read GIS Network</tt></font> <font color="red"><tt>==</tt></font><tt>..\model\mi\1d_nwke_*****.MIF</tt><br>
<br>
The order of the <font color="blue"><tt>Pit Search Distance</tt></font> command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. There is an example on the TUFLOW Forum [http://www.tuflow.com/forum/index.php?/topic/1232-pit-search-distance-not-working/ here] that describes the setup of the commands within the .ecf. <br>
<br>
To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. <br>
| |||