visummodelwiki - User contributions [en]

5.2 DaySim Input Preparation - Using Parcel Editing Tool

2017-01-31T16:56:58Z

Mlocklear:

[[Category:5.0 User Interface & Running the Model]]

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CopyGeodatabaseArchivetotheModelDirectory">
Copy Geodatabase Archive to the Model Directory</h4>

The user must have the appropriate zipped geodatabase parcel file in the
“Input_ParcelData” folder within the “NERPMAB1v2” directory. Copy the appropriate year’s
zipped geodatabase into the “Input_ParcelData” folder to run the DaySim input
generator tools successfully. The tool uses the zipped archive so there is no
need to unzip the archive.

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CubeCatalogapplication“GenerateorEditParcelFile”">
Cube Catalog application “Generate or Edit Parcel File”</h4>

The Cube Catalog application “Generate or Edit Parcel File” generates
default DaySim input files or generates an editing environment for parcel
editing based on user input. The user only needs to run this application if
they need input files for years other than 2010, 2030 or 2040 or if they need
to edit input files.

To run the new application, the user first should select a scenario from the
scenario window and then open the new application interface, which looks like
Figure 5.13.

Figure 5‑13 Generate or edit parcel file application
interface


[[File:Figure 5-13.png]]

The user needs to type in the correct path to the Python.exe file as well as
the correct version of ArcGIS. If the users selects Master and runs the new
application, Cube shows an error message like in Figure 5-14 to warn the user
that the application cannot run for this scenario




Figure 5‑14 generate or edit parcel file application
warning


[[File:Figure 5-14.png]]

After selecting a scenario and opening the new application interface, the
user should enter the model year (only 2 digits, for instance 10 for 2010 and
40 for 2040), the correct path to the python.exe, the correct version of
ArcGIS, and one of the following options:

<ol>
<li>Generate default files- Select this option if editing the
parcel file is unnecessary; if the user selects this option, the program
generates default files automatically for the selected scenario and model
year.</li>

<li>Edit parcel file- Select this option if editing the parcel
file is necessary; if the user selects this option, ArcMap will launch to make
the requisite edits for the selected scenario and model year like in Figure
5-15</li>
</ol>

If option 1, wait for the program to complete and then run the scenario
normally.

If option 2, continue to ArcMap Parcel Editingin
order to undertake parcel editing.

Figure 5-15: ArcMap Parcel Editing MXD Opened from Cube


[[File:Figure 5-15.png]]

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-ArcMapParcelEditing">
ArcMap Parcel Editing</h4>

After clicking “Run” in the Cube interface, a dialog box will appear similar
to the one in Figure 5-16 below. Click the “Install Add-in” button to install
the “DaySim Input Generator toolbar” into ArcMap. A second dialog will then
appear to confirm that the toolbar was installed successfully. Click “OK” on
this second dialog. ArcMap will then be opened for the user to make parcel
edits and develop DaySim inputs.

Figure 5-16: Install Add-In


[[File:Figure 5-16.png]]

When Cube pushes out to ArcMap the application prepares a workspace for
editing and copies data for the appropriate scenario year for editing.

Note that the Cube application added a layer to the active data frame in
ArcMap called “Edit Parcels”. Please edit the parcel in this layer.
Edit only the parcels you wish to adjust. In order to edit, please do the
following:

Use the zoom tool to identify the area you wish to edit.

This step could take 45-60 minutes depending on processing power.

Figure 5-17: Identify the
area of Interest


[[File:Figure 5-17.png]]

Start an editing session by
clicking the “Editor” drop-down and selecting “Start Editing” option as in
Figure 5-18.




Figure 5-18: Start an edit session


[[File:Figure 5-18.png]]

If the editor toolbar is not
present in your map document, navigate to Customize - Toolbars - Editor as in
Figure 5-19.

Figure 5-19: Open the Editor toolbar


[[File:Figure 5-19.png]]

After selecting the “Start Editing”
option, a warning box like in Figure 5-20 may open explaining that the spatial
reference of the layer does not match the spatial reference of the data frame.
Click “Continue” to continue the edit session.

Figure 5-20: Edit Session
Warning BOX


[[File:Figure 5-20.png]]

Use the standard Esri editing tools
to:

Merge two parcels together:

Use the editing tool to select the polygons you wish to merge then select
“Merge…” from the “Editor” dropdown like in Figure 5-21.

A box will ask you which polygons attributes you would like to keep. Select
one of the polygons and click “OK”. Be sure to update the demographic data once
the merge is complete.

Figure 5-21: Polygon Merge
tool


[[File:Figure 5-21.png]]

Figure 5-22: Polygon
Attribute Merge


[[File:Figure 5-22.png]]

Split a parcel into component parts:

Use the editing tool to select the polygons you wish to split.

Use the “Cut Polygons” tool to split a parcel into two parts as in Figure
5-23.

Be sure to update the demographic data once the split is complete.




Figure 5-23: Using the Cut
Polygon tool to Split a polygon


[[File:Figure 5-23.png]]

Adjust parcel attributes:

Use the editing tool to select the polygon for which you wish to adjust
attributes.

Click the “Attributes” button in the “Editor” Toolbar [[File:attributes_icon.png]] to edit the parcel attributes.

Type in the desired attribute adjustment as in Figure 5-24.

Figure 5-24: Adjusting
parcel attributes in the attribute table


[[File:Figure 5-24.png]]

Once you are finished with your editing session click “Stop Editing” in the
“Editor” dropdown menu.

Click “Yes” to the Save Edits option

Complete the editing process by using the “DaySim Input Generator toolbar”.
If the DaySim Input Generator toolbar is not present in your map document, use
the following directions:

Navigate to Customize - Add-In Manager - Customize

Click the checkbox next to the “DaySim Input Generator Toolbar” that was
added to the list of Toolbars like in Figure 5-25 then click “Close” to return
to your active dataframe. Your display should look like Figure 5-26.

Figure 5-25: Customize
Active Toolbars


[[File:Figure 5-25.png]]




Figure 5-26: ArcMap with
DaySim Input Generator Toolbar


[[File:Figure 5-26.png]]

In the DaySim Input Generator toolbar, click on the “Parcel Edits Layer:”
dropdown menu to pick the appropriate “Edit Parcels” layer.

Click the DaySim Input Generator Addin button [[File:addin_icon.png]] and the appropriate DaySim inputs are generated and populate the active
scenario’s DaySimInput folder. This process takes several minutes.

A dialog box informs the user of the tool’s completion. Click OK when
prompted by the tool’s finishing.

After the successful toolbar run, close ArcMap. You can save the changes to
the map document (.mxd) if desired.

Back in Cube click on the “OK” button to finish the application run. Then,
the edited parcel files and updated DaySim input files are ready to run by the
main model. To use the new files, make sure to update the following scenario
inputs to refer to the new files:

DaySim parcels

DaySim HH File

DaySim Person File

Employment

7.2 Version NERPMAB1v3

2017-01-31T16:46:24Z

Mlocklear: Created blank page

Chapter: 7.0 Version Updates

2017-01-31T16:45:13Z

Mlocklear:

*[[7.1 Version NERPMAB1v2]]
*[[7.2 Version NERPMAB1v3]]

5.2 DaySim Input Preparation - Using Parcel Editing Tool

2017-01-31T16:41:57Z

Mlocklear:

[[Category:5.0 User Interface & Running the Model]]

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CopyGeodatabaseArchivetotheModelDirectory">
Copy Geodatabase Archive to the Model Directory</h4>

The user must have the appropriate zipped geodatabase parcel file in the
“Input_ParcelData” folder within the “NERPMAB1v2” directory. Copy the appropriate year’s
zipped geodatabase into the “Input_ParcelData” folder to run the DaySim input
generator tools successfully. The tool uses the zipped archive so there is no
need to unzip the archive.

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CubeCatalogapplication“GenerateorEditParcelFile”">
Cube Catalog application “Generate or Edit Parcel File”</h4>

The Cube Catalog application “Generate or Edit Parcel File” generates
default DaySim input files or generates an editing environment for parcel
editing based on user input. The user only needs to run this application if
they need input files for years other than 2010, 2030 or 2040 or if they need
to edit input files.

To run the new application, the user first should select a scenario from the
scenario window and then open the new application interface, which looks like
Figure 5.13.

Figure 5‑13 Generate or edit parcel file application
interface


[[File:Figure 5-13.png]]

The user needs to type in the correct path to the Python.exe file as well as
the correct version of ArcGIS. If the users selects Master and runs the new
application, Cube shows an error message like in Figure 5-14 to warn the user
that the application cannot run for this scenario




Figure 5‑14 generate or edit parcel file application
warning


[[File:Figure 5-14.png]]

After selecting a scenario and opening the new application interface, the
user should enter the model year (only 2 digits, for instance 10 for 2010 and
40 for 2040), the correct path to the python.exe, the correct version of
ArcGIS, and one of the following options:

<ol>
<li>Generate default files- Select this option if editing the
parcel file is unnecessary; if the user selects this option, the program
generates default files automatically for the selected scenario and model
year.</li>

<li>Edit parcel file- Select this option if editing the parcel
file is necessary; if the user selects this option, ArcMap will launch to make
the requisite edits for the selected scenario and model year like in Figure
5-15</li>
</ol>

If option 1, wait for the program to complete and then run the scenario
normally.

If option 2, continue to ArcMap Parcel Editingin
order to undertake parcel editing.

Figure 5-15: ArcMap Parcel Editing MXD Opened from Cube


[[File:Figure 5-15.png]]

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-ArcMapParcelEditing">
ArcMap Parcel Editing</h4>

After clicking “Run” in the Cube interface, a dialog box will appear similar
to the one in Figure 5-16 below. Click the “Install Add-in” button to install
the “DaySim Input Generator toolbar” into ArcMap. A second dialog will then
appear to confirm that the toolbar was installed successfully. Click “OK” on
this second dialog. ArcMap will then be opened for the user to make parcel
edits and develop DaySim inputs.

Figure 5-16: Install Add-In


[[File:Figure 5-16.png]]

When Cube pushes out to ArcMap the application prepares a workspace for
editing and copies data for the appropriate scenario year for editing.

Note that the Cube application added a layer to the active data frame in
ArcMap called “Edit Parcels”. Please edit the parcel in this layer.
Edit only the parcels you wish to adjust. In order to edit, please do the
following:

Use the zoom tool to identify the area you wish to edit.

Figure 5-17: Identify the
area of Interest


[[File:Figure 5-17.png]]

Start an editing session by
clicking the “Editor” drop-down and selecting “Start Editing” option as in
Figure 5-18.




Figure 5-18: Start an edit session


[[File:Figure 5-18.png]]

If the editor toolbar is not
present in your map document, navigate to Customize - Toolbars - Editor as in
Figure 5-19.

Figure 5-19: Open the Editor toolbar


[[File:Figure 5-19.png]]

After selecting the “Start Editing”
option, a warning box like in Figure 5-20 may open explaining that the spatial
reference of the layer does not match the spatial reference of the data frame.
Click “Continue” to continue the edit session.

Figure 5-20: Edit Session
Warning BOX


[[File:Figure 5-20.png]]

Use the standard Esri editing tools
to:

Merge two parcels together:

Use the editing tool to select the polygons you wish to merge then select
“Merge…” from the “Editor” dropdown like in Figure 5-21.

A box will ask you which polygons attributes you would like to keep. Select
one of the polygons and click “OK”. Be sure to update the demographic data once
the merge is complete.

Figure 5-21: Polygon Merge
tool


[[File:Figure 5-21.png]]

Figure 5-22: Polygon
Attribute Merge


[[File:Figure 5-22.png]]

Split a parcel into component parts:

Use the editing tool to select the polygons you wish to split.

Use the “Cut Polygons” tool to split a parcel into two parts as in Figure
5-23.

Be sure to update the demographic data once the split is complete.




Figure 5-23: Using the Cut
Polygon tool to Split a polygon


[[File:Figure 5-23.png]]

Adjust parcel attributes:

Use the editing tool to select the polygon for which you wish to adjust
attributes.

Click the “Attributes” button in the “Editor” Toolbar [[File:attributes_icon.png]] to edit the parcel attributes.

Type in the desired attribute adjustment as in Figure 5-24.

Figure 5-24: Adjusting
parcel attributes in the attribute table


[[File:Figure 5-24.png]]

Once you are finished with your editing session click “Stop Editing” in the
“Editor” dropdown menu.

Click “Yes” to the Save Edits option

Complete the editing process by using the “DaySim Input Generator toolbar”.
If the DaySim Input Generator toolbar is not present in your map document, use
the following directions:

Navigate to Customize - Add-In Manager - Customize

Click the checkbox next to the “DaySim Input Generator Toolbar” that was
added to the list of Toolbars like in Figure 5-25 then click “Close” to return
to your active dataframe. Your display should look like Figure 5-26.

Figure 5-25: Customize
Active Toolbars


[[File:Figure 5-25.png]]




Figure 5-26: ArcMap with
DaySim Input Generator Toolbar


[[File:Figure 5-26.png]]

In the DaySim Input Generator toolbar, click on the “Parcel Edits Layer:”
dropdown menu to pick the appropriate “Edit Parcels” layer.

Click the DaySim Input Generator Addin button [[File:addin_icon.png]] and the appropriate DaySim inputs are generated and populate the active
scenario’s DaySimInput folder. This process takes several minutes.

A dialog box informs the user of the tool’s completion. Click OK when
prompted by the tool’s finishing.

After the successful toolbar run, close ArcMap. You can save the changes to
the map document (.mxd) if desired.

Back in Cube click on the “OK” button to finish the application run. Then,
the edited parcel files and updated DaySim input files are ready to run by the
main model. To use the new files, make sure to update the following scenario
inputs to refer to the new files:

DaySim parcels

DaySim HH File

DaySim Person File

Employment

5.2 DaySim Input Preparation - Using Parcel Editing Tool

2017-01-31T16:38:42Z

Mlocklear:

[[Category:5.0 User Interface & Running the Model]]

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CopyGeodatabaseArchivetotheModelDirectory">
Copy Geodatabase Archive to the Model Directory</h4>

The user must have the appropriate zipped geodatabase parcel file in the
“Input_ParcelData” folder within the “NERPMAB1v2” directory. Copy the appropriate year’s
zipped geodatabase into the “Input_ParcelData” folder to run the DaySim input
generator tools successfully. The tool uses the zipped archive so there is no
need to unzip the archive.

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CubeCatalogapplication“GenerateorEditParcelFile”">
Cube Catalog application “Generate or Edit Parcel File”</h4>

The Cube Catalog application “Generate or Edit Parcel File” generates
default DaySim input files or generates an editing environment for parcel
editing based on user input. The user only needs to run this application if
they need input files for years other than 2010, 2030 or 2040 or if they need
to edit input files.

To run the new application, the user first should select a scenario from the
scenario window and then open the new application interface, which looks like
Figure 5.13.

Figure 5‑13 Generate or edit parcel file application
interface


[[File:Figure 5-13.png]]

The user needs to type in the correct path to the Python.exe file as well as
the correct version of ArcGIS. If the users selects Master and runs the new
application, Cube shows an error message like in Figure 5-14 to warn the user
that the application cannot run for this scenario




Figure 5‑14 generate or edit parcel file application
warning


[[File:Figure 5-14.png]]

After selecting a scenario and opening the new application interface, the
user should enter the model year (only 2 digits, for instance 10 for 2010 and
40 for 2040), the correct path to the python.exe, the correct version of
ArcGIS, and one of the following options:

<ol>
<li>Generate default files- Select this option if editing the
parcel file is unnecessary; if the user selects this option, the program
generates default files automatically for the selected scenario and model
year.</li>

<li>Edit parcel file- Select this option if editing the parcel
file is necessary; if the user selects this option, ArcMap will launch to make
the requisite edits for the selected scenario and model year like in Figure
5-15</li>
</ol>

If option 1, wait for the program to complete and then run the scenario
normally.

If option 2, continue to ArcMap Parcel Editingin
order to undertake parcel editing.

Figure 5-15: ArcMap Parcel Editing MXD Opened from Cube


[[File:Figure 5-15.png]]

<h4 id=
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-ArcMapParcelEditing">
ArcMap Parcel Editing</h4>

After clicking “Run” in the Cube interface, a dialog box will appear similar
to the one in Figure 5-16 below. Click the “Install Add-in” button to install
the “DaySim Input Generator toolbar” into ArcMap. A second dialog will then
appear to confirm that the toolbar was installed successfully. Click “OK” on
this second dialog. ArcMap will then be opened for the user to make parcel
edits and develop DaySim inputs.

Figure 5-16: Install Add-In


[[File:Figure 5-16.png]]

When Cube pushes out to ArcMap the application prepares a workspace for
editing and copies data for the appropriate scenario year for editing.

Note that the Cube application added a layer to the active data frame in
ArcMap called “Edit Parcels”. Please edit the parcel polygons in this layer.
Edit only the parcels you wish to adjust. In order to edit, please do the
following:

Use the zoom tool to identify the area you wish to edit.

Figure 5-17: Identify the
area of Interest


[[File:Figure 5-17.png]]

Start an editing session by
clicking the “Editor” drop-down and selecting “Start Editing” option as in
Figure 5-18.




Figure 5-18: Start an edit session


[[File:Figure 5-18.png]]

If the editor toolbar is not
present in your map document, navigate to Customize - Toolbars - Editor as in
Figure 5-19.

Figure 5-19: Open the Editor toolbar


[[File:Figure 5-19.png]]

After selecting the “Start Editing”
option, a warning box like in Figure 5-20 may open explaining that the spatial
reference of the layer does not match the spatial reference of the data frame.
Click “Continue” to continue the edit session.

Figure 5-20: Edit Session
Warning BOX


[[File:Figure 5-20.png]]

Use the standard Esri editing tools
to:

Merge two parcels together:

Use the editing tool to select the polygons you wish to merge then select
“Merge…” from the “Editor” dropdown like in Figure 5-21.

A box will ask you which polygons attributes you would like to keep. Select
one of the polygons and click “OK”. Be sure to update the demographic data once
the merge is complete.

Figure 5-21: Polygon Merge
tool


[[File:Figure 5-21.png]]

Figure 5-22: Polygon
Attribute Merge


[[File:Figure 5-22.png]]

Split a parcel into component parts:

Use the editing tool to select the polygons you wish to split.

Use the “Cut Polygons” tool to split a parcel into two parts as in Figure
5-23.

Be sure to update the demographic data once the split is complete.




Figure 5-23: Using the Cut
Polygon tool to Split a polygon


[[File:Figure 5-23.png]]

Adjust parcel attributes:

Use the editing tool to select the polygon for which you wish to adjust
attributes.

Click the “Attributes” button in the “Editor” Toolbar [[File:attributes_icon.png]] to edit the parcel attributes.

Type in the desired attribute adjustment as in Figure 5-24.

Figure 5-24: Adjusting
parcel attributes in the attribute table


[[File:Figure 5-24.png]]

Once you are finished with your editing session click “Stop Editing” in the
“Editor” dropdown menu.

Click “Yes” to the Save Edits option

Complete the editing process by using the “DaySim Input Generator toolbar”.
If the DaySim Input Generator toolbar is not present in your map document, use
the following directions:

Navigate to Customize - Add-In Manager - Customize

Click the checkbox next to the “DaySim Input Generator Toolbar” that was
added to the list of Toolbars like in Figure 5-25 then click “Close” to return
to your active dataframe. Your display should look like Figure 5-26.

Figure 5-25: Customize
Active Toolbars


[[File:Figure 5-25.png]]




Figure 5-26: ArcMap with
DaySim Input Generator Toolbar


[[File:Figure 5-26.png]]

In the DaySim Input Generator toolbar, click on the “Parcel Edits Layer:”
dropdown menu to pick the appropriate “Edit Parcels” layer.

Click the DaySim Input Generator Addin button [[File:addin_icon.png]] and the appropriate DaySim inputs are generated and populate the active
scenario’s DaySimInput folder. This process takes several minutes.

A dialog box informs the user of the tool’s completion. Click OK when
prompted by the tool’s finishing.

After the successful toolbar run, close ArcMap. You can save the changes to
the map document (.mxd) if desired.

Back in Cube click on the “OK” button to finish the application run. Then,
the edited parcel files and updated DaySim input files are ready to run by the
main model. To use the new files, make sure to update the following scenario
inputs to refer to the new files:

DaySim parcels

DaySim HH File

DaySim Person File

Employment

1.2 Model Sensitivities

2017-01-31T16:31:39Z

Mlocklear:

[[Category:1.0 Overview]]

'''Transportation Investments & Policies
'''
NERPM-AB system is designed to be sensitive to a wide variety of transportation investments and policies. The model system incorporates representations of roadway and transit networks that can be easily configured to represent changes in network capacity or service provision. Detailed pathtype alternatives such as roadway toll and no-toll paths and transit submodes are explicitly represented in the model system. In addition, the model incorporates distributed values-of-time across the population, dependent of travel purpose, income and other factors, providing a more realistic representation of travelers’ willingness-to-pay. The model system’s explicit representation of each individual’s entire daily activity pattern also provides the opportunity to better represent the impacts of travel demand management scenarios.

It should be pointed out that in the NERPM-AB, the tolling capabilities are not activated. Therefore, there currently is no additional cost associated with the use of the managed lanes nor with any of the planned toll facilities. As additional data and funding sources become available, a tolling mechanism will be developed that is sensitive to the characteristics of the travel behavior in northeast Florida.

'''Land Use'''

One of the distinguishing features of the NERPM-AB is the use of parcels as the basic spatial unit for generating travel demand. Use of this fine-grained geography, in conjunction with “all streets” based network impedances, provides the model with an enhanced ability to represent detailed urban form and land use characteristics that are particularly important when considering non-motorized travel such as walking and bicycling. In addition, the model predicts demand for seven different activity types using detailed land use information such employment by nine industrial sectors and enrollment by school type.

'''Socioeconomics & Demographics'''

NERPM-AB uses a “synthetic population” to predict individual and household level travel choices. The synthetic population is comprised of lists of households and persons that are based on observed or forecasted distributions of socioeconomic attributes and are typically created by sampling detailed Census microdata. These lists function as the basis for all subsequent choice making simulated in the activity-based model. Use of a disaggregate representation of the population reduces aggregation bias in the model system, and allows the model to more realistically incorporate the influence of socioeconomic and demographic information on individual and household travel choices.

Frequently Asked Questions

2017-01-31T16:26:43Z

Mlocklear:

'''Are there restrictions associated with the naming conventions?'''

Yes, avoid blank spaces in file name paths. Although hyphens will work, using underscores is a better way to create clarity in the naming conventions.

Will work:

WorkingDirectory="D:\FSUTMS\NERPM_AB1\Master\Base2010\Output\DaySim\working"

Will NOT work:

WorkingDirectory="D:\FSUTMS\NERPM AB-1\Master\Base2010\Output\DaySim\working"

'''What programs do I need to run PopGen?'''

We did not provide PopGen with the modeling package that has been made available through the FSUTMS portal because the user does not need to run PopGen. PopGen is not part of the distribution, and we do not recommend that the end users attempt to use it to produce new synthetic populations. It should only be run by RSG, NFTPO and D2 staff to produce baseline populations.

PyQt is a Python GUI library, which is used to create PopGen’s user interface. The version of PyQt to which the questioner refers to is an older version that is probably no longer supported. It may be possible to download and install a more recent version of the library, but we cannot guarantee that it would be backward compatible. In addition, it would be possible to run PopGen without a GUI, but that requires some reprogramming to break the dependencies on the UI and to run the program from command line inputs.

The current, active curator of PopGen is Prof. Karthik Konduri at the University of Connecticut (kkonduri@engr.uconn.edu).

All DaySim future year parcel and synthetic household and person files, covering the years 2011 through 2039, have been created and are available to the user. They are created in the form of Geodatabases which are part of the NERPMAB1v2 download. The Geodatabase files are located in the Input_ParcelData folder. The years 2010, 2030 and 2040 DaySim input files are included in the current version of NERPMAB1v2. Please refer to the section “Editing Tool” in the NERPMAB1v2 documentation or to the video link in the "Support" section for guidance on converting the Geodatabase files into the correct format for use by the DaySim program. These two sections also provide the user with directions on how to change the socioeconomic data files.

'''Does the NERPMAB1v2 run in Cube 6.4.1?'''

No, currently the NERPMAB1v2 is not compatible with Cube 6.4.1. Model runs are being made to analyze the issues. When resolved, we will update the answer to this question.

'''Can the data (_jax_hrec2040.dat) be summarized into SFDU and MFDU?'''

No, DaySim does not use dwelling units. Instead it uses households and "focusses" on the characteristics of the household; not the dwelling unit.

'''What future enhancements are planned for the model?'''

#Update of truck data
#Tolling for managed lanes
#Data collection-In FY 2016/17 and FY 2017/18 household travel data and origin-destination data for update of the model for the 2045 Long Range Transportation Plan which is due in Fall of 2019. This data will improve validation/calibration and estimation of EE, EI and IE trips.

'''What should I do if I find an incorrectly coded link and/or links with zero volumes?'''

Please report incorrect coding for correction in a subsequent model release. If you are doing a sub-area study and have links with zero volumes it may indicate a coding error, the need for a new centroid connector… Please let us know how you resolved the problem.

'''When setting up the new NERPMAB1v2 model is a full installation of ArcGIS is required?'''

Yes, you will need the full ArcGIS 10.2 or higher to run the land use and parcel editing tool. Please install ArcGIS 10.2 or higher and reinstall CUBE without ArcGIS.

'''ArcGIS Desktop software has 3 levels of licensing. Basic, Standard and Advanced. Which level of licensing is required for NERPMABMv2?'''

You need ArcGIS 10.2 or higher with basic or standard licenses but not Advanced.

'''The property appraiser updates the parcel data annually. How is the user supposed to keep the parcel data in the model current? Will the department provide annual releases of the parcel data corrected to the population and employment?'''

Property appraiser information is updated annually. However, the ownership is typically updated, and not the parcel boundary. The ABM allows for any year to be analyzed and the end user should verify the parcel boundary with the Property Appraiser (website) to ensure no boundary changes have not occurred. If no changes have occurred, then input the new land uses or trips. For future year analyses, the most current Parcel layer is not needed. Consult with the agency you are working with. The data sets are updated every five years in development of the long range transportation plan. We do not have the resources to update them annually

'''When you add a new development, in your example you are only adding development to one parcel. Won’t that just add development to an existing zone and lump the data of the parcel in with all the other parcels of that zone?'''

Yes, that is what happens. If you want to know difference between the background traffic and the traffic from the development, you run a select link analysis without the development and with the development to analyze the difference. It was suggested that a new TAZ be created with just the one parcel tied to it, for this analysis. We have not verified that the results are the same with both methodologies. We will follow up on the Wiki FAQ page.
We suggest that you consult with the agency you are doing the analysis for to make sure they concur with the methodology you use.

'''I have a mixed use project with multiple TAZs and have tried to re-run the highway module to get distributions for each of the TAZs but get an error. Any suggestions to get multiple distributions for the same model scenario.'''

It was suggested that the Path File options could be used for this. You can then use the Cube analysis tools to get multiple select links from the same assignment.

'''We don't have ArcGIS so how do you change things manually?'''

The instructions to manually edit the files are included in the User’s Guide on the wiki page. Due to the interrelationship of the four DaySim files and the need to edit each file, we strongly recommend using the Parcel and Land Use editing tool.

'''When should I run the Shadow Price step?'''

The Shadow Price step should be run when changes are made to the employment and/school enrollment data.

'''How do you save the turning movements at a series of nodes?'''

Turning movements for specific nodes are saved by listing the node number in the assignment scripts (HTHWY00A.S, HTHWY00B.S, HTHWY00C.S, and HTHWY00D.S). The node numbers are hardcoded into the assignment scripts on the lines 26 and 27. In the current NERPMAB model, line 26 is ignored through the use of the semicolon. The semicolon turns the line into a comment, which is ignored by the program. Line 27 identifies the specific turns the user would like to save.

For example:
;TURNS N= 1-999999
TURNS N=39782,40555,40265,40258,40241,40568

'''Should the user want to save all the turns, then remove the semicolon from line 26 and start line 27 with the semicolon. In this example, the turning movement for the listed node numbers (39782, etc.) will be saved.'''

After modifying the assignment scripts, save the scripts and run the model to obtain the turning movements. The turning movements will be save in the *.bin files and the volumes can be displayed by selecting the “intersections” tab in Cube and opening the desired *.bin file to display the volumes.

'''Can I still use the Site Impact Tool to calculate the difference between the Build and No Build scenarios if there are differences in the highway networks?

Yes, as long as the links exist in both networks. The NERPM-AB network is a database network, so all nodes and links are the same in all networks. However, facility types that are coded with a zero, will not be carried over into the loaded networks. If you add a facility to the Build network and leave the facility type set to zero in the No Build network, the difference between the two networks cannot be calculated. One way around this, is by coding the facility type the same in both networks but setting the number of lanes to zero in the No Build network. This way there will not be any volume on the links with the zero lanes and the application will still work.