Difference between revisions of "4.3 DaySim"

From NFTPO Model
Jump to: navigation, search
 
Line 1: Line 1:
 
[[Category:4.0 Directory & Data Structures]]
 
[[Category:4.0 Directory & Data Structures]]
  
<h3 id="id-4.3DAYSIM-ParcelInputPreparation"><span style="color: rgb(255,102,0);">Parcel Input Preparation</span></h3><p class="BodyParagraph">TAZ level household, employment and school enrollment are allocated to parcels using the allocation tool. The location of allocation is \User.prg\DaySim_Inputs\1_Parcel\AllocationTool\AllocationTool.exe. It must be noted again that this tool was built after NERPM-AB model development and hence, allocation for the model was done manually.</p><p class="BodyParagraph">The allocation tool requires following four inputs:</p><ul><li>TAZ file</li><li>Block file</li><li>TAZ-Block intersect file</li><li>School file</li></ul><h4 id="id-4.3DAYSIM-TAZFile"><em>TAZ File</em></h4><p class="BodyParagraph">The TAZ file used as input to the parcel allocation tool contains TAZ-level information control totals of employment by industrial sector, households and enrollment school type, which are disaggregated down to the parcel level. </p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-4PARCELALLOCATIONTOOLTAZINPUTFILE">TABLE 4-4 PARCEL ALLOCATION TOOL TAZ INPUT FILE</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 \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">
{|  class="wikitable"
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>DESCRIPTION</strong></p>
 
|-
 
|  class="confluenceTd" | <p>TAZ</p>
 
|  class="confluenceTd" | <p>taz number</p>
 
|-
 
|  class="confluenceTd" | <p>XCOORD</p>
 
|  class="confluenceTd" | <p>X coordinate of taz centroid – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>YCOORD</p>
 
|  class="confluenceTd" | <p>Y coordinate of taz centroid – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>AREA</p>
 
|  class="confluenceTd" | <p>taz area – square feet</p>
 
|-
 
|  class="confluenceTd" | <p>HH10</p>
 
|  class="confluenceTd" | <p>households in taz</p>
 
|-
 
|  class="confluenceTd" | <p>EMP_{by_Industry}</p>
 
|  class="confluenceTd" | <p>{industry} employment in taz</p>
 
|}</div><h4 id="id-4.3DAYSIM-BlockFile"><em>Block File</em></h4><p class="BodyParagraph">The block file used as input to the parcel distribution tool contains key information describing employment by sector and households, which are used to inform the disaggregation of the TAZ-level controls.  There are two primary sources for this block–level information:  Household information the US Census Bureau’s American Community Survey, while information on employment by industrial sector is derived from US Census Bureau’s Local Employment Dynamics database.  Table 4‑5 summarizes the contents of the block file.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-5PARCELALLOCATIONTOOLBLOCKINPUTFILE">TABLE 4-5 PARCEL ALLOCATION TOOL BLOCK INPUT FILE</h4><div class="table-wrap">
 
{|  class="wikitable"
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>DESCRIPTION</strong></p>
 
|-
 
|  class="confluenceTd" | <p>blockid10</p>
 
|  class="confluenceTd" | <p>Block id number</p>
 
|-
 
|  class="confluenceTd" | <p>xcoord</p>
 
|  class="confluenceTd" | <p>X coordinate of block centroid – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>ycoord</p>
 
|  class="confluenceTd" | <p>Y coordinate of block centroid – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>SQFT</p>
 
|  class="confluenceTd" | <p>block area – square feet</p>
 
|-
 
|  class="confluenceTd" | <p>IFE002</p>
 
|  class="confluenceTd" | <p>households in block</p>
 
|-
 
|  class="confluenceTd" | <p>CNS01</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 11 (agriculture, forestry, fishing, and hunting)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS02</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 21 (mining, quarrying, and oil and gas extraction)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS03</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 22 (utilities)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS04</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 23 (construction)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS05</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 31-33 (manufacturing)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS06</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 42 (wholesale trade)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS07</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 44-45 (retail trade)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS08</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 48-49 (transportation and warehousing)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS09</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 51 (information)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS10</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 52 (finance and insurance)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS11</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 53 (real estate and rental and leasing)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS12</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 54 (professional, scientific, and technical services)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS13</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 55 (management of companies and enterprise)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS14</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 56 (administrative and support and waste management and remediation services)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS15</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 61 (educational services)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS16</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 62 (health care and social assistance)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS17</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 71 (arts, entertainment, and recreation)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS18</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 72 (accommodation and food services)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS19</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 81 (other services, except public administration)</p>
 
|-
 
|  class="confluenceTd" | <p>CNS20</p>
 
|  class="confluenceTd" | <p>Number of jobs in NAICS sector 92 (public administration)</p>
 
|-
 
|  class="confluenceTd" | <p>C000</p>
 
|  class="confluenceTd" | <p>Total number of jobs in block</p>
 
|}</div><h4 id="id-4.3DAYSIM-TAZ-BlockIntersectFile"><em>TAZ-Block Intersect File</em></h4><p>The TAZ-block intersect file is the source for the parcel geography.  This file is created by intersecting the Census block geography with the TAZ geography</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-6PARCELALLOCATIONTOOLTAZ-BLOCKINTERSECTINPUTFILE">TABLE 4-6 PARCEL ALLOCATION TOOL TAZ-BLOCK INTERSECT INPUT FILE</h4><div class="table-wrap">
 
{|  class="wikitable"
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>DESCRIPTION</strong></p>
 
|-
 
|  class="confluenceTd" | <p>ID</p>
 
|  class="confluenceTd" | <p>parcel/microzone id number</p>
 
|-
 
|  class="confluenceTd" | <p>XCOORD</p>
 
|  class="confluenceTd" | <p>X coordinate of intersect centroid – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>YCOORD</p>
 
|  class="confluenceTd" | <p>Y coordinate of intersect centroid – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>AREA</p>
 
|  class="confluenceTd" | <p>intersect area – square feet</p>
 
|-
 
|  class="confluenceTd" | <p>TAZID</p>
 
|  class="confluenceTd" | <p>TAZ in which intersect is located</p>
 
|-
 
|  class="confluenceTd" | <p>BLOCKID</p>
 
|  class="confluenceTd" | <p>Block in which intersect is located</p>
 
|}</div><h4 id="id-4.3DAYSIM-SchoolFile"><em>School File</em></h4><p class="BodyParagraph">School location-level information on enrollment is necessary to order to ensure that the proper number of students are being attracted to each school location.  Unlike employment and households, for which we must rely on block-level and TAZ-level information in order to derive parcel-level totals for these attributes, the allocation tool uses school specific information to associate enrollment with parcels.  The data must include information on enrollment by grade for all schools in the region. It is recommended that the school locations be geocoded and visually inspected using land use information and aerial photos to ensure that schools are being placed in their correct locations.  DaySim distinguishes school enrollment into three enrollment sectors:</p><ul><li>Grade school enrollment (K-8)</li><li>High school enrollment (9-12)</li><li>University enrollment (post-secondary)</li></ul><p class="BodyParagraph">Future year school enrollment assumptions may be adjusted either by scaling the enrollment at the existing school locations consistently or by identifying new parcels as locations for schools.  In either case, the amount of the scaled or additional enrollment should be consistent with the expected change in population by age, which can be derived from the trip-based model inputs. The file contents are provided in Table 4‑7.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-7PARCELALLOCATIONTOOLSCHOOLINPUTFILE">TABLE 4-7 PARCEL ALLOCATION TOOL SCHOOL INPUT FILE</h4><div class="table-wrap">
 
{|  class="wikitable"
 
!  class="highlight-red confluenceTh" data-highlight-colour="red" | <p>FIELD</p>
 
!  class="highlight-red confluenceTh" data-highlight-colour="red" | <p>DESCRIPTION</p>
 
|-
 
|  class="confluenceTd" | <p>SCHID</p>
 
|  class="confluenceTd" | <p>School ID</p>
 
|-
 
|  class="confluenceTd" | <p>MZID</p>
 
|  class="confluenceTd" | <p>Parcel/Microzone id</p>
 
|-
 
|  class="confluenceTd" | <p>XCOORD</p>
 
|  class="confluenceTd" | <p>X coordinate of school – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>YCOORD</p>
 
|  class="confluenceTd" | <p>Y coordinate of school – state plane feet</p>
 
|-
 
|  class="confluenceTd" | <p>STUGRD</p>
 
|  class="confluenceTd" | <p>grade school enrollment in taz</p>
 
|-
 
|  class="confluenceTd" | <p>STUHGH</p>
 
|  class="confluenceTd" | <p>high school enrollment in taz</p>
 
|-
 
|  class="confluenceTd" | <p>STUUNI</p>
 
|  class="confluenceTd" | <p>university enrollment in taz</p>
 
|}</div><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">
 
 
{|  class="wikitable"  
 
{|  class="wikitable"  
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
Line 258: Line 107:
 
|  class="confluenceTd" | <p>DISTANCE</p>
 
|  class="confluenceTd" | <p>DISTANCE</p>
 
|  class="confluenceTd" | <p>Shortest path distance in miles</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 parcel 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 parcel input file for DaySim.</p><h4 id="id-4.3DAYSIM-BufferedParcelFile"><em>Buffered Parcel File</em></h4><p class="BodyParagraph">This is a space-delimited delimited ASCII text format file (.dat) with one row of data per parcel and is the primary file used to maintain socioeconomic information. The file begins with several fields that identify the parcel, and describe the physical location and size of the parcel, and then contains fields that describe the quantity of housing, school enrollment, and employment around the parcel 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 parcel file contains information about urban form and the transportation system on and close to the parcel, including the proximity to transit stops and the price and supply of parking.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-13BUFFEREDPARCELFILE">TABLE 4-13 BUFFERED PARCEL 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 “\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">
 
{|  class="wikitable"  
 
{|  class="wikitable"  
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>DESCRIPTION</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>DESCRIPTION</strong></p>
 
|-  
 
|-  
|  class="confluenceTd" | <p>id</p>
+
|  class="confluenceTd" | <p>parcelid</p>
|  class="confluenceTd" | <p>Parcel/Microzone ID number</p>
+
|  class="confluenceTd" | <p>Microzone ID number</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>xcoord_p</p>
 
|  class="confluenceTd" | <p>xcoord_p</p>
Line 282: Line 131:
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>hh_p</p>
 
|  class="confluenceTd" | <p>hh_p</p>
|  class="confluenceTd" | <p>households on parcel</p>
+
|  class="confluenceTd" | <p>households on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>stugrd_p</p>
 
|  class="confluenceTd" | <p>stugrd_p</p>
|  class="confluenceTd" | <p>grade school enrollment on parcel</p>
+
|  class="confluenceTd" | <p>grade school enrollment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>stuhgh_p</p>
 
|  class="confluenceTd" | <p>stuhgh_p</p>
|  class="confluenceTd" | <p>high school enrollment on parcel</p>
+
|  class="confluenceTd" | <p>high school enrollment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>stuuni_p</p>
 
|  class="confluenceTd" | <p>stuuni_p</p>
|  class="confluenceTd" | <p>university enrollment on parcel</p>
+
|  class="confluenceTd" | <p>university enrollment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empedu_p</p>
 
|  class="confluenceTd" | <p>empedu_p</p>
|  class="confluenceTd" | <p>educational employment on parcel</p>
+
|  class="confluenceTd" | <p>educational employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empfoo_p</p>
 
|  class="confluenceTd" | <p>empfoo_p</p>
|  class="confluenceTd" | <p>food employment on parcel</p>
+
|  class="confluenceTd" | <p>food employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empgov_p</p>
 
|  class="confluenceTd" | <p>empgov_p</p>
|  class="confluenceTd" | <p>government employment on parcel</p>
+
|  class="confluenceTd" | <p>government employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empind_p</p>
 
|  class="confluenceTd" | <p>empind_p</p>
|  class="confluenceTd" | <p>industrial employment on parcel</p>
+
|  class="confluenceTd" | <p>industrial employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empmed_p</p>
 
|  class="confluenceTd" | <p>empmed_p</p>
|  class="confluenceTd" | <p>medical employment on parcel</p>
+
|  class="confluenceTd" | <p>medical employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empofc_p</p>
 
|  class="confluenceTd" | <p>empofc_p</p>
|  class="confluenceTd" | <p>office employment on parcel</p>
+
|  class="confluenceTd" | <p>office employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empret_p</p>
 
|  class="confluenceTd" | <p>empret_p</p>
|  class="confluenceTd" | <p>retail employment on parcel</p>
+
|  class="confluenceTd" | <p>retail employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empsvc_p</p>
 
|  class="confluenceTd" | <p>empsvc_p</p>
|  class="confluenceTd" | <p>service employment on parcel</p>
+
|  class="confluenceTd" | <p>service employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empoth_p</p>
 
|  class="confluenceTd" | <p>empoth_p</p>
|  class="confluenceTd" | <p>other employment on parcel</p>
+
|  class="confluenceTd" | <p>other employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>emptot_p</p>
 
|  class="confluenceTd" | <p>emptot_p</p>
|  class="confluenceTd" | <p>total employment on parcel</p>
+
|  class="confluenceTd" | <p>total employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>parkdy_p</p>
 
|  class="confluenceTd" | <p>parkdy_p</p>
|  class="confluenceTd" | <p>offstreet daily parking on parcel</p>
+
|  class="confluenceTd" | <p>offstreet daily parking on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>parkhr_p</p>
 
|  class="confluenceTd" | <p>parkhr_p</p>
|  class="confluenceTd" | <p>offstreet hourly parking on parcel</p>
+
|  class="confluenceTd" | <p>offstreet hourly parking on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>ppricdyp</p>
 
|  class="confluenceTd" | <p>ppricdyp</p>
Line 480: Line 329:
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>dist_lbus</p>
 
|  class="confluenceTd" | <p>dist_lbus</p>
|  class="confluenceTd" | <p>distance to nearest local bus stop from parcel</p>
+
|  class="confluenceTd" | <p>distance to nearest local bus stop from maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>dist_ebus</p>
 
|  class="confluenceTd" | <p>dist_ebus</p>
|  class="confluenceTd" | <p>distance to nearest express bus stop from parcel</p>
+
|  class="confluenceTd" | <p>distance to nearest express bus stop from maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>dist_crt</p>
 
|  class="confluenceTd" | <p>dist_crt</p>
|  class="confluenceTd" | <p>distance to nearest commuter rail stop from parcel</p>
+
|  class="confluenceTd" | <p>distance to nearest commuter rail stop from maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>dist_fry</p>
 
|  class="confluenceTd" | <p>dist_fry</p>
|  class="confluenceTd" | <p>distance to nearest ferry stop from parcel</p>
+
|  class="confluenceTd" | <p>distance to nearest ferry stop from maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>dist_lrt</p>
 
|  class="confluenceTd" | <p>dist_lrt</p>
|  class="confluenceTd" | <p>distance to nearest light rail stop from parcel</p>
+
|  class="confluenceTd" | <p>distance to nearest light rail stop from maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>dist_park</p>
 
|  class="confluenceTd" | <p>dist_park</p>
|  class="confluenceTd" | <p>distance to nearest park from parcel</p>
+
|  class="confluenceTd" | <p>distance to nearest park from maz</p>
|}</div><p class="BodyParagraph">The following are the input files required for buffering process.</p><h4 id="id-4.3DAYSIM-BaseParcelFile"><em>Base Parcel File</em></h4><p class="BodyParagraph">This file contains information regarding location and land-use of parcels. The buffer variable calculations pivot off of this base file. This is an output generated from the distribution tool described earlier and has the following format.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-14BASEPARCEL/MICROZONEFILEFORMAT">TABLE 4-14 BASE PARCEL/MICROZONE FILE FORMAT</h4><div class="table-wrap">
+
|}</div><p class="BodyParagraph">The following are the input files required for buffering process.</p><h4 id="id-4.3DAYSIM-BaseMicrozoneFile"><em>Base Microzone File</em></h4><p class="BodyParagraph">This file contains information regarding location and land-use of maz. The buffer variable calculations pivot off of this base file. This is an output generated from the distribution tool described earlier and has the following format.</p><h4 class="BodyParagraph" id="id-4.3DAYSIM-TABLE4-14BASEMICROZONEFILEFORMAT">TABLE 4-14 BASE MICROZONE FILE FORMAT</h4><div class="table-wrap">
 
{|  class="wikitable"  
 
{|  class="wikitable"  
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
Line 502: Line 351:
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>parcelid</p>
 
|  class="confluenceTd" | <p>parcelid</p>
|  class="confluenceTd" | <p>Parcel/Microzone ID number</p>
+
|  class="confluenceTd" | <p>Microzone ID number</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>xcoord_p</p>
 
|  class="confluenceTd" | <p>xcoord_p</p>
Line 511: Line 360:
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>sqft_p</p>
 
|  class="confluenceTd" | <p>sqft_p</p>
|  class="confluenceTd" | <p>parcel area – square feet</p>
+
|  class="confluenceTd" | <p>maz area – square feet</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>taz_p</p>
 
|  class="confluenceTd" | <p>taz_p</p>
Line 520: Line 369:
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>hh_p</p>
 
|  class="confluenceTd" | <p>hh_p</p>
|  class="confluenceTd" | <p>households on parcel</p>
+
|  class="confluenceTd" | <p>households on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>stugrd_p</p>
 
|  class="confluenceTd" | <p>stugrd_p</p>
|  class="confluenceTd" | <p>grade school enrollment on parcel</p>
+
|  class="confluenceTd" | <p>grade school enrollment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>stuhgh_p</p>
 
|  class="confluenceTd" | <p>stuhgh_p</p>
|  class="confluenceTd" | <p>high school enrollment on parcel</p>
+
|  class="confluenceTd" | <p>high school enrollment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>stuuni_p</p>
 
|  class="confluenceTd" | <p>stuuni_p</p>
|  class="confluenceTd" | <p>university enrollment on parcel</p>
+
|  class="confluenceTd" | <p>university enrollment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empedu_p</p>
 
|  class="confluenceTd" | <p>empedu_p</p>
|  class="confluenceTd" | <p>educational employment on parcel</p>
+
|  class="confluenceTd" | <p>educational employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empfoo_p</p>
 
|  class="confluenceTd" | <p>empfoo_p</p>
|  class="confluenceTd" | <p>food employment on parcel</p>
+
|  class="confluenceTd" | <p>food employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empgov_p</p>
 
|  class="confluenceTd" | <p>empgov_p</p>
|  class="confluenceTd" | <p>government employment on parcel</p>
+
|  class="confluenceTd" | <p>government employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empind_p</p>
 
|  class="confluenceTd" | <p>empind_p</p>
|  class="confluenceTd" | <p>industrial employment on parcel</p>
+
|  class="confluenceTd" | <p>industrial employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empmed_p</p>
 
|  class="confluenceTd" | <p>empmed_p</p>
|  class="confluenceTd" | <p>medical employment on parcel</p>
+
|  class="confluenceTd" | <p>medical employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empofc_p</p>
 
|  class="confluenceTd" | <p>empofc_p</p>
|  class="confluenceTd" | <p>office employment on parcel</p>
+
|  class="confluenceTd" | <p>office employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empret_p</p>
 
|  class="confluenceTd" | <p>empret_p</p>
|  class="confluenceTd" | <p>retail employment on parcel</p>
+
|  class="confluenceTd" | <p>retail employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empsvc_p</p>
 
|  class="confluenceTd" | <p>empsvc_p</p>
|  class="confluenceTd" | <p>service employment on parcel</p>
+
|  class="confluenceTd" | <p>service employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>empoth_p</p>
 
|  class="confluenceTd" | <p>empoth_p</p>
|  class="confluenceTd" | <p>other employment on parcel</p>
+
|  class="confluenceTd" | <p>other employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>emptot_p</p>
 
|  class="confluenceTd" | <p>emptot_p</p>
|  class="confluenceTd" | <p>total employment on parcel</p>
+
|  class="confluenceTd" | <p>total employment on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>parkdy_p</p>
 
|  class="confluenceTd" | <p>parkdy_p</p>
|  class="confluenceTd" | <p>offstreet daily parking on parcel</p>
+
|  class="confluenceTd" | <p>offstreet daily parking on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>parkhr_p</p>
 
|  class="confluenceTd" | <p>parkhr_p</p>
|  class="confluenceTd" | <p>offstreet hourly parking on parcel</p>
+
|  class="confluenceTd" | <p>offstreet hourly parking on maz</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>ppricdyp</p>
 
|  class="confluenceTd" | <p>ppricdyp</p>
Line 572: Line 421:
 
|  class="confluenceTd" | <p>pprichrp</p>
 
|  class="confluenceTd" | <p>pprichrp</p>
 
|  class="confluenceTd" | <p>offstreet hourly parking price</p>
 
|  class="confluenceTd" | <p>offstreet hourly parking price</p>
|}</div><p class="BodyParagraph">Offstreet parking location and pricing information is used in the activity-based models system to influence mode and other choices.  Note that this parking information is focused on publically accessibility off-street locations and does not consider private off-street parking locations (such as those available only to workers in an office building), nor does it consider on-street parking location. Future year parking locations and costs can be easily added to the model system by simply updating the parcel base file to identify parking capacity and costs for individual parcels.  Where data is unavailable or unknown, the parking attributes should be set to 0.</p><h4 id="id-4.3DAYSIM-IntersectionDataFile"><em>Intersection Data File</em></h4><p class="BodyParagraph">A unique measure of urban form that DaySim incorporates is the number of intersections or nodes of different types around a parcel. These intersection types include, dead-ends (1 link), T-intersections (3-links), and tradition intersections (4+ links), and help characterize the pattern of urban development. The intersection data currently used is in a text file and has the following format.</p><h4 id="id-4.3DAYSIM-TABLE4-15INTERSECTIONDATFILEFORMAT">TABLE 4-15 INTERSECTION DAT FILE FORMAT</h4><div class="table-wrap">
+
|}</div><p class="BodyParagraph">Offstreet parking location and pricing information is used in the activity-based models system to influence mode and other choices.  Note that this parking information is focused on publically accessibility off-street locations and does not consider private off-street parking locations (such as those available only to workers in an office building), nor does it consider on-street parking location. Future year parking locations and costs can be easily added to the model system by simply updating the maz base file to identify parking capacity and costs for individual mazs.  Where data is unavailable or unknown, the parking attributes should be set to 0.</p><h4 id="id-4.3DAYSIM-IntersectionDataFile"><em>Intersection Data File</em></h4><p class="BodyParagraph">A unique measure of urban form that DaySim incorporates is the number of intersections or nodes of different types around a maz. These intersection types include, dead-ends (1 link), T-intersections (3-links), and tradition intersections (4+ links), and help characterize the pattern of urban development. The intersection data currently used is in a text file and has the following format.</p><h4 id="id-4.3DAYSIM-TABLE4-15INTERSECTIONDATFILEFORMAT">TABLE 4-15 INTERSECTION DAT FILE FORMAT</h4><div class="table-wrap">
 
{|  class="wikitable"  
 
{|  class="wikitable"  
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
Line 588: Line 437:
 
|  class="confluenceTd" | <p>ycoord_p</p>
 
|  class="confluenceTd" | <p>ycoord_p</p>
 
|  class="confluenceTd" | <p>Y coordinate – state plane feet</p>
 
|  class="confluenceTd" | <p>Y coordinate – state plane feet</p>
|}</div><p>A largely automated process has been developed to calculate these urban form measures based on detailed GIS street centerline files. This is more detailed than the modeled network, which does not include all streets. This GIS process analyses the GIS street centerline file to locate nodes and assigns an intersection type code to them based on the number of links joined to the node.</p><h4 id="id-4.3DAYSIM-TransitStopsFile"><em>Transit Stops File</em></h4><p class="BodyParagraph">In addition to using zone-level information on access times to transit, DaySim also incorporates detailed parcel -level information on the distance to transit by transit sub-mode. The following table summarizes the contents of this file.</p><h4 id="id-4.3DAYSIM-TABLE4-16TRANSITSTOPSFILEFORMAT">TABLE 4-16 TRANSIT STOPS FILE FORMAT</h4><div class="table-wrap">
+
|}</div><p>A largely automated process has been developed to calculate these urban form measures based on detailed GIS street centerline files. This is more detailed than the modeled network, which does not include all streets. This GIS process analyses the GIS street centerline file to locate nodes and assigns an intersection type code to them based on the number of links joined to the node.</p><h4 id="id-4.3DAYSIM-TransitStopsFile"><em>Transit Stops File</em></h4><p class="BodyParagraph">In addition to using zone-level information on access times to transit, DaySim also incorporates detailed maz -level information on the distance to transit by transit sub-mode. The following table summarizes the contents of this file.</p><h4 id="id-4.3DAYSIM-TABLE4-16TRANSITSTOPSFILEFORMAT">TABLE 4-16 TRANSIT STOPS FILE FORMAT</h4><div class="table-wrap">
 
{|  class="wikitable"  
 
{|  class="wikitable"  
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
Line 604: Line 453:
 
|  class="confluenceTd" | <p>ycoord_p</p>
 
|  class="confluenceTd" | <p>ycoord_p</p>
 
|  class="confluenceTd" | <p>Y coordinate – state plane feet</p>
 
|  class="confluenceTd" | <p>Y coordinate – state plane feet</p>
|}</div><p class="BodyParagraph">When developing or updating forecast year or project alternative networks, careful consideration should be given to the location of individual bus stops. In addition to the bus tops located in urban areas of the county, it is also necessary to incorporate bus stop locations for rural transit routes into the model. This fine-grained information is used by DaySim to develop parcel -level estimates of access time to transit.  Ideally, forecast year transit networks would include a similar level of detail.  Forecast year travel model transit network do include information on stop locations as part of the network coding.  However, these stop locations are constrained by the coarser travel model roadway networks, and thus may tend to make transit access times appear longer by not including stops that are on major roads included in the roadway network.  Model users should ensure that the future year transit stop location file used as input to the parcel preparation contains information consistent with expected future year alignments and stop spacing assumptions.</p><h4 id="id-4.3DAYSIM-Parks/OpenSpacesDataStopsFile"><em>Parks/Open Spaces Data Stops File</em></h4><p class="BodyParagraph">A unique feature of DaySim is that it incorporates measures of access to publically accessible open space.  Although open space is clearly an attractor of travel for recreational, social and other purposes, typically open space is not included in travel models because the traditional “size” measures used as input to travel models, such as employment and population, are not good indicators of the attractiveness of open space (i.e. a popular park will often have no employment and no population).  The open space measures incorporated into DaySim capture the proximity of each parcel to the nearest open space, and the amount of open space present in the buffer area around the parcel. The following table describes the format of the file.</p><h4 id="id-4.3DAYSIM-TABLE4-17OPENSPACEDATAFILEFORMAT">TABLE 4-17 OPEN SPACE DATA FILE FORMAT</h4><div class="table-wrap">
+
|}</div><p class="BodyParagraph">When developing or updating forecast year or project alternative networks, careful consideration should be given to the location of individual bus stops. In addition to the bus tops located in urban areas of the county, it is also necessary to incorporate bus stop locations for rural transit routes into the model. This fine-grained information is used by DaySim to develop maz-level estimates of access time to transit.  Ideally, forecast year transit networks would include a similar level of detail.  Forecast year travel model transit network do include information on stop locations as part of the network coding.  However, these stop locations are constrained by the coarser travel model roadway networks, and thus may tend to make transit access times appear longer by not including stops that are on major roads included in the roadway network.  Model users should ensure that the future year transit stop location file used as input to the maz preparation contains information consistent with expected future year alignments and stop spacing assumptions.</p><h4 id="id-4.3DAYSIM-Parks/OpenSpacesDataStopsFile"><em>Parks/Open Spaces Data Stops File</em></h4><p class="BodyParagraph">A unique feature of DaySim is that it incorporates measures of access to publically accessible open space.  Although open space is clearly an attractor of travel for recreational, social and other purposes, typically open space is not included in travel models because the traditional “size” measures used as input to travel models, such as employment and population, are not good indicators of the attractiveness of open space (i.e. a popular park will often have no employment and no population).  The open space measures incorporated into DaySim capture the proximity of each maz to the nearest open space, and the amount of open space present in the buffer area around the maz. The following table describes the format of the file.</p><h4 id="id-4.3DAYSIM-TABLE4-17OPENSPACEDATAFILEFORMAT">TABLE 4-17 OPEN SPACE DATA FILE FORMAT</h4><div class="table-wrap">
 
{|  class="wikitable"  
 
{|  class="wikitable"  
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
Line 620: Line 469:
 
|  class="confluenceTd" | <p>sqft</p>
 
|  class="confluenceTd" | <p>sqft</p>
 
|  class="confluenceTd" | <p>Open space grid cell size in sq ft</p>
 
|  class="confluenceTd" | <p>Open space grid cell size in sq ft</p>
|}</div><p class="BodyParagraph">The individual records in the open space file are based on converting a shapefile of regional, publically accessibility open spaces into a smaller set of open space grid cells.</p><p class="BodyParagraph">If all streets network based short trip distances need to be used, the buffering program requires two additional input files that are described in the previous section on short distance impedance generation:</p><ul><li>Node file (input_node.csv)</li><li>Node-to-node distance file (output_shortest_path.txt)</li></ul><h3 id="id-4.3DAYSIM-DaySimInputs"><span style="color: rgb(255,102,0);">DaySim Inputs</span></h3><h4 id="id-4.3DAYSIM-Parcels"><em>Parcels</em></h4><p class="BodyParagraph">The final parcel data input file is a tab-delimited ASCII text format file created by the project team. This file has the main land use inputs, including parcel-specific values, and buffered measures. DaySim can read these variables in any order, but the variable names must remain the same as those in Table 4‑13. Currently, this file is \Master\{SCENARIO_DIR}\ Input\DaySimInput\02_Parcel\ Jacksonville_parcel_decayandCirc.dat.</p><h4 id="id-4.3DAYSIM-SyntheticPopulation"><em>Synthetic Population</em></h4><p class="BodyParagraph">Tools used to convert PopGen outputs to DaySim format can be found in \User.prg\DaySim_Inputs\2_PopGen. The household file, an input to DaySim, contains household-level variable and is Master\{SCENARIO_DIR}\ Input\DaySimInput\03_Household\_jax_hrec.dat.</p><h4 id="id-4.3DAYSIM-TABLE4-18SYNTHETICPOPULATIONHOUSEHOLDFILE">TABLE 4-18 SYNTHETIC POPULATION HOUSEHOLD FILE</h4><div class="table-wrap">
+
|}</div><p class="BodyParagraph">The individual records in the open space file are based on converting a shapefile of regional, publically accessibility open spaces into a smaller set of open space grid cells.</p><p class="BodyParagraph">If all streets network based short trip distances need to be used, the buffering program requires two additional input files that are described in the previous section on short distance impedance generation:</p><ul><li>Node file (input_node.csv)</li><li>Node-to-node distance file (output_shortest_path.txt)</li></ul><h3 id="id-4.3DAYSIM-DaySimInputs"><span style="color: rgb(255,102,0);">DaySim Inputs</span></h3><h4 id="id-4.3DAYSIM-Microzones"><em>Microzones</em></h4><p class="BodyParagraph">The final microzones data input file is a tab-delimited ASCII text format file created by the project team. This file has the main land use inputs, including microzones-specific values, and buffered measures. DaySim can read these variables in any order, but the variable names must remain the same as those in Table 4‑13. Currently, this file is \Master\{SCENARIO_DIR}\ Input\DaySimInput\02_Parcel\ buffered_maz_2015.dat.</p><h4 id="id-4.3DAYSIM-SyntheticPopulation"><em>Synthetic Population</em></h4><p class="BodyParagraph">Tools used to convert PopulationSim outputs to DaySim format can be found in \User.prg\Population_Synthesis. The household file, an input to DaySim, contains household-level variable and is Master\{SCENARIO_DIR}\ Input\DaySimInput\03_Household\household_2015.dat.</p><h4 id="id-4.3DAYSIM-TABLE4-18SYNTHETICPOPULATIONHOUSEHOLDFILE">TABLE 4-18 SYNTHETIC POPULATION HOUSEHOLD FILE</h4><div class="table-wrap">
 
{|  class="wikitable"  
 
{|  class="wikitable"  
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
 
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p><strong>FIELD</strong></p>
Line 670: Line 519:
 
|  class="confluenceTd" | <p>Household residence type</p>
 
|  class="confluenceTd" | <p>Household residence type</p>
 
|-  
 
|-  
|  class="confluenceTd" | <p>HHPARCEL</p>
+
|  class="confluenceTd" | <p>HHMAZ</p>
|  class="confluenceTd" | <p>Residence parcel id</p>
+
|  class="confluenceTd" | <p>Residence MAZ id</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>HHTAZ</p>
 
|  class="confluenceTd" | <p>HHTAZ</p>
Line 705: Line 554:
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>PWPCL</p>
 
|  class="confluenceTd" | <p>PWPCL</p>
|  class="confluenceTd" | <p>usual work parcel id</p>
+
|  class="confluenceTd" | <p>usual work maz id</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>PWTAZ</p>
 
|  class="confluenceTd" | <p>PWTAZ</p>
Line 720: Line 569:
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>PSPCL</p>
 
|  class="confluenceTd" | <p>PSPCL</p>
|  class="confluenceTd" | <p>usual school parcel id</p>
+
|  class="confluenceTd" | <p>usual school maz id</p>
 
|-  
 
|-  
 
|  class="confluenceTd" | <p>PSTAZ</p>
 
|  class="confluenceTd" | <p>PSTAZ</p>

Latest revision as of 23:02, 26 August 2020


Contents

Short Distance Impedance Generation

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:

  • Node file
  • Link file
  • Link type file
  • Node pairs file

Node File

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.

TABLE 4-8 DTALITE INPUT NODE FILE FORMAT

FIELD

DESCRIPTION

NODEID

Node id number

XCOORD

X coordinate of node– state plane feet

YCOORD

Y coordinate of node – state plane feet

Link File

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.

TABLE 4-9 DTALITE INPUT LINK FILE FORMAT

FIELD

DESCRIPTION

REQUIRED

FROM_NODE_ID

A node of the link

Yes

TO_NODE_ID

B node of the link

Yes

LINK_ID

Link id number

Yes

LENGTH_IN_MILE

Link length in miles

Yes

DIRECTION

Direction of the link

No

NAME

Name of the link

No

SPEED_LIMIT_IN_MPH

Speed limit

No

NUMBER_OF_LANES

Number of lanes

No

LINK_TYPE

Type of link

No

LANE_CAPACITY_IN_VHC_PER_HOUR

Lane capacity

No

Link Type File

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.

TABLE 4-10 DTALITE INPUT LINK TYPE FILE FORMAT

FIELD

DESCRIPTION

LINK_TYPE

Link type code

LINK_TYPE_NAME

Link type name

FREEEWAY_FLAG

1 if freeway; 0 otherwise

RAMP_FLAG

1 if ramp; 0 otherwise

ARTERIAL_FLAG

1 if arterial; 0 otherwise

Node Pairs File

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.

TABLE 4-11 DTALITE INPUT NODE PAIRS FILE FORMAT

FIELD

DESCRIPTION

RECORD_ID

Record id number

ORIGIN_NODE_ID

Origin node id

DEST_NODE_ID

Destination node id

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.

Node-to-Node Distance File

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.

TABLE 4-12 DTALITE OUTPUT NODE DISTANCE FILE FORMAT

FIELD

DESCRIPTION

RECORD_ID

Record id number

FROM_NODE_ID

Origin node id

TO_NODE_ID

Destination node id

DISTANCE

Shortest path distance in miles

DaySim Buffering Tool

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.

Buffered MAZ File

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/8th 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.

TABLE 4-13 BUFFERED MAZ FILE

FIELD

DESCRIPTION

parcelid

Microzone ID number

xcoord_p

X coordinate – state plane feet

ycoord_p

Y coordinate – state plane feet

sqft_p

Area – square feet

taz_p

TAZ number

lutype_p

land use type

hh_p

households on maz

stugrd_p

grade school enrollment on maz

stuhgh_p

high school enrollment on maz

stuuni_p

university enrollment on maz

empedu_p

educational employment on maz

empfoo_p

food employment on maz

empgov_p

government employment on maz

empind_p

industrial employment on maz

empmed_p

medical employment on maz

empofc_p

office employment on maz

empret_p

retail employment on maz

empsvc_p

service employment on maz

empoth_p

other employment on maz

emptot_p

total employment on maz

parkdy_p

offstreet daily parking on maz

parkhr_p

offstreet hourly parking on maz

ppricdyp

offstreet daily parking price

pprichrp

offstreet hourly parking price

hh_1

households within buffer 1

stugrd_1

grade school enrollment within buffer 1

stuhgh_1

high school enrollment within buffer 1

stuuni_1

university enrollment within buffer 1

empedu_1

educational employment within buffer 1

empfoo_1

food employment within buffer 1

empgov_1

government employment within buffer 1

empind_1

industrial employment within buffer 1

empmed_1

medical employment within buffer 1

empofc_1

office employment within buffer 1

empret_1

retail employment within buffer 1

empsvc_1

service employment within buffer 1

empoth_1

other employment within buffer 1

emptot_1

total employment within buffer 1

parkdy_1

offstreet daily parking within buffer 1

parkhr_1

offstreet hourly parking within buffer 1

ppricdy1

average offstreet daily parking price within buffer 1

pprichr1

average offstreet hourly parking price within buffer 1

nodes1_1

number of single link street nodes (dead ends) within buffer 1

nodes3_1

number of three-link street nodes (T-intersections) within buffer 1

nodes4_1

number of 4+ link street nodes (traditional 4-way +) within buffer 1

tstops_1

number of transit stops within buffer 1

nparks_1

number of open space parks within buffer 1

aparks_1

open space area in square feet within buffer 1

hh_2

households within buffer 2

stugrd_2

grade school enrollment within buffer 2

stuhgh_2

high school enrollment within buffer 2

stuuni_2

university enrollment within buffer 2

empedu_2

educational employment within buffer 2

empfoo_2

food employment within buffer 2

empgov_2

government employment within buffer 2

empind_2

industrial employment within buffer 2

empmed_2

medical employment within buffer 2

empofc_2

office employment within buffer 2

empret_2

retail employment within buffer 2

empsvc_2

service employment within buffer 2

empoth_2

other employment within buffer 2

emptot_2

total employment within buffer 2

parkdy_2

offstreet daily parking within buffer 2

parkhr_2

offstreet hourly parking within buffer 2

ppricdy2

average offstreet daily parking price within buffer 2

pprichr2

average offstreet hourly parking price within buffer 2

nodes1_2

number of single link street nodes (dead ends) within buffer 2

nodes3_2

number of three-link street nodes (T-intersections) within buffer 2

nodes4_2

number of 4+ link street nodes (traditional 4-way +) within buffer 2

tstops_2

number of transit stops within buffer 2

nparks_2

number of open space parks within buffer 2

aparks_2

open space area in square feet within buffer 2

dist_lbus

distance to nearest local bus stop from maz

dist_ebus

distance to nearest express bus stop from maz

dist_crt

distance to nearest commuter rail stop from maz

dist_fry

distance to nearest ferry stop from maz

dist_lrt

distance to nearest light rail stop from maz

dist_park

distance to nearest park from maz

The following are the input files required for buffering process.

Base Microzone File

This file contains information regarding location and land-use of maz. The buffer variable calculations pivot off of this base file. This is an output generated from the distribution tool described earlier and has the following format.

TABLE 4-14 BASE MICROZONE FILE FORMAT

FIELD

DESCRIPTION

parcelid

Microzone ID number

xcoord_p

X coordinate – state plane feet

ycoord_p

Y coordinate – state plane feet

sqft_p

maz area – square feet

taz_p

corresponding TAZ number

block_p

corresponding census block number

hh_p

households on maz

stugrd_p

grade school enrollment on maz

stuhgh_p

high school enrollment on maz

stuuni_p

university enrollment on maz

empedu_p

educational employment on maz

empfoo_p

food employment on maz

empgov_p

government employment on maz

empind_p

industrial employment on maz

empmed_p

medical employment on maz

empofc_p

office employment on maz

empret_p

retail employment on maz

empsvc_p

service employment on maz

empoth_p

other employment on maz

emptot_p

total employment on maz

parkdy_p

offstreet daily parking on maz

parkhr_p

offstreet hourly parking on maz

ppricdyp

offstreet daily parking price

pprichrp

offstreet hourly parking price

Offstreet parking location and pricing information is used in the activity-based models system to influence mode and other choices. Note that this parking information is focused on publically accessibility off-street locations and does not consider private off-street parking locations (such as those available only to workers in an office building), nor does it consider on-street parking location. Future year parking locations and costs can be easily added to the model system by simply updating the maz base file to identify parking capacity and costs for individual mazs. Where data is unavailable or unknown, the parking attributes should be set to 0.

Intersection Data File

A unique measure of urban form that DaySim incorporates is the number of intersections or nodes of different types around a maz. These intersection types include, dead-ends (1 link), T-intersections (3-links), and tradition intersections (4+ links), and help characterize the pattern of urban development. The intersection data currently used is in a text file and has the following format.

TABLE 4-15 INTERSECTION DAT FILE FORMAT

FIELD

DESCRIPTION

id

Intersection ID number

links

Number of links associated with node

xcoord_p

X coordinate – state plane feet

ycoord_p

Y coordinate – state plane feet

A largely automated process has been developed to calculate these urban form measures based on detailed GIS street centerline files. This is more detailed than the modeled network, which does not include all streets. This GIS process analyses the GIS street centerline file to locate nodes and assigns an intersection type code to them based on the number of links joined to the node.

Transit Stops File

In addition to using zone-level information on access times to transit, DaySim also incorporates detailed maz -level information on the distance to transit by transit sub-mode. The following table summarizes the contents of this file.

TABLE 4-16 TRANSIT STOPS FILE FORMAT

FIELD

DESCRIPTION

id

Transit stop ID number

mode

Transit submode code

1=local bus

2=express bus

3=commuter rail

4=ferry

5=light rail

xcoord_p

X coordinate – state plane feet

ycoord_p

Y coordinate – state plane feet

When developing or updating forecast year or project alternative networks, careful consideration should be given to the location of individual bus stops. In addition to the bus tops located in urban areas of the county, it is also necessary to incorporate bus stop locations for rural transit routes into the model. This fine-grained information is used by DaySim to develop maz-level estimates of access time to transit. Ideally, forecast year transit networks would include a similar level of detail. Forecast year travel model transit network do include information on stop locations as part of the network coding. However, these stop locations are constrained by the coarser travel model roadway networks, and thus may tend to make transit access times appear longer by not including stops that are on major roads included in the roadway network. Model users should ensure that the future year transit stop location file used as input to the maz preparation contains information consistent with expected future year alignments and stop spacing assumptions.

Parks/Open Spaces Data Stops File

A unique feature of DaySim is that it incorporates measures of access to publically accessible open space. Although open space is clearly an attractor of travel for recreational, social and other purposes, typically open space is not included in travel models because the traditional “size” measures used as input to travel models, such as employment and population, are not good indicators of the attractiveness of open space (i.e. a popular park will often have no employment and no population). The open space measures incorporated into DaySim capture the proximity of each maz to the nearest open space, and the amount of open space present in the buffer area around the maz. The following table describes the format of the file.

TABLE 4-17 OPEN SPACE DATA FILE FORMAT

FIELD

DESCRIPTION

id

Open space ID number

xcoord_p

X coordinate – state plane feet

ycoord_p

Y coordinate – state plane feet

sqft

Open space grid cell size in sq ft

The individual records in the open space file are based on converting a shapefile of regional, publically accessibility open spaces into a smaller set of open space grid cells.

If all streets network based short trip distances need to be used, the buffering program requires two additional input files that are described in the previous section on short distance impedance generation:

  • Node file (input_node.csv)
  • Node-to-node distance file (output_shortest_path.txt)

DaySim Inputs

Microzones

The final microzones data input file is a tab-delimited ASCII text format file created by the project team. This file has the main land use inputs, including microzones-specific values, and buffered measures. DaySim can read these variables in any order, but the variable names must remain the same as those in Table 4‑13. Currently, this file is \Master\{SCENARIO_DIR}\ Input\DaySimInput\02_Parcel\ buffered_maz_2015.dat.

Synthetic Population

Tools used to convert PopulationSim outputs to DaySim format can be found in \User.prg\Population_Synthesis. The household file, an input to DaySim, contains household-level variable and is Master\{SCENARIO_DIR}\ Input\DaySimInput\03_Household\household_2015.dat.

TABLE 4-18 SYNTHETIC POPULATION HOUSEHOLD FILE

FIELD

DESCRIPTION

HHNO

Household id

HHSIZE

Household size

HHVEHS

Vehicles available

HHWKRS

Household workers

HHFTW

HH full time workers (type 1)

HHPTW

HH part time workers (type 2)

HHRET

HH retired adults (type 3)

HHOAD

HH other adults (type 4)

HHUNI

HH college students (type 5)

HHHSC

HH high school students (type 6)

HH515

HH kids age 5-15 (type 7)

HHCU5

HH kids age 0-4 (type 8)

HHINCOME

Household income ($)

HOWNRENT

Household own or rent

HRESTYPE

Household residence type

HHMAZ

Residence MAZ id

HHTAZ

Residence TAZ index number

HHEXPFAC

HH expansion factor

SAMPTYPE

Sample type (permanent, seasonal, groupquarter)

The person file, an input to DaySim, contains person-level variables and is Master\{SCENARIO_DIR}\ Input\DaySimInput\04_Person\_jax_prec.dat.

TABLE 4-19 SYNTHETIC POPULATION PERSON FILE

FIELD

DESCRIPTION

HHNO

Household id

PNO

person sequential id number on file

PPTYP

person type

PAGEY

age in years

PGEND

gender

PWTYP

worker type

PWPCL

usual work maz id

PWTAZ

usual work TAZ

PWAUTIME

auto time to usual work

PWAUDIST

auto distance to usual work

PSTYP

student type

PSPCL

usual school maz id

PSTAZ

usual school TAZ

PSAUTIME

auto time to usual work

PSAUDIST

auto distance to usual work

PUWMODE

usual mode to work

PUWARRP

Usual arrival period to work

PUWDEPP

Usual depart period from work

PTPASS

0/1 - 1 indicates an transit pass

PPAIDPRK

0/1 - 1 indicates paid parking available at workplace

PDIARY

0/1 - 1 indicates Person used paper diary

PPROXY

0/1 - 1 indicates an proxy response

PSEXPFAC

Person expansion factor

Worker IXXI Fraction

The IXXI fractions file has the fraction of workers in each zone who work outside the region, and the fraction of jobs filled by workers from outside the region. This file is an ASCII space-delimited file. Its location is Master\{SCENARIO_DIR}\ Input\DaySimInput\05_ixxi\ _jax_worker_ixxifractions.dat.

TABLE 4-20 WORKER IXXI FRACTION FILE

FIELD

DESCRIPTION

ZoneID

The TAZ number

Worker_IXFrac

The fraction of workers living in the zone who work outside the region

Jobs_XIFrac

The fraction of jobs in the zone filled by workers from outside the region

TAZ Indexes

The TAZ index file assigns a continuous numbering to the zones. External zones are also identifies in the file. The file is in ASCII space-delimited file with header. Its location is \Master\{SCENARIO_DIR}\ Input\DaySimInput\ 01_TAZ_Index\ _jax_taz_indexes.dat.

TABLE 4-21 TAZ INDEX FILE

FIELD

DESCRIPTION

ZoneID

The TAZ number

Zone_ordinal

A zone index number, generally starting at 1, with no gaps

Dest_eligible

0/1 - 1 indicates an internal zone that is eligible as a destination in Daysim

External

0/1 - 1 indicates an external zone, not eligible as a destination in Daysim

PNR Nodes

The PNR node file contains PNR location ids and corresponding capacity and parking cost. The file is ASCII space-delimited. Its location is \Master\{SCENARIO_DIR}\ Input\DaySimInput\ 05_pnr\ jax_p_rNodes.dat.

TABLE 4-22 PNR NODE FILE

FIELD

DESCRIPTION

NodeID

The park and ride node ID (can be the same as the ZoneID)

ZoneID

The TAZ number

XCoord

The X coordinate (in length units) of the park and ride node

YCoord

The Y coordinate (in length units) of the park and ride node

Capacity

The total capacity, in spaces, of the park and ride lot

Cost

The daily parking cost, in hundredths of monetary units, of the park and ride lot

PNR

PNR flag (1/99)

KNR

KNR flag (1/99)

Coefficients

Coefficient for each model is a separate text file (.F12 format) that can be edited by the user for calibration purpose. There are a total of 23 files corresponding to all the models. All coefficient files are in the same directory at \User.prg\DaySim\07_Coefficients. For example, the person day pattern model coefficient is a file named IndividualPersonDayPatternCoefficients_Jacksonville-v.5.F12 at that directory.

FIGURE 4-1 COEFFICIENT FILE EXAMPLE

<img class="confluence-embedded-image" src="/wiki/download/attachments/1179712/Figure%204-1.png?version=1&modificationDate=1433178311313&api=v2" data-image-src="/wiki/download/attachments/1179712/Figure%204-1.png?version=1&modificationDate=1433178311313&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="1179718" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Figure 4-1.png" data-base-url="https://rsginc.atlassian.net/wiki" data-linked-resource-content-type="image/png" data-linked-resource-container-id="1179712" data-linked-resource-container-version="6">

Roster

Skim files report the level of services on regional network. All skim files are in text (*.TXT) format. The roster file is a CSV file that lists all the impedance skim files to be read and used by Daysim. Its location is \Master\{SCENARIO_DIR}\ Input\DaySimInput\ 06_Roster\roster_jax.csv.

TABLE 4-23 ROSTER FILE

FIELD

DESCRIPTION

#variable

Skim variable, with string that is used in the C# code

mode

Skim mode, valid values are walk, bike, SOV, HOV2, HOV3, and transit

path-type

Path type, valid values are full-network, bus, knr-bus, pnr-bus

vot-group

Value of time range, valid values are very-low, low, medium, high, and very-high (currently all values are medium)

start-minute

First minute for which skim applies, in minutes past midnight

end-minute

Last minute for which skim applies, in minutes past midnight (if lower than start-minute, then period spans midnight

length

Size of matrix (currently all values are maxzone)

File-type

Type of input file, current valid values are Text_IJ, BIN and null (leave as 0)

name

File name (assumes same directory as roster file). Null is assumed for file type null

field

The field on the file (use 1 for BIN, for Text-IJ, the O and D zones are fields 1 and 2)

transpose

If TRUE, DaySim will use the transpose of the matrix that is read in

blend-variable

Variable that is used for short distance "blending" - the same mode is assumed

blend-path-type

Allows blending variable to be for a different path type, If null, same path type is assumed

factor

A factor to be applied to the matrix - e.g. 20 to turn walk distance to time. (If null, factor is 1)

scaling

If TRUE, matrix is scaled by 100 before being stored as a 2-byte integer. (BIN matrices are assumed to already be scaled)

Roster Combination

The "Roster Combinations" file gives the possible mode/path type combinations used in DaySim. It is a CSV file at \Master\{SCENARIO_DIR}\ Input\DaySimInput\ 06_Roster\roster.combinations_Jax.csv. The file has columns that enumerate the 9 modes used in the current model system (walk, bike, SOV, HOV2, HOV3, transit, park-and-ride, school-bus, other) and 8 rows that enumerate the path types currently used. The cells are TRUE for valid combinations within DaySim and FALSE otherwise.

TABLE 4-24 ROSTER COMBINATION FILE EXAMPLE

#

WALK

BIKE

SOV

HOV2

HOV3

TRANSIT

PNR

full-network

TRUE

TRUE

TRUE

TRUE

TRUE

TRUE

TRUE

no-tolls

FALSE

FALSE

TRUE

TRUE

TRUE

FALSE

FALSE

bus

FALSE

FALSE

FALSE

FALSE

FALSE

TRUE

FALSE

project

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

pnr-bus

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

TRUE

pnr-project

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

knr-bus

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

TRUE

knr-project

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

Configuration

The configuration file is the main user input control file for DaySim. This file is an XML format. When running DaySim, the name of the configuration file and the name of the print log file can be given as command-line arguments. An example is:

Daysim – c [configuration_file_name] – p [print_file_name]

Setting

Value

Description

ChoiceModelRunner

Default

Type of choice model runner

DataType

Default

Identifies the presence of client-specific household input data (currently only used for Actum)

Settings

DefaultSettings

WorkingSubpath

".\working"

Working directory name

OutputSubpath

".\outputs"

Output directory name

EstimationSubpath

".\estimation"

If estimation mode, estimation directory name

RandomSeed

1234

Initial seed value for the random number generator

ShouldSynchronizeRandomSeed

TRUE

If true, Daysim will use a seed for each person/tour/trip/model combination that depends only on the initial seed

NumberOfRandomSeeds

1000

Number of random seeds

RosterPath

.\jacksonville-roster_matrix.csv

Name of roster CSV file, including full directory path

RosterCombinationsPath

.\jacksonville_roster.combinations.csv

Name of valid roster combinations CSV file, including full directory path

SkimDelimiter

"44"

The delimiter for text_IJ (ascii text) skim input files (9=TAB, 32=space, 44=comma)

VotVeryLowLow

0

Boundary between VeryLow and Low VOT groups, in Monetary units per hour

VotLowMedium

6.78

Boundary between Low and Medium VOT groups, in Monetary units per hour

VotMediumHigh

20.89

Boundary between Medium and High VOT groups, in Monetary units per hour

VotHighVeryHigh

1001

Boundary between High and VeryHigh VOT groups, in Monetary units per hour

IxxiPath

.\jacksonville_worker_IXXIfractions.dat

The full path name for the input worker IXXI fractions file

IxxiDelimiter

32

The delimiter for the input file (9=TAB, 32=space, 44=comma)

IxxiFirstLineIsHeader

FALSE

If true, DaySim expects a header record for this file (all other raw data' files have headers)

RawParkAndRideNodePath

.\p_r_Nodes.dat

The full path name for the raw park and ride node file. (If none given, the park and ride mode will not be available)

RawParkAndRideNodeDelimiter

9

The delimiter for the input file (9=TAB, 32=space, 44=comma)

ImportParkAndRideNodes

TRUE

If TRUE, the raw file should be imported (always TRUE if ShouldRunRawConversion=true)

ShouldReadParkAndRideNodeSkim

FALSE

If true, will expect a skim matrix with the best park and ride node number for each OD pair

RawParcelPath

.\Jacksonville_mzbuffer_stline_1.dat

The full path name for the raw parcel or microzone input file

RawParcelDelimiter

32

The delimiter for the input file (9=TAB, 32=space, 44=comma)

RawZonePath

.\jacksonville_taz_indexes_1.dat

The full path name for the raw zone indexes input file

RawZoneDelimiter

9

The delimiter for the input file (9=TAB, 32=space, 44=comma)

RawHouseholdPath

.\jacksonville_household.dat

The full path name for the raw household input file

RawHouseholdDelimiter

32

The delimiter for the input file (9=TAB, 32=space, 44=comma)

OutputHouseholdPath

.\_household.tsv

The full path name for the household output file

OutputHouseholdDelimiter

9

The delimiter for the output file (9=TAB, 32=space, 44=comma)

RawPersonPath

.\jacksonville_person.dat

The full path name for the raw person input file

RawPersonDelimiter

32

The delimiter for the input file (9=TAB, 32=space, 44=comma)

OutputPersonPath

.\_person.tsv

The full path name for the person output file

OutputPersonDelimiter

9

The delimiter for the output file (9=TAB, 32=space, 44=comma)

OutputHouseholdDayPath

.\_household_day.tsv

The full path name for the household-day output file

OutputHouseholdDayDelimiter

9

The delimiter for the output file (9=TAB, 32=space, 44=comma)

OutputPersonDayPath

.\_person_day.tsv

The full path name for the person-day output file

OutputPersonDayDelimiter

9

The delimiter for the output file (9=TAB, 32=space, 44=comma)

OutputTourPath

.\_tour.tsv

The full path name for the tour output file

OutputTourDelimiter

9

The delimiter for the output file (9=TAB, 32=space, 44=comma)

OutputTripPath

.\_trip.tsv

The full path name for the trip output file

OutputTripDelimiter

9

The delimiter for the input file (9=TAB, 32=space, 44=comma)

ShouldRunRawConversion

TRUE

If true, DAYSIM will convert and input all of the raw data files listed below

MinParcelSize

10

The minimum microzone size variable (in units of 1/1000) to be considered available in destination sampling

UrbanThreshold

500

The minimum parcel size (based on households + employment in buffer 1) to be considered "urban" rather than "rural". (Used in auto ownership model calibration)

IsInEstimationMode

FALSE

TRUE if DaySim should be run in order to estimate a specific model, rather than running a simulation

ShouldRunChoiceModels

TRUE

A toggle switch to run all choice models (TRUE can be overridden by switches below and by individual model switches)

ShouldRunHouseholdModels

TRUE

A toggle switch to run household level models (used to perform partial runs, TRUE can be overridden by individual model switches)

ShouldRunPersonModels

TRUE

A toggle switch to run person level models (used to perform partial runs, TRUE can be overridden by individual model switches)

ShouldRunPersonDayModels

TRUE

A toggle switch to run person-day level models (used to perform partial runs, TRUE can be overridden by individual model switches)

ShouldRunTourModels

TRUE

A toggle switch to run tour level models (used to perform partial runs, TRUE can be overridden by individual model switches)

ShouldRunTourTripModels

TRUE

A toggle switch to run trip level models (used to perform partial runs, TRUE can be overridden by individual model switches)

ShouldRunSubtourModels

TRUE

A toggle switch to run subtour level models (used to perform partial runs, TRUE can be overridden by individual model switches)

ShouldRunSubtourTripModels

TRUE

A toggle switch to run trip level models for subtours (used to perform partial runs, TRUE can be overridden by individual model switches)

DestinationScale

0

EstimationModel

none

The name of the specific model to be estimated

ShouldOutputAlogitData

FALSE

TRUE if an Alogit data file for model estimation should be written

OutputAlogitDataPath

.\xxx.dat

The full pathname of the Alogit data file for model estimation

OutputAlogitControlPath

.\xxx.alo

The full pathname of the Alogit control (.ALO) file for model estimation

MaximumBlendingDistance

3

The maximum (network) distance for which short-distance blending should be used, in miles

ShowRunChoiceModelsStatus

TRUE

TRUE to show percent of households simulated on the screen during simulation

LargeDegreeOfParallelism

8

Controls the use of multiple processors for threading

SmallDegreeOfParallelism

4

Controls the use of multiple processors for threading

ShouldOutputTDMTripList

FALSE

TRUE to produce a separate trip list output file for use by other models

OutputTDMTripListPath

.\transims_trip_list.csv

The full path name of the output trip list file

TDMTripListDelimiter

44

The delimiter for the output file (9=TAB, 32=space, 44=comma)

UseTransimsTDMTripListFormat

TRUE

TRUE to write the output trip list file in the format to be used by Transims

PathImpedance_PathChoiceScaleFactor

1.5

A scale factor for the coefficients of the path type models (the inverse of a logsum coefficient in upper level models)

PathImpedance_AutoOperatingCostPerMile

0.12

The auto operating cost, in Monetary Units per Distance Unit

PathImpedance_TransitInVehicleTimeWeight

1

The relative weight on transit in-vehicle time in the transit and park and ride path type models

PathImpedance_TransitFirstWaitTimeWeight

2

The relative weight on transit first wait time in the transit and park and ride path type models

PathImpedance_TransitTransferWaitTimeWeight

2

The relative weight on transit transfer wait time in the transit and park and ride path type models

PathImpedance_TransitNumberBoardingsWeight

4

The relative weight on transit number of boardings in the transit and park and ride path type models

PathImpedance_TransitDriveAccessTimeWeight

2

The relative weight on transit drive access in-vehicle time in the park and ride path type models

PathImpedance_TransitWalkAccessTimeWeight

2

The relative weight on transit walk access and egress times in the transit and park and ride path type models

PathImpedance_WalkTimeWeight

2

The relative weight on walk mode time in the walk path type model

PathImpedance_BikeTimeWeight

2

The relative weight on bike mode time in the bike path type model

PathImpedance_WalkMinutesPerMile

20

The factor to convert parcel-based transit walk access/egress distance into time (in minutes per distance unit)

PathImpedance_TransitWalkAccessDistanceLimit

2

The maximum parcel-based transit walk access or egress distance allowed for available transit paths

PathImpedance_TransitWalkAccessDirectLimit

1

The maximum parcel-based transit walk access or egress distance allowed for direct transit paths to be chosen over mixed paths

PathImpedance_TransitSingleBoardingLimit

1.1

The maximum number of boardings for a transit path to be considered a "direct path" (no transfers)

PathImpedance_AutoTolledPathConstant

0

The path type constant for an auto path that includes a non-zero toll cost (reflects extra resistance to paying tolls)

PathImpedance_AvailablePathUpperTimeLimit

180

The maximum total (unweighted) path travel time for a path to be considered as an available option

PathImpedance_TransitLocalBusPathConstant

0

The path type constant for transit local bus only paths

PathImpedance_TransitPremiumBusPathConstant

0

The path type constant for transit premium bus (possibly plus feeder) paths

PathImpedance_TransitLightRailPathConstant

0.156

The path type constant for transit light rail (possibly plus feeder) paths

PathImpedance_TransitCommuterRailPathConstant

0.45

The path type constant for transit commuter rail (possibly plus feeder) paths

PathImpedance_TransitFerryPathConstant

0.45

The path type constant for transit passenger ferry (possibly plus feeder) paths

PathImpedance_TransitUsePathTypeSpecificTime

FALSE

A switch to use additional skims and weights to reflect transit submode-specific in-vehicle times (SACOG-specific)

PathImpedance_TransitPremiumBusTimeAdditiveWeight

0

An additive weight on premium bus submode-specific in-vehicle time (adds to TransitInVehicleTimeWeight)

PathImpedance_TransitLightRailTimeAdditiveWeight

-0.07

An additive weight on light rail submode-specific in-vehicle time (adds to TransitInVehicleTimeWeight)

PathImpedance_TransitCommuterRailTimeAdditiveWeight

-0.1

An additive weight on commuter rail submode-specific in-vehicle time (adds to TransitInVehicleTimeWeight)

PathImpedance_TransitFerryTimeAdditiveWeight

-0.05

An additive weight on passenger ferry submode-specific in-vehicle time (adds to TransitInVehicleTimeWeight)

PathImpedance_BikeUseTypeSpecificDistanceFractions

FALSE

A switch to use additional skims and weights to reflect bicycle distances on specific facility types (SACOG-specific)

PathImpedance_BikeType1DistanceFractionAdditiveWeight

0

An additive weight on bike distance on Class 1 bike paths (adds to BikeTimeWeight, distance is converted to time)

PathImpedance_BikeType2DistanceFractionAdditiveWeight

0

An additive weight on bike distance on Class 1 bike paths (adds to BikeTimeWeight, distance is converted to time)

PathImpedance_BikeType3DistanceFractionAdditiveWeight

0

An additive weight on bike distance on Class 1 bike paths (adds to BikeTimeWeight, distance is converted to time)

PathImpedance_BikeType4DistanceFractionAdditiveWeight

0

An additive weight on bike distance on Class 1 bike paths (adds to BikeTimeWeight, distance is converted to time)

PathImpedance_TransitUseFareDiscountFractions

TRUE

A switch to use transit fare discount fractions based on person type and age

PathImpedance_TransitFareDiscountFractionChildUnder5

0.8

Transit fare discount fraction for children under age 5

PathImpedance_TransitFareDiscountFractionChild5To15

0.5

Transit fare discount fraction for children age 5 to 15

PathImpedance_TransitFareDiscountFractionHighSchoolStudent

0.5

Transit fare discount fraction for high school students (children age 16+)

PathImpedance_TransitFareDiscountFractionUniverityStudent

0.5

Transit fare discount fraction for college students

PathImpedance_TransitFareDiscountFractionAge65Up

0.5

Transit fare discount fraction for adults age 65+

PathImpedance_TransitPassCostPercentChangeVersusBase

0

Policy input variable to change the cost of transit passes with respect to the base year

Coefficients_BaseCostCoefficientPerDollar

-0.15

A base cost coefficient (per monetary unit), when income = BaseCostCoefficientIncomeLevel

Coefficients_BaseCostCoefficientIncomeLevel

30000

The household income level (monetary units per year) where the cost coefficient is the BaseCostCoefficient

Coefficients_CostCoefficientIncomePower_Work

0.6

The power function exponent to use for adjusting the cost coefficient for income, for work tours

Coefficients_CostCoefficientIncomePower_Other

0.5

The power function exponent to use for adjusting the cost coefficient for income, for non-work tours

Coefficients_MeanTimeCoefficient_Work

-0.03

The mean time coefficient (/minute) for work tours

Coefficients_MeanTimeCoefficient_Other

-0.015

The mean time coefficient (/minute) for non-work tours

Coefficients_StdDeviationTimeCoefficient_Work

0.24

The standard deviation of the time coefficient (/minute) for work tours, when using random VOT distribution

Coefficients_StdDeviationTimeCoefficient_Other

0.15

The standard deviation of the time coefficient (/minute) for non-work tours, when using random VOT distribution

Coefficients_HOV2CostDivisor_Work

1.741

The divisor for the cost coefficient for the HOV2 mode for work tours (to reflect cost-sharing)

Coefficients_HOV2CostDivisor_Other

1.625

The divisor for the cost coefficient for the HOV2 mode for non-work tours (to reflect cost-sharing)

Coefficients_HOV3CostDivisor_Work

2.408

The divisor for the cost coefficient for the HOV3+ mode for work tours (to reflect cost-sharing)

Coefficients_HOV3CostDivisor_Other

2.158

The divisor for the cost coefficient for the HOV3+ mode for non-work tours (to reflect cost-sharing)

UseRandomVotDistribution

TRUE

TRUE to randomly simulate a time coefficient for each tour, using a log-normal distribution

ShouldRunTrace

FALSE

TRUE to trace the details of the simulation for a specific household (for diagnostics/debugging)

TracePath

.\trace.txt

The full path name for the trace output file

HouseholdIdForTrace

1

The household ID for the trace

ShouldLoadAggregateLogsumsFromFile

FALSE

TRUE to read the aggregate logsums from a file generated by a previous run (otherwise they are re-calculated)

ShouldOutputAggregateLogsums

TRUE

TRUE to write the aggregate logsums to a file for a subsequent run

OutputAggregateLogsumsPath

.\aggregate_logsums.dat

The full path name for the file where the aggregate logsums are written

ShouldLoadSamplingWeightsFromFile

FALSE

TRUE to read the pre-calculated sampling weights from a file generated by a previous run (otherwise they are re-calculated)

ShouldOutputSamplingWeights

TRUE

TRUE to write the pre-calculated sampling weights to a file for a subsequent run

OutputSamplingWeightsPath

.\sampling_weights.dat

The full path name for the file where the sampling weights are written

WorkLocationModelSampleSize

50

The maximum number of destinations to be sampled for this model

WorkLocationModelCoefficients

.\WorkLocationCoefficients_SACOG-v1.5.f12

The full path name for the coefficient file for this model

ShouldRunWorkLocationModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceWorkLocationModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

IncludeWorkLocationModel

TRUE

FALSE to always exclude this model from the set of models to be run (not sure how this is different from ShouldRun?)

SchoolLocationModelSampleSize

50

The maximum number of destinations to be sampled for this model

SchoolLocationModelCoefficients

.\SchoolLocationCoefficients_SACOG-v1.8.f12

The full path name for the coefficient file for this model

ShouldRunSchoolLocationModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceSchoolLocationModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

IncludeSchoolLocationModel

TRUE

FALSE to always exclude this model from the set of models to be run (not sure how this is different from ShouldRun?)

PayToParkAtWorkplaceModelCoefficients

.\PayToParkAtWorkplaceCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunPayToParkAtWorkplaceModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTracePayToParkAtWorkplaceModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

IncludePayToParkAtWorkplaceModel

TRUE

FALSE to always exclude this model from the set of models to be run (not sure how this is different from ShouldRun?)

TransitPassOwnershipModelCoefficients

.\TransitPassOwnershipCoefficients_SACOG-v1.5.f12

The full path name for the coefficient file for this model

ShouldRunTransitPassOwnershipModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceTransitPassOwnershipModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

IncludeTransitPassOwnershipModel

TRUE

FALSE to always exclude this model from the set of models to be run (not sure how this is different from ShouldRun?)

AutoOwnershipModelCoefficients

.\AutoOwnershipCoefficients_SACOG-v1.5.f12

The full path name for the coefficient file for this model

ShouldRunAutoOwnershipModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceAutoOwnershipModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

IndividualPersonDayPatternModelCoefficients

.\IndividualPersonDayPatternCoefficients_SACOG-v1.8.f12

The full path name for the coefficient file for this model

ShouldRunIndividualPersonDayPatternModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceIndividualPersonDayPatternModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

PersonExactNumberOfToursModelCoefficients

.\PersonExactNumberOfToursCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunPersonExactNumberOfToursModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTracePersonExactNumberOfToursModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

WorkTourDestinationModelSampleSize

25

The maximum number of destinations to be sampled for this model

WorkTourDestinationModelCoefficients

.\WorkTourDestinationCoefficients_SACOG-v1.8.F12

The full path name for the coefficient file for this model

ShouldRunWorkTourDestinationModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceWorkTourDestinationModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

OtherTourDestinationModelSampleSize

25

The maximum number of destinations to be sampled for this model

OtherTourDestinationModelCoefficients

.\OtherTourDestinationCoefficients_SACOG-v1.8.F12

The full path name for the coefficient file for this model

ShouldRunOtherTourDestinationModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceOtherTourDestinationModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

WorkBasedSubtourGenerationModelCoefficients

.\WorkbasedSubtourGenerationCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunWorkBasedSubtourGenerationModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceWorkBasedSubtourGenerationModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

WorkTourModeModelCoefficients

.\WorkTourModeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunWorkTourModeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceWorkTourModeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

SchoolTourModeModelCoefficients

.\SchoolTourModeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunSchoolTourModeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceSchoolTourModeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

WorkBasedSubtourModeModelCoefficients

.\WorkBasedSubtourModeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunWorkBasedSubtourModeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceWorkBasedSubtourModeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

EscortTourModeModelCoefficients

.\EscortTourModeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunEscortTourModeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceEscortTourModeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

OtherHomeBasedTourModeModelCoefficients

.\OtherHomeBasedTourModeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunOtherHomeBasedTourModeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceOtherHomeBasedTourModeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

WorkTourTimeModelCoefficients

.\WorkTourTimeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunWorkTourTimeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceWorkTourTimeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

SchoolTourTimeModelCoefficients

.\SchoolTourTimeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunSchoolTourTimeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceSchoolTourTimeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

OtherHomeBasedTourTimeModelCoefficients

.\OtherHomeBasedTourTimeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunOtherHomeBasedTourTimeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceOtherHomeBasedTourTimeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

WorkBasedSubtourTimeModelCoefficients

.\WorkbasedSubtourTimeCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunWorkBasedSubtourTimeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceWorkBasedSubtourTimeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

IntermediateStopGenerationModelCoefficients

.\IntermediateStopGenerationCoefficients_SACOG-v1.5.F12

The full path name for the coefficient file for this model

ShouldRunIntermediateStopGenerationModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceIntermediateStopGenerationModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

IntermediateStopLocationModelSampleSize

50

The maximum number of destinations to be sampled for this model

IntermediateStopLocationModelCoefficients

.\IntermediateStopLocationCoefficients_SACOG-v1.8.F12

The full path name for the coefficient file for this model

ShouldRunIntermediateStopLocationModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceIntermediateStopLocationModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

TripModeModelCoefficients

.\TripModeCoefficients_SACOG-v1.5.f12

The full path name for the coefficient file for this model

ShouldRunTripModeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceTripModeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

TripTimeModelCoefficients

.\TripTimeCoefficients_SACOG-v1.5.f12

The full path name for the coefficient file for this model

ShouldRunTripTimeModel

TRUE

A toggle switch to run this model (can be used for partial runs, TRUE can be overridden by more general switches above)

ShouldTraceTripTimeModel

FALSE

TRUE to trace the calculations for this model (if ShouldRunTrace is also TRUE)

UseShortDistanceCircuityMeasures

FALSE

TRUE to read in and use parcel-specific circuity factors in the short distance blending calculations

HouseholdSamplingRateOneInX

1

The denominator of the fraction of households in the input sample to be simulated (e.g. 100 is for 1 / 100)

HouseholdSamplingStartWithY

1

The household number to simulate first (e.g. 2, in combination with 100 above would simulate HH 2, 102, 202, etc.)

ShouldUseShadowPricing

TRUE

TRUE to apply shadow pricing for the WorkLocation and SchoolLocation models

UsualWorkMicrozoneThreshold

5

Parcel-specific threshold used in the shadow price calculations

UsualSchoolMicrozoneThreshold

5

Parcel-specific threshold used in the shadow price calculations

UsualUniversityMicrozoneThreshold

5

Parcel-specific threshold used in the shadow price calculations

NumberOfMicrozonesInReportDiffs

10

Control for printing out reporting on shadow price calculations

UsualWorkPercentTolerance

0

Percentage tolerance to trigger work parcel shadow price adjustment

UsualWorkAbsoluteTolerance

0

Absolute tolerance to trigger work parcel shadow price adjustment

UsualSchoolPercentTolerance

0

Percentage tolerance to trigger school parcel shadow price adjustment

UsualSchoolAbsoluteTolerance

0

Absolute tolerance to trigger school parcel shadow price adjustment

UsualUniversityPercentTolerance

0

Percentage tolerance to trigger university parcel shadow price adjustment

UsualUniversityAbsoluteTolerance

0

Absolute tolerance to trigger university parcel shadow price adjustment

ShadowPriceDelimiter

9

The delimiter for the shadow price files (9=TAB, 32=space, 44=comma)

NBatches

16

NProcessors

4

Number of processors to be used

ShouldUseParkAndRideShadowPricing

TRUE

If, True park and ride shadow pricing would be used in the model

ParkAndRideShadowPriceDelimiter

9

The delimiter for the park and ride shadow pricing file (9=TAB, 32=space, 44=comma)

ParkAndRideShadowPriceMaximumPenalty

-20

ParkAndRideShadowPriceTimeSpread

5

Seed Shadow Price

The see shadow price file is created by running the long-term models (work and school location choice) in DaySim ten times while continuously updating the shadow prices during each iteration. It needs to be only run once per scenario by checking “Update Shadow Price” checkbox. This runs the “ShadowPrice” application within “DaySim” application. Each time DaySim long term models are run, a shadow price file “shadow_prices.txt” is created in the working directory \Master\{SCENARIO_DIR}\Output\DaySim\working. At the end of ten iterations, the shadow price file is copied from the working directory to \Master\{SCENARIO_DIR}\Input\DaySimInput\09_SeedShadow\shadow_prices.txt. At beginning of each run this file is copied back to the working directory so that DaySim could use it while simulating work and school parcel location choices.

DaySim Outputs

The person, tour and trip level output files contain all of the variables predicted by DaySim, plus ID variables to cross-reference each other and the input data files in order to append more information if necessary. These output files are under the scenario directory \Master\{SCENARIO_DIR}\Output\DaySim.

Household and Household Day Files

The DaySim household and household day output files append the model predicted information into the household input files. Household output file is \Master\{SCENARIO_DIR}\Output\DaySim\_household.tsv, in the exact same format as the input file in Table 4‑18.

The household day output file is at \Master\{SCENARIO_DIR}\Output\DaySim \household_day.tsv.

TABLE 4-25 HOUSEHOLD DAY FILE

FIELD

DESCRIPTION

ID

internal DaySim record ID

HHNO

Household id

DAY

Diary / simulation day ID

DOW

Day of week

JTTOURS

HH fully joint tours in day

PHTOURS

HH partially joint half tours

FHTOURS

HH fully joint half tours

HDEXPFAC

HH day expansion factor

Person and Person Day Files

The person output file is \Master\{SCENARIO_DIR}\Output\DaySim\_person.tsv; in the exact same format as the input file in Table 4‑19.

The person-day output file has the person-day-level variables from a previous run. It is \Master\{SCENARIO_DIR}\Output\DaySim\_person_day.tsv.

TABLE 4-26 PERSON DAY FILE FORMAT

FIELD

DESCRIPTION

ID

internal DaySim record ID

PERSON_ID

internal DaySim record ID

HOUSEHOLD_DAY_ID

internal DaySim record ID

HHNO

Household id

PNO

person sequential number on file

DAY

Diary / simulation day ID

BEGHOM

Dairy day begins at home?

ENDHOM

Dairy day ends at home?

HBTOURS

home based tours in day

WBTOURS

work based tours in day

UWTOURS

tours to usual workplace in day

WKTOURS

work tours

SCTOURS

school tours

ESTOURS

escort tours

PBTOURS

personal business Tours

SHTOURS

shopping tours

MLTOURS

meal tours

SOTOURS

social tours

RETOURS

recreation tours

METOURS

medical tours

WKSTOPS

work stops in day

SCSTOPS

school stops in day

ESSTOPS

escort stops in day

PBSTOPS

personal bus stops in day

SHSTOPS

shopping stops in day

MLSTOPS

meal stops in day

SOSTOPS

social stops in day

RESTOPS

recreation stops in day

MESTOPS

medical stops in day

WKATHOME

Minutes worked at home in day

PDEXPFAC

Person-day expansion factor

Tour File

This file has tour-level variables based by all persons predicted by a previous DaySim run. It is \Master\{SCENARIO_DIR}\Output\DaySim\_tour.tsv. The following table summarizes the contents of this file.

TABLE 4-27 TOUR FILE

FIELD

DESCRIPTION

ID

internal DaySim record ID

PERSON_ID

internal DaySim record ID

PERSON_DAY_ID

internal DaySim record ID

HHNO

Household ID

PNO

person sequential number on file

DAY

Diary / simulation day ID

TOUR

tour ID

JTINDEX

household joint tour index

PARENT

parent tour ID

SUBTRS

number of sub-tours

PDPURP

primary destination purpose

TLVORIG

time leave tour origin

TARDEST

time arrive tour destination

TLVDEST

time leave tour destination

TARORIG

time arrive tour origin

TOADTYP

tour origin address type

TDADTYP

tour destination address type

TOPCL

tour origin parcel

TOTAZ

tour origin TAZ

TDPCL

tour destination parcel

TDTAZ

tour destination TAZ

TMODETP

tour main mode type

TPATHTP

tour main mode path type

TAUTOTIME

tour 1-way auto time

TAUTOCOST

tour 1-way auto distance

TAUTODIST

tour 1-way auto cost

TRIPSH1

1st half tour number of trips

TRIPSH2

2nd half tour number of trips

PHTINDX1

1st half-partial joint half tour index

PHTINDX2

2nd half-partial joint half tour index

FHTINDX1

1s half- fully joint half tour index

FHTINDX2

2nd half- fully joint half tour index

TOEXPFAC

trip expansion factor

Trip File

This file has trip-level variables for all trips predicted from a previous DaySim run. It is \Master\{SCENARIO_DIR}\Output\DaySim\_trip.tsv.

TABLE 4-28 DAYSIM OUTPUT TRIP FILE

FIELD

DESCRIPTION

ID

internal DaySim record ID

TOUR_ID

internal DaySim record ID

HHNO

household ID

PNO

person sequence number on file

DAY

diary / simulation day ID

TOUR

tour ID

HALF

tour half

TSEG

trip segment number within half tour

TSVID

original survey trip ID number

OPURP

trip origin purpose

DPURP

trip destination purpose

OADTYP

trip origin address type

DADTYP

trip destination address type

OPCL

trip origin parcel

OTAZ

trip origin zone

DPCL

trip destination parcel

DTAZ

trip destination zone

MODE

trip mode

PATHTYPE

transit sub-mode

DORP

trip driver or passenger

DEPTM

trip departure time (min after 3 am)

ARRTM

trip arrival time (min after 3 am)

ENDACTTM

trip destination activity end time

TRAVTIME

network travel time, min (by SOV)

TRAVCOST

network travel time, min (by SOV)

TRAVDIST

network travel distance, miles (by SOV)

VOT

trip value of time (cents/minute)

TREXPFAC

trip expansion factor