Bpaul at 05:06, 13 March 2023

2023-03-13T05:06:56Z

Show changes

Bpaul at 04:50, 13 March 2023

2023-03-13T04:50:47Z

Bpaul at 04:47, 13 March 2023

2023-03-13T04:47:23Z

Bstabler at 23:02, 26 August 2020

2020-08-26T23:02:29Z

Show changes

Gwineman at 21:33, 17 October 2016

2016-10-17T21:33:56Z

Show changes

Gwineman: Created page with "Category:4.0 Directory & Data Structures"

2016-10-17T21:28:06Z

Created page with "Category:4.0 Directory & Data Structures"

New page

[[Category:4.0 Directory & Data Structures]]

@@ Line 14: / Line 14: @@
 |  class="confluenceTd" | <p>YCOORD</p>
 |  class="confluenceTd" | <p>Y coordinate of node – state plane feet</p>
-|}</div><h4 id="id-4.3DAYSIM-LinkFile"><em>Link File</em></h4><p class="BodyParagraph">This file provides DTALite with information about link attributes and the nodes they connect and has the following format. It has to be named “input_link.csv” and can be found in the “\User.prg\DaySim_Inputs\1_Parcel\Buffering\)” folder of the master model directory. Only the first four fields are used in calculations. The remaining fields can use dummy values if that information is not readily available.</p><h4 id="id-4.3DAYSIM-TABLE4-9DTALITEINPUTLINKFILEFORMAT">TABLE 4-9 DTALITE INPUT LINK FILE FORMAT</h4><div class="table-wrap">
+|}</div><h4 id="id-4.3DAYSIM-LinkFile"><em>Link File</em></h4><p class="BodyParagraph">This file provides DTALite with information about link attributes and the nodes they connect and has the following format. It has to be named “input_link.csv” and can be found in the “\tools\DaySim_Data_Tools\)” folder of the master model directory. Only the first four fields are used in calculations. The remaining fields can use dummy values if that information is not readily available.</p><h4 id="id-4.3DAYSIM-TABLE4-9DTALITEINPUTLINKFILEFORMAT">TABLE 4-9 DTALITE INPUT LINK FILE FORMAT</h4><div class="table-wrap">
 {|  class="wikitable"
 |  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
@@ Line 59: / Line 59: @@
 |  class="confluenceTd" | <p>Lane capacity</p>
 |  class="confluenceTd" | <p>No</p>
-|}</div><h4 id="id-4.3DAYSIM-LinkTypeFile"><em>Link Type File</em></h4><p class="BodyParagraph">This file provides DTALite with link type definitions and has the following format. It has to be named “input_link_type.csv” and can be found in the “\User.prg\DaySim_Inputs\1_Parcel\Buffering\)” folder of the master model directory. However, the default provided with the model setup can be used instead of creating a new file each time. This is because the input in this file is not taken into consideration for just getting shortest path distances over the network.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-10DTALITEINPUTLINKTYPEFILEFORMAT">TABLE 4-10 DTALITE INPUT LINK TYPE FILE FORMAT</h4><div class="table-wrap">
+|}</div><h4 id="id-4.3DAYSIM-LinkTypeFile"><em>Link Type File</em></h4><p class="BodyParagraph">This file provides DTALite with link type definitions and has the following format. It has to be named “input_link_type.csv” and can be found in the “\tools\DaySim_Data_Tools\)” folder of the master model directory. However, the default provided with the model setup can be used instead of creating a new file each time. This is because the input in this file is not taken into consideration for just getting shortest path distances over the network.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-10DTALITEINPUTLINKTYPEFILEFORMAT">TABLE 4-10 DTALITE INPUT LINK TYPE FILE FORMAT</h4><div class="table-wrap">
 {|  class="wikitable"
 |  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
@@ Line 78: / Line 78: @@
 |  class="confluenceTd" | <p>ARTERIAL_FLAG</p>
 |  class="confluenceTd" | <p>1 if arterial; 0 otherwise</p>
-|}</div><h4 id="id-4.3DAYSIM-NodePairsFile"><em>Node Pairs File</em></h4><p class="BodyParagraph">This file provides DTALite with the specific node pairs for which network shortest path distance needs to calculated. As noted earlier, it is usually all nodes that are with 3-miles (Euclidean) of each other. It has to be named “input_od_pairs.csv” and can be found in the “\User.prg\DaySim_Inputs\1_Parcel\Buffering\)” folder of the master model directory. The node pairs file needs to be in the following format.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-11DTALITEINPUTNODEPAIRSFILEFORMAT">TABLE 4-11 DTALITE INPUT NODE PAIRS FILE FORMAT</h4><div class="table-wrap">
+|}</div><h4 id="id-4.3DAYSIM-NodePairsFile"><em>Node Pairs File</em></h4><p class="BodyParagraph">This file provides DTALite with the specific node pairs for which network shortest path distance needs to calculated. As noted earlier, it is usually all nodes that are with 3-miles (Euclidean) of each other. It has to be named “input_od_pairs.csv” and can be found in the “\tools\DaySim_Data_Tools\)” folder of the master model directory. The node pairs file needs to be in the following format.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-11DTALITEINPUTNODEPAIRSFILEFORMAT">TABLE 4-11 DTALITE INPUT NODE PAIRS FILE FORMAT</h4><div class="table-wrap">
 {|  class="wikitable"
 |  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
@@ Line 91: / Line 91: @@
 |  class="confluenceTd" | <p>DEST_NODE_ID</p>
 |  class="confluenceTd" | <p>Destination node id</p>
-|}</div><p class="BodyParagraph">There exists a utility “Network_DataPrepv2.exe” (also in \User.prg\DaySim_Inputs\1_Parcel\Buffering\) folder of the master model directory) that uses the node file (input_node.csv) and produces the node pairs file. The Euclidean distance threshold between the node pairs can be controlled by changing BUFRAD parameter in “netprep.ctl” file.</p><h4 id="id-4.3DAYSIM-Node-to-NodeDistanceFile"><em>Node-to-Node Distance File</em></h4><p class="BodyParagraph">When run, DTALite outputs a comma-separated text file named “output_shortest_path.txt”. This contains the shortest path distance information for all the network node pairs provided as input. The format of the file is as follows.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-12DTALITEOUTPUTNODEDISTANCEFILEFORMAT">TABLE 4-12 DTALITE OUTPUT NODE DISTANCE FILE FORMAT</h4><div class="table-wrap">
+|}</div><p class="BodyParagraph">There exists a utility “Network_DataPrepv2.exe” (also in \tools\DaySim_Data_Tools\) folder of the master model directory) that uses the node file (input_node.csv) and produces the node pairs file. The Euclidean distance threshold between the node pairs can be controlled by changing BUFRAD parameter in “netprep.ctl” file.</p><h4 id="id-4.3DAYSIM-Node-to-NodeDistanceFile"><em>Node-to-Node Distance File</em></h4><p class="BodyParagraph">When run, DTALite outputs a comma-separated text file named “output_shortest_path.txt”. This contains the shortest path distance information for all the network node pairs provided as input. The format of the file is as follows.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-12DTALITEOUTPUTNODEDISTANCEFILEFORMAT">TABLE 4-12 DTALITE OUTPUT NODE DISTANCE FILE FORMAT</h4><div class="table-wrap">
 {|  class="wikitable"
 |  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
@@ Line 107: / Line 107: @@
 |  class="confluenceTd" | <p>DISTANCE</p>
 |  class="confluenceTd" | <p>Shortest path distance in miles</p>
-|}</div><h3 id="id-4.3DAYSIM-DaySimBufferingTool"><span style="color: rgb(255,102,0);">DaySim Buffering Tool</span></h3><p class="BodyParagraph">The Daysim buffering tool is run to prepare microzone input file for DaySim. The executable is called “DSBuffTool.exe” and can be found in the “\User.prg\DaySim_Inputs\1_Parcel\Buffering\” folder of the master model directory. The tool is run to prepare microzone input file for DaySim.</p><h4 id="id-4.3DAYSIM-BufferedMAZFile"><em>Buffered MAZ File</em></h4><p class="BodyParagraph">This is a space-delimited delimited ASCII text format file (.dat) with one row of data per microzone and is the primary file used to maintain socioeconomic information. The file begins with several fields that identify the microzone , and describe the physical location and size of the microzone, and then contains fields that describe the quantity of housing, school enrollment, and employment around the microzone using logistic distance decay curves with 1/8th mile and quarter mile inflection points. These two distance decay curves with 1/8<sup>th</sup> and quarter mile inflection points result in “buffer 1” and “buffer 2” variables respectively which are referred to in the file format table below. In addition, the microzone file contains information about urban form and the transportation system on and close to the microzone, including the proximity to transit stops and the price and supply of parking.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-13BUFFEREDMAZFILE">TABLE 4-13 BUFFERED MAZ FILE</h4><div class="table-wrap">
+|}</div><h3 id="id-4.3DAYSIM-DaySimBufferingTool"><span style="color: rgb(255,102,0);">DaySim Buffering Tool</span></h3><p class="BodyParagraph">The Daysim buffering tool is run to prepare microzone input file for DaySim. The executable is called “DSBuffTool.exe” and can be found in the “\tools\DaySim_Data_Tools\” folder of the master model directory. The tool is run to prepare microzone input file for DaySim.</p><h4 id="id-4.3DAYSIM-BufferedMAZFile"><em>Buffered MAZ File</em></h4><p class="BodyParagraph">This is a space-delimited delimited ASCII text format file (.dat) with one row of data per microzone and is the primary file used to maintain socioeconomic information. The file begins with several fields that identify the microzone , and describe the physical location and size of the microzone, and then contains fields that describe the quantity of housing, school enrollment, and employment around the microzone using logistic distance decay curves with 1/8th mile and quarter mile inflection points. These two distance decay curves with 1/8<sup>th</sup> and quarter mile inflection points result in “buffer 1” and “buffer 2” variables respectively which are referred to in the file format table below. In addition, the microzone file contains information about urban form and the transportation system on and close to the microzone, including the proximity to transit stops and the price and supply of parking.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-13BUFFEREDMAZFILE">TABLE 4-13 BUFFERED MAZ FILE</h4><div class="table-wrap">
 {|  class="wikitable"
 |  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>

@@ Line 1: / Line 1: @@
 [[Category:4.0 Directory & Data Structures]]
-<h3 id="id-4.3DAYSIM-ShortDistanceImpedanceGeneration"><span style="color: rgb(255,102,0);">Short Distance Impedance Generation</span></h3><p class="BodyParagraph">This process is required to generate more accurate short distances based on an all streets network. DTALite, a dynamic traffic assignment software, is used to generate node-to-node shortest path distances using the all streets network. The executable is called “DTALite_64.exe” (in \User.prg\DaySim_Inputs\1_Parcel\Buffering\) and requires the following input files:</p><ul><li>Node file</li><li>Link file</li><li>Link type file</li><li>Node pairs file</li></ul><h4 id="id-4.3DAYSIM-NodeFile"><em>Node File</em></h4><p class="BodyParagraph">This file provides DTALite with the locations of all the nodes in the all streets network and has the following format. It has to be named “input_node.csv” and can be found in the “\User.prg\DaySim_Inputs\1_Parcel\Buffering\)” folder of the master model directory.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-8DTALITEINPUTNODEFILEFORMAT">TABLE 4-8 DTALITE INPUT NODE FILE FORMAT</h4><div class="table-wrap">
+<h3 id="id-4.3DAYSIM-ShortDistanceImpedanceGeneration"><span style="color: rgb(255,102,0);">Short Distance Impedance Generation</span></h3><p class="BodyParagraph">This process is required to generate more accurate short distances based on an all streets network. DTALite, a dynamic traffic assignment software, is used to generate node-to-node shortest path distances using the all streets network. The executable is called “DTALite_64.exe” (in \tools\DaySim_Data_Tools\) and requires the following input files:</p><ul><li>Node file</li><li>Link file</li><li>Link type file</li><li>Node pairs file</li></ul><h4 id="id-4.3DAYSIM-NodeFile"><em>Node File</em></h4><p class="BodyParagraph">This file provides DTALite with the locations of all the nodes in the all streets network and has the following format. It has to be named “input_node.csv” and can be found in the “\tools\DaySim_Data_Tools\)” folder of the master model directory.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-8DTALITEINPUTNODEFILEFORMAT">TABLE 4-8 DTALITE INPUT NODE FILE FORMAT</h4><div class="table-wrap">
 {|  class="wikitable"
 |  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>

4.3 DaySim - Revision history

Bpaul at 05:06, 13 March 2023

Bpaul at 04:50, 13 March 2023

Bpaul at 04:47, 13 March 2023

Bstabler at 23:02, 26 August 2020

Gwineman at 21:33, 17 October 2016

Gwineman: Created page with "Category:4.0 Directory & Data Structures"