http://visummodelwiki.northfloridatpo.com/api.php?action=feedcontributions&feedformat=atom&user=Gwinemanvisummodelwiki - User contributions [en]2026-05-15T12:21:07ZUser contributionsMediaWiki 1.27.1http://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=385Frequently Asked Questions2017-05-31T19:06:17Z<p>Gwineman: </p>
<hr />
<div>'''When editing the parcel attributes (via the parcel editing tool), you can edit the number of households. Can you also/do you need to indicate if these households are single- or multi-family?'''<br />
<br />
No, the user can only edit the number of households with the editing tool. The characteristics of the households are assigned by the tool. The trip making patterns of the household are based on the characteristics of the household and the persons within the household, not by identifying the type of dwelling unit. <br />
<br />
'''Is there an attribute for hotel/motel population or number of rooms?'''<br />
<br />
The NERPM-AB does not contain a visitor’s model and the trip making patterns are associated with the residents of the area. The only way to associate trips with a hotel/motel is by adding employment associated with the use. In developing the 2040 socioeconomic data, the ITE trip rate of 0.90 commercial employees per room was used. These rates change and can vary by type of hotel. The user should determine if this rate is appropriate for new hotel/motel units added. The Shadow Price step should be run when changes are made to the employment and/school enrollment data.<br />
<br />
Note: The current version of the NERPM-AB, uses special generators to account for the number of trips associated with Jacksonville International Airport and the City of Saint Augustine. <br />
<br />
'''Are there restrictions associated with the naming conventions?'''<br />
<br />
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.<br />
<br />
Will work:<br />
<br />
WorkingDirectory="D:\FSUTMS\NERPM_AB1\Master\Base2010\Output\DaySim\working"<br />
<br />
Will NOT work:<br />
<br />
WorkingDirectory="D:\FSUTMS\NERPM AB-1\Master\Base2010\Output\DaySim\working"<br />
<br />
'''What programs do I need to run PopGen?'''<br />
<br />
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.<br />
<br />
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.<br />
<br />
The current, active curator of PopGen is Prof. Karthik Konduri at the University of Connecticut (kkonduri@engr.uconn.edu).<br />
<br />
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.<br />
<br />
'''Does the NERPMAB1v2 run in Cube 6.4.1?'''<br />
<br />
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. <br />
<br />
'''Can the data (_jax_hrec2040.dat) be summarized into SFDU and MFDU?'''<br />
<br />
No, DaySim does not use dwelling units. Instead it uses households and "focusses" on the characteristics of the household; not the dwelling unit.<br />
<br />
'''What future enhancements are planned for the model?'''<br />
<br />
#Update of truck data<br />
#Tolling for managed lanes<br />
#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.<br />
<br />
'''What should I do if I find an incorrectly coded link and/or links with zero volumes?'''<br />
<br />
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.<br />
<br />
'''When setting up the new NERPMAB1v2 model is a full installation of ArcGIS is required?'''<br />
<br />
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.<br />
<br />
'''ArcGIS Desktop software has 3 levels of licensing. Basic, Standard and Advanced. Which level of licensing is required for NERPMABMv2?'''<br />
<br />
You need ArcGIS 10.2 or higher with basic or standard licenses but not Advanced.<br />
<br />
'''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?'''<br />
<br />
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<br />
<br />
'''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?'''<br />
<br />
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.<br />
We suggest that you consult with the agency you are doing the analysis for to make sure they concur with the methodology you use.<br />
<br />
'''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.'''<br />
<br />
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.<br />
<br />
'''We don't have ArcGIS so how do you change things manually?'''<br />
<br />
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. <br />
<br />
'''When should I run the Shadow Price step?'''<br />
<br />
The Shadow Price step should be run when changes are made to the employment and/school enrollment data.<br />
<br />
'''How do you save the turning movements at a series of nodes?''' <br />
<br />
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. <br />
<br />
For example:<br />
;TURNS N= 1-999999<br />
TURNS N=39782,40555,40265,40258,40241,40568<br />
<br />
'''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.'''<br />
<br />
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.<br />
<br />
'''Can I still use the Trip Impact Tool to calculate the difference between the Build and No Build scenarios if there are differences in the highway networks?<br />
<br />
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.<br />
<br />
'''What is the ArcGIS Versions compatibility?'''<br />
<br />
The Generate of Edit Parcel File Application developed for use with the NERPM-AB model has been tested and is compatible with ArcGIS 10.2 ([http://northfloridatpo.com/images/uploads/wiki/prepare_workspace.py prepare_workspace.py]). The Generate of Edit Parcel File Application might not be compatible with the newer versions of ArcGIS. However, recently the tool was tested with ArcGIS 10.4, and with the following changes in the code, the tool will be compatible with the latest version.<br />
<br />
New code statements:<br />
<br />
import csv<br />
with open(output_parcels_csv,'wb') as f:<br />
w=csv.writer(f)<br />
w.writerow(fieldnames)<br />
for row in arcpy.da.SearchCursor(output_parcels,field_names=fieldnames):<br />
w.writerow(row)</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=384Frequently Asked Questions2017-05-31T19:05:43Z<p>Gwineman: </p>
<hr />
<div>'''When editing the parcel attributes (via the parcel editing tool), you can edit the number of households. Can you also/do you need to indicate if these households are single- or multi-family?'''<br />
<br />
No, the user can only edit the number of households with the editing tool. The characteristics of the households are assigned by the tool. The trip making patterns of the household are based on the characteristics of the household and the persons within the household, not by identifying the type of dwelling unit. <br />
<br />
'''Is there an attribute for hotel/motel population or number of rooms?'''<br />
<br />
The NERPM-AB does not contain a visitor’s model and the trip making patterns are associated with the residents of the area. The only way to associate trips with a hotel/motel is by adding employment associated with the use. In developing the 2040 socioeconomic data, the ITE trip rate of 0.90 commercial employees per room was used. These rates change and can vary by type of hotel. The user should determine if this rate is appropriate for new hotel/motel units added. The Shadow Price step should be run when changes are made to the employment and/school enrollment data.<br />
<br />
Note: The current version of the NERPM-AB, uses special generators to account for the number of trips associated with Jacksonville International Airport and the City of Saint Augustine. <br />
<br />
'''Are there restrictions associated with the naming conventions?'''<br />
<br />
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.<br />
<br />
Will work:<br />
<br />
WorkingDirectory="D:\FSUTMS\NERPM_AB1\Master\Base2010\Output\DaySim\working"<br />
<br />
Will NOT work:<br />
<br />
WorkingDirectory="D:\FSUTMS\NERPM AB-1\Master\Base2010\Output\DaySim\working"<br />
<br />
'''What programs do I need to run PopGen?'''<br />
<br />
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.<br />
<br />
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.<br />
<br />
The current, active curator of PopGen is Prof. Karthik Konduri at the University of Connecticut (kkonduri@engr.uconn.edu).<br />
<br />
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.<br />
<br />
'''Does the NERPMAB1v2 run in Cube 6.4.1?'''<br />
<br />
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. <br />
<br />
'''Can the data (_jax_hrec2040.dat) be summarized into SFDU and MFDU?'''<br />
<br />
No, DaySim does not use dwelling units. Instead it uses households and "focusses" on the characteristics of the household; not the dwelling unit.<br />
<br />
'''What future enhancements are planned for the model?'''<br />
<br />
#Update of truck data<br />
#Tolling for managed lanes<br />
#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.<br />
<br />
'''What should I do if I find an incorrectly coded link and/or links with zero volumes?'''<br />
<br />
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.<br />
<br />
'''When setting up the new NERPMAB1v2 model is a full installation of ArcGIS is required?'''<br />
<br />
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.<br />
<br />
'''ArcGIS Desktop software has 3 levels of licensing. Basic, Standard and Advanced. Which level of licensing is required for NERPMABMv2?'''<br />
<br />
You need ArcGIS 10.2 or higher with basic or standard licenses but not Advanced.<br />
<br />
'''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?'''<br />
<br />
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<br />
<br />
'''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?'''<br />
<br />
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.<br />
We suggest that you consult with the agency you are doing the analysis for to make sure they concur with the methodology you use.<br />
<br />
'''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.'''<br />
<br />
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.<br />
<br />
'''We don't have ArcGIS so how do you change things manually?'''<br />
<br />
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. <br />
<br />
'''When should I run the Shadow Price step?'''<br />
<br />
The Shadow Price step should be run when changes are made to the employment and/school enrollment data.<br />
<br />
'''How do you save the turning movements at a series of nodes?''' <br />
<br />
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. <br />
<br />
For example:<br />
;TURNS N= 1-999999<br />
TURNS N=39782,40555,40265,40258,40241,40568<br />
<br />
'''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.'''<br />
<br />
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.<br />
<br />
'''Can I still use the Trip Impact Tool to calculate the difference between the Build and No Build scenarios if there are differences in the highway networks?<br />
<br />
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.<br />
<br />
'''What is the ArcGIS Versions compatibility?'''<br />
<br />
The Generate of Edit Parcel File Application developed for use with the NERPM-AB model has been tested and is compatible with ArcGIS 10.2 ([http://northfloridatpo.com/images/uploads/wiki/prepare_workspace.py / prepare_workspace.py]). The Generate of Edit Parcel File Application might not be compatible with the newer versions of ArcGIS. However, recently the tool was tested with ArcGIS 10.4, and with the following changes in the code, the tool will be compatible with the latest version.<br />
<br />
New code statements:<br />
<br />
import csv<br />
with open(output_parcels_csv,'wb') as f:<br />
w=csv.writer(f)<br />
w.writerow(fieldnames)<br />
for row in arcpy.da.SearchCursor(output_parcels,field_names=fieldnames):<br />
w.writerow(row)</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=381Support/Training2017-05-01T13:57:23Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]."<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf|NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 NERPMAB1v3 Webinar Video Recording]<br />
<br />
*[[Media:NERPMAB1v2_Training_June_2016.pdf|NERPMABv2 Training Slides]]<br />
*[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]<br />
*[[Media:NERPMAB1v2 Webinar Excercise Revised (2).pdf|NERPMABv2 Exercise]]<br />
<br />
If you need additional information, please contact [mailto:mlocklear@northfloridatpo.com?cc=Stephen.Lawe@rsginc.com;Ameera.Sayeed@dot.state.fl.us;Hadi.Sadrsadat@rsginc.com Milton Locklear]<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.3_DaySim_Input_Preparation_-_Running_the_Model&diff=3665.3 DaySim Input Preparation - Running the Model2017-02-14T18:58:01Z<p>Gwineman: Gwineman moved page 5.2 DaySim Input Preparation - Running the Model to 5.3 DaySim Input Preparation - Running the Model</p>
<hr />
<div>[[Category:5.0 User Interface & Running the Model]]<br />
<br />
<p class="BodyParagraph">NERPM activity based model integrates DaySim within Cube environment. The following figure shows a screenshot of the Cube interface that is used to run and maintain the model.</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.2RUNNINGTHEMODEL-FIGURE5-27NERPM-ABCUBEINTERFACE">FIGURE 5-27 NERPM-AB CUBE INTERFACE</h4><br />
<br />
[[File:Figure 5-27.png]]<br />
<br />
<p class="BodyParagraph">There are two ways of running the whole model:</p><ul><li>Select the scenario in ‘scenario manager’ and click on ‘Run’ button on the top left portion of the menu bar.</li><li>Right-click on the scenario manager and select ‘Edit/Run Scenario’ menu item. Go through all the scenario editor screens to verify inputs and click on the ‘Run’ button on the bottom right portion of the scenario editor.</li></ul><p class="BodyParagraph">The following is a list of some keys that the user may want to update:</p><ul><li>“Alternative Letter” (One digital letter such as A, B, C, etc)</li><li>“Alternative Year” (Two digial number such as 10, 15, 20, etc)</li><li>“Alternative Year Directory”, where Input and Output folders located</li><li>“ClusterNodes”, which could be equal or less than number of processors. Set this equal to number of processors to fully utilize computation power</li><li>If a scenario involved different park and ride or kiss and ride lots than base year (see \Master\{SCENARIO_DIR}\Input\DaySimInput\05_pnr\jax_p_rNodes.dat), user should create new Park and ride file and update key “ParkAndRide”</li><li>If a scenario is future scenario or involved different land use than base year, user should create new DaySim inputs and update following keys<ul><li>ParcelFile</li><li>HouseholdFile</li><li>PersonFile</li></ul></li></ul><br />
<br />
<h4 id="id-5.2RUNNINGTHEMODEL-FIGURE5-28MODELRUNINTERFACE">FIGURE 5-28 MODEL RUN INTERFACE</h4><br />
<br />
[[File:Figure 5-28.png]]<br />
<br />
<h4 id="id-5.2RUNNINGTHEMODEL-FIGURE5-29CUBESCENARIOEDITOR">FIGURE 5-29 CUBE SCENARIO EDITOR</h4><br />
<br />
[[File:Figure 5-29.png]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.2_DaySim_Input_Preparation_-_Running_the_Model&diff=3675.2 DaySim Input Preparation - Running the Model2017-02-14T18:58:01Z<p>Gwineman: Gwineman moved page 5.2 DaySim Input Preparation - Running the Model to 5.3 DaySim Input Preparation - Running the Model</p>
<hr />
<div>#REDIRECT [[5.3 DaySim Input Preparation - Running the Model]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_5.0_User_Interface_%26_Running_the_Model&diff=365Chapter: 5.0 User Interface & Running the Model2017-02-14T18:57:53Z<p>Gwineman: </p>
<hr />
<div>*[[5.1 DaySim Input Preparation - Using Manual Methods]]<br />
*[[5.2 DaySim Input Preparation - Using Parcel Editing Tool]]<br />
*[[5.3 DaySim Input Preparation - Running the Model]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.2_DaySim_Input_Preparation_-_Using_Parcel_Editing_Tool&diff=3635.2 DaySim Input Preparation - Using Parcel Editing Tool2017-02-14T18:57:10Z<p>Gwineman: Gwineman moved page 5.1.2 DaySim Input Preparation - Using Parcel Editing Tool to 5.2 DaySim Input Preparation - Using Parcel Editing Tool</p>
<hr />
<div><br />
[[Category:5.0 User Interface & Running the Model]]<br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CopyGeodatabaseArchivetotheModelDirectory"><br />
Copy Geodatabase Archive to the Model Directory</h4><br />
<br />
<p>The user must have the appropriate zipped geodatabase parcel file in the<br />
“Input_ParcelData” folder within the “NERPMAB1v2” directory. Copy the appropriate year’s<br />
zipped geodatabase into the “Input_ParcelData” folder to run the DaySim input<br />
generator tools successfully. The tool uses the zipped archive so there is no<br />
need to unzip the archive.</p><br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CubeCatalogapplication“GenerateorEditParcelFile”"><br />
Cube Catalog application “Generate or Edit Parcel File”</h4><br />
<br />
<p>The Cube Catalog application “Generate or Edit Parcel File” generates<br />
default DaySim input files or generates an editing environment for parcel<br />
editing based on user input. The user only needs to run this application if<br />
they need input files for years other than 2010, 2030 or 2040 or if they need<br />
to edit input files.</p><br />
<br />
<p>To run the new application, the user first should select a scenario from the<br />
scenario window and then open the new application interface, which looks like<br />
Figure 5.13.</p><br />
<br />
<p><strong>Figure 5‑13 Generate or edit parcel file application<br />
interface</strong><br />
</p><br />
<br />
[[File:Figure 5-13 rev.jpg]]<br />
<br />
<p>The user needs to type in the correct path to the Python.exe file as well as<br />
the correct version of ArcGIS. If the users selects Master and runs the new<br />
application, Cube shows an error message like in Figure 5-14 to warn the user<br />
that the application cannot run for this scenario</p><br />
<br />
<p><br />
</p><br />
<br />
<p><strong>Figure 5‑14 generate or edit parcel file application<br />
warning</strong><br />
</p><br />
<br />
[[File:Figure 5-14rev.jpg]]<br />
<br />
<p>After selecting a scenario and opening the new application interface, the<br />
user should enter the model year (only 2 digits, for instance 10 for 2010 and<br />
40 for 2040), the correct path to the python.exe, the correct version of<br />
ArcGIS, and one of the following options:</p><br />
<br />
<ol><br />
<li><strong>Generate default files</strong>- Select this option if editing the<br />
parcel file is unnecessary; if the user selects this option, the program<br />
generates default files automatically for the selected scenario and model<br />
year.</li><br />
<br />
<li><strong>Edit parcel file</strong>- Select this option if editing the parcel<br />
file is necessary; if the user selects this option, ArcMap will launch to make<br />
the requisite edits for the selected scenario and model year like in Figure<br />
5-15</li><br />
</ol><br />
<br />
<p>If option 1, wait for the program to complete and then run the scenario<br />
normally.</p><br />
<br />
<p>If option 2, continue to <strong><em>ArcMap Parcel Editing</em></strong>in<br />
order to undertake parcel editing.</p><br />
<br />
<p><strong>Figure 5-15: ArcMap Parcel Editing MXD Opened from Cube</strong><br />
</p><br />
<br />
[[File:Figure 5-15rev.jpg]]<br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-ArcMapParcelEditing"><br />
ArcMap Parcel Editing</h4><br />
<br />
<p>After clicking “Run” in the Cube interface, a dialog box will appear similar<br />
to the one in Figure 5-16 below. Click the “Install Add-in” button to install<br />
the “DaySim Input Generator toolbar” into ArcMap. A second dialog will then<br />
appear to confirm that the toolbar was installed successfully. Click “OK” on<br />
this second dialog. ArcMap will then be opened for the user to make parcel<br />
edits and develop DaySim inputs.</p><br />
<br />
<p><strong>Figure 5-16: Install Add-In</strong><br />
</p><br />
<br />
[[File:Figure 5-16rev.jpg]]<br />
<br />
<p>When Cube pushes out to ArcMap the application prepares a workspace for<br />
editing and copies data for the appropriate scenario year for editing.</p><br />
<br />
<p>Note that the Cube application added a layer to the active data frame in<br />
ArcMap called “Edit Parcels”. Please edit the parcel in this layer.<br />
Edit only the parcels you wish to adjust. In order to edit, please do the<br />
following:</p><br />
<br />
<p>Use the zoom tool to identify the area you wish to edit.</p><br />
<br />
<p>This step could take 45-60 minutes depending on processing power.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-17: Identify the<br />
area of Interest</strong><br />
</p><br />
<br />
[[File:Figure 5-17rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">Start an editing session by<br />
clicking the “Editor” drop-down and selecting “Start Editing” option as in<br />
Figure 5-18.</p><br />
<br />
<p align="center" style="text-align: left;"><br />
</p><br />
<br />
<p><strong>Figure 5-18: Start an edit session</strong><br />
</p><br />
<br />
[[File:Figure 5-18rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">If the editor toolbar is not<br />
present in your map document, navigate to Customize - Toolbars - Editor as in<br />
Figure 5-19.</p><br />
<br />
<p><strong>Figure 5-19: Open the Editor toolbar</strong><br />
</p><br />
<br />
[[File:Figure 5-19rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">After selecting the “Start Editing”<br />
option, a warning box like in Figure 5-20 may open explaining that the spatial<br />
reference of the layer does not match the spatial reference of the data frame.<br />
Click “Continue” to continue the edit session.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-20: Edit Session<br />
Warning BOX</strong><br />
</p><br />
<br />
[[File:Figure 5-20.png]]<br />
<br />
<p align="center" style="text-align: left;">Use the standard Esri editing tools<br />
to:</p><br />
<br />
<p>Merge two parcels together:</p><br />
<br />
<p>Use the editing tool to select the polygons you wish to merge then select<br />
“Merge…” from the “Editor” dropdown like in Figure 5-21.</p><br />
<br />
<p>A box will ask you which polygons attributes you would like to keep. Select<br />
one of the polygons and click “OK”. Be sure to update the demographic data once<br />
the merge is complete.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-21: Polygon Merge<br />
tool</strong><br />
</p><br />
<br />
[[File:Figure 5-21rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-22: Polygon<br />
Attribute Merge</strong><br />
</p><br />
<br />
[[File:Figure 5-22rev.jpg]]<br />
<br />
<p>Split a parcel into component parts:</p><br />
<br />
<p>Use the editing tool to select the polygons you wish to split.</p><br />
<br />
<p>Use the “Cut Polygons” tool to split a parcel into two parts as in Figure<br />
5-23.</p><br />
<br />
<p>Be sure to update the demographic data once the split is complete.</p><br />
<br />
<p><br />
</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-23: Using the Cut<br />
Polygon tool to Split a polygon</strong><br />
</p><br />
<br />
[[File:Figure 5-23rev.jpg]]<br />
<br />
<p>Adjust parcel attributes:</p><br />
<br />
<p>Use the editing tool to select the polygon for which you wish to adjust<br />
attributes.</p><br />
<br />
<p>Click the “Attributes” button in the “Editor” Toolbar [[File:attributes_icon.png]] to edit the parcel attributes.</p><br />
<br />
<p>Type in the desired attribute adjustment as in Figure 5-24.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-24: Adjusting<br />
parcel attributes in the attribute table</strong><br />
</p><br />
<br />
[[File:Figure 5-24rev.jpg]]<br />
<br />
<p>Once you are finished with your editing session click “Stop Editing” in the<br />
“Editor” dropdown menu.</p><br />
<br />
<p>Click “Yes” to the Save Edits option</p><br />
<br />
<p>Complete the editing process by using the “DaySim Input Generator toolbar”.<br />
If the DaySim Input Generator toolbar is not present in your map document, use<br />
the following directions:</p><br />
<br />
<p>Navigate to Customize - Add-In Manager - Customize</p><br />
<br />
<p>Click the checkbox next to the “DaySim Input Generator Toolbar” that was<br />
added to the list of Toolbars like in Figure 5-25 then click “Close” to return<br />
to your active dataframe. Your display should look like Figure 5-26.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-25: Customize<br />
Active Toolbars</strong><br />
</p><br />
<br />
[[File:Figure 5-25rev.jpg]]<br />
<br />
<p><br />
</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-26: ArcMap with<br />
DaySim Input Generator Toolbar</strong><br />
</p><br />
<br />
[[File:Figure 5-26.png]]<br />
<br />
<p>In the DaySim Input Generator toolbar, click on the “Parcel Edits Layer:”<br />
dropdown menu to pick the appropriate “Edit Parcels” layer.</p><br />
<br />
<p>Click the DaySim Input Generator Addin button [[File:addin_icon.png]] and the appropriate DaySim inputs are generated and populate the active<br />
scenario’s DaySimInput folder. This process takes several minutes.</p><br />
<br />
<p>A dialog box informs the user of the tool’s completion. Click OK when<br />
prompted by the tool’s finishing.</p><br />
<br />
<p>After the successful toolbar run, close ArcMap. You can save the changes to<br />
the map document (.mxd) if desired.</p><br />
<br />
<p>Back in Cube click on the “OK” button to finish the application run. Then,<br />
the edited parcel files and updated DaySim input files are ready to run by the<br />
main model. To use the new files, make sure to update the following scenario<br />
inputs to refer to the new files:</p><br />
<br />
<p>DaySim parcels</p><br />
<br />
[[File:Daysiminput 02 Parcel.jpg]]<br />
<br />
<p>DaySim HH File</p><br />
<br />
[[File:Daysiminput 03 Household.jpg]]<br />
<br />
<p>DaySim Person File</p><br />
<br />
[[File:Daysiminput 04 Person.jpg]]<br />
<br />
<p>Employment</p><br />
<br />
[[File:Daysiminput 02 Employment-parcel.jpg]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.1.2_DaySim_Input_Preparation_-_Using_Parcel_Editing_Tool&diff=3645.1.2 DaySim Input Preparation - Using Parcel Editing Tool2017-02-14T18:57:10Z<p>Gwineman: Gwineman moved page 5.1.2 DaySim Input Preparation - Using Parcel Editing Tool to 5.2 DaySim Input Preparation - Using Parcel Editing Tool</p>
<hr />
<div>#REDIRECT [[5.2 DaySim Input Preparation - Using Parcel Editing Tool]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_5.0_User_Interface_%26_Running_the_Model&diff=362Chapter: 5.0 User Interface & Running the Model2017-02-14T18:56:47Z<p>Gwineman: </p>
<hr />
<div>*[[5.1 DaySim Input Preparation - Using Manual Methods]]<br />
*[[5.1.2 DaySim Input Preparation - Using Parcel Editing Tool]]<br />
*[[5.2 DaySim Input Preparation - Running the Model]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.1.1_DaySim_Input_Preparation_-_Using_Manual_Methods&diff=3615.1.1 DaySim Input Preparation - Using Manual Methods2017-02-14T18:56:15Z<p>Gwineman: Gwineman moved page 5.1.1 DaySim Input Preparation - Using Manual Methods to 5.1 DaySim Input Preparation - Using Manual Methods</p>
<hr />
<div>#REDIRECT [[5.1 DaySim Input Preparation - Using Manual Methods]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.1_DaySim_Input_Preparation_-_Using_Manual_Methods&diff=3605.1 DaySim Input Preparation - Using Manual Methods2017-02-14T18:56:14Z<p>Gwineman: Gwineman moved page 5.1.1 DaySim Input Preparation - Using Manual Methods to 5.1 DaySim Input Preparation - Using Manual Methods</p>
<hr />
<div>[[Category:5.0 User Interface & Running the Model]]<br />
<br />
<p class="BodyParagraph">This section describes the process of running programs and scripts to prepare various inputs required by DaySim, as well as the process of executing a model run.</p><h3 id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-AllocateTAZDatatoParcels"><span style="color: rgb(255,102,0);">Allocate TAZ Data to Parcels</span></h3><p class="BodyParagraph">A key data preparation step involved allocating TAZ-level controls to the parcels. A flexible tool has been developed in order to allow users to systematically and easily perform this allocation. </p><p class="BodyParagraph">The figure below illustrates the allocation tool user interface.</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-1ALLOCATIONTOOLINTERFACE">FIGURE 5-1 ALLOCATION TOOL INTERFACE</h4><br />
<br />
[[File:Figure 5-1.png]]<br />
<br />
<p class="BodyParagraph">If the user has a pre-generated xml input file, that can be used to populate inputs to the tool. To read an xml file, click on “Read XML Input File” button:</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-2ALLOCATIONTOOLINPUT">FIGURE 5-2 ALLOCATION TOOL INPUT</h4><br />
<br />
[[File:Figure 5-2.png]]<br />
<br />
<p class="BodyParagraph">And navigate to the file:</p><h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-3ALLOCATIONTOOLINPUTXMLFILEDIALOG">FIGURE 5-3 ALLOCATION TOOL INPUT XML FILE DIALOG</h4><br />
<br />
[[File:Figure 5-3.png]]<br />
<br />
<p class="BodyParagraph">After choosing a file, click “Open” and the input fields will be populated automatically. The inputs can be changed if required.</p><h4 id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-4ALLOCATIONTOOLINPUTSNAPSHOT">FIGURE 5-4 ALLOCATION TOOL INPUT SNAPSHOT</h4><br />
<br />
[[File:Figure 5-4.png]]<br />
<br />
<p class="BodyParagraph">ALTERNATIVELY, the inputs can be entered manually as following:</p><p class="BodyParagraph">First, choose a TAZ file</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-5ALLOCATIONTOOLINPUTTAZFILEDIALOG">FIGURE 5-5 ALLOCATION TOOL INPUT TAZ FILE DIALOG</h4><br />
<br />
[[File:Figure 5-5.png]]<br />
<br />
<p class="BodyParagraph">Once a TAZ file is chosen, data fields (columns) in the file would be displayed in the check box.</p><h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-6ALLOCATIONTOOLTAZSELECTIONINTERFACE">FIGURE 5-6 ALLOCATION TOOL TAZ SELECTION INTERFACE</h4><br />
<br />
[[File:Figure 5-6.png]]<br />
<br />
<p class="BodyParagraph">The user then checks the boxes for the employment categories. In addition, the user selects the employment classification system that was used while creating the employment categories. The default is set to NAICS.</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-7ALLOCATIONTOOLTAZCOLUMNSELECTIONINTERFACE">FIGURE 5-7 ALLOCATION TOOL TAZ COLUMN SELECTION INTERFACE</h4><br />
<br />
[[File:Figure 5-7.png]]<br />
<br />
<p class="BodyParagraph">Once done, click OK button. This would open a new form asking the user to select associated NAICS/SIC codes (whichever is chosen before).</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-8ALLOCATIONTOOLINDUSTRYCODEMAPPING">FIGURE 5-8 ALLOCATION TOOL INDUSTRY CODE MAPPING</h4><br />
<br />
[[File:Figure 5-8.png]]<br />
<br />
<p class="BodyParagraph">After this, choose other input files (block file, MAZ geometry file, and school file) appropriately. All four input files are space delimited text files.</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-9ALLOCATIONTOOLINPUTSNAPSHOT">FIGURE 5-9 ALLOCATION TOOL INPUT SNAPSHOT</h4><br />
<br />
[[File:Figure 5-9.png]]<br />
<br />
<p class="BodyParagraph">In the output section, in addition to pointing to output file, the user can also provide output employment categories and indicate associated NAICS codes.</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-10ALLOCATIONTOOLDAYSIMINDUSTRYCATEGORIES">FIGURE 5-10 ALLOCATION TOOL DAYSIM INDUSTRY CATEGORIES</h4><br />
<br />
[[File:Figure 5-10.png]]<br />
<br />
<p class="BodyParagraph">By default, it is assumed that an input file has a header. If not then uncheck the header option. Once, the input and output files are selected, hit RUN to start the distribution process.</p><br />
<br />
<h3 id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-PrepareBufferedParcelFile"><span style="color: rgb(255,102,0);">Prepare Buffered Parcel File</span></h3><br />
<br />
<p class="BodyParagraph">As mentioned previously, the executable for bringing up the buffering tool is “DSBuffTool.exe” and can be found in the “\User.prg\DaySim_Inputs\1_Parcel\Buffering\” folder of the master model directory. Double-clicking the executable will bring up a GUI as shown in the following figure. The use of this tool is straightforward. The user just needs to specify all the inputs and click on the “Run” button at the bottom of the GUI.</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-11DAYSIMBUFFERINGTOOLGUI">FIGURE 5-11 DAYSIM BUFFERING TOOL GUI</h4><br />
<br />
[[File:Figure 5-11.png]]<br />
<br />
<p class="BodyParagraph">In the “INPUT” section of the GUI, distance calculation and buffer type are set to “Euclidean” and “Logistic decay” respectively. These are the recommended settings for running this tool. If node-to-node distances obtained from an all streets network are available, distance calculation may be set to “Node-to-Node”. The default recommended parameters for logistic decay weights (described in the model design chapter) such as buffer decay slope, offset etc., are also automatically populated in the appropriate fields in the GUI.</p><br />
<br />
<p class="BodyParagraph">All other inputs are to specify file paths that can be done by clicking on the “Browse” button. This pops a file dialog as show in the figure below. The user may also enter full file paths manually using keyboard.</p><br />
<br />
<h4 class="BodyParagraph" id="id-5.1.1DAYSIMINPUTPREPARATION-USINGMANUALMETHODS-FIGURE5-12BUFFERTOOLFILESELECTIONDIALOG">FIGURE 5-12 BUFFER TOOL FILE SELECTION DIALOG</h4><br />
<br />
[[File:Figure 5-12.png]]<br />
<br />
<p>All file specification fields for the tool are described below. Details about formats for the input files can be found in the directory and data structures chapter.</p><ul><li><strong>Parcel Data File:</strong> This is the base parcel file. It is obtained by running the disaggregation tool.</li><li><strong>Intersection Data File: </strong>This file has the coordinates of intersections and the number of links intersecting at each one of them.</li><li><strong>Transit Stops File:</strong> This file has the transit stop location coordinates by transit sub-mode.</li><li><strong>Open Spaces File: </strong>This file has the locations and area of parks/open spaces in the model region.</li><li><strong>Circuity Data File:</strong> This is only required for “Circuity” distance calculation that is now an obsolete method.</li></ul><p>The following files are only needed for “Node-to-Node” distance calculation method.</p><ul><li><strong>Node Data File: </strong>This file contains the coordinates of node from an all streets network.</li><li><strong>Node to Node Distance File: </strong>This file contains the network shortest path distances between a list of node pairs that are within 3 miles of each other. It is output from DTALite.</li><li><strong>Extended Node File:</strong> This is an intermediate file created during the buffering process and contains base parcel data aggregated to the network node level. This is created after each parcel/microzone has been associated with the nearest network node.</li><li><strong>Parcel-Node Correspondence File: </strong>This is an intermediate file created during the buffering process and contains the correspondence between parcels and nodes.</li><li><strong>Intersection-Node Correspondence File:</strong> This is an intermediate file created during the buffering process and contains the correspondence between intersections and nodes.</li><li><strong>Stop-Node Correspondence File:</strong> This is an intermediate file created during the buffering process and contains the correspondence between transit stops and nodes.</li><li><strong>Open spaces-Node Correspondence File:</strong> This is an intermediate file created during the buffering process and contains the correspondence between open spaces and nodes.</li><li>Specification of the following XML files is optional. However, they store the input configuration of a buffering tool run and make it convenient to use the tool.</li></ul><p><strong>Output XML File: </strong>If a file is specified in this field, an XML file containing all the input information specified by the user is stored upon clicking on “Run” button that initiated the buffer process.</p><p><strong>XML Input File: </strong>Once an XML file has been stored as described above, it can be selected to automatically populate all the input fields required for a buffer run. This can be used to re-run a buffer process with the same inputs or modify a few inputs to generate a different buffered parcel file.</p><p class="BodyParagraph">Finally, <strong>Buffered Output File</strong> field is used to specify the location and name of the buffered parcel/microzone output file that needs to go into DaySim inputs folder.</p><p class="BodyParagraph"></p></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=359Support/Training2017-02-14T18:53:08Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf|NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 NERPMABv3 Webinar Video Recording]<br />
*[[Media:NERPMAB1v2_Training_June_2016.pdf|NERPMABv2 Training Slides]]<br />
*[[Media:NERPMAB1v2 Webinar Excercise Revised (2).pdf|NERPMABv2 Exercise]]<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=358Support/Training2017-02-14T18:52:43Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf|NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 NERPMABv3 Webinar Video Recording]<br />
*[[Media:NERPMAB1v2_Training_June_2016.pdf|NERPMABv2 Training]]<br />
*[[Media:NERPMAB1v2 Webinar Excercise Revised (2).pdf|NERPMABv2 Exercise]]<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=357Support/Training2017-02-14T18:52:05Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf|NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 NERPMABv3 Webinar Video Recording]<br />
*[[Media:NERPMAB1v2 Webinar Excercise Revised (2).pdf|NERPMABv2 Exercise]]<br />
*[[Media:NERPMAB1v2_Training_June_2016.pdf|NERPMABv2 Training]]<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:NERPMAB1v2_Training_June_2016.pdf&diff=356File:NERPMAB1v2 Training June 2016.pdf2017-02-14T18:51:32Z<p>Gwineman: </p>
<hr />
<div></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=355Support/Training2017-02-14T18:50:06Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf|NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 NERPMABv3 Webinar Video Recording]<br />
*[[Media:NERPMAB1v2 Webinar Excercise Revised (2).pdf|NERPMABv2 Exercise]]<br />
*NERPMABv2 Training<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.2_DaySim_Input_Preparation_-_Using_Parcel_Editing_Tool&diff=3545.2 DaySim Input Preparation - Using Parcel Editing Tool2017-02-14T18:11:27Z<p>Gwineman: </p>
<hr />
<div><br />
[[Category:5.0 User Interface & Running the Model]]<br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CopyGeodatabaseArchivetotheModelDirectory"><br />
Copy Geodatabase Archive to the Model Directory</h4><br />
<br />
<p>The user must have the appropriate zipped geodatabase parcel file in the<br />
“Input_ParcelData” folder within the “NERPMAB1v2” directory. Copy the appropriate year’s<br />
zipped geodatabase into the “Input_ParcelData” folder to run the DaySim input<br />
generator tools successfully. The tool uses the zipped archive so there is no<br />
need to unzip the archive.</p><br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CubeCatalogapplication“GenerateorEditParcelFile”"><br />
Cube Catalog application “Generate or Edit Parcel File”</h4><br />
<br />
<p>The Cube Catalog application “Generate or Edit Parcel File” generates<br />
default DaySim input files or generates an editing environment for parcel<br />
editing based on user input. The user only needs to run this application if<br />
they need input files for years other than 2010, 2030 or 2040 or if they need<br />
to edit input files.</p><br />
<br />
<p>To run the new application, the user first should select a scenario from the<br />
scenario window and then open the new application interface, which looks like<br />
Figure 5.13.</p><br />
<br />
<p><strong>Figure 5‑13 Generate or edit parcel file application<br />
interface</strong><br />
</p><br />
<br />
[[File:Figure 5-13 rev.jpg]]<br />
<br />
<p>The user needs to type in the correct path to the Python.exe file as well as<br />
the correct version of ArcGIS. If the users selects Master and runs the new<br />
application, Cube shows an error message like in Figure 5-14 to warn the user<br />
that the application cannot run for this scenario</p><br />
<br />
<p><br />
</p><br />
<br />
<p><strong>Figure 5‑14 generate or edit parcel file application<br />
warning</strong><br />
</p><br />
<br />
[[File:Figure 5-14rev.jpg]]<br />
<br />
<p>After selecting a scenario and opening the new application interface, the<br />
user should enter the model year (only 2 digits, for instance 10 for 2010 and<br />
40 for 2040), the correct path to the python.exe, the correct version of<br />
ArcGIS, and one of the following options:</p><br />
<br />
<ol><br />
<li><strong>Generate default files</strong>- Select this option if editing the<br />
parcel file is unnecessary; if the user selects this option, the program<br />
generates default files automatically for the selected scenario and model<br />
year.</li><br />
<br />
<li><strong>Edit parcel file</strong>- Select this option if editing the parcel<br />
file is necessary; if the user selects this option, ArcMap will launch to make<br />
the requisite edits for the selected scenario and model year like in Figure<br />
5-15</li><br />
</ol><br />
<br />
<p>If option 1, wait for the program to complete and then run the scenario<br />
normally.</p><br />
<br />
<p>If option 2, continue to <strong><em>ArcMap Parcel Editing</em></strong>in<br />
order to undertake parcel editing.</p><br />
<br />
<p><strong>Figure 5-15: ArcMap Parcel Editing MXD Opened from Cube</strong><br />
</p><br />
<br />
[[File:Figure 5-15rev.jpg]]<br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-ArcMapParcelEditing"><br />
ArcMap Parcel Editing</h4><br />
<br />
<p>After clicking “Run” in the Cube interface, a dialog box will appear similar<br />
to the one in Figure 5-16 below. Click the “Install Add-in” button to install<br />
the “DaySim Input Generator toolbar” into ArcMap. A second dialog will then<br />
appear to confirm that the toolbar was installed successfully. Click “OK” on<br />
this second dialog. ArcMap will then be opened for the user to make parcel<br />
edits and develop DaySim inputs.</p><br />
<br />
<p><strong>Figure 5-16: Install Add-In</strong><br />
</p><br />
<br />
[[File:Figure 5-16rev.jpg]]<br />
<br />
<p>When Cube pushes out to ArcMap the application prepares a workspace for<br />
editing and copies data for the appropriate scenario year for editing.</p><br />
<br />
<p>Note that the Cube application added a layer to the active data frame in<br />
ArcMap called “Edit Parcels”. Please edit the parcel in this layer.<br />
Edit only the parcels you wish to adjust. In order to edit, please do the<br />
following:</p><br />
<br />
<p>Use the zoom tool to identify the area you wish to edit.</p><br />
<br />
<p>This step could take 45-60 minutes depending on processing power.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-17: Identify the<br />
area of Interest</strong><br />
</p><br />
<br />
[[File:Figure 5-17rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">Start an editing session by<br />
clicking the “Editor” drop-down and selecting “Start Editing” option as in<br />
Figure 5-18.</p><br />
<br />
<p align="center" style="text-align: left;"><br />
</p><br />
<br />
<p><strong>Figure 5-18: Start an edit session</strong><br />
</p><br />
<br />
[[File:Figure 5-18rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">If the editor toolbar is not<br />
present in your map document, navigate to Customize - Toolbars - Editor as in<br />
Figure 5-19.</p><br />
<br />
<p><strong>Figure 5-19: Open the Editor toolbar</strong><br />
</p><br />
<br />
[[File:Figure 5-19rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">After selecting the “Start Editing”<br />
option, a warning box like in Figure 5-20 may open explaining that the spatial<br />
reference of the layer does not match the spatial reference of the data frame.<br />
Click “Continue” to continue the edit session.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-20: Edit Session<br />
Warning BOX</strong><br />
</p><br />
<br />
[[File:Figure 5-20.png]]<br />
<br />
<p align="center" style="text-align: left;">Use the standard Esri editing tools<br />
to:</p><br />
<br />
<p>Merge two parcels together:</p><br />
<br />
<p>Use the editing tool to select the polygons you wish to merge then select<br />
“Merge…” from the “Editor” dropdown like in Figure 5-21.</p><br />
<br />
<p>A box will ask you which polygons attributes you would like to keep. Select<br />
one of the polygons and click “OK”. Be sure to update the demographic data once<br />
the merge is complete.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-21: Polygon Merge<br />
tool</strong><br />
</p><br />
<br />
[[File:Figure 5-21rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-22: Polygon<br />
Attribute Merge</strong><br />
</p><br />
<br />
[[File:Figure 5-22rev.jpg]]<br />
<br />
<p>Split a parcel into component parts:</p><br />
<br />
<p>Use the editing tool to select the polygons you wish to split.</p><br />
<br />
<p>Use the “Cut Polygons” tool to split a parcel into two parts as in Figure<br />
5-23.</p><br />
<br />
<p>Be sure to update the demographic data once the split is complete.</p><br />
<br />
<p><br />
</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-23: Using the Cut<br />
Polygon tool to Split a polygon</strong><br />
</p><br />
<br />
[[File:Figure 5-23rev.jpg]]<br />
<br />
<p>Adjust parcel attributes:</p><br />
<br />
<p>Use the editing tool to select the polygon for which you wish to adjust<br />
attributes.</p><br />
<br />
<p>Click the “Attributes” button in the “Editor” Toolbar [[File:attributes_icon.png]] to edit the parcel attributes.</p><br />
<br />
<p>Type in the desired attribute adjustment as in Figure 5-24.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-24: Adjusting<br />
parcel attributes in the attribute table</strong><br />
</p><br />
<br />
[[File:Figure 5-24rev.jpg]]<br />
<br />
<p>Once you are finished with your editing session click “Stop Editing” in the<br />
“Editor” dropdown menu.</p><br />
<br />
<p>Click “Yes” to the Save Edits option</p><br />
<br />
<p>Complete the editing process by using the “DaySim Input Generator toolbar”.<br />
If the DaySim Input Generator toolbar is not present in your map document, use<br />
the following directions:</p><br />
<br />
<p>Navigate to Customize - Add-In Manager - Customize</p><br />
<br />
<p>Click the checkbox next to the “DaySim Input Generator Toolbar” that was<br />
added to the list of Toolbars like in Figure 5-25 then click “Close” to return<br />
to your active dataframe. Your display should look like Figure 5-26.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-25: Customize<br />
Active Toolbars</strong><br />
</p><br />
<br />
[[File:Figure 5-25rev.jpg]]<br />
<br />
<p><br />
</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-26: ArcMap with<br />
DaySim Input Generator Toolbar</strong><br />
</p><br />
<br />
[[File:Figure 5-26.png]]<br />
<br />
<p>In the DaySim Input Generator toolbar, click on the “Parcel Edits Layer:”<br />
dropdown menu to pick the appropriate “Edit Parcels” layer.</p><br />
<br />
<p>Click the DaySim Input Generator Addin button [[File:addin_icon.png]] and the appropriate DaySim inputs are generated and populate the active<br />
scenario’s DaySimInput folder. This process takes several minutes.</p><br />
<br />
<p>A dialog box informs the user of the tool’s completion. Click OK when<br />
prompted by the tool’s finishing.</p><br />
<br />
<p>After the successful toolbar run, close ArcMap. You can save the changes to<br />
the map document (.mxd) if desired.</p><br />
<br />
<p>Back in Cube click on the “OK” button to finish the application run. Then,<br />
the edited parcel files and updated DaySim input files are ready to run by the<br />
main model. To use the new files, make sure to update the following scenario<br />
inputs to refer to the new files:</p><br />
<br />
<p>DaySim parcels</p><br />
<br />
[[File:Daysiminput 02 Parcel.jpg]]<br />
<br />
<p>DaySim HH File</p><br />
<br />
[[File:Daysiminput 03 Household.jpg]]<br />
<br />
<p>DaySim Person File</p><br />
<br />
[[File:Daysiminput 04 Person.jpg]]<br />
<br />
<p>Employment</p><br />
<br />
[[File:Daysiminput 02 Employment-parcel.jpg]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.2_DaySim_Input_Preparation_-_Using_Parcel_Editing_Tool&diff=3535.2 DaySim Input Preparation - Using Parcel Editing Tool2017-02-14T18:06:50Z<p>Gwineman: </p>
<hr />
<div><br />
[[Category:5.0 User Interface & Running the Model]]<br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CopyGeodatabaseArchivetotheModelDirectory"><br />
Copy Geodatabase Archive to the Model Directory</h4><br />
<br />
<p>The user must have the appropriate zipped geodatabase parcel file in the<br />
“Input_ParcelData” folder within the “NERPMAB1v2” directory. Copy the appropriate year’s<br />
zipped geodatabase into the “Input_ParcelData” folder to run the DaySim input<br />
generator tools successfully. The tool uses the zipped archive so there is no<br />
need to unzip the archive.</p><br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-CubeCatalogapplication“GenerateorEditParcelFile”"><br />
Cube Catalog application “Generate or Edit Parcel File”</h4><br />
<br />
<p>The Cube Catalog application “Generate or Edit Parcel File” generates<br />
default DaySim input files or generates an editing environment for parcel<br />
editing based on user input. The user only needs to run this application if<br />
they need input files for years other than 2010, 2030 or 2040 or if they need<br />
to edit input files.</p><br />
<br />
<p>To run the new application, the user first should select a scenario from the<br />
scenario window and then open the new application interface, which looks like<br />
Figure 5.13.</p><br />
<br />
<p><strong>Figure 5‑13 Generate or edit parcel file application<br />
interface</strong><br />
</p><br />
<br />
[[File:Figure 5-13rev.jpg]]<br />
<br />
<p>The user needs to type in the correct path to the Python.exe file as well as<br />
the correct version of ArcGIS. If the users selects Master and runs the new<br />
application, Cube shows an error message like in Figure 5-14 to warn the user<br />
that the application cannot run for this scenario</p><br />
<br />
<p><br />
</p><br />
<br />
<p><strong>Figure 5‑14 generate or edit parcel file application<br />
warning</strong><br />
</p><br />
<br />
[[File:Figure 5-14rev.jpg]]<br />
<br />
<p>After selecting a scenario and opening the new application interface, the<br />
user should enter the model year (only 2 digits, for instance 10 for 2010 and<br />
40 for 2040), the correct path to the python.exe, the correct version of<br />
ArcGIS, and one of the following options:</p><br />
<br />
<ol><br />
<li><strong>Generate default files</strong>- Select this option if editing the<br />
parcel file is unnecessary; if the user selects this option, the program<br />
generates default files automatically for the selected scenario and model<br />
year.</li><br />
<br />
<li><strong>Edit parcel file</strong>- Select this option if editing the parcel<br />
file is necessary; if the user selects this option, ArcMap will launch to make<br />
the requisite edits for the selected scenario and model year like in Figure<br />
5-15</li><br />
</ol><br />
<br />
<p>If option 1, wait for the program to complete and then run the scenario<br />
normally.</p><br />
<br />
<p>If option 2, continue to <strong><em>ArcMap Parcel Editing</em></strong>in<br />
order to undertake parcel editing.</p><br />
<br />
<p><strong>Figure 5-15: ArcMap Parcel Editing MXD Opened from Cube</strong><br />
</p><br />
<br />
[[File:Figure 5-15rev.jpg]]<br />
<br />
<h4 id=<br />
"id-5.1.2DAYSIMINPUTPREPARATION-USINGPARCELEDITINGTOOL-ArcMapParcelEditing"><br />
ArcMap Parcel Editing</h4><br />
<br />
<p>After clicking “Run” in the Cube interface, a dialog box will appear similar<br />
to the one in Figure 5-16 below. Click the “Install Add-in” button to install<br />
the “DaySim Input Generator toolbar” into ArcMap. A second dialog will then<br />
appear to confirm that the toolbar was installed successfully. Click “OK” on<br />
this second dialog. ArcMap will then be opened for the user to make parcel<br />
edits and develop DaySim inputs.</p><br />
<br />
<p><strong>Figure 5-16: Install Add-In</strong><br />
</p><br />
<br />
[[File:Figure 5-16rev.jpg]]<br />
<br />
<p>When Cube pushes out to ArcMap the application prepares a workspace for<br />
editing and copies data for the appropriate scenario year for editing.</p><br />
<br />
<p>Note that the Cube application added a layer to the active data frame in<br />
ArcMap called “Edit Parcels”. Please edit the parcel in this layer.<br />
Edit only the parcels you wish to adjust. In order to edit, please do the<br />
following:</p><br />
<br />
<p>Use the zoom tool to identify the area you wish to edit.</p><br />
<br />
<p>This step could take 45-60 minutes depending on processing power.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-17: Identify the<br />
area of Interest</strong><br />
</p><br />
<br />
[[File:Figure 5-17rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">Start an editing session by<br />
clicking the “Editor” drop-down and selecting “Start Editing” option as in<br />
Figure 5-18.</p><br />
<br />
<p align="center" style="text-align: left;"><br />
</p><br />
<br />
<p><strong>Figure 5-18: Start an edit session</strong><br />
</p><br />
<br />
[[File:Figure 5-18rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">If the editor toolbar is not<br />
present in your map document, navigate to Customize - Toolbars - Editor as in<br />
Figure 5-19.</p><br />
<br />
<p><strong>Figure 5-19: Open the Editor toolbar</strong><br />
</p><br />
<br />
[[File:Figure 5-19rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">After selecting the “Start Editing”<br />
option, a warning box like in Figure 5-20 may open explaining that the spatial<br />
reference of the layer does not match the spatial reference of the data frame.<br />
Click “Continue” to continue the edit session.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-20: Edit Session<br />
Warning BOX</strong><br />
</p><br />
<br />
[[File:Figure 5-20rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;">Use the standard Esri editing tools<br />
to:</p><br />
<br />
<p>Merge two parcels together:</p><br />
<br />
<p>Use the editing tool to select the polygons you wish to merge then select<br />
“Merge…” from the “Editor” dropdown like in Figure 5-21.</p><br />
<br />
<p>A box will ask you which polygons attributes you would like to keep. Select<br />
one of the polygons and click “OK”. Be sure to update the demographic data once<br />
the merge is complete.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-21: Polygon Merge<br />
tool</strong><br />
</p><br />
<br />
[[File:Figure 5-21rev.jpg]]<br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-22: Polygon<br />
Attribute Merge</strong><br />
</p><br />
<br />
[[File:Figure 5-22rev.jpg]]<br />
<br />
<p>Split a parcel into component parts:</p><br />
<br />
<p>Use the editing tool to select the polygons you wish to split.</p><br />
<br />
<p>Use the “Cut Polygons” tool to split a parcel into two parts as in Figure<br />
5-23.</p><br />
<br />
<p>Be sure to update the demographic data once the split is complete.</p><br />
<br />
<p><br />
</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-23: Using the Cut<br />
Polygon tool to Split a polygon</strong><br />
</p><br />
<br />
[[File:Figure 5-23rev.jpg]]<br />
<br />
<p>Adjust parcel attributes:</p><br />
<br />
<p>Use the editing tool to select the polygon for which you wish to adjust<br />
attributes.</p><br />
<br />
<p>Click the “Attributes” button in the “Editor” Toolbar [[File:attributes_icon.png]] to edit the parcel attributes.</p><br />
<br />
<p>Type in the desired attribute adjustment as in Figure 5-24.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-24: Adjusting<br />
parcel attributes in the attribute table</strong><br />
</p><br />
<br />
[[File:Figure 5-24rev.jpg]<br />
<br />
<p>Once you are finished with your editing session click “Stop Editing” in the<br />
“Editor” dropdown menu.</p><br />
<br />
<p>Click “Yes” to the Save Edits option</p><br />
<br />
<p>Complete the editing process by using the “DaySim Input Generator toolbar”.<br />
If the DaySim Input Generator toolbar is not present in your map document, use<br />
the following directions:</p><br />
<br />
<p>Navigate to Customize - Add-In Manager - Customize</p><br />
<br />
<p>Click the checkbox next to the “DaySim Input Generator Toolbar” that was<br />
added to the list of Toolbars like in Figure 5-25 then click “Close” to return<br />
to your active dataframe. Your display should look like Figure 5-26.</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-25: Customize<br />
Active Toolbars</strong><br />
</p><br />
<br />
[[File:Figure 5-25rev.jpg]]<br />
<br />
<p><br />
</p><br />
<br />
<p align="center" style="text-align: left;"><strong>Figure 5-26: ArcMap with<br />
DaySim Input Generator Toolbar</strong><br />
</p><br />
<br />
[[File:Figure 5-26rev.jpg]]<br />
<br />
<p>In the DaySim Input Generator toolbar, click on the “Parcel Edits Layer:”<br />
dropdown menu to pick the appropriate “Edit Parcels” layer.</p><br />
<br />
<p>Click the DaySim Input Generator Addin button [[File:addin_icon.png]] and the appropriate DaySim inputs are generated and populate the active<br />
scenario’s DaySimInput folder. This process takes several minutes.</p><br />
<br />
<p>A dialog box informs the user of the tool’s completion. Click OK when<br />
prompted by the tool’s finishing.</p><br />
<br />
<p>After the successful toolbar run, close ArcMap. You can save the changes to<br />
the map document (.mxd) if desired.</p><br />
<br />
<p>Back in Cube click on the “OK” button to finish the application run. Then,<br />
the edited parcel files and updated DaySim input files are ready to run by the<br />
main model. To use the new files, make sure to update the following scenario<br />
inputs to refer to the new files:</p><br />
<br />
<p>DaySim parcels</p><br />
<br />
<p>DaySim HH File</p><br />
<br />
<p>DaySim Person File</p><br />
<br />
<p>Employment</p></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=352Support/Training2017-02-14T18:03:11Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 Webinar Video Recording]<br />
*[[Media:NERPMAB1v2 Webinar Excercise Revised (2).pdf|Webinar Exercise]]<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=351Support/Training2017-02-14T18:01:07Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 Webinar Video Recording]<br />
*[[File:NERPMAB1v2 Webinar Excercise Revised (2).pdf|Example Exercise]]<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=350Support/Training2017-02-14T18:00:02Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 Webinar Video Recording]<br />
*[[File:NERPMAB1v2 Webinar Excercise Revised (2).pdf Example Exercise]]<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=349Support/Training2017-02-14T17:56:59Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*[https://vimeo.com/202441046 Webinar Video Recording]<br />
*[[Example Exercise]]<br />
<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=348Support/Training2017-02-14T17:55:33Z<p>Gwineman: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]".<br />
For guidance on the use of the Scenario application, Generate or Edit Parcel application, and the Select Link Analysis tool, please check the "[[https://youtu.be/IApPyy-Zi_s NERPMAB1v2 Webinar, June 15, 2016]]".<br />
<br />
*[[Media:NERPMABv3_Update_Overview_Webinar_Slides.pdf]] <br />
*Webinar Video Recording<br />
*[[Example Exercise]]<br />
<br />
<br />
If you need additional information, please contact [[mailto:mlocklear@northfloridatpo.com?cc=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3477.2 Version NERPMAB1v32017-02-14T17:53:26Z<p>Gwineman: </p>
<hr />
<div>'''7.2 VERSION NERPM-AB1v3'''<br />
<br />
This section documents the second set of improvements that were made to the NERPM model since the release of NERPM-AB1v2. The improvements focused on: <br />
<br />
*corrections and updates made to the Master Network<br />
*development of interim years 2025 and 2035<br />
*addition of a Site Impact Analysis application<br />
*ability to run one-time period in the Highway Assignment<br />
*simplification of the use of the statewide freight model step<br />
*Cube Version 6.4.2 compatibility<br />
<br />
'''Master Network'''<br />
<br />
Corrections and updates have been made to the MicroCodedHnet42.net located in the Parameters folder. The updates/corrections necessitated updates to the turn penalty files in the CF2040 and INT2030 folder. <br />
<br />
'''Primary changes to the updated MicroCodedHnet42:'''<br />
<br />
*Added network attributes for Analysis Year 2025 and 2035. Corresponding Input directories are provided in the NERPMAV1v3 release.<br />
*TAZ 527: Added centroid connector (cc) to US 1 Philips Hwy and removed cc to I-95<br />
*I-95 and San Diego Rd (74353): Removed I-95 access from and to San Diego Road<br />
*I-95 and Kings Ave (Nodes 40557-40468-411131): Allowed access to I-95 from Kings Ave<br />
*SR 200 / A1A from Stratton to Griffin Road: Corrected lane age from 2/U to 4/D<br />
<br />
In addition, the interim years 2025 and 2035 were added to the Master Network as well as to the scenarios in the NERPM-AB1v3 User Interphase.<br />
<br />
'''Year 2025'''<br />
<br />
The projects in the year 2025 highway network were selected based on the funding information developed for the Path Forward 2040 LRTP. In this process, funding source availability and project implementation were documented in five-year time periods. The transit projects were kept identical to those projects as listed for the EC2018 transit network. No additional changes were made to the transit network. The socioeconomic data was developed using the Editing Tool. EE and EI trips tables were developed through straight line projection between the years 2010 and 2040. <br />
<br />
'''Year 2035'''<br />
<br />
The projects in the year 2035 highway network were selected based on the funding information developed for the Path Forward 2040 LRTP. In this process, funding source availability and project implementation were documented in five-year time periods. The transit projects were kept identical to those projects listed in the INT2030 transit network. No additional changes were made to the transit network. The socioeconomic data was developed using the Editing Tool. EE and EI trips tables were developed through straight line projection between the years 2010 and 2040. <br />
<br />
'''Site Impact Analysis Application'''<br />
<br />
The Site Impact Analysis tool was added as an application in the User Interphase. This tool provides the user with an easy way to post the difference between two runs, e.g. a Build and a No Build scenario. In the Doc folder of the NERPM-AB1v3 the Power Point file “NERPM-AB1v3 Overview” provides the user with a step by step overview on how to execute the Site Impact Analysis tool. The tool creates an output file named SI_Loaded_CombinedPeriods.Net. In this file the difference between the two selected networks is listed in volumes and in percentages for each time period and by trip table. Table 7-1 lists all the fields in the SI_Loaded_CombinedPersios.Net file. This table can also be found in the Doc folder<br />
<br />
'''Highway Traffic Assignment'''<br />
<br />
In this version of the model, the user has the option of choosing which time period to run in the highway assignment step. In the Doc folder of the NERPM-AB1v3 the Power Point file “NERPM-AB1v3 Overview” provides the user with a step by step overview on how to run only one highway assignment period. <br />
The NERPM-AB1v3 has four time periods (AM, MD, PM and NT). These time periods are listed on the last page of the User Interphase. The user can run/select any combination. '''However, it is important to note that in the current version, the user needs to make sure the output files for those time periods not run, are located in the output folder'''. The FINAL.ASGN_*.net files need to be in the folder for the model to run. If the user does not select all time periods, a message will remind the user to copy the files. <br />
<br />
It is also important to note, that only the time period which the user runs will be updated in the daily assignment file. <br />
<br />
'''Cube Version 6.4.2'''<br />
<br />
NERPM-AB1v3 was run using the latest Cube version 6.4.2. The highway and transit assignments were compared against Cube Version 6.1.1 and no significant differences were identified. <br />
The NERPM-AB does not run with Cube version 6.4.1.<br />
<br />
Additional information regarding this release:<br />
<br />
'''*ArcGIS Versions Compatibility'''<br />
<br />
The Generate of Edit Parcel File Application developed for use with the NERPM-AB model has been tested and is compatible with ArcGIS10.2. The Generate of Edit Parcel File Application might not be compatible with the newer versions of ArcGIS. However, recently the tool was tested with ArcGIS 10.4, and with the following changes in the code, the tool will be compatible with the latest version.<br />
<br />
[[File:NERPM fields - bottom of 7.2.jpg]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=308MediaWiki:Sidebar2016-10-28T13:38:40Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
** Chapter: 1.0 Overview|Chapter: 1.0 Overview<br />
** Chapter: 2.0 Hardware & Software Requirements|Chapter: 2.0 Hardware & Software Requirements<br />
** Chapter: 3.0 Model Design|Chapter: 3.0 Model Design<br />
** Chapter: 4.0 Directory & Data Structures|Chapter: 4.0 Directory & Data Structures<br />
** Chapter: 5.0 User Interface & Running the Model|Chapter: 5.0 User Interface & Running the Model<br />
** Chapter: 6.0 Configuring a Scenario|Chapter: 6.0 Configuring a Scenario<br />
** Chapter: 7.0 Version Updates|Chapter: 7.0 Version Updates<br />
** Frequently Asked Questions<br />
** Support/Training<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_6.0_Configuring_a_Scenario&diff=307Chapter: 6.0 Configuring a Scenario2016-10-28T13:38:05Z<p>Gwineman: </p>
<hr />
<div>This section provides guidance on steps necessary to perform in order to reflect the changes in existing model conditions such as transportation infrastructure, land use, or household/person socio-economics.<br />
<br />
*[[6.1 General Overview]]<br />
*[[6.2 Existing Scenarios]]<br />
*[[6.3 Creating a New Scenario]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=306MediaWiki:Sidebar2016-10-28T13:37:19Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
** Chapter: 1.0 Overview|Chapter: 1.0 Overview<br />
** Chapter: 2.0 Hardware & Software Requirements|Chapter: 2.0 Hardware & Software Requirements<br />
** Chapter: 3.0 Model Design|Chapter: 3.0 Model Design<br />
** Chapter: 4.0 Directory & Data Structures|Chapter: 4.0 Directory & Data Structures<br />
** Chapter: 5.0 User Interface & Running the Model|Chapter: 5.0 User Interface & Running the Model<br />
** Chapter: 6.0 Configuring a Scenario|Chapter: 6.0 Configuring a Scenario<br />
** Chapter: 7.0 Version Updates|Chapter: 7.0 Version Updates<br />
** Frequently Asked Questions<br />
** Support/Training<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages<br />
<br />
<br />
<!--**Category:1.0 Overview | Chapter: 1.0 Overview<br />
**Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements<br />
**Category:3.0 Model Design | Chapter: 3.0 Model Design<br />
**Category:4.0 Directory & Data Structures | Chapter: 4.0 Directory & Data Structures<br />
**Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model<br />
**Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario<br />
**Category:7.0 Version Updates | Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training /--></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=305MediaWiki:Sidebar2016-10-28T13:36:13Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
** Chapter: 1.0 Overview<br />
** Chapter: 2.0 Hardware & Software Requirements<br />
** Chapter: 3.0 Model Design<br />
** Chapter: 4.0 Directory & Data Structures<br />
** Chapter: 5.0 User Interface & Running the Model<br />
** Chapter: 6.0 Configuring a Scenario<br />
** Chapter: 7.0 Version Updates<br />
** Frequently Asked Questions<br />
** Support/Training<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages<br />
<br />
<br />
<!--**Category:1.0 Overview | Chapter: 1.0 Overview<br />
**Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements<br />
**Category:3.0 Model Design | Chapter: 3.0 Model Design<br />
**Category:4.0 Directory & Data Structures | Chapter: 4.0 Directory & Data Structures<br />
**Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model<br />
**Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario<br />
**Category:7.0 Version Updates | Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training /--></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=304MediaWiki:Sidebar2016-10-28T13:35:37Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
**Chapter: 1.0 Overview<br />
**Chapter: 2.0 Hardware & Software Requirements<br />
**Chapter: 3.0 Model Design<br />
**Chapter: 4.0 Directory & Data Structures<br />
**Chapter: 5.0 User Interface & Running the Model<br />
**Chapter: 6.0 Configuring a Scenario<br />
**Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=303MediaWiki:Sidebar2016-10-28T13:34:58Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
<!--**Category:1.0 Overview | Chapter: 1.0 Overview<br />
**Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements<br />
**Category:3.0 Model Design | Chapter: 3.0 Model Design<br />
**Category:4.0 Directory & Data Structures | Chapter: 4.0 Directory & Data Structures<br />
**Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model<br />
**Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario<br />
**Category:7.0 Version Updates | Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training /--><br />
**Chapter: 1.0 Overview<br />
**Chapter: 2.0 Hardware & Software Requirements<br />
**Chapter: 3.0 Model Design<br />
**Chapter: 4.0 Directory & Data Structures<br />
**Chapter: 5.0 User Interface & Running the Model<br />
**Chapter: 6.0 Configuring a Scenario<br />
**Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=302MediaWiki:Sidebar2016-10-28T13:34:06Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
<!--**Category:1.0 Overview | Chapter: 1.0 Overview<br />
**Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements<br />
**Category:3.0 Model Design | Chapter: 3.0 Model Design<br />
**Category:4.0 Directory & Data Structures | Chapter: 4.0 Directory & Data Structures<br />
**Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model<br />
**Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario<br />
**Category:7.0 Version Updates | Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training /--><br />
<br />
*Chapter: 1.0 Overview<br />
*Chapter: 2.0 Hardware & Software Requirements<br />
*Chapter: 3.0 Model Design<br />
*Chapter: 4.0 Directory & Data Structures<br />
*Chapter: 5.0 User Interface & Running the Model<br />
*Chapter: 6.0 Configuring a Scenario<br />
*Chapter: 7.0 Version Updates<br />
*[requently Asked Questions<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=301MediaWiki:Sidebar2016-10-28T13:33:45Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
<!--**Category:1.0 Overview | Chapter: 1.0 Overview<br />
**Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements<br />
**Category:3.0 Model Design | Chapter: 3.0 Model Design<br />
**Category:4.0 Directory & Data Structures | Chapter: 4.0 Directory & Data Structures<br />
**Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model<br />
**Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario<br />
**Category:7.0 Version Updates | Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training/--><br />
*Chapter: 1.0 Overview<br />
*Chapter: 2.0 Hardware & Software Requirements<br />
*Chapter: 3.0 Model Design<br />
*Chapter: 4.0 Directory & Data Structures<br />
*Chapter: 5.0 User Interface & Running the Model<br />
*Chapter: 6.0 Configuring a Scenario<br />
*Chapter: 7.0 Version Updates<br />
*[requently Asked Questions<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=300MediaWiki:Sidebar2016-10-28T13:32:59Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
<!--**Category:1.0 Overview | Chapter: 1.0 Overview<br />
**Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements<br />
**Category:3.0 Model Design | Chapter: 3.0 Model Design<br />
**Category:4.0 Directory & Data Structures | Chapter: 4.0 Directory & Data Structures<br />
**Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model<br />
**Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario<br />
**Category:7.0 Version Updates | Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training/--><br />
*[[Chapter: 1.0 Overview]]<br />
*[[Chapter: 2.0 Hardware & Software Requirements]]<br />
*[[Chapter: 3.0 Model Design]]<br />
*[[Chapter: 4.0 Directory & Data Structures]]<br />
*[[Chapter: 5.0 User Interface & Running the Model]]<br />
*[[Chapter: 6.0 Configuring a Scenario]]<br />
*[[Chapter: 7.0 Version Updates]]<br />
*[[Frequently Asked Questions]]<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=North_Florida_TPO_Model_Users%E2%80%99_Guide&diff=299North Florida TPO Model Users’ Guide2016-10-28T13:32:23Z<p>Gwineman: </p>
<hr />
<div><h2>Northeast Regional Planning Model: Activity Based</h2><br />
<br />
[[File:model_image.jpg]]<br />
<br />
<h5>PREPARED FOR: North Florida Transportation Planning Organization</h5><br />
<br />
<!--<br />
*[[:Category:1.0 Overview | Chapter: 1.0 Overview]]<br />
*[[:Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements]]<br />
*[[:Category:3.0 Model Design | Chapter| 3.0 Model Design]]<br />
*[[:Category:4.0 Directory & Data Structures | Chapter:4.0 Directory & Data Structures]]<br />
*[[:Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model]]<br />
*[[:Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario]]<br />
*[[:Category:7.0 Version Updates | Chapter: 7.0 Version Updates]]<br />
*[[Frequently Asked Questions]]<br />
*[[Support/Training]]<br />
/--><br />
*[[Chapter: 1.0 Overview]]<br />
*[[Chapter: 2.0 Hardware & Software Requirements]]<br />
*[[Chapter: 3.0 Model Design]]<br />
*[[Chapter: 4.0 Directory & Data Structures]]<br />
*[[Chapter: 5.0 User Interface & Running the Model]]<br />
*[[Chapter: 6.0 Configuring a Scenario]]<br />
*[[Chapter: 7.0 Version Updates]]<br />
*[[Frequently Asked Questions]]<br />
*[[Support/Training]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_7.0_Version_Updates&diff=298Chapter: 7.0 Version Updates2016-10-28T13:31:35Z<p>Gwineman: Created page with "*7.1 Version NERPMAB1v2"</p>
<hr />
<div>*[[7.1 Version NERPMAB1v2]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_6.0_Configuring_a_Scenario&diff=297Chapter: 6.0 Configuring a Scenario2016-10-28T13:30:57Z<p>Gwineman: Created page with "*6.1 General Overview *6.2 Existing Scenarios *6.3 Creating a New Scenario"</p>
<hr />
<div>*[[6.1 General Overview]]<br />
*[[6.2 Existing Scenarios]]<br />
*[[6.3 Creating a New Scenario]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_5.0_User_Interface_%26_Running_the_Model&diff=296Chapter: 5.0 User Interface & Running the Model2016-10-28T13:30:39Z<p>Gwineman: Created page with "*5.1.1 DaySim Input Preparation - Using Manual Methods *5.1.2 DaySim Input Preparation - Using Parcel Editing Tool *5.2 DaySim Input Preparation - Running the Model"</p>
<hr />
<div>*[[5.1.1 DaySim Input Preparation - Using Manual Methods]]<br />
*[[5.1.2 DaySim Input Preparation - Using Parcel Editing Tool]]<br />
*[[5.2 DaySim Input Preparation - Running the Model]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_4.0_Directory_%26_Data_Structures&diff=295Chapter: 4.0 Directory & Data Structures2016-10-28T13:30:17Z<p>Gwineman: Created page with "* 4.1 Master Model Directory * 4.2 Network Skims * 4.3 DaySim * 4.4 DaySim-Cube Linkage * 4.5 Auxiliary Demand * 4.6 Network Assignment * 4.7 Post Pr..."</p>
<hr />
<div>* [[4.1 Master Model Directory]]<br />
* [[4.2 Network Skims]]<br />
* [[4.3 DaySim]]<br />
* [[4.4 DaySim-Cube Linkage]]<br />
* [[4.5 Auxiliary Demand]]<br />
* [[4.6 Network Assignment]]<br />
* [[4.7 Post Processing]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_3.0_Model_Design&diff=294Chapter: 3.0 Model Design2016-10-28T13:29:40Z<p>Gwineman: Created page with "*3.1 Process Flow *3.2 All Streets Network Preparation *3.3 Short Distance Impedance Generation *3.4 Land Use Data Prep *3.5 Synthetic Population *3.6 Da..."</p>
<hr />
<div>*[[3.1 Process Flow]]<br />
*[[3.2 All Streets Network Preparation]]<br />
*[[3.3 Short Distance Impedance Generation]]<br />
*[[3.4 Land Use Data Prep]]<br />
*[[3.5 Synthetic Population]]<br />
*[[3.6 Daysim Inputs]]<br />
*[[3.7 Configuration]]<br />
*[[3.8 Network Preparation & Skimming]]<br />
*[[3.9 Auxiliary Demand]]<br />
*[[3.10 DaySim]]<br />
*[[3.11 Assignment Preparation]]<br />
*[[3.12 Assignment]]<br />
*[[3.13 Feedback]]<br />
*[[3.14 Reporting]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=North_Florida_TPO_Model_Users%E2%80%99_Guide&diff=293North Florida TPO Model Users’ Guide2016-10-28T13:29:26Z<p>Gwineman: </p>
<hr />
<div><h2>Northeast Regional Planning Model: Activity Based</h2><br />
<br />
[[File:model_image.jpg]]<br />
<br />
<h5>PREPARED FOR: North Florida Transportation Planning Organization</h5><br />
<br />
*[[:Category:1.0 Overview | Chapter: 1.0 Overview]]<br />
*[[:Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements]]<br />
*[[:Category:3.0 Model Design | Chapter| 3.0 Model Design]]<br />
*[[:Category:4.0 Directory & Data Structures | Chapter:4.0 Directory & Data Structures]]<br />
*[[:Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model]]<br />
*[[:Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario]]<br />
*[[:Category:7.0 Version Updates | Chapter: 7.0 Version Updates]]<br />
*[[Frequently Asked Questions]]<br />
*[[Support/Training]]<br />
<br />
<br />
<br />
*[[Chapter: 1.0 Overview]]<br />
*[[Chapter: 2.0 Hardware & Software Requirements]]<br />
*[[Chapter: 3.0 Model Design]]<br />
*[[Chapter: 4.0 Directory & Data Structures]]<br />
*[[Chapter: 5.0 User Interface & Running the Model]]<br />
*[[Chapter: 6.0 Configuring a Scenario]]<br />
*[[Chapter: 7.0 Version Updates]]<br />
*[[Frequently Asked Questions]]<br />
*[[Support/Training]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_2.0_Hardware_%26_Software_Requirements&diff=292Chapter: 2.0 Hardware & Software Requirements2016-10-28T13:28:24Z<p>Gwineman: Created page with "*2.1 Hardware Requirements *2.2 Software Requirements"</p>
<hr />
<div>*[[2.1 Hardware Requirements]]<br />
*[[2.2 Software Requirements]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Chapter:_1.0_Overview&diff=291Chapter: 1.0 Overview2016-10-28T13:27:10Z<p>Gwineman: Created page with "*1.1 Model System *1.2 Model Sensitivities"</p>
<hr />
<div>*[[1.1 Model System]]<br />
*[[1.2 Model Sensitivities]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=North_Florida_TPO_Model_Users%E2%80%99_Guide&diff=290North Florida TPO Model Users’ Guide2016-10-28T13:26:10Z<p>Gwineman: </p>
<hr />
<div><h2>Northeast Regional Planning Model: Activity Based</h2><br />
<br />
[[File:model_image.jpg]]<br />
<br />
<h5>PREPARED FOR: North Florida Transportation Planning Organization</h5><br />
<br />
*[[:Category:1.0 Overview | Chapter: 1.0 Overview]]<br />
*[[:Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements]]<br />
*[[:Category:3.0 Model Design | Chapter| 3.0 Model Design]]<br />
*[[:Category:4.0 Directory & Data Structures | Chapter:4.0 Directory & Data Structures]]<br />
*[[:Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model]]<br />
*[[:Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario]]<br />
*[[:Category:7.0 Version Updates | Chapter: 7.0 Version Updates]]<br />
*[[Frequently Asked Questions]]<br />
*[[Support/Training]]<br />
<br />
<br />
<br />
*[[Chapter: 1.0 Overview]]<br />
*[[Chapter: 2.0 Hardware & Software Requirements]]<br />
*[[Chapter| 3.0 Model Design]]<br />
*[[Chapter:4.0 Directory & Data Structures]]<br />
*[[Chapter: 5.0 User Interface & Running the Model]]<br />
*[[Chapter: 6.0 Configuring a Scenario]]<br />
*[[Chapter: 7.0 Version Updates]]<br />
*[[Frequently Asked Questions]]<br />
*[[Support/Training]]</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Category:1.0_Overview&diff=289Category:1.0 Overview2016-10-28T12:22:49Z<p>Gwineman: Blanked the page</p>
<hr />
<div></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Category:1.0_Overview&diff=288Category:1.0 Overview2016-10-28T12:21:27Z<p>Gwineman: </p>
<hr />
<div>{{#catlabel: categories | newtitle | newtext}}</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=MediaWiki:Sidebar&diff=287MediaWiki:Sidebar2016-10-26T17:01:24Z<p>Gwineman: </p>
<hr />
<div>* navigation<br />
** NFTPO_Model|Home<br />
**Category:1.0 Overview | Chapter: 1.0 Overview<br />
**Category:2.0 Hardware & Software Requirements | Chapter: 2.0 Hardware & Software Requirements<br />
**Category:3.0 Model Design | Chapter: 3.0 Model Design<br />
**Category:4.0 Directory & Data Structures | Chapter: 4.0 Directory & Data Structures<br />
**Category:5.0 User Interface & Running the Model | Chapter: 5.0 User Interface & Running the Model<br />
**Category:6.0 Configuring a Scenario | Chapter: 6.0 Configuring a Scenario<br />
**Category:7.0 Version Updates | Chapter: 7.0 Version Updates<br />
**Frequently Asked Questions<br />
**Support/Training<br />
<br />
* TOOLBOX<br />
**Support/Training|Support/Training<br />
** Frequently_Asked_Questions|FAQs<br />
** PRINT|printableversion<br />
** UPLOAD|upload<br />
** SPECIALPAGES|specialpages</div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Category:7.0_Version_Updates&diff=286Category:7.0 Version Updates2016-10-26T16:57:07Z<p>Gwineman: </p>
<hr />
<div><!--<br />
*[[7.1 Version NERPMAB1v2]]<br />
--></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Category:6.0_Configuring_a_Scenario&diff=285Category:6.0 Configuring a Scenario2016-10-26T16:56:50Z<p>Gwineman: </p>
<hr />
<div>This section provides guidance on steps necessary to perform in order to reflect the changes in existing model conditions such as transportation infrastructure, land use, or household/person socio-economics.<br />
<br />
<!--<br />
*[[6.1 General Overview]]<br />
*[[6.2 Existing Scenarios]]<br />
*[[6.3 Creating a New Scenario]]<br />
--></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Category:5.0_User_Interface_%26_Running_the_Model&diff=284Category:5.0 User Interface & Running the Model2016-10-26T16:56:37Z<p>Gwineman: </p>
<hr />
<div><!--<br />
*[[5.1.1 DaySim Input Preparation - Using Manual Methods]]<br />
*[[5.1.2 DaySim Input Preparation - Using Parcel Editing Tool]]<br />
*[[5.2 DaySim Input Preparation - Running the Model]]<br />
--></div>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=Category:4.0_Directory_%26_Data_Structures&diff=283Category:4.0 Directory & Data Structures2016-10-26T16:56:18Z<p>Gwineman: </p>
<hr />
<div><!--<br />
* [[4.1 Master Model Directory]]<br />
* [[4.2 Network Skims]]<br />
* [[4.3 DaySim]]<br />
* [[4.4 DaySim-Cube Linkage]]<br />
* [[4.5 Auxiliary Demand]]<br />
* [[4.6 Network Assignment]]<br />
* [[4.7 Post Processing]]<br />
--></div>Gwineman