Tampa Bay Regional Planning Model Cube Voyager Conversion - Procedural Guide 2007… · ·...

Tampa Bay Regional Planning Model

Cube Voyager Conversion

Technical Report No. 2 Procedural Guide

Financial Project ID No. 259173-1-12-05

Prepared for:

Prepared by:

November 2007

Technical Report No. 2 Procedural Guide TBRPM v6.0

ii

Table of Content

Chapter 1 - Overview...........................................................................................................................1 1.1 Introduction...............................................................................................................................1

1.1.1 Study Area ..................................................................................................................1 1.2 Travel Demand Modeling .........................................................................................................1

1.2.1 Travel Forecasting Process .........................................................................................1 1.2.2 Specific Forecasting Tools..........................................................................................3

1.3 Model Conversion.....................................................................................................................5 1.3.1 File Structure...............................................................................................................6 1.3.2 Catalog Keys...............................................................................................................8 1.3.3 File Format and Name convention..............................................................................9 1.3.4 TranPlan File Conversion Tools .................................................................................9 1.3.5 Model Efforts and Enhancements.............................................................................10

Chapter 2 - Data Preparation and Standard Reporting ................................................................13 2.1 General Description ................................................................................................................13 2.2 Standard Reporting .................................................................................................................13

Chapter 3 - External Trips................................................................................................................18 3.1 General Description ................................................................................................................18 3.2 Model Inputs and Outputs.......................................................................................................20 3.3 Model Procedure.....................................................................................................................20 3.4 Standard Output ......................................................................................................................21

Chapter 4 - Trip Generation.............................................................................................................23 4.1 General Description ................................................................................................................23 4.2 Trip Generation Inputs and Outputs .......................................................................................24 4.3 Model Procedure.....................................................................................................................28 4.4 Standard Output ......................................................................................................................29

Chapter 5 - Highway Network and Path .........................................................................................32 5.1 General Description ................................................................................................................32 5.2 Model Inputs and Outputs.......................................................................................................33 5.3 Model Procedure.....................................................................................................................34 5.4 Standard Output ......................................................................................................................40

Chapter 6 - Trip Distribution ...........................................................................................................45 6.1 General Description ................................................................................................................45 6.2 Model Inputs and Outputs.......................................................................................................45 6.3 Model Procedure.....................................................................................................................47 6.4 Model Output ..........................................................................................................................49

Chapter 7 - Transit Network ............................................................................................................50 7.1 General Description ................................................................................................................50 7.2 Model Inputs and Outputs.......................................................................................................51 7.3 Model Procedures ...................................................................................................................53 7.4 Mode Outputs..........................................................................................................................60

Chapter 8 - Transit Path ...................................................................................................................61 8.1 General Description ................................................................................................................61 8.2 Model Inputs and Outputs.......................................................................................................61 8.3 Model Procedure.....................................................................................................................63


iii

8.4 Model Output ..........................................................................................................................66 Chapter 9 - Mode Choice ..................................................................................................................68

9.1 General Description ................................................................................................................68 9.2 Model Inputs and Outputs.......................................................................................................68 9.3 Model Procedure.....................................................................................................................69 9.4 Model Outputs ........................................................................................................................70

Chapter 10 - Highway Assignment...................................................................................................71 10.1 General Description ..............................................................................................................71 10.2 Model Inputs and Outputs.....................................................................................................71 10.3 Model Procedure...................................................................................................................72 10.4 Model Outputs ......................................................................................................................73

Chapter 11 - Transit Assignment .....................................................................................................75 11.1 General Description ..............................................................................................................75 11.2 Model Inputs and Outputs.....................................................................................................75 11.3 Model Procedure...................................................................................................................76 11.4 Model Outputs ......................................................................................................................77

Chapter 12 - Summary ......................................................................................................................78 Chapter 13 - Model Utilities..............................................................................................................80

13.1 Conversion Tools ..................................................................................................................80 13.2 Measures of Effectiveness (MOE) Reporting.......................................................................82 13.3 Model File Cleanup Tools ....................................................................................................83


iv

List of Figures Figure 1.1 - Tampa Bay Regional Planning Model (TBRPM) Study Area.......................................... 2 Figure 1.2 - The Florida Standard Urban Transportation Modeling Structure (FSUTMS) Flowchart. 4 Figure 1.3 - TBRPM v5.2 File Structure .............................................................................................. 7 Figure 1.4 - TBRPM v6.0 File Structure .............................................................................................. 7 Figure 1.5 - TranPlan Input File Conversion Tools............................................................................ 10 Figure 3.1 - TBRPM External Station Locations................................................................................ 19 Figure 3.2 - EXT Mode Stream .......................................................................................................... 21 Figure 3.2 - External Module Reporting Page .................................................................................... 22 Figure 4.1 - Trip Generation (GEN) Model Stream ........................................................................... 28 Figure 4.2 - Trip Generation Reporting Page ..................................................................................... 30 Figure 4.3 - Trip Generation Example Report .................................................................................... 31 Figure 5.1 - HNET Model Stream ...................................................................................................... 35 Figure 5.2 - Highway Network Reporting Page ................................................................................. 41 Figure 5.3 - Highway Path Reporting Page ........................................................................................ 42 Figure 5.3 - Example Highway Network Report ................................................................................ 43 Figure 5.4 - Example Highway Path Report....................................................................................... 44 Figure 6.1 - Trip Distribution Model Stream...................................................................................... 47 Figure 6.2 - Trip Distribution Reporting Page.................................................................................... 49 Figure 7.1 - Transit Network Model Stream....................................................................................... 53 Figure 7.3 - Create Non Transit Connectors Databases and Networks .............................................. 56 Figure 7.4 - Side Walk Connectors..................................................................................................... 57 Figure 7.5 - Walk Connectors............................................................................................................. 58 Figure 7.6 - Auto Connectors.............................................................................................................. 59 Figure 8.1 - Transit Path Model Stream.............................................................................................. 63 Figure 8.2 - Transit Path Model Stream.............................................................................................. 64 Figure 8.3 - Transit Path Model Stream.............................................................................................. 65 Figure 8.2 - Transit Path Finding........................................................................................................ 67 Figure 9.1 - Model Choice Model Stream .......................................................................................... 69 Figure 10.1 - Highway Assignment Model Stream ............................................................................ 72 Figure 11.1 - Transit Assignment Model Stream................................................................................ 76 Figure 13.1 - TranPlan File Conversion Tools ................................................................................... 81 Figure 13.2 Measures of Effectiveness Reporting Module ............................................................. 82 Figure 13.3 - Model File Cleanup Tools............................................................................................. 83


v

List of Tables Table 1.1 - TBRPM v6.0 Input and Output Directory.......................................................................... 8 Table 1.2 - TBRPM v6.0 Catalog Keys................................................................................................ 8 Table 3.1 - External Model Inputs and Outputs.................................................................................. 20 Table 4.1 - TAZ Numbers by County................................................................................................. 24 Table 4.2 - Trip Generation Inputs and Outputs ................................................................................. 25 Table 5.1 - Highway Network Inputs and Outputs ............................................................................. 33 Table 6.1 - Trip Distribution Inputs and Outputs ............................................................................... 45 Table 7.1 - Transit Network Inputs and Outputs ................................................................................ 51 Table 7.2 - Transit Mode Number Definitions ................................................................................... 54 Table 8.1 - Transit Path Inputs and Outputs ....................................................................................... 61 Table 9.1 - Mode Choice Model Input and Outputs ........................................................................... 68 Table 10.1 - Highway Assignment Inputs and Outputs...................................................................... 71 Table 10.2 - Highway Assignment Validation Reports ...................................................................... 73 Table 10.3 - Highway Assignment Analysis Reports......................................................................... 74 Table 11.1 - Transit Assignment Inputs and Outputs ......................................................................... 75 Table 12.1 - Model Run Time............................................................................................................. 78


1

Chapter 1 - Overview

1.1 Introduction This technical report serves as a "hands-on" Procedural Guide for applying and interpreting the results of the Tampa Bay Regional Planning Model Version 6.0 (TBRPM v6.0). The model chain is fully described in detail including: required inputs, step-by-step procedures for setting up and running the model chain, outputs produced by the model runs, procedures for interpreting and using the model run outputs, and special considerations that need to be taken into account in applying the model runs and interpreting their results.

1.1.1 Study Area The Tampa Bay study area for the Regional Transportation Analysis (RTA) corresponds with the jurisdiction of the Florida Department of Transportation (FDOT), District Seven (D7). During the RTA, Phase IX, TBRPM development and its validation effort, FDOT D7 included the Counties Hillsborough, Pinellas, Pasco, Hernando, and Citrus of Florida. The TBRPM boundary is also expanded southward into Manatee County to include the Port Manatee area and I-75 / I-275 loop and interchange. The purpose of the RTA and TBRPM is not to conduct planning activities in Manatee County. However, due the heavy trip interchange between southern Hillsborough and Pinellas Counties it is essential to include to the Port Manatee area to more accurately model travel patterns in the region. The RTA Study Area for the TBRPM is as depicted in Figure 1.1. The RTA Study Area in 2000 already had a population of over 2.5 million, showing an approximate 1.3% annual growth rate since 1990.

1.2 Travel Demand Modeling The TBRPM v6.0 is the tool that the RTA uses in forecasting future travel demand. The following sections of this report explain, in general terms, how travel demand models operate.

1.2.1 Travel Forecasting Process Whether using sophisticated computer models or hand calculations, there are four basic steps to the process of travel demand forecasting. These steps include the following:

Trip Generation Trip Distribution Mode Choice Trip Assignment


2

Figure 1.1 - Tampa Bay Regional Planning Model (TBRPM) Study Area


3

These four steps allow the number of trips in a given area to be estimated, and then assigned to specific transportation facilities, such as either highway or transit systems.

1.2.2 Specific Forecasting Tools There are many different travel demand modeling software packages available. For this current configuration, the model setup has been fully converted from the TranPlan modeling package into a new modeling software known as CUBE Voyager. Full details about this software can be found on the Citilabs website, www.citilabs.com, the softwares manufacturer. Florida Standard Urban Transportation Model Structure (FSUTMS) Figure 1.2 shows the ten component modules of FSUTMS which are used to fulfill the four basic travel demand forecasting steps discussed above. These components - briefly described below - are processed in a serial fashion to complete the travel demand simulation. EXT creates the external-external trip table. GEN calculates the zonal trip productions and attractions. HNET builds the highway network. HPATH finds the minimum impedance inter-zonal highway travel paths. DISTRIB creates the zone-to-zone person trip table. TNET builds the transit network. TPATH finds the minimum impedance inter-zonal transit travel paths. MODE converts the person trips to transit mode of travel and highway vehicle trips. HASSIGN assigns the vehicle trips to the highway network and produces summary statistics on the highway assignment model performance. TASSIGN assigns the transit person trips to the transit system and produces summary statistics on the transit assignment model performance The FSUTMS components as describe above are now implemented in the CUBE environment as CUBE modules / applications. The only exception is that the HNET and HPATH steps are now combined into one application in CUBE. CUBE applications are stored in .APP files and make up the whole model stream, but the current CUBE Voyager conversion still processes the model inputs in a similar manner as previous model validations on legacy software platforms. Tampa Bay Regional Planning Model (TBRPM) The TBRPM is the FSUTMS model for the Tampa Bay / FDOT D7 study area. TBRPM v6.0 is the latest version of the model and uses Cube Voyager with TRNBUILD as the new platform for highway and transit travel estimation. This new setup completely eliminates all uses of TranPlan modules. Two user programs, written in FORTRAN, are still used which are based on the TranPlan file formats for both Trip Generation and Mode Choice. These programs will be described later in detail. The CUBE Voyager conversion creates the text based file formats for these user programs when needed, so the user does not have to rely on the old TranPlan file formats, but can edit the data as needed in the newer dBase formatted files being used by the rest of the CUBE Voyager model.

http://www.citilabs.com/


4

Figure 1.2 - The Florida Standard Urban Transportation Modeling Structure (FSUTMS) Flowchart


5

This report assumes that the readers already have some familiarity with the standard modeling techniques used in Florida, FSUTMS, and CUBE Voyager. For more details on modeling with CUBE Voyager, the user should refer to the software documentation as provided by Citilabs, Inc. Since the TBRPM v6.0 uses the newer CUBE Voyager engine, the internal modeling structure has been changed including file structures and model flows as discussed in the next section.

1.3 Model Conversion The previous versions of the TBRPM, 5.0 5.2, were a combination environment of Cube and TranPlan. But, since the State of Florida through the Florida Department of Transportation has chosen the Cube modeling software platform, it has always been the intent to fully convert the legacy TranPlan models into the new environment to take full advantage of the newer developing Voyager modeling engine. Eventually this will also mean the use of the Public Transport (PT) modeling engine which is used for transit. This version of the TBRPM, however, uses the TRNBUILD transit modeling engine from TP+ which is also still a part of the Cube environment.


6

The next sections describe what changes this conversion to the Voyager engine entailed for the TBRPM.

1.3.1 File Structure Figure 1.3 shows the typical file structure in TBRPM v5.2. The Year 2000 Base scenario directory is used as the base directory which contains all the files for the base scenario, but is also the parent directory for all other scenarios. The files contained in the Base scenario are paralleled in the other future year alternative directories; Year 2008 EC, Year 2015 CA, Year 2025 CA. The TBRPM v6.0 model uses a similar directory structure as other newer regional models in Florida with some enhancements. Figure 1.4 depicts the new file structure of the TBRPM v6.0. It is located under a model-specific folder called TBRPM_Voyager. This folder is a subdirectory of the D7 or District 7 folder, which is located under the FSUTMS folder. In TBRPM v6.0, the subdirectories can be classified according to five general categories as below:

(1) Base: the base scenario directory containing all the common files being used by all scenarios. (i) Year_2000_Base: includes Input and Output directories for the base year model run. (a) Input: all the input files for the base year model run, including any TranPlan formatted

input files used for the conversion to the input database file formats; (b) Output: all the output files generated for the base year model run, including the output

database files, matrix files, and a subfolder WWW used for reporting purposes.

(ii) Year_2008_EC: includes Input and Output directories for 2008 E+C. (ii) Year_2015_CA: includes Input and Output directories for 2015 cost affordable. (ii) Year_2025_CA: includes Input and Output directories for 2025 cost affordable.

(2) cube: is the working directory which contains the application files, script files and intermediate print out files of the current model run.

(3) Doc: directory contains the .PDF version of the TR1 - Validation Report and TR2 Procedural Guide, this report, and any other pertinent documentation for the current model.

(4) GIS: directory contains all the GIS shapefiles and other graphic images that are used by the model.

(5) user.prg: directory is inherited from the previous version of TBRPM and contains all user-defined programs used by the model.

As shown in Figure 1.4, all the common files (.SYN files and converted database files such as a terminal time database, transit speed lookup database, etc.) are located in the Base directory, while the Year_2000_Base scenario directory, with its scenario specific files, is paralleled to all other future year model run / alternative directories.


7

Figure 1.3 - TBRPM v5.2 File Structure

Figure 1.4 - TBRPM v6.0 File Structure


8

The TBRPM_Voyager folder also contains the CUBE catalog file, TBRPM6.cat. To access the model structure, the user should open this file in CUBE and run the model using the CUBE interface. The most common way to run TBRPM v6.0 is to execute the entire model for a selected model year run or all model years can be run in a series. Model run times are typically 1 - 2 hours long depending on the speed of the computer used to run the model and the model scenario. A single application of one complete model run usually takes about 2GB of hard-disk space.

1.3.2 Catalog Keys Although the scenario key could be used to facilitate the file management for a variety of scenarios and alternatives, it was not used in TBRPM v6.0. The users must use the following catalog keys to define their input and output directories for each scenario / alternative:

Table 1.1 - TBRPM v6.0 Input and Output Directory Catalog Key Value (for example) Comment {WORK_DIR}\Input\ C:\fsutms\d7\TBRPM_Voyager\Base\Year_2000_Base\Input\ Input dir {WORK_DIR}\Output\ C:\fsutms\d7\TBRPM_ Voyager\Base\Year_2000_Base\Output\ Output dir The use of these catalog keys increased the ease and efficiency of file management. It is believed to be a good modeling practice. TBRPM v6.0 catalog keys use different values for the Base Year 2000, validation, network than the other alternative model runs. In addition, the following catalog keys should also be checked to make sure that they are appropriate for each scenario / alternative:

Table 1.2 - TBRPM v6.0 Catalog Keys Catalog Key Value (for example) Comment ALT A Alternative name YEAR 00 Last 2 digit of the year WORK_DIR C:\fsutms\d7\TBRPM_Voyager\Base\Year_2000_Base\ Working directory USERPRG C:\fsutms\d7\TBRPM_Voyager\User.prg\ User defined program dir. ANALYSIS 0 (1 --- HEVAL analysis run) HEVAL validation run Cube uses its built-in catalog key SCENARIO_DIR to define the base scenario and other scenarios are then defined under the base scenario. By defining the WORK_DIR and setting the value to C:\fsutms\d7\TBRPM_Voyager\Base\Year_2000_Base\, the base scenario directory is moved to the folder Year_2000_Base under the Base directory and paralleled with all other scenarios.


9

1.3.3 File Format and Name convention In TBRPM v6.0, the input files used are generally in the dBase .DBF database format instead of the plain, column delimited ASCII text files that the TranPlan input files used. These text files used the extension .YYA for input files and the extension .AYY for the output files as found in the TBRPM v5.2 CUBE TranPlan Model. The TBRPM v6.0 generally follows similar naming convention rules as recommended by the FDOT Central Office; using the same filename as in previous TBRPM models with the use of _YYA, for input files, and _AYY, for output files, with the .DBF extension.

1.3.4 TranPlan File Conversion Tools One unique feature of the TBRPM v6.0 is that it offers a set of conversion tools which allows for conversion of the original TranPlan formatted input files to the necessary database formats. Consultants who have the historical input files for other intermediate model year networks (for instance, year 2009 or year 2010) can use this set of conversion tools to generate the input database files. The Conversion application is set with the execution order of 0 within the main application, and therefore will be ignored in the normal model stream. A user can run the procedure manually to execute the file conversions. First double-click the Conversion application box, and run the model with the run this group only option to execute only the application boxes of the conversion routines. The TranPlan input files are highlighted in the PINK colored boxes as shown in Figure 1.5. They should all be located in a scenarios input directory before conversion. A copy of the original binary TranPlan highway network should also be saved as a Voyager network in the same input directory as Base_YYA.net, substituting the YYA with the proper year and alternative letter of the scenario being converted. The user needs to setup a new scenario in Cube, before attempting to convert any TranPlan files, if the desired scenario does not already exist in the model structure. See also Chapter 13 - Model Utilities for other details.


10

Figure 1.5 - TranPlan Input File Conversion Tools

1.3.5 Model Efforts and Enhancements The new Cube Voyager engine has required a lot of effort to make the model results comparable with the previous TranPlan model results due to the differences in methodology behind each module, especially for highway skim and assignment. Continuing efforts are being made during the final process of conversion to understand and make these differences as close as possible. The following sections outline some of the differences made because the conversion to Voyager as well as other changes to the model stream.

(1) Trip Distribution First difficulty in the conversion was to make the trip distribution results to be close as possible to the previous Cube TranPlan model runs. TranPlan uses GMODEL for the trip distribution and only integer number are reported in the output matrices. The conversion to Voyager presented three


11

major problems to solve: gravity model calculation, friction factor lookup, and rounding issues. Details of the effort will be explained in Chapter 5 - Trip Distribution.

(2) Remove the CPI calculation The concept of Composite Impedance (CPI) was adopted back in TBRPM v3.2 to properly account for the availability and influence of transit on the transportation network. For simplicity and ease of understanding, the TBRPM v6.0 does not include the conception of CPI under the approval of FDOT District 7.

(3) Highway Assignment algorithm TBRPM v5.2 uses the Highway Equilibrium methodology of TranPlan to assign the trips into the highway network while TBRPM v6.0 uses the HIGHWAY module of Cube Voyager. To make the results close enough for comparison the following problems were addressed:

(i) Implementation of the Toll Facility Model as used in TranPlan (ii) Correct Impedance Calculation (iii)Convergence Criteria (iv) Number of Iterations (v) Use of Damping Factor (vi) Maximum V/C Ratio Used

(4) Develop Selected Link and Selected Zone applications

The Selected Zone and Selected Link applications have also been developed for the TBRPM v6.0 using the Voyager highway assignment processes. There are some model enhancements that have been made in TBRPM v6.0 in order to better represent the model results and be more compatible with the new Cube Voyager engine.

(5) Use of TRNBUILD for Transit Modeling TRNBUILD, an alternative transit modeling tool based in a planning software package Transportation Planning Plus (TP+) which is part of the Cube environment, has been used in TBRPM v6.0 for the transit travel demand modeling, including building of the transit network, transit path finding and transit assignment. For consistency with past models, the TBRPM v6.0 still uses the FORTRAN based user written programs Sidecon / Walkcon / Autocon, slightly modified, to create non-transit connectors for the transit connectivity between TAZs and transit lines. The output of these user programs is reformatted in order to be compatible with TRNBUILD during the modeling process.


12

(6) Newly Adopted Mode Choice Model The Miami North Corridor Transit Study Models Mode Choice application has been approved by FTA and was adopted for use in the new TBRPM v6.0 after some necessary adjustments. There are 3 paths in the previous TBRPM TranPlan model. The adoption of the new Model Choice Model now uses 14 paths in each time period. The parameters used in the transit path skimming also were adjusted according to the new Mode Choice Models coefficients.

(7) Generate the standard model output report using a web-based interface An HTML formatted, reporting functionality has been developed for the TBRPM v6.0 to better report the model results by using web browser technology. Chapter 2 - Chapter 11 explains each module in the model in more detail. There are five components in each chapter: (1) General Description: introduction of each module in detail. (2) Model Inputs and Outputs: List all the input and output files for each module. (3) Model Procedure: Step by step description of the process and conversion efforts taken. (4) Model Output: Sample output (HTML, .DBF)


13

Chapter 2 - Data Preparation and Standard Reporting

2.1 General Description Within the Cube interface of the main TBRPM v6.0 application, one can see the individual modules of the model. The first model step is a Pilot module, File Copy and Data Preparation, which is used to setup a model run. The function of this module is to delete all the unnecessary files from any previous model run and copy all the new model network input files from the appropriate directories. The PROFILE.MAS file, from the previous Cube TranPlan model setup, still needs to be copied from the scenario directory for the two user-written programs that are in use for this current Cube Voyager model chain. These two user programs are: TBGEN36.exe for trip generation and the new MODMIAUB.exe used for mode choice. A time stamp file RUNTIME.PRN is generated for the TBRPM v6.0 to record the start and end run times for each module. Any previous time stamp file is deleted in this step before the rest of the model execution.

2.2 Standard Reporting An HTML formatted reporting functionality has been developed for the TBRPM v6.0 to better report the model results in the easy to use web browser technology. Since multiple reports are generated at various model steps, this technology is being used to consolidate the reporting environment for easier viewing. The following text describes the steps necessary to setup this reporting function. The ADOBE SVG Viewer is used in the model reporting for graphs, charts, and maps that will be generated in the reports. The SVG viewer will need to be downloaded and installed on the users machine. The SVG Viewer integrates with your web browser as a plug-in. The SVG Viewer allows the user to interact with SVG images and is required to view any web content that contains SVG. The SVG Viewer program can be downloaded at http://www.adobe.com/svg/viewer/install/ for the SVG files to be correctly displayed in the web browser. The latest version of the viewer has also been included in the TBRPM v6.0 package under the User.prg folder, as SVGView.EXE. Double-clicking this file will begin the install process. At this time, only Internet Explorer is supporting this viewer. For the HTML reporting to be used properly from within Cube, a user program called WEBREPORT, in a process box located at the bottom of the TBRPMs main application window needs to be setup as well. This box is only used to reference the Internet Explorer application with the starting HTML page for the scenario that is selected. To set this up properly the user resource file WEBREPORT.Rsc from the model download needs to be placed in the C:\Program

http://www.adobe.com/svg/viewer/install/


14

Files\Citilabs\Cube\Resource\User correctly. This should automatically happen when the model download is unzipped to the C:\ drive of the machine that will run the model. This should work for any Cube Voyager version 4.1 or higher. If the Cube install or Internet Explorer is not located in their default locations, the process can also be setup manually following the steps as outlined in the following:

(1) In Cube Voyager Menu, click Settings and then User Programs

(2) Click the Add button on the right of the User Program Settings panel that is displayed


15

(3) Under the Program Tab of the next form, fill-in the setup as follows:

(4) Then under the Input Files Tab, click Add and setup as follows:


16

(5) Under the Command Line Tab, fill-in the setup as follows:

After this initial setup, the user can double click the WEBREPORT box from the main application window and click Run on the following form which shows next. The web browser will be launched accessing the model reporting.


17

Another option to open the report is to locate the HTML report files in the OUTPUT\WWW directory of the scenario and open the Index.html file using the Internet Explorer (IE) application. For the base year scenario this location would be the following: C:\FSUTMS\D7\TBRPM_VOYAGER\Base\Year_2000_Base\Output\www\index.htm Once the WEBREPORT is open, the user can navigate through reports for each module from the menu bar on the left, accessing the various HTML reports from the WWW directory of the scenario.

Each report generally contains two components. The first component provides another set direct links to the primary input and output files for each module. The second component contains individual reports, charts, graphs or maps specific to each module.


18

Chapter 3 - External Trips

3.1 General Description The study area of the TBRPM v6.0 consists of Hillsborough, Pinellas, Pasco, Hernando, and Citrus Counties along with a representative portion of northwest Manatee County to accommodate the I-275 / I-75 traffic interchange. External stations are the intersections between the model boundary or cordon line and the highway network of the study area. These stations serve as points of entry or exit, to or from the study area. The TBRPM v6.0 has a total of twenty-three (23) external stations. Each station was coded with a traffic analysis zone (TAZ) number between 2601 and 2623, as depicted in Figure 3.1. The External Trip (EXTERNAL) model is the second module on the main TBRPM v6.0 Cube application interface. The function of this module is to produce a trip table that specifies the number of daily External-External (EE) vehicle trips passing between each pair of external traffic analysis zones (TAZs / stations). External trip data contained in the EETRIPS_YYA.DBF file is the input into the External Trip model (EXTERNAL), creating the EE trip table data set (EETABLE_AYY.MAT). Separate trip tables are generated for autos, light-duty trucks, and heavy trucks from the model input. Two other output files are generated in this module: a dBase database formatted report (EXT.DBF) and an HTML format report (EXT.HTM). The EE trip table data in the form of a Cube matrix file (EETABLE_AYY.MAT) is later used as input for assignment during the Distribution and Highway Assignment applications of the modeling process.


19

Figure 3.1 - TBRPM External Station Locations


20

3.2 Model Inputs and Outputs

Table 3.1 - External Model Inputs and Outputs

Input Process Output

EETRIPS_YYA.DBF EXT EETAB_AYY.MAT EXT.HTM EXT.DBF

INPUT: EETRIPS_YYA.DBF Total external-external vehicle trips between each external

station pairs, with three trip mode designations (purpose 1 = autos, purpose 2 = light-duty trucks, purpose 3 = heavy trucks).

OUTPUT: EETAB_AYY.MAT External-external trip table. EXT.HTM Trip end summary report for the external zones. EXT.DBF Trip end summary in Database format.

3.3 Model Procedure The module processing steps are shown in Figure 3.2 and described by the following:

(1) Create Initial Index.HTML for reporting access.

(2) Create external trips percentage report from input file ZDATA4.

(3) Create EETAB_YYA.MAT, which contains three trip matrices: auto, light truck and heavy truck. The FSUTMS.CTL file is also created in the working directory to be used in the Trip Generation and Mode Choice user programs.

(4) Create HTML formatted external trip report (EXT.HTM) and database file (EXT.DBF).


21

Figure 3.2 - EXT Mode Stream

3.4 Standard Output The following standard reports are generated by this process and can be accessed in the HTML reporting as shown in Figure 3.3:

External trip Origins and Destinations at each of the external stations for auto, light truck, and heavy truck

Summary Report of the Total EE Trip Ends Summary Report of EE Trips in ZDATA4


22

Figure 3.2 - External Module Reporting Page


23

Chapter 4 - Trip Generation

4.1 General Description Trip Generation (GEN) model is the second step that occurs in the Florida Standard Urban Transportation Model Structure (FSUTMS) process, and the third module (GENERATION) in the new TBRPM v6.0. It determines the number of trips ends that originate from, called productions, or terminate in, called attractions, each Traffic Analysis Zone (TAZ). Trip generation is the determination of zonal travel demand by trip purpose. The Trip Generation model uses the demographic characteristics of each zone as input to estimate the number of daily person and vehicle trips produced and attracted by each TAZ by trip purpose. The FSUTMS trip generation model for the TBRPM requires five input data sets. The first Zonal Data set, ZDATA1_YYA.DBF, contains zonal data used for trip productions including population, dwelling units, vacancy rates, lifestyle by auto ownership breakdowns, and hotel / motel units. The second Zonal Data set, ZDATA2_YYA.DBF, contains zonal data for employment, school enrollment, trucks, and parking costs. Special traffic generator information is contained in the third Zonal Data set, ZDATA3_YYA.DBF. The fourth Zonal Data set, ZDATA4_YYA.DBF, contains the external station descriptions, the total external vehicle trips by each station, and the percent of those trips that are External-External (EE) trips, as discussed in the previous chapter. The fifth Zonal Data set, ZDATA5_YYA.DBF, contains the average auto occupancies by trip end type, production or attraction, by trip purpose, and the trip purpose percent of allocation to be used in the external trip generation model. An enhancement to the Trip Generation model includes the calculation of the zonal area type based on zonal land use and demographic characteristics from the ZDATA input files. Land use data for each zone is maintained in the VACACRES.YYA file and is used to compute zonal area type through calculations that also use the land use and demographic coefficients which are maintained in the ATCOEF.SYN file. The calculated area type for a zone can be overridden by updating the area type for that zone in the ATYPES.SYN input file. This area type for the TAZ determines the area type coefficient to be used during the trip generation of productions and attractions by trip purpose. A cross-classification procedure is used that stratifies the trip generation rates by lifestyle categories. These lifestyle categories include the retired, workers without children, and workers with children by auto ownership, seasonal residents and hotel / motel units. The trip generation rates for these lifestyle categories and the area type coefficients, mentioned above, are maintained in the GRATES.SYN file. These rates are used to compute trip productions and attractions. The trip production and attraction equations are now controlled through the coefficients that are being used in the GRATES.SYN input file. To modify an equation for a trip purpose, for either productions or attractions, a coefficient for one of the independent variables, as listed in the GRATES.SYN file, must be added, deleted, or modified for that particular trip purpose. Three data sets (ATTRS.AYY, PRODS.AYY, A1DECK.AYY) are produced by the trip generation model. The trip productions by trip purpose for each zone are contained in the PRODS.AYY data


24

set, and the trip attractions by trip purpose for each zone are contained in the ATTRS.AYY data set. The A1DECK.AYY file is a consolidation of zonal data and is used to generate the new A1DECK file needed for the newly adopted Miami North Corridor Transit Study Model, Mode Choice model. The information in the A1DECK file includes attraction zone terminal time, daily (peak model / work trip) parking cost, midday (off-peak model / non-work trip) parking cost, percent of trips by auto ownership category, and an area type flag (ex. CBD) by zone. The PRODS.AYY and ATTRS.AYY files are converted into the GEN_PANDA.DBF dBase formatted database file as the input to the new Cube Voyager based Trip Distribution (DISTRIB) module. TBRPM v6.0 uses the user-defined, FORTRAN program TBGEN36.EXE for the trip generation calculations. The only difference in the new TBRPM version is that all the input files (ZDATA1-5) and output files (PRODS, ATTRS) are now using the dBase database formatted files for editing, display, or use by other model modules. These new ZDATA files are converted back to the legacy text file formats by the model stream as needed for any user written program. A user should only edit the dBase version of the ZDATA files, if needed. Any edits to the plain text version of these files, though used by the user defined programs, will be over written when the model converts the dBase formatted files to the text version. The model still uses the .SYN files, located mostly in the Base scenario directory, except where deem necessary for individual use by each scenario. Most of these files may later be converted, especially when the TBGEN36 program is later converted into Cube Voyager script.

4.2 Trip Generation Inputs and Outputs The Traffic Analysis Zone (TAZ) numbering for the Tampa Bay Area by County is shown below in Table 4.1.

Table 4.1 - TAZ Numbers by County

County TAZs Dummy TAZs Available

Hillsborough 1-738 739-1000

Pinellas 1001-1741 1742-1800

Pasco 1801-2132 2133-2200

Hernando 2201-2392 2393-2400

Citrus 2401-2492 2493-2589

Others (Manatee County) 2590-2597 2598-2600

External 2601-2623


25

Table 4.2 illustrates all of the input and output files associated with the Trip Generation model followed by a brief description of each of these files and any special considerations or checking that are required to ensure the integrity of the data.

Table 4.2 - Trip Generation Inputs and Outputs


PROFILE.MAS BALZ.SYN CBDZONES.SYN EXURBS.SYN GRATES.SYN ATCOEF.SYN LINKS.YYA XY.YYA VACACRES.YYA ATYPES.YYA

GEN (TranPlan Format)

PRODS.AYY ATTRS.AYY A1DECK.AYY GEN.OUT LUCHECK.OUT NRZONE.OUT

ZDATA_YYA.DBF ZDATA2_YYA.DBF ZDATA3_YYA.DBF ZDATA4_YYA.DBF ZDATA5_YYA.DBF

GEN (Voyager Format)

GEN_PANDA.DBF GEN_SUM.DBF GEN_SOCECO.DBF GEN_TRIPRATES.DBF GEN_PANDA_SUM.DBF GEN.HTM

INPUTS:

PROFILE.MAS Included the TranPlan parameters for TBGEN.

BALZ.SYN Used to set up trip balancing between the productions and attractions of each zone. Use of the dummy TAZs from another county should use the appropriate balancing group code.

CBDZONES.SYN Used to define the TAZs that compose the CBD areas.

EXURBS.SYN Used to define Exurban area (Not used).

GRATES.SYN Area Type coefficients and Trip generation rates used to compute trip productions and attractions.

ATCOEF.SYN This file contains coefficients used for calculating the Area Type of each TAZ based on its land use characteristic.

LINKS.YYA Used by the program to look-up the link area type which is used to determine the attraction zone terminal time which is later use by the mode choice program.

XY.YYA Contains the X and Y coordinates of the ANODE and BNODE of the LINKS.YYA.

ATYPES.SYN Used to override a TAZs general Area Type calculation in the GEN model. The Area Types now used are CBD, Urban / Suburban, and Sub Fringe / Rural.


26

VACACRES.YYA Shows each TAZs available vacant land by residential, industrial, commercial, and service land uses.

ZDATA1_YYA.DBF (Trip Production) - data from local sources, Census Bureau, and the Florida Statistical Abstract (FSA). Total DUs, % of Vacant and Non-permanent (Seasonal) DUs, % of Vacant DUs, Permanent DU Population, and Group Quarter Population. % of Auto Ownership (0, 1, 2 or 3+ autos) DUs by Retiree, Workers w/o Children, Workers w/ Children. Number of Business, Economy, Resort, Residence Type Hotels Units (Rooms), % Occupied and Total Occupants. Environment Justification Flag and Urban Area Flag

Data Checks Ratio of Population to Permanent DUs % of Vacant and Non-permanent DUs, % of Vacant % of Auto Ownership DUs by Retiree, Workers without Children, and Workers with

Children should add to 100% Hotel / Motel Units - Location in TAZs

ZDATA2_YYA.DBF (Trip Attractions) - Employment by Industrial, Regional / Local

Commercial, Regional / Local Service, and Total Employment - Data developed from Florida Agency for Workforce Innovation Labor Market Statistics, U.S. Department of Commerce Bureau of Economic Analysis, and Info USA. School Enrollment for Kindergarten to College - Data from School Boards and Florida Department of Education.

Number of Light Trucks (Class 5, 6, and 7) and Number of Heavy Trucks (Class 8 through 13) - data from Department of Highway Safety and Motor Vehicles.

Parking Costs (Long Term and Short Term). Activity Center Code and Description.

Data Checks: Employment by industrial, commercial, service should add to equal total employment. Major employees - Location in TAZs. School enrollment - Location in TAZs. Ratio of Trucks to Employees

ZDATA3_YYA.DBF (Special Generator)

Use with caution and requires reviewing the assignment results.

ZDATA4_YYA.DBF (EI Trips) Shows the total external traffic volume, and % of EE trips. No changes should be made without review by FDOT.


27

ZDATA5_YYA.DBF (EI Trips) - Shows the average auto occupancy, by trip end type (production / attraction flag), trip purpose, and % of trip allocation for the trip purpose from the residual trip totals in ZDATA4, after EE trips. No changes should be made without review by FDOT.

It should be noted that the LINKS.YYA and XY.YYA files are no longer used in the highway network module for the Cube Voyager conversion. However, since these files are utilized by the TBGEN36 user program, they are generated in this module from the Base__YYA.net network file for the scenario. OUTPUTS:

PRODS.AYY Trip productions by TAZ, by trip purposes for HBW, HBSH, HBSR, HBO, HBSCH, NHBW, NHBO, HT, LT, Taxi, EI, Airport, Collage / University and Total.

ATTRS.AYY Trip attractions by TAZ, by trip purpose for HBW, HBSH, HBSR, HBO, HBSCH, NHBW, NHBO, HT, LT, Taxi, EI, Airport, Collage / University and Total.

A1DECK.AYY TAZ attributes for mode choice calculations which include terminal times, parking costs, trip percentages by purpose, by auto ownership and CBD or Exurban flags.

GEN.OUT Trip generation report by trip purpose for each TAZ and trip generation statistical summary.

LUCHECK.OUT A Trip Generation error checking report.

NRZONE.OUT List of the three nearest zones for each TAZ.

GEN_PANDA.DBF Final Trip productions and attractions from Trip Generation by TAZ.

GEN_SUM.DBF A Trip generation statistical summary.

GEN_SOCECO.DBF Social economic data error checking database file.

GEN_TRIPRATES.DBF Trip rates by purpose.

GEN_PANDA_SUM.DBF A Report of Trip production and attraction subtotals by county.

GEN.HTM Trip Generation report in HTML format.


28

4.3 Model Procedure

Figure 4.1 - Trip Generation (GEN) Model Stream

(1) Launch the TBGEN36.exe user program to generate PRODS.AYY and ATTRS.AYY. All of the input and output files involved in TBGEN36 are shown for reference in the light blue boxes on the left of the module. Only the ZDATA dBase input files are available for editing at this time.


29

(2) Convert PRODS.AYY text output file to dBase database format. In the text output file one record contains the productions for the first ten trip purposes and the next record contains the productions of the last three trip purposes as a pair of records for each TAZ.

(3) Convert ATTRS.AYY text output file to dBase database format. In the text output file one record contains the attractions for the first ten trip purposes and the next record contains the attractions of the last three trip purposes as a pair of records for each TAZ.

(4) Combine the productions and attractions into one database GEN_PANDA.DBF. Also, PA.TXT file is output as the total productions and attractions for all the purposes by each TAZ.

(5) Use ZDATA1, ZDATA2 and PA.txt to generate the social economic summary for each zone, including occupied DU, population, car ownership, trips rates, etc. Total productions and attractions are obtained from PA.TXT to calculate the trip rates (total productions / occupied DU and total attractions / employment).

(6) Equations used for area type estimation, Trip Production and Attraction Equations report, Special Generator report, and the Subarea Balance report are created in this step for the HTML reporting.

(7) Trip Generation report GEN.HTM is created using the content of the output GEN.OUT from the FORTRAN trip generation user program. It has been verified that all the statistics are exactly same as the TBRPM v5.2 results for the same datasets. The dBase files GEN_SUM.DBF, GEN_TRIPRATES.DBF, and GEN_PANDA_SUM.DBF are then generated and contain the trip generation summary, trip rates by purposes, and the number of productions and attractions by county and trip purpose, respectively, for reporting purposes.

(8) Create SVG chart files for HTML reporting and record the time stamp.

4.4 Standard Output The following standard output reports are generated and accessed through the HTML page for Trip Generation as shown in Figure 4.2:

List of Independent Variables Equation Used for Area Type Estimation Production Equations Attraction Equations Special Generators Subarea Balancing Results Trip Generation Statistics Summary Productions and Attractions by County and Purpose Trip Rates


30

Social Economic Data Check (Detailed Report) Productions by Zone (Detailed Report) Attractions by Zone (Detailed Report)

Figure 4.2 - Trip Generation Reporting Page

An example report, for the Trip Generation Statistics is shown in the Figure 4.3.


31

Figure 4.3 - Trip Generation Example Report


32

Chapter 5 - Highway Network and Path

5.1 General Description Highway Network (HNET) is the third step in the FSUTMS model chain, and the forth module (NETWORK) on the TBRPM v6.0 main application interface. In this module, the highway system characteristics described by the highway network are summarized. Characteristics such as number of highway links, system miles, roadway classification, laneage, speed, and capacity are all inputs into the model through the binary highway network. The model uses these inputs to determine the speeds and capacities of the highway system. The fourth step in the FSUTMS model chain is Highway Path (HPATH), the path building module. In the new Cube Voyager conversion, TBRPM v6.0, the HPATH step is incorporated into the new highway network (NETWORK) module, so that the HNET and HPATH steps are in one module. In this consolidated module, the highway network is updated using its current input characteristics and the uncongested travel time, distance, and impedances are skimmed. The HPATH part of the module identifies the minimum uncongested travel time path between each pair of zones for use later in the model chain. Path selection is an important part of the modeling process since it has a significant impact on the final distribution of the trips which were generated during the trip generation (GENERATION) module of the model. In TBRPM v5.2, the TranPlan highway network is represented as a network of connected link segments and nodes, derived from the highway links file, LINKS.YYA, and node coordinates file, XY.YYA. The following data files are used to describe the highway network in TranPlan:

LINKS highway link characteristics

XY highway node coordinates

SPDCAP highway speeds and capacities

TCARDS highway link prohibitors and time penalties

TOLLLINK highway toll plaza characteristics

VFACTORS parameters used to convert hourly capacity to daily capacity, also provide facility type specific CONFAC, UROAD and BPR coefficients for equilibrium equations.

TBRPM v6.0 starts with the Cube Voyager binary network (BASE_YYA.NET), and does not rely on the text-based TranPlan format LINKS and XY files. When the user edits / changes the network, the unbuild operation is unnecessary for creating these files. For other purposes an unbuild operation is used to convert the binary network into links and node dBase files, which are converted to the text-based TranPlan files as needed for any legacy user programs. These files can be used as a backup to the binary network or for reporting purposes as needed. Other TranPlan files including SPDCAP, TOLLLINK, VFACTORS, and TCARDS have been converted into dBase file formats to be used as input for the current model structure. The dBase


33

version of these files should be edited with any necessary changes to work within the Voyager model stream. A conversion module of tools is offered in the CONVERSION module to convert any TranPlan files needed into the proper dBase file formats for use in the Voyager setup. The TBRPM v5.2, Cube TranPlan version, uses the NETPRO executable to generate a temporary HWYNET.TEM, and in turn uses the Build Highway Network function in TranPlan to build the base network, HNET.AYY. The NETPRO program also calculated the distance for each link based on the XY coordinates and looked-up the link speed and capacity based on the area type, facility type and number of lanes combination for each link, etc. The Cube Voyager scripts developed in the NETWORK module duplicate the NETPRO program functionality for the Voyager-based networks. After the network is updated, it is skimmed for its impedances for both Free-Flow and Free-Flow with HOV, output matrices are created and reports are generated for a selected path which the user can adjust through the {FromNode} and {ToNode} keys.


Table 5.1 - Highway Network Inputs and Outputs


BASE_YYA.NET SPDCAP_YYA.DBF TOLLLINK_YYA.DBF STATDATA_YYA.DBF

HNET

UNLOADED_AYY.NET LINKS.DBF XY.DBF HNET.HTM

TCARDS_YYA.DBF TERMTIME.DBF

HPATH

FREESKIM_HOV_AYY.MAT FREESKIM _AYY.MAT HPATH_TRACE.DBF HPATH_DISTSKIM.DBF HPATH_TIME2SKIM.DBF HPATH.HTM

HPATH (TranPlan Format)

FHSKIMS.TEM FHSKIMS.AYY FHSKIMS2.AYY

INPUTS:

BASE_YYA.NET Voyager binary network file.

SPDCAP_YYA.DBF Free-flow (uncongested) speed and capacity table by facility type, area type and number of lanes.

TOLLLINK_YYA.DBF Toll links location with associated attributes such as toll cost, service times or delay.

STATDATA_YYA.DBF Characteristics of transit stations, including park-and-ride and kiss-and-ride lots, and major transit centers.


34

TCARDS_YYA.DBF Turn prohibitor and time penalty records.

TERMTIME.DBF Terminal times by area type.

OUTPUTS: UNLOADED_AYY.NET Updated highway network with free-flow speed and travel time.

LINKS.DBF Highway network links database

XY.DBF Highway network nodes database

HNET.HTM HNET report

FREESKIM_HOV_AYY.MAT Free-flow (uncongested) interzonal travel impedances for LOV travelers.

FREESKIM _AYY.MAT Free-flow (uncongested) interzonal travel impedances for HOV travelers.

HPATH_TRACE.DBF Path trace database from {FromNode} to {ToNode}.

HPATH_DISTSKIM.DBF Distance skim report database from {SkimZone}

HPATH_TIME2SKIM.DBF TIME2 skim report database from {SkimZone}

HPATH.HTM HPATH report

FHSKIMS.TEM Free-flow (uncongested) interzonal travel impedances for LOV travelers in TranPlan format. (Includes terminal time, Intrazonal time, and max out the EE skim)

FHSKIMS.AYY Free-flow (uncongested) interzonal travel impedances for LOV travelers in TranPlan format. (No terminal time, no Intrazonal time)

FHSKIMS2.AYY Free-flow (uncongested) interzonal travel impedances for HOV travelers in TranPlan format. (No terminal time, no Intrazonal time)

5.3 Model Procedure The portion of the Highway Network module that updates the highway network is shown in Figure 5.1 below. The steps that are being performed are described in the following:


35

Figure 5.1 - HNET Model Stream

(1) Speed Capacity Lookup uses the dBase formatted SPDCAP file and converts it into a lookup table for the Voyager NETWORK process. The value being looked-up is the combination of area type, facility type and number of lanes. It should be noted that in a Voyager script syntax, only a single value can be used for lookup within a lookup table, and that the built-in functions of Voyager for speed and capacity lookups only allow for 1-digit Area and Facility Types. So, in order to lookup a combination of the area type, facility type and number of lanes for a link, a temporary value INDEXVAL is created for each combination for which an effective speed and capacity is specified in the input. The lookup functionality can then return the proper speed and capacity to be applied to each link. Any combination not found in the SPDCAP file will return a zero for both the speed and capacity and an error will be recorded in a file NETWORK.ERR in the Cube working directory.

A text, column-delimited output file, SPDCAP.TXT, is generated for the lookup function used by the module step 8, NETWORK process and an error message file, SPDCAP.ERR,


36

is then created for reporting erroneous speeds and capacities of the lookup table in the HNET web-based report.

(2) VFACTORS Lookup module step prepares the lookup table to be used for the UROAD, CONFAC, BPRLOS, and BPREXP attribute / constants and coefficients that are added to each link of the Base_YYA.NET. The UROAD parameter is applied to highway capacities to calculate the practical capacity for each link. Generally, this is Level of Service (LOS) C. The CONFAC parameter is used to factor the capacities of each link in the highway network from hourly to daily equivalents, generally at Level of Service (LOS) E, for computation of the daily volume over capacity ratios in the highway assignment.

A text, column delimited output file VFACTORS.TXT is generated as a lookup file for use in module step 8, NETWORK process and an output file VFACTORS.PRN is then created for reporting in the HNET HTML reporting page.

(3) In the first Turn Penalty step, the TURN_YYA.PEN file, which has been converted from

the original TranPlan formatted TCARDS.YYA into a Voyager formatted file, is converted again into a TURN_YYA dBase file used for reporting. As a Voyager formatted turn penalty input file, the TURN_YYA.PEN file can be used with the Voyager network for editing. This file is a free format text file with the time penalties in minutes, while in the original TCARDS.YYA file all the time penalties are in hundredths of minutes.

(4) In the second Turn Penalty step, the TURN_YYA dBase file is used to generate a time only PENALTY dBase database file that will be used later in the HPATH Output, module step 16. Reports on the time penalties and turn prohibitors are also prepared here from the TURN_YYA dBase file as two separate HTML reports on the Highway Network reporting page.

(5) In the Toll Link step, reports on the toll attributes including the toll number, car toll, service time, toll plaza description, and etc. are prepared for all toll links from the TOLLLINK_YYA dBase file which was converted from the original TranPlan file format. A text, column delimited output file TOLLLINK.TXT is generated minus the CTOLL record, but the dBase file version is used directly as a lookup file in the step 8, NETWORK process which joins the toll data directly to the highway network. An output file TOLLLINK.XML is created for reporting use in the Highway Network reporting page. TOLLLINK1.TXT is also created as a fixed formatted text file to be used later for the Mode Choice model which contains the same toll content as the original TranPlan format, including the insertion of the CTOLL=??.?? record that is used by the user program in the Mode Choice module. Otherwise, CTOLL has been created as a key {CTOLL} for this parameter.

(6) In the Station Data step, the Transit Station data in the converted dBase file STATDATA is used to generate an HTML report for the station data and to generate the station data text file that is later used in the Transit Network module, for use with the non-transit connector generating user programs. The station data in the dBase file STATDATA is


37

then used as a node input file in the step 8, NETWORK process to apply the station data to the highway network. The file has all of the same attributes as used in the previous TranPlan models so that it specifies the node numbers where the transit stations are located, and assigns the associated attributes such as station number, service area, available parking space, and etc. to those nodes in the base network. Once this file has been to the network, these station attributes will be saved in the binary network and carried forward through the rest of the model flow.

(7) In the Terminal Time step, terminal times are prepared from the TERMTIME dBase file into a lookup table TERMTIME.TXT to be used in the step 13, HIGHWAY process. In TBRPM v5.2, and previous TranPlan model versions, the terminal times are looked-up from the PROFILE.MAS based on the area type of each TAZs centroid. In TBRPM v6.0, the terminal time database, TERMTIME.DBF, was created and stored in the base scenario directory for this use.

(8) The Build Highway Network step is used to prepare the Cube Voyager binary highway network, BASE_AYY.NET, which is the starting network in the TBRPM v6.0, for use in the rest of the highway network processing. The toll link file TOLLLINK.DBF is used to update the link attributes in the base network for links which are toll links and the station file STATDATA.DBF is used to update the node attributes of the nodes which are the transit stations with their information.

The LINKMERGE phase is invoked during this step, and the fundamental link attributes such as link distance and travel time (TIME and TIME2) are calculated and speeds and capacities are looked-up from the SPDCAP.TXT file. The VFACTORS.TXT file is also used to join the UROAD, CONFAC, and other attributes into the network. The toll facilities are involved in the highway network from this step forward and their toll impedances are updated to each toll link along with the impedance of the non-toll highway links in this step. Generally, the Impedances for toll and non-toll facilities are calculated as follows:

IMPED = CTIME * TIME + CDIST * DIST (for non-toll links) IMPED = CTIME * (SERVT+TIME) + CTOLL * TOLL (for toll links) where: CTIME = time coefficient TIME = the travel time on the link CDIST = distance coefficient DIST = the link distance SERVT = service time at toll booths CTOLL = constant time value of toll TOLL = the link toll cost

In TBRPM v6.0, CTIME = 1.0, CDIST = 0, and CTOLL = 0.10. Therefore,


38

IMPED = TIME (for non-toll links) IMPED = (SERVT+TIME) + CTOLL * TOLL (for toll links)

According to the Toll Facilities Model, as implemented in TranPlan, the acceleration and deceleration delay before and after the toll booth also needs to be calculated here. The acceleration rate a1 is always set to 2.5 mph / sec, and the deceleration rate a3 is calculated by a linear interpolation between 6.2 mph / sec at an approach speed of 70 mph and 4.0 mph / sec at an approach speed 30 mph. The constant acceleration rate is defined by the key {ACCELRATE}.

The acceleration delay at the toll plaza is calculated as follows:

Acceleration Delay at Plaza = Approach Speed / acceleration rate / 2

The deceleration delay at the toll plaza is calculated as follows:

Deceleration Delay at Plaza = Approach Speed / deceleration rate / 2

The link attribute LINKCOST is used to represent the impedance including all toll equivalent time. The link attribute TOTALCOST includes toll equivalent time and the acceleration / deceleration delay.

(9) The Mark the Toll Acceleration / Deceleration Lanes step is used to update the highway links before and after the toll links which represent toll booths, so where links have a toll type=1, the links that immediately join to toll links are marked as acceleration / deceleration lanes.

(10) The Calculate the Acceleration / Deceleration Delay step is used to calculate and save the link attribute DELAY for each acceleration and deceleration link. The link attribute TOTALCOST is then also updated with LINKCOST + DELAY for these links. The unloaded network, UNLOADED_AYY.NET, which is the final output network at this step which is then used for the rest of the mode chain.

(11) Generate LINKS and XY Database step creates and stores dBase versions of the network links and nodes in the scenario output directory used following steps for reporting purposes.

(12) Generate HNET Report step prepares the output reports for HNET which includes reports on the number of links by area type and facility type, the average validated speed by area type and facility type, the capacity by area type and facility type, and other basic network information reports including information about toll links, transit stations, VFACTORS, time penalties and turn prohibitors.

(13) At the Highway Free Flow Skim step, terminal times need to be added to the model networks for skimming times that will be used in the gravity model for Trip Distribution. Previously in FSUTMS, a user program TTPREP was used to lookup the terminal time for each TAZ based on the area type of the centroid connectors. When there is only one centroid connector that exists for a TAZ there is no problem in determining the Area Type for the centroid. However, there is some confusion as to what the correct Area Type is when more than one centroid connector exists and each has a different Area Type


39

designation. In TTPREP, when there is more than one link connected to the TAZ centroid, the Area Type was assigned based on the first entry in the network that was linked to that centroid, or the centroid link with the lowest network BNODE number not including the centroid number itself, and not the last entry to the network, or the one that had the highest network BNODE number connected to that centroid. Some of the FSUTMS conversions to Voyager had scripts that adopted the Area Type of the connector that had the highest BNODE number. To make the validation results match as closely as possible to the previous TranPlan model versions, the TBRPM v6.0 uses the area type of the centroid connector with the lowest BNODE number as the area type for terminal time.

After the terminal times are computed, the highway network is skimmed for Free-Flow and Free-Flow with HOV paths. A detailed path trace report is generated here for one node pair based on the {FromNode} key value as the origin TAZ and {ToNode} key value as the destination TAZ as described earlier.

(14) The Zero out Paths without Trips step is used to zero out those path in the skim files that are not really used since there are no trip ends either originating in or terminating in the specific TAZ. These TAZs would generally be dummy TAZs that have no SE data at all. This allows for analysis of the shortest paths that are actually used by the model.

(15) Convert to TranPlan Format Skim Matrices step needs to take the LOS output matrices of the previous step and convert them into TranPlan formatted matrices which is the format still used in the FORTRAN based Mode Choice user program. New for this conversion to Voyager is the adoption the MIAMODUB Mode Choice user program from the Miami North Corridor Transit Study Model. It should be pointed out that there were three skim matrices in the previous TBRPM v5.2 that are correspondingly generated here:

(a) FHSKIMS.AYY no intrazonal skims, no terminal times, LOV skim, used for mode choice.

(b) HFSKIMS.AYY no intrazonal skims, no terminal times, HOV skim, used for mode choice.

(c) FHSKIMSUP.TEM added intrazonal skims and terminal times to the FHSKIMS.YYA LOV skim, and maxed out the EE skim times to 200 minutes, which is used for the gravity model.

The units in the TranPlan matrices are in hundredths of miles and hundredths of minutes, while the units in Voyager matrices are in miles and minutes with default 2-decimal point accuracy. The accuracy which is stored in the matrices can be adjusted as necessary.

(16) The Generate HPATH Output Report step takes the reports that were generated in this module along with some it generates and creates the HPATH web-based report page which includes:

A detailed path-trace report from {FromNode} to {ToNode}.


40

A detailed distance and time1 (no toll, no penalty), and time2 (with toll and time penalty) report from an origin zone specified by the catalog key {SkimZone}.

(17) The Record the time stamp step is used to create the SVG files needed for the web-

based reports and record the time stamp for when then current module has finished.

5.4 Standard Output The HNET web-based reports include the following reports as shown in Figure 5.2:

Highway Network Area Type Highway Network Facility Type Number of Links by Area Type and Facility Type (Single Digit) Number of Links by Area Type and Facility Type (Double Digit) Average Speed by Area Type and Facility Type (Double Digit) Average Capacity by Area Type and Facility Type(Double Digit) VFACTORS Toll Links Transit Stations Time Penalty Turn Prohibitor

Data Checks / Application

Facility types (FT), area types (AT), and number of lanes (NL) - using plots by annotation or by colors.

Centroid Connectors should be verified against TAZ polygon locations, local street and land use maps.

All links should have facility type (FT), area type (AT), number of lanes (NL), link group (LG), screenline (SL), and geographic location (GL) codes.

FIHS facilities should have corridor segment codes. The HPATH web-based reports include the following reports as shown in Figure 5.3:

A detailed path trace report from {FromNode} to {ToNode} A detailed distance and time1 (no toll, no penalty), and time2 (with toll and time penalty)

report from an origin zone specified by the catalog key {SkimZone}. Data Checks

Add turn prohibitor or turn penalty records to the TURNS_YYA.PEN file for any prohibited or extremely difficult movements when revising network. Toll Facilities should be coded in the highway network with the appropriate toll Facility Type and with appropriate toll attributes (cost, service time and number of toll booths) in the TOLLLINK_YYA dBase file. Use Cube to check for logical paths between two TAZs based on time or distances. The detailed path reports above should be used in double-checking paths being generated.


41

Figure 5.2 - Highway Network Reporting Page


42

Figure 5.3 - Highway Path Reporting Page

Figure 5.4 shows an example report for the Highway Network Reporting page and Figure 5.5 shows an example report for the Highway Path Reporting page.


43

Figure 5.3 - Example Highway Network Report


44

Figure 5.4 - Example Highway Path Report


45

Chapter 6 - Trip Distribution

6.1 General Description Trip distribution is the matching of Zonal trip productions to trip attractions. In FSUTMS this is accomplished through the use of a gravity model. The gravity model is based upon the concept that the desirability of traveling to a particular zone is directly related to the amount of activity in each potential destination zone, and inversely related to the perceived spatial separation (the highway impedance) between the production and the attraction zones. This spatial separation is measured in terms of travel time. The inverse relationship to highway impedance is assumed to be nonlinear and is modified by friction factors. The friction factor is an exponent of highway impedance analogous to the square of the distance that appears in the Newtonian gravity equation. In addition to the matching of trip productions to trip attractions, the distribution module also performs other additional functions including: Pre-loading of the highway network; and Development of congested travel time skims for input into later steps of the model. The results of these functions, in turn, become inputs for transit network development and mode choice estimation.


Table 6.1 - Trip Distribution Inputs and Outputs


PROFILE.MAS MODE9.SYN ZDATA1.YYA PCWALK.YYA A1DECK.TEM

DISTRIB (TranPlan Format) Used in Pre-Mode Choice

HTWRKDEF.AYY HTNWKDEF.AYY RHSKIMS.AYY RHSKIMS2.AYY

GEN_PANDA.DBF EETAB_AYY.MAT FREESKIMS_AYY.MAT

DISTRIB (Voyager Format)

CONGSKIM_AYY.MAT CONGSKIM_HOV_AYY.MAT TTEIEE_AYY.MAT DIST.HTM MODEIN.TEM

INPUTS:

MODE9.SYN Calibrated constant and coefficient parameters for the RTA nested logit mode choice model (MODMIAUB.EXE).

ZDATA1.YYA Zdata1 generated from ZDATA1.DBF.


46

PCWALK.YYA File containing the proportion, or percent of each zones productions and attractions that are within walking distance of the transit system by short and long walk criteria.

A1DECK.TEM TAZ attributes for mode choice calculations which include terminal times, parking costs, percentages of person trips by auto ownership, and CBD or Exurban flags.

GEN_PANDA.DBF Trip Generation output database used as a input file

EETAB_AYY.MAT EXT output matrix.

FREESKIMS_AYY.MAT HNET / HPATH output, LOS matrix.

TranPlan Format OUTPUT: HTWRKDEF.AYY Highway trip tables for work trips which include LOV (low

occupant vehicle or drive alone) and HOV (high occupant vehicle or vehicles with two or more occupants).

HTNWKDEF.AYY Highway trip tables for non-work trips which include LOV (low occupant vehicle or drive alone) and HOV (high occupant vehicle or vehicles with two or more occupants).

RHSKIMS.AYY Restrained (congested) skims of cost, distance, and time impedances for network without HOV.

RHSKIMS2.AYY Restrained (congested) skims of cost, distance, and time impedances for network with HOV.

Voyager Format OUTPUT:

CONGSKIM_AYY.MAT Restrained (congested) skims of cost, distance, and time impedances for network without HOV.

CONGSKIM_HOV_AYY.MAT Restrained (congested) skims of cost, distance, and time impedance for network with HOV.

TTEIEE_AYY.MAT Matrix file containing Truck (heavy and light duty), Taxi, external-internal (EI), and external-external (EE) trip tables.

MODEIN.TEM Person Trip table including HBW, HBNW, and NHB trips as an input of those trips subject to mode choice.

DIST.HTM Web-based Distribution Report


47

6.3 Model Procedure

Figure 6.1 - Trip Distribution Model Stream

(1) Generate Skim for Gravity Model The LOS matrix FREESKIM_AYY.MAT that is generated by the Network module includes the impedance (TIME2) which is the total travel time, turn penalties, toll equivalent time, and acceleration / deceleration delay time for all given paths. This step is where the matrix is updated with terminal time for each node pair and when the EE path impedances are maxed out to eliminate any Internal-Internal (II) trips from using EE paths.

(2) K Factor Matrix The K Factor matrix is generated here to be used in the gravity model of the next step to ensure that Home-Based School (HBSC) trips are contained within each county.


48

(3) Trip Distribution This is the application of the Gravity Model to the Production and Attraction trip ends using the k-factor matrix, Friction factor file from the Base scenario directory, and the adjusted Free-Flow skim from step 1.

(4) Bucket Rounding is used in this step to round off the trips that come out of the gravity model. This ensures the best possible match to the number of trips after the gravity model to the number of productions as input.

(5) Matrix manipulation is used to combine trip purposes into what is needed for the preliminary assignment to get the congested network.

(6) Preliminary Mode Split runs the mode choice program used to estimate the auto only trips dividing them into Drive Alone and Share Ride vehicle trips in order to closely match the calibrated auto occupancy, ignoring those person trips to be used later for the transit mode choice splits.

(7) Generate Preliminary Highway Assignment Trip Table (8) Preliminary Highway Assignment (9) Update the Congested Travel Time

For the preloaded network, the travel time related attributes need to be updated based on the congested travel time.

(10) The Congested Skims or Congested LOS matrix for the highway network include with only non-HOV lanes and the network with HOV lanes.

(11) Equivalent Congested Skims for Mode Choice are converted from the Voyager format for use by the FORTRAN user program.

(12) Update the Congested Skim with terminal times and maximize EE path times as for the Free-Flow skim earlier.

(13) Run the Congested distribution for Home-Based Work (HBW) trips (14) Bucket round the HBW distribution results (15) Calculate and report the Average Uncongested Trip Lengths for all purposes (16) Number of Free-Flow Trips by Minutes

This step calculates the number of trips grouped by trip length in minutes and creates a database of the output. A web-based HTML report of the same output is also prepared in this step.

(17) Average Congested Trip Length This step calculates the average trip length by purpose using the congested skim. A database and HTML formatted report of the output are then created.

(18) Number of Congested HBW Trips by Minutes This step calculates the number of trips grouped by trip length in minutes and creates a database of the output. A web-based HTML report of the same output is also prepared in this step.


49

(19) Distribution Report The combined HTML web-based Distribution reports are prepared in this step.

(20) Record Time Stamps Record the final time stamp with the full Distribution process is complete.

6.4 Model Output The HNET web-based reports include the following reports as shown in Figure 6.2:

Highway Skim from {SkimZone} (free flow time + Term Time + Intrazonal) Average Trip Length (Free Flow) Trip Length Frequency Distribution Figures (Tables Available in Detailed Report) Average Trip Length (Congested)

Figure 6.2 - Trip Distribution Reporting Page


50

Chapter 7 - Transit Network

7.1 General Description The Transit Network Model (TNET) builds the transit network files, TNETAM.NET, and TNETMD.NET, which contains the transit network attributes developed from the transit route files, TROUTEAM_YYA.LIN and TROUTEMD_YYA.LIN, the optional link files, OPLINKAM.DBF and OPLINKMD.DBF, the highway / transit speed conversion files, TCURVE.DBF and TSPEED.DBF, and the station data file, STATDATA_YYA.DBF. Transit access is developed using the three automated programs sidecon9, walkcon9 and autocon9. The sidecon9 program generates sidewalk link additions at transit stations, Park-N-Ride lots, and transit centers. Additional walk links can be created from special files, SIDEWALKAM.AYY and SIDEWALKMD.AYY, to provide access to these facilities from nearby TAZs. The walkcon9 program develops short and long walk access connections to the transit system. The walkcon9 program creates the special files, CODWAM.AYY and CODWMD.AYY, which contains the walk times that are used in short walk and long walk calculations in the Mode Choice Model (MODE). The autocon9 program develops auto access

Date post:	11-May-2018
Category:	Documents
Upload:	dinhdang
View:	215 times
Download:	1 times

Tampa Bay Regional Planning Model Cube Voyager Conversion - Procedural Guide 2007… · ·...

Documents