http://visummodelwiki.northfloridatpo.com/api.php?action=feedcontributions&feedformat=atom&user=Mvpenningtonvisummodelwiki - User contributions [en]2026-05-15T13:42:51ZUser contributionsMediaWiki 1.27.1http://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=392Frequently Asked Questions2019-02-20T16:50:02Z<p>Mvpennington: </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 />
'''I noticed that when I rerun the model without any change to model inputs and scripts, the output trip tables are different each time. I would like to know if there is any randomness within the NERPM process, especially within the DaySim model?'''<br />
<br />
When run using the exact same set of inputs, DaySim will produce the exact same set of outputs. DaySim has a random seed setting that is used to seed the drawing of random numbers throughout the simulation. Assuming this is the same, then DaySim will choose the same series of random numbers for each HH, person and choice model. Sometimes users see differences because the work and school destination choice shadow prices are updated between runs, which changes the relative attractiveness of destinations. <br />
<br />
'''When I added some roadway improvement, some shifting in work location that were not quite related to the roadway improvement was observed. The number of trips destined for certain TAZs increased drastically. Is the work location choice process constrained by the number of employments in each parcel? If one parcel has an employment of 100, is it possible that more than 100 workers choose that parcel as their work location?''' <br />
<br />
The work and school location choice models are shadow priced, which means the chosen work and school locations are compared to the employment and enrollment by zone, a difference ratio is calculated, an additional shadow price (or cost) is added to each over-assigned zone, and then the process repeated until converged. Destination choice shadow pricing is like auto-calibrating workers to jobs (and students to enrollment) by zone. The relationship is not a hard constraint, i.e. it is possible for the workers that choose a zone to exceed the applicable employment. It’s a good idea to instead look at a zone’s regional share of the relevant worker types to the relevant employment. <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 . 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 ([http://northfloridatpo.com/images/uploads/wiki/prepare_workspace.py prepare_workspace.py]) 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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=391Support/Training2017-09-06T16:36:13Z<p>Mvpennington: </p>
<hr />
<div>For support, please first check "[[Frequently Asked Questions]]."<br />
<br />
*[[Media:NERPMAB1v3_Update_Overview_Amended_9_4_2017.pdf|NERPMAB1v3_Update_Overview_Amended_9_4_2017.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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:NERPMAB1v3_Update_Overview_Amended_9_4_2017.pdf&diff=390File:NERPMAB1v3 Update Overview Amended 9 4 2017.pdf2017-09-06T16:32:54Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3897.2 Version NERPMAB1v32017-09-06T15:47:08Z<p>Mvpennington: </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 Loaded Network Comparison Application Tool<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 />
'''Loaded Network Comparison Application'''<br />
<br />
The Loaded Network Comparison tool was added as an application in the User Interface. 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 Loaded Network Comparison tool. The tool creates an output file named NetComp_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 NetComp_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 />
<br />
[[File:NERPM fields - bottom of 7.2.jpg]]</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3887.2 Version NERPMAB1v32017-09-06T15:44:13Z<p>Mvpennington: </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 Loaded Network Comparison Application Tool<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 />
<br />
[[File:NERPM fields - bottom of 7.2.jpg]]</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3877.2 Version NERPMAB1v32017-05-31T19:13:57Z<p>Mvpennington: </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 Trip 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 />
<br />
[[File:NERPM fields - bottom of 7.2.jpg]]</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=386Frequently Asked Questions2017-05-31T19:12:36Z<p>Mvpennington: </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 . 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 ([http://northfloridatpo.com/images/uploads/wiki/prepare_workspace.py prepare_workspace.py]) 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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=383Frequently Asked Questions2017-05-31T18:50:58Z<p>Mvpennington: </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. 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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=382Frequently Asked Questions2017-05-31T18:49:40Z<p>Mvpennington: </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. 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:</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=380Support/Training2017-04-06T12:31:47Z<p>Mvpennington: </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:NERPMABv2_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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=6.1_General_Overview&diff=3796.1 General Overview2017-04-04T18:04:01Z<p>Mvpennington: </p>
<hr />
<div><p><strong><em>Network Change</em></strong></p><p class="BodyParagraph">There are four networks officially part of the LRTP<br />
“2040 Path Forward” effort. These are for the years 2010, 2018 (E+C), 2030 and<br />
2040. Table 6.1 provides the user with information regarding the period of<br />
construction related to the planned roadway projects within the North Florida<br />
TPO’s area.</p><p></p><p><strong>Table 6-1 Path Forward 2040 Cost Feasible Plan Project List</strong></p><div class="table-wrap"><br />
{| class="wikitable" <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1027<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
218<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cosmos<br />
Avenue<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Pine<br />
Tree Lane<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
33<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR 220<br />
Doctors Inlet Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Knight<br />
Boxx Road (end of four lane)<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
114<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR<br />
16<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR 215<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
41<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
218<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1012<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
739<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1013<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at SR<br />
16<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
8202<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US<br />
17<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 4<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Clay<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 34<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR 220<br />
Doctors Inlet Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | College<br />
Drive<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
17<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
6 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Clay<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 106<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
218<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 15A<br />
Oakridge Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Clay<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 908<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
17<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Shands<br />
Bridge<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Clay<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 13<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Cheswick<br />
Oak Avenue Extension<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Oakleaf<br />
Plantation Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Savannah<br />
Glen Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 4 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Clay<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 1026<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
218<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US<br />
301<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Cosmos<br />
Avenue<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Clay/St.<br />
John's<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 8203<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 23<br />
First Coast Expressway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 17<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 6 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2021-2025<br />
|- <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1019<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 5th Street<br />
(McDuff Avenue Phase 3)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Melson<br />
Avenue<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Huron<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 2<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Alta<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Faye<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Burkit<br />
Lane<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 5<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 15<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pine<br />
Verde<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 930<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Shindler<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Rampart<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 932<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old<br />
Middleburg Road S<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Shindler<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 37<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Eastport<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 105<br />
Heckscher Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pulaski<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1021<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Florida<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Penman<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 49<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Hartley<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 13 San<br />
Jose Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old St.<br />
Augustine Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1022<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-95<br />
South<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 13 San<br />
Jose Boulevard (Buckman Bridge)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Add 2<br />
Express Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1023<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 202 J. T.<br />
Butler Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 9B<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Add 2<br />
Express Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 73<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Kernan<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 202 J. T.<br />
Butler Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Glen Kernan<br />
Parkway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 6<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 933<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Kernan<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | McCormick<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 6<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1015<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old<br />
Middleburg Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Argyle<br />
Forest Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 134 103rd<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 953<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pulaski<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Eastport<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 935<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Ramona<br />
Boulevard (Crystal Springs Road Phase 2)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Hammond<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Cahoon<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 5<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 934<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Ricker<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Morse<br />
Avenue<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old<br />
Middleburg Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1009<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | San Pablo<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | US 90 Beach<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 101<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Shindler<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 134 103rd<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 960<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 115<br />
Southside Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Gate<br />
Parkway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Hogan<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 957A<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 957B<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at SR 134<br />
103rd Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 957C<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at Cedar<br />
Hills Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 701<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 243 JIA<br />
North Access Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 102<br />
Airport Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pecan Park<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1024<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 9B<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Phillips<br />
Highway (US 1)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Add 2<br />
Auxiliary Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1016<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cahoon<br />
Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Lenox<br />
Avenue<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 90<br />
Beaver Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Reconstruct 2 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
972<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cecil<br />
Field Connector<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Commerce Center<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 2<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
971<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Chaffee Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 228<br />
Normandy Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Crystal Springs Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 5 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1020<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Clark<br />
Road Extension<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Broward Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Clark<br />
Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 3<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
121<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 113<br />
Southside Connector<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 202<br />
J. T. Butler Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Add 4<br />
Express Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
964<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at US<br />
17 Roosevelt Boulevard to Wells Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Modify<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
68<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Airport Road (SR 102) - Phase 2<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Modify<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
418A<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval/St. John's County Line<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Add 4<br />
Express Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
714<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Girvin Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
715<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Hodges Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
716<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at San<br />
Pablo Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
968<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 115<br />
Southside Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at SR<br />
10 Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | 9<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Wilson<br />
Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 6 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
701<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 243<br />
JIA North Access Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 102<br />
Airport Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Pecan<br />
Park Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
959<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 17<br />
Main Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Eastport Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1017<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 17<br />
Main Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Berlin Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Pecan<br />
Park Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
16<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 17<br />
Roosevelt Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Collins Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | 7<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 90<br />
Beaver Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cahoon<br />
Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | McDuff<br />
Avenue<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 1<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Alta<br />
Drive Realignment<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 105<br />
Zoo Parkway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | North of<br />
New Berlin Road (south)<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 4<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 406<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-10<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
301<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 23<br />
First Coast Expressway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Add 4<br />
Express Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 57<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-295<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 13<br />
San Jose Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | W of US<br />
17 Roosevelt Boulevard (Buckman Bridge)<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Add 4<br />
Express Lanes on Bridge<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 410<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-295<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 134<br />
103rd Street<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-10<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Add 4<br />
Express Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 419<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-95<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | at US<br />
1/SR 15 MLK<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Modify<br />
Interchange<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 962<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-95<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | at SR<br />
115 Southside Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Modify<br />
Interchange<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
1034<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New<br />
World Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 23<br />
First Coast Expressway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Chaffee<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 2<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 940<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 104<br />
Dunn Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 1 SR<br />
15 New Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-295<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 941<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 104<br />
Dunn Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Old<br />
Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 23<br />
New Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Intersection Improvements<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 102<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 115<br />
Southside Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 1/SR<br />
5 Philips Highway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | I-95<br />
Ramps<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
6 Lanes*<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 955<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Trout<br />
River Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Old<br />
Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 23<br />
New Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 2<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Alta Drive<br />
/ Yellow Bluff Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New Berlin<br />
Road (north)<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 432<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 454<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | at<br />
I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Modify<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 403<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau/Duval County Line<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US<br />
301<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 407<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95 North<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Dames<br />
Point Bridge/ SR 105 Heckscher Drive<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 408<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | North of<br />
Trout River<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95 North<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 409<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South of<br />
US 1 New Kings Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | North of<br />
Trout River<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 411<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South of<br />
US 1 New Kings Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 431<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 17<br />
Roosevelt Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 134<br />
103rd Street<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 433<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 434<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 1033<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | National<br />
Cemetery Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Lannie<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Arnold<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 2 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 948<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New Berlin<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Pulaski<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Yellow<br />
Bluff Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 949<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New Berlin<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Yellow<br />
Bluff Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Cedar<br />
Point Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 103<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 115<br />
Southside Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 90<br />
Beach Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 966<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 115<br />
Southside Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | at SR 202<br />
J. T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Modify<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 151<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
A1A<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 116<br />
Wonderwood Drive<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Naval<br />
Station Mayport North Gate<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 94<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1 SR 5<br />
Philips Highway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 9B<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1 SR 5<br />
Philips Highway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95 at<br />
the Avenues<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Nassau<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 708<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | US 301 SR<br />
200<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | US 1 S Kings<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Nassau<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
708<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 301<br />
SR 200<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 1 S<br />
Kings Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Nassau<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 703<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 200<br />
SR A1A<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Amelia<br />
Island Parkway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Sadler<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
6 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Nassau<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 707<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
17<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Nassau/Duval County Line<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Harts<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Intersection Improvements<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 704<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Amelia<br />
Island Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South 14th<br />
Street<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR 105A<br />
Buccaneer Trail<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes*<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 501<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Concourse<br />
Loop Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | License<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Amelia<br />
Concourse<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 2 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 705<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR 105A<br />
Buccaneer Trail<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South<br />
Fletcher Avenue<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Canopy<br />
Drive<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Turn Lane<br />
Improvements*<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 402<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Baker/Nassau County Line<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau/Duval County Line<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 981<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
200<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Fernandina<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Intersection Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 706<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
A1A<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South<br />
Fletcher Avenue<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Amelia<br />
Island Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Turn Lane<br />
Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 427<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR A1A SR<br />
200<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | at US<br />
17<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Intersection Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 708<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 301 SR<br />
200<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1 S<br />
Kings Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Intersection Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 810<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | CR 2209<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 23 First<br />
Coast Expressway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | CR 210<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | New 6 Lane<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1025<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Dixie<br />
Highway / Pellicer Lane<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | CR 214 King<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 207<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Reconstruct<br />
2 Lanes and Widen to add Sidewalks and Bike Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 835<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 16<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
International Golf Parkway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | South<br />
Francis Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 831<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 313<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 207<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 16<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | New 6 Lane<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1008<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR A1A<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at Red<br />
Cox/Coquina Rd<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
811<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
2209<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 16<br />
Connector<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 6<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
818<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
305<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
204<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR<br />
206<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 2<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
418B<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
International Golf Parkway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
John's/Duval County Line<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Add 4<br />
Express Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
828<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Race<br />
Track Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Bartram Park Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Bartram Springs<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
840<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
841<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
16 A<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
847<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
2209<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
845<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 1<br />
SR 5 Philips Highway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
210<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Modify<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 812<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
2209<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
International Golf Parkway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 16<br />
Connector<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 6<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 816<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
2209<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
208<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 4<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 832<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
313<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 1<br />
Dixie Highway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 4<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 800<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
A1A<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Mickler<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Palm<br />
Valley Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 813<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
2209<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
214<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
208<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 4 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 815<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
2209<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 16<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
International Golf Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 4 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 827<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Race Track<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St. Johns<br />
Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Bartram<br />
Park Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 827<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Race Track<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St. Johns<br />
Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Bartram<br />
Park Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 113<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
207<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South<br />
Holmes Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 115<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
312<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1/SR 5<br />
Dixie Highway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
A1A<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
<br />
<br />
<br />
<br />
|}</div><p></p><h4 id="id-6.1GENERALOVERVIEW-EmploymentChange"><em>Employment Change</em></h4><p class="BodyParagraph">In future, some areas may see growth/decline in employment due to increase/decrease in business establishments or some other reasons. In addition, the distribution of different employment types could change over the years.</p><p class="BodyParagraph">In order to reflect those changes in the model, the DaySim buffered parcel file needs to be updated - \Master\{SCENARIO_DIR}\<br />
Input\DaySimInput\02_Parcel\ Jacksonville_parcel_decayandCirc.dat.</p><p class="BodyParagraph">To update the file, two steps should be performed:</p><ul><li>If employment at a TAZ is same, including in different sectors, but distribution of employment in parcels within the TAZ have changed then either of the two should be undertaken:<br />
<ul><li>Edit the parcel file manually.</li><li>Get new block level controls (with employment in 2-digit NAICS categories)<br />
and run the allocation tool (see section 5.1 &#124;) to obtain an updated parcel file.</li></ul></li><li>If employment (or/and distribution of employment sectors) at a TAZ is different, the new TAZ file should be used to run the allocation tool (see section 5.1 &#124;). The tool will produce an updated parcel file.</li><li>The first step would create a new parcel file and an updated TAZ file, if necessary. The new parcel file should be provided as input to the buffering too (see section 5.1 &#124; )and generate a new buffered parcel file. This file should then be replaced in the DaySimInput folder.</li></ul><h4 id="id-6.1GENERALOVERVIEW-PopulationChange"><em>Population Change</em></h4><p class="BodyParagraph">After a base year population has been synthesized, new synthetic populations may need to be generated based on the type scenario being run or the policy being tested. For example, a change in the network may not require the population to be synthesized again. On the other hand, if a land-use policy variable is being tested which would result in significantly different patterns in the population and employment levels in the TAZs than in the base case, a new synthetic population would be have to be generated. The same would be the case for a future year run when the population mix or distribution of specific population characteristics may deviate from those in the base synthetic population. Population is likely to increase in future, however, it may not increase proportionately geographically. A change in employment may also alter the existing geographic distribution of the population. To accommodate a change in population following three input files need to be updated:</p><ul><li>Buffered parcel file (\Master\{SCENARIO_DIR}\Input\DaySimInput\02_Parcel\<br />
Jacksonville_parcel_decayandCirc.dat)</li><li>Household file<br />
(\Master\{SCENARIO_DIR}\Input\DaySimInput\03_Household\_jax_hrec.dat)</li><li>Person file<br />
(\Master\{SCENARIO_DIR}\Input\DaySimInput\04_Person\_jax_prec.dat)</li></ul><p class="BodyParagraph">To update the buffered parcel file, the similar steps<br />
as employment change accommodation needs to be performed. First, the parcel file (output of the allocation tool) is updated and then it is used in the buffering tool to generate a new buffered parcel file that goes into DaySim.</p><p class="BodyParagraph">Synthetic population data (household and person files) would also need updates. As previously described, the synthetic population is<br />
generated using PopGen. The marginal control files for population synthesis need to be updated to reflect the new control totals. After that synthetic population needs to be generated using the new input files (Please refer to PopGen guide for synthesis instructions).</p></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=5.2_DaySim_Input_Preparation_-_Using_Parcel_Editing_Tool&diff=3785.2 DaySim Input Preparation - Using Parcel Editing Tool2017-04-04T17:59:41Z<p>Mvpennington: </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>In the DaySim Input Generator toolbar, click on the “Parcel Edits Layer:”<br />
dropdown menu to pick the appropriate “Edit Parcels” layer. See Figure 5-25 above.</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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=6.1_General_Overview&diff=3776.1 General Overview2017-04-04T17:54:24Z<p>Mvpennington: </p>
<hr />
<div><p><strong><em>Network Change</em></strong></p><p class="BodyParagraph">There are four networks officially part of the LRTP<br />
“2040 Path Forward” effort. These are for the years 2010, 2018 (E+C), 2030 and<br />
2040. Table 6.1 provides the user with information regarding the period of<br />
construction related to the planned roadway projects within the North Florida<br />
TPO’s area.</p><p></p><p><strong>Table 6-1 Path Forward 2040 Cost Feasible Plan Project List</strong></p><div class="table-wrap"><br />
{| class="wikitable" <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1027<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
218<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cosmos<br />
Avenue<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Pine<br />
Tree Lane<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
33<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR 220<br />
Doctors Inlet Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Knight<br />
Boxx Road (end of four lane)<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
114<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR<br />
16<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR 215<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
41<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
218<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1012<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
739<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1013<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at SR<br />
16<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Clay<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
8202<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US<br />
17<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 4<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Clay<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 34<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR 220<br />
Doctors Inlet Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | College<br />
Drive<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
17<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
6 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Clay<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 106<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
218<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 15A<br />
Oakridge Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Clay<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 908<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
17<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Shands<br />
Bridge<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Clay<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 13<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Cheswick<br />
Oak Avenue Extension<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Oakleaf<br />
Plantation Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Savannah<br />
Glen Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 4 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Clay<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 1026<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
218<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US<br />
301<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Cosmos<br />
Avenue<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Clay/St.<br />
John's<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 8203<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 23<br />
First Coast Expressway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 17<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 6 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2021-2025<br />
|- <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1019<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 5th Street<br />
(McDuff Avenue Phase 3)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Melson<br />
Avenue<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Huron<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 2<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Alta<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Faye<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Burkit<br />
Lane<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 5<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 15<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pine<br />
Verde<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 930<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Shindler<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Rampart<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 932<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old<br />
Middleburg Road S<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Shindler<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 37<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Eastport<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 105<br />
Heckscher Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pulaski<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1021<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Florida<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Penman<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 49<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Hartley<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 13 San<br />
Jose Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old St.<br />
Augustine Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1022<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-95<br />
South<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 13 San<br />
Jose Boulevard (Buckman Bridge)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Add 2<br />
Express Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1023<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 202 J. T.<br />
Butler Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 9B<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Add 2<br />
Express Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 73<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Kernan<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 202 J. T.<br />
Butler Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Glen Kernan<br />
Parkway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 6<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 933<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Kernan<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | McCormick<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 6<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1015<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old<br />
Middleburg Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Argyle<br />
Forest Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 134 103rd<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 953<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pulaski<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Eastport<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 935<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Ramona<br />
Boulevard (Crystal Springs Road Phase 2)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Hammond<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Cahoon<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 5<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 934<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Ricker<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Morse<br />
Avenue<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Old<br />
Middleburg Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1009<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | San Pablo<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | US 90 Beach<br />
Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 101<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Shindler<br />
Drive<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 134 103rd<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 3<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 960<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 115<br />
Southside Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Gate<br />
Parkway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Hogan<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 957A<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at Collins<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 957B<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at SR 134<br />
103rd Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 957C<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at Cedar<br />
Hills Boulevard<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 701<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 243 JIA<br />
North Access Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 102<br />
Airport Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Pecan Park<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Duval<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1024<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 9B<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Phillips<br />
Highway (US 1)<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | I-295<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Add 2<br />
Auxiliary Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1016<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cahoon<br />
Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Lenox<br />
Avenue<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 90<br />
Beaver Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Reconstruct 2 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
972<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cecil<br />
Field Connector<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Commerce Center<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 2<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
971<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Chaffee Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 228<br />
Normandy Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Crystal Springs Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 5 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1020<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Clark<br />
Road Extension<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Broward Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Clark<br />
Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 3<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
121<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 113<br />
Southside Connector<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 202<br />
J. T. Butler Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Add 4<br />
Express Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
964<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at US<br />
17 Roosevelt Boulevard to Wells Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Modify<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
68<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Airport Road (SR 102) - Phase 2<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Modify<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
418A<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval/St. John's County Line<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Add 4<br />
Express Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
714<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Girvin Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
715<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Hodges Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
716<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at San<br />
Pablo Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
968<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 115<br />
Southside Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at SR<br />
10 Atlantic Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | 9<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 21<br />
Blanding Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-295<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Wilson<br />
Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 6 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
701<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 243<br />
JIA North Access Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 102<br />
Airport Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Pecan<br />
Park Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
959<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 17<br />
Main Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Eastport Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
1017<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 17<br />
Main Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Berlin Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Pecan<br />
Park Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
16<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 17<br />
Roosevelt Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
Collins Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Duval<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | 7<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 90<br />
Beaver Street<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Cahoon<br />
Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | McDuff<br />
Avenue<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 1<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Alta<br />
Drive Realignment<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 105<br />
Zoo Parkway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | North of<br />
New Berlin Road (south)<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 4<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 406<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-10<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
301<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 23<br />
First Coast Expressway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Add 4<br />
Express Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 57<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-295<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 13<br />
San Jose Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | W of US<br />
17 Roosevelt Boulevard (Buckman Bridge)<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Add 4<br />
Express Lanes on Bridge<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 410<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-295<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 134<br />
103rd Street<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-10<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Add 4<br />
Express Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 419<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-95<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | at US<br />
1/SR 15 MLK<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Modify<br />
Interchange<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 962<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-95<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | at SR<br />
115 Southside Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Modify<br />
Interchange<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
1034<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New<br />
World Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 23<br />
First Coast Expressway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Chaffee<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 2<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 940<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 104<br />
Dunn Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 1 SR<br />
15 New Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
I-295<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 941<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 104<br />
Dunn Avenue<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Old<br />
Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 23<br />
New Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Intersection Improvements<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 102<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 115<br />
Southside Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 1/SR<br />
5 Philips Highway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | I-95<br />
Ramps<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
6 Lanes*<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Duval<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 955<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Trout<br />
River Boulevard<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Old<br />
Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 23<br />
New Kings Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 2<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Alta Drive<br />
/ Yellow Bluff Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New Berlin<br />
Road (north)<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 432<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 454<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | at<br />
I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Modify<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 403<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau/Duval County Line<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US<br />
301<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 407<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95 North<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Dames<br />
Point Bridge/ SR 105 Heckscher Drive<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 408<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | North of<br />
Trout River<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95 North<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 409<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South of<br />
US 1 New Kings Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | North of<br />
Trout River<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 411<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South of<br />
US 1 New Kings Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 431<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 17<br />
Roosevelt Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 134<br />
103rd Street<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 433<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 10<br />
Atlantic Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 434<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 1033<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | National<br />
Cemetery Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Lannie<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Arnold<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 2 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 948<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New Berlin<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Pulaski<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Yellow<br />
Bluff Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 949<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New Berlin<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Yellow<br />
Bluff Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Cedar<br />
Point Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 103<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 115<br />
Southside Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 90<br />
Beach Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 966<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 115<br />
Southside Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | at SR 202<br />
J. T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Modify<br />
Interchange<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 151<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
A1A<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 116<br />
Wonderwood Drive<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Naval<br />
Station Mayport North Gate<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 94<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1 SR 5<br />
Philips Highway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 9B<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-295<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Duval<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1 SR 5<br />
Philips Highway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95 at<br />
the Avenues<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 202 J.<br />
T. Butler Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Nassau<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 708<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | US 301 SR<br />
200<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | US 1 S Kings<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Nassau<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
708<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 301<br />
SR 200<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 1 S<br />
Kings Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Intersection Improvements<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Nassau<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 703<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 200<br />
SR A1A<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Amelia<br />
Island Parkway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Sadler<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
6 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Nassau<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 707<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US<br />
17<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Nassau/Duval County Line<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Harts<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
Intersection Improvements<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 704<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Amelia<br />
Island Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South 14th<br />
Street<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR 105A<br />
Buccaneer Trail<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes*<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 501<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Concourse<br />
Loop Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | License<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Amelia<br />
Concourse<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 2 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 705<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR 105A<br />
Buccaneer Trail<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South<br />
Fletcher Avenue<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Canopy<br />
Drive<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Turn Lane<br />
Improvements*<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 402<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-10<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Baker/Nassau County Line<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau/Duval County Line<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Add 4<br />
Express Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 981<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
200<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Fernandina<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Intersection Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 706<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
A1A<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South<br />
Fletcher Avenue<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Amelia<br />
Island Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Turn Lane<br />
Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 427<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR A1A SR<br />
200<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | at US<br />
17<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Intersection Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Nassau<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 708<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 301 SR<br />
200<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1 S<br />
Kings Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
Intersection Improvements<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
! class="confluenceTh" | County<br />
! class="confluenceTh" | Map Id<br />
! class="confluenceTh" | Facility<br />
! class="confluenceTh" | From<br />
! class="confluenceTh" | To<br />
! class="confluenceTh" | Improvement Type<br />
! class="confluenceTh" | Construction Year Band<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 810<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | CR 2209<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 23 First<br />
Coast Expressway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | CR 210<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | New 6 Lane<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1025<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Dixie<br />
Highway / Pellicer Lane<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | CR 214 King<br />
Street<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 207<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Reconstruct<br />
2 Lanes and Widen to add Sidewalks and Bike Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 835<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 16<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
International Golf Parkway<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | South<br />
Francis Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Widen to 4<br />
Lanes<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 831<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 313<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 207<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR 16<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | New 6 Lane<br />
Road<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | St.<br />
Johns<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | 1008<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | SR A1A<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | at Red<br />
Cox/Coquina Rd<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | Intersection<br />
Improvements<br />
| class="highlight-red confluenceTd" data-highlight-colour="red" | <br />
2019-2020<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
811<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
2209<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 16<br />
Connector<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 6<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
818<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
305<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | CR<br />
204<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR<br />
206<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New 2<br />
Lane Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
418B<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
International Golf Parkway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
John's/Duval County Line<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Add 4<br />
Express Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
828<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Race<br />
Track Road<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Bartram Park Boulevard<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Bartram Springs<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Widen<br />
to 4 Lanes<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
840<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at<br />
I-95<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
841<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
16 A<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
847<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | SR 23<br />
First Coast Expressway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
2209<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | New<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | St.<br />
Johns<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
845<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | US 1<br />
SR 5 Philips Highway<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | at CR<br />
210<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | Modify<br />
Interchange<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
2021-2025<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 812<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
2209<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
International Golf Parkway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR 16<br />
Connector<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 6<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 816<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
2209<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | CR<br />
208<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 4<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 832<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
313<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
16<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | US 1<br />
Dixie Highway<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | New 4<br />
Lane Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | St.<br />
Johns<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | 800<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | SR<br />
A1A<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Mickler<br />
Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Palm<br />
Valley Road<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | Widen to<br />
4 Lanes<br />
| class="highlight-green confluenceTd" data-highlight-colour="green" | <br />
2026-2030<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 813<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
2209<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
214<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
208<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 4 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 815<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | CR<br />
2209<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR 16<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
International Golf Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | New 4 Lane<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 827<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Race Track<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St. Johns<br />
Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Bartram<br />
Park Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 827<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Race Track<br />
Road<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St. Johns<br />
Parkway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Bartram<br />
Park Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 4<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 113<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
207<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | I-95<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | South<br />
Holmes Boulevard<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | St.<br />
Johns<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | 115<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
312<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | US 1/SR 5<br />
Dixie Highway<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | SR<br />
A1A<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | Widen to 6<br />
Lanes<br />
| class="highlight-blue confluenceTd" data-highlight-colour="blue" | <br />
2031-2040<br />
|- <br />
<br />
<br />
<br />
<br />
|}</div><p></p><h4 id="id-6.1GENERALOVERVIEW-EmploymentChange"><em>Employment Change</em></h4><p class="BodyParagraph">In future, some areas may see growth/decline in employment due to increase/decrease in business establishments or some other reasons. In addition, the distribution of different employment types could change over the years.</p><p class="BodyParagraph">In order to reflect those changes in the model, the DaySim buffered parcel file needs to be updated - \Master\{SCENARIO_DIR}\<br />
Input\DaySimInput\02_Parcel\ Jacksonville_parcel_decayandCirc.dat.</p><p class="BodyParagraph">To update the file, two steps should be performed:</p><ul><li>If employment at a TAZ is same, including in different sectors, but<br />
distribution of employment in parcels within the TAZ have changed then either<br />
of the two should be undertaken:<br />
<ul><li>Edit the parcel file manually.</li><li>Get new block level controls (with employment in 2-digit NAICS categories)<br />
and run the allocation tool (see section 5.1 &#124;) to obtain an updated parcel<br />
file.</li></ul></li><li>If employment (or/and distribution of employment sectors) at a TAZ is<br />
different, the new TAZ file should be used to run the allocation tool (see<br />
section 5.1 &#124;). The tool will produce an updated parcel file.</li><li>The first step would create a new parcel file and an updated TAZ file, if<br />
necessary. The new parcel file should be provided as input to the buffering too<br />
(see section 5.1 &#124; ) and generate a new buffered parcel file. This file should<br />
then be replaced in the DaySimInput folder.</li></ul><h4 id="id-6.1GENERALOVERVIEW-PopulationChange"><em>Population Change</em></h4><p class="BodyParagraph">After a base year population has been synthesized, new<br />
synthetic populations may need to be generated based on the type scenario being<br />
run or the policy being tested. For example, a change in the network may not<br />
require the population to be synthesized again. On the other hand, if a<br />
land-use policy variable is being tested which would result in significantly<br />
different patterns in the population and employment levels in the TAZs than in<br />
the base case, a new synthetic population would be have to be generated. The<br />
same would be the case for a future year run when the population mix or<br />
distribution of specific population characteristics may deviate from those in<br />
the base synthetic population. Population is likely to increase in future,<br />
however, it may not increase proportionately geographically. A change in<br />
employment may also alter the existing geographic distribution of the<br />
population. To accommodate a change in population following three input files<br />
need to be updated:</p><ul><li>Buffered parcel file (\Master\{SCENARIO_DIR}\Input\DaySimInput\02_Parcel\<br />
Jacksonville_parcel_decayandCirc.dat)</li><li>Household file<br />
(\Master\{SCENARIO_DIR}\Input\DaySimInput\03_Household\_jax_hrec.dat)</li><li>Person file<br />
(\Master\{SCENARIO_DIR}\Input\DaySimInput\04_Person\_jax_prec.dat)</li></ul><p class="BodyParagraph">To update the buffered parcel file, the similar steps<br />
as employment change accommodation needs to be performed. First, the parcel<br />
file (output of the allocation tool) is updated and then it is used in the<br />
buffering tool to generate a new buffered parcel file that goes into<br />
DaySim.</p><p class="BodyParagraph">Synthetic population data (household and person files)<br />
would also need updates. As previously described, the synthetic population is<br />
generated using PopGen. The marginal control files for population synthesis<br />
need to be updated to reflect the new control totals. After that synthetic<br />
population needs to be generated using the new input files (Please refer to<br />
PopGen guide for synthesis instructions).</p></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3767.2 Version NERPMAB1v32017-04-04T17:42:12Z<p>Mvpennington: </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 Trip 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 />
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)<br />
<br />
<br />
[[File:NERPM fields - bottom of 7.2.jpg]]</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3757.2 Version NERPMAB1v32017-04-04T17:37:53Z<p>Mvpennington: import csv</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 Trip 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 />
New code statements:<br />
<br />
<br />
[[File:NERPM fields - bottom of 7.2.jpg]]</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=374Frequently Asked Questions2017-04-04T17:33:57Z<p>Mvpennington: </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.</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3737.2 Version NERPMAB1v32017-04-04T17:31:57Z<p>Mvpennington: </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 Trip 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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=3.2_All_Streets_Network_Preparation&diff=3723.2 All Streets Network Preparation2017-04-04T17:31:06Z<p>Mvpennington: </p>
<hr />
<div>[[Category:3.0 Model Design]]<br />
<br />
The NERPM-AB (activity-based) model uses parcels as the fundamental spatial unit for predicting travel demand. In order to support this more detailed geography, DaySim is designed to take advantage of more accurate distances for short distance on-street trips than are available from the TAZ-to-TAZ road network skims. These more accurate shortest-path node-to-node distances are calculated from an “All Streets Network” which is a network that (as the name indicates) that consists of all the streets in the model region. A typical model network would only consist of freeways, expressways, and major and minor arterials. This coarser network cannot accurately represent the accessibility between small geographies such as parcels.<br />
<br />
These short distance parcel-level impedances are most important for non-motorized trips such as bike and walk trips. Thus, facilities such as freeways and expressways, freeway ramps, and other facilities that are not available to non-motorized modes are excluded from the all-streets based network pathbuilding. In addition, short driveways (if present) are also typically dropped from the all-streets network in order to reduce the computation burden. The modified all streets network is then used to generate node-to-node shortest path distance as described in the next section.</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.1_Version_NERPMAB1v2&diff=3717.1 Version NERPMAB1v22017-04-04T17:29:46Z<p>Mvpennington: </p>
<hr />
<div>[[Category:7.0 Version Updates]]<br />
<br />
<p class="BodyParagraph">This section documents the improvements that were made<br />
to the NERPM-AB model since the adoption of the model as part as the “Path Forward<br />
2040” Long Range Transportation Plan. The improvements focused on improving its<br />
usability related to runtime, user’s catalog interface, and model usability</p><br />
<br />
<h3 id="id-7.1VERSIONNERPMAB1v2-Runtime">Runtime</h3><br />
<br />
<p>The investigation of alternative methods to reduce system run times focused<br />
on the highway network assignments and global feedback iterations. After<br />
investigating several different options for reducing runtime the following<br />
improvements were made:</p><br />
<br />
<h4 id="id-7.1VERSIONNERPMAB1v2-FeedbackLoops">Feedback Loops</h4><br />
<br />
<p>The transition of model outputs from one feedback loop to the next one and<br />
feedback loop termination criteria were adjusted in the new model. The model<br />
has been set up such that the weighted-average volume for each link is<br />
calculated at the end of each loop, based on the current and previous feedback<br />
loop flows. These averaged volumes are used to generate skims for the next<br />
iteration of the model system and are fed back to the demand models<br />
(DaySim).</p><br />
<br />
<p>In addition, rather than terminate based on a fixed number of iterations,<br />
the model has been set up to terminate the feedback loops if <em>both</em> of<br />
the following criteria are met:</p><br />
<br />
<ol><br />
<li>Change in total AM and PM VMT of two successive feedback loops is less than<br />
five percent</li><br />
<br />
<li>The AM and PM volumes of more than 95 percent of freeway and arterial links<br />
change less than five percent in two successive loops.</li><br />
</ol><br />
<br />
<p>The net effect of these changes are that the model runs one feedback loop<br />
less than the original model for the 2010 baseline scenario.</p><br />
<br />
<h4 id="id-7.1VERSIONNERPMAB1v2-HighwayTrafficAssignment">Highway Traffic<br />
Assignment</h4><br />
<br />
<p>The model is able to run midday and nighttime highway assignments in<br />
parallel. The user can assign computer logical processors to time periods by<br />
filling the corresponding keys added to the user interface. Figure 7-1, below,<br />
shows an example of the Cube catalog (last page of user interface page) for a<br />
computer with 8 logical processors. The AM and the PM assignments use all<br />
available logical processors, whereas the midday and nighttime assignments use<br />
different logical processors and can therefore run in parallel.</p><br />
<br />
<p>The model currently runs AM and PM assignments in sequence; however, it will<br />
be able to run them in parallel with minor changes in the model. In this case,<br />
the model should know which computer logical processor is the first one used<br />
for AM assignment (also which one is the first one for PM period). The<br />
interface has these two keys now and, since they are not run in parallel, the<br />
value for them should be <em>higher than number of computer logical<br />
processors</em>. The default value, therefore, was set to 25, which is suitable<br />
for any machine with up to 24 logical processors.</p><br />
<br />
<p><strong>Figure 7-1: Assigning computer logical processors to highway<br />
assignments by time period</strong><br />
</p><br />
<br />
[[File:Figure 7-1.png]]<br />
<br />
<h4 id="id-7.1VERSIONNERPMAB1v2-HighwayTrafficAssignmentParameters">Highway<br />
Traffic Assignment Parameters</h4><br />
<br />
<p>The assignment convergence criterion was changed to the accepted standard<br />
practice of relative gap. In addition, the maximum number of iterations was<br />
increased from 50 to 150, allowing for greater accuracy in the assignment<br />
process. The model is setup to use a tighter relative gap in the highway<br />
assignment after the first loop. Following best practice recommendations for<br />
regional highway assignments, it is recommended that this relative gap be set<br />
to 0.0001. The user may increase or decrease the relative gap, depending on the<br />
accuracy level required for the analysis under consideration. Figure 7-2 shows<br />
that the relative gap used <em>after</em> the first feedback loop was added to<br />
the interface as a key controlled by the user.</p><br />
<br />
<p><strong>Figure 7-2: Setting the relative gap used in highway assignment<br />
after the second feedback loop</strong><br />
</p><br />
<br />
[[File:Figure 7-2.png]]<br />
<br />
<br />
<h3 id="id-7.1VERSIONNERPMAB1v2-Post-ProcessAnalysis">Post-Process<br />
Analysis</h3><br />
<br />
<p>The Select link analysis is set to run <em>after</em> the feedback loop. The<br />
user selects the option to run a selected link analysis on typically the third<br />
page of the user interface, as shown in Figure 7-3. The select link analysis<br />
can be run for any of the time periods, including the daily assignment, by<br />
selecting the specific option. In order to run the daily select link option,<br />
all the time periods need to be run for the select link.</p><br />
<br />
<p>If the user wants to save the congested path files, they can choose the<br />
option to save the path file for a particular period. The paths are saved in an<br />
extra highway assignment run at the end of the model based on the final<br />
congested network. It should be noted that Cube Cluster does not support the<br />
use of multiple logical processors for path saving; therefore, this step takes<br />
a bit longer than would a normal assignment that can be distributed across<br />
processors.</p><br />
<br />
<p><strong>Figure 7-3: Keys used to define links for select link analysis and<br />
time periods for path saving</strong><br />
</p><br />
<br />
[[File:Figure 7-3a.png]]<br />
<br />
[[File:Figure 7-3b.png]]<br />
<br />
<br />
<p>Table 7-1 lists all the fields in the loaded network files. The two columns<br />
on the right lists the fields associated with the links which the user selected<br />
in the &quot;select link&quot; option shown in Figure 7-3. The yellow rows on<br />
the table are used in the calculation listed on the last row of the table and<br />
calculates the total link volume.</p><br />
<br />
<p><strong>Table 7-1 NERPAB1v2 Loaded highway network fields</strong><br />
</p><br />
<br />
<br />
<br />
{| class="wikitable" <br />
! class="confluenceTh" colspan="2" | NERPM AB LOADED NETWORK Fields<br />
! class="confluenceTh" colspan="2" | NERPM AB LOADED NETWORK Fields<br />
|- <br />
! class="confluenceTh" | New Variable<br />
! class="confluenceTh" | Description<br />
! class="confluenceTh" | New Variable<br />
! class="confluenceTh" | Description<br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
COUNT<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
Directional 2010 AADT count value, 0 if not available<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AMCOUNT<br />
| class="confluenceTd" | Directional 2010 AM count value, 0 if not<br />
available<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MDCOUNT<br />
| class="confluenceTd" | Directional 2010 MD count value, 0 if not<br />
available<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PMCOUNT<br />
| class="confluenceTd" | Directional 2010 PM count value, 0 if not<br />
available<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NTCOUNT<br />
| class="confluenceTd" | Directional 2010 NT count value, 0 if not<br />
available<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | SCREENLINE_YR10<br />
| class="confluenceTd" | Screenline number for year 2010<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NT_VL_TOT_10A<br />
| class="confluenceTd" | Night offpeak time total volume for year 2010 and<br />
scenario &quot;A&quot;<br />
| class="confluenceTd" | NTSL_VL_TOT_10A<br />
| class="confluenceTd" | Selected Link Night offpeak time total volume for year<br />
2010 and scenario &quot;A&quot;<br />
|- <br />
| class="confluenceTd" | NT_VL_DA_10A<br />
| class="confluenceTd" | Night offpeak DA-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
| class="confluenceTd" | NTSL_VL_DA_10A<br />
| class="confluenceTd" | Selected Link Night offpeak<br />
DA-Free&amp;Toll-II&amp;IE+EE traffic<br />
|- <br />
| class="confluenceTd" | NT_F_DA_10A<br />
| class="confluenceTd" | Night offpeak DA-II&amp;IE-Free traffic<br />
| class="confluenceTd" | NTSL_F_DA_10A<br />
| class="confluenceTd" | Selected Link Night offpeak DA-II&amp;IE-Free<br />
traffic<br />
|- <br />
| class="confluenceTd" | NT_T_DA_10A<br />
| class="confluenceTd" | Night offpeak DA-II&amp;IE-Toll<br />
| class="confluenceTd" | NTSL_T_DA_10A<br />
| class="confluenceTd" | Selected Link Night offpeak DA-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | NT_F_EDA_10A<br />
| class="confluenceTd" | Night offpeak DA-EE-Free<br />
| class="confluenceTd" | NTSL_F_EDA_10A<br />
| class="confluenceTd" | Selected Link Night offpeak DA-EE-Free<br />
|- <br />
| class="confluenceTd" | NT_T_EDA_10A<br />
| class="confluenceTd" | Night offpeak DA-EE-Toll<br />
| class="confluenceTd" | NTSL_T_EDA_10A<br />
| class="confluenceTd" | Selected Link Night offpeak DA-EE-Toll<br />
|- <br />
| class="confluenceTd" | NT_VL_SR2_10A<br />
| class="confluenceTd" | Night offpeak SR2-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
| class="confluenceTd" | NTSL_VL_SR2_10A<br />
| class="confluenceTd" | Selected Link Night offpeak<br />
SR2-Free&amp;Toll-II&amp;IE+EE traffic<br />
|- <br />
| class="confluenceTd" | NT_F_SR2_10A<br />
| class="confluenceTd" | Night offpeak SR2-II&amp;IE-Free<br />
| class="confluenceTd" | NTSL_F_SR2_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR2-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | NT_T_SR2_10A<br />
| class="confluenceTd" | Night offpeak SR2-II&amp;IE-Toll<br />
| class="confluenceTd" | NTSL_T_SR2_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR2-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | NT_F_ESR2_10A<br />
| class="confluenceTd" | Night offpeak SR2-EE-Free<br />
| class="confluenceTd" | NTSL_F_ESR2_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR2-EE-Free<br />
|- <br />
| class="confluenceTd" | NT_T_ESR2_10A<br />
| class="confluenceTd" | Night offpeak SR2-EE-Toll<br />
| class="confluenceTd" | NTSL_T_ESR2_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR2-EE-Toll<br />
|- <br />
| class="confluenceTd" | NT_VL_SR3_10A<br />
| class="confluenceTd" | Night offpeak SR3-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
| class="confluenceTd" | NTSL_VL_SR3_10A<br />
| class="confluenceTd" | Selected Link Night offpeak<br />
SR3-Free&amp;Toll-II&amp;IE+EE traffic<br />
|- <br />
| class="confluenceTd" | NT_F_SR3_10A<br />
| class="confluenceTd" | Night offpeak SR3-II&amp;IE-Free<br />
| class="confluenceTd" | NTSL_F_SR3_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR3-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | NT_T_SR3_10A<br />
| class="confluenceTd" | Night offpeak SR3-II&amp;IE-Toll<br />
| class="confluenceTd" | NTSL_T_SR3_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR3-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | NT_F_ESR3_10A<br />
| class="confluenceTd" | Night offpeak SR3-EE-Free<br />
| class="confluenceTd" | NTSL_F_ESR3_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR3-EE-Free<br />
|- <br />
| class="confluenceTd" | NT_T_ESR3_10A<br />
| class="confluenceTd" | Night offpeak SR3-EE-Toll<br />
| class="confluenceTd" | NTSL_T_ESR3_10A<br />
| class="confluenceTd" | Selected Link Night offpeak SR3-EE-Toll<br />
|- <br />
| class="confluenceTd" | NT_VL_TRK_10A<br />
| class="confluenceTd" | Night offpeak Truck-II&amp;IE+EE+Port<br />
| class="confluenceTd" | NTSL_VL_TRK_10A<br />
| class="confluenceTd" | Selected Link Night offpeak<br />
Truck-II&amp;IE+EE+Port<br />
|- <br />
| class="confluenceTd" | NT_VL_PRTTK_10A<br />
| class="confluenceTd" | Night offpeak Port-Truck<br />
| class="confluenceTd" | NTSL_VL_PRTTK_10A<br />
| class="confluenceTd" | Selected Link Night offpeak Port-Truck<br />
|- <br />
| class="confluenceTd" | NT_VL_EXT_10A<br />
| class="confluenceTd" | Night offpeak EXT-TRK +<br />
EE-Free&amp;Toll(DA+SR2+SR3)<br />
| class="confluenceTd" | NTSL_VL_EXT_10A<br />
| class="confluenceTd" | Selected Link Night offpeak EXT-TRK +<br />
EE-Free&amp;Toll(DA+SR2+SR3)<br />
|- <br />
| class="confluenceTd" | NT_VC_10A<br />
| class="confluenceTd" | Night offpeak V/C Ratio<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NT_CGSPEED_10A<br />
| class="confluenceTd" | Night offpeak average congested speed<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NT_VMT_10A<br />
| class="confluenceTd" | Night offpeak VMT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NT_VHT_10A<br />
| class="confluenceTd" | Night offpeak VHT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NT_CGTIME_10A<br />
| class="confluenceTd" | Night offpeak congested travel time<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NT_FLGCGSPDZERO<br />
| class="confluenceTd" | Night offpeak congested speed is 0 indicator, 1 if<br />
speed is 0<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | NT_VCCAPRTO_10A<br />
| class="confluenceTd" | Night offpeak V/C Ratio (same as VC_10A)<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PM_VL_TOT_10A<br />
| class="confluenceTd" | PM peak time total volume for year 2010 and scenario<br />
&quot;A&quot;<br />
| class="confluenceTd" | PMSL_VL_TOT_10A<br />
| class="confluenceTd" | Selected Link PM peak time total volume for year 2010<br />
and scenario &quot;A&quot;<br />
|- <br />
| class="confluenceTd" | PM_VL_DA_10A<br />
| class="confluenceTd" | PM peak DA-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | PMSL_VL_DA_10A<br />
| class="confluenceTd" | Selected Link PM peak DA-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | PM_F_DA_10A<br />
| class="confluenceTd" | PM peak DA-II&amp;IE-Free traffic<br />
| class="confluenceTd" | PMSL_F_DA_10A<br />
| class="confluenceTd" | Selected Link PM peak DA-II&amp;IE-Free traffic<br />
|- <br />
| class="confluenceTd" | PM_T_DA_10A<br />
| class="confluenceTd" | PM peak DA-II&amp;IE-Toll<br />
| class="confluenceTd" | PMSL_T_DA_10A<br />
| class="confluenceTd" | Selected Link PM peak DA-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | PM_F_EDA_10A<br />
| class="confluenceTd" | PM peak DA-EE-Free<br />
| class="confluenceTd" | PMSL_F_EDA_10A<br />
| class="confluenceTd" | Selected Link PM peak DA-EE-Free<br />
|- <br />
| class="confluenceTd" | PM_T_EDA_10A<br />
| class="confluenceTd" | PM peak DA-EE-Toll<br />
| class="confluenceTd" | PMSL_T_EDA_10A<br />
| class="confluenceTd" | Selected Link PM peak DA-EE-Toll<br />
|- <br />
| class="confluenceTd" | PM_VL_SR2_10A<br />
| class="confluenceTd" | PM peak SR2-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | PMSL_VL_SR2_10A<br />
| class="confluenceTd" | Selected Link PM peak SR2-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | PM_F_SR2_10A<br />
| class="confluenceTd" | PM peak SR2-II&amp;IE-Free<br />
| class="confluenceTd" | PMSL_F_SR2_10A<br />
| class="confluenceTd" | Selected Link PM peak SR2-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | PM_T_SR2_10A<br />
| class="confluenceTd" | PM peak SR2-II&amp;IE-Toll<br />
| class="confluenceTd" | PMSL_T_SR2_10A<br />
| class="confluenceTd" | Selected Link PM peak SR2-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | PM_F_ESR2_10A<br />
| class="confluenceTd" | PM peak SR2-EE-Free<br />
| class="confluenceTd" | PMSL_F_ESR2_10A<br />
| class="confluenceTd" | Selected Link PM peak SR2-EE-Free<br />
|- <br />
| class="confluenceTd" | PM_T_ESR2_10A<br />
| class="confluenceTd" | PM peak SR2-EE-Toll<br />
| class="confluenceTd" | PMSL_T_ESR2_10A<br />
| class="confluenceTd" | Selected Link PM peak SR2-EE-Toll<br />
|- <br />
| class="confluenceTd" | PM_VL_SR3_10A<br />
| class="confluenceTd" | PM peak SR3-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | PMSL_VL_SR3_10A<br />
| class="confluenceTd" | Selected Link PM peak SR3-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | PM_F_SR3_10A<br />
| class="confluenceTd" | PM peak SR3-II&amp;IE-Free<br />
| class="confluenceTd" | PMSL_F_SR3_10A<br />
| class="confluenceTd" | Selected Link PM peak SR3-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | PM_T_SR3_10A<br />
| class="confluenceTd" | PM peak SR3-II&amp;IE-Toll<br />
| class="confluenceTd" | PMSL_T_SR3_10A<br />
| class="confluenceTd" | Selected Link PM peak SR3-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | PM_F_ESR3_10A<br />
| class="confluenceTd" | PM peak SR3-EE-Free<br />
| class="confluenceTd" | PMSL_F_ESR3_10A<br />
| class="confluenceTd" | Selected Link PM peak SR3-EE-Free<br />
|- <br />
| class="confluenceTd" | PM_T_ESR3_10A<br />
| class="confluenceTd" | PM peak SR3-EE-Toll<br />
| class="confluenceTd" | PMSL_T_ESR3_10A<br />
| class="confluenceTd" | Selected Link PM peak SR3-EE-Toll<br />
|- <br />
| class="confluenceTd" | PM_VL_TRK_10A<br />
| class="confluenceTd" | PM peak Truck-II&amp;IE+EE+Port<br />
| class="confluenceTd" | PMSL_VL_TRK_10A<br />
| class="confluenceTd" | Selected Link PM peak Truck-II&amp;IE+EE+Port<br />
|- <br />
| class="confluenceTd" | PM_VL_PRTTK_10A<br />
| class="confluenceTd" | PM peak Port-Truck<br />
| class="confluenceTd" | PMSL_VL_PRTTK_10A<br />
| class="confluenceTd" | Selected Link PM peak Port-Truck<br />
|- <br />
| class="confluenceTd" | PM_VL_EXT_10A<br />
| class="confluenceTd" | PM peak EXT-TRK + EE-Free&amp;Toll(DA+SR2+SR3)<br />
| class="confluenceTd" | PMSL_VL_EXT_10A<br />
| class="confluenceTd" | Selected Link PM peak EXT-TRK +<br />
EE-Free&amp;Toll(DA+SR2+SR3)<br />
|- <br />
| class="confluenceTd" | PM_VC_10A<br />
| class="confluenceTd" | PM peak V/C Ratio<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PM_CGSPEED_10A<br />
| class="confluenceTd" | PM peak average congested speed<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PM_VMT_10A<br />
| class="confluenceTd" | PM peak VMT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PM_VHT_10A<br />
| class="confluenceTd" | PM peak VHT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PM_CGTIME_10A<br />
| class="confluenceTd" | PM peak congested travel time<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PM_FLGCGSPDZERO<br />
| class="confluenceTd" | PM peak congested speed is 0 indicator, 1 if speed is<br />
0<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | PM_VCCAPRTO_10A<br />
| class="confluenceTd" | PM peak V/C Ratio (same as VC_10A)<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MD_VL_TOT_10A<br />
| class="confluenceTd" | MD offpeak time total volume for year 2010 and<br />
scenario &quot;A&quot;<br />
| class="confluenceTd" | MDSL_VL_TOT_10A<br />
| class="confluenceTd" | Selected Link MD offpeak time total volume for year<br />
2010 and scenario &quot;A&quot;<br />
|- <br />
| class="confluenceTd" | MD_VL_DA_10A<br />
| class="confluenceTd" | MD offpeak DA-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | MDSL_VL_DA_10A<br />
| class="confluenceTd" | Selected Link MD offpeak DA-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | MD_F_DA_10A<br />
| class="confluenceTd" | MD offpeak DA-II&amp;IE-Free traffic<br />
| class="confluenceTd" | MDSL_F_DA_10A<br />
| class="confluenceTd" | Selected Link MD offpeak DA-II&amp;IE-Free<br />
traffic<br />
|- <br />
| class="confluenceTd" | MD_T_DA_10A<br />
| class="confluenceTd" | MD offpeak DA-II&amp;IE-Toll<br />
| class="confluenceTd" | MDSL_T_DA_10A<br />
| class="confluenceTd" | Selected Link MD offpeak DA-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | MD_F_EDA_10A<br />
| class="confluenceTd" | MD offpeak DA-EE-Free<br />
| class="confluenceTd" | MDSL_F_EDA_10A<br />
| class="confluenceTd" | Selected Link MD offpeak DA-EE-Free<br />
|- <br />
| class="confluenceTd" | MD_T_EDA_10A<br />
| class="confluenceTd" | MD offpeak DA-EE-Toll<br />
| class="confluenceTd" | MDSL_T_EDA_10A<br />
| class="confluenceTd" | Selected Link MD offpeak DA-EE-Toll<br />
|- <br />
| class="confluenceTd" | MD_VL_SR2_10A<br />
| class="confluenceTd" | MD offpeak SR2-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | MDSL_VL_SR2_10A<br />
| class="confluenceTd" | Selected Link MD offpeak<br />
SR2-Free&amp;Toll-II&amp;IE+EE traffic<br />
|- <br />
| class="confluenceTd" | MD_F_SR2_10A<br />
| class="confluenceTd" | MD offpeak SR2-II&amp;IE-Free<br />
| class="confluenceTd" | MDSL_F_SR2_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR2-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | MD_T_SR2_10A<br />
| class="confluenceTd" | MD offpeak SR2-II&amp;IE-Toll<br />
| class="confluenceTd" | MDSL_T_SR2_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR2-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | MD_F_ESR2_10A<br />
| class="confluenceTd" | MD offpeak SR2-EE-Free<br />
| class="confluenceTd" | MDSL_F_ESR2_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR2-EE-Free<br />
|- <br />
| class="confluenceTd" | MD_T_ESR2_10A<br />
| class="confluenceTd" | MD offpeak SR2-EE-Toll<br />
| class="confluenceTd" | MDSL_T_ESR2_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR2-EE-Toll<br />
|- <br />
| class="confluenceTd" | MD_VL_SR3_10A<br />
| class="confluenceTd" | MD offpeak SR3-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | MDSL_VL_SR3_10A<br />
| class="confluenceTd" | Selected Link MD offpeak<br />
SR3-Free&amp;Toll-II&amp;IE+EE traffic<br />
|- <br />
| class="confluenceTd" | MD_F_SR3_10A<br />
| class="confluenceTd" | MD offpeak SR3-II&amp;IE-Free<br />
| class="confluenceTd" | MDSL_F_SR3_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR3-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | MD_T_SR3_10A<br />
| class="confluenceTd" | MD offpeak SR3-II&amp;IE-Toll<br />
| class="confluenceTd" | MDSL_T_SR3_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR3-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | MD_F_ESR3_10A<br />
| class="confluenceTd" | MD offpeak SR3-EE-Free<br />
| class="confluenceTd" | MDSL_F_ESR3_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR3-EE-Free<br />
|- <br />
| class="confluenceTd" | MD_T_ESR3_10A<br />
| class="confluenceTd" | MD offpeak SR3-EE-Toll<br />
| class="confluenceTd" | MDSL_T_ESR3_10A<br />
| class="confluenceTd" | Selected Link MD offpeak SR3-EE-Toll<br />
|- <br />
| class="confluenceTd" | MD_VL_TRK_10A<br />
| class="confluenceTd" | MD offpeak Truck-II&amp;IE+EE+Port<br />
| class="confluenceTd" | MDSL_VL_TRK_10A<br />
| class="confluenceTd" | Selected Link MD offpeak Truck-II&amp;IE+EE+Port<br />
|- <br />
| class="confluenceTd" | MD_VL_PRTTK_10A<br />
| class="confluenceTd" | MD offpeak Port-Truck<br />
| class="confluenceTd" | MDSL_VL_PRTTK_10A<br />
| class="confluenceTd" | Selected Link MD offpeak Port-Truck<br />
|- <br />
| class="confluenceTd" | MD_VL_EXT_10A<br />
| class="confluenceTd" | MD offpeak EXT-TRK + EE-Free&amp;Toll(DA+SR2+SR3)<br />
| class="confluenceTd" | MDSL_VL_EXT_10A<br />
| class="confluenceTd" | Selected Link MD offpeak EXT-TRK +<br />
EE-Free&amp;Toll(DA+SR2+SR3)<br />
|- <br />
| class="confluenceTd" | MD_VC_10A<br />
| class="confluenceTd" | MD offpeak V/C Ratio<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MD_CGSPEED_10A<br />
| class="confluenceTd" | MD offpeak average congested speed<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MD_VMT_10A<br />
| class="confluenceTd" | MD offpeak VMT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MD_VHT_10A<br />
| class="confluenceTd" | MD offpeak VHT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MD_CGTIME_10A<br />
| class="confluenceTd" | MD offpeak congested travel time<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MD_FLGCGSPDZERO<br />
| class="confluenceTd" | MD offpeak congested speed is 0 indicator, 1 if speed<br />
is 0<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | MD_VCCAPRTO_10A<br />
| class="confluenceTd" | MD offpeak V/C Ratio (same as VC_10A)<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
AM_VL_TOT_10A<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | AM<br />
peak time total volume for year 2010 and scenario &quot;A&quot;<br />
| class="confluenceTd" | AMSL_VL_TOT_10A<br />
| class="confluenceTd" | Selected Link AM peak time total volume for year 2010<br />
and scenario &quot;A&quot;<br />
|- <br />
| class="confluenceTd" | AM_VL_DA_10A<br />
| class="confluenceTd" | AM peak DA-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | AMSL_VL_DA_10A<br />
| class="confluenceTd" | Selected Link AM peak DA-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | AM_F_DA_10A<br />
| class="confluenceTd" | AM peak DA-II&amp;IE-Free traffic<br />
| class="confluenceTd" | AMSL_F_DA_10A<br />
| class="confluenceTd" | Selected Link AM peak DA-II&amp;IE-Free traffic<br />
|- <br />
| class="confluenceTd" | AM_T_DA_10A<br />
| class="confluenceTd" | AM peak DA-II&amp;IE-Toll<br />
| class="confluenceTd" | AMSL_T_DA_10A<br />
| class="confluenceTd" | Selected Link AM peak DA-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | AM_F_EDA_10A<br />
| class="confluenceTd" | AM peak DA-EE-Free<br />
| class="confluenceTd" | AMSL_F_EDA_10A<br />
| class="confluenceTd" | Selected Link AM peak DA-EE-Free<br />
|- <br />
| class="confluenceTd" | AM_T_EDA_10A<br />
| class="confluenceTd" | AM peak DA-EE-Toll<br />
| class="confluenceTd" | AMSL_T_EDA_10A<br />
| class="confluenceTd" | Selected Link AM peak DA-EE-Toll<br />
|- <br />
| class="confluenceTd" | AM_VL_SR2_10A<br />
| class="confluenceTd" | AM peak SR2-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | AMSL_VL_SR2_10A<br />
| class="confluenceTd" | Selected Link AM peak SR2-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | AM_F_SR2_10A<br />
| class="confluenceTd" | AM peak SR2-II&amp;IE-Free<br />
| class="confluenceTd" | AMSL_F_SR2_10A<br />
| class="confluenceTd" | Selected Link AM peak SR2-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | AM_T_SR2_10A<br />
| class="confluenceTd" | AM peak SR2-II&amp;IE-Toll<br />
| class="confluenceTd" | AMSL_T_SR2_10A<br />
| class="confluenceTd" | Selected Link AM peak SR2-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | AM_F_ESR2_10A<br />
| class="confluenceTd" | AM peak SR2-EE-Free<br />
| class="confluenceTd" | AMSL_F_ESR2_10A<br />
| class="confluenceTd" | Selected Link AM peak SR2-EE-Free<br />
|- <br />
| class="confluenceTd" | AM_T_ESR2_10A<br />
| class="confluenceTd" | AM peak SR2-EE-Toll<br />
| class="confluenceTd" | AMSL_T_ESR2_10A<br />
| class="confluenceTd" | Selected Link AM peak SR2-EE-Toll<br />
|- <br />
| class="confluenceTd" | AM_VL_SR3_10A<br />
| class="confluenceTd" | AM peak SR3-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | AMSL_VL_SR3_10A<br />
| class="confluenceTd" | Selected Link AM peak SR3-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | AM_F_SR3_10A<br />
| class="confluenceTd" | AM peak SR3-II&amp;IE-Free<br />
| class="confluenceTd" | AMSL_F_SR3_10A<br />
| class="confluenceTd" | Selected Link AM peak SR3-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | AM_T_SR3_10A<br />
| class="confluenceTd" | AM peak SR3-II&amp;IE-Toll<br />
| class="confluenceTd" | AMSL_T_SR3_10A<br />
| class="confluenceTd" | Selected Link AM peak SR3-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | AM_F_ESR3_10A<br />
| class="confluenceTd" | AM peak SR3-EE-Free<br />
| class="confluenceTd" | AMSL_F_ESR3_10A<br />
| class="confluenceTd" | Selected Link AM peak SR3-EE-Free<br />
|- <br />
| class="confluenceTd" | AM_T_ESR3_10A<br />
| class="confluenceTd" | AM peak SR3-EE-Toll<br />
| class="confluenceTd" | AMSL_T_ESR3_10A<br />
| class="confluenceTd" | Selected Link AM peak SR3-EE-Toll<br />
|- <br />
| class="confluenceTd" | AM_VL_TRK_10A<br />
| class="confluenceTd" | AM peak Truck-II&amp;IE+EE+Port<br />
| class="confluenceTd" | AMSL_VL_TRK_10A<br />
| class="confluenceTd" | Selected Link AM peak Truck-II&amp;IE+EE+Port<br />
|- <br />
| class="confluenceTd" | AM_VL_PRTTK_10A<br />
| class="confluenceTd" | AM peak Port-Truck<br />
| class="confluenceTd" | AMSL_VL_PRTTK_10A<br />
| class="confluenceTd" | Selected Link AM peak Port-Truck<br />
|- <br />
| class="confluenceTd" | AM_VL_EXT_10A<br />
| class="confluenceTd" | AM peak EXT-TRK + EE-Free&amp;Toll(DA+SR2+SR3)<br />
| class="confluenceTd" | AMSL_VL_EXT_10A<br />
| class="confluenceTd" | Selected Link AM peak EXT-TRK +<br />
EE-Free&amp;Toll(DA+SR2+SR3)<br />
|- <br />
| class="confluenceTd" | AM_VC_10A<br />
| class="confluenceTd" | AM peak V/C Ratio<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AM_CGSPEED_10A<br />
| class="confluenceTd" | AM peak average congested speed<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AM_VMT_10A<br />
| class="confluenceTd" | AM peak VMT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AM_VHT_10A<br />
| class="confluenceTd" | AM peak VHT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AM_CGTIME_10A<br />
| class="confluenceTd" | AM peak congested travel time<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AM_FLGCGSPDZERO<br />
| class="confluenceTd" | AM peak congested speed is 0 indicator, 1 if speed is<br />
0<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AM_VCCAPRTO_10A<br />
| class="confluenceTd" | AM peak V/C Ratio (same as VC_10A)<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AL_VL_TOT_1A<br />
| class="confluenceTd" | Daily time total volume for year 2010 and scenario<br />
&quot;A&quot;<br />
| class="confluenceTd" | ALSLSL_VL_TOT_1A<br />
| class="confluenceTd" | Selected Link Daily time total volume for year 2010<br />
and scenario &quot;A&quot;<br />
|- <br />
| class="confluenceTd" | AL_VL_DA_10A<br />
| class="confluenceTd" | Daily DA-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | ALSL_VL_DA_10A<br />
| class="confluenceTd" | Selected Link Daily DA-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | AL_F_DA_10A<br />
| class="confluenceTd" | Daily DA-II&amp;IE-Free traffic<br />
| class="confluenceTd" | ALSL_F_DA_10A<br />
| class="confluenceTd" | Selected Link Daily DA-II&amp;IE-Free traffic<br />
|- <br />
| class="confluenceTd" | AL_T_DA_10A<br />
| class="confluenceTd" | Daily DA-II&amp;IE-Toll<br />
| class="confluenceTd" | ALSL_T_DA_10A<br />
| class="confluenceTd" | Selected Link Daily DA-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | AL_F_EDA_10A<br />
| class="confluenceTd" | Daily DA-EE-Free<br />
| class="confluenceTd" | ALSL_F_EDA_10A<br />
| class="confluenceTd" | Selected Link Daily DA-EE-Free<br />
|- <br />
| class="confluenceTd" | AL_T_EDA_10A<br />
| class="confluenceTd" | Daily DA-EE-Toll<br />
| class="confluenceTd" | ALSL_T_EDA_10A<br />
| class="confluenceTd" | Selected Link Daily DA-EE-Toll<br />
|- <br />
| class="confluenceTd" | AL_VL_SR2_10A<br />
| class="confluenceTd" | Daily SR2-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | ALSL_VL_SR2_10A<br />
| class="confluenceTd" | Selected Link Daily SR2-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | AL_F_SR2_10A<br />
| class="confluenceTd" | Daily SR2-II&amp;IE-Free<br />
| class="confluenceTd" | ALSL_F_SR2_10A<br />
| class="confluenceTd" | Selected Link Daily SR2-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | AL_T_SR2_10A.<br />
| class="confluenceTd" | Daily SR2-II&amp;IE-Toll<br />
| class="confluenceTd" | ALSL_T_SR2_10A.<br />
| class="confluenceTd" | Selected Link Daily SR2-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | AL_F_ESR2_10A<br />
| class="confluenceTd" | Daily SR2-EE-Free<br />
| class="confluenceTd" | ALSL_F_ESR2_10A<br />
| class="confluenceTd" | Selected Link Daily SR2-EE-Free<br />
|- <br />
| class="confluenceTd" | AL_T_ESR2_10A<br />
| class="confluenceTd" | Daily SR2-EE-Toll<br />
| class="confluenceTd" | ALSL_T_ESR2_10A<br />
| class="confluenceTd" | Selected Link Daily SR2-EE-Toll<br />
|- <br />
| class="confluenceTd" | AL_VL_SR3_10A<br />
| class="confluenceTd" | Daily SR3-Free&amp;Toll-II&amp;IE+EE traffic<br />
| class="confluenceTd" | ALSL_VL_SR3_10A<br />
| class="confluenceTd" | Selected Link Daily SR3-Free&amp;Toll-II&amp;IE+EE<br />
traffic<br />
|- <br />
| class="confluenceTd" | AL_F_SR3_10A<br />
| class="confluenceTd" | Daily SR3-II&amp;IE-Free<br />
| class="confluenceTd" | ALSL_F_SR3_10A<br />
| class="confluenceTd" | Selected Link Daily SR3-II&amp;IE-Free<br />
|- <br />
| class="confluenceTd" | AL_T_SR3_10A<br />
| class="confluenceTd" | Daily SR3-II&amp;IE-Toll<br />
| class="confluenceTd" | ALSL_T_SR3_10A<br />
| class="confluenceTd" | Selected Link Daily SR3-II&amp;IE-Toll<br />
|- <br />
| class="confluenceTd" | AL_F_ESR3_10A<br />
| class="confluenceTd" | Daily SR3-EE-Free<br />
| class="confluenceTd" | ALSL_F_ESR3_10A<br />
| class="confluenceTd" | Selected Link Daily SR3-EE-Free<br />
|- <br />
| class="confluenceTd" | AL_T_ESR3_10A<br />
| class="confluenceTd" | Daily SR3-EE-Toll<br />
| class="confluenceTd" | ALSL_T_ESR3_10A<br />
| class="confluenceTd" | Selected Link Daily SR3-EE-Toll<br />
|- <br />
| class="confluenceTd" | AL_VL_TRK_10A<br />
| class="confluenceTd" | Daily Truck-II&amp;IE+EE+Port<br />
| class="confluenceTd" | ALSL_VL_TRK_10A<br />
| class="confluenceTd" | Selected Link Daily Truck-II&amp;IE+EE+Port<br />
|- <br />
| class="confluenceTd" | AL_VL_PRTTK_10A<br />
| class="confluenceTd" | Daily Port-Truck<br />
| class="confluenceTd" | ALSL_VL_PRTTK_10A<br />
| class="confluenceTd" | Selected Link Daily Port-Truck<br />
|- <br />
| class="confluenceTd" | AL_VL_EXT_10A<br />
| class="confluenceTd" | Daily EXT-TRK + EE-Free&amp;Toll(DA+SR2+SR3)<br />
| class="confluenceTd" | ALSL_VL_EXT_10A<br />
| class="confluenceTd" | Selected Link Daily EXT-TRK +<br />
EE-Free&amp;Toll(DA+SR2+SR3)<br />
|- <br />
| class="confluenceTd" | AL_VMT_10A<br />
| class="confluenceTd" | Daily VMT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AL_VHT_10A<br />
| class="confluenceTd" | Daily VHT<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AL_CGTIME_10A<br />
| class="confluenceTd" | Daily congested travel time, weighted average of four<br />
time period<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AL_CGSPEED_10A<br />
| class="confluenceTd" | Daily congested travel speed<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AL_VOLCNTRTO<br />
| class="confluenceTd" | Old measure (obsolete)<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="confluenceTd" | AL_VCCAPRTO_10A<br />
| class="confluenceTd" | Daily V/C Ratio<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|- <br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
TOTAL_VOLUME<br />
| class="highlight-yellow confluenceTd" data-highlight-colour="yellow" | <br />
AL_VL_TOT_1A+AL_VL_TOT_1A.R<br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
| class="highlight-grey confluenceTd" data-highlight-colour="grey" | <br />
|}<br />
<br />
<br />
<h3 id="id-7.1VERSIONNERPMAB1v2-RedundantSteps">Redundant Steps</h3><br />
<br />
<p>Several steps in the trip distribution part of the model are no longer<br />
needed.</p><br />
<br />
<p>Model operations previously used to combine trip tables are no longer<br />
necessary because DaySim uses its own set of procedures for creating trip<br />
tables from trip lists.</p><br />
<br />
<p>The pre-assignment step is now run only once, during the first feedback loop<br />
iteration. This is because the outputs from pre-assignment are used to build<br />
the transit network, which is only run during the first feedback loop<br />
iteration.</p><br />
<br />
<h3 id="id-7.1VERSIONNERPMAB1v2-CleanupCubeCatalogInterface">Clean up Cube<br />
Catalog Interface</h3><br />
<br />
<p>The validation base year key (Valyear) is not read by the model and was<br />
removed from the catalog interface. All other keys in the interface are<br />
needed.</p><br />
<br />
<h3 id="id-7.1VERSIONNERPMAB1v2-PerformanceImprovements">Performance<br />
Improvements</h3><br />
<br />
<p>Table 7-2 shows the run times based on a 2015 vintage workstation with 8<br />
logical processors before the changes were made and the run times after the<br />
changes, with various settings. Comparing the rows shaded in orange, the<br />
changes made to the model decreased the run time by more than 9 hours, a 44<br />
percent improvement, for the base year model (2010), using the stricter<br />
relative gap and without path saving and select link analysis. The run of the<br />
same model with select link analysis for AM and PM periods and saving path file<br />
for AM period ran for 16:27, using the stricter relative gap, which is<br />
reasonable.</p><br />
<br />
<p><strong>Table 7-2: Run time of the original and improved (V2) NERPMAB1v2<br />
models Using a workstation with 8 logical processors</strong><br />
</p><br />
<br />
[[File:Table 7-2.png]]<br />
<br />
<h3 id="id-7.1VERSIONNERPMAB1v2-NewandUpdatedScripts">New and Updated<br />
Scripts</h3><br />
<br />
<p>Several new scripts were created and/or updated to support the listed<br />
changes. Table 7-3 shows the four scripts that are updated in the NERPMAB1v2<br />
model, all corresponding to the highway assignments by time period. Table 7-4<br />
presents the new scripts in the NERPMAB1v2 model with a brief description for<br />
each.</p><br />
<br />
<p><strong>Table 7-3: Updated Scripts in the NERPMAB1v2 model</strong><br />
</p><br />
<br />
[[File:Table 7-3.png]]<br />
<br />
<p><strong>Table 7-4: New scripts in the NERPMAB1v2 model</strong><br />
</p><br />
<br />
[[File:Table 7-4.png]]</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=370Support/Training2017-04-04T17:28:36Z<p>Mvpennington: </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:NERPMABv2_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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Frequently_Asked_Questions&diff=369Frequently Asked Questions2017-04-04T17:23:36Z<p>Mvpennington: </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 Site 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.</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=368Support/Training2017-02-14T19:43:48Z<p>Mvpennington: </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:NERPMABv2_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=Jeanette.Berk@rsginc.com,Ameera.Sayeed@dot.state.fl.us Milton Locklear]]Milton Locklear<br />
<br />
Thank you!</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:NERPMABv3_Update_Overview_Webinar_Slides.pdf&diff=346File:NERPMABv3 Update Overview Webinar Slides.pdf2017-02-13T21:49:30Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=345Support/Training2017-02-13T21:46:20Z<p>Mvpennington: </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 />
*NERPM AB1v3 Update Overview Webinar Slides <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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:NERPMAB1v2_Webinar_Excercise_Revised.pdf&diff=344File:NERPMAB1v2 Webinar Excercise Revised.pdf2017-02-13T21:43:55Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Example_exercise&diff=343Example exercise2017-02-13T21:40:33Z<p>Mvpennington: Created page with "'''Example Exercise with NERPM AB1v2''' The actual user interface for the exercise is approximately 2 hours. The whole exercise will take approximately 24 hours to complete..."</p>
<hr />
<div>'''Example Exercise with NERPM AB1v2''' <br />
<br />
The actual user interface for the exercise is approximately 2 hours. The whole exercise will take approximately 24 hours to complete (depending on the hardware). The majority of this time will be computer running time.<br />
<br />
If you run into problems or have questions, please visit http://northfloridatpo.com/modelwiki/ or, send an email to Milton Locklear at mlocklear@northfloridatpo.com. <br />
<br />
Exercise</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Daysiminput_02_Employment-parcel.jpg&diff=342File:Daysiminput 02 Employment-parcel.jpg2017-02-03T19:21:14Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Daysiminput_04_Person.jpg&diff=341File:Daysiminput 04 Person.jpg2017-02-03T19:20:37Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Daysiminput_03_Household.jpg&diff=340File:Daysiminput 03 Household.jpg2017-02-03T19:20:07Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Daysiminput_02_Parcel.jpg&diff=339File:Daysiminput 02 Parcel.jpg2017-02-03T19:19:28Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-25rev.jpg&diff=338File:Figure 5-25rev.jpg2017-02-03T19:17:24Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-24rev.jpg&diff=337File:Figure 5-24rev.jpg2017-02-03T19:16:59Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-23rev.jpg&diff=336File:Figure 5-23rev.jpg2017-02-03T19:16:19Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-22rev.jpg&diff=335File:Figure 5-22rev.jpg2017-02-03T19:15:48Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-21rev.jpg&diff=334File:Figure 5-21rev.jpg2017-02-03T19:15:23Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-19rev.jpg&diff=333File:Figure 5-19rev.jpg2017-02-03T19:14:58Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-18rev.jpg&diff=332File:Figure 5-18rev.jpg2017-02-03T19:14:29Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-17rev.jpg&diff=331File:Figure 5-17rev.jpg2017-02-03T19:13:54Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-16rev.jpg&diff=330File:Figure 5-16rev.jpg2017-02-03T19:13:05Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-15rev.jpg&diff=329File:Figure 5-15rev.jpg2017-02-03T19:12:32Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-14rev.jpg&diff=328File:Figure 5-14rev.jpg2017-02-03T19:11:20Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:Figure_5-13_rev.jpg&diff=327File:Figure 5-13 rev.jpg2017-02-03T19:09:47Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=326Support/Training2017-02-03T18:47:08Z<p>Mvpennington: </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 />
*NERPM AB1v3 Update Overview webinar slides <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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:NERPMAB1v3_Update_Overview_Final.pdf&diff=325File:NERPMAB1v3 Update Overview Final.pdf2017-02-03T18:46:17Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:NERPM_fields_-_bottom_of_7.2.jpg&diff=324File:NERPM fields - bottom of 7.2.jpg2017-02-03T18:43:56Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=323Support/Training2017-02-03T18:42:27Z<p>Mvpennington: </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 />
*NERPM AB1v3 webinar <br />
*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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=File:NERPMAB1v2_Webinar_Excercise_Revised_(2).pdf&diff=322File:NERPMAB1v2 Webinar Excercise Revised (2).pdf2017-02-03T18:40:17Z<p>Mvpennington: </p>
<hr />
<div></div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=Support/Training&diff=321Support/Training2017-02-03T18:39:15Z<p>Mvpennington: </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 />
*NERPM AB1v3 webinar <br />
*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>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3207.2 Version NERPMAB1v32017-02-03T18:36:55Z<p>Mvpennington: </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:Example.jpg]]</div>Mvpenningtonhttp://visummodelwiki.northfloridatpo.com/index.php?title=7.2_Version_NERPMAB1v3&diff=3197.2 Version NERPMAB1v32017-02-03T17:46:09Z<p>Mvpennington: </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 />
<br />
• development of interim years 2025 and 2035<br />
<br />
• addition of a Site Impact Analysis application<br />
<br />
• ability to run one-time period in the Highway Assignment<br />
<br />
• simplification of the use of the statewide freight model step<br />
<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 />
<br />
• TAZ 527: Added centroid connector (cc) to US 1 Philips Hwy and removed cc to I-95<br />
<br />
• I-95 and San Diego Rd (74353): Removed I-95 access from and to San Diego Road<br />
<br />
• I-95 and Kings Ave (Nodes 40557-40468-411131): Allowed access to I-95 from Kings Ave<br />
<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:Example.jpg]]</div>Mvpennington