3D_Network_Toolbox/3DNetworkToolbox.Network2DTo3D.pyt.xml at master · higgicd/3D_Network_Toolbox · GitHub

1
2
3
4
5
6
7
8
<?xml version="1.0"?>
<metadata xml:lang="en"><Esri><CreaDate>20200720</CreaDate><CreaTime>14500600</CreaTime><ArcGISFormat>1.0</ArcGISFormat><SyncOnce>TRUE</SyncOnce><ModDate>20200720</ModDate><ModTime>15032200</ModTime><scaleRange><minScale>150000000</minScale><maxScale>5000</maxScale></scaleRange></Esri><tool name="Network2DTo3D" displayname="3D Network Generation from 2D Network and DTM" toolboxalias="Network3D" xmlns=""><arcToolboxHelpPath>c:\program files\arcgis\pro\Resources\Help\gp</arcToolboxHelpPath><parameters><param name="Input_Surface" displayname="Input Surface" type="Required" direction="Input" datatype="Raster Dataset" expression="Input_Surface"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Input digital elevation/terrain model in raster format&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="Input_Line_Feature_Class" displayname="Input Network (2D)" type="Required" direction="Input" datatype="Feature Layer" expression="Input_Line_Feature_Class"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Input (2D) pedestrian network&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="Distance" displayname="Sample Distance" type="Required" direction="Input" datatype="Double" expression="Distance"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;T&lt;/SPAN&gt;&lt;SPAN&gt;he distance at which to split the edges of the network to calculate their slope and travel time. The selection of this variable determines the slope detail in the network and should be based on some tradeoff between your desired network slope resolution and the resolution of the DTM, as this can dramatically increase the number of edges in your network. In &lt;/SPAN&gt;&lt;A href="https://doi.org/10.1016/j.landurbplan.2018.12.011" STYLE="text-decoration:underline;"&gt;&lt;SPAN&gt;&lt;SPAN&gt;Higgins (2019)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; for example, a sample distance of 10m was determined to be a reasonable compromise with a DTM available at a 2m resolution&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="FalseSplit" displayname="Network has No Split edges" type="Required" direction="Input" datatype="Boolean" expression="FalseSplit"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;If checked, this parameter indicates that your input 2D network has lines that should &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;not &lt;/SPAN&gt;&lt;SPAN&gt;be split by the tool. Useful for line features like bridges, where the standard interpolation and line splitting work flow could result in these edges traversing up and down the steep sides of a ravine in the DTM.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If you would like to use the No Split option, the tool is presently &lt;/SPAN&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;&lt;SPAN&gt;hard coded&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; to expect a field &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;&lt;SPAN&gt;NO_SPLIT&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt; in the input 2D network. With NO_SPLIT = 1, these edges will have the height of their start and end point coordinates interpolated from the DTM, but will not be split further. Slope, and slope-aware travel times will still be calculated based on the average slope of the unsplit line’s start and end points in 3D space.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Note: if you tick the &lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;&lt;SPAN&gt;No Split&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; box but do not have any &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;&lt;SPAN&gt;NO_SPLIT&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; links identified, the tool will not work properly. We will try to make this more user-friendly in a future release.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="FalseSlope" displayname="Network has No Slope edges" type="Required" direction="Input" datatype="Boolean" expression="FalseSlope"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;If checked, this parameter indicates that your input 2D network has edges that should not have their travel time based on the slope of the terrain. Useful for any network elements that you do not want to have 3D, slope-aware travel times, such as internal pathways in buildings or pedestrian subways. If slope were applied, would result in inaccurate estimates of travel time.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If you would like to use the No Split option, the tool is presently &lt;/SPAN&gt;&lt;SPAN STYLE="font-weight:bold;"&gt;&lt;SPAN&gt;hard coded&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; to expect a field &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN STYLE="font-style:italic;"&gt;&lt;SPAN&gt;NO_SLOPE&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt; in the input 2D network. With NO_SLOPE = 1, these edges still have their height interpolated from the DTM, but these values are not used to calculate their travel time; the 2D travel time is used instead. This is done to maintain network topology when creating a network that uses the geometry of features for elevation in Network Analyst.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</dialogReference></param><param name="Network_3D" displayname="Output Network (3D)" type="Required" direction="Output" datatype="Feature Layer" expression="Network_3D"><dialogReference>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;The output 3D pedestrian network for further analysis&lt;/SPAN&gt;&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;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Create 3D pedestrian network features with travel times defined by Tobler's Hiking Function. Used in the paper by Higgins (2019) available at https://doi.org/10.1016/j.landurbplan.2018.12.011&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</summary></tool><dataIdInfo><idCitation><resTitle>3D Network Generation from 2D Network and DTM</resTitle></idCitation><idCredit>Christopher D. Higgins
Department of Human Geography
University of Toronto Scarborough

Jimmy Chan
Department of Land Surveying and Geo-Informatics
The Hong Kong Polytechnic University</idCredit><searchKeys><keyword>network</keyword><keyword>3D gis</keyword></searchKeys></dataIdInfo><distInfo><distributor><distorFormat><formatName>ArcToolbox Tool</formatName></distorFormat></distributor></distInfo><mdHrLv><ScopeCd value="005"/></mdHrLv><mdDateSt Sync="TRUE">20200720</mdDateSt></metadata>