Socioeconomic Data

January 2004

SOCIOECONOMIC PRE-PROCESSOR (FRATAR)

Network Geography Turn Penalties

Socioeconomic Data with Bivariate Distributions

Attribute Lookup Tables

NETWORK INITIALIZATION

TRIP GENERATION

Production and Attraction Rates Special Generators

Roadway Network

ALLOCATION MODELS

Terminal Penalties

ROADWAY PATHBUILDING

Person Trip Productions & Attractions

SPEED FEEDBACK MODULE

Roadway Impedance, Time and Distance Skims

TRIP DISTRIBUTION

Friction Factors K Factors

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

Zone to Zone Person Trips

Bicycle and Pedestrian Parameters Transit Networks

NON-MOTORIZED MODE SPLIT

USER GUIDE

Zone to Zone Non-Motorized Person Trips

TRANSIT PATHBUILDING

Zone to Zone Motorized Person Trips

Transit Impedance, Time and Distance Skims

MODE CHOICE
Zone to Zone Vehicle Trips Zone to Zone Transit Trips

MOTORIZED MODE SPLIT

Auto Occupancy Factors Transit Factors

Zone to Zone Transit Trips

TRANSIT ASSIGNMENT

TIME OF DAY PA TO OD CONVERSION

External-External Vehicle Trips

Zone to Zone Vehicle Trips in OD Format, by Period Transit Boardings and Line Volumes Input

LEGEND

MODEL
Output Loaded Speeds Toggle Switch

TIME OF DAY TRAFFIC ASSIGNMENT

System Performance

Traffic Volumes

TABLE OF CONTENTS
Installing the Model........................................................................................................................................................................................................................................................................ 1 Copy the Program Files ............................................................................................................................................................................................................................................................ 1 Create a Customized Windows Shortcut ........................................................................................................................................................................................................................... 1 Install the TransCAD Add-In ................................................................................................................................................................................................................................................... 1 Copy the Model Input Files..................................................................................................................................................................................................................................................... 1 Running the Model ......................................................................................................................................................................................................................................................................... 3 Starting the Model ..................................................................................................................................................................................................................................................................... 3 Creating a Scenario.................................................................................................................................................................................................................................................................... 3 Maintaining and Running Scenarios ................................................................................................................................................................................................................................... 3 Viewing the Model Results........................................................................................................................................................................................................................................................... 5 Performance Report .................................................................................................................................................................................................................................................................. 5 Editing the Model Inputs .............................................................................................................................................................................................................................................................. 7 Making a Change (Excel Files)................................................................................................................................................................................................................................................ 7 Roadway Networks.................................................................................................................................................................................................................................................................... 8 Preparing The Model for Future Scenarios...........................................................................................................................................................................................................................11 Additional Functions....................................................................................................................................................................................................................................................................13 Mobile6 For Conformity Utility............................................................................................................................................................................................................................................13 Mode Choice ..............................................................................................................................................................................................................................................................................13 NCHRP 255 Adjustments .......................................................................................................................................................................................................................................................13 Level of Service Capacities and Analysis..........................................................................................................................................................................................................................15 Resource Code................................................................................................................................................................................................................................................................................18 Navigation...................................................................................................................................................................................................................................................................................18 Recompiling the Model..........................................................................................................................................................................................................................................................18

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

TABLE OF CONTENTS
TABLES Table 1 Available Tables and Their Contents .........................................................................................................................................................................................................................5 Table 2 Information Contained in Each Field of the Flow Tables....................................................................................................................................................................................6 Table 3 Primary Input Tables........................................................................................................................................................................................................................................................7 Table 4 Additional input files .......................................................................................................................................................................................................................................................8 Table 5 Network Link Fields..........................................................................................................................................................................................................................................................8 Table 6 Network Node Fields .......................................................................................................................................................................................................................................................9 Table 7 Changes for Future Year Scenarios.......................................................................................................................................................................................................................... 11 Table 8a Growth Factor Criteria ............................................................................................................................................................................................................................................... 14 Table 8b Error Factor Criteria .................................................................................................................................................................................................................................................... 14 Table 9 Additional Network Link Fields for NCHRP........................................................................................................................................................................................................... 15 Table 10 Level of Service Capacities ....................................................................................................................................................................................................................................... 16 Table 11 Upper Limit V/C Cutpoints....................................................................................................................................................................................................................................... 16

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

ii

INSTALLING THE MODEL INSTALLING THE MODEL

The NFR MPO Travel Demand Model requires TransCAD version 4.5. Before attempting to install the model, the user should ensure that this version of TransCAD is properly installed. For the easiest installation, it is recommended that TransCAD be installed in the default location of C:\Program Files\TransCAD; however, installation to another location is acceptable. Two installation methods are presented below. Under method 1, the travel model will be readily available whenever TransCAD is started from the provided windows shortcut. If method 2 is used, the NFR MPO Travel Demand Model will need to be activated manually each time TransCAD is started. If TransCAD is installed in a location other than the default (e.g. on the D:\ drive) or there are multiple versions installed on your system, modify the shortcut properties to correctly reference the TransCAD program file and startup directory. THE

I NSTALL

T RANS CAD A DD -I N

(METHOD 2)
Use the TransCAD menu system to open the Add-Ins dialog box. It can be found under Tools->Add-Ins Click the Setup Button Click the Add Button Be sure that Macro is selected (as opposed to Dialog Box) In the Description and Name fields, type NFR Model Menu In the UI Database field, type NFRMPO\nfrmenu_ui.dbd Each time TransCAD is started, the NFR MPO Travel Demand Model can only be run after the following steps are taken: o Go to Tools: Add-Ins from the TransCAD menu o Double click on the item called NFR Model Menu THE

C OPY

THE

P ROGRAM F ILES

(BOTH METHODS)
Browse to the folder where TransCAD is installed. Create a folder called NFRMPO inside of the program folder Copy all of the files in the Add-Ins\NFRMPO folder from the CD to the NFRMPO folder on your hard drive A

C OPY C REATE C USTOMIZED W INDOWS S HORTCUT

(METHOD 1)
Copy the TransCAD 4.5 NFR Model shortcut from the Add-Ins folder on the model CD and place it on the desktop or another convenient location. If TransCAD is installed in the default location, this shortcut should work without any modifications.

M ODEL I NPUT F ILES

Once the model has been installed, model networks and input tables can be copied from the CD. The folder titled NFR Model contains the input files required to run the NFR MPO Travel Demand Model, as well as a completed model run for the 2000 validation scenario. These files can be copied to any location on your PC, but it is preferable to run the model from a local drive. Once these files have been copied, the NFR MPO Travel Demand Model is ready to be run.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

INSTALLING THE MODEL

MODEL FILENAMES AND FOLDER STRUCTURE
To minimize the difficulty of setting up model runs, the input and output files should be stored in a fashion similar to that provided on the CD. Use of the default filenames will prevent the need to individually locate files each time a scenario is created. While just about any filenames and folder structure can be used, it is recommended that the folder structure be kept similar to that provided on the CD. As more input files are created for different alternatives, the model file structure will grow and change. Various input and output folders can be used with additional subfolders and filenames to test different sets of model input data.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

RUNNING THE MODEL RUNNING THE MODEL

The NFR MPO Travel Demand Model is run by interacting with a series of menus and dialog boxes. The process consists of starting the main model dialog box, creating model scenarios, and running the model. By following the directions in this section, the user should be able to run the validation year model that is included on the CD. In the Stages list, click on each stage and verify that all input files exist. If all files are missing, verify that the input directory was correctly selected. If only some files are missing, double-click on the filename and browse to the correct file. In the description field, enter a few words about the scenario (optional). If mode choice is to be run, check the Enable Mode Choice for this Scenario option. Refer to the mode choice chapter in the model documentation for details on running mode choice. Click on OK to accept and save the settings. AND

S TARTING

THE

M ODEL

The model can be started from the TransCAD menu, under NFR Travel Model: Model Dialog Box. If the NFR Travel Model menu is not present, please ensure that the installation steps were followed correctly. If installation method 2 was used, you will need to enable the NFR Travel Model menu using the Add-ins dialog box.

M AINTAINING

R UNNING S CENARIOS

C REATING

S CENARIO

The dialog box titled Scenario Toolbox contains a list of the model scenarios. Each scenario is created by the user and defines a set of input and output files for a specific model run. Different scenarios can be used to run the model using different networks, different socioeconomic data, or with a change to any of the input files. Scenarios can be selected, added, deleted, and edited by double-clicking an entry in the Scenario Toolbox. The dialog box titled NFR MPO Travel Demand Model is used to run the model, create performance reports, and run utilities. If an action cannot be taken on the selected scenario, the corresponding button will be disabled. Buttons may not, however, be disabled if multiple scenarios are selected. Model steps can only be run if all required input files are present and the previous step has already been run.

When the model is started for the first time, a new scenario will be created automatically. Information about this scenario must be entered before the model can be run. Use the Scenario Editor to enter the scenario name, input and output directories, and to define input and output filenames. Typically, most input and output filenames can be left at their defaults.

EXAMPLE 1: CREATING THE BASE YEAR SCENARIO DIALOG BOX SECTIONS

For Scenario Name, enter 2000 Base Year. For Input Directory, browse to the folder called 00Inputs, which was copied from the CD during installation. For Output Directory, use Windows Explorer to create a new folder in the OUTPUT directory that was copied from the CD. Browse to this new folder from the Scenario Editor. Scenario Information: o Output directory: Displays the output directory for the selected scenario. o Scenario description: Displays the description of the selected scenario.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

RUNNING THE MODEL

Model Step Checkboxes: o Stop after each step: Causes the model to run one step at a time if selected. This option must be selected unless all input files are present for each model step. o Create report when done: Causes a performance report to be created upon completion of the final model step. This option is not available if Stop after each step is selected. Model Step Buttons: o 1 Prepare Networks: Use this button to initialize the TransCAD network files for use by the model. o 2 Trip generation: Generates trips in PA format for each TAZ based on socioeconomic inputs. o 3 Trip Distribution: builds shortest paths and skims between each zone and distributes trips based on these skims. o 4 Mode Models: Separates bike, walk, carpool, and transit trips from auto-driver trips. o 5 Traffic Assignment: Assigns vehicle trips to the roadway network. Also assigns transit trips if the Fort Collins Mode Choice Model is enabled. o 6 Post Processing: Combines multiple period assignment results and calculates additional data such as Level of Service and Emissions. Reports: o Create Performance Report: Creates a report for the selected scenario o Create Maps: Creates volume/count maps in the output directory. Utilities: o Update Transit dbd: This utility will update a geographic file (*.dbd) that is being edited to create a transit network. It also creates a network (*.net) related to the geographic file. o Mobile6 for conformity: This runs a Mobile6 conformity analysis that is consistent with the process used by the Colorado Air Pollution Control Division (APCD). o The remainder of this space is reserved for future use. Additional functions can be added by modifying the GISDK script.

EXAMPLE 2: RUNNING THE BASE YEAR SCENARIO

Select the scenario created in Example 1. Remove the check from the Stop after Each Step checkbox. If the checkbox is disabled, use the scenario editor to check that all input files exist. Check the Create report when done checkbox. A new dialog will appear. To create a full performance report, simply click OK. Click on the button to run step 1. Steps 2 through 8 will run as well. The base year model run is now complete. If desired, maps and Mobile6 conformity reports can be created.

R U N N I NG M U L T I P LE S CEN A RIOS
To run multiple scenarios in batch mode, simply select more than one scenario in the Scenario Toolbox. Before starting, individually check each scenario for the desired options. If multiple scenarios are selected, buttons and checkboxes may not be disabled, even if one or more scenarios cannot be run in full. As with single scenarios, steps can be run individually or in sequence, and performance reports can be created automatically.

R U N N I NG A L L - O R -N O T H I N G A S S I G N M E N T
To run the model with All-or-Nothing assignment instead of using the standard method, check the Use AON Assignment option. With this option checked, the model can be run in full. All model procedures can be run with the AON option enabled, however results must be interpreted carefully. For example, output speeds and air quality information has little meaning when all-or-nothing assignment has been run.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

VIEWING THE MODEL RESULTS VIEWING THE MODEL RESULTS

Once a model scenario has been successfully run, the resulting data can be viewed interactively from within TransCAD or as a performance report from any text editor.

TABLES
In order to avoid writing to the input geographic file, (*.dbd) link-specific model output is stored in separate tables in the scenario output directory. Each table contains a filed called ID1 which can be used to join the table with the network geographic file (*.dbd). Table 1 describes the available tables and their contents. Table 2 describes the information contained in each field of the flow tables. Table 1 Available Tables and Their Contents Default Name Ini_LinkData.bin FlowAM.bin FlowMD.bin FlowPM.bin FlowOP.bin Flow.bin HrFlows.bin Contents Link characteristics, such as speed, capacity, and volume-delay parameters. This table contains information that is retrieved from an input lookup table or calculated directly based on input variables. Morning peak-period model outputs Mid-day peak-period model outputs Afternoon peak-period model outputs Off-peak model outputs Daily summary of model outputs Data disaggregated by half-hour period for use in Mobile6 air quality modeling

P ERFORMANCE R EPORT
The performance report provides aggregate summaries of model results, along with information about the inputs to a specific scenario. Each section of the performance report is intended to be self-explanatory. Certain reports summarize data separately by time of day, jurisdiction, or air quality non-attainment area. By default, the performance report is created in the output directory with the name Summary.txt. The report can be viewed in any text editor, such as Notepad, or can be opened using word processing software. The performance report can be printed landscape on 8.5 x 11 paper. Before printing the report, ensure that the last line on the first page contains the phrase, This is the last line on the first page. It may be necessary to adjust margins or font sizes before printing the report.

MAPS
Maps showing volumes in thousands, volume bandwidths, and Level of Service can automatically be created using the included Create Maps utility. Custom maps can be created by adjusting the label and theme settings on the volume/count maps. By default, these maps are saved in the output directory for each scenario.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

VIEWING THE MODEL RESULTS

Table 2 Information Contained in Each Field of the Flow Tables
Field ID1 *_Flow *_Time *_Speed CSPEED *_voc VMT CVHT FVHT CSPDVMT FSPDVMT LOS_TOT LOS_VOL LOS_CAP LOS_VC LOS_NUM Contents Period Table Unique link number matching ID in the network geographic (*.dbd) file Peak period flow VMT-weighted period travel time from speed postprocessor (min) VMT-weighted period speed from speed post-processor N/A V/C ratio for the peak hour within the specified time period Period vehicle miles traveled Period vehicle hours traveled (using congested speeds) Period vehicle hours traveled (using free-flow speeds) Period speed multiplied by period VMT (using congested speeds) Period speed multiplied by period VMT (using free-flow speeds) N/A N/A N/A N/A N/A Contents Daily Table Unique link number matching ID in the network geographic (*.dbd) file Daily traffic volume N/A N/A VMT weighted daily congested speed N/A Daily vehicle miles traveled Sum of period CVHT Sum of period FVHT Sum of period CSPDVMT Sum of period FSPDVMT 2-way Peak-hour level of service volume+ Peak directional peak-hour level of service volume+ Peak-hour directional level of service capacity Peak-hour level of service V/C ratio Number representing level of service score Field LOS CO NOX VOC lbl lbl2 Priority Contents Period Table N/A Period emissions of Carbon Monoxide (Link-based analysis) Period emissions of Nitrogen Oxides (Link-based analysis) Period emissions of Volatile Organic Compounds (Linkbased analysis) N/A N/A N/A Contents Daily Table Estimated Peak-hour level of service Daily emissions of Carbon Monoxide (Link-based analysis) Daily emissions of Nitrogen Oxides (Link-based analysis) Daily emissions of Volatile Organic Compounds (Linkbased analysis) Label field: volume and count in thousands Label field: volume in thousands Labeling priority expression

* denotes bi-directional field + see level of service section for a definition of the level of service peak-hour.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

EDITING THE MODEL INPUTS EDITING THE MODEL INPUTS

Most inputs to the NFR MPO Travel Demand model are stored in the Input Tables directory provided on the model CD. Inputs are provided in a spreadsheet format that is often easier to edit than native TransCAD files. However, they must be exported to DBASE (*.dbf) format to be used in the model. Input tables are provided in DBASE format in the 00inputs folder on the model CD. In addition to the input parameters contained in the Excel files described in Table 3, some parameters are contained in secondary input tables, TransCAD native files, or within the resource code. Secondary input tables are listed in Table 4, and contain data used for post-processing. A K-factors matrix is included as the file KFAC.mtx. Under the current calibration, K-factors are all set to 1.0. However, this file is required as a model input. All other parameters are contained with the GISDK code. See the section titled Resource Code for more information on identifying and adjusting these parameters. c. Choose DBF 4 (DBASE IV) from the Save as Type: dropdown menu; d. Choose a name and location for the file, and click Save; e. Click OK and Yes on any warning messages that appear; and f. Close the file. It is not necessary to save again. 6. Copy the exported table to your model input directory and use the scenario manager to reference the adjusted file. Table 3 Primary Input Tables Default Name 1a_LinkLookup.xls 1b_TurnPenalties.xls Contents Link speed, capacity, alpha, beta, alpha2, and beta2 by facility and area type. Also contains some mode-choice specific information. Turn penalty table. See special notes on start page. Household data by income and size, employment data by type, IE Production data, area type, university status, jurisdiction, and proximity to Denver (external stations only). All data by TAZ. If bivariate distributions of household data by income and size are available, they will be used. Otherwise, only marginals (totals) are required. Regional bivariate distribution of households by income and size (seed matrix for Fratar process). Production rates, Attraction rates, WBO production allocation rates, jurisdictional trip rate factors. Special generator data. See special notes on start page. Terminal times. Portion of trips that occur in the peak and offpeak times. By trip type.

M AKING

C HANGE (E XCEL F ILES )

Take the following steps to change a model input parameter. 1. Locate and open the correct Excel (.xls) spreadsheet in the Input Tables directory. It may be desirable to make a copy of the original file. 2. Read any information provided on the Start tab of the spreadsheet. 3. Make changes where directed on the Start tab, or if no information is provided, directly on the DBF tab of the spreadsheet. Note that in some cases, the DBF spreadsheet is linked to more conveniently formatted tables and should not be edited. 4. Save the spreadsheet. 5. Export the data on the DBF sheet to DBASE IV format: a. Select cell A1 on the DBF tab; b. Choose Save As from the File menu; 7

2a_SocioData.xls or 2a_SocioData_bv.xls

2b_HHseed.xls 2c_TripRates.xls 2d_SpecialGen.xls 3a_TerminalTimes.xls 3b_CongWeights.xls

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

EDITING THE MODEL INPUTS

Default Name 4a_WalkParams.xls 4b_BikeParams.xls 4c_TransitShares.xls 4d_AutoOccupancy.xls 5a_PeriodFactors.xls 5b_EEtrips.xls 5c_HourFactors.xls KFAC.mtx Contents Parameters for the distance-based walk mode split model. Parameters for the distance-based bike mode split model. Percent transit ridership by jurisdictional trip interchange. Auto occupancy by trip type. Directional time-of-day factors. External to External trip table. Peak-period to Peak-hour conversion table K-factors. The index ZONE is used to define the factor for each trip interchange. Table 4 Additional input files Default Name FwyEm00.dbf, ArtEm00.dbf, LocEm00.dbf, RmpEm00.dbf LOS_CAP.xls/dbf HourlyTraffic.xls/dbf Contents Mobile6 factors for a link-based analysis. The link based supplements the Mobile6 for Conformity module. These files were generated through analysis of multiple MOBILE6 output files. Level of service capacity lookup table Portion of daily trips made during each half hour. FT Table 5 Network Link Fields Link Field Name ID Length Dir Street Name Local Name Contents Unique record identifier. This can be joined with ID1 in many output data tables. Internally calculated link length in miles Indicates one-way or two-way street. 0 = 2-way 1 = 1-way in the AB direction -1 = 1-way in the BA direction Optional field indicating street name. Optional filed indicating second street name Value Facility Type 1 Freeway 2 Expressway 3 Major Arterial 4 Minor Arterial 5 Collector 6 Ramp 7 Frontage Road 8 Centroid Connector Value Area Type 1 Rural 2 Suburban 3 Urban 4 Fort Collins CBD 5 Other CBD Directional number of lanes (* indicates AB or BA) Indicates whether the link is on a screenline, and if so, which screenline. Indicates whether the link is in the Fort Collins (1) or Greeley (2) non-attainment area.

AT

R OADWAY N ETWORKS
Roadway networks are stored as TransCAD geographic files (*.dbd). The geographic file contains information about the number of lanes, facility type, and area type of each link, as well as additional information used to summarize results. Table 5 lists the fields contained in the roadway network, along with a short description of the fields contents. Link attributes such as speed and capacity are not stored on the geographic file, but rather in the link lookup table described previously. *_LANES NFR_SCRL NON-ATTAIN

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

EDITING THE MODEL INPUTS

Link Field Name Contents Value Jurisdiction 1 Fort Collins 2 Greeley 3 Loveland 4 Other/Rural Optional field indicating districts within the 4 jurisdictions. Traffic count factored to 2000 and used for validation. Traffic count provided by the City of Loveland and the year the count was taken. Traffic count provided by the City of Greeley and the year the count was taken. Traffic count provided by the City of Fort Collins and the year the count was taken. Traffic count provided by Weld County and the year the count was taken. Traffic count provided by Larimer County and the year the count was taken. Traffic count provided by CDOT and the year the count was taken. 2000 traffic count arrived at through analysis of raw count data Table 6 Network Node Fields Node Field Name ID Longitude, Latitude ZONE LOGIT Contents Unique node identifier. Coordinates of node. Traffic Analysis Zone number. This field matches the socioeconomic data table. Used for mode choice only, this flag indicates for which zones mode choice should be run.

JURIS_NO

DISTRICT NFR_CNT LOV_(CNT/Year) GRE_(CNT/Year) FC_(CNT/Year) WELD_(CNT/Year) LAR_(CNT/Year) CDOT_(CNT/Year) CDOT_Raw_Count

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

EDITING THE MODEL INPUTS

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

10

PREPARING THE MODEL FOR FUTURE SCENARIOS PREPARING THE MODEL FOR FUTURE SCENARIOS
Table 7 lists the changes that should be made to each input table before running a future year scenario. In addition to the changes listed below, be sure to use a roadway network that is representative of the forecast year. Table 7 Changes for Future Year Scenarios Input Table 1a_LinkLookup.xls 1b_TurnPenalties.xls 2a_SocioData.xls or 2a_SocioData_bv.xls 2b_HHseed.xls 2c_TripRates.xls 2d_SpecialGen.xls 3a_TerminalTimes.xls 3b_CongWeights.xls 4a_WalkParams.xls 4b_BikeParams.xls 4c_TransitShares.xls 4d_AutoOccupancy.xls 5a_PeriodFactors.xls 5b_EEtrips.xls 5c_HourFactors.xls Contents Use this table to feed output speeds back to distribution. This table should be verified and adjusted each time major network changes are made. Socioeconomic data, IE production data at external stations, and area type should be updated in this file. If bivariate distributions of households by income and size are available, use 2a_SocioData_bv.xls. No change required. No change required. Adjust to reflect forecast conditions No change required. No change required. No change required. No change required. No change required. No change required. No change required. Adjust to reflect forecast conditions No change required.

11

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

PREPARING THE MODEL FOR FUTURE SCENARIOS

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

12

ADDITIONAL FUNCTIONS ADDITIONAL FUNCTIONS

The NFR MPO Travel Model has the built-in capability to run a mode choice model and an air quality conformity process based on the EPAs Mobile6 emission model. The included mode choice model was developed for use by the City of Fort Collins in the Mason Street Corridor FTA New Starts application process. The Mobile6 conformity process was developed for the NFR MPO and is consistent in methodology with processes used by the Air Pollution Control Department (ACPD) at the Colorado Department of Health and Environment. Each of these functions can be accessed through the standard model dialog boxes. version 3.0 will be run. In order to run mode choice, the necessary input files must be created. These files include a route system (*.rts), transit networks (*.tnw), a geographic file containing walk and drive access links (*.dbd), a SUMMIT equivalency table (*.bin), and access and egress matrices (*.mtx). These files must be created according to the information provided in documentation for the Mason Street Multimodal Travel Model and the Fort Collins Multimodal Travel Model version 3.0. Due to changes in the TransCAD software and the NFR modeling process since the initial development of the mode choice model, the step-bystep instructions in the Mode Choice users guides cannot be followed directly. The creation of route systems, walk and drive access links, transit networks, and access/egress matrices remains similar. In order to create a TransCAD network (*.net) attached to the route system (*.rts) geographic file (*.dbd), the Update Transit dbd utility should be used. This utility updates link speeds and capacities while creating a TransCAD network attached to the selected geographic file.

M OBILE 6 F OR C ONFORMITY U TILITY

The Mobile6 for Conformity Utility is accessed from the main model dialog box. In order to run, it requires that all model steps, including post-processing, have been run successfully. When run, this process will create a folder called MOBILE6 within the scenario output directory. Mobile6 input and output files, as well as files converted for use with TransCAD, will be created in this directory and its subfolders. Each time the Mobile6 conformity utility is run, these directories will be purged. It is not recommended that any files be edited or saved directly in the Mobile6 output directories. The Mobile6 conformity utility will also create (or replace) two reports in the output directory for the selected scenario. These reports contain information that is likely to be needed in conformity submissions to the State APCD. The files, M6COLLINS.TXT and M6GREELEY.TXT contain information for the Fort Collins and Greeley non-attainment areas.

NCHRP 255 A DJUSTMENTS

Due to inherent errors that result from the aggregated model methodology, it is often useful to adjust future model volumes based observed data. The NFR MPO Travel Model includes a utility that performs such adjustments as described in the National Cooperative Highway Research Program report 255 (NCHRP 255). This utility applies the difference or average adjustment methods as described in the report. The adjustment methods used are summarized below.

M ODE C HOICE
An option to run mode choice is included in the scenario editor. When enabled, the Mode Choice model developed for the Mason Street Multimodal Travel Model and the Fort Collins Multimodal Travel Model

13

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

ADDITIONAL FUNCTIONS
Ratio Method: Table 8a: Growth Factor Criteria Growth Factor Base Year Count Method Used Use Difference Method Use Difference Method Use Average Method if Error Factor Criteria are met

BaseCount AdjustedVolume = ModelVolume BaseVolume

Difference Method:

>4 >3
3

1000 > 1000

Any

AdjustedVolume = ModelVolume + ( BaseCount BaseVolume)

Average Method: This method is an average of the results of the Ratio Method and the Difference Method. Where: ModelVolume: The raw modeled volume, to be adjusted using NCHRP procedures BaseCount: The base year traffic count BaseVolume: The base year raw modeled volume. When the base year model is to be adjusted, BaseVolume is identical to ModelVolume. AdjustedVolume: The volume after an NCHRP 255 adjustment has been applied Either the average method or the difference method is used to adjust model volumes. In some cases, use of the average method, which includes results from the ratio method, would result in unacceptably large adjustments. The ratio method is likely to produce unacceptable results when the growth factor or the error factor becomes large. The growth factor is computed as (ModelVolume / BaseVolume) and the error factor is computed as the larger of (BaseVolume / BaseCount) or (BaseCount / BaseVolume). Growth factor and error factor criteria are shown in Tables 8a and 8b respectively.

Error Factor

>4
>3

Table 8b: Error Factor Criteria Model Method Used Volume Use Difference Method 1000 > 1000 and Use Difference Method

>2
> 1 .5 1 .5

2000 > 2000 and 3000 > 3000

Use Difference Method Use Difference Method Use Average Method if Growth Factor Criteria are met

Any

To use the NCHRP 255 adjustment utility, the roadway network must contain information about base year volumes and counts. The required fields are described in Table 9. If one or more of these fields is missing, the NCHRP adjustment will not be performed, and the adjustment toggle switch will be unavailable.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

14

ADDITIONAL FUNCTIONS
Table 9 Additional Network Link Fields for NCHRP Link Field Name RSC RSC_Flow RSC_Count Contents Abbreviation for Regionally Significant Corridor. NCHRP adjustments will be run on links with a 1 in this field. Base year traffic volume. Data must be provided for each link where RSC=1. Base year traffic count. Data must be provided for each link where RSC=1.

L EVEL

OF

S ERVICE C APACITIES

AND

A NALYSIS

The NFR MPO Travel Model performs basic Level of Service computations as part of the post-processing algorithm. However, the capacities used in this procedure have not been calibrated to the North Front Range as a whole, and have not been calibrated to the refreshed model. The procedure used to calculate Level of Service is largely based on general rules, and has not been adjusted to take full advantage of data available to the NFR MPO. For these reasons, it is important that Level of Service results be interpreted with great care.

The NCHRP adjustment utility is run automatically with post-processing if the required fields are present. However, the effects of the adjustment are not applied until the user toggles the NCHRP 255 option to Adjustment On. When the adjustment is turned on, volumes and speeds are adjusted for all time periods. This will cause the performance report and maps to reference adjusted data. The Mobile6 for conformity process will also use NCHRP adjusted information when the adjustment is turned on. Note: If the NCHRP adjustment status is changed after a TransCAD map (*.map), layout (*.lay), dataview (*.dvw), or workspace (*.wrk) is created, the change may be immediately applied to the saved file, even if no changes are made to the map, layout, dataview, or workspace itself. The NCHRP adjustment toggle works by replacing certain files with adjusted or unadjusted volumes. The following files are replaced when the adjustment status is changed: FlowAM.bin FlowMD.bin FlowPM.bin FlowOP.bin Flow.bin HrFlow.bin

PEAK DIRECTIONAL VOLUME

Level of service is based on a generalized peak-hour volume. This volume is determined by factoring the total daily traffic volume on each link in the roadway network. A factor of 0.09 is used to convert daily volumes to peak-hour volumes. For two-way streets, a peak directional factor of 0.6 is applied. For one-way streets, a peak factor of 1.20 (or 0.6/0.5) is applied.

LEVEL OF SERVICE CAPACITIES

Level of service is computed based on a set of Level of Service Capacities. While traffic assignment is based on LOS C capacities, Level of service computations are based on peak-hour directional LOS E capacities. These Level of Service capacities as shown in Table 10 were calibrated to match observed intersection Level of Service in the Fort Collins area. This calibration was done using a previous version of the travel model that only contained urban, rural, and CBD area types. Therefore, only these types are listed. Suburban capacities are currently set to match urban capacities, and both CBD types use the general CBD capacities.

15

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

ADDITIONAL FUNCTIONS
Table 10 Level of Service Capacities Urban 1950 1080 980 910 520 910 1040 Rural 2275 1340 1250 960 520 960 1040 CBD 1950 1120 910 560 520 560 1040

Freeway Expressway Major Arterial Minor Arterial Collector Frontage Road Ramp

VOLUME TO CAPACITY CUTPOINTS

Volume to Capacity ratios are determined and compared to Highway Capacity Manual cutpoints, shown in Table 11. These cutpoints were applied separately for freeways/expressways and arterials. Although volumes and capacities are calculated for all facility types, Level of Service is not computed for collectors, frontage roads, and ramps. Table 11 Upper Limit V/C Cutpoints LOS A B C D E F Freeways / Expressways 0.31 0.50 0.71 0.87 1.0 n/a Arterials 0.51 0.67 0.79 0.9 1.0 n/a

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

16

ADDITIONAL FUNCTIONS

17

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

RESOURCE CODE RESOURCE CODE

The NFR MPO travel model was created using the TransCAD GISDK scripting language. While many parameters and model settings can be edited by changing input files and scenario settings, some aspects of the model must be changed from within the model script. It is not necessary to have a strong understanding of the GISDK language to edit the NFR MPO model script, however some understanding of computer programming or scripting is needed. The GISDK Help section of the TransCAD help utility provides specific information on the syntax and capabilities of the GISDK language.

N AVIGATION
The NFR MPO TransCAD model is contained in three separate resource files. The file NFR100.rsc contains the primary model and dialog box script. The performance report is contained in NFRperf100.rsc, and the mode choice model is contained in NFRchoice.rsc. In the primary model script, each model step is prefaced with descriptive comments in the GISDK code. To easily find these comments, search for the character combinations described at the beginning of the resource file. At the beginning of each model step, input files, intermediate files, and output files are defined.

R ECOMPILING

THE

M ODEL

To recompile the model, ensure that the edited script has the name NFR100.rsc and is located at C:\Program Files TransCAD\NFRMPO\rsc, where C:\Program Files\TransCAD is the location of TCW.exe (TCW.exe may be located elsewhere on a specific computer). Choose NFR Travel Model -> Recompile from the TransCAD menu. This option will only be available if the NFR MPO model has been installed and activated.

NORTH FRONT RANGE REGIONAL TRAVEL MODEL

18