GNAT.CommitRealization.pyt.xml

<?xml version="1.0"?>
<metadata xml:lang="en"><Esri><CreaDate>20170622</CreaDate><CreaTime>11391400</CreaTime><ArcGISFormat>1.0</ArcGISFormat><SyncOnce>TRUE</SyncOnce><ModDate>20171019</ModDate><ModTime>211228</ModTime><scaleRange><minScale>150000000</minScale><maxScale>5000</maxScale></scaleRange><ArcGISProfile>ItemDescription</ArcGISProfile></Esri><dataIdInfo><idCitation><resTitle>Commit Stream Network</resTitle></idCitation><idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;With the &lt;/SPAN&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;Commit Stream Network &lt;/SPAN&gt;&lt;SPAN&gt;tool, the user selects a specific representation of a stream network. That representation can be based on specific criteria (or combination of criterias), such as a custom spatial extent.  By "committing" that network to a GNAT Riverscapes project, that stream network is the basis for a new &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;realization&lt;/SPAN&gt;&lt;SPAN&gt;, upon which all subsequent &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;analysis&lt;/SPAN&gt;&lt;SPAN&gt; are performed.  Each Riverscapes project can have multiple &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;realizations&lt;/SPAN&gt;&lt;SPAN&gt;, and each &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;realization&lt;/SPAN&gt;&lt;SPAN&gt; can have multiple &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;analyses&lt;/SPAN&gt;&lt;SPAN&gt;.  Each new realization must be created by committing a different version of the stream network.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs><idCredit>Kelly Whitehead, Jesse Langdon, South Fork Research, Inc.</idCredit><searchKeys><keyword>riverscapes</keyword><keyword>stream</keyword><keyword>network</keyword><keyword>realization</keyword></searchKeys></dataIdInfo><distInfo><distributor><distorFormat><formatName>ArcToolbox Tool</formatName></distorFormat></distributor></distInfo><tool name="CommitRealization" displayname="Commit Stream Network" toolboxalias="GNAT" xmlns=""><parameters><param name="projectXML" displayname="GNAT Project XML" type="Optional" direction="Input" datatype="File" expression="{projectXML}"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The Riverscapes project XML file (named "project.rs.xml") which stores all relevant information about the GNAT project.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="realization" displayname="Realization Name" type="Required" direction="Input" datatype="String" expression="realization"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The name for the realization that will be created upon commital of the stream network to the project.  Each realization name should be unique.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="InputFCStreamNetwork" displayname="Input Stream Network" type="Required" direction="Input" datatype="Feature Class" expression="InputFCStreamNetwork"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The stream network polyline feature class which will be commited to the GNAT project. &lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="reachIDfield" displayname="Unique Reach ID Field" type="Optional" direction="Input" datatype="Field" expression="{reachIDfield}"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;An attribute field with a unique identifier value for each stream reach feature in the input stream network polyline feature class.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="tblNetwork" displayname="Network Table" type="Optional" direction="Input" datatype="Table" expression="{tblNetwork}"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;A network topology table, preferably built using the &lt;/SPAN&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;Build Network Topology&lt;/SPAN&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;Table&lt;/SPAN&gt;&lt;SPAN&gt; tool, found in GNAT &amp;gt; Main &amp;gt; Step 1- Stream Network Preparation.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param></parameters><summary>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;With the &lt;/SPAN&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;Commit Stream Network &lt;/SPAN&gt;&lt;SPAN&gt;tool, the user selects a specific representation of a stream network. That representation can be based on specific criteria (or combination of criterias), such as a custom spatial extent.  By "committing" that network to a GNAT Riverscapes project, that stream network is the basis for a new &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;realization&lt;/SPAN&gt;&lt;SPAN&gt;, upon which all subsequent &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;analysis&lt;/SPAN&gt;&lt;SPAN&gt; are performed.  Each Riverscapes project can have multiple &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;realizations&lt;/SPAN&gt;&lt;SPAN&gt;, and each &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;realization&lt;/SPAN&gt;&lt;SPAN&gt; can have multiple &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;analyses&lt;/SPAN&gt;&lt;SPAN&gt;.  Each new realization must be created by committing a different version of the stream network.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</summary></tool><mdHrLv><ScopeCd value="005"></ScopeCd></mdHrLv></metadata>