New York Best Practice Model (BPM) For Regional Travel Demand Forecasting

Transcription

1 New York Best Practice Model (BPM) For Regional Travel Demand Forecasting New York Metropolitan Transportation Council (NYMTC) NYBPM User Documentation May 2004 Prepared by Parsons Brinckerhoff / PB Consult

2 Table of Contents SUMMARY OF BPM DEVELOPMENT SECTION 1 REGIONAL TRAVEL--HOUSEHOLD INTERVIEW SURVEY 1-2 DATA DEVELOPMENT 1-3 NETWORKS 1-3 MODELS 1-10 PRE-ASSIGNMENT PROCESSOR 1-12 EXTERNALS 1-12 HIGHWAY NETWORK PREPARATION PROCEDURES SECTION 2 CREATING A NEW SCENARIO DIRECTORY 2-1 PROJECT TIP CODING 2-4 PREPARING SOCIO-ECONOMIC DATA 2-12 UPDATING THE SCENARIO MANAGER FOR A NEW SCENARIO 2-14 BUILDING A NEW HIGHWAY NETWORK FROM CODED PROJECTS 2-16 BUILDING NEW PERIOD HIGHWAY NETWORKS 2-19 BUILDING PERIOD NETWORKS WITH BUS PRELOADS 2-30 CREATING HIGHWAY PRE-SKIM PROCEEDURES 2-39 USING THE TRIP TABLE INFLATION PROCEDURE 2-41 TRANSIT NETWORK CODING AND PROCEDURES SECTION 3 TRANSIT NETWORK DATA CODING 3-2 PREPARING TRANSIT DATABASE NETWORK AND SKIMS PROCEDURES 3-3 RUNNING THE CORE MODEL COMPONENTS SECTION 4 CREATING TRANSIT AND HIGHWAY ACCESSIBILITIES 4-2 HOUSEHOLD AUTO JOURNEY PROCEDURES 4-14 MODE DESTINATION STOPS CHOICE PROCEDURESG 4-22 COMMERCIAL VEHICLE PROCEDURES 4-37 EXTERNAL AUTOS PROCEDURES 4-47 PRE-ASSIGNMENT PROCESSOR PROCEDURES 4-56 HIGHWAY ASSIGNEMTN PROCEDURES 4-65 TRANSIT ASSIGNMENT PROCEDURES SECTION 5 ADDITIONAL MODEL COMPOENTNS SECTION 6 TRIP TABLE ADJUSTMENT PROCEDUE 6-2 USING THE ZIPING AND EXTRACTION TOOL 6-7 RUNNING THE ENTIRE HIGHWAY MODEL IN ONE-STEP 6-14 RUNNING THE SUB-AREA EXTRACTION MODEL 6-21 INDEX AND FLOWCHARTS SECTION 7 GLOSSARY 7-2. NYBPM: FILES DESCRIPTION 7-10 FLOWCHARTS 7-16

3

4 Summary of BPM Development SECTION 1 REGIONAL TRAVEL--HOUSEHOLD INTERVIEW SURVEY 1-2 DATA DEVELOPMENT 1-3 NETWORKS 1-3 MODELS 1-10 PRE-ASSIGNMENT PROCESSOR 1-12 EXTERNALS 1-12 Page 1-1

5 Summary of BPM Development Regional Travel--Household Interview Survey The Household Interview Survey was conducted between February 1997 and May The survey was in the form of a 24-hour travel diary, requiring each member of the household to describe every journey taken on that day. The households were selected at random for each of the 28 counties in the area. For the 14,441 households given surveys, 11,264 completed and returned them. Each household was assigned a travel day for which to complete their 24-hour travel diary. Of the completed surveys, 10,971 were for weekdays and 275 were for weekends. The data from the survey was collected into 6 database files: Household, Person, Place, Vehicles, Location, and an Audit File. The Household database lists the characteristics of the 11,264 households. The Person database lists the characteristics for 27,369 persons responding to the survey. The Place database lists all the places (118,134 places) listed as destinations by the survey participants. The Location database gives the longitude and latitude for these places (55, 349 records). The Vehicle database gives the characteristics of the vehicles used (17,517). The consultant team then combined these databases into files for analysis, such as origindestination trip tables, and developed travel measures for each person (purpose, mode). Then weights were applied to account for the sampling process, with respect to telephone ownership, and non-response bias. The first weight is applied to adjust the weekday data to correct for differential rates due to the sampling process and telephone ownership patterns. The five elements of this weight include the probability of selection in the sampling plan, multiple phone numbers for one household, multiple households sharing one phone number, episodic telephone ownership, and the normalization of weights. The second weight is used to adjust for possible non-response bias found by comparing the RT- HIS sample to the 1990 census results). The factors adjusted for were household income, household size, and the number of vehicles owned per household. The final weight normalizes the data based on the weights used above and includes a countywide re-factoring to match the distribution of households per county. Finally, the data is expanded by an average factor of 655. Page 1-2

6 Data Development Socio-Economic Data Forecasts Data Contents and Structure The forecast data items are the same set of SED measures that were used for estimation and calibration of the BPM. Identically formatted basic files have been created for each of these three years, with 15 SED data items for each of the 3,586 transportation analysis zones (TAZs) in the 28 county NYMTC model region. Methods and Assumptions The Default SED forecasts have been developed using two basic assumptions: Growth in population, employment and labor force should match the regionally adopted county level forecasts for these primary SED measures. The projection of other SED items, such has number of households, and household income growth (not explicitly included in the adopted forecasts series) can be grown at the county level based on the Household Model developed by Urbanomics, as part of Track 8 of the NYMTC Transportation Models and Data Initiative. Networks The highway network consists of 28 counties and 3,586 zones with 118 external stations spanning New York, New Jersey, and Connecticut. Of these counties, twelve match the GIS, Tiger/Line street base. The highway network database consists of standard link attributes as well as a Physical Link Type field that is used to determine the free flow speed, capacity per hour per lane, and the type of vehicle density function in the NetPrep program. For each base highway network, there are 4 derived period networks: AM peak (6 10), midday (10 A 3 P), PM peak (3 7), and night (7 P 6 A). In order to enhance assignment accuracy, the Base Network is used to create four separate networks by time period (the Period Networks ), and those networks are used as the basis for traffic assignment. However, the Base Network is the principal file that the user will work with (edit, update, etc.) using coded changes and projects to be added to the base. Most of the data used to define the highway network was drawn from existing sources such as networks developed for previous studies. A substantial amount of information was collected, reviewed, and checked. Most of this data is not needed in order to define the new NYMTC network, but the consulting team wanted to leave an audit trail indicating the source of each data field and providing some information about manipulations and adjustments that were made along the way. The following tables give the codes used in the highway network for county, functional class, design elements, access control, usage restrictions, ramp type, link directionality, signal density, driveway spacing, median, turn lane, and TransCAD link type. Page 1-3

7 Table 1A.1 County Codes Code Description 1 New York (Manhattan) 2 Queens 3 Bronx 4 Kings (Brooklyn) 5 Richmond (Staten Island) 6 Nassau 7 Suffolk 8 Westchester 9 Rockland 10 Putnam 11 Orange 12 Dutchess 13 Fairfield 14 Bergen 15 Passaic 16 Hudson 17 Essex 18 Union 19 Morris 20 Somerset 21 Middlesex 22 Monmouth 23 Ocean 24 Hunterdon 25 Warren 26 Sussex 27 New Haven 28 Mercer Page 1-4

8 Table 1A.4 Functional Classification Codes Code Description 1 Rural Interstate 2 Rural Principal Arterial 6 Rural Minor Arterial 7 Rural Major Collector 8 Rural Minor Collector 9 Rural Local 11 Urban Interstate 12 Urban Other Freeway and Expressway 16 Urban Minor Arterial 17 Urban Major Collector 18 Urban Minor Collector 19 Urban Local 20 Ramp 996 Dummy Link 997 External Station Connector 998 Premium Transit Station Zone Connector 999 Centroid Connector Note: Functional classification codes 1-19 are used by NYSDOT. Codes 20 and higher are unique to this model. Page 1-5

9 Table 1A.5 Design Standard Codes (DESIGN) Code Description 1 Standard design elements (grades, clearances, curves, lane widths, medians, shoulders, etc.) 2 Below-average design elements 3 Poor design elements Table 1A.6 Access Control Codes (ACCESS) Code F P L N Description Full control (freeways and most parkways) Partial control (principal highways with some signalized intersections) Limited control (high-type arterials, grade-separated interchanges at major roadways) No access control Table 1A.7 Usage Restriction Codes (xx_rest, xx = time period) Code Description NT No heavy trucks 2+ Only vehicles with 2 or more persons (HOV2) 3+ Only vehicles with 3 or more persons (HOV3) NR No restrictions Page 1-6

10 Table 1A.8 Ramp Type Codes (RAMPTYPE) Code HS O (1) I (2) D Description High-speed ramp, such as a slip ramp or a directional ramp for a flyover Outer cloverleaf ramp Inner cloverleaf ramp Diamond ramp Notes: The letter O. The capital letter I. Table 1A.9 Link Directionality Codes (DIR) Code Description 0 Two-way link 1 One-way link, operating in the topologically forward direction (i.e., as the link was originally created, from A node to B node) -1 One-way link, operating in the topologically reverse direction (i.e., opposite to the way the link was originally created, from B to A) Table 1A.10 Signal Density Codes (SIGNAL) Code NA L M H Description Not applicable (freeways, ramps, other roadways with no signals) Low number of signals (2 or fewer per mile) Medium number of signals (2 7 per mile) High number of signals (more than 7 per mile) Page 1-7

11 Table 1A.11 Driveway Spacing Codes (DRIVEWAY) Code NA L M H Description Not applicable (i.e., freeways, ramps, other roadways with no driveways) Low number of driveways (3 or fewer per mile) Medium number of driveways (3 7 per mile) High number of driveways (more than 7 per mile) Table 1A.12 Median Codes (MEDIAN) Code A S N Note: Description Median always exists (i.e., more or less continuous on this link) Median sometimes exists No median Median means any kind of median treatment, including concrete barrier, raised curb, or striped pavement, several feet wide. Table 1A.13 Turn Lane Codes (TURN) Code NA A S N Description Not applicable (i.e., freeways, ramps, other roadways with no turn lanes at intersections) Always have left turn lanes at intersections, or left turns prohibited, or have continuous two-way left turn lane Sometimes have left turn lanes or prohibit left turns No separate left turn lanes (but left turns are permitted) Page 1-8

12 Table 1A.14 TransCAD Link Type Codes (TCTYPE) Code Description 0 External or other dummy link 1 Zone centroid connector 2 Premium transit station zonal connector 3 Normal roadway link, 2-way 4 Normal roadway link, 1-way The physical link type attribute is assigned in the NetPrep program. The program examines a series of coded attributes and then automatically assigns the link to one of 21 physical link types (PLTs). These PLTs are then used as an index (along with area type) to look up the freeflow speed and capacity values for each link. Truck Penalty The value of the truck penalty depends upon the truck flag (trucks allowed or restricted) on the link, area type, and physical link type (PLT) as follows: Table 1 TRUCK* PLT Penalty(min/mi) , , *TRUCK = 1 : trucks are allowed Table 2 TRUCK* TRUCK_USG** Penalty(min/mi) *TRUCK = 2 : trucks are restricted **TRUCK_USG = 1: truck frequency is less than 500 per day **TRUCK_USG = 2: truck frequency is between 500 and 1,000 per day **TRUCK_USG = 3: truck frequency is more than 1,000 per day Page 1-9

13 Table 3 TRUCK* AREATYPE PLT Penalty(min/mi) , ,7-8, *TRUCK = 2 : trucks are restricted 5-6, Models Micro-Simulation Choice Models The probabilities for the model are based on choice models but the predicted outcome is based on a Monte Carlo estimation. Due to the random number generator seeds, the model results are variable. Household Auto Journey In the household synthesis model, a random number is drawn for each household in the zone then assigns the households to one of 288 household types (6 household size categories by 3 household income groups by 4 number of worker categories by 4 number of children categories). Then, the number of non-working adults is calculated for each household. The auto ownership model is a logit model that uses the household data (income, number of workers, number of adult non-workers, density and accessibility) from the transit/highway accessibility and household synthesis models to estimate the probability of no cars, one car, two cars, or more than 3 cars for each household. A random number is drawn to determine the auto ownership category for each household. The journey frequency model is a logit model that estimates the frequency that a person makes 0,1,2 or over 3 journey pairs a day. A journey is a trip from an origin to a destination. This model uses paired journeys, otherwise known as tours. Journey frequency modeling on the individual level is based on a hierarchy of probabilities for an individual in a household based on the decisions of the other members of this household. The model also uses independent variables such as income, automobile ownership, the number of vehicles compared to the number of workers, whether a child is home alone, or if a work is not working to decide an individual s journey frequency. So, a child staying home from school will necessitate a worker or non-worker staying home, with the higher probability given to the nonworker staying home. Page 1-10

14 MDC Stage1 This step uses a custom program to select the destination of every disaggregate journey and then determine the walk/motorized split and the motorized mode in a recursive loop. The application for the destination and mode choice model uses the following inputs: Individual journey file produced by the journey-frequency model with non-motorized journeys separated by the pre-mode choice model; in this file household characteristics are attached to each journey including the origin (residential for all purposes except journeys at work ) zone, Destination and mode choice model coefficients, OD-related matrices of mode utilities (without household variables) computed at the previous calibration stage see section 3.2, Destination attractions for motorized travel (total attractions after subtracting the modeled non-motorized journeys). The application procedure proceeds through three stages: Preparation of the OD probability tables and scaling the totals, Micro-simulation in order to attach destination zone and mode to each individual journey record, Aggregation of the micro-simulation results into OD demand matrices by modes. MDC Stage 2 The stops model can be broken up into two parts: the stop frequency model and the stop location model. In the stop frequency model, each paired journey created in MDC Stage 1 is assigned to one of 4 alternatives: no stop, one stop on the inbound leg, one stop on the outbound leg, and one stop on both the inbound and outbound leg. The model uses the trip purpose, person type, income, household composition, the number of other journeys within the household, and auto sufficiency as inputs. The stop location model assigns locations for the stop events created in the stop frequency model. The location on the stop must be within a five-mile radius from the origin or destination or within a 20% deviation from the route. The model also uses purpose, person type, and mode as inputs. Page 1-11

15 Pre-Assignment Processor The PAP model uses a custom program to apply the Time Of Day distribution to daily journeys in order to obtain sets of origin destination trip tables for the four time periods. It also converts the disaggregate microsimulation records to origin-destination based trip tables to be used in the highway and transit assignment. The highway trip tables produced are SOV, HOV 2 and Taxi, HOV 3, External Autos, Trucks and Commercial Vehicles these trip tables are a new format introduced in May The transit trip tables produced are Walk to Transit, Drive to Transit, Walk to Commuter Rail and Drive to Commuter Rail. Externals The External Model set contains two separate sub-models that are used for estimating different types of external auto travel. The first sub-model estimates the external-local trips (X-I). These include trips that originate in an external zone and terminate in an internal zone (i.e., a zone within the NYMTC study area), and those trips that originate in an internal zone and end in an external zone. External-local auto travel is estimated for three different trip purposes. They are home-based work (HBW) trips, home-based other (HBO) trips and non-home based (NHB) trips. The second sub-model was developed to estimate external travel for through trips (X-X). These trips pass through the study area and have both their origin and destination at an external zone. The through trip model has two sub-components. The X-X1 component is used to estimate through travel on interstate type facilities. The X-X2 component is used to estimate through travel for all other facility types. The facility type definitions used in the Highway Assignment process apply to this sub-model. For any given forecast year between 2002 and 2030, the external-local and the through trip submodels perform two functions. They provide a forecast of daily external auto travel by zone. Once these forecasts are computed, the sub-models then distribute the estimated trips. For the external-local sub-model, the trips are distributed between external stations and internal zones by trip purpose. For the through trips sub-model, the trips are distributed between the two facility categories. The EXTTRIPZ.dat output file produced by the External Models program is used as input to the Pre-Assignment Processor (PAP) Time-of-Day (TOD) process developed by AECOM. Page 1-12

16 Page 1-13

17 Highway Network Preparation Procedures SECTION 2 CREATING A NEW SCENARIO DIRECTORY 2-1 PROJECT TIP CODING 2-4 PREPARING SOCIO-ECONOMIC DATA 2-12 UPDATING THE SCENARIO MANAGER FOR A NEW SCENARIO 2-14 BUILDING A NEW HIGHWAY NETWORK FROM CODED PROJECTS 2-16 BUILDING NEW PERIOD HIGHWAY NETWORKS 2-19 BUILDING PERIOD NETWORKS WITH BUS PRELOADS 2-30 CREATING HIGHWAY PRE-SKIM PROCEEDURES 2-39 USING THE TRIP TABLE INFLATION PROCEDURE 2-41 Page 2-1

18 Creating a New Scenario Directory 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin\ as your working directory. Now click GO. 2. In the BPM Menu, click on Scenario. Page 2-2

19 3. In the Network Scenario Manager, type in a new scenario name then Click on Create.. A scenario name should follow the format of the first 4 digits being the year of the scenario, followed by a letter indicating what type of scenario this is. Common types of scenarios are: T (TIP), C (Committed), P (Plan), and N (No Build). Page 2-3

20 Project TIP Coding New Scenario highway networks are built up from the base highway network and a large number of highway project files, each of which is individually coded by the user. The project files are small networks, and only comprise the small area Step1.rsc is the GISDK program that runs in two parts: Step 1 and Step 2. First, Step 1 will export the TransCAD window into its own network. The user must then manually code new projects. Afterwards Step 2 will make these changes permanent. Later in the BPM, the Highway Network Build step will construct a new scenario highway network using the coded projects and the base highway network. Step 1 Open the base highway network and zoom to desired location. Page 2-4

21 Bring up GISDK tools through Tool/Add Ins Then load the GIS Developer s Kit Page 2-5

22 Open the GISDK resource code to be compiled. Select Step1.rsc in the 0_BPM1\6_Pgms\4_Hnet\ folder. Page 2-6

23 After it has been compiled, the code is run by using the Test button. Type STEP1 and click OK. STEP1 will select the links in the view and create two geographic files, one becomes the project file and the other is used for updating the base network. It also adds two fields to the highway layer dataview: ACTION and TEMPID. ACTION will be used by the user to code projects with 1 (Add link), 2 (Modify link), or 3 (Delete link). TEMPID is automatically computed to be a unique ID for all links and nodes. STEP1 will require a Log File, User Name, Project Directory, Project Number, and Base Highway Network to run. The Log File should be UNIQUE, so as not to overwrite any existing log files. The name chosen for it should be log(project Number)_(User Initials). Putting a.txt at the end is not necessary. The Project Number must be a 3 digit number. For example, if the project being coded is project 29, then the Project Number should be entered as 029. Also, the project n umber should be UNIQUE so as to avoid overwriting an existing project file. Page 2-7

24 After selecting the base highway layer, remember to select New Network in the Link menu and NYMTC Nodes in the Node menu (they will be highlighted blue once selected). Once STEP1 is finished running, you will see both geographic files open. Usually, a project will only be coded in the Project layer by adding links, changing link attributes, or deleting links according to the TIP coding sheets. Occasionally edits will be made to the Base layer. This will only occur when the coded changes in the Project file require a change to the base. Page 2-8

25 The editing process uses the ACTION field to specify to the Builder program what kind of edit should be done to any give link. The ACTION field currently supports the following kinds of changes: 1 = add, 2= modify and 3=delete link. So, if you add a link through the Map Editing toolbox, then you must fill in the ACTION field of that newly created link with 1. If you want to add more lanes to a link, then after making the edits to the LANESBA and LANESAB fields, enter a 2 for the ACTION code. If a link must be deleted from the network, the ACTION field must be 3 for that link. (**Remember that if a link has been added (it has been coded with an ACTION field of 1), that the user must manually edit the Zone to Link congruency file after the project coding is finished. This file is called Z2L.dbf and sits in the 0_BPM1\0_Setup\2_LUT\4_hnet folder. To add a link, simply open the file in TransCAD, go to Edit Add Records and add as many records as there are new links. Then, in the Link ID field, type in the new link ID and in the TAZ Zone field, the zone the link is in.**) When finished coding the new project, without closing TransCAD or any window in TransCAD, go to Step 2. Example 1: Add a lane to an existing link. 1. In the Project layer, use the information tool (the i tool) to click on the link. Then, edit the LANESBA and LANESAB field for all four periods. 2. Type 2 (2 is for editing) in the ACTION field for the link. 3. Go on to STEP2. Example 2: A new link must be added to the network and there is to be a new intersection connecting this link to the middle of an existing link. 1. First, the Base Layer link (the existing link) must be split. To do this, use the Map Editing toolbox to split the link. Since the link has been split in two, one half will have the old link ID and the other will have a new ID. Page 2-9

26 2. Use the information tool (the i tool) to click on the link with the old ID. In its ACTION field, type 2, this means that it has changed. 3. Use the information tool to click on the new link and type in 1 in its ACTION field, which means that it is new to the network. 4. Next, use the information tool to click on the new node, the one that was created when the links were split. Write down the values for Longitude and Latitude fields. 5. Now, go to the Project layer. Using the search tool, select to search on Coordinates (the last option). Now, type in the Longitude and Latitude values and make sure the blue star option is on. Click OK and zoom in to the Blue Star. 6. By selecting on the white arrow the toolbox and right clicking on the star, you can change the star to a circle with size 4. Now, zoom in very close. 7. Open the Map Editing Toolbox, and split the links at what used to be the blue star. Click on the green light. 8. To check if the new node is in the right position, use the information tool to see if the Latitude and Longitude values are the same as what you wrote down. They need to be exactly the same. If they aren t, join the link and try over again. 9. Now, add the new link, which is to connect to the intersection. After adding it, type 1 into its ACTION field, because it is new. Take extra care not to move the new node. If by mistake you do so while using the Map Editing Toolbox tools, click on the red light immediately. If the node is moved, then the whole Step1 process must re-done. 10. Now go on to Step 2. Page 2-10

27 Step 2 STEP2 will take these intermediate files and create two final project and changes files. It exports the two windows, updating the link and node ID to ensure no overlap with the base highway network or any other project files. STEP2 does not need to be compiled, just go to the run button on the GISDK toolbox, and type in STEP2. When STEP2 is finished, find the project *.dbd file in the 0_BPM1\1_Prep\1_Hnet\3_Proj\ folder and check to make sure all links have been coded correctly and with the correct ACTION field. Also, write down the link Ids of all new links and enter them, along with the Transportation Analysis Zone, TAZ, they are in, in the Z2L.dbf file (see the section on Building New Period Highway Networks Preparing NetPrep for more instructions on how to edit the Z2L.dbf file). Page 2-11

28 Create Socio-Economic Data Preparing Socio-Economic Data For a New Scenario Look for raw data in 0_BPM1/1_Prep/0_SED/(New Scenario Year) Copy the entire contents of the folder into 0_BPM1\2_Alts\(New Scenario)\0_Input\0_SED Running Areatype process If the areatype file is not available for a specific year, then it must be created. The areatype process is actually composed of three linked programs: Zone_pct.rsc Calczone.exe Areatype.exe The first program is rarely run. It is a GISDK routine that will take the existing zone system and create buffers of 0.5 and 1.0 miles around all zones. The outcome of the routine is a file called zone_pct.asc that indicates what proportion of neighboring zones fall within each zone s buffer. Unless the zone system changes, this file will remain unchanged, so it only has to be run once. The intent of the buffering is to smooth out the socioeconomic data so that peaks and valleys are ignored while determining a zone s areatype. It also will mean that areatype values will tend to increase or decrease gradually as one looks across the region. Calczone.exe starts with the buffer file (zone_pct.asc) and applies it to a modified version of the socioeconomic file. Six variables must be extracted from zsedbs.prn and saved into a new land-use file: zone id, zone area, HHPop, GQPop, Total Pop, Total Emp. The output from calczone will be a buffered land-use file that looks very similar to the input file. There will still be six variables for example. However, there are two differences. First, the values of each variable will have been buffered (aside from zone id). Second, the values will have been Page 2-12

29 turned into densities, i.e. the buffered total population is divided by the buffered area. Areatype.exe takes this final buffered land-use file and determines the areatype (from 1 to 11) of each zone, based on certain parameters set by the atype.asc file. This is stored in the atype.dat file, which is used by various network-processing programs. Because there is only land-use data for the internal zones (3586) and the highway network has external links, the atype.dat file must be modified so that it contains data on the external zones. The simplest method to do so is to manually edit the buffered land-use file before running areatype.exe. All missing records -- from the last internal zone to the final external zone will be filled in with a value of for buffered area and 0 for all other socioeconomic variables. This guarantees that the external zones will be treated as the most rural zones (areatype=11). Page 2-13

30 Updating the Scenario Manager for a New Scenario After creating TIP Projects, but before creating the new scenario highway network, we must edit the Scenario Manager. This needs to be done for all new, previously undefined scenarios but it does not need to be done for the base year, Also, if the user is running a scenario that does not yet exits the scenario manager needs to be updated. Otherwise the scenario manager does not need to be updated since no projects are being added. This file is called scen_mgr.dbf and sits in the 0_BPM1/0_Setup/2_LUT/4_hnet folder. To get started, open this file in TransCAD. Next, go to Dataview Modify Table In the Modify Table menu, click on Add Field Rename the added field to the scenario you created with a Y in the beginning. So, if we ve created a scenario called 2005VA, the new field would be called Y2005VA. Click OK. Now, go to Edit Add Records Add as many records as new TIP projects you have coded. Click OK In the Changes field, the first field in the file, type in CHGS plus the project number of the project you would like to add. So, if we ve created a new project with a number of 032, then we must type in CHGS032 in the Changes field. In the Project field, type in PROJ plus the project number (in this example, PROJ032 ). In the Base field, type in Y for each new record. To fill in the newly created scenario field, type in a Y for all project records to include in the new highway network. Last, fill in any remaining data for each new record, such as PIN number, County, Project Name, Completion Date, Program, Year, and Scenario Type (TIP, Committed, or No- Build). All programs will run without these fields, but for bookkeeping purposes, they should be filled out. When finished, close TransCAD. Page 2-14

31 Building a New Highway Network from Coded Projects Preparation This step only needs to be run for future scenarios. If running a base year scenario, then go on to the section on Running Network Preparations Procedures, following this section. In Windows Explorer, check to make sure all the files are in the correct directories with the correct cases. Control Files Location Size (approx.) Main.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl 4 network.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\network.ctl 7 mgrboth.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\mgrboth.ctl 4 builder1.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\builder1.ctl 28 builder2.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\builder2.ctl 28 Input Files Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN bin 18,303 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN BX 1,452 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN cdd 1 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN cdk 2 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN dbd 5 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN DCB 3 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN des 3 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN dsk 2 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN grp 2 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN lok 1,909 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN pnk 3,082 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN pts 1,944 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN r0 2,615 Base Highway Network C:\0_BPM1\1_Prep\1_HNet\0_Base\HN r1 4,063 Scenario Manager C:\0_BPM1\0_SetUp\2_LUT\4_hnet\scen_mgr.dbf 17 Project Files C:\0_BPM1\1_Prep\1_HNET\3_Proj\ Changes Files C:\0_BPM1\1_Prep\1_HNET\2_Chgs\ Output Files New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).bin 18,423 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).BX 1,453 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).cdd 1 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).cdk 2 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).dbd 5 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).DCB 3 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).des 3 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).dsk 2 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).grp 2 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).lok 1,903 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).pnk 3,077 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).pts 1,950 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).r0 2,634 New Highway Network C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\HB(Alternative).r1 4,089 Log File C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\(LogFileName) 3 Page 2-15

32 Running Highway Network Builder 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the Model Forecast Run menu, choose the scenario you would like to run. Page 2-16

33 3. By going through the folders on the left, choose the scenario year you would like to run. 4. Back in the Model Forecast Run menu; notice that the scenario has been changed to what you selected. Now, click on Scenario/Networks. Page 2-17

34 5. In the Network Scenario Manager, click on Build. 6. In the Build Network menu, again choose the scenario you would like to run and Click on Update and Build Net. This will launch the highway builder program. It will take about 10 minutes to run. Page 2-18

35 Building New Period Highway Networks Preparing NetPrep In Windows Explorer, check to make sure all the files are in the correct directories with the correct cases. Remember that the Zone to Link (Z2L.dbf) file must be updated if links have been added to the network in the Builder program. To add links to this file, open the file in Microsoft Excel and add the link and the TAZ it is in under the appropriate columns. This only needs to be done if new projects have been coded for the new scenario. If running NetPrep with Bus Preloads, please skip to the next section on Building Period Highway Networks with Bus Preloads. Control Files Location Size (approx.) Main.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl 4 network.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\network.ctl 7 netset1.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\netset1.ctl 6 trkdriver.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\trkdriver.ctl 1 netprep1.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\NetPrep1.ctl 78 plt.exe C:\0_BPM1\6_Pgms\4_hnet\plt.exe 921 trk.exe C:\0_BPM1\6_Pgms\4_hnet\trk.exe 521 Look-Up Tables SPDCAP.dbf C:\0_BPM1\0_Setup\2_LUT\4_hnet\SPDCAP.dbf 18 ATYPE.dat C:\0_BPM1\2_Alts\(Alternative)\0_Input\0_SED\ATYPE.dat 148 ATYPE.dbf C:\0_BPM1\2_Alts\(Alternative)\0_Input\0_SED\ATYPE.dbf 144 Input Files Highway Network C:\0_BPM1\2_Alts\(Scenario)\0_Input\1_HNet\HB(Scenario).dbd 5 Zone Layer C:\0_BPM1\3_GIS\1_TAZ\bpz00805.dbd 5 Zone to Link File C:\0_BPM1\0_SetUp\2_LUT\4_hnet\Z2L.dbf 888 Output Files AM Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\AM\AM.dbd 5 MD Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\MD\MD.dbd 5 PM Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\PM\PM.dbd 5 NT Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\NT\NT.dbd 5 Log File C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\(LogFileName).log 1 Page 2-19

36 Running NetPrep 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the NYMTC Best Practice Model Phase 1 menu, select the scenario to run by clicking on Select. Now, click on Scenario/Networks. Page 2-20

37 3. In the Network Scenario Manager, click on the Network tab. 4. In the Model Forecast Run Menu, choose the correct scenario. Then Click on the NetPrep button. Page 2-21

38 5. In the Highway Network Preparation menu, you will need to select which period networks you would like to create. You must choose at least one. 6. In Choose Zone System, select the current zone.dbd file. 7. For Choose Highway Network, select the highway.dbd network you would like to run NetPrep on. If running a 2002 Base Year scenario, then the highway network selected should be the base highway network stored in c:\0_bpm1\1_prep\1_hnet\0_base\hn dbd. Page 2-22

39 8. For Does Zone To Link File Exist?, click yes if you have created a Zone To Link File for this highway and zone layer; then, select the file. Page 2-23

40 9. Next, type in what you would like to call the log file created for this run. Choose a name, which will easily describe the contents of the log file. In this example, we use log2020n_ for a 2020 No-Build network created on July 18 th, When you are finished, click on Run NetPrep. 11. A TransCAD dialogue box will appear and ask you to add or delete fields. Do neither and click OK. Page 2-24

41 12. Next, another TransCAD dialogue box will ask you to change the names of the fields for all the period networks selected. If any field names are missing, click on the field that needs to be added. At the bottom of the dialogue box, click on the highway network field that needs to be added to the period files, click on the period file that is missing it, then click on the appropriate name for the field in the period network. Click OK. 13. When NetPrep is complete, in approximately 10 minutes, TransCAD will show a message saying NetPrep Complete. Click OK. Page 2-25

42 Definitions and Explanations Control Files Netprep.ctl: This program takes the base highway network and breaks it into four period highway networks. In NetPrep, all links are assigned a physical link type (PLT), area type, free speeds, and capacities. General costs for each automotive mode are also calculated for each link. Builder.rsc: This program runs in two parts. In the first run, the base network will be updated with the changes to be made. In the second run, it will create the scenario using the scenario manager and coded projects. Input Files Scenario Manager: This.dbf file contains a list of all the Changes files along with their associated Project files. For each file, there is a PIN number, Year, and Scenario type. Changes Files: The Changes Files should be in the C:\0_BPM1\1_Prep\1_Hnet\2_Chgs folder. Each change file should be a standard geographic file with its 16 other components. Each change file must have the same fields as a highway network, and contain only the number of links that need to be changed. Project Files: The Project Files should be in the C:\0_BPM1\1_Prep\1_Hnet\3_Proj folder. Each project file must be a standard geographic file with its 16 other components. Each project file must have the same fields as a highway network. Highway Network: The highway network is the map that the model will run off of. It should be a TransCAD standard geographical file with Node and NetworkLinks Layers; it should be a.dbd file with 16 other components. It is currently stored as C:\0_BPM1\1_Prep\1_Hnet\0_Base\HN*****.dbd. However, when updated for new projects through the Builder.rsc program, it will be stored in C:\0_BPM1\1_Prep\1_Hnet\1_BaseUp\HB*****.dbd. Only once a projected network has been established as the base should it be moved into the 0_Base file. The Network must have the following fields. The fields in bold type are required for running NetPrep. (Remember that TransCAD is case sensitive.) Page 2-26

43 Field Name Type Width Decimal Index ID Integer (4 bytes) 10 0 Yes Length Real (8 bytes) 10 2 Dir Integer (2 bytes) 2 0 LID Integer (4 bytes) 10 0 LID Integer (4 bytes) 10 0 LID Integer (4 bytes) 10 0 LID Integer (4 bytes) 10 0 LID Integer (4 bytes) 10 0 LID Integer (4 bytes) 10 0 NAME1 Character 30 0 NAME2 Character 30 0 NAME3 Character 30 0 COUNTY Integer (2 bytes) 4 0 FCLASS Integer (2 bytes) 4 0 DESIGN Integer (1 byte) 2 0 MEDIAN Character 3 0 ACCESS Character 5 0 SIGNAL Character 5 0 DRIVEWAY Character 5 0 TURN Character 5 0 RAMPTYPE Character 5 0 SPECIAL Character 5 0 TOT_LANE Integer (2 bytes) 3 0 AMLANESAB Integer (2 bytes) 3 0 AMLANESBA Integer (2 bytes) 3 0 AMPARK Character 3 0 AMREST Character 3 0 MDLANESAB Integer (4 bytes) 5 0 MDLANESBA Integer (4 bytes) 5 0 MDPARK Character 5 0 MDREST Character 5 0 PMLANESAB Integer (2 bytes) 3 0 PMLANESBA Integer (2 bytes) 3 0 PMPARK Character 3 0 PMREST Character 3 0 NTLANESAB Integer (2 bytes) 11 0 NTLANESBA Integer (2 bytes) 3 0 NTPARK Character 3 0 NTREST Character 3 0 SPDMOD Integer (2 bytes) 5 0 CAPMOD Integer (2 bytes) 5 0 UNIQUEID Character 12 0 SCL_LINKID Character 14 0 SPD_ID_SW Character 16 0 SPD_ID_NE Character 16 0 AUTOTOLL Integer (4 bytes) 10 0 TRUKTOLL Integer (4 bytes) 10 0 TRUCK Integer (2 bytes) 4 0 TRUK_USG Integer (2 bytes) 4 0 AMDELAY Real (8 bytes) 10 2 MDDELAY Real (8 bytes) 10 2 PMDELAY Real (8 bytes) 10 2 EditFlag Character 16 0 EditProj Character 16 0 DEF_CNT Integer (4 bytes) 10 0 RCS_ID Character 11 0 CCSTYLE Integer (4 bytes) 12 0 MULTILNK Integer (4 bytes) 10 0 Page 2-27

44 1. Zone File: This is the TransCAD standard geographical file that specifies the zone system for the network. Like the highway network, it should have a.dbd file with 16 other components. o The Zone.dbd file must have the following fields: Field Name Type Width Decimal Index ID Integer (4 bytes) 10 0 Yes Area Real (8 bytes) 10 2 AREA:1 Real (8 bytes) 10 3 TAZ_ID:1 Integer (4 bytes) 10 0 BPZ3_ID Integer (4 bytes) 10 0 REGION Integer (4 bytes) 12 0 COUNTYCODE Integer (4 bytes) 12 0 TYPE Character 3 0 TRACT1 Character 11 0 MCD Character 8 0 BG1 Character 12 0 BG2 Character 12 0 BG3 Character 12 0 BG4 Character 12 0 WPFAC Real (8 bytes) 10 6 RSFAC Real (8 bytes) 10 6 Field_2 Integer (4 bytes) 10 0 CCSTYLE Integer (4 bytes) 12 0 Zone To Link File: This is a TransCAD dbase file that contains all the links in the current highway network along with the zone that it is in. o The dbase file must have the following fields: (remember that TransCAD is case sensitive.) Field Name Type Width Decimal ID Integer 8 0 ZONE Integer 8 0 Output Files Period Files: These standard geographical files are the highway period networks created by NetPrep. They are currently stored in the working directory in folders for each period. You can only specify the working directory to be used, not what the period files are named. The period files are used for input to the Highway Assignment program at the end of the model run. Each Period File should have the following fields: (remember that TransCAD is case sensitive!) Page 2-28

45 Field Name Type Decimal Width Index ID Integer (4 bytes) 10 0 Yes Length Real (8 bytes) 10 2 Dir Integer (2 bytes) 2 0 LID Integer (4 bytes) 10 0 NAME1 Character 30 0 COUNTY Integer (2 bytes) 4 0 FCLASS Integer (2 bytes) 4 0 DESIGN Integer (1 byte) 2 0 MEDIAN Character 3 0 ACCESS Character 5 0 SIGNAL Character 5 0 DRIVEWAY Character 5 0 TURN Character 5 0 RAMPTYPE Character 5 0 AUTOTOLL Integer (4 bytes) 10 0 TRUKTOLL Integer (4 bytes) 10 0 TRUCK Integer (2 bytes) 4 0 TRUK_USG Integer (2 bytes) 4 0 SPECIAL Character 5 0 TOT_LANE Integer (2 bytes) 3 0 LANESAB Integer (4 bytes) 5 0 LANESBA Integer (4 bytes) 5 0 PARK Character 5 0 RESTRICT Character 5 0 SPDMOD Integer (2 bytes) 5 0 CAPMOD Integer (2 bytes) 5 0 ZONE Integer (4 bytes) 5 0 AREATYPE Integer (4 bytes) 5 0 PLT Integer (4 bytes) 5 0 FREESPD Integer (4 bytes) 5 0 LANECAP Integer (4 bytes) 5 0 CAPACITYAB Integer (4 bytes) 6 0 CAPACITYBA Integer (4 bytes) 6 0 TIMEAB Real (8 bytes) 9 4 TIMEBA Real (8 bytes) 9 4 IMPEDAB Real (8 bytes) 9 4 IMPEDBA Real (8 bytes) 9 4 AUTOFIX Real (8 bytes) 12 4 HOV2FIX Real (8 bytes) 12 4 HOV3FIX Real (8 bytes) 12 4 HOV4FIX Real (8 bytes) 12 4 TRUCKFIX Real (8 bytes) 12 4 TAXIFIX Real (8 bytes) 12 4 COMMFIX Real (8 bytes) 12 4 Log File: The log file written by NetPrep displays all the input files used in the NetPrep program. Page 2-29

46 Building Period Networks with Bus Preloads Page 2-30

47 Preparing NetPrep with Bus Preloads Be sure to have created the Transit Database before running NetPrep with Bus Preloads. Consult the section on Creating Transit Database for how to do this. Control Files Location Size (approx.) Main.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl 4 network.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\network.ctl 7 netset1.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\netset1.ctl 6 trkdriver.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\trkdriver.ctl 1 netprep1.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\NetPrep1.ctl 78 plt.exe C:\0_BPM1\6_Pgms\4_hnet\plt.exe 921 trk.exe C:\0_BPM1\6_Pgms\4_hnet\trk.exe 521 Look-Up Tables SPDCAP.dbf C:\0_BPM1\0_Setup\2_LUT\4_hnet\SPDCAP.dbf 18 ATYPE.dat C:\0_BPM1\2_Alts\(Alternative)\0_Input\0_SED\ATYPE.dat 148 ATYPE.dbf C:\0_BPM1\2_Alts\(Alternative)\0_Input\0_SED\ATYPE.dbf 144 HWYTRANS.dbf C:\0_BPM1\5_RunBin\4_Hnet\HWYTRANS.dbf Input Files Highway Network C:\0_BPM1\2_Alts\(Scenario)\0_Input\1_HNet\HB(Scenario).dbd 5 Zone Layer C:\0_BPM1\3_GIS\1_TAZ\bpz00805.dbd 5 Zone to Link File C:\0_BPM1\0_SetUp\2_LUT\4_hnet\Z2L.dbf 888 Transit Link Layer C:\0_BPM1\2_Alts\(Scenario)\1_Out\5_tnet\(scenario)lnk.dbd Transit Route System C:\0_BPM1\2_Alts\(Scenario)\1_Out\5_tnet\(scenario)rte.rts Output Files AM Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\AM\AM.dbd 5 MD Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\MD\MD.dbd 5 PM Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\PM\PM.dbd 5 NT Network Files C:\0_BPM1\2_Alts\(Alternative)\0_Input\1_HNet\NT\NT.dbd 5 Page 2-31

48 Running NetPrep 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the NYMTC Best Practice Model Phase 1 menu, select the scenario to run by clicking on Select. Choose the scenario year you would like to run. Now, click on Scenario/Networks. Page 2-32

49 3. In the Network Scenario Manager, click on the Network tab. 4. In the Model Forecast Run Menu, choose the correct scenario. Page 2-33

50 5. Now, click on NetPrep 6. In the Highway Network Preparation menu, you will need to select which period networks you would like to create. You must choose at least one. Page 2-34

51 7. In Choose Zone System, select the current zone.dbd file. 8. For Choose Highway Network, select the highway.dbd network you would like to run NetPrep on. If running a 2002 Base Year scenario, then the highway network selected should be the base highway network stored in 0_BPM1\1_Prep\1_Hnet\0_Base\HN dbd. Page 2-35

52 9. For Does Zone To Link File Exist?, click yes if you have created a Zone To Link File for this highway and zone layer; then, select the file. 10. To apply Bus Preloads, click on Apply Bus Preloads. Page 2-36

53 11. Next, type in what you would like to call the log file created for this run. Choose a name, which will easily describe the contents of the log file. In this example, we use log2030n_ for a 2030 No-Build network created on July 18 th, Then, Click on the Bus Tab. 12. In the Bus Tab, select the Transit Route System file to use when adding Bus Prelaods to the highway period networks. If the file does not exist, make sure that the Creating Transit Database step has been run (refer to the section on Creating Transit Database and Skimming Procedures). Also, Select the Transit Line Layer associated with this Route System. Page 2-37

54 13. When you are finished, click on Run NetPrep with Bus Preloads. 14. A TransCAD dialogue box will appear and ask you to add or delete fields. Do neither and click OK. 15. Next, another TransCAD dialogue box will ask you to change the names of the fields for all the period networks selected. If any field names are missing, click on the field that needs to be added. At the bottom of the dialogue box, click on the highway network field that needs to be added to the period files, click on the period file that is missing it, then click on the appropriate name for the field in the period network. Click OK. 16. When NetPrep is complete, in approximately 10 minutes, TransCAD will show a message saying NetPrep Complete. Click OK. Page 2-38

55 Creating Highway Pre-Skims Procedures Page 2-39

56 Creating Pre-Skims 1. First, if the new highway network is an edited version of an existing scenario, then run the highway assignment using the old trip tables of the same scenario with the edited highway network. Skims should be created for SOV (1), Truck (5), and Van (6). When running the highway assignment, remember to click Update Highway Skims on the Components screen. 2. Second, if the new highway network is part of a completely new scenario, then either use skims from a scenario that is within 5 years of the new scenario as your pre-skims or use the trip tables from the existing scenario to run a highway assignment using the new scenario network. a. To use existing skims, copy the AM and MD SOB skims (AMSKIM1.mtx and MDSKIM1.mtx) from 0_BPM1\2_Alts\(Old Scenario)\0_Input\4_Hnet\ to 0_BPM1\2_Alts\(New Scenario)\0_Input\4_Hnet\. Also, copy the truck and van MD skims (assn_md5.mtx and assn_md6.mtx) from 0_BPM1\2_Alts\(Old Scenario)\1_Out\4_Hnet\ to 0_BPM1\2_Alts\(New Scenario)\1_Out\4_Hnet\. b. To use existing trip tables, copy the trip tables (highway_am.mtx, highway_md.mtx, highway_pm.mtx, and highway_nt.mtx from 0_BPM1\2_Alts\(Old Scenario)\1_Out\3_PAP\ to 0_BPM1\2_Alts\(New Scenario)\1_Out\3_PAP\.. When finished, run the highway assignment as shown in the documentation. Skims should be created for SOV (1), Truck (5), and Van (6). When running the highway assignment, remember to click Update Highway Skims on the Components screen. 3. If there are not any existing scenarios within 5 years of the new scenario, then a matrix-factoring program to calculate new skims must be used. See the following section on how to use the matrix factoring program. Page 2-40

57 Using the Trip Table Inflation Procedure This procedure will inflate the 2002 highway trip tables to the year the user specifies. It will only create trip tables for AM and Midday, since these are the only trip tables needed to generate pre-skims (all programs either use AM or Midday skims, none use PM or Night.) So, when running the assignment, do not run a standard assignment. Instead run only periods AM and MD. 1. In the Central Process screen, click Go. Page 2-41

58 17. In the Main Setup screen, select the scenario you would like to run and Click on Utilities. 18. In the Utilities Screen, select the new scenario you would like to run. Also, type in which year to inflate the trip table matrices. This should be the same year as the new scenario. 19. Now, click on Matrix Inflation. Page 2-42

59 20. The Matrix Inflation Procedure will take 2 hours. This will create two trip tables, highway_am.mtx and highway_md.mtx, in the 0_BPM1\2_Alts\(New Scenario)\1_Out\3_PAP\ folder. Since the program only creates AM and MD trip tables, the user needs to make a copy of each and re-name it for PM and NT. A copy of highway_am.mtx should be created and renamed to highway_pm.mtx. A copy of highway_nt.mtx should be created and renamed to highway_nt.mtx. These files are not used when running the Pre-Skimming Highway Assignment, but they are necessary to run the programs. 21. Next, run the highway assignment, see the section on running the Highway Assignment later in the documentation, but only run for AM and MD periods. Do not select the Standard Highway Assignment checkbox. Page 2-43

60 Page 2-44

61 Transit Network Database and Skim Procedures SECTION 3 UPDATING TRANSIT NETWORK PROCEDURES 3-2 CREATING A NEW TRANSIT SCENARIO 3-4 CODING A NEW TRANSIT NETWORK 3-11 PREPARING TRANSIT DATABASE NETWORK AND SKIMS PROCEDURES 3-54 Page 3-1

62 Updating Transit Network Procedures Note: Accompanying this User s Guide is a supplement user s guide specifically for Transit Coding with the BPM. This document is called, Best Practice Model Transit Network Data Coding. This document describes the procedures used to setup the transit network data and processing procedures on a new computer, the required input data files, and the steps used to run the transit network processing procedures for the NYMTC BPM or the full MTA RTFM. The Transit Coding supplement contains the following sections: 1. Introduction 2. Setup Procedures 3. Alternative-Specific Basic Input Data Files 4. Alternative-Specific Supplementary Input Data Files 5. Alternative Independent Input Data 6. BPM Transit Network Coding Procedures 7. Transit Path Tracing 8. Running the BPM Transit Model 9. Detailed Program Descriptions Page 3-2

63 Preparing Transit Database Network and Skims Procedures In Windows Explorer, check to make sure all the files are in the correct directories with the correct cases. Control Files Size (approx) 0_BPM1\6_Pgms\5_tnet\utils\ZoneProc.rsc 4 0_BPM1\6_Pgms\5_tnet\programs\Adjustx.exe 381 0_BPM1\6_Pgms\5_tnet\programs\ASSNMERG.exe 316 0_BPM1\6_Pgms\5_tnet\programs\Build.exe 360 0_BPM1\6_Pgms\5_tnet\programs\Buildb.exe 372 0_BPM1\6_Pgms\5_tnet\programs\convert.exe 41 0_BPM1\6_Pgms\5_tnet\utils\buildtnet.rsc 9 0_BPM1\6_Pgms\5_tnet\programs\makecent.exe 347 0_BPM1\6_Pgms\5_tnet\programs\makecon.exe 380 0_BPM1\6_Pgms\5_tnet\programs\parsese.exe 316 0_BPM1\6_Pgms\5_tnet\programs\POSTMEGA.exe 348 ProgramFiles\TransCAD\Railfare.exe 33 0_BPM1\6_Pgms\5_tnet\utils\routerep.rsc 14 0_BPM1\6_Pgms\5_tnet\utils\runtrnmodel.rsc 31 0_BPM1\6_Pgms\5_tnet\programs\tcmx4.exe 464 0_BPM1\6_Pgms\5_tnet\programs\tran_con.exe 520 0_BPM1\6_Pgms\5_tnet\utils\trnassns4.rsc 5 0_BPM1\6_Pgms\5_tnet\utils\trnskim.rsc 65 0_BPM1\6_Pgms\5_tnet\utils\PctWalk.rsc 5 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputs.rsc 35 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputsdata.rsc 6 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputsview.rsc 5 0_BPM1\6_Pgms\5_tnet\programs\chkbus.exe 380 0_BPM1\6_Pgms\5_tnet\programs\chktnet.exe 360 0_BPM1\6_Pgms\5_tnet\programs\schedrte.exe 328 0_BPM1\6_Pgms\5_tnet\utils\ubuildtnet.rsc 17 0_BPM1\6_Pgms\5_tnet\programs\viewstat.exe 310 Page 3-3

64 Input Files Size (approx.) 0_BPM1\6_Pgms\5_tnet\utils\Altparm.rsc 17 0_BPM1\6_Pgms\5_tnet\utils\model2.dbd 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)rtem08.new _BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)chkrtem08.prn 233 0_BPM1\2_Alts\(Alternative)\0_Input\2_Tnet\(Alt)modes40.dbf 6 0_BPM1\2_Alts\(Alternative)\0_Input\2_Tnet\(Alt)modexf.dbf 17 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm01.asc 19 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm02.asc 725 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm03.asc 559 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm04.asc 224 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm05.asc 332 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm06.asc 9 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm07.asc 3 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTEm08.asc _BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)STATIONS.ASC 410 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)BUSPNR.asc 36 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PTZCON.asc 32 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)TAZCoord.asc 113 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PNR.asc 32 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PNR.geo 113 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm01.bin 5 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm01.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm01.geo 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm02.bin 76 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm02.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm02.geo 74 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm03.bin 50 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm03.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm03.geo 59 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm04.bin 30 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm04.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm04.geo 20 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm05.bin 39 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm05.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm05.geo 104 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm06.bin 3 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm06.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm06.geo 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm07.bin 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm07.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm01.geo 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm01.bin _BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm01.dcb 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnkm01.geo _BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)select.asc 25 0_BPM1\1_Prep\2_tnet\trn\conlinks\contype.asc 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SIDEWALK.GEO 186 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)Ferry.csv 9 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRBAB.csv 14 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRFAR.csv 6 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRRON.csv 15 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRHEM.csv 7 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRLON.csv 7 Page 3-4

65 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIROYS.csv 6 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRPTJ.csv 18 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRPTW.csv 8 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)LIRWHE.csv 6 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)MNRHUD.csv 11 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)MNRHAR.csv 15 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)MNRNHV.csv 35 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NJTNJC.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NJTNEC.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NJTRAR.csv 3 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NJTMOR.csv 7 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NJTBOO.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NJTPAS.csv 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NJTBRG.csv 6 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAY19.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAY23.csv 5 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAY45.csv 12 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAY6.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAY7.csv 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYGS.csv 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYAC.csv 11 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYB.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYD.csv 3 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYE.csv 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYF.csv 3 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYFS.csv 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYG.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYH.csv 1 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYJ.csv 3 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYL.csv 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYM.csv 4 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYNR.csv 5 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYQ.csv 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SUBWAYZ.csv 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)SIRTOA.csv 2 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PATH.csv 3 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)NCS.csv 1 Output Files Size (approx.) 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)modexf.dbf 17 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rter.bin 545 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rtel.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rtes.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rtes.tmp _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)megalo.asc 863 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)_lnk.dbd 5 Page 3-5

66 Running Transit Network Database and Skims Procedures 1. In Central, make sure the Primary Control File is Main.ctl. Click Go. 2. In the NYMTC Best Practices Model Phase 1 window, click on Select to choose the Scenario ID and then click on the Transit button. Page 3-6

67 3. In the Transit Processing Setup, click on Select to choose the correct Transit Scenario Parameter File. 4. Now, click on the Settings tab. Page 3-7

68 5. In the Settings Tab, check all boxes in the Build Transit Database Section. 6. ***If Running Transit Database Procedures in order to run NetPrep with Bus Preloads, skip to step 13 now do not build new skims***. Page 3-8

69 7. Now, select the boxes in the Skims section. To build both AM and MD period skims, click on Build AM Period and Build MD Period. Click on Build New Network. This step is necessary before building new skims and running a Transit Assignment. Next, click on Build New Skims to build new transit skims. Finally, to have the transit skims renamed and saved to the correct folders for the rest of the model stream, click Update Transit Skims. Page 3-9

70 8. Now click on Tran to go back to the main menu. 9. In the Transit main menu, click on Update Parameter File. Page 3-10

71 10. When that is finished running, go back to the Transit main menu. Remember to reselect the Parameter file. Now, click on Run Transit Components. This will take roughly 2 days. Page 3-11

72 Description of Files Input Files Base Link Geographic Files: (Alt_LNKM**.geo) This alternative and mode specific geographic file contains the base links used by the transit routes. They must be stored in the input directory. Base Link Data Files: (Alt_LNKM**.dcb and Alt_LNKM**.bin) These alternative and mode specific data files contain descriptive information for each transit base link in the base link geographic file. o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX ID Integer (4 bytes) 10 0 Length Real (4 bytes) 10 6 Dir Integer (1 byte) 2 0 CLASS Character 4 0 TYPE Integer (4 bytes) 12 0 NAME Character 30 0 FCLASS Real (8 bytes) 16 0 FromNID Integer (4 bytes) 12 0 ToNID Integer (4 bytes) 12 0 Direction Integer (4 bytes) 12 0 Distance Real (8 bytes) 16 2 TT Real (8 bytes) 16 2 CON_TYPE Integer (2 bytes) 12 0 XferMode Integer (2 bytes) 12 0 CT_DESCRIP Character 20 0 PREMIUM Integer (4 bytes) 10 0 NONPREM Integer (4 bytes) 10 0 DRIVE_AM Integer (4 bytes) 10 0 DRIVE_PM Integer (4 bytes) 10 0 Transit_IVTT Real (8 bytes) 10 2 LINK_MODE Integer (4 bytes) 12 0 AUTOTIME Real (8 bytes) 10 2 AUTOCOST Real (8 bytes) 10 2 CAPACITY Real (8 bytes) 10 2 Station Definition File: (Alt_STATIONS.rsc) This alternative specific data file contains all the information for stations. They ensure that all given stations are coded at the same longitude and latitude and are given the same fare zone and PTZ id. Zone Fare Definition File: This ASCII text file consists of four files defining the fair structure for ferries (Alt_FERFARE.ctl), Long Island Rail Road Page 3-12

73 (Alt_LIRFARE.ctl), Metro-North Railroad (Alt_MNRRFARE.ctl), and New Jersey Transit Rail (Alt_NJTFARE.ctl). Each file contains a record for each station, with fare zone assignments for each station. A look-up table below these defines the fare for each fare zone origin-destination pair. Mode Definition File: (Alt_MODES40.dbf) This dbase file defines the characteristics of each transit mode and is used by the transit network builder and path builder to define modes for the purpose of determining fare and establishing path-building weights. This file should not be altered, and changes to this file could negatively affect the model s consistency with calibration conditions. This file must be stored in the input directory. This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX MODE_NAME Character 22 0 MODE_ID Integer 8 0 TYPE Character 22 0 IMP_FIELD Character 16 0 FARE_TYPE Integer 8 0 FARE_FIELD Character 22 0 FARE_CORE Character 8 0 HEADWAY Real Number 10 2 FARE Real Number 10 2 XFARE Real Number 10 2 XFER_TIME Real Number 10 2 XFER_TIM2 Real Number 10 2 IN_V_W Character 10 2 WALK_W Character 10 2 WAIT_W Character 10 2 XFER_W Character 10 2 DWELL_W Character 10 2 WAIT_WGHT Real Number 10 2 COMMENTS Character 22 0 MIN_WAIT Real Number 10 2 MAX_WAIT Real Number 10 2 Bus PNR Data File: (Alt_BUSPNR.asc) This data file contains information on bus park-and-rides, which is used to identify available bus park-and-ride locations in order to build drive-to-bus connector links in the TRAN_CON procedure. It contains one record for each PNR location in the region. o This file must have the following format: Page 3-13

74 FIELD_NAME TYPE WIDTH DECIMAL INDEX PNR_ID Integer 6 0 Yes PNR_Sequence Integer 7 0 Blank1 Character 1 0 Name Character 40 0 Co_Name Character 11 0 Serv_1 Character 8 0 Serv_2 Character 8 0 Serv_3 Character 8 0 Serv_4 Character 8 0 Serv_5 Character 8 0 Serv_6 Character 8 0 Serv_7 Character 8 0 Serv_8 Character 8 0 Serv_9 Character 8 0 Serv_10 Character 8 0 PNR_Longitude Integer 10 0 PNR_Latitude Integer 11 0 RPNR_Longitude Integer 11 0 RPNR_Latitude Integer 11 0 NJT_Zone Integer 7 0 TAZ Integer 7 0 County Integer 7 0 Mode Integer 7 0 No_of_Spaces Integer 7 0 Parking_Cost Real Number 7 0 Walk_Time Real Number 7 0 Connect_Flag Integer 7 0 Route Files: (Alt_RTEM**.asc) These alternative and mode specific files describe the characteristics of every route in the NYMTC network. For each route record, there is a list of links and stop records that define the base links that make up that route s path and stops. This file must be stored in the input directory. o This file must have the following format: Transportation Analysis Zone Coordinates Alt_TAZCOORD.asc: Output Files Rail Fare Matrix: (Alt_RAILFARE.mtx) This matrix file contains the fare in dollars of all origin destination pairs. The rows are origins and columns are destinations. The matrix file contains one matrix for each transit mode: Ferry, Page 3-14

75 Long Island Rail Road, Metro-North Railroad, and New Jersey Transit commuter rail. It is used in the transit model in the transit assignment. Route Stop File (Alt)RTES.bin: This file contains the routes, and their stops, which should correspond to the underlying geographic line layer. o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAINDEX STOP_ID Integer (4 bytes) 10 0 Yes ROUTE_ID Integer (4 bytes) 10 0 Yes LINK_ID Integer (4 bytes) 10 0 Yes PASS_COUNT Integer (4 bytes) 10 0 MILEPOST Real (8 bytes) 10 6 LONGITUDE Integer (4 bytes) 10 0 LATITUDE Integer (4 bytes) 10 0 OLD_ID Integer (4 bytes) 8 0 NODE_ID Integer (4 bytes) 12 0 STOPLABEL Character 24 0 STATION_NA Character 24 0 STN_CODE Integer (4 bytes) 4 0 PTZ_ID Integer (4 bytes) 4 0 LOCATION Integer (4 bytes) 12 0 OLDPTZID Integer (4 bytes) 4 0 FAREZONE Integer (4 bytes) 10 0 MEGA_ID Integer (4 bytes) 10 0 REP_SID Integer (4 bytes) 10 0 LONG_MEGA Integer (4 bytes) 10 0 LAT_MEGA Integer (4 bytes) 10 0 REP_LONG Integer (4 bytes) 10 0 REP_LAT Integer (4 bytes) 10 0 ENDPTID Integer (4 bytes) 10 0 MERGEID Integer (4 bytes) 10 0 RUNTIME Real (8 bytes) 10 3 PNR_ID Integer (4 bytes) 10 0 OLDSTOPID Integer (4 bytes) 10 0 BUSIVTT Real (8 bytes) 10 3 XBUSIVTT Real (8 bytes) 10 3 RAILIVTT Real (8 bytes) 10 3 CRIVTT Real (8 bytes) 10 3 FERRYIVTT Real (8 bytes) 10 3 PATH1TIME Real (8 bytes) 10 3 PATH2TIME Real (8 bytes) 10 3 PATH3TIME Real (8 bytes) 10 3 ROUTE_ID2 Integer (4 bytes) 10 0 PATH1TIM2 Real (8 bytes) 10 3 PATH2TIM2 Real (8 bytes) 10 3 PATH3TIM2 Real (8 bytes) 10 3 VOLUME Real (8 bytes) 10 3 ADJUST Real (8 bytes) 10 3 Page 3-15

76 Link Database File (Alt)lnk.dbd: This file contains a database for the underlying line layer for the transit model. o This file must have the following database structure: FIELD_NAME TYPE WIDTH DECIMAL INDEX ID Integer (4 bytes) 10 0 Yes Length Real (8 bytes) 10 2 Dir Integer (2 bytes) 2 0 CLASS Character 4 0 TYPE Integer (4 bytes) 12 0 NAME Character 30 0 FCLASS Real (8 bytes) 16 0 FromNID Integer (4 bytes) 12 0 ToNID Integer (4 bytes) 12 0 Direction Integer (4 bytes) 12 0 Distance Real (8 bytes) 16 2 TT Real (8 bytes) 16 2 CON_TYPE Integer (2 bytes) 12 0 XferMode Integer (2 bytes) 12 0 CT_DESCRIP Character 20 0 PREMIUM Integer (4 bytes) 10 0 NONPREM Integer (4 bytes) 10 0 DRIVE_AM Integer (4 bytes) 10 0 DRIVE_PM Integer (4 bytes) 10 0 Transit_IVTT Real (8 bytes) 10 2 LINK_MODE Integer (4 bytes) 12 0 AUTOTIME Real (8 bytes) 10 2 AUTOCOST Real (8 bytes) 10 2 CAPACITY Real (8 bytes) 10 2 BUSIVTT Integer (4 bytes) 12 0 XBUSIVTT Integer (4 bytes) 12 0 RAILIVTT Integer (4 bytes) 12 0 CRIVTT Integer (4 bytes) 12 0 FERRYIVTT Integer (4 bytes) 12 0 ACCOVTT Real (8 bytes) 12 4 EGROVTT Real (8 bytes) 12 4 XFROVTT Real (8 bytes) 12 4 Route System File (Alt)rte.rts This file contains the route system of the model along with the underlying geographic line layer. o This file must have the following structure: Page 3-16

77 FIELD_NAME TYPE WIDTH DECIMAL INDEX STOP_ID Integer (4 bytes) 10 0 Yes ROUTE_ID Integer (4 bytes) 10 0 Yes LINK_ID Integer (4 bytes) 10 0 Yes PASS_COUNT Integer (4 bytes) 10 0 MILEPOST Real (8 bytes) 10 6 LONGITUDE Integer (4 bytes) 10 0 LATITUDE Integer (4 bytes) 10 0 OLD_ID Integer (4 bytes) 8 0 NODE_ID Integer (4 bytes) 12 0 STOPLABEL Character 24 0 STATION_NA Character 24 0 STN_CODE Integer (4 bytes) 4 0 PTZ_ID Integer (4 bytes) 4 0 LOCATION Integer (4 bytes) 12 0 OLDPTZID Integer (4 bytes) 4 0 FAREZONE Integer (4 bytes) 10 0 MEGA_ID Integer (4 bytes) 10 0 REP_SID Integer (4 bytes) 10 0 LONG_MEGA Integer (4 bytes) 10 0 LAT_MEGA Integer (4 bytes) 10 0 REP_LONG Integer (4 bytes) 10 0 REP_LAT Integer (4 bytes) 10 0 ENDPTID Integer (4 bytes) 10 0 MERGEID Integer (4 bytes) 10 0 RUNTIME Real (8 bytes) 10 3 PNR_ID Integer (4 bytes) 10 0 OLDSTOPID Integer (4 bytes) 10 0 BUSIVTT Real (8 bytes) 10 3 XBUSIVTT Real (8 bytes) 10 3 RAILIVTT Real (8 bytes) 10 3 CRIVTT Real (8 bytes) 10 3 FERRYIVTT Real (8 bytes) 10 3 PATH1TIME Real (8 bytes) 10 3 PATH2TIME Real (8 bytes) 10 3 PATH3TIME Real (8 bytes) 10 3 ROUTE_ID2 Integer (4 bytes) 10 0 PATH1TIM2 Real (8 bytes) 10 3 PATH2TIM2 Real (8 bytes) 10 3 PATH3TIM2 Real (8 bytes) 10 3 VOLUME Real (8 bytes) 10 3 ADJUST Real (8 bytes) 10 3 Page 3-17

78 Page 3-18

79 Running the Core Model Components SECTION 4 CREATING TRANSIT AND HIGHWAY ACCESSIBILITIES 4-2 HOUSEHOLD AUTO JOURNEY PROCEDURES 4-14 MODE DESTINATION STOPS CHOICE PROCEDURESG 4-22 COMMERCIAL VEHICLE PROCEDURES 4-37 EXTERNAL AUTOS PROCEDURES 4-47 PRE-ASSIGNMENT PROCESSOR PROCEDURES 4-56 HIGHWAY ASSIGNEMTN PROCEDURES 4-65 Page 4-1

80 Preparing Transit Accessibilities Control Files 0_BPM1\6_Pgms\5_tnet\utils\ZoneProc.rsc 0_BPM1\6_Pgms\5_tnet\programs\Adjustx.exe 0_BPM1\6_Pgms\5_tnet\programs\ASSNMERG.exe 0_BPM1\6_Pgms\5_tnet\programs\Build.exe 0_BPM1\6_Pgms\5_tnet\programs\Buildb.exe 0_BPM1\6_Pgms\5_tnet\utils\buildtnet.rsc 0_BPM1\6_Pgms\5_tnet\programs\convert.exe 0_BPM1\6_Pgms\5_tnet\utils\buildtnet.rsc 0_BPM1\6_Pgms\5_tnet\programs\makecent.exe 0_BPM1\6_Pgms\5_tnet\programs\makecon.exe 0_BPM1\6_Pgms\5_tnet\programs\parsese.exe 0_BPM1\6_Pgms\5_tnet\programs\POSTMEGA.exe ProgramFiles\TransCAD\Railfare.exe 0_BPM1\6_Pgms\5_tnet\utils\routerep.rsc 0_BPM1\6_Pgms\5_tnet\utils\runtrnmodel.rsc 0_BPM1\6_Pgms\5_tnet\txmx.ctl 0_BPM1\6_Pgms\5_tnet\programs\tcmx4.exe 0_BPM1\6_Pgms\5_tnet\programs\tran_con.exe 0_BPM1\6_Pgms\5_tnet\utils\trnassns4.rsc 0_BPM1\6_Pgms\5_tnet\utils\trnskim.rsc 0_BPM1\6_Pgms\5_tnet\utils\PctWalk.rsc 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputs.rsc 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputsdata.rsc 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputsview.rsc 0_BPM1\6_Pgms\5_tnet\programs\chkbus.exe 0_BPM1\6_Pgms\5_tnet\programs\chktnet.exe 0_BPM1\6_Pgms\5_tnet\programs\schedrte.exe 0_BPM1\6_Pgms\5_tnet\utils\ubuildtnet.rsc 0_BPM1\6_Pgms\5_tnet\programs\viewstat.exe Page 4-2

81 Input Files Size (approx) 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)newparm.rsc 17 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)stations.asc 410 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)modes40.dbf 6 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)modexf.dbf 17 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)BUSPNR.asc 36 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)megalo.asc 0_BPM1\5_RunBin\5_tnet\(Alt)rtemega.asc 762 0_BPM1\1_Prep\2_tnet\trn\barrier\barrier.asc 8 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PTZCON.asc 32 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)TAZCON.asc 113 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PNR.asc _BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PNR.geo _BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnk.dcb 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnk.bin 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnk.geo 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)select.asc 0_BPM1\2_tnet\trn\conlinks\contype.asc 25 0_BPM1\3_GIS\4_Counties\county_h.dbd 110 0_BPM1\3_GIS\1_TAZ\bpz00805g.dbd 5 0_BPM1\1_PREP\0_SED\(Scen Year)\zsedbs.prn 852 0_BPM1\3_GIS\1_TAZ\manhattan.dbd 5 Page 4-3

82 Output Files Size (approx.) 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rtel.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\megalo.asc 863 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rtes.tmp _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)_rte.rts 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)HwyConSkim.mtx _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)WalkAccess.ten 101 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)HwyAccess.ten 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)WalkRetAccess.ten 98 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)HwyRetAccess.ten 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\trnaccess.prn 98 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\trnretaccess.prn 98 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCwalk_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCwalk_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCwalk_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCwalk_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTwalk_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTwalk_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTwalk_flw.bin _BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTwalk_flw.dcb 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_ono.bin 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_ono.dcb 414 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_ono.bin 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_ono.dcb 248 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_ono.bin 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_ono.dcb 594 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_ono.bin 1 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_ono.dcb 301 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rte2.prn 1 Page 4-4

83 Running Transit and Highway Accessibilities 1. In Central, make sure the Primary Control File is Main.ctl. Click Go. 2. In the NYMTC Best Practices Model Phase 1 window, click on Select to choose the Scenario ID. Then click on the Transit button. Page 4-5

84 1. In the Transit Processing Setup, click on Select to choose the correct Transit Scenario Parameter File. 2. Now, click on the Settings tab. Page 4-6

85 1. In the Settings Tab, select the Accessibilities steps to run. You can run both Highway and Transit Accessibilities at once. 2. Now, click on the Tran tab to go back to the main transit menu. Page 4-7

86 3. In the Transit main menu, click on Update Parameter File. 4. When that is finished running, go back to the Transit main menu. Remember to reselect the Parameter file. Now, click on Run Transit Components. This will take roughly 2 hours. Page 4-8

87 Input Files Description of Files Route System File (Alt)rte.rts This file contains the route system of the model along with the underlying geographic line layer. o This file must have the following structure: FIELD_NAME TYPE WIDTH DECIMAL INDEX STOP_ID Integer (4 bytes) 10 0 Yes ROUTE_ID Integer (4 bytes) 10 0 Yes LINK_ID Integer (4 bytes) 10 0 Yes PASS_COUNT Integer (4 bytes) 10 0 MILEPOST Real (8 bytes) 10 6 LONGITUDE Integer (4 bytes) 10 0 LATITUDE Integer (4 bytes) 10 0 OLD_ID Integer (4 bytes) 8 0 NODE_ID Integer (4 bytes) 12 0 STOPLABEL Character 24 0 STATION_NA Character 24 0 STN_CODE Integer (4 bytes) 4 0 PTZ_ID Integer (4 bytes) 4 0 LOCATION Integer (4 bytes) 12 0 OLDPTZID Integer (4 bytes) 4 0 FAREZONE Integer (4 bytes) 10 0 MEGA_ID Integer (4 bytes) 10 0 REP_SID Integer (4 bytes) 10 0 LONG_MEGA Integer (4 bytes) 10 0 LAT_MEGA Integer (4 bytes) 10 0 REP_LONG Integer (4 bytes) 10 0 REP_LAT Integer (4 bytes) 10 0 ENDPTID Integer (4 bytes) 10 0 MERGEID Integer (4 bytes) 10 0 RUNTIME Real (8 bytes) 10 3 PNR_ID Integer (4 bytes) 10 0 OLDSTOPID Integer (4 bytes) 10 0 BUSIVTT Real (8 bytes) 10 3 XBUSIVTT Real (8 bytes) 10 3 RAILIVTT Real (8 bytes) 10 3 CRIVTT Real (8 bytes) 10 3 FERRYIVTT Real (8 bytes) 10 3 PATH1TIME Real (8 bytes) 10 3 PATH2TIME Real (8 bytes) 10 3 PATH3TIME Real (8 bytes) 10 3 ROUTE_ID2 Integer (4 bytes) 10 0 PATH1TIM2 Real (8 bytes) 10 3 PATH2TIM2 Real (8 bytes) 10 3 PATH3TIM2 Real (8 bytes) 10 3 VOLUME Real (8 bytes) 10 3 ADJUST Real (8 bytes) 10 3 Page 4-9

88 Employment File (allind(scen Year).asc): This alternative specific ASCII file is only used for formatting purposes. In other words, the content is not used in the model, so the file never has to be updated from the 96 base year. o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX TAZ_ID Integer 10 0 EmpTot Integer 10 0 Retail Employment File (retemp(scen Year).asc) This alternative specific ASCII file is only used for formatting purposes. In other words, the content is not used, so the file never has to be updated from the 96 base year. o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX TAZ_ID Integer 10 0 EmpRet Integer 10 0 Page 4-10

89 Route Stop File (Alt)RTES.bin: This file contains the routes, and their stops, which should correspond to the underlying geographic line layer. This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX STOP_ID Integer (4 bytes) 10 0 Yes ROUTE_ID Integer (4 bytes) 10 0 Yes LINK_ID Integer (4 bytes) 10 0 Yes PASS_COUNT Integer (4 bytes) 10 0 MILEPOST Real (8 bytes) 10 6 LONGITUDE Integer (4 bytes) 10 0 LATITUDE Integer (4 bytes) 10 0 OLD_ID Integer (4 bytes) 8 0 NODE_ID Integer (4 bytes) 12 0 STOPLABEL Character 24 0 STATION_NA Character 24 0 STN_CODE Integer (4 bytes) 4 0 PTZ_ID Integer (4 bytes) 4 0 LOCATION Integer (4 bytes) 12 0 OLDPTZID Integer (4 bytes) 4 0 FAREZONE Integer (4 bytes) 10 0 MEGA_ID Integer (4 bytes) 10 0 REP_SID Integer (4 bytes) 10 0 LONG_MEGA Integer (4 bytes) 10 0 LAT_MEGA Integer (4 bytes) 10 0 REP_LONG Integer (4 bytes) 10 0 REP_LAT Integer (4 bytes) 10 0 ENDPTID Integer (4 bytes) 10 0 MERGEID Integer (4 bytes) 10 0 RUNTIME Real (8 bytes) 10 3 PNR_ID Integer (4 bytes) 10 0 OLDSTOPID Integer (4 bytes) 10 0 BUSIVTT Real (8 bytes) 10 3 XBUSIVTT Real (8 bytes) 10 3 RAILIVTT Real (8 bytes) 10 3 CRIVTT Real (8 bytes) 10 3 FERRYIVTT Real (8 bytes) 10 3 PATH1TIME Real (8 bytes) 10 3 PATH2TIME Real (8 bytes) 10 3 PATH3TIME Real (8 bytes) 10 3 ROUTE_ID2 Integer (4 bytes) 10 0 PATH1TIM2 Real (8 bytes) 10 3 PATH2TIM2 Real (8 bytes) 10 3 PATH3TIM2 Real (8 bytes) 10 3 VOLUME Real (8 bytes) 10 3 ADJUST Real (8 bytes) 10 3 Page 4-11

90 Mode Transfer File ((Alt)MODEXF.dbf) o This file contains the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX FROM Integer 9 0 TO Integer 9 0 STOP Integer 8 0 COST Real Number 9 2 FARE Character 9 2 Rail Fare Matrix ((Alt)_RAILFARE.mtx): This matrix file contains the fare in dollars of all origin destination pairs. The rows are origins and columns are destinations. The matrix file contains one matrix for each transit mode: Ferry, Long Island Rail Road, Metro-North Railroad, and New Jersey Transit commuter rail. It is used in the transit model in the transit assignment. Area Type File (atype.asc) o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX TAZ_ID Integer 10 0 AREA_TYPE Integer 10 0 DATA2 Integer 10 0 DATA2:1 Integer 10 0 Congested Highway Skim Matrix (AMSKIM1.mtx) Free Flow Highway Skim Matrix (MDSKIM1.mtx): : These SOV period specific matrices contain the general cost for each Origin and Destination TAZ pair. Each file contains six matrices: generalized cost, length, free flow time, toll costs, fixed costs, and congested time. In the access procedures, these highway skim matrices are used to compute highway and walk accessibilities. Transit Skims for Walk-to-Transit Mode ((Alt)TNETAMWTb.mtx This matrix file contains 14 matrices: Fare, Initial Wait Time, Transfer Wait Time, Number of Transfers, BUSIVTT (Bus in-vehicle travel time), XBUSIVTT (transfer bus invehicle travel time), RAILIVTT (Rail in-vehicle travel time), CRIVTT (Commuter rail in-vehicle travel time), FERRYIVTT (Ferry in-vehicle travel time), ACCOVTT (access out-of-vehicle travel time), EGROVTT (egress out-ofvehicle travel time), XFROVTT (transfer out-of-vehicle travel time), AUTOTIME, and AUTOCOST. In the access procedures, this transit skim matrix is used to compute transit accessibilities. Page 4-12

91 Walk Percentage Files ((Alt)WalkPct.bin) o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX Area_1 Integer (4 bytes) 10 0 Yes Percent_1 Real (8 bytes) 10 6 Area_2 Integer (4 bytes) 10 0 Yes Percent_2 Real (8 bytes) 10 6 Highway Accessibilities ((Alt)HwyAccess.prn) Walk Accessibilities ((Alt)WalkAccess.prn) Walk Retail Accessibilities ((Alt)WalkRetAccess.prn) Transit Accessibilities ((Alt)TrnAccess.prn) Transit Retail Accessibilities ((Alt)TrnRetAccess.prn) (Alt)TNETAM(W or D)Stass_flw.bin o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX ROUTE Integer (4 bytes) 10 0 FROM_STOP Integer (4 bytes) 10 0 TO_STOP Integer (4 bytes) 10 0 CENTROID Integer (2 bytes) 10 0 FROM_MP Real (8 bytes) 15 4 TO_MP Real (8 bytes) 15 4 FLOW Real (8 bytes) 15 4 IVTT Real (8 bytes) 15 4 VOC Real (8 bytes) 15 4 (Alt)TNETAM(W or D)Stwalk_flw.bin o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX ID1 Integer (4 bytes) 10 0 AB_Flow Real (8 bytes) 15 4 BA_Flow Real (8 bytes) 15 4 TOT_Flow Real (8 bytes) 15 4 (Alt)TNETAM(W or D)Stass_ono.bin o This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX STOP Integer (4 bytes) 10 0 ROUTE Integer (4 bytes) 10 0 ON Real (4 bytes) 15 4 OFF Real (4 bytes) 15 4 Page 4-13

92 Household Auto Journey Procedures Page 4-14

93 Preparing Household Auto Journey Control Files Location Size Main.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl 4 model.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\model.ctl 22 HAJ.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\HAJ.ctl 3 Look-Up Tables co_dist.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\co_dist.prn 92 seedfile.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\seedfile.prn 2 hhsize.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\hhsize.prn 3 suffncy.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\suffncy.prn 6 workers.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\workers.prn 4 HAJ_JFC4.txt C:\0_BPM1\0_Setup\2_LUT\1_HAJ\haj_jfc4.txt 4 children.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\children.prn 18 ctype.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\ctype.prn 1 income.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\income.prn 1 hdist2.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\hdist2.prn 22 atconst.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\atconst.prn 1 journey.prn C:\0_BPM1\0_Setup\2_LUT\1_HAJ\journey.prn 5 Input Files zsedbs.prn C:\0_BPM1\2_Alts\ (ALTERNATIVE) \0_Input\0_SED\zsedbs.prn 852 Output Files trips.out C:\0_BPM1\2_Alts\ (ALTERNATIVE) \1_Out\1_HAJ\ hajtrips.txt C:\0_BPM1\2_Alts\(ALTERNATIVE)\3_Eval\hajtrips.txt 23 hajsummary.txt C:\0_BPM1\2_Alts\(ALTERNATIVE)\3_Eval\hajsummary.txt 9 summary.out C:\0_BPM1\2_Alts\ (ALTERNATIVE) \2_Rep\1_HAJ\summary.out 9 hhsum.out C:\0_BPM1\2_Alts\ (ALTERNATIVE) \2_Rep\1_HAJ\hhsum.out 11 buildhh2.out C:\0_BPM1\2_Alts\ (ALTERNATIVE) \2_Rep\1_HAJ\buildhh2.out 2964 trips.sum C:\0_BPM1\2_Alts\ (ALTERNATIVE) \2_Rep\1_HAJ\trips.sum 23 Page 4-15

94 Running Household Auto Journey 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the NYMTC BPM menu, select the scenario you would like to run. Then Click on the Model Run button. Page 4-16

95 3. In the Model Forecast Run menu, select the scenario to run by clicking on Select. 4. By going through the folders on the left, choose the scenario year you would like to run. Page 4-17

96 5. After selecting the right scenario, click on Components. 6. In the Components Menu, check the box for Household Auto Journey. Also click on Update HAJ Inputs to update the socio-economic data for HAJ. This needs to only be run once per new scenario. Page 4-18

97 7. Now, click on the Model tab. 8. In the Model Forecast Run menu, click on Selected Components. A warning will appear asking to proceed. Click Yes. Page 4-19

98 Description of Files Control Files Look-Up Tables Household Size : (hhsize.prn) This file gives the average number of persons per household by TAZ. Atconst.prn This file gives the coefficients used for regression. Auto Sufficiency (suffncy.prn) This file contains the utility coefficients used to generate auto ownership categories for each household. Number of Workers : (workers.prn) This file gives the probability a member of a household is a worker based on urban type, household size, and income level. Production Adjustment: (HAJ_JFC.txt) This table modifies the number of productions of the different purposes by district. Children: (children.prn) This file is a probability table for the number of children per household. For every urban type, household size, income level, and number of workers, the table gives a probability that there is a child in the household. Probabilities for Generating Journeys Zone-County Equivalency: (co-dist.prn) This file contains the county for each TAZ in the highway network. Probability of Trip Purpose by County County-Urban Type Equivalency: (CTYPE.prn) This file gives the urban type for each county in the highway network. Seed File : (seedfile.prn) This table gives the base probabilities for the model, which will later be adjusted according to adjustment matrices to better fit the survey data. Journey Tables: (journey.prn) This table lists all the journeys by purpose. Input Files Socio-Economic Data: (bpzdata.prn) This file contains a record for each TAZ in the network and the basic socio-economic data for them. This file is output by the Walk/Transit Accessibility Model. Page 4-20

99 Output Files Household Records : (final.out) This table lists the characteristics of all households generated by the model. Journey Records: (trips.out) This table lists the daily journey pairs for each household in the model. The first line of each record contains the household information and the successive lines list the journey pairs made by the members of the household. Summary of Output: (trips.sum) This report file contains a list of all the input files, output files, and a list of the regression coefficients as well as a table of Trips by Purpose and Area. Summary Report: (summary.out) This report file contains summary tables for Household Size by District, Workers per District, Children per District, and Autos per District. Page 4-21

100 Mode Destination Stops Choice Procedures Page 4-22

101 Mode Destination Choice Preparing Mode Destination Choice Control Files Location Size (approx) Main.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl 4 model.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\model.ctl 22 MDC.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MDC.ctl 23 runmdc.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\runmdc.ctl 1 mdcsum.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\mdcsum.ctl 2 timer3s.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\timer3s.ctl 2 Look-Up Tables DistFact(purpose).prn C:\0_BPM1\0_Setup\2_LUT\2_MDC 1 DC_Dist_Rings.prn C:\0_BPM1\0_Setup\2_LUT\2_MDC 134 taxifare.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC 45 M_INDICES_1.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_1.csv 4 M_INDICES_2.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_2.csv 4 M_INDICES_3.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_3.csv 4 M_INDICES_4.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_4.csv 4 M_INDICES_5.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_5.csv 4 M_INDICES_6.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_6.csv 4 M_INDICES_7csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_7.csv 4 M_INDICES_8.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_INDICES_8.csv 3 NM_INDICES_1.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_1.csv 1 NM_INDICES_2.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_2.csv 1 NM_INDICES_3.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_3.csv 1 NM_INDICES_4.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_4.csv 1 NM_INDICES_5.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_5.csv 1 NM_INDICES_6.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_6.csv 1 NM_INDICES_7csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_7.csv 1 NM_INDICES_8.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_INDICES_8.csv 1 cc1 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc1 _x.csv 5 cc2 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc2 _x.csv 5 cc3 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc3 _x.csv 5 cc4 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc4 _x.csv 3 cc5 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc5 _x.csv 4 cc6 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc6 _x.csv 5 cc7 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc7 _x.csv 5 cc8 _x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\cc8 _x.csv 3 att_corr_1.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_1.txt 60 att_corr_2.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_2.txt 60 att_corr_3.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_3.txt 60 att_corr_4.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_4.txt 60 att_corr_5.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_5.txt 60 att_corr_6.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_6.txt 60 att_corr_7.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_7.txt 60 att_corr_8.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC\att_corr_8.txt 60 revzone2.dat C:\0_BPM1\0_Setup\2_LUT\2_MDC\revzone2.dat 8994 co_ijx.prn C:\0_BPM1\0_Setup\2_LUT\2_MDC\co_ijx.prn 18 revzone3.dat C:\0_BPM1\0_Setup\2_LUT\2_MDC\revzone3.dat 8232 M_targets_1.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_1.csv 2 M_targets_2.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_2.csv 2 Page 4-23

102 M_targets_3.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_3.csv 2 M_targets_4.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_4.csv 1 M_targets_5.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_5.csv 2 M_targets_6.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_6.csv 2 M_targets_7.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_7.csv 2 M_targets_8.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_targets_8.csv 1 NM_targets_1.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_1.csv 1 NM_targets_2.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_2.csv 1 NM_targets_3.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_3.csv 1 NM_targets_4.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_4.csv 1 NM_targets_5.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_5.csv 1 NM_targets_6.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_6.csv 1 NM_targets_7.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_7.csv 1 NM_targets_8.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_targets_8.csv 1 M_MSCS_1.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_1.csv 4 M_MSCS_2.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_2.csv 4 M_MSCS_3.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_3.csv 4 M_MSCS_4.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_4.csv 1 M_MSCS_5.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_5.csv 2 M_MSCS_6.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_6.csv 3 M_MSCS_7.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_7.csv 3 M_MSCS_8.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\M_MSCS_8.csv 1 NM_MSCS_1.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_1.csv 1 NM_MSCS_2.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_2.csv 1 NM_MSCS_3.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_3.csv 1 NM_MSCS_4.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_4.csv 1 NM_MSCS_5.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_5.csv 1 NM_MSCS_6.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_6.csv 1 NM_MSCS_7.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_7.csv 1 NM_MSCS_8.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC\NM_MSCS_8.csv 1 taz2schl.prn C:\0_BPM1\0_Setup\2_LUT\2_MDC\taz2schl.prn 134 Input Files zsedbs.prn C:\0_BPM1\2_Alts\ (Alt) \0_Input\0_SED 852 trips.out C:\0_BPM1\2_Alts\ (Alt) \1_Out\1_HAJ AM Highway Pre-Skims C:\0_BPM1\2_Alts\(Alt)\0_Input\1_Hnet\AMSKIM.mtx MD Highway Pre-Skims C:\0_BPM1\2_Alts\(Alt)\0_Input\1_Hnet\MDSKIM.mtx AM Transit Walk to Subway Pre-SkimC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TAMWSb.mtx AM Transit Drive to Subway Pre-SkimC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TAMDSb.mtx AM Transit Walk to Comm Rail Pre-SC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TAMWCb.mtx AM Transit Drive to Comm Rail Pre-SC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TAMDCb.mtx MD Transit Walk to Subway Pre-SkimC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TMDWSb.mtx MD Transit Drive to Subway Pre-SkimC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TMDDSb.mtx MD Transit Walk to Comm Rail Pre-SC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TMDWCb.mtx MD Transit Drive to Comm Rail Pre-SC:\0_BPM1\2_Alts\(Alt)\0_Input\3_TSKIM\TMDDCb.mtx Output Files mdc_dest1.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_dest1.txt 7983 mdc_dest2.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_dest2.txt mdc_dest3.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_dest3.txt mdc_out1.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out1.txt 9654 mdc_out2.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out2.txt mdc_out3.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out3.txt mdc_out4.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out4.txt mdc_out5.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out5.txt mdc_out6.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out6.txt mdc_out7.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out7.txt mdc_out8.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_out8.txt mdc_stops1.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops1.txt Page 4-24

103 mdc_stops2.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops2.txt mdc_stops3.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops3.txt mdc_stops4.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops4.txt mdc_stops5.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops5.txt mdc_stops6.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops6.txt mdc_stops7.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops7.txt mdc_stops8.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_stops8.txt mdc_rep1.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep1.txt 122 mdc_rep2.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep2.txt 124 mdc_rep3.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep3.txt 125 mdc_rep4.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep4.txt 101 mdc_rep5.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep5.txt 109 mdc_rep6.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep6.txt 115 mdc_rep7.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep7.txt 115 mdc_rep8.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\mdc_rep8.txt 100 coco_rep1.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep1.txt 507 coco_rep2.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep2.txt 507 coco_rep3.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep3.txt 507 coco_rep4.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep4.txt 507 coco_rep5.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep5.txt 507 coco_rep6.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep6.txt 507 coco_rep7.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep7.txt 507 coco_rep8.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\coco_rep8.txt 507 running1.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running1.txt 317 running2.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running2.txt 3956 running3.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running3.txt 1231 running4.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running4.txt 2468 running5.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running5.txt 386 running6.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running6.txt 6094 running7.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running7.txt 1996 running8.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\running8.txt 720 jrn_seq1 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq jrn_seq2 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq jrn_seq3 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq jrn_seq4 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq jrn_seq5 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq jrn_seq6 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq jrn_seq7 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq jrn_seq8 C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\jrn_seq calibs_1.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_1.txt 0 calibs_2.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_2.txt 0 calibs_3.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_3.txt 0 calibs_4.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_4.txt 0 calibs_5.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_5.txt 0 calibs_6.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_6.txt 0 calibs_7.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_7.txt 0 calibs_8.txt C:\0_BPM1\2_Alts\ (Alt) \2_Rep\2_MDC\calibs_8.txt 0 sum_rep_(alt).txt C:\0_BPM1\2_Alts\(Alt)\3_Eval\sum_rep_(Alt).txt 212 Page 4-25

104 Running Mode Destination Stops Choice 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the NYMTC Best Practice Model Phase 1 menu, select the scenario to run by clicking on Select and then click on Model Run. Page 4-26

105 3. In the Model Forecast Run menu, select the scenario to run by clicking on Select. 4. After selecting the right scenario, click on Components. Page 4-27

106 5. In the Components menu, check the box for Mode Destination (Stops) Choice. 6. Now, click on the MDC tab. Select the purposes you would like to run. To select all purposes, click the box in the upper left hand corner that says All Purposes. Page 4-28

107 7. Or, to select all purposes, click on All Purposes. 8. Next, click on the Model tab. Page 4-29

108 9. In the Model Forecast Run menu, click on Selected Components. A warning will appear asking if you would like to proceed. Click Yes. MDC will take roughly 5-10 hours, depending on the speed of the machine. Page 4-30

109 Description of Files Control Files Look-Up Tables County to County Trip Adjustment: (cc*_x.csv) This 31 x 32, purpose specific matrix controls the county to county K-factors used in the destination choice model. This file has the following format: Field Name Field Description Field Start Column Field Length Field Type BPMDist1_index numeric index (0-30) for BPMDist1 values 1 14 integer BPMDist1 numeric BPMDist1 values ( , 2-28) float CoName character label of County / Manhattan sub-area character IntraCo coefficient for intra-bpmdist float To_LM coefficient for destination in Lower Manhattan 52 9 float To_VM coefficient for destination in Valley Manhattan 61 9 float To_MM coefficient for destination in Midtown Manhattan 70 9 float To_OM coefficient for destination in Other Manhattan 79 9 float Walk Accessibilities: (revzone2.dat and revzone3.dat) This file contains a list of walk accessible destination zones for each origin zone, their O-D distances, and the percentage of the zone that is walk accessible. Revzone3 is used for the School purpose, and Revzone2 is used for all other purposes. This file has the following format: Field Name Field Description Field Start Column Field Length Field Type TAZ_I Origin Taz 1 8 integer TAZ_J Walk accessible destination TAZ 9 8 integer DIST OD distance in miles 17 9 float WALK_PCT Percent of Dest TAZ walk accessible from Orig TAZ float FLAG Special handling code - not used 36 8 float Attractions Adjustment: (Att_corr_*.txt) This un-indexed, mode specific file adjusts the attractions generated at each zone at the TAZ level. This file has the following formats: Field Name Field Description Field Start Column Field Length Field Type TAZ_ID numeric zone index (1-3586) 1 5 integer CORR_FAC attraction correction multiplier 6 15 float Page 4-31

110 Zone-county Equivalency: (DC_Dist_Rings2.prn) This file contains the zone to county equivalency for reporting purposes. For each TAZ, the table lists the county it is in. This file has the following format: Field Name Field Description Field Start Column Field Length Field Type TAZ_ID taz number (1-3586) 1 12 integer RINGTAZN ring label integer BPMDIST0 district label float Distfact1.prn This file is used to adjust the distance parameters in the destination choice models. Both linear and non-linear adjustment factors are used. This file has the following formats: Field Name Field Description Field Start Column Field Length Field Type BPMCo County index (1-28) 1 5 integer Dist_Lin distance scale function coefficient 6 10 float Dist_Nlin distance scale function exponent float Taxi Fares (TAXIFARE.txt) This is an inter-county file of taxi waiting time and associated costs. It has the following format: Field Name Field Description Field Start Column Field Length Field Type CO_I Origin County (1-28) 1 5 integer CO_J Destination County (1-28) 6 5 integer TX_WAIT Wait time for taxi 11 5 integer TX_PICKUP Flat fee for pickup 16 5 float TX_CPM Cost per mile 21 5 float TX_SURCHG Additional surcharge 26 5 float TX_TOLL Customers pay tolls 31 5 float DEST_LABELS destination county labels character River Crossing Penalty: (co_ijx.prn) This is a county-to-county interchange file showing incidence of river crossings. It has the following formats: Field Name Field Description Field Start Column Field Length Field Type CO_I origin county (1-28) 1 9 integer CO_J destination county (1-28) 10 9 integer ERX 1 if East River is crossed; 0 otherwise 19 9 integer HRX 1 if Hudson River is crossed; 0 otherwise 28 9 integer MINX 1 if other minor river is crossed; 0 otherwise 37 9 integer Page 4-32

111 Workers by Income: (workers.prn) Taz2schl.txt: This is a zonal correspondence file for the zonal geographic variable called SchoolDist. It has the following formats: Field Name Field Description Field Start Column Field Length Field Type TAZ_ID numeric zone index (1-3586) 1 12 integer REV_SCH numeric school district values (1-1040) integer SCH_MCD numeric MCD code of school district value integer Auto-Calibration based on Census: (targets_*c.txt) M_Indices_1.csv and NM_Indices_1.csv: These files contain the motorized and nonmotorized, respectively, indices to common targets. M_MSCS_1.csv and NM_MSCS_1.csv: These files contain the sets of coefficients added into the mode choice model to better match the output to survey data. M_TARGETS_1.csv and NM_TARGETS_1.csv: These files contain the mode choice distribution by county. Work Trip Allocation: (Work_att_pcts.prn) This file gives the percentage of work attractions that are in the three different income levels. This file has the following format: Field Name Field Description Field Start Column Field Length Field Type zone Origin Taz (1-3586) 1 14 integer pct low percent of attractions for low income journeys float pct med percent of attractions for medium income journeys float pct high percent of attractions for high income journeys float Page 4-33

112 Input Files Socio-Economic Data : (zsedbs.prn) This file contains a record for each TAZ in the network and the basic socio-economic data for them. The file has the following format: Field Name Field Description Field Start Column Field Length Field Type TAZ_ID Origin Taz (1-3586) 1 11 integer BPZ3_ID Alternate zone label integer LandArea zonal area in sq. miles float NYM_CO county code (1-28) integer CountyType 1=Manhattan, 2=Urban, 3=Suburban, 4=Rural integer AreaType Area type (1-11) / set by AreaType.exe integer HHPop Total non-gq population integer GQPop Total GQ population integer GQPopIns GQ population in institutions integer GQPopStr GQ population in ("Street people") integer GQPopOth GQ remainder (other) integer HHNum Number of Households integer HHSize Mean household size float ELF Employed Labor Force (workers at residence) integer Hhincx Mean household income (1996 $'s) integer EmpTot Total empployment (CTPP-based) integer EmpRet Retail employment (CTPP-based) integer EmpOff Office employment (CTPP-based) integer EarnWork Mean earnings per worker (1996 $'s / workplace taz) integer UnvEnrol University enrollment integer K12ETot K-12 enrollment integer PC_WALK % of zone with walk access to transit (in whole %'s) integer Journey Records: (journey.prn) This file contains the journey records by purpose. These records are output by the Household Auto Journey Model. Highway Skims: (**SKIM1.mtx) These period specific matrix files produced by the Highway Assignment give the generalized cost for automobiles in a 3586 x 3586, (TAZ) matrix. Each cell represents the cost of going from an origin TAZ (on the vertical axis) to a destination TAZ (on the horizontal axis) in six cost categories: generalized cost, length, free flow time, toll costs, fixed costs, and congested time. Only the SOV mode matrix files are used for MDC. Transit Skims (T****B.mtx) These period and mode specific matrices produced by the Transit Assignment give the following costs for transit: Fare, Initial Wait Time, Transfer Wait Time, Number of Transfers, Bus In-vehicle Time Page 4-34

113 Output Files Trip Records: (mdc_out*.txt) This purpose specific file details all the journey pairs created in MDC. Each record contains an origin-destination TAZ pair, purpose, and mode. Stop Records: (mdc_stops*.txt) This purpose specific file details all the stops made for each journey pair. Utilities File: (mdc_sum*.txt) Summary of Trips by County: (coco_rep*.txt) This file reports the number of journeys for each origin-destination district pair. Each record consists of an origin-destination district pair, mode, and the number of journey pairs. Summary of Reports: (sum_rep_****.txt) This alternative-specific report file contains the paired journeys by mode and district, with a table for each purpose and origin and destination. Mode Split of All Trips: (running*.txt) This purpose-specific report file created during MDC reports the number of journeys processed, as they are being processed, and the current mode percentage breakdown. Debugging Utility File: (debug*.txt) Auto-Calibration File: (calib*.txt) Page 4-35

114 Report File: (mdc_rep*.txt) This purpose-specific report file contains a list of all the input files and the parameters used as well as the following purpose-specific report tables: Table Title Initial Unbalanced Journey Attractions by Purpose Final Balanced Journey Attractions by Purpose Frequency of (Purpose) Accessible Journey Destination Counties by Mode Frequency of (Purpose) Journey Destination Counties by Mode (Purpose) Journey Trip Length Frequency Distribution (Purpose) Journey District to District by Mode Frequency Distribution (Purpose) Journey MSC Values by Motorized Mode Choice MSC Stratification (Purpose) Journey Observed Shares (in %) by Motorized Mode Choice MSC Stratification (Purpose) Journey Estimated Shares (in %) by Motorized Mode Choice MSC Stratification (Purpose) Journey Relative Differences (in %) between Observed and Estimated by Motorized Mode Choice MSC Stratification (Purpose) Journey Shares (in %) by Pre-Mode Choice MSC Stratification (Purpose) Stop Frequency by Mode (Purpose) Percentage Stop Frequency by Mode (Purpose) Stop Frequency by Origin/Destination Urban Type (Purpose) Percentage Stop Frequency by Origin/Destination Urban Type (Purpose) Stop Locations by District Page 4-36

115 Commercial Vehicles Procedures Page 4-37

116 How to Run Commercial Vehicle Preparing Commercial Vehicle Control Files Location Size (approx.) CONVERT.exe C:\0_BPM1\6_Pgms\6_trk\programs\convert.exe Il_PA.exe C:\0_BPM1\6_Pgms\6_trk\programs\II_PA.exe Trk_II.prn C:\0_BPM1\5_RunBin\TRK_II.prn Van.prn C:\0_BPM1\5_RunBin\Van.prn EETrkPA.exe C:\0_BPM1\5_RunBin\EETRKPA.exe EITrkPA.exe C:\0_BPM1\6_Pgms\6_trk\programs\EITRKPA.exe Trk_IE.prn C:\0_BPM1\5_RunBin\Trk_IE.prn Van_PA.exe C:\0_BPM1\6_Pgms\6_trk\programs EXTRKPA.exe C:\0_BPM1\6_Pgms\6_trk\programs\EXTRKPA.exe EETRKTrips.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\EXTRKTRIPS.ctl Look-Up Tables BASE_TRK_EE.mtx C:\0_BPM1\0_Setup\2_LUT\6_trk\BASE_TRK_EE.mtx 52 K_IETrk.mtx C:\0_BPM1\0_Setup\2_LUT\6_trk\K_IETRK.mtx K_IITrk.mtx C:\0_BPM1\0_Setup\2_LUT\6_trk\K_IITrk.mtx K_Van.mtx C:\0_BPM1\0_Setup\2_LUT\6_trk\K_VAN.mtx NM_ and M_MSCS_*.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC * NM_ and M_Targets_*.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC * cc*_x.csv C:\0_BPM1\0_Setup\2_LUT\2_MDC * att_corr_*.txt C:\0_BPM1\0_Setup\2_LUT\2_MDC * Input Files zsedbs.prn C:\0_BPM1\2_Alts\ (ALT) \0_Input\0_SED\zsedbs.prn VanPA96.dbf C:\0_BPM1\0_Setup\2_LUT\6_trk\VanPA96.dbf 256 ETrkPA96.dbf C:\0_BPM1\0_Setup\2_LUT\6_trk\ETRKPA96.dbf 10 Output Files TRUCK.txt C:\0_BPM1\2_Alts\ (ALT) \0_Input\0_SED\TRUCK.txt 7235 VAN.txt C:\0_BPM1\2_Alts\ (AL) \0_Input\0_SED\VAN.txt 5236 * See Preparation for Mode Destination Choice for full description of files. Page 4-38

117 Running Commercial Vehicles 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the Model Forecast Run menu, click on Select to choose the scenario to run. Then, click on Model Run. Page 4-39

118 3. In the Data Preparation Menu, again select the scenario you would like to run. 4. Then, click on Components. Page 4-40

119 5. Click on Trucks and Externals. Notice that the Trucks tab is now active. 6. Now, click on the Trucks tab. In the Trucks screen, click on Forecast Trucks Trips and Forecast Commercial Van Trips. Page 4-41

120 7. Now, click on the Model tab. 8. In the Model screen, click on Selected Components. Trucks and Commercial Vehicles will take roughly 2 hours to run. Page 4-42

121 Description of Files Control Files Avergemtx.rsc: This program calculates the averaged internal-internal impedance matrix sing the future year zone-to-zone impedance matrix and the future year impedance matrices for trucks. ImpedMTX.rsc: This program exports the zone-to-zone impedance matrix as a commadelimited file. CONVERT.exe: This program calculates the average internal-external impedance matrix as a comma-delimited file. Intrazonal.rsc: This program calculates the intrazonal trips using the averaged internalinternal impedance matrix. WriteIEImped.rsc: This program imports the zone-to-zone impedance matrix into a TransCAD matrix. Il_PA.exe: This program computes the future year zonal trip production/ attraction from the base year daily internal zone production/ attraction. Trk_II.rsc and Van.rsc: These programs apply the calibrated gamma function gravity model to the future year truck and commercial van impedance matrices to calculate the Internal-Internal truck and commercial truck trip matrices. EETrkPA.exe: This program computes the future year daily external-external trip production/ attraction using the future year daily all-vehicle traffic by external station and the base year daily external-external truck trip production. Trk_EE.rsc: This program applies the FRATAR process to the external-external truck trip table to compute the final future year external-external truck trip table matrix. ELTrkPA.exe: This program estimates the future year internal zone internal-external truck trip production using the future year daily zonal trip production/ attraction and future year daily external station production/ attraction. Trk_IE.rsc: This program applies the calibrated gamma function gravity model to the future year internal-external truck impedance matrix and future year daily zonal trip production/ attractions to compute the future year internal-external truck trip table matrix. Page 4-43

122 Input Files Impedance Matrices for Truck and Vans: (Assn_MD5.mtx and Assn_MD6.mtx) These period- and mode-specific matrix files contain the general costs associated with each origin and destination TAZ pair. The matrices are for: generalized cost, length, free flow time, toll costs, fixed costs, and congested time. Socio-Economic Data: (zsed_.dbf) This alternative-specific dbase file contains the future year socio-economic data for every zone in the area. This data is used to calculate the future year zonal trip attraction/ production for each area. This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX TAZ_ID Integer 9 0 BPZ3_ID Integer 9 0 LANDAREA Integer 9 0 NYM_CO Integer 9 0 COUNTYTYPE Integer 9 0 AREATYPE Integer 9 0 HHPOP Integer 9 0 GQPOP Integer 9 0 GQPOPINS Integer 9 0 GQPOPSTR Integer 9 0 GQPOPOTH Integer 9 0 HHNUM Integer 9 0 HHSIZE Integer 9 0 ELF Integer 9 0 HHINCX Integer 9 0 EMPTOT Integer 9 0 EMPRET Integer 9 0 EMPOFF Integer 9 0 EARNWORK Integer 9 0 UNVENROL Integer 9 0 K12ETOT Integer 9 0 PC_WALK Integer 9 0 External Station Daily Traffic: (ExData_.dbf) This alternative-specific dbase file contains the future year daily, all-vehicle traffic for every external station. It is used to compute the daily external-external trip production/ attraction. This file must have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX OZN Integer 9 0 DZN Integer 9 0 ORG Integer 9 0 DES Integer 9 0 Page 4-44

123 Trip Tables: (BASE_TRK_EE.mtx) These matrices are created through the Pre-Skim Process. The Commercial Vehicle Model only uses the skims for Truck and Van for the AM and Midday Periods. Gravity Model: (K_IETrk.mtx) Internal Zone Production/Attraction: (IITrkPA96.dbf and VanPA96.dbf) These mode specific dbase files contain the future year daily production and attraction for each internal zone. Combined with the external zone production/ attraction file, this file is used to estimate the future year daily zonal production attraction between internal and external zones. These files must have the following formats: For truck: For Van: FIELD_NAME TYPE WIDTH DECIMAL INDEX TAZ_ID Integer 10 0 P_ALL Real Number 10 2 A_ALL Real Number 10 2 P_TRK Real Number 10 2 A_TRK Real Number 10 2 P_XXT Real Number 10 2 A_XXT Real Number 10 2 P_IXT Real Number 10 2 A_IXT Real Number 10 2 FIELD_NAME TYPE WIDTH DECIMAL INDEX TAZ_ID Integer 9 0 HHNUM Integer 9 0 EMPRET Integer 9 0 EMPOFF Integer 9 0 EMPOTH Integer 9 0 TRIPEST Real Number 9 2 P Real Number 9 2 A Real Number 9 2 K-Factor Matrices: (K_IITrk.mtx and K_Van.mtx) External Trip Production: (EtrkPA96.dbf) This mode specific dbase file contains the future year attractions and productions for external zones. It is used to calculate, along with the internal zonal trip production/ attraction file, the daily zonal internal-external truck trip production/ attraction. External Truck Trip Tables: (BASE_TRK_EE.mtx) This matrix contains the base year external-external truck trip table. The origin TAZ s are on the horizontal axis, the destinations on the vertical. The table gives the number of truck trips from each origin- Page 4-45

124 destination pair. This matrix is used, with the future year external-external daily trip production/ attraction file, to calculate the external-external truck trip table matrix. Output Files External-External Truck Trip Tables: (EETrk_.mtx) Internal-Internal Truck and Commercial Van Trip Tables: (IITrk_.mtx and Van_.mtx) Internal-External Truck Trip Tables: (IETrk_.mtx) Internal Truck Impedance Matrix: (IETrkimp_.mtx) Truck Trip Tables: (TRUCK.txt) This alternative-specific text file Commercial Van Trip Tables: (VAN.txt) This alternative-specific text file Page 4-46

125 External Autos Procedures Page 4-47

126 How to Run External Auto Preparing External Auto Control Files. Size (appro Main.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl dataprep.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\dataprep.ctl runext.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\runext.ctl runext2.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\runext2.ctl Look-Up Tables xzonexrf.prn C:\0_BPM1\5_RunBin\7_ext 10 Input Files AM Highway Pre-Skims C:\0_BPM1\2_Alts\ (ALT) \0_Input\1_HNet\AMSKIM1.mtx zsedbs.prn C:\0_BPM1\2_Alts\ (ALT) \0_Input\0_SED\zsedbs.prn 852 Output Files external.prn C:\0_BPM1\5_RunBin\7_ext\external.prn 61 external.dat C:\0_BPM1\5_RunBin\7_ext\external.dat external.txt C:\0_BPM1\2_Alts\(Alternative)\7_ext\external.txt external.txt C:\0_BPM1\2_Alts\(Alternative)\0_Input\0_SED\external.txt ext_rep.prn C:\0_BPM1\2_Alts\(Alternative)\2_Rep\7_ext\ext_rep.prn 61 Page 4-48

127 Running Externals 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the Model Forecast Run menu, click on Select to choose the scenario to run. Then select the Model Run button. Page 4-49

128 1. In the Model Forecast Menu, again select the scenario you would like to run. 2. Then, click on Components. Page 4-50

129 3. Click on Trucks and Externals. Notice that the Trucks tab is now active. 4. Now, click on the Trucks tab. In the Trucks screen, click on External Models. Page 4-51

130 5. Now, click on the Model tab. 6. In the Model screen, click on Selected Components. The External model will take less than a minute to run. Page 4-52

131 Description of Files Control Files Control.TXT: This ASCII file provides the specific modeling parameters for the External Models program and must be updated prior to running the program. It must be in the alternative-specific directory for the program to run successfully. There are five different sections to this file. Modifications to the file can be made using any ASCII text editor. The file can also include user provided comments as long as the comments (or blank lines) begin with an asterisk (*) in column 1. The required layout of this file is as follows. Look-Up Tables External Zone Files: (XZONEXRF.PRN) This is the external zone characteristics file that contains the computed compound growth rate factors used by the program to forecast external trips. Data are included for each external zone. This is a fixed format ASCII file derived from an Excel spreadsheet. This file contains both historic as well as future year auto and truck volumes by external zone. Should new volumes or forecasts become available, this file can be modified. However, it is highly recommended that changes be made in the Excel spreadsheet. The External Zone Characteristics File includes the following fields: Field Name Type Width Decimal Origin (inbound) zone number Integer 8 0 Destination (outbound) zone number Integer 8 0 Inbound station ID Character 8 0 Outbound station ID Character 8 0 Fraction for truck trips inbound Decimal 8 4 Fraction for truck trips outbound Decimal Functional Class Code Integer 8 0 Page 4-53

132 1996 Inbound Daily Total Volume Integer Outbound Daily Total Volume Integer Functional Class Code Integer Inbound Daily Total Volume Integer Outbound Daily Total Volume Integer to 2025 annual growth rate (CAGR) Decimal 8 4 The basis for the XZONEXRF.PRN file is an Excel spreadsheet. As previously mentioned, the model is allows the user to change volumes and forecasts if new data are available. To maintain the data integrity of the system, it is recommended that updates be made in the appropriate tab of the XZONEXRF.XLS and not in the.prn file. Input Files Period Skim Matrices: There are five standard TransCAD 4.0 matrices used by the External Models program. The skim table name, shown after the pound symbol (#), must be entered exactly as shown because TransCAD is case sensitive. \ASSN_AM1.MTX#*_TIME for X-I home-based work trips \ASSN_AM1.MTX#TIME* for X-I home-based other trips \ASSN_AM1.MTX#TIME* for X-I non home-based trips \ASSN_AM1.MTX#Length for X-X1 through trips \ASSN_AM1.MTX#TIME* for X-X2 through trips Page 4-54

133 The *_TIME skim table contains the variable congested time. The TIME* skim table contains the variable free flow time. The Length skim table contains the variable length. The value for these variables is used in the distribution function for each of the sub-models. Internal Zone Files: (ZSEDBS**.PRN) This is the internal zone characteristics file containing demographic variables for each internal zone. The External Models program reads this fixed format ASCII file and stores, in memory, the values for seven specific variables. The variables that are used by the Externals procedure are TAZ_ID (columns 1-11), five different types of population fields, each 11 bytes long (starting in column 67 through and including column 121), and total employment (columns ). Output Files External Trip Records: (EXTERNAL.dat) This file contains the external trip interchange information. It is used as input to the PAP/TOD process. The external trip records are in fixed format ASCII and contain information for four variables. The file layout is such that there is one blank byte between each field. For example, OTAZ begins in column 1 and ends in column 4. DTAZ begins in column 6 and ends in column 9. Field Name Type Width Decimal OTAZ (Origin TAZ) Integer 4 0 DTAZ (Destination TAZ) Integer 4 0 TYPE Integer 2 0 VOLUME Integer 4 0 The TYPE field relates to the trip purpose codes. The values for this field are: Home-Based Work Trips - 14 Home-Based Other Trips - 15 Non Home-Based Trips - 16 Through Trips - 17 External Trip Records: (EXTERNAL.txt) This text file contains the external trip records. External Report: (EXTERNAL.prn) This file contains all the parameters and input files used in Externals, as well as a Report of Target 2-Way Auto Volumes by Station and Mode. The report file also lists the station volume represented and the cumulative volume records written for each external station and a table of Control and Modeled Auto Trips by Mode. Page 4-55

134 Pre-Assignment Processor Procedures Page 4-56

135 How to Run the Pre-Assignment Processor Preparing the Pre-Assignment Processor Control Files Location Size (approx.) Main.ctl C:\0_BPM1\0_Setup\0_Pre\1_Ctl\ 4 model.ctl C:\0_BPM1\0_Setup\0_Pre\1_Ctl\ 22 pap.ctl C:\0_BPM1\0_Setup\0_Pre\1_Ctl\ 13 Look-Up Tables tod_factors5.asc C:\0_BPM1\0_Setup\2_LUT\3_PAP 1 blank_h_mat.mtx C:\0_BPM1\0_Setup\2_LUT\3_PAP blank_t_mat.mtx C:\0_BPM1\0_Setup\2_LUT\3_PAP type_distb.asc C:\0_BPM1\0_Setup\2_LUT\3_PAP 1 zone_equiv.asc C:\0_BPM1\0_Setup\2_LUT\3_PAP 75 co_dist.prn C:\0_BPM1\0_Setup\2_LUT\3_PAP 92 Input Files mdc_tot.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_tot.txt truck.txt C:\0_BPM1\2_Alts\ (Alt) \0_Input\0_SED 7235 van.txt C:\0_BPM1\2_Alts\ (Alt) \0_Input\0_SED 5236 external.txt C:\0_BPM1\2_Alts\ (Alt) \0_Input\0_SED Output Files mdc_tot.txt C:\0_BPM1\2_Alts\ (Alt) \1_Out\2_MDC\mdc_tot.txt Highway Trip Tables AC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\highway_am.mtx Highway Trip Tables MC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\highway_md.mtx Highway Trip Tables PC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\highway_pm.mtx Highway Trip Tables NC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\highway_nt.mtx Transit Trip Tables AMC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\transit_am.mtx Transit Trip Tables MDC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\transit_md.mtx Transit Trip Tables PMC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\transit_pm.mtx Transit Trip Tables AMC:\0_BPM1\2_Alts\ (Alt) \1_Out\3_PAP\transit_nt.mtx pap.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\pap.prn 142 tod_am.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\tod_am.prn 3 tod_md.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\tod_md.prn 3 tod_pm.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\tod_pm.prn 3 tod_nt.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\tod_nt.prn 3 summary_am.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_pap\summary_AM.prn 170 summary_md.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\summary_MD.prn 174 summary_pm.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\summary_PM.prn 155 summary_nt.prn C:\0_BPM1\2_Alts\ (Alt) \2_Rep\3_PAP\summary_NT.prn 170 Page 4-57

136 Running the Pre-Assignment Processor 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the NYMTC BPM menu, click on Select to choose the scenario to run. Next, clock on the Model Run button. Page 4-58

137 3. In the Model Forecast Run menu, select the scenario to run by clicking on Select. 4. By going through the folders on the left, choose the scenario folder you would like to run. Page 4-59

138 5. After selecting the right scenario, click on Components. 6. In the Components menu, choose the box for Time Of Day Page 4-60

139 7. Next, click on the Model Tab. In the Model screen, click on Selected Components. A warning will appear asking you to proceed. Click Yes. The Time-of-Day model will take roughly a half hour to run. Page 4-61

140 Description of Files Control Files Pap.ctl Tod_*.ctl Time of Day Distributions Input Files Trip Records: (mdc_tot.txt) This file contains the trip records created by MDC aggregated into one file. Each record consists of a journey pair, containing an origindestination TAZ pair, purpose, mode, stop1, and stop2. Stop1, if greater than 0, indicates the TAZ where a stop on the inbound leg of the journey was made. If this number is negative, then the stop was made closer to the destination than to the origin. Stop2 is the same but for the outbound leg of the journey. Truck Trip File: (trucks.txt) This file contains a record for all origin-destination TAZ pairs including externals. For each record, there is the mode: (which is 12 for trucks) and the number of paired journeys for this TAZ pair. Other Commercial Trip File: (van.txt) This file contains a record for all origindestination TAZ pairs including externals. For each record, there is the mode: (which is 13 for trucks) and the number of paired journeys for this TAZ pair. External Travel File: (external.txt) This file contains a record for all origin-destination TAZ pairs including externals. For each record, there is the mode: (which is 14 through 15 for trucks) and the number of paired journeys for this TAZ pair. Time of Day Distribution Factors: (tod_factors4.asc) This file contains the distribution factors with which to split trip tables into the four time periods. Output Files Auto-Based Trip Tables: (highway_**.mtx) These period specific matrix files contain one matrix for each automotive mode type: Drive Alone, HOV 2 and Taxi, HOV 3+, External Autos, Truck, and Commercial Vehicle. Each matrix contains the origin TAZ s in the rows and the destination TAZ s in the columns. The number of trips for each O-D pair is calculated in the Pre-Assignment Processor procedure and is used by the Highway Assignment procedure to assign routes to O-D pairs and calculate total flows and speeds for each link given these routes. Page 4-62

141 Transit-Based Trip Tables: (transit_**.mtx) These period specific matrix files contain one matrix for each transit mode type: Walk to Transit, Drive to Transit, Walk to Commuter Rail, Drive to Commuter Rail. Each matrix contains the origin TAZ s in the rows and the destination TAZ s in the columns. The number of trips for each O-D pair is calculated in the Pre-Assignment Processor procedure and is used by the Transit Assignment procedure. PAP Process Report : (pap.prn) This file is a report of the PAP process. It contains a list of the parameters and input files used as well as the following report tables: Mdc_tot.txt : This text file contains all the trip tables for every period. Table Title Report 1: Total Trips Report 11: Heavy Trucks and Other Commercial Vehicles Report 12: External Trips Report 13: Total Maintenance Trips Report 14: Highway Maintenance Trips to Manhattan Report 15: Transit Maintenance Trips to Manhattan Report 16: Highway Maintenance Trips Outside Manhattan Report 17: Transit Maintenance Trips Outside Manhattan Report 18: Total Discretionary Trips Report 19: Highway Discretionary Trips to Manhattan Report 20: Transit Discretionary Trips to Manhattan Report 21: Highway Discretionary Trips Outside Manhattan Report 22: Transit Discretionary Trips Outside Manhattan Report 23: Total School Trips Report 24: Highway School Trips to Manhattan Report 25: Transit School Trips to Manhattan Report 26: Highway School Trips Outside Manhattan Report 27: Transit School Trips Outside Manhattan Report 28: Total University Trips Report 29: Highway University Trips to Manhattan Report 30: Transit University Trips to Manhattan Report 31: Highway University Trips Outside Manhattan Report 32: Transit University Trips Outside Manhattan Person Trips by Trip Purpose and Origin District Person Trips by Trip Purpose and Destination District Vehicle Trips by Trip Purpose and Origin District Vehicle Trips by Trip Purpose and Destination District Highway Vehicle Trips by Mode and Origin District Highway Vehicle Trips by Mode and Destination District Transit Trips by Mode and Origin District Transit Trips by Mode and Destination District Page 4-63

142 Time Of Day Period Report: (tod_**.prn) This period-specific file is a report of the TOD process. The file contains a list of the parameters and input files used as well as the number of trips per mode in the highway and transit output files for this time of day. Auto-based trip table: (highway_**.mtx) This period specific matrix file contains 6 matrices, one for each highway mode, with the number of trips for all origin and destinations, listing the origin TAZs on the vertical axis and the destination TAZs on the horizontal. Transit-based trip table: (transit_**.mtx) This period specific matrix file contains 4 matrices, one for each transit mode, with the number of trips for all origin and destinations, listing the origin TAZs on the vertical axis and the destination TAZs on the horizontal. Summary Report: (summary_**.prn) This period-specific summary report file is a table containing the following fields: Field Value Highway/Transit 1-Highway 2-Transit Mode 1.1-SOV 1.2-HOV2 and Taxi 1.3-HOV External 1.5-Truck 1.6-Commercial Vehicle 2.1-Walk to Transit 2.2-Drive to Transit 2.3-Walk to Commuter Rail 2.4-Drive to Commuter Rail Origin District 0 through 30 Destination District 0 through 30 Number of Trips Integer Page 4-64

143 Highway Assignment Procedures Page 4-65

144 Highway Assignment Preparing Highway Assignment In Windows Explorer, check to make sure all the files are in the correct directories with the correct cases. There must highway assignment output, assn_**.bin and assn_**.dbf, files for every period in the 0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet folder for the Highway Assignment to run. These files will only be used as a shell and can come from any other scenario s highway assignment. Control Files Location Size (approx Main.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl model.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\model.ctl run_hassn_check.ctl C:\0_BPM1\0_Setup\1_Ctl\0_Pre\run_hassn_check.ctl Input Files AM Period Network FilesC:\0_BPM1\2_Alts\(Alt)\0_Input\1_hnet\AM\AM.dbd 5 MD Period Network File C:\0_BPM1\2_Alts\(Alt)\0_Input\1_hnet\MD\MD.dbd 5 PM Period Network FilesC:\0_BPM1\2_Alts\(Alt)\0_Input\1_hnet\PM\PM.dbd 5 NT Period Network FilesC:\0_BPM1\2_Alts\(Alt)\0_Input\1_hnet\NT\NT.dbd 5 AM Observed data files C:\0_BPM1\1_Prep\1_HNet\0_Base\OBS_AM.dbf MD Observed data files C:\0_BPM1\1_Prep\1_HNet\0_Base\OBS_MD.dbf PM Observed data files C:\0_BPM1\1_Prep\1_HNet\0_Base\OBS_PM.dbf NT Observed data files C:\0_BPM1\1_Prep\1_HNet\0_Base\OBS_NT.dbf AM Highway Trip TablesC:\0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_am.mtx MD Highway Trip TablesC:\0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_md.mtx PM Highway Trip TablesC:\0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_pm.mtx NT Highway Trip TablesC:\0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_nt.mtx VDFMMRev5.dbf C:\0_BPM1\0_Setup\2_LUT\4_Hnet\VDFMMRev5.dbf 2 Output Files AM.bin Flows C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_AM.bin AM.dbf Flows C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_AM.dbf MD.bin Flows C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_MD.bin MD.dbf Flows C:\0_BPM1\2_Alts(Alt)\1_Out\4_Hnet\ASSN_MD.dbf PM.bin Flows C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_PM.bin PM.dbf Flows C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_PM.dbf NT.bin Flows C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_NT.bin NT.dbf Flows C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_NT.dbf AM Highway Skims C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_AM*.mtx MD Highway Skims C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_MD*.mtx PM Highway Skims C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_PM*.mtx NT Highway Skims C:\0_BPM1\2_Alts\(Alt)\1_Out\4_Hnet\ASSN_NT*.mtx Page 4-66

145 Running Highway Assignment 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. 2. In the NYMTC BPM menu, click on Select to choose the scenario to run. Then select the Model Run button. Page 4-67

146 3. Selecting the right scenario, and then click on the Components tab. 4. In the Model Run menu, click on the (2) Components tab. In the Components menu, select Highway Assignment. Make sure all other checkboxes are blank. Page 4-68

147 5. If you would like to use the skims created by the highway assignment as pre-skims, click on Update Highway Skims. This is only necessary if you are planning to run Highway and Transit Accessibilities, Transit Skims, MDC, Externals or Commercial Vehicles after this highway assignment. 6. Next, click on the (4) HWY_ASSN tab. If it is not active, make sure that the Highway Assignment checkbox in the (2) Components menu has been checked. In HWY_ASSN, choose which period you would like to run an assignment on. Page 4-69

148 7. For each period chosen, enter the number of iterations to run. 8. Then, select which skims, if any, should be produced. There is also an option to run only skims, but only proceed if there is already is an assignment output for this scenario. Page 4-70

149 9. Or, to run a Standard Highway Assignment, click on Standard Highway Assignment. 10. If running a highway assignment off of Adjusted Trip Tables (the Trip Table Adjustment step must be performed before running this kind of assignment, see the section on Trip Table Adjustment Procedures for more information), click on Assignment with Adjusted Trip Tables. Page 4-71

150 11. To run a highway assignment with bus preloads, check on the Assignment with Bus Preloads check box. In order to run this type of assignment, Bus Preloads must exist in the period networks (for more information on how to run this step, refer to the section on Creating Period Highway Networks with Bus Preloads). 12. Now, click on the Model tab. Page 4-72

151 13. In the Model menu, click on Selected Components. A message will appear asking whether to continue with the run, click Yes. Central will launch TransCAD with an Interface window; when the assignment is complete, TransCAD will close. The Highway Assignment will take roughly 12 hours to run. Page 4-73

152 Description of Files Control Files ASSN.ctl: This program runs the TransCAD Multi-Modal Assignment procedure then appends the output to create a dbase file. To create skims, the procedure uses the trip tables from the Pre-Assignment Processor and the link flows from the Multi-Modal Assignment to calculate costs for each origin-destination TAZ pair. Batchrun.ini: This file is written out by Central each time the Assignment is run. It specifies which periods are to be run and contains all the output, input, and lookup table files to use for each period. Look Up Files VDFMMRev5.dbf: This look up table gives the specifications for each PLT type. Input Files The table should have the following fields: (remember that TransCAD is case sensitive.) Field Name Type Width Decimal LINKNAME Character 16 0 CODE Integer 6 0 TIME Real Number 6 1 CAPACITY Integer 6 0 ALPHA Real Number 6 2 BETA Real Number 6 2 PRELOAD Real Number 4 2 Period Files: These standard geographical files are the highway period networks created by NetPrep. They are currently stored in the working directory (for the base network, this is C:\0_BPM1\1_Prep\1_Hnet\0_Base\) in folders for each period. In the assignment procedure, the binary file created by TransCAD will be appended to the end of the period.dbd file to produce a dbase file. Page 4-74

153 Each Period File should have the following fields: (remember that TransCAD is case sensitive!) Field Name Type Decimal Width Index ID Integer (4 bytes) 10 0 Yes Length Real (8 bytes) 10 2 Dir Integer (2 bytes) 2 0 LID Integer (4 bytes) 10 0 NAME1 Character 30 0 COUNTY Integer (2 bytes) 4 0 FCLASS Integer (2 bytes) 4 0 DESIGN Integer (1 byte) 2 0 MEDIAN Character 3 0 ACCESS Character 5 0 SIGNAL Character 5 0 DRIVEWAY Character 5 0 TURN Character 5 0 RAMPTYPE Character 5 0 AUTOTOLL Integer (4 bytes) 10 0 TRUKTOLL Integer (4 bytes) 10 0 TRUCK Integer (2 bytes) 4 0 TRUK_USG Integer (2 bytes) 4 0 SPECIAL Character 5 0 TOT_LANE Integer (2 bytes) 3 0 LANESAB Integer (4 bytes) 5 0 LANESBA Integer (4 bytes) 5 0 PARK Character 5 0 RESTRICT Character 5 0 SPDMOD Integer (2 bytes) 5 0 CAPMOD Integer (2 bytes) 5 0 ZONE Integer (4 bytes) 5 0 AREATYPE Integer (4 bytes) 5 0 PLT Integer (4 bytes) 5 0 FREESPD Integer (4 bytes) 5 0 LANECAP Integer (4 bytes) 5 0 CAPACITYAB Integer (4 bytes) 6 0 CAPACITYBA Integer (4 bytes) 6 0 TIMEAB Real (8 bytes) 9 4 TIMEBA Real (8 bytes) 9 4 IMPEDAB Real (8 bytes) 9 4 IMPEDBA Real (8 bytes) 9 4 AUTOFIX Real (8 bytes) 12 4 HOV2FIX Real (8 bytes) 12 4 HOV3FIX Real (8 bytes) 12 4 HOV4FIX Real (8 bytes) 12 4 TRUCKFIX Real (8 bytes) 12 4 TAXIFIX Real (8 bytes) 12 4 COMMFIX Real (8 bytes) 12 4 Page 4-75

154 OBS_**.dbf: These files contain observed data for each link on the network. In the highway assignment, the observed data files are used to compare the newly assigned speeds and flows to observed speeds and flows for reporting purposes. Highway Trip Tables: These period specific matrix files contain one matrix for each automotive mode type: Drive Alone, HOV 2, HOV 3+, Taxi, Truck, and Commercial Vehicle. Each matrix contains the origin TAZ s in the rows and the destination TAZ s in the columns. The number of trips for each O-D pair is calculated in the Pre-Assignment Processor procedure and is used by the Highway Assignment procedure to assign routes to O-D pairs and calculate total flows and speeds for each link given these routes. Output Files ASSN_**.bin: This period specific file contains the output from the internal TransCAD highway assignment for each link of the network. Each file should have the following format: (remember that TransCAD is case sensitive.) Field Name Type Width Decimal ID1 Integer (4 bytes) 10 0 AB_Flow Real (8 bytes) 15 4 BA_Flow Real (8 bytes) 15 4 TOT_Flow Real (8 bytes) 15 4 AB_Time Real (8 bytes) 15 4 BA_Time Real (8 bytes) 15 4 MAX_Time Real (8 bytes) 15 4 AB_voc Real (8 bytes) 15 4 BA_voc Real (8 bytes) 15 4 MAX_voc Real (8 bytes) 15 4 AB_speed Real (8 bytes) 15 4 BA_speed Real (8 bytes) 15 4 AB_VDF Real (8 bytes) 15 4 BA_VDF Real (8 bytes) 15 4 MAX_VDF Real (8 bytes) 15 4 AB_Flow_Drive Alone Real (8 bytes) 15 4 BA_Flow_Drive Alone Real (8 bytes) 15 4 AB_Flow_HOV 2 Real (8 bytes) 15 4 BA_Flow_HOV 2 Real (8 bytes) 15 4 AB_Flow_HOV 3+ Real (8 bytes) 15 4 BA_Flow_HOV 3+ Real (8 bytes) 15 4 AB_Flow_Taxi Real (8 bytes) 15 4 BA_Flow_Taxi Real (8 bytes) 15 4 AB_Flow_Trucks Real (8 bytes) 15 4 BA_Flow_Trucks Real (8 bytes) 15 4 AB_Flow_Other Commercial Real (8 bytes) 15 4 BA_Flow_Other Commercial Real (8 bytes) 15 4 Page 4-76

155 ASSN_**.dbf: This period specific dbase file contains the information from the period.dbd file appended to the highway assignment output. It is used in the assignment procedure to assign aggregate costs to traveling between origin and destination TAZ pairs (see ASSN_***.mtx). Each file should have the following format: (remember that TransCAD is case sensitive.) Field Name Type Width Decimal Description ID Integer 10 0 ID LID Integer 8 0 Old Link ID FROMNODE Integer 10 0 From Node TONODE Integer 10 0 To Node SCLID Character 14 0 SCL Counts Link ID LENGTH Real Number 10 2 Length DIR Integer 2 0 Direction COUNTY Integer 4 0 Coundy Code FCLASS Integer 4 0 Functional Class AREATYPE Integer 5 0 Area Type PLT Integer 5 0 Physical Link Type RESTRICT Character 5 0 Restrictions SPDMOD Integer 5 0 Speed Modification CAPMOD Integer 5 0 Capaciy Modification LANESAB Integer 5 0 # of Lanes in AB Direction LANESBA Integer 5 0 # of Lanes in BA Direction AB_FLOW Real Number 15 4 Volume in AB direction BA_FLOW Real Number 15 4 Volume in BA direction TOT_FLOW Real Number 15 4 Total Flow in AB and BA direction Congested Travel Time on AB AB_TIME Real Number 15 4 direction Congested Travel Time on BA BA_TIME Real Number 15 4 direction MAX_TIME Real Number 15 4 Maximum Congested Time Volume over capacity in AB AB_VOC Real Number 15 4 direction BA_VOC Real Number 15 Volume over capacity in BA 4 direction AB_SPEED Real Number 15 4 Congested speed in AB direction BA_SPEED Real Number 15 4 Congested speed in BA direction Truck Flow in AB direction (this is AB_FLOW_TR Real Number 15 4 a component of AB_Flow) Truck Flow in BA direction (this is BA_FLOW_TR Real Number 15 4 a component of BA Flow) Page 4-77

156 ASSN_***.mtx: This period and mode specific matrix contains the cost for each Origin and Destination TAZ pair. The matrix file contains one matrix for six costs: generalized cost, length, free flow time, toll costs, fixed costs, and congested time. Every matrix lists the Origin TAZ s on the vertical axis and the Destination TAZ s on the horizontal. Report: (ASSN***.txt) This alternative-specific text file contains all the input files and parameters used in the assignment procedure. Page 4-78

157 Page 4-79

158 Transit Assignment Procedures SECTION 5 Page 5-1

159 Preparing Transit Assignment Control Files 0_BPM1\6_Pgms\5_tnet\utils\ZoneProc.rsc 0_BPM1\6_Pgms\5_tnet\programs\Adjustx.exe 0_BPM1\6_Pgms\5_tnet\programs\ASSNMERG.exe 0_BPM1\6_Pgms\5_tnet\programs\Build.exe 0_BPM1\6_Pgms\5_tnet\programs\Buildb.exe 0_BPM1\6_Pgms\5_tnet\utils\buildtnet.rsc 0_BPM1\6_Pgms\5_tnet\programs\convert.exe 0_BPM1\6_Pgms\5_tnet\utils\buildtnet.rsc 0_BPM1\6_Pgms\5_tnet\programs\makecent.exe 0_BPM1\6_Pgms\5_tnet\programs\makecon.exe 0_BPM1\6_Pgms\5_tnet\programs\parsese.exe 0_BPM1\6_Pgms\5_tnet\programs\POSTMEGA.exe ProgramFiles\TransCAD\Railfare.exe 0_BPM1\6_Pgms\5_tnet\utils\routerep.rsc 0_BPM1\6_Pgms\5_tnet\utils\runtrnmodel.rsc 0_BPM1\6_Pgms\5_tnet\txmx.ctl 0_BPM1\6_Pgms\5_tnet\programs\tcmx4.exe 0_BPM1\6_Pgms\5_tnet\programs\tran_con.exe 0_BPM1\6_Pgms\5_tnet\utils\trnassns4.rsc 0_BPM1\6_Pgms\5_tnet\utils\trnskim.rsc 0_BPM1\6_Pgms\5_tnet\utils\PctWalk.rsc 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputs.rsc 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputsdata.rsc 0_BPM1\6_Pgms\5_tnet\utils\buildtrninputsview.rsc 0_BPM1\6_Pgms\5_tnet\programs\chkbus.exe 0_BPM1\6_Pgms\5_tnet\programs\chktnet.exe 0_BPM1\6_Pgms\5_tnet\programs\schedrte.exe 0_BPM1\6_Pgms\5_tnet\utils\ubuildtnet.rsc 0_BPM1\6_Pgms\5_tnet\programs\viewstat.exe Page 5-2

160 Input Files 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)newparm.rsc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)stations.asc 0_BPM1\5_RunBin\5_tnet\TAZCOORD.asc 0_BPM1\5_RunBin\5_tnet\taz_edge.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)modes40.dbf 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)modexf.dbf 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)RTE.asc 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)TAZCoord.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)BUSPNR.asc 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)PNRLIST.asc 0_BPM1\5_RunBin\5_tnet\(Alt)ptz_mega.asc 0_BPM1\5_RunBin\5_tnet\(Alt)pnr_mega.asc 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)megalo.asc 0_BPM1\5_RunBin\5_tnet\(Alt)rtemega.asc 0_BPM1\1_Prep\2_tnet\trn\barrier\barrier.asc 0_BPM1\5_RunBin\5_tnet\(Alt)ptz_data.asc 0_BPM1\5_RunBin\5_tnet\(Alt)freexfer.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PTZCON.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)TAZCON.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PTZCON.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PNR.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)PNR.geo 0_BPM1\5_RunBin\5_tnet\(Alt)maxmega.asc 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnk.dcb 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnk.bin 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)lnk.geo 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)select.asc 0_BPM1\2_tnet\trn\conlinks\contype.asc 0_BPM1\5_RunBin\5_tnet\baselink.bin 0_BPM1\5_RunBin\5_tnet\basenode.bin 0_BPM1\2_Alts\(Alternative)\0_Input\2_tnet\(Alt)rter.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)_rtel.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)_rtes.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rte.rts 0_BPM1\3_GIS\4_Counties\county_h.dbd 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rte.rts 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)_rteS.dbd 0_BPM1\3_GIS\1_TAZ\bpz00805g.dbd 0_BPM1\1_PREP\0_SED\(Scen Year)\zsedbs.prn 0_BPM1\5_RunBin\5_tnet\allind96.asc 0_BPM1\5_RunBin\5_tnet\retemp96.asc 0_BPM1\5_RunBin\5_tnet\Select.ctl 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\walkaccess.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\hwyaccess.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\walkretaccess.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\hwyretaccess.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)walkpctc.tab 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rte.rts 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)statvol(1-#iterations).txt 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)cordvol(1-#iterations).txt 0_BPM1\3_GIS\1_TAZ\manhattan.dbd Page 5-3

161 Output Files 0_BPM1\5_RunBin\5_tnet\RailFare2.prn WorkRailFare3.prn 0_BPM1\5_RunBin\5_tnet\RailFare4.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rtel.bin 0_BPM1\5_RunBin\5_tnet\(Alt)pnrlist.asc 0_BPM1\5_RunBin\5_tnet\(Alt)build.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)PTZ_MEGA.asc 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)PTZ_DATA.asc 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)PNR_MEGA.asc 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)PNR_DATA.asc 0_BPM1\5_RunBin\5_tnet\(Alt)megast.rpt 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\megalo.asc 0_BPM1\5_RunBin\5_tnet\sidmeg.asc 0_BPM1\5_RunBin\5_tnet\rtmega.asc 0_BPM1\5_RunBin\5_tnet\duplica.asc 0_BPM1\5_RunBin\5_tnet\(Alt)trancon.rpt 0_BPM1\5_RunBin\5_tnet\(Alt)trncon.geo 0_BPM1\5_RunBin\5_tnet\(Alt)adjustx.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rtes.tmp 0_BPM1\5_RunBin\5_tnet\(Alt)sidmeg.asc 0_BPM1\5_RunBin\5_tnet\(Alt)postmega.asc 0_BPM1\5_RunBin\5_tnet\(Alt)basenode.bin 0_BPM1\5_RunBin\5_tnet\(Alt)baselink.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)_rte.rts 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet(1-7).mtx 0_BPM1\5_Runb0_BPM1\2_Alts\(Alternative)\0_Input\2_Tnet\5_Tnet\barrier.asc 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)HwyConSkim.mtx 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)WalkAccess.ten 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)HwyAccess.ten 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)WalkRetAccess.ten 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)HwyRetAccess.ten 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\trnaccess.prn 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\trnretaccess.prn 0_BPM1\2_Alts\(Alternative)\1_0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\3_Pap\transit_am.mtx 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_flw.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_flw.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_flw.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_flw.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCwalk_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCwalk_flw.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCwalk_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCwalk_flw.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTwalk_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTwalk_flw.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTwalk_flw.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTwalk_flw.dcb Page 5-4

162 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_ono.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WCtass_ono.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_ono.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DCtass_ono.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_ono.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**WTtass_ono.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_ono.bin 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)tnet**DTtass_ono.dcb 0_BPM1\2_Alts\(Alternative)\1_Out\5_tnet\(Alt)rte2.prn Page 5-5

163 Running Transit Assignment. In Central, make sure the Primary Control File is Main.ctl. Click Go. 2. In the NYMTC Best Practices Model Phase 1 window, click on Select to choose the Scenario ID. Then hit the Transit button. Page 5-6

164 5. In the Transit Processing Setup, click on Select to choose the correct Transit Scenario Parameter File. Then choose the Settings tab. 1. In the Settings screen, click on Transit Assignment. If you would like to create assignment reports, click on Transit Reporter. Page 5-7

165 2. Now, click on Tran to go back to the main transit menu. 3. In the Transit main menu, click on Update Parameter File. Page 5-8

166 4. When that is finished running, go back to the Transit main menu. Remember to reselect the Parameter file. Now, click on Run Transit Components. This will take roughly 2 ½ days. Page 5-9

167 Description of Files Control Files Look Up Tables Input Files Matrix Template ((Alt)TNET**tmplt.tmx) This matrix file consists of ** matrices each containing a 3586 by 3586 null matrix template. (Alt)TNET**WCB.mtx (Alt)TNET**DCB.mtx (Alt)TNET**WSB.mtx (Alt)TNET**WCB.mtx (Alt)TNETAM(Mode)tass_flow1.bin o This file should have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX ROUTE Integer (4 bytes) 10 0 FROM_STOP Integer (4 bytes) 10 0 TO_STOP Integer (4 bytes) 10 0 CENTROID Integer (2 bytes) 10 0 FROM_MP Real (8 bytes) 15 4 TO_MP Real (8 bytes) 15 4 FLOW Real (8 bytes) 15 4 IVTT Real (8 bytes) 15 4 VOC Real (8 bytes) 15 4 (Alt)TNETAM(Mode)tass_ono1.bin o This file should have the following format: Page 5-10

168 FIELD_NAME TYPE WIDTH DECIMAL INDEX STOP Integer (4 bytes) 10 0 ROUTE Integer (4 bytes) 10 0 ON Real (4 bytes) 15 4 OFF Real (4 bytes) 15 4 (Alt)TNETAM(Mode)wlk_flw1.bin o This file should have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX ID1 Integer (4 bytes) 10 0 AB_Flow Real (8 bytes) 15 4 BA_Flow Real (8 bytes) 15 4 TOT_Flow Real (8 bytes) 15 4 Output Files Assignment Output Flows (Alt)TNETAM(Mode)tass_flw.bin: These alternative and mode specific binary file contains the output from the TransCAD transit assignment. For each link along a route, it gives the flow, in-vehicle travel time, and the VOC ratio. o This file should have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX ROUTE Integer (4 bytes) 10 0 FROM_STOP Integer (4 bytes) 10 0 TO_STOP Integer (4 bytes) 10 0 CENTROID Integer (2 bytes) 10 0 FROM_MP Real (8 bytes) 15 4 TO_MP Real (8 bytes) 15 4 FLOW Real (8 bytes) 15 4 IVTT Real (8 bytes) 15 4 VOC Real (8 bytes) 15 4 Page 5-11

169 Assignment Output Ons and Offs (Alt)TNETAM(Mode)tass_ono.bin: These alternative and mode specific binary files contain the number of Ons and Offs at every stop along every route. o This file should have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX STOP Integer (4 bytes) 10 0 ROUTE Integer (4 bytes) 10 0 ON Real (4 bytes) 15 4 OFF Real (4 bytes) 15 4 Assignment Output Walk Flow (Alt)TNETAM(Mode)walk_flw.bin: This alternative and mode specific files contain the amount of flow in both directions on every link in the network. o This file should have the following format: FIELD_NAME TYPE WIDTH DECIMAL INDEX ID1 Integer (4 bytes) 10 0 AB_Flow Real (8 bytes) 15 4 BA_Flow Real (8 bytes) 15 4 TOT_Flow Real (8 bytes) 15 4 Page 5-12

170 Page 5-13

171 Additional Model Components SECTION 6 TRIP TABLE ADJUSTMENT PROCEDUE 6-2 USING THE ZIPING AND EXTRACTION TOOL 6-7 RUNNING THE ENTIRE HIGHWAY MODEL IN ONE-STEP 6-14 RUNNING THE SUB-AREA EXTRACTION MODEL 6-21 Page 6-1

172 Preparing Trip Table Adjustment This procedure must always be run before running PPAQ. The entire procedure, including the highway assignment after the trip table adjustment, will take roughly 13 to 14 hours to run. Control Files Location Size (approx) Main.ctl 0_BPM1\0_Setup\1_Ctl\0_Pre\Main.ctl Util.ctl 0_BPM1\0_Setup\1_Ctl\0_Pre\Util.ctl final_mat_inc_adj.ctl 0_BPM1\0_Setup\1_Ctl\0_Pre\final_mat_inc_adj.ctl Increment_Apply_AM.ctl 0_BPM1\0_Setup\1_Ctl\0_Pre\Increment_Apply_AM.ctl Increment_Apply_MD.ctl 0_BPM1\0_Setup\1_Ctl\0_Pre\Increment_Apply_MD.ctl Increment_Apply_PM.ctl 0_BPM1\0_Setup\1_Ctl\0_Pre\Increment_Apply_PM.ctl Increment_Apply_NT.ctl 0_BPM1\0_Setup\1_Ctl\0_Pre\Increment_Apply_NT.ctl Input Files AM Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_am.mtx 375,065 MD Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_md.mtx 375,065 PM Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_pm.mtx 375,065 NT Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_nt.mtx 375,065 AM Matrix Increment 0_BPM1\5_RunBin\4_Hnet\increm_am.mtx 1,125,066 MD Matrix Increment 0_BPM1\5_RunBin\4_Hnet\increm_md.mtx 1,125,066 PM Matrix Increment 0_BPM1\5_RunBin\4_Hnet\increm_pm.mtx 1,125,066 NT Matrix Increment 0_BPM1\5_RunBin\4_Hnet\increm_nt.mtx 1,125,066 AM Matrix Adjustment 0_BPM1\5_RunBin\4_Hnet\adjam0.mtx 375,065 MD Matrix Adjustment 0_BPM1\5_RunBin\4_Hnet\adjmd0.mtx 375,065 PM Matrix Adjustment 0_BPM1\5_RunBin\4_Hnet\adjpm0.mtx 375,065 NT Matrix Adjustment 0_BPM1\5_RunBin\4_Hnet\adjnt0.mtx 375,065 Output Files AM Adjusted Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_am_adj.mtx 1,875,067 MD Adjusted Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_md_adj.mtx 1,875,067 PM Adjusted Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_pm_adj.mtx 1,875,067 NT Adjusted Highway Trip Table 0_BPM1\2_Alts\(Alt)\1_Out\3_PAP\highway_nt_adj.mtx 1,875,067 AM Report 0_BPM1\5_RunBin\4_Hnet\adj_rep_am.mtx 2 MD Report 0_BPM1\5_RunBin\4_Hnet\adj_rep_md.mtx 2 PM Report 0_BPM1\5_RunBin\4_Hnet\adj_rep_pm.mtx 2 NT Report 0_BPM1\5_RunBin\4_Hnet\adj_rep_nt.mtx 2 AM Intermediate File 0_BPM1\5_RunBin\4_Hnet\interm_am.mtx 375,065 MD Intermediate File 0_BPM1\5_RunBin\4_Hnet\interm_md.mtx 375,065 PM Intermediate File 0_BPM1\5_RunBin\4_Hnet\interm_pm.mtx 375,065 NT Intermediate File 0_BPM1\5_RunBin\4_Hnet\interm_nt.mtx 375,065 Page 6-2

173 Running Highway Trip Table Adjustment 1. In the NYMTC BPM Menu, click GO. 2. Next, click Utilities in the Main Menu. Page 6-3

174 3. In the Utilities Menu, select the scenario to perform the matrix adjustment on. 4. Next, click on Apply Adjustment. Page 6-4

175 5. In the Adjustment Menu, select the scenario you wish to run the adjustment on. 6. Next, select the highway trip tables to do the adjustment on. All periods must be selected. Page 6-5

176 7. Now, click on Proceed in the bottom right hand corner to launch the program. The adjustment will take a half hour to run. 8. After the adjustment has been performed, the highway assignment procedure should be run in order to get the adjusted highway assignments. When configuring the Highway Assignment Screen, click on Adjusted Trip Tables in order to use the new adjusted trip tables. Page 6-6

177 Using the Zipping/Extracting Utility After the end of a BPM run, it is possible to use the Zipping Utility to zip all the important output files into 4 zip files, which are saved to the 0_BPM1\2_Alts\(Scenario)\4_zip that can then be copied to 4 cds. After creating the 4 cds, the files in the scenario can be deleted. Later, the scenario can be extracting from the cds by copying the contents of the four cds into the 0_BPM1\2_Alts\(Scenario)\4_Zip folder, then using the Extraction Tool. The zip files will be extracted to their appropriate locations. Zipping a Scenario 1. In the e Central Process screen, click Go. Page 6-7

178 1. In the Main Setup screen, select the scenario you would like to run and click on Utilities. 2. In the Utilities Screen, select the scenario you would like to run. Then click on the ZIP tab at the bottom of the screen. Page 6-8

179 3. Now, select which files you would like to have zipped up. The Zip Prefix and Zip Suffix are text strings that can be added to the zip files for identification purposes. In addition, the user can select the TransCAD log file to include in the zip file set. The zipping program will take roughly 10 minutes to run. Page 6-9

180 Unzipping a Scenario 1. In the Central Process screen, click Go. 4. In the Main Setup screen, select the scenario you would like to run and click on Utilities. Page 6-10

181 5. In the Utilities Screen, select the scenario you would like to run. Page 6-11

182 6. Next, click on the ZIP tab at the bottom of the screen. Then click on the ZIP tab at the bottom of the screen. 7. Note that Extracting the Scenario will replace every file in the scenario with those in the zip file, regardless of date. Page 6-12

183 8. Now, click on Extract Scenario. Page 6-13

184 Running the Entire Highway Model in One Step This section explains how to run the Highway Model to the BPM in one step. However, in order to do this, all steps up to and including running Transit Database and Skims procedures. 1. In Central, choose C:\0_BPM1\0_Setup\1_Ctl\0_Pre\MAIN.ctl as your control file. Choose C:\0_BPM1\5_RunBin \ as your working directory. Now click GO. Page 6-14

185 2. In the NYMTC BPM menu, select the scenario you would like to run. Then choose Model Run. 3. In the Model Forecast Run menu, select the scenario to run by clicking on Select. Page 6-15

186 4. By going through the folders on the left, choose the scenario year you would like to run. 5. After selecting the right scenario, click on Components. Page 6-16

187 6. Click on Update HAJ Inputs, Household Auto Journey, Mode Destination Choice, Trucks and Externals, Time-of-Day, and Highway Assignment. Now, click on the MDC tab. 7. In the MDC screen, click on All Purposes. If running the entire model in one stream, all purposes of MDC must be run. Page 6-17

188 8. Now, click on the Highway Assignment Tab. 9. In the Highway Assignment Screen, click on Standard Highway Assignment. Page 6-18

189 10. Now, click on the Trucks tab. 11. In the Trucks screen, select Forecast Truck Model, Forecast Commercial Van, and External Model. Page 6-19

190 12. Now, click on the Model tab. 13. In the Model screen, click on Selected Components. The whole model will take 1 to 2 days. Page 6-20

191 Running the Sub-Area Model Application Module 1: Sub-Area Trip Matrices/Network Extraction 1. In the NYMTC BPM Menu, select C:\0_BPM1\0_SETUP\1_CTL\0_PRE\RunSubExt.ctl.CTL. Then hit the Go button. Page 6-21

192 2. Specify the ID of the output scenario (a scenario directory corresponding to this output scenario should be created prior to the process, please refer to NYBPM User Documentation for detail). Select option Run Sub-Area Trip Table/ Network Extraction for Module 1: Sub-Area Trip Matrices/Network Extraction. 3. Click on Tab (2) Network to specify the sub-area boundary layer and input highway network files for the extraction of sub-area O/D matrices. Insert the name for the output sub-area highway network. 4. Click on Tab (3) Triptable. Specify the input time-period O/D trip matrices. User has the flexibility to run any time periods by checking/unchecking the boxes. The Page 6-22

193 files names of the extracted O/D matrices are standardized as SUB_OD_xx.mtx (where xx=am, MD, PM or NT) and are located at C:\0_bpm1\2_Alts\(scenario id)\1_out\3_pap\. 5. Return to Tab (1) Main, press GO to start the process (or QUIT to exit from the setup). Module 2: Sub-Area Detailing 1. Select option Run Data Preparation for Module 2: Sub-Area Detailing Page 6-23

194 2. Click on Tab (4) DataPrep. Specify the input O/D trip matrices to be renumbered/re-allocated. The BPM-to-sub-area zone equivalency file should be specified. Press ReNum to start renumbering process. 3. On Tab (4) DataPrep, press NetPrep to launch the Highway Network Preparation setup screen. User has the flexibility to specify a user-defined link free-flow speed/capacity lookup file. Specify all necessary input files. Press Run NetPrep to start the process. Page 6-24

195 The output time period networks will be located at C:\0_bpm1\2_Alts\(scenario id)\0_input\1_hnet\xx (for xx=am, MD, PM or NT). Page 6-25

196 Module 3: Sub-Area Traffic Assignment 1. Select option Run Sub-Area Traffic Assignment for Module 3: Sub-Area Traffic Assignment 2. Click on Tab (5) SubAssn. Select the checkboxes for the appropriate time periods for the highway assignment run. Input highway networks and O/D trip matrices should also be specified. Page 6-26

197 3. Click on Tab (6) SubAssnPrm, specify the highest number of the sub-area zone centroid. User has the flexibility to run highway assignment with a user-defined Volume Delay Function (VDF) file. 4. Return to Tab (1) Main, press GO to start the process (or QUIT to exit from the setup). The output assignment link flows will be located at C:\0_bpm1\2_Alts\(scenario id)\1_out\4_hnet\. Page 6-27

198 Page 6-28

199 Index and Flow Charts SECTION 7 GLOSSARY 7-2. NYBPM: FILES DESCRIPTION 7-10 FLOWCHARTS 7-16 PAGE 7-1

200 Glossary Terms Term Accessibility Definition Measure of average nearness from a given point or analysis zone to all opportunities to satisfy a particular activity need; e.g. total number of jobs located within 60 minutes travel from zone i. An indication of the ease of reaching desired locations. Conceptually, accessibility is a function of some generalized price, which depends on standard measures of separation (time, cost), on modal characteristics which influence perception (such as comfort, speed, directness, consistency, degree of physical effort, and extent of waiting), on personal characteristics which influence perception (such as income, age, family status, work status, and physical condition), and on the quality of the desired activity at the destination location (e.g., the quantity and mix of retail stores, in the case of a shopping trip). Accessibility between two locations is sometimes measured as location-to-location time by a specific mode (usually highway), but also can be measured as cost or as a composite of time, cost, and other modal, personal, and location attributes. The denominator of a logit mode choice model is a comprehensive accessibility measure for a specific trip. Accessibility of a location is a weighted composite of individual accessibilities for all suitable location pairs at that place. The denominator of a logit destination choice model or a gravity trip distribution model is a comprehensive accessibility measure for an origin location. 2) Suitability for use by a person who is "mobility limited" (see also mobility). (NARC MODELING MANUAL). Activity, committed A regular activity of person in household for which there is little daily discretion, i.e. work and school. NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-2

201 Activity, non-committed Any activity other than work or school, typically possible to accomplish with more flexibility with respect to the place and time of day. Algorithm Bias Constant Coefficient A step-by-step procedure for computing a solution to a mathematical problem. Solutions to some mathematical problems may be computed by applying any one of several alternative algorithms; the solutions will not necessarily be identical. For example, comparison of traffic assignments computed with different algorithms generally will reveal different numbers of vehicles assigned to a link (NARC MODELING MANUAL). In mode choice models, the error term or constant in each separate utility expression; a mode bias constant is the unique error term included in the utility equation for that specific mode. One type of parameter in a statistical model, generally used to refer to the scalar values that are multiplied time independent or explanatory variables in a utility expression. In the following expression, a and b are the coefficients for the X and Z explanatory variables. [Y = ax + bz + c] Commute Commuting pattern Constant BPM Term: Travel by a worker from home to work and from work to home including any stops made at intermediate locations but excluding any travel leaving and then returning to work BPM Term: The aggregation of all commutes into marketlevel information that describes, for example, county-tocounty movements between home and work A parameter in a utility equation that does not vary with respect to any of the explanatory variables, generally representing the variation in the dependant variable that is unaccounted for by the independent variables, or error term. In the following expression, c is the constant term. [Y = ax + bz + c] NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-3

202 Daily Traffic: (ExData_.dbf) This dbase file contains the future year daily allvehicle traffic for every external station. It is used to compute the daily external-external trip production/ attraction. Hypothesis Impedance ImpedMTX.rsc: In the scientific method, a prediction, based on a theory, for the outcome of an experiment that can be conducted so as to provide a test of the validity of theory, or to disprove it. In choice modeling, a formulation of a model that is consistent with a behavioral explanation, which is expected to show a reasonably good fit with the estimation data using standard statistical measures. Measure of the disutility along a travel path, typically either travel time, or a combination of travel time and out-ofpocket costs in a generalized cost formulation in which value of time, and varying weights on the components of travel time such as in-vehicle and out-of-vehicle times are weighted differently. This program exports the zone-to-zone impedance matrix as a comma-delimited file. Journey Segmentation, market Logit Model BPM Term: Travel between two principal locations in either direction. The breakdown of some population into logical and measurable components that may share common travel behavior, such households segmented by income group (low, medium, and high). A choice model formulation based on the principle that individuals maximize utility in choosing among available alternatives. The logit formulation involves specifying a utility function for each individual, with a deterministic component (that is, one which depends on characteristics of the individual and of the alternatives) and a stochastic disturbance (or error term). The form of the logit model, shown below, follows from the assumption that the error terms are independent and share the same probability distribution. This assumption under certain conditions may produce erroneous results, which can be overcome by using the nested logit or probit formulations. (NARC MODELING MANUAL). NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-4

203 where: P n (i) is the probability that individual n chooses alternative i, e is the base of the natural logarithm, V in is the deterministic component of the utility mode i for individual n, and incne V in is the sum of the exponential term over all alternatives in individual n's choice set Most transportation demand model systems use a logit formulation for mode choice; a few represent joint destination/mode choice and vehicle ownership using a logit or nested logit formulation. (See also multinomial logit) Logit, multinomial Logit, nested Logit, ordered LogSum A form of the logit model that assumes equal competition among the discrete alternatives. This assumption is true only if there are no significant correlations among any subgroups of the alternatives in terms of attributes not included in the model. A form of the logit model that provides for subgroupings of the discrete alternatives that represent various levels of competition among the alternatives to group together various levels of auto-occupancy or various means of access to transit. A form of the logit model that recognizes that a specific order exists in the discrete alternatives -- that choosing one item is more than choosing none and less than choosing two (potentially useful for the choice of a number of trips to make during the day, the number of vehicles to own, and other choices among quantities). The natural log of the denominator of a logit function, sometimes used as a measure of accessibility when it comes from a mode choice model. The logsum is equal to the expected utility from the choice being modeled. (NARC MODELING MANUAL). NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-5

204 Lookup-table Market Model, aggregate Model, disaggregate A table of values that are used in model application that referenced by some attribute, such as peak period speeds for a highway link based on facility type; also referred to as contingency table. A population group that creates demand for the consumption of something, such as travel. Units of model are not individual travelers, but aggregates such as zones, for which average values represent the constituent population of travelers. Units of model are individual travelers. Disaggregate model estimation use statistical files in which individual households or persons are the units of analysis or records. In common usage, models developed to represent the behavior of individual decision-makers (persons, households, firms). (NARC MODELING MANUAL) Model, discrete-choice A modeling approach depicting choice among readily definable and distinct alternatives. (NARC MODELING MANUAL) Model, non-linear Model, regression Model in which the relationship of variables that contribute to the utility expression are combined in a non-linear manner, i.e., not additive. A model, which is estimated, based on a regression technique, such as some conventional trip production and attraction models. Model calibration The adjustment of constants (alternative-specific parameters) in a model so that the market-specific estimates for the alternatives match, in the aggregate, the demand for those alternatives observed in current data. Model estimation Model validation Occupancy, discrete The application of an econometric software package to estimate parameters in a model (logit, regression, others) using data that describe the behavior that the model is intended to describe. The testing of calibrated models in an application setting identical to that in which the model will be used for forecasting but representing some base year for which data (usually traffic counts and transit boardings) are available to examine the performance of the model. Accounting for the number of persons in a vehicle by NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-6

205 category, such as: 1-person (SOV), two person (HOV-2), and three or more (HOV=3+) as opposed to a mean average. Parameter Pathbuilder A term in a utility expression for which a specific value is estimated as a result of the statistical estimation process in which data is applied to a particular model form. Parameters include coefficients, exponents (applied to independent or endogenous variables) as well as constants in such equations. A procedure in network-based transportation software that is used to find selected paths across a transportation network between selected pairs or among all origins and destinations. The criteria for selection of paths may be specified by the analyst, such as minimum distance or minimum generalized cost. Pedestrian friendliness Physical characteristics of an residential or business area that provide for convenient, safe and pleasant walking conditions. Principal location Pseudo-household Speed, average Speed, congested Speed, free-flow BPM Term: For committed travel, principal locations are home, work, and school. For non-committed travel, principal locations are home and the most-distant location visited on each departure from home. A synthetic household constructed by sampling randomly from distributions of household characteristics, usually for the purpose of applying disaggregate models with disaggregate data. Average speed of travel for all vehicles during some specified time period, commonly determined as the ratio of Vehicle Miles of Travel (VMT) / Vehicle Hours of Travel (VHT). Speed associated with a peak period travel during which congestion levels are significant and cause travel time delays. In capacity-constrained assignment models, the final speeds produced as the result of equilibration of travel times and route choices and volume loadings on links. A hypothetical speed of travel on a road network that would be typical of a the average driver when there is no other traffic present; commonly used as a starting point in speed delay functions related to volume to capacity NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-7

206 calculations in capacity restraint assignment procedures. Stop In transit coding, a boarding and/or alighting point on a route. BPM Term: A visit to an intermediate location during a journey between home and some other principal location (in either direction). Travel-frequency How often on a typical weekday an particular type of travel occurs. Trip A unit of travel that is demarcated by an origin and a destination, and can be assigned to a network using a pathfinding and loading procedures. Usually groups in trip tables or origin-destination flow matrices with similar types of trips (e.g. same time, mode, purpose, etc.). Trip-rate Tour Variable, explanatory A measure of the average or typical number of trips that are associated with something considered to either produce or attract travel, such as households, or employment, respectively. For example: a average weekday person trip rate of 10 trips / household. BPM Term: travel from home to one or more location. The terms in a functional equation that represent characteristics or attributes of individuals or other entities that are associated with or predict the some outcome or behavior. These factors, such as income levels, travel costs, etc., are distributed, or vary, across the population; also termed independent or endogenous variables. In the following expression, X and Z are the explanatory variables. [Y = ax + bz + c] Variable, dependent The predicted term in a functional equation. In the following expression, Y is the dependant variable. [Y = ax + bz + c] Variable, independent Same as explanatory variable (see above). Variable, shortfall BPM Term A term used for a class of explanatory variables used in the Vehicle-Ownership model developed for the NYMTC model. (See the Final Model Specifications for a detailed definition and examples of its construction) NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-8

207 Variable, sufficiency Weighting of data Worker Zone BPM Term A term used for a class of explanatory variables used in the Vehicle-Ownership model developed for the NYMTC model. (See the Final Model Specifications for a detailed definition and examples of its construction) Estimating and applying factors to sample data, such as travel surveys, that is done to make good estimates of characteristics of the population that it represents; includes corrective adjustments for sampling plans that are not purely random (stratified or quotas ), as well as for estimates of varying rates of participation among different groups comprising the sample of respondents. A household member who is employed, either full time or part time, as his/her primary out-of-home commitment. A worker who is also a part-time student is classified as a worker. A full-time student who also holds a job is identified as a student. Transportation Analysis Zone (TAZ): a small geographic subarea of a regional study area or corridor that is used in aggregate modeling as the basic units of travel. Ideal zones are ones which are 1) relatively homogenous with respect to their population, so as to minimize aggregation error, and which are 2) small enough so that the geographic relationship of their centroids fairly represents the access characteristics of travelers to/from the zone to the transportation networks that connect them to all other parts of the modeled study area. NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-9

208 NYMTC BPM: Files Description ASSN_**.bin: ASSN.ctl: ASSN_**.dbf: This period specific file contains the output data from the internal TransCAD highway assignment for each link of the network. This program runs the TransCAD Multi-Modal Assignment procedure then appends the output to the network to create a dbase file. The macro also uses highway trip tables from the Pre-Assignment Processor and link flows from the Multi-Modal Assignment to calculate generalized traveling costs for each Origin-Destination TAZ pair. This period specific dbase file contains the information from the period.dbd file appended to the highway assignment output. ASSN_***.mtx: Adjustment: This period and mode specific matrix contains the generalized traveling costs for each Origin and Destination TAZ pair. The matrix file contains six matrices, one for each cost: generalized cost, length, free flow time, toll costs, fixed costs, and congested time. The Origins are listed on the vertical axis and the Destinations on the horizontal. (Att_corr_*.txt) This un-indexed, mode specific file adjusts the attractions generated at each zone at the TAZ level Avergemtx.rsc: Batchrun.ini: This program calculates the averaged internal-internal impedance matrix sing the future year zone-to-zone impedance matrix and the future year impedance matrices for trucks. This batch file is written out by Central each time the Assignment is run. It specifies which periods are to be run and contains all the output, input, and lookup table files to use for each period. Builder.rsc: This program creates a new base network using changes and project scenarios. In the first run, the base network will be updated with the changes to be made. In the second run, it will create the scenario using the scenario manager and coded projects. NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-10

209 Bus PNR Data File: Changes Files: (Alt_BUSPNR.asc) This data file contains information on bus park-and-rides that is used to identify available bus park-and-ride locations in order to build drive-to-bus connector links in the (TRAN_CON procedure). It contains one record for each PNR location in the region. This file must be stored in the input directory. The Changes Files should be in the C:\0_BPM1\1_Prep\1_Hnet\2_Chgs folder. Each change file should be a standard geographic file with its 16 other components. Each change file must have the same fields as a highway network, and contain only the number of links that need to be changed. CONVERT.exe: County to County Trip Adjustment: Distfact1.prn: EETrkPA.exe: ELTrkPA.exe: External Trip Production: This program calculates the average internal-external impedance matrix as a comma-delimited file. (cc*_x.csv) This 31 x 32, purpose specific matrix controls the county to county K-factors used in the destination choice model. This file is used to adjust the distance parameters in the destination choice models. Both linear and non-linear adjustment factors are used. This program computes the future year daily externalexternal trip production/ attraction using the future year daily all-vehicle traffic by external station and the base year daily external-external truck trip production. This program estimates the future year internal zone internal-external truck trip production using the future year daily zonal trip production/ attraction and future year daily external station production/ attraction. (EtrkPA96.dbf) This mode specific dbase file contains the future year attractions and productions for external zones. NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-11

210 External Truck Trip Tables: Highway Network: (BASE_TRK_EE.mtx) This matrix contains the base year external-external truck trip table. The origin TAZ s are on the horizontal axis, the destinations on the vertical. The table gives the number of truck trips for each origindestination pair. The highway network is the map that the model will run off of. It should be a TransCAD standard geographical file with two layers: Node and NetworkLinks. Highway Trip Tables: These period specific matrix files contain one matrix for each automotive mode type. Each matrix contains the origin TAZ s on the vertical axis and the destination TAZ s on the horizontal. The number of trips for each O-D pair is calculated in the Pre-Assignment Processor procedure and is used by the highway assignment procedure to assign routes and calculate total flows and speeds for each link. Il_PA.exe: This program computes the future year zonal trip production/ attraction from the base year daily internal zone production/ attraction. Internal Zone Production/Attraction: (IITrkPA96.dbf and VanPA96.dbf) These mode specific dbase files contain the future year daily production and attraction for each internal zone. Intrazonal.rsc: Journey Records: Log File: This program calculates the intrazonal trips using the averaged internal-internal impedance matrix. (journey.prn) This file contains the all journey records by purpose. The log file written by NetPrep displays all the files used and the values of the matrices and arrays used in the program. Mode Definition File: (Alt_MODES40.dbf) This dbase file defines the characteristics of each transit mode and is used by the transit network builder and path builder to define modes for the purpose of determining fare and establishing pathbuilding weights. This file should not be altered, and NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-12

211 changes to this file could negatively affect the model s consistency with calibration conditions. This file must be stored in the input directory. Netprep.ctl: OBS_**.dbf: This program takes the base highway network and breaks it into four period highway networks. In NetPrep, all links are assigned a physical link type (PLT), area type, free speeds, and capacities. General costs for each automotive mode are also calculated for each link. These files contain observed data for each link on the network. In the highway assignment, the observed data files are used to compare the newly assigned speeds and flows to observed speeds and flows for reporting purposes. Period Files: Project Files: Rail Fare Matrix: Report: These standard geographical files are the highway period networks created by NetPrep. The Project Files are the coded projects to be incorporated into the future year network. (Alt_RAILFARE.mtx) This matrix file gives the fare in dollars of all origin destination pairs. The rows are origins and columns are destinations. Each matrix in the matrix file corresponds to each transit mode: Ferry, Long Island Rail Road, Metro-North Railroad, and New Jersey Transit commuter rail. This file contains all the files and variables used in the assignment procedure. Route Files: Scenario Manager: (Alt_RTEM**.asc) These alternative and mode specific files describe the characteristics of every route in the NYMTC network. For each route record, there is a list of links and stop records that define the base links that make up that route s path and stops. This.dbf file contains a list of all the Changes files along with their associated Project files. For each file, there is a PIN number, Year, and Scenario type. Socio-Economic Data: (Zsed_.dbf) This dbase file contains the future year socioeconomic data for every zone in the area. NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-13

212 Socio-Economic Data : (zsedbs.prn) This file contains a record for each TAZ in the network and the basic socio-economic data for them. Station File: Stop Records: Summary of Trips by County: Transit Geographic Files: Transit Data Files: Trip Mode Split: Trip Records: Trk_EE.rsc: Trk_II.rsc and Van.rsc: (Alt_STATIONS.rsc) This alternative specific data file contains all the information for stations. They ensure that the route system is built so that all given stations are coded at the same longitude and latitude and are given the same fare zone and PTZ id. (mdc_stops*.txt) This purpose specific file details all the stops made for each journey pair. (coco_rep*.txt) This file reports the number of journeys for each origin-destination district pair. Each record consists of an origin-destination district pair, mode, and the number of journey pairs. (Alt_LNKM**.geo) This alternative and mode specific geographic file contains the base links used by the transit routes. They must be stored in the input directory. (Alt_LNKM**.dcb and Alt_LNKM**.bin) These alternative and mode specific data files contain descriptive information for each transit base link in the base link geographic file. (running*.txt) This file created during MDC reports the number of journeys processed and the current mode percentage breakdown. (mdc_out*.txt) This purpose specific file details all the journey pairs created in MDC. Each record contains an origin-destination TAZ pair, purpose, and mode. This program applies the FRATAR process to the external-external truck trip table to compute the final future year external-external truck trip table matrix. These programs apply the calibrated gamma function gravity model to the future year truck and commercial van impedance matrices to calculate the Internal-Internal truck and commercial truck trip matrices. NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-14

213 Trk_IE.rsc: VDFRemm5.dbf: This program applies the calibrated gamma function gravity model to the future year internal-external truck impedance matrix and future year daily zonal trip productoin/ attractions to compute the future year internalexternal truck trip table matrix This look up table gives the specifications for each PLT type. Work Trip Allocation: (Work_att_pcts.prn) This file gives the percentage of work attractions that are in the three different income levels. WriteIEImped.rsc: Zone-county Equivalency: Zone Fare File: This program imports the zone-to-zone impedance matrix into a TransCAD matrix. (DC_Dist_Rings2.prn) This file gives the zone to county equivalency for reporting purposes. For each TAZ, the table lists which county it is in. This ASCII text file consists of four files defining the fair structure for ferries (Alt_FERFARE.ctl), Long Island Rail Road (Alt_LIRFARE.ctl), Metro-North Railroad (Alt_MNRRFARE.ctl), and New Jersey Transit Rail (Alt_NJTFARE.ctl). Each file contains a record for each station, with fare zone assignments for each station. A look-up table below these defines the fare for each fare zone origin-destination pair. Zone File: Zone To Link File: This is the TransCAD standard geographical file that specifies the zone system for the network. This is a TransCAD dbase file that contains all the links in the current highway network along with the zone that it is in. NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-15

214 Flow Charts and Diagrams NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-16

215 Figure 1. Flow Chart of the Model HIGHWAY COMMERCIAL VEHICLES NETWORK PREPARATION COML HNET SOCIO- ECONOMIC DATA FORECASTS SEDF HIGHWAY ACCESS PROCEDURES TRANSIT ACCESS HACC HOUSEHOLD AUTO- JOURNEY HAJ EXTERNAL AUTOS EXTL MODE DESTINATION STOPS MDSC PRE- ASSIGNMENT PROCESSOR PAP HIGHWAY ASSIGNMENT HASN TRANSIT ASSIGNMENT POST PROCESSING PPAQ BPM REPORTING PROCEDURES TACC TASN REPT TRANSIT NETWORK PREPARATION TNET NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-17

216 Figure 13: Detailed BPM Flow Chart NYMTC Best Practise Model (NYBPM: Detailed Model Application Flow Chart) DRAFT 2/12/02 Legend Input Data Set (from externally prepared source) Creating Pre-Skims Input Model Parameters Decision Process Computational Process Is this a new scenario network? Yes Is the new scenario network within 5 years of a previous scenario? Run Highway Assignment using Trip Tables from older No version of same scenario with new updated network Use matrix No factoring program to calculate new skims Create Pre-Skims Using Advised Method MD Period Truck Skims (assn_md5.mtx) AM Period Commercial Vehicle Skims (assn_am6.mtx) AM Period Truck Skims (assn_am5.mtx) MD Period Commercial Vehicle Skims (assn_md6.mtx) Commercial Vehicles Trip Generation Commercial Vehicles Procedures (averagemtx.rsc, convert.rsc, writeieimped.rsc, impedmtx.rsc, II_PA.rsc, intrazonal.rsc, EEtrkPA.exe, van.rsc, EItrkPA.exe trkii.rsc, trkee.rsc, trkie.rsc) External Station Daily Traffic Commercial Vehicles Trip Tables (Truck.txt, Van.txt) Manual Process Yes AM Period SOV Skims (assn_am1.mtx) K-Factor Matrix Gravity Model Intermediate Data Set Use Skims from previous scenario MD Period SOV Skims (assn_md1.mtx) External Trip Production External Truck Trip Table Highway Accessibility EmpInFile RetErrInFile Socio-Economic Data Forecasts Compute Zone Layer Percentages of Zones (bpz dbd) (zone_pct.rsc) SocioEconomic Data Forecasts (zseds.prn) Transit Accessibility ****WalkPctc.tab *****Employment.tab Highway Skims (ASSN_***.mtx) Transit Skims (ASSN_***.mtx) Zone Buffer Characteristics (zone_pct.asc) Area Type Calculator (calczone.rsc) Output Data Set Area Type Characteristics (ATYPE**.dat) Highway Access Procedures hwacces.rsc tcmx4.exe Rename ATYPE**.dat to ATYPE.dat and move to Scenario-specific folder Transit Access Procedures (trnaccess.rsc) Seed File seedfile.prn No. of workers Probability Table worker.prn HACC County-Urban Type Equivalency ctype.prn Auto Sufficiency Utility Coefficients suffcny.prn Highway Network Preparation Base Highway Network (HN****.dbd) Scenario Manager (ScenarioManager.d bf) Project Files (Proj***.dbd) Changes Files (Chgs***.dbd) Household Auto Journey Generation (prepit.bat) Walk Accesibility (WalkAccess.prn/.ten) Walk Accesibility (WalkAccess.prn/.ten) Zone Socio-Economic Data (bpzdata.prn) Transit Accessibilities Alt_TrnAccess.prn TACC Zone-County Equivalency co-dist.prn Regression Coefficients atconst.prn Household Auto Journey Procedures hhbuild.ctl journey.ctl Build Highway Network (Builder.rsc) Household Size hhsize.prn Production Ajdustment HAJ_JFC.txt Routes Alt_TAZCOORD Zone Layer (bpz******.dbd) Zone to Link Files Z2L.dbf New Alternative Highway Network (*******.dbd) Journey Tables journey.prn Children Probability Table children.prn Journey Records trips.out Household Records final.out Report summary.out Summary of Output trips.sum Transit Network Preparation InZone railfare Base Link Geographic Files Base Link Data Files HAJ Speed-Capacity Look-Up Table (SPDCAP.dbf) Prepare Period Networks (NetPrep.ctl) Mode Share Adjustment (M_MSCS_*.csv and NM_MSCS_*.csv) Period Highway Networks (**.dbd) Transit Skims (TSKIM*.mtx) Work Trip Allocation (Work_att_pcts.prn) Auto-Calibraton Based on Census (targets_*c.txt) Transit Network Preparation (build.exe, zoneproc.rsc, runtrnmodel, adjust.exe, postmega.exe, buildtnet.rsc, megastop.exe, tran_con.exe, loadtime4.rsc, makecent.exe) Mode Definition File Bus Park and Ride Data Mode Destination Stops Choice Model Station Definition Files Zone Fair Definition File HNET Attractions Adjustment (Att_corr_*.txt) Rename AM Period Skims to AMSKIM1.mtx and MD Period Skims to MDSKIM1.mtx River Crossing Penalties (co_ijx.prn) External Autos Trip Generartion External Zone Data Internal Zone Data Mode Destination Stops Choice (mdc_*.ini) Zone-County Equivalency (DC_Dist_Rings2.prn) Taxi Trip Cost Calculation Auto-Calibration (calib*.txt) mdc_dest*.txt Distance Parameter Adjustment (DistFact1.prn) Rail Fare Matrix Alt_RAILFARE.mtx Alt_rtes.bin Alt_lnk.dbd Route System Alt_rte.rts Mode File Alt_MODES40.dbf Mode Transfer File Alt_MODESXF.dbf External Autos Intracounty and Manhattan Trips Adjustment (cc*_x.csv) Workers by Income (workers.prn) Internal Zone Production/Attraction All Trip and Stops Records (mdc_tot.txt) Report File (mdc_rep*.txt) Summary of Report Files (sum_rep_****.txt) Summary of Trips by County (coco_rep*.txt) Mode Choice Distribution by County (M_Targets_*.csv and NM_Targets_*.csv) Report File EXTL (EXTERNAL.prn) External Trip Records (External.dat) Rename External.dat to MDSC External.txt Time of Day Time of Day and Pre-Assignment Processor pap.ctl tod_x*.ctl PAP Time of Day Distributions COML Highway Network Assignment Observed Volumes and Speeds Highway Trip Tables (highway_**.mtx) TransiTrip Tables (transit_**.mtx) Transit-based Trip Tables (transit_**.mtx) Transit-based Trip Tables (transit_**.mtx) Transit-based Trip Tables (transit_**.mtx) Transit Assignment (assnmerg.exe, routerep4.rsc, trnassn4.rsc, Runtrnmodel) Highway Assignment assn.ctl VDF Curves Transit Network Assignment Alt_TNETAM**tass_flw.bin Alt_TNETAM**walk_flo w.bin Transit Ons and Offs Alt_TNERAM**tass_ono.bi n Alt_TNETAM**2.tnw Report File Alt_rte2.prn AM Period Flows (assn_am.bin/.dbf) MD Period Flows (assn_md.bin/.dbf) PM Period Flows (assn_pm.bin/.dbf) NT Period Flows (assn_nt.bin/.dbf) AM Period SOV Skims (assn_am1.mtx) AM Period Truck Skims (assn_am5.mtx) TASN AM Period Commercial Vehicle Skims (assn_am6.mtx) MD Period SOV Skims (assn_md1.mtx) MD Period Truck Skims (assn_md5.mtx) MD Period Commercial Vehicle Skims (assn_md6.mtx) HASN TNET NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-18

217 NYMTC BPM USER S DOCUMENTATION REVISED MAY 2004 PAGE 7-19