The purpose of this page is to identify changes to the latest version of the CFRPM 7 model.
All updates and changes to CFRPM are listed here, in descending order by date. In cases where model files were changed, they are listed for download and use.
CFRPM 7 has a new versioning system for updates, with new nomenclature as well.
Version numbers use a 7.####### format, with the first digit indicating a major update number in sequential order, starting with 0. The remaining six digits indicate the update release date, using a 2-digit year, 2-digit month and 2-digit day format (i.e. 210228 for February 28, 2021).
A major update will use trailing zeros after the first digit. Subsequent related minor updates will have the release date after the first digit. For example, 7.1000000 would be the first major release after 7.0000000. A subsequent minor update to 7.1000000 would be 7.1230127, indicating a January 27, 2023 release date.
Model Files & Geodatabase Updates
CFRPM six (6) has separate update paths for the model files and input geodatabase, meaning that they are and can be updated independently of one another.
Updates to model files, depending on the nature, will be done via a major or minor update and distributed accordingly. Please see the Updates page for detailed information.
Updates to the geodatabase will be done to update the model networks as needed and distributed accordingly.
This site will be the ultimate source for update information. Update logs will be provided with the model file package, outlining changes with each version of the model files and/or geodatabase.
|Change Log File
|Official release of CFRPM 7
Version 7.00 Overview
CFRPM 7 represents a significant change from previous versions of CFRPM. This version has been completely re-scripted to remove legacy code developed for FSUTMS-Tranplan software but maintained in Cube-Voyager software. A number of legacy scripts have been merged together for faster processing. FSUTMS-Tranplan software allowed only one matrix operation per script, and similar scripts were developed during CFRPM’s conversion to Cube-Tranplan and then Cube-Voyager in the late 2000s. Also, CFRPM 7 now uses floating-point formats for all matrices. Previous versions used either integer formatted matrices or a mix of floating-point and integer formats.
CFRPM 7 has a 2015 Base Year and 2045 Horizon Year, with additional scenarios provided for each interim 5-year period in-between.
Zone & Network System
For the first time in its history, CFRPM uses a highway network and a zone structure developed consistently across the entire District. Whereas previous editions of CFRPM merged county- and MPO-networks and zone structures, this consistent network and zone structure will reduce the inconsistencies across the individual counties. The new highway network is spatially correct, making it easier to present results with other data in GIS format (specifically a geodatabase). The zone structure is more refined than previous editions. The number of zones has grown by one-third, from 4,700 to 7,100 zones, producing more refined traffic assignment results.
The trip generation module has been developed using 2017 NHTS data. This is the first update of the generation routines in over a decade, and the first time they have ever been updated districtwide. County- or area-level differences in trip generation equations have been removed to improve consistency throughout the model.
The trip distribution module has been calibrated districtwide for the first time. Previous CFRPM versions relied on calibrations conducted at the county- or MPO-levels, resulting in noticeable inconsistencies in travel patterns.
The transit modeling routines have been shifted offline to a companion transit model that uses the Federal Transit Administration’s Simplified Trips on Project Software (STOPS). The transit trips from the District Five Districtwide STOPS model are copied offline to CFRPM 7. These trips are deducted from the person trip table before the highway assignment phase. Therefore, CFRPM 7’s streamlined structure makes it easier for users to analyze individual model steps.
CFRPM 7 includes a revamped air passenger module for the Orlando International Airport (OIA). The model was originally developed for the SunRail Connector to the Airport in 2015 using an Origin/Destination survey and extensive count data.
The toll methodology has been updated to reflect the widespread use of electronic transponders and Open Road Tolling. The legacy Toll Facilities Model, which estimated delays due to traditional toll plazas, has been removed to streamline equilibrium assignment computations. The toll rates have been updated to reflect current toll rates.
- Updated scripts: CFRPM 7 Select Zone Scripts. These scripts have been revised to reflect volumes for both directions (in and out) of the selected zone.
- For clarification, the external traffic counts used by CFRPM 7 are in AADT, not in PSWADT. If users want to make the external traffic counts in PSWADT, PSWADT can be developed by multiplying the AADT volumes with the seasonal factors on the external links. The EE/EI EE trip tables would need to be adjusted for each scenario year to match the PSWADT on external links. In keeping with standard practice, users should review the seasonal and MOCF factors developed on all external station links since the counties are outside of the D5 region
- Updated script: CFRPM_LoadedNetworkToGDB.py. This script creates the loaded network for each scenario. It has been revised to rename the loaded network field names. Previously, only the field aliases were renamed; this corrects this to ensure that the field names are the same as the aliases.
- Updated scripts for daily volumes. The daily volume/daily capacity ratio equation was updated, in order to provide users with some base ratios. CFRPM 7 does not have daily capacities because it is a Time-of-Day model, so the updated equation is an estimation. They are close to previous daily capacities from CFRPM 6.1.
- Confirmation of New Users
- Due to inundation of spam bots posting spam articles on the CFRPM Wiki, we have implemented a mechanism for new users who create accounts. They will now have to be confirmed by a Wiki administrator. This will be done on a daily basis, and all legitimate users should be confirmed and able to post and edit by the next business day. We apologize for the inconvenience.
CFRPM Is Transitioning to Caliper TransCAD
District 5 has made the decision to select Caliper TransCAD as the new software platform for CFRPM. Read more about it here.