3.4 Land Use Data Prep - Revision history

Bstabler: Updated to NERPMAB2

2020-11-09T13:47:10Z

Updated to NERPMAB2

Bstabler at 18:29, 27 August 2020

2020-08-27T18:29:52Z

Bstabler at 18:24, 27 August 2020

2020-08-27T18:24:06Z

Bstabler at 21:22, 26 August 2020

2020-08-26T21:22:03Z

Bstabler at 20:58, 26 August 2020

2020-08-26T20:58:18Z

Bstabler at 20:57, 26 August 2020

2020-08-26T20:57:31Z

Bstabler at 20:46, 26 August 2020

2020-08-26T20:46:35Z

Bstabler at 20:35, 26 August 2020

2020-08-26T20:35:04Z

Gwineman at 20:55, 17 October 2016

2016-10-17T20:55:33Z

Gwineman at 20:52, 17 October 2016

2016-10-17T20:52:00Z

@@ Line 84: / Line 84: @@
 For distance decay buffering, the user specifies three parameters for each buffer: (1) the distance parameter, (2) the offset parameter, and (3) the slope parameter (the latter two are used only for logistic buffering). The parameters and equation for the logistic curves used for DaySim model estimation and calibration are listed below. It is necessary that these same parameters be used for model application.
-−
 Parameter                 Buffer 1                       Buffer 2
 Inflection                     BDIST1 = 660 (ft)         BDIST2 = 1320 (ft)
@@ Line 90: / Line 90: @@
 Slope                          DECAY1 = 0.76            DECAY2 = 0.76
 The equation is:
-Weight = MIN(1, (1 +  Exp(DECAY – 0.5 + BOFFS/5280))
+  Weight = MIN(1, (1 +  Exp(DECAY – 0.5 + BOFFS/5280))
    / (1 + Exp(DECAY * (Distance/BDIST – 0.5 – BOFFS/5280))))
-−
 Distance is the distance, in feet, from the origin parcel to any other parcel whose calculation is explained in the next paragraph.
@@ Line 135: / Line 135: @@
 #Run DaySim data tools (DSBuffTool.exe)
 #Copy outputs (buffered_maz_year.csv) to the model scenario input directory
-#Update PopulationSim controls (control_totals_maz.csv, control_total_taz.csv, control_totals_county.csv)
+#Update PopulationSim controls (update_controls.bat)
 #Run PopulationSim
-#Run PopSim_to_DaySim.R
+#Convert PopulationSim output to DaySim input (popsim_to_daysim.bat)
 #Copy outputs to the model scenario input directory
 #Run the model
 The above steps are illustrated in detail in the training slides June2020_Training_NERPM-AB_2.0.pdf here [[Support/Training]]

← Older revision		Revision as of 18:29, 27 August 2020
Line 40:		Line 40:

	DTASettings.ini (settings file)		DTASettings.ini (settings file)
		+
		+	settings.csv (settings file)

	'''Output''':		'''Output''':

@@ Line 25: / Line 25: @@
 DTALite, a dynamic traffic assignment software, is used to generate node-to-node shortest path distances using the all streets network. The output from this step is used by the DaySim Buffering Tool to prepare the buffered MAZ files.
-'''Tool''': ''DTALite64.exe''
+'''Tool''': ''DTALite.exe''
 '''Directory''':  \User.prg\DaySim_Data_Tools

← Older revision		Revision as of 21:22, 26 August 2020
Line 139:		Line 139:
	#Run the model		#Run the model

−	~~'''Step 1:'''~~	+	The above steps are illustrated in detail in the training slides June2020_Training_NERPM-AB_2.0.pdf here [[Support/Training]]

← Older revision		Revision as of 20:58, 26 August 2020
Line 140:		Line 140:

	'''Step 1:'''		'''Step 1:'''
−	~~[[File:Step1.jpg]]~~

← Older revision		Revision as of 20:57, 26 August 2020
Line 140:		Line 140:

	'''Step 1:'''		'''Step 1:'''
−	[[File:~~Example~~.jpg]]	+	[[File:Step1.jpg]]

← Older revision		Revision as of 20:46, 26 August 2020
Line 121:		Line 121:

	'''''It must be noted that option 2 – use interpolation with a circuity surface was used when developing the model. However, going forward it is recommended that node-to-node (option 3) method be used for calculating buffer variables.'''''		'''''It must be noted that option 2 – use interpolation with a circuity surface was used when developing the model. However, going forward it is recommended that node-to-node (option 3) method be used for calculating buffer variables.'''''
		+
		+	<h2>Updating Land-use Data</h2>
		+
		+	The user can update the land-use file manually if changes are required in specific zones because of new development, changed land-use etc. The starting point for such changes should be buffering micro-zones step. One of the inputs to the buffering tool is the MAZ file, for example, nftpo_microzones_2015.csv for the 2015 scenario. This file should be manually updated for such changes and saved with the same name. The user should then run the buffer tool and copy the output file (buffered_microzone_2015.dat) to the scenario input directory. The following example describes it step by step.
		+
		+	<h3>Adding 100 Households to an MAZ</h3>
		+
		+	To add 100 additional households to an MAZ, the user needs to run the DaySim data tools, PopulationSim, and the model
		+
		+	#Update the base microzone file (nftpo_microzones_year.csv)
		+	#Run DaySim data tools (DSBuffTool.exe)
		+	#Copy outputs (buffered_maz_year.csv) to the model scenario input directory
		+	#Update PopulationSim controls (control_totals_maz.csv, control_total_taz.csv, control_totals_county.csv)
		+	#Run PopulationSim
		+	#Run PopSim_to_DaySim.R
		+	#Copy outputs to the model scenario input directory
		+	#Run the model
		+
		+	'''Step 1:'''
		+	[[File:Example.jpg]]

@@ Line 1: / Line 1: @@
 [[Category:3.0 Model Design]]
-<h2>Parcel Allocation</h2>
+<h2>Network Data Preparation</h2>
-One of the distinguishing features of NERPM-AB is the use of parcels as the basic spatial unit for generating demand. In order to run the ABM, it is necessary to develop parcel level estimates of employment by industrial sector, households, and enrollment.  The parcel estimates are typically derived from TAZ-level information obtained from the TPO.
+This step calculates “nearby” pairs of microzones (MAZ) for shortest distance path calculations. For each MAZ, it selects all MAZs within a buffer and creates pairs of MAZs. These MAZ pairs are input to the next step where DTALite finds the shortest path between them.
-In order to facilitate the preparation of parcel information, a parcel allocation tool has been developed.  This tool requires a number of inputs such as the TAZ-level employment and household controls, the block level employment household information, school locations and enrollment by grade, and correspondences between TAZ, Census block, and parcel geographies.  Note that in addition to performing spatial allocation from TAZs to parcels, the tool is also capable of allocating employment from a more aggregate categorization of employment sectors to the nine industrial sectors required by DaySim.
+'''Tool''': ''Network_DataPrepv2.exe''
-This sector allocation is performed by first disaggregating the employment for each of the broad sectors into twenty  more detailed employment sectors using 2-digit NAICS code employment totals from the Census Bureau’s Longitudinal Employer-Household Dynamics (LEHD) data source, and then aggregating these twenty sectors back to the nine sectors used in the NERPM-AB DaySim activity-based model components.
+'''Directory''':  \User.prg\DaySim_Data_Tools
-Table 3‑1 summarizes the employment sectors used in the activity-based model and their associated 20digit NAICS codes.
+'''Inputs''':
-TABLE 3-1 DAYSIM ACTIVITY-BASED MODEL EMPLOYMENT SECTORS
+input_node.csv (Node x, y from an all-streets network)
-{|  class="wikitable"
+nftpo_MAZs_year.dat (The coordinates of the newly developed microzones)
-*STUGRD – students in kindergarten through grade 8
+nftpo_netprep.ctl (Network prep control file)
-The allocation tool uses US Department of Education National Center for Education Statistics information on the point location of schools and their associated enrollment by grade (http://nces.ed.gov/ccd/elsi/tableGenerator.aspx).  Post-secondary information can be obtained from the US Department of Education’s Integrated Postsecondary Education Data System (http://nces.ed.gov/ipeds/datacenter/).
+'''Output''':
-The allocation tool is programmed in C#, and includes some key features such as:
+input_od_pairs.csv (for input to shortest path update tool)
-*A graphical user interface (GUI) that allows users to easily reconfigure the employment sector allocation scheme
+<h2>Shortest Path Update</h2>
-Four inputs are required to run the tool:
+DTALite, a dynamic traffic assignment software, is used to generate node-to-node shortest path distances using the all streets network. The output from this step is used by the DaySim Buffering Tool to prepare the buffered MAZ files.
-*TAZ file - TAZ level totals for employment, household, and enrollment.
+'''Tool''': ''DTALite64.exe''
-The allocation tool performs the following sequential steps:
+'''Directory''':  \User.prg\DaySim_Data_Tools
-#Disaggregate block data to parcel/microzone level
+'''Inputs''':
-The process is illustrated in Figure 3‑2
+input_od_pairs.csv (from the Network Data Preparation tool)
-'''FIGURE 3-2 LAND USE ALLOCATION TOOL FLOW'''
+input_node.csv (from all-street network)
-[[File:Figure_3-2.png]]
+input_link_type.csv (from all-street network)
-'''''It must be noted that this tool was developed after NERPM-AB model was in place. Various data sources such as infoUSA were used to develop employment and enrollment data at the parcel level.'''''
+input_link.csv (from all-street network)
 <h2>Buffering & Transit Access Preparation</h2>
-In DaySim, it is important to have measures not only of within a particular parcel, but also what lies in the area immediately surrounding each parcel. These measures are created by defining a “buffer” area around each parcel and counting what lies inside the buffer. These variables can then be used in DaySim in a way similar to how zonal land use and density variables are used in TAZ-based models, with the advantage that the buffer is defined in exactly the same way for each parcel. The buffer variables that DaySim uses include:
+In DaySim, it is important to have measures not only of within a particular microzone, but also what lies in the area immediately surrounding each microzone. These measures are created by defining a “buffer” area around each microzone and counting what lies inside the buffer. These variables can then be used in DaySim in a way similar to how zonal land use and density variables are used in TAZ-based models, with the advantage that the buffer is defined in exactly the same way for each microzone. The buffer variables that DaySim uses include:
 *The number of households in the buffer;
@@ Line 96: / Line 56: @@
 *The number of street intersections in the buffer, segmented by 1-node (dead-end or cul-de-sac), 3-node (T-junction), and 4+node intersections; and
-In addition, DaySim also uses the distance from the parcel centroid to the nearest transit stop (by transit sub-mode, if relevant), as well as the distance to the nearest open space area while simulating models.
+In addition, DaySim also uses the distance from the microzone centroid to the nearest transit stop (by transit sub-mode, if relevant), as well as the distance to the nearest open space area while simulating models.
 <h3>DaySim Buffering Tool</h3>

@@ Line 81: / Line 81: @@
 '''FIGURE 3-2 LAND USE ALLOCATION TOOL FLOW'''
+[[File:Figure_3-2.png]]
 '''''It must be noted that this tool was developed after NERPM-AB model was in place. Various data sources such as infoUSA were used to develop employment and enrollment data at the parcel level.'''''
@@ Line 134: / Line 134: @@
 '''FIGURE 3-3 BUFFER1 AND BUFFER2 DISTANCE DECAY WEIGHTS'''
 The buffering program also gives the user three options as to how distances are calculated within the buffering program:

@@ Line 13: / Line 13: @@
 TABLE 3-1 DAYSIM ACTIVITY-BASED MODEL EMPLOYMENT SECTORS
-{|  class="confluenceTable"
+{|  class="wikitable"
 !  class="highlight-red confluenceTh" data-highlight-colour="red" | <strong>DAYSIM SECTOR</strong>
 !  class="highlight-red confluenceTh" data-highlight-colour="red" | <strong>2-DIGIT NAICS CODE</strong>