User Guide STOPS Simplified Trips-on-Project Software
Federal Transit Administration - STOPS
STOPS 1.50 user documentation v5 reduced User Guide
STOPS Simplified Trips-on-Project Software
Version 1.50 Prepared for: Federal Transit Administration 1200 New Jersey Avenue, SE Washington, DC 20590
Prepared by: RSG
2200 Wilson Boulevard Arlington, VA 22101 April 29, 2015
Table of Contents
1. Introduction ................................................................................1
2. Overview of STOPS and Its Application ....................................5
2.1 STOPS Model Structure ....................................................................................................................................... 5 2.2 Suggested Application Approach..................................................................................................................... 7 2.3 Input Data.................................................................................................................................................................. 7 2.4 Computer Resources ............................................................................................................................................ 8 2.5 Skill Requirements ................................................................................................................................................ 8 2.6 Time Requirements............................................................................................................................................... 9
3. Installing STOPS Software....................................................... 10
3.1 Installation Steps..................................................................................................................................................10 3.2 Specifying Automatic GIS Linkage.................................................................................................................12
4. Scenario Set-Up Steps .............................................................. 17
4.1 Defining the STOPS Run Parameters ...........................................................................................................21 4.2 Station Locations..................................................................................................................................................25
4.2.1 Creating the Station Data File.................................................................................................................28 4.3 Define STOPS Parameters (Part 1 - Run Names and Geography)....................................................32 4.4 List and Check TAZ and CTPP Files ..............................................................................................................34 4.5 Obtaining Census and CTPP Data ..................................................................................................................34
4.5.1 CTPP and Census File Names .................................................................................................................35 4.5.2 Downloading CTPP and Census Geographic Boundary File Data ...........................................36 4.5.3 Splitting CTPP Geography........................................................................................................................36 4.5.4 Controlling the Geographic Extent of the Analysis........................................................................36 4.6 Metropolitan Planning Organization Data.................................................................................................37 4.6.1 MPO Data Filenames ..................................................................................................................................37 4.6.2 MPO Zone Layer with Existing and Forecasted Population and Employment ..................37 4.6.3 MPO Auto Time Matrix..............................................................................................................................42 4.7 Check File Status...................................................................................................................................................44 4.8 Transit Agency Schedule and Supplemental Data..................................................................................44 4.8.1 Overview of GTFS File Formats.............................................................................................................45 4.8.2 Managing GTFS Files and Creating Project Scenarios in STOPS ..............................................55 4.8.3 Visualizing GTFS Data................................................................................................................................62 4.8.4 Obtaining GTFS Files..................................................................................................................................65 4.8.5 Setting up GTFS File Characteristics and STOPS Parameters in the Parameter File.......66 4.8.6 Identifying Required GTFS Files and Sub-Directories .................................................................68 4.8.7 Creating GTFS Sub-Directories and Data Files................................................................................70 4.8.8 Confirming that All GTFS Files are Present ......................................................................................84 4.8.9 Final Review of Station File.....................................................................................................................85 4.9 Define Forecast Years.........................................................................................................................................86
5. Data Preparation Steps ........................................................... 89
5.1 Create Station Buffers ........................................................................................................................................90 5.2 District Definitions and Zonal Data ..............................................................................................................90 5.3 Create MPO-TAZ Equivalency and File and Generate Zonal Socioeconomic Forecasts..........95 5.4 Prepare Pedestrian Environment Data.......................................................................................................95
i
Federal Transit Administration STOPS v1.50 Users Guide
6. Run STOPS Batch Steps ............................................................ 96
7. Reporting Results .................................................................... 99
7.1 Report STOPS Results ..................................................................................................................................... 100 7.1.1 Summary of Key Inputs ......................................................................................................................... 101 7.1.2 Summary of Existing Scenario Results Before Station Group Calibration........................ 102 7.1.3 Summary of Station Group Calibration Process .......................................................................... 105 7.1.4 Summary of Project Results................................................................................................................. 106 7.1.5 Summary of Project Results for Trips on Fixed Guideway (FG) Modes ............................ 107 7.1.6 Summary of Project Results for Trips Made by 0-Car Households ..................................... 107 7.1.7 Summary of Project Results for Trips on Fixed Guideway (FG) Modes Made by 0-Car Households ................................................................................................................................................................... 107 7.1.8 Summary of Impacts on Automobile Person Miles of Travel................................................. 107 7.1.9 Comparison of Existing, No-Build and Build Station Boardings by Station Mode of Access 108 7.1.10 Comparison of Existing, No-Build and Build Route Boardings by Route Mode of Access 109 7.1.11 Summary of Trips by Submode, Access Mode, Auto Ownership, and Scenario ............. 109 7.1.12 Summary of CTPP Workers and Employees and MPO Estimates of Population and Employment by Scenario........................................................................................................................................ 110 7.1.13 Summary of Highway Time, Distance and Speed........................................................................ 111 7.1.14 District to District Analysis of Gains and Losses Between No-Build and Build.............. 112 7.1.15 Detailed District-to-District Linked Trips and Selected Station-Station Flows.............. 113
7.2 Mapping Results ................................................................................................................................................ 113
8. Procedures for Handling Large Problems, Bus Projects, and Unusual Scheduling Issues.............................................................. 117
8.1 Large Problem Sizes......................................................................................................................................... 117 8.2 Bus Projects ......................................................................................................................................................... 118
9. Appendices ............................................................................. 119
9.1 State FIPS Codes ................................................................................................................................................ 119 9.2 Census MPO Codes ........................................................................................................................................... 120 9.3 MPO Geography Types by County.............................................................................................................. 130
List of Figures
Figure 1. STOPS Application Flow Chart........................................................................................................................ 6
Figure 2. STOPS Program Setup Process .....................................................................................................................11
Figure 3. STOPS Main Menu When Opened the First Time ..................................................................................12
Figure 4. STOPS Dialog to Select GIS Executable ......................................................................................................13
Figure 5. STOPS Main Menu After Selection of TransCAD GIS............................................................................14
Figure 6. Setting TransCAD Quick Start and Second Instance Warning Options ........................................15
Figure 7. STOPS Main Menu After Selection of ArcMap GIS.................................................................................16
Figure 8. Click "No" in TransCAD Map Save Confirmation Dialog .....................................................................16
ii
April 29, 2015
Figure 9. Initial STOPS Menu ............................................................................................................................................22 Figure 10. Standard Windows File Selection Dialog Used in STOPS ................................................................23 Figure 11. Creating a New Folder and Folder Name...............................................................................................23 Figure 12. Creating a New Parameter File ..................................................................................................................24 Figure 13. Station Map View (with user-added state/county boundaries)...................................................30 Figure 14. Station Definition in TransCAD..................................................................................................................31 Figure 15. TransCAD Confirmation After Station Editing.....................................................................................31 Figure 16. STOPS Parameter Screen..............................................................................................................................32 Figure 17. STOPS Parameter Screen With Geography Type, State, and MPO Codes .................................33 Figure 18. Screen Showing Location of CTPP and MPO TAZ Files ....................................................................34 Figure 19. TransCAD Shape File Opening Dialog with Longitude/Latitude (Left) and NonLongitude/Latitude Coordinates (Right).....................................................................................................................39 Figure 20. Arc Map Screen with Longitude/Latitude Coordinates (Top) and NonLongitude/Latitude Coordinates (Bottom) ................................................................................................................40 Figure 21. Select the Projections and Transformations Project Tool ..............................................................41 Figure 22. Arc Map Dialog to Convert Coordinates to Longitude/Latitude ..................................................42 Figure 23. Sample MPO Auto Time Matrix File .........................................................................................................43 Figure 24. STOPS Main Menu After All TAZ and CTPP Files Are Loaded .......................................................44 Figure 25. Sample trip file with Long Trip IDs ..........................................................................................................46 Figure 26. Sample GTFS Calendar File ..........................................................................................................................47 Figure 27. Sample GTFS Stop file ....................................................................................................................................49 Figure 28. Sample GTFS Route File ................................................................................................................................50 Figure 29. Sample GTFS Trip File....................................................................................................................................51 Figure 30. Sample GTFS Stop_Time File.......................................................................................................................52 Figure 31. Sample GTFS Frequencies File ...................................................................................................................53 Figure 32. Sample GTFS PNR File. ..................................................................................................................................55 Figure 33. Sample GTFS Editlist File..............................................................................................................................60 Figure 34. Output from GTFS Feed Validator.............................................................................................................63 Figure 35. GTFS Schedule Viewer Console Window ...............................................................................................64 Figure 36. GTFS Scheduler Viewer Window Showing Error in Route 12 Re-Routing ..............................65 Figure 37. Defining GTFS File Characteristics and STOPS Parameters ...........................................................68 Figure 38. Example GTF File Status Screen ................................................................................................................69 Figure 39. Contents of KCMEXIST\ and SND\ GTFS Subdirectories ................................................................70 Figure 40. Addition of Fixed-Guideway-only STOP_IDs ........................................................................................72 Figure 41. Editlist Re-Route to Use LRT-specific STOP_IDs.................................................................................72
iii
Federal Transit Administration STOPS v1.50 Users Guide
Figure 42. GTFS File Investigation..................................................................................................................................74 Figure 43. Westlake Terminus of SLU Streetcar.......................................................................................................75 Figure 44 Westlake Terminus of Central Link LRT .................................................................................................76 Figure 45. New Stop Added to Stop File.......................................................................................................................76 Figure 46. Re-route existing Streetcar to Extend Service to New Station......................................................77 Figure 47. Exploration of Routes Serving Third Avenue Stops ..........................................................................78 Figure 48. Records Added to Edit List File to Represent Re-Route of 3rd Avenue Routes.....................79 Figure 49. Records Added to Station File to Represent New Streetcar Stations.........................................79 Figure 50. Record Added to Route File to Represent New Streetcar Route..................................................79 Figure 51. Records Added to Trip File to Represent New Streetcar Trips ....................................................80 Figure 52. Records added to the Stop_Time file for New Streetcar Trips ......................................................80 Figure 53. Records Added to Frequency File .............................................................................................................80 Figure 54. Listing of Fixed Guideway STOP_IDs .......................................................................................................82 Figure 55. Scheduler Viewer Showing Extension of SLU Streetcar ..................................................................83 Figure 56. Schedule Viewer After Addition of New Streetcar .............................................................................83 Figure 57. Southbound Route 26 Deviation to 5th/Madison ..............................................................................84 Figure 58. STOPS Main Menu After All GTFS Files are Found.............................................................................85 Figure 59. Adding New Stations to Station File.........................................................................................................86 Figure 60. Dialog to Confirm Creation of Year Definition File ............................................................................88 Figure 61. Year Definition Dialog....................................................................................................................................88 Figure 62. STOPS Main Menu At Beginning of Data Preparation ......................................................................89 Figure 63. Sample District System for Houston, TX ................................................................................................91 Figure 64. District Definition in TransCAD .................................................................................................................94 Figure 65. District Map Following District Definition ............................................................................................94 Figure 66. Dialogue for Running Batch Steps and De-Selecting Scenarios....................................................97 Figure 67. STOPS Main Menu Before Batch Steps....................................................................................................98 Figure 68. STOPS Main Menu After Completion of Batch Steps .........................................................................99 Figure 69. Example Report File .................................................................................................................................... 100 Figure 70. Section 1 - Run Parameters ...................................................................................................................... 101 Figure 71. Station Listing ................................................................................................................................................ 102 Figure 72. Initial Calibration Statistics ...................................................................................................................... 102 Figure 73. Production District - Station Group Results ...................................................................................... 104 Figure 74. Station Group Boardings Prior to Adjustment.................................................................................. 104 Figure 75. Station Group Boardings After Adjustment ....................................................................................... 105
iv
April 29, 2015
Figure 76. Summary of Project Results ..................................................................................................................... 106 Figure 77. Origin Station to Destination Station Project Flows....................................................................... 107 Figure 78. Incremental Automobile PMT ................................................................................................................. 108 Figure 79. Average Weekday Station Utilization by Scenario and Mode of Access................................. 108 Figure 80. Weekday Route Ridership......................................................................................................................... 109 Figure 81. Summary of Linked Transit Trips by Submode, Access Mode, and Auto Ownership....... 110 Figure 82. Summary of District Level CTPP, Population, and Employment............................................... 111 Figure 83. Average Highway Time for Existing Scenario................................................................................... 112 Figure 84. Dialog for Specifying Map Output Options ......................................................................................... 114 Figure 85. Map of Project Trips to All Destinations ............................................................................................. 114 Figure 86. Map of Walk Access Fixed Guideway Only Project Trips to CBD .............................................. 115
List of Tables
Table 1. STOPS Directory Structure...............................................................................................................................20 Table 2. State FIPS Codes ................................................................................................................................................ 119
v
Federal Transit Administration STOPS v1.50 User Guide
1. INTRODUCTION
The Simplified Trips-on-Project Software (STOPS) is a series of programs designed to estimate transit project ridership using a streamlined set of procedures that bypass the time-consuming process of developing and applying a regional travel demand forecasting model. STOPS is quite similar in structure to regional models and includes many of the same computations of transit level-of-service and market share found in model sets maintained by Metropolitan Planning Organizations. What makes STOPS much simpler to use than regional models is the following:
1. Estimates of total origin-to-destination travel are derived from Census data rather than elaborate trip generation and destination choice procedures. This avoids the need to calibrate these tools to the degree of accuracy required to estimate transit ridership.
2. Representations of transit levels-of-service are derived from timetable information, bypassing the need to develop detailed transit networks in the planning environment. Timetable information is already available at most agencies and is much more accurate than the representations of travel time and frequencies contained in typical planning networks.
3. The model calibrates itself to represent current conditions. This means that the months, and sometimes years, that are spent developing and documenting effective forecasting tools can be avoided.
Although STOPS represents a significant simplification over existing procedures, it still requires careful development of input information that describes existing transit ridership, existing transit schedules and future transit service scenarios. This document describes the process that should be followed to install STOPS, develop input data, and run the STOPS model to generate estimates of trips on transit projects. This document describes Version 1.50 of STOPS. This version is similar in operation to prior releases but is designed to generate more accurate results due to the following major changes:
Non-home based trip procedures have been refined based on experience with STOPS 1.01 and 1.02 which generated more NHB transit trips in large central business districts than actually occur.
The number of separate GTFS directories that can be combined in a single STOPS run has been increased from 4 to 20.
Schedule-based path-building has been updated so that trips are scheduled to reach the destination at a specific time (e.g., arrive at work by 8:00 am) rather than depart the origin at a specific time (e.g., depart home at 7:30). Although similar for shorter trips, the arrival time approach works much better for very long trips in which the traveler may need to leave home by 6:00 am to reach work by 8:00 am.
Path-building was also updated so that each interchange has a different arrival time rather than having all interchanges use a single time. This variation in arrival times is designed to
1
Federal Transit Administration STOPS v1.50 Users Guide
reflect the fact that different travelers may need to arrive at work at different times. This change results in more robust estimate of trips-on-project that are less dependent on a single (and arbitrary) assumed arrival time.
Wait time estimates have been updated to reflect the scheduled difference between arrival time and either the time the traveler wishes to be at the destination or the departure time of the next vehicle. This computation replaces the process that uses station-to-station frequencies to estimate the average waiting time.
The model calibration has been updated to reflect actual experience with multiple cities with new fixed guideway systems.
New capabilities have been added to represent impedances for fixed guideway stations (and other stops) including:
o Stations can accept additional values of STOPSType to indicate the number of levels between the street and platform that corresponds to the additional walking time required to reach the actual bus stop or train platform.
o Additional time can added to represent station impedance. This capability is provided by adding optional fields to the station file that specify additional time for walk access, kiss-and ride access, park-and-ride access, and transfers (separately for connecting stops in the same GTFS file set or directory or a different GTFS file set). These times can be used to:
Represent the additional time required to use transit beyond that represented by simple straight-line distances implied by the latitude and longitude or the degree of grade separation
Represent the impact that fare policy may have on the desirability of specific transit services
Account for usage patterns as revealed by actual ridership
o STOPS now can read the GTFS transfers.txt file (if provided) to code (or prevent) specific station-to-station transfer times. The values coded in transfers.txt override the times in the station file.
o Park-and-Ride lots can be coded with a time parameter used to represent the additional time required to travel from a parked car to the transit platform. This capability allows the user to more accurately represent the time required to park a car and walk to transit. It also can be used to institute parking capacity-based shadow pricing.
STOPS has been enhanced to simplify the process of coding of BRT facilities. STOPS now reports project ridership for bus routes and bus "stations" (BRT bus stops) and it is not necessary to code BRT routes as fixed guideway routes. Note, however, that it may still be desirable to code BRT as a fixed guideway route if the BRT operates on a separate right-ofway.
Redefined the Fixed Guideway Visibility Factor so that nearly all fixed guideway projects can use the full amount (1.0). In earlier versions, only Heavy Rail systems were coded with
2
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
1.0. LRT and commuter rail systems were coded with 0.5 and some streetcars were coded with lower values. With version 1.5, only those streetcars or BRT routes that are partially in a mixed traffic should be coded with a visibility factor less than 1.0.
Revised the process used to identify project trips in cases where the project may be used by bus or rail customers who neither board nor alight at a project station. With Version 1.50, only new project stations need to be identified. Any trip boarding, alighting, or passing through the station will be identified even if the trip neither boards nor alights at an identified station.
Revised the recommended practices for coding station groups.
Added the capacity to process split Traffic Analysis Zones, Tracts, or Block Groups.
Increased the maximum problem size that STOPS can handle. Current limits are:
o Number of TAZs (or tracts or block groups depending on Census Geography) is 9,000.
o Number of stations (or bus stops identified as stations) with counts that can be used for station group calibration is now 10,000.
o Number of new stations (or other stations where station-to-station flows are reported) is now 250.
o Number of station groups for station group-to-station group reporting (can include stations that are not separately reported in the station-to-station fields) is now 250.
o Number of GTFS files sets for each scenario is now 20.
Added a new transit route statistics report (Tables 10.03 and 10.04 in the STOPS report file) to show revenue mile and hour operating statistics for each operated route for the time spans used for simulating peak and midday periods. This report is designed to identify large and unintended changes in operating assumptions between the existing, no-build, and build scenarios.
Revised the effects of the visibility factor on mode-specific constants (parameters which affect the choice of path-type and access mode for each auto ownership) and nesting constants so that a fixed guideway visibility factor of 0.1 applied to a fixed guideway project generates a similar number of trips-on-project as the same service coded as a bus.
Added a new "Group Calibration Approach" option to the STOPS parameter screen that allows the user to control the station calibration process. In earlier versions of STOPS, station group calibration was always invoked so that STOPS adjusted both mode-specific choice constants and trip factoring to match existing station group ridership. This factor was computed for the existing scenario in the current year and then applied to the no-build and build scenarios for the horizon year. With Version 1.5, the default is changed so that no station calibration is performed automatically. The user can select from among several new optional procedures for implementing station group calibration if this functionality is desired. See Section 4.8.5 for more information.
3
Federal Transit Administration STOPS v1.50 Users Guide
Version 1.50 Changes Affecting Setups from Earlier Versions: The STOPS setups from earlier versions can be used with Version 1.5 with only a few items that require review and modification:
1. The STOPS Fixed Guideway visibility factor should be set to 1.0 for all types of fixed guideway transit.
2. Stations with a STOPS Type code indicating grade separation (STOPSType greater than 2) separation should be reviewed to identify the degree of vertical separation between the station platform and the street.
3. Stations groups should be redefined so that new stations are given different groups from existing stations. Station groups for existing stations should be defined so that similar stations (in terms of location, routes, and markets) are grouped together.
4. It is no longer necessary (but still allowed) to set NewStation values "2" and "3" to indicate fixed guideway stops on either side of a "gap-filler" project. With Version 1.50, users need only code a "1" for the stations that are part of a project. See Section 4.2 (and the footnote for the NewStation code) for advice on coding a gap-filler project that has no new station.
5. Some internal working files have a different structure with Version 1.5. Be sure to re-run all batch steps (Step 11, all elements) the first time Version 1.5 is run with an existing STOPS setup.
6. The default type of station group calibration has changed from full station group factoring to no station group calibration. The user can select station group calibration type 9 to have STOPS apply a similar type of station group calibration to that employed in previous version. See Section 4.8.5 for more details.
The remainder of this document describes the STOPS model, how it is installed, how it can be used to generate estimates of fixed guideway ridership, and the output reports that it generates.
4
April 29, 2015
2. OVERVIEW OF STOPS AND ITS APPLICATION
Federal Transit Administration STOPS v1.50 User Guide
This section describes the STOPS model and provides guidance on its application.
2.1 STOPS Model Structure
STOPS is designed to estimate fixed guideway transit trips on a project using readily available data and procedures that are calibrated to match both local and national experience related to rail and BRT ridership. STOPS is similar, in concept, to traditional trip-based four-step travel forecasting models. This structure is more complex than a simple direct-generation model so that STOPS can discern project ridership in a wide range of situations including:
A fixed guideway starter line An extension to an existing fixed guideway line A new line added to an existing fixed guideway system A gap-filler project in which a new segment connects two previously separated fixed
guideway systems
To be able to measure project ridership in all of these situations, STOPS includes the capability to represent the transit system and the project definition so that trips can be identified that benefit from the investment in new fixed guideway services.
In STOPS, person trip tables (i.e., the results of Steps 1 and 2 of traditional four-step models) are developed from Year 2000 Census Transportation Planning Package (CTPP) Journey-to-Work (JTW) flows that are updated to account for current and future year demographic growth. Transit timetable data from local General Transit Feed Specification (GTFS) files are used to develop zoneto-zone transit, access, and waiting times. A traditional nested logit mode choice model computes the transit shares stratified by access mode (walk, kiss-and-ride, and park-and-ride) and sub-mode (fixed guideway-only, fixed guideway and bus, and bus-only).
An overview of STOPS is presented in Figure 1.
Similar to nearly all multi-modal travel forecasting models, STOPS has three parallel tracks:
Highway supply. The left column in the flow chart represents information about the highway system in the region. STOPS does not directly process information on highway attributes and instead relies on estimates of zone-to-zone highway travel times and distances obtained from regional travel forecasting model sets maintained by Metropolitan Planning Organizations (MPOs). Since MPO models might not still use the same geographic (zone) system used in the CTPP, STOPS includes a procedure to convert MPO geography to CTPP geography.
Note that although STOPS allows (and requires) the user to have separate Census and MPO zone systems, all geographic files MUST be coded with longitude and latitude coordinates consistent with files prepared by the U.S. Census Bureau. Any geographic file obtained from an MPO that is specified in State Plane Coordinates must be converted to longitude and latitude coordinates prior to use with STOPS.
5
Federal Transit Administration STOPS v1.50 Users Guide
.
Figure 1. STOPS Application Flow Chart
Transit supply. The right column represents information about the transit system. Like traditional models, transit network characteristics are used to build zone-to-zone level of service (skim) matrices and load transit trips to determine ridership by route and station. Unlike traditional forecasting models, STOPS does not use elaborate hand-coded networks. Instead, STOPS takes advantage of a recent advance in on-line schedule data--the General Transit Feed Specification (GTFS). This data format is a commonly-used format for organizing transit data so that on-line mapping programs can help customers find the optimal paths (times, routes, and stop locations) for their trips. STOPS includes a program known as GTFPath that generates the shortest path between every combination of regional origin and destination. This path is used for estimating travel times (as an input to mode choice) and for assigning transit trips (an output of mode choice) to routes and stations.
Travel Demand. The central column represents the demand side of STOPS. STOPS uses Year 2000 CTPP JTW data to estimate zone-to-zone demand for travel (i.e., travel flows) as an input to the models that determine the mode of travel. This data is adapted to represent current and future years by using MPO demographic forecasts to account for zone-specific
6
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
growth in population and employment. A traditional nested logit mode choice model is used to determine the proportion of trips utilizing transit stratified by access mode and transit sub-mode. Results of mode choice are summarized in a series of district-to-district flow tables.
2.2 Suggested Application Approach
STOPS is designed to simplify the process of developing and applying travel forecasting procedures while maintaining much of the internal sophistication of regional travel forecasting models. Nevertheless there are still a number of implementation and application steps that must be followed to successfully use STOPS to estimate fixed guideway transit ridership.
In order to streamline the process of applying STOPS, the user may wish to employ an incremental approach that breaks the STOPS application down into a series of simple steps including:
Implement STOPS on the user's computer.
Run STOPS for the current year and existing transit services and test the local model calibration. This step tests the local calibration of STOPS with existing transit services and current socioeconomic conditions in the corridor. STOPS is fundamentally organized around three separate transit service scenarios--(1) the existing, (2) the no-build, and (3) the build conditions. A current year / existing transit scenario run can be created by configuring all three scenarios so that they represent the existing transit schedule.
Determine the characteristics of transportation system if the project is not built (i.e., the nobuild scenario). This scenario is used as a point of comparison for the purpose of computing incremental transportation impacts such as the change in VMT. After defining no-build schedules, STOPS can use this information in the no-build and build scenarios to confirm that the no-build is properly defined.
Code the full project in the build network and run STOPS for the current year with all three scenarios--existing, no-build, and build. This step will generate current year project ridership, a key input to the New Starts reporting process.
If optional future year forecasts are desired, the user can develop future year demographic data and run STOPS for the forecast year. The result of this step is optional future year project ridership.
2.3 Input Data
STOPS is designed to make use of pre-existing data sources on transportation supply and demand for nearly all aspects of the ridership forecasting process. The only information that must be created specifically for a STOPS application are transit timetables (in GTFS format) representing the no-build and build scenarios.
Data are obtained from four sources:
Federal Transit Administration: The FTA STOPS website includes copies of the CTPP data used by STOPS. Data is organized by state, and users can download one or more states to represent travel patterns in their corridor. Data in each state file include geographic files in ESRI shape file format describing Census Traffic Analysis Zones, Block Groups, or Tracts
7
Federal Transit Administration STOPS v1.50 Users Guide
(depending on the geographic unit of analysis of CTPP data in the project corridor), Census Blocks, and Parts I, II, and III of the CTPP.
Local Transit Agencies. Transit timetables in GTFS format for existing conditions.
Metropolitan Planning Organizations. Geographic files in ESRI shape file format describing the agency's traffic analysis zone system with information on zone number and current and forecast year population and employment by zone. MPOs also provide zone-tozone estimates of highway time and distance for the current and forecast year.
Project Sponsors. Project definition include station locations, station grade level (i.e., at grade or grade-separated), station presence or absence of park-and-ride, and operating plan at a sufficient level of detail to synthesize a transit schedule for the new service.
2.4 Computer Resources
STOPS is designed to run on a computer running a 32- or 64-bit version of Microsoft Windows such Version 7, or Version 8. At least 4GB of installed memory is required and 8GB is recommended.
STOPS generates large tables of zone-to-zone travel times and output summary files. The size of these files is related to the number of zones contained in the metropolitan area's Census Traffic Analysis Zone (TAZ) system1 and the number of different forecast years that are generated. In practice the storage required for each scenario ranges from 20 GB to 100 GB. A USB external hard drive is recommended for storing scenario results and can also be used for running STOPS.
STOPS uses ESRI Shape files to describe the geographic relationships between Census TAZs (or block groups or tracts, depending on the availability of CTPP data), MPO TAZs, and station locations. The user should have access to Geographic Information System (GIS) software to update these files to define station locations and zonal district aggregations. Any GIS software that can read ESRI Shape files can be used; however, STOPS automates the linkage to two of the most common GIS packages used in transportation analysis and modeling: TransCAD Version 5.0/6.0. and ArcMap Version 10.1.
2.5 Skill Requirements
STOPS is designed for use by technical staff with a basic understanding of the principles of travel forecasting and model application. Skill requirements include:
Experience using one or more GIS packages and the ability to create GIS layers in ESRI shape file format representing station locations and MPO zone systems.
Understanding of the mechanics of travel forecasting including the concept of a "run", the types of data used as input to the travel forecasting process, and techniques for reviewing model outputs.
Familiarity with the regional transit system including the different agencies providing service and the nature of the scheduled service in the region.
1 In some cases (explained later in the document) Census Block Groups or Tracts are used in place of Census Zones. No matter which geographic unit of analysis is selected, the required hard drive space is a function of the number of these units.
8
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
2.6 Time Requirements
STOPS is designed to dramatically reduce the time required to prepare forecasts of transit trips on a project. The existing process required to prepare a fully operational local transit forecasting model often exceeds a year if the full range of model development activities is required. These steps include a comprehensive transit passenger survey, model calibration, and refinements required to generate a reasonable representation of existing transit patterns while conforming to best practices regarding model structure and parameters.
By contrast, STOPS utilizes data from a variety of sources to represent travel flows and transit supply, bypassing the need to calibrate these challenging model elements. It utilizes relatively conventional procedures for estimating mode shares and then calibrates these results to match estimated home-to-work transit shares attracted to each zone (from the CTPP), local regional transit boardings (from the National Transit Database or other sources), and station level (aggregated to groups) ridership data in cities where fixed guideway transit is already present.
STOPS requires carefully-developed input information and this data takes time to obtain and prepare. In general, STOPS can be used to generate estimates of project ridership within the following timeline:
Prepare data and run model for current/existing conditions--1 to 2 weeks. In some regions, all information required to run STOPS is available on-line and 1 to 2 days are required to download the data files and reformat these data to the structure expected by STOPS. In other areas, these data must be obtained from transit agencies and MPOs and a greater amount of time will be required to request and obtain the needed input files.
Developing data for build scenarios--1 to 2 weeks. The amount of time required to prepare a build scenario will depend on the complexity of the alternative. A new fixed guideway line that is introduced into a corridor with relatively minor changes to the local bus service can be coded in as little as a day. A more complex project in which a new fixed guideway line is integrated into an existing system with significant changes to feeder and/or competing bus lines could take up to a week to code.
Running STOPS--3-8 hours. STOPS, itself, is fairly fast. Even for relatively large transit systems such as King County Metro and Sound Transit in Seattle, STOPS can be run in 3 hours.
Reviewing results 1 to 2 weeks. As is true of any forecasting application, the time spent reviewing results is a critical part of the process of generating ridership forecasts. At least a day should be anticipated for reviewing every aspect of the forecasting process including both the characteristics of the transportation supply and transit demand to make sure that every aspect of the model aligns with the intended definition of the project. STOPS may need to be re-run, if changes to the transportation supply, demographic forecasts, or calibration parameters are required. This process of code, run, and review may need to be repeated several times over the course of several weeks to generate a final estimate of trips on a transit project.
9
Federal Transit Administration STOPS v1.50 Users Guide
3. INSTALLING STOPS SOFTWARE
This section describes the steps required to install STOPS on a new computer.
3.1 Installation Steps
STOPS can be downloaded from the FTA STOPS web page. The downloaded file is named STOPSv[9.99]Install.zip2. To install STOPS, create a directory on the computer where STOPS is to reside and copy the distribution file to this directory. Extract the contents of this zip file (STOPS_setup.bat and STOPSPackage.dat) to this directory and then double click on STOPS__setup.bat to complete the installation. The program extraction and setup process is illustrated in Figure 2. If the program is successfully installed, the STOPS program directory should have the application (STOPSMenu.exe) and two subdirectories (STOPSComponents and datatemplates). The user may want to create a short-cut to STOPSMenu.exe and copy it to the desktop for easy access to STOPS.
2 9.99 stands for the actual current version of STOPS, currently 1.50 at the time this manual was written.
10
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 2. STOPS Program Setup Process A zip file containing sample data is also available from the FTA Website. This zip file
includes all of the information necessary to represent a fictional project in Seattle, WA. This folder can be unzipped to a location on the user's computer (e.g., j:\STOPSRun\SEA) and run to test the implementation of STOPS. The examples in this menu are mostly based on the results of this project so the reader can run this sample set to generate many of the examples on a local computer.
11
Federal Transit Administration STOPS v1.50 Users Guide
3.2 Specifying Automatic GIS Linkage
After the STOPS software is installed on the computer it should be opened by double clicking on the STOPSMenu Application (or the shortcut). The first time that STOPS is used after installation, the screen shown in Figure 3 appears.
Figure 3. STOPS Main Menu When Opened the First Time
The message "No GIS Selected" appears at the top of the dialogue box to remind the user that no automatic GIS linkage has been defined. Until this is updated, that means that STOPS will prompt the user to manually edit station and district shape files.
To define an automatic GIS linkage, the user can click on the button "Select GIS Executable". When this is done, the standard windows file selection box appears as shown in Figure 4.
Use the file selection dialog to identify the location of one of the two files shown below:
TransCAD executable TCW.exe (typically located at C:\Program files (x86)\TransCAD\tcw.exe); or
ArcMap executable ArcMap.exe (typically located at C:\Program files (x86)\ArcGIS10.1\bin\ArcMap.exe))
12
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
After the GIS executable is selected, the message at the top of the dialogue changes to indicate that STOPS has been properly associated with one of the recognized GIS packages. Figure 5 shows the appearance of the Main Menu after STOPS is successfully associated with the TransCAD GIS package.
Figure 4. STOPS Dialog to Select GIS Executable
13
Federal Transit Administration STOPS v1.50 Users Guide
Figure 5. STOPS Main Menu After Selection of TransCAD GIS
14
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Before TransCAD can be used in STOPS, it must be configured to allow it to open without using the quick start window and without warning the user if there is a second instance of TransCAD running. This is done by opening TransCAD and selecting the Edit > Preferences menu option. Unclick the start up and second instance warning options as shown in Figure 6.
Figure 6. Setting TransCAD Quick Start and Second Instance Warning Options If the user selects ArcMap, then the python executable file should also be defined. This program is named pythonw.exe and is typically installed at c:\python27\ArcGIS10.1\. When ArcMap is selected the appearance of the main menu is shown in Figure 7.
15
Federal Transit Administration STOPS v1.50 Users Guide
Figure 7. STOPS Main Menu After Selection of ArcMap GIS
In both TransCAD and ARCGIS, the user interface sets up the environment for the user to edit and display various data files. When editing is complete, the user must terminate the GIS using a menu command or clicking on the red "X" at the upper right hand corner of the screen. In some cases the GIS program will ask if it is OK to save the map (See Figure 8 for an example from TransCAD). The User should click "No" since the GIS system saves data as it is entered; this question is asking if it should save the map display settings which is not necessary since STOPS generates this information each time it is needed.
Figure 8. Click "No" in TransCAD Map Save Confirmation Dialog
16
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
4. SCENARIO SET-UP STEPS
STOPS develops predictions of transit fixed guideway ridership based on the experiences of a wide variety of rapid transit, light rail transit, commuter rail, streetcar, and bus rapid transit systems built over the last 40 years in various cities across the United States. This experience is adapted to new settings according to:
Year 2000 trip-making characteristics in the corridor as represented by the Year 2000 Census Transportation Planning Package (CTPP) Journey-to-Work (JTW) data sets.
Information on the density of the street grid conveyed by Census Block definitions. Forecasted changes in population and employment from the Year 2000 to the current year
and future forecast years that are prepared by local Metropolitan Planning Organizations (MPOs). MPO data is also used to characterize travel times on the regional highway system. Characteristics of the transit system as represented by automated schedule data and supplemental information on station characteristics, park and ride locations, and existing ridership.
Each source of data must be understood and, in many cases, prepared for use by STOPS. This chapter describes the various input data and the steps that must be taken to set-up a STOPS scenario and prepare data for use in generating forecasts of fixed guideway ridership.
At this stage in the process, the user needs to organize the analysis, collect data from FTA's STOPS webpage, obtain data on highway travel times and socioeconomic forecasts from the regional MPO, collect existing schedule data in GTFS format, and prepare information related to the transit project to be studied. In some cases (station locations and district definitions), STOPS, itself, is used to prepare input data. Other data (CTPP and Census Data) are downloaded and used "as-is." In other cases (GTFS scenario definitions), the user must create the input data using a text editor.
Before the user begins, several key decisions must be made based on the availability of Census data and local information that will streamline the process of setting up a STOPS run. These decisions include:
1. What is the project corridor? STOPS defines the project corridor as being all areas within 25 miles3 of a project station or within 25 miles of existing fixed guideway transit stations that connect4 to the project. It is a good idea to identify the location of existing and potential project fixed guideway stations prior to beginning the process of data assembly. To facilitate this process, the second step in setting up a STOPS run involves identifying station locations in a GIS. The user can use standard GIS functions to create a 25 mile buffer around the set of existing and future stations to create a GIS representation of the project corridor.
2. What States and MPO regions are included in the project corridor? CTPP data are organized around states and MPO regions so the next step is to identify the states and MPO regions that are included in the project corridor. This can be done by adding a state layer to
3 Straight line distance 4 "Connect" in this context means that transit passengers on the project may utilize the connecting service or that the other services will be helpful in calibrating STOPS. As a practical matter, this means that all or nearly all fixed guideway stations in a metropolitan area will be included in this definition of the project corridor. The only exception will occur in very large metropolitan areas where the inclusion of distant and not relevant stations may not be necessary.
17
Federal Transit Administration STOPS v1.50 Users Guide
the GIS view showing stations and buffers described above and then identifying all states that overlap the 25 mile buffer. MPO coverage can be determined by identifying the counties that are included in the buffer area and comparing this list to the MPO counties provided in Section 9.3.
3. What geography type will be used in the analysis? STOPS supports Census Traffic Analysis Zones (TZ), Census Block Groups (BG), and Census Tracts (TR) as the units of geographic analysis. Only one type of geography can be used in each scenario or model run. TZ or BG are the most detailed options but can only be used for situations where the entire corridor lies within a single MPO region5 and the Census Bureau collected information at the TZ or BG (either one but not both) level throughout the corridor. A county-by-county listing of MPO areas and geography types appears in Section 9.3. If all of these conditions are met, then the user can select TZ or BG as the geography type. Otherwise, users must select TR as the geography type.
4. What years will be modeled? STOPS allows the user to define up to four different application years.
a. The current year is used in the local calibration element of the model and may also be used for forecasting. The current year must be supported with information on zonal population and employment and optional information on regional transit boardings, regional home-to-work linked transit trips, and fixed guideway station boarding counts.
b. Optional forecast years include: opening year, 10-year, and 20-year forecasts and (if defined) require just population and employment data for each MPO zone in the corridor.
5. What are the definitions of the existing, no-build, and build scenarios? STOPS expects the user to define 3 distinct transportation scenarios:
a. Existing scenario (EXST). The "EXST" scenario represents the existing transit system and is used with current year socioeconomic data to calibrate the local application of STOPS to observed current year ridership. The resulting calibration is applied to all other scenarios.
b. No-build scenario (NOBL). The no-build scenario represents the future year network that is to be used as the basis of comparison for the project for any statistic requiring information on incremental impacts of the project (e.g., Vehicle Miles of Travel). The no-build scenario includes the existing system together with relevant transit elements that are already committed for construction and operation.
c. Build scenario (BLD-). The build scenario represents conditions after the project fixed guideway transit system is constructed and in operation.
STOPS requires information on the service plan, station locations and station characteristics for each transportation scenario. STOPS can, however, accept the same files for each alternative if, for example, the EXST and NOBL scenarios are identical.
5 In some cases, a small portion of the corridor's expected ridership shed may lie outside of the MPO region. If the demand from this area is expected to be relatively small, it may be appropriate to ignore this area in favor of generating more detailed estimates in the portion of the corridor that is within the MPO boundary.
18
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
6. How is automated schedule data structured in the corridor? STOPS uses data organized in General (formerly Google) Transit Feed Specification (GTFS) format. Nearly every large transit agency in the United States has this data available and it is possible to convert manual schedule information into this format if the data is not already available. In some cities with multiple transit operators, each transit operator creates its own separate GTFS files. STOPS allows the user to combine up to four independent datasets to make up a regional schedule. STOPS introduces two extensions to the specification to allow the user to code Park-and-Ride (PNR) locations and to introduce simple changes to the GTFS files to represent new services.
It is useful to understand the STOPS directory structure which is shown in Table 1 . The STOPS project root directory can have any legal Windows name and can be a subdirectory to the drive's root directory or a subdirectory of any other folder. At the beginning of a run, the STOPS directory will only have one file, a parameter file, and a series of subdirectories. Both the parameter file and the directory structure are created by the STOPS program and no manual steps are required. As noted above, the user may copy sample data to a new folder and use this information as the basis for a STOPS run. In that case, STOPS will add the required additional directories. The directory name is not strictly limited in length. However, the user should note that Windows may limit the length of file name (drive, directory, name, and extension) to 255 characters and many STOPS displays are not wide enough to display very long filenames. STOPS maximum suggested filename lengths are as follows:
Maximum length of control file name (including drive letter, colon, directory names, backslashes, filename, and extension) is 80 characters and fewer than 40 characters are recommended.
Maximum length of all GTFS subdirectory names (excluding the root directory or "inputs\") is 20 characters and under 10 characters is recommended. If more than 4 GTFS filesets are used, then even shorter directory names (i.e., 2-character codes) may be required.
STOPS periodically tests the lengths of key file names to confirm that the directory names will not generate file names lengths that are too long. Nevertheless, the user should keep file name lengths under these guidelines to minimize the chance of problems in later steps.
19
Federal Transit Administration STOPS v1.50 Users Guide
Table 1. STOPS Directory Structure
Directory
Example
Contents
STOPS project root Inputs Logfiles GTFS subdirectories of Inputs that contain information for a particular agency and/or scenario
Districts Scratch
Skims GTFOutput
STOPS Reports OutputData
C:\STOPSProject\ C:\STOPSProject\Inputs\ C:\STOPSProject\Logfiles\ C:STOPSProject\Inputs\[Dir 1]\ C:STOPSProject\Inputs\[Dir 2]\ C:STOPSProject\Inputs\[Dir 3]\ Etc.
C:\STOPSProject\Districts\ C:\STOPSProject\Scratch\
C:\STOPSProject\Skims\ C:\STOPSProject\GTFOutput\
C:\STOPSProject\STOPS\ C:\STOPSProject\Reports\ C:\STOPSProject\OutputData\
Parameter (control) file
Input data.
STOPS program logfiles that determine the completion status of each step.
GTFS schedule data for agency and scenario defined by Directory 1, Directory 2, Directory 3, etc. Note these directories are not created by STOPS; They are created by the user when a new GTFS file set is created for each agency and/or scenario. [Dir 1], [Dir 2], [Dir 3], etc., can be any user-defined Windowssupported subdirectory name.
District definition
Temporary working files that can be deleted by the user after each STOPS run is complete and checked.
Output transit level-of-service matrices (often known as skim files)
GTFS files created by STOPS from input information provided by User (accounts for edits performed by STOPS) for visualizing the built schedules.
Empty directory that user can use to store STOPS-related files.
STOPS and related output reports
Mapable STOPS output data files and various outputs that can be used to understand the results of each STOPS run.
20
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
4.1 Defining the STOPS Run Parameters
The STOPS menu screen (after the GIS software is selected) looks like the example shown in Figure 9. Each aspect of a STOPS run is labeled as "Files Not Found" or "Not Complete"at the beginning of a run. Each item on the left side of the menu (Set-up and Data Preparation Steps) will switch to "FILES FOUND!" when STOPS detects that the necessary files have been properly assembled. Please note that in some cases a "FILES FOUND!" status label does not necessarily mean that the file is ready for use. In many cases a user might defer data entry for one or more elements of a data file (e.g., GTFS file parameters before the GTFS files have been constructed). STOPS does not know if the various files have been fully populated with accurate data, only that the files appear to be complete and suitable for running STOPS. The user is responsible for completing data entry for files that are only partly populated. On the right side of the main menu (Batch Steps), the label switches to "COMPLETE!" to indicate that the batch step successfully ran to completion and generated the necessary information to proceed to the next step. To create or select an existing parameter file (also known as a "control" file) that will control a STOPS model run, click on "1. Select/Create Parameter File". This will open a standard windows dialog for selecting a file (see Figure 10). If the parameter file has been previously created, use the dialog to select the directory and filename containing the parameter file. If this is the first time that you are using STOPS or is a brand-new project, this dialog can be used to create a new folder (using the "New Folder" Button, see Figure 11) where the project will reside. Please note that just like all Windows applications, the "New Folder" Button creates the new folder at the location that is highlighted in the body of the dialogue so the user should first point to the main folder where the project should reside (e.g., d:\stops in this example) before pressing the "New Folder" button. The user should rename the folder to describe the project ("SEA" in the example for "Seattle"). Double click on the new folder to open it and then type the name of the desired parameter filename in the line labeled "File name:". It is not necessary to enter the file extension (".ctl"), just the name is required (Seattle in the example). If this is a new file, then STOPS will ask you to confirm that you want to create a new parameter file. Click "Yes" to proceed or "No" to select another filename. If "Yes" is clicked, STOPS will ask the user if the new scenario should be created by copying another scenario. If "Yes" is clicked in response to this question, then a dialogue will open that asking the user to select the control filename of the scenario to be copied. If "No" is clicked, then STOPS will create a blank scenario. This dialogue is illustrated in Figure 12. This action will result in STOPS creating the STOPS sub-directory structure that will provide a home for the STOPS input and output data files. All directories are created except those which relate to individual GTFS file sets which are manually created by the user as those files are prepared.
21
Federal Transit Administration STOPS v1.50 Users Guide
Figure 9. Initial STOPS Menu
22
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 10. Standard Windows File Selection Dialog Used in STOPS
Figure 11. Creating a New Folder and Folder Name
23
Federal Transit Administration STOPS v1.50 Users Guide
Figure 12. Creating a New Parameter File
24
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
4.2 Station Locations
STOPS preparation begins with a file defining the station locations, names, types, and information that relate these stations to the region's automated schedule data. This file starts with a nationwide database of existing stop locations that is included with the STOPS program and is automatically copied the first time that the STOPS step that specifies station locations is run. This file is pre-populated with many existing stations across the United States6 and includes the station name, latitude, and longitude. This file includes a variable called "STOPSType" that indicates whether or not the station is active for this scenario. All stations in the pre-populated database have a null value for this variable which means that the station is not part of the scenario. The user should identify which of the existing stations should be enabled, whether or not it has Park-andRide, and whether or not the station is at-grade or grade-separated. New stations can also be added to this database using standard GIS tools.
When the station database is complete for a scenario, it should include all stations that currently exist in the corridor, all stations that are part of the no-build, and all stations that are to be built as part of the project. Stations represent just the fixed guideway portion of service at a particular location and stations shared by multiple agencies should be coded as distinct stations, each having ridership information for that agency.
Data to be entered into the station file include:
Station Location latitude and longitude in decimal degrees (e.g., 38.892427 or 77.084714). This value is generated by the GIS software by locating the station point on a map.
STATIONSEQ (Station sequence) an integer used to specify the sort order of stations for reports. This number has no impact on STOPS processing and is only used to make output reports more readable. The station sequence should organize stations in a logical order. One approach is to have all new project stations have the lowest numbers and be in the order that they exist on the line. This will make these stations easier to see in the STOPS report. For each existing or no-build line, code the sequence for each line from the outer-most station to the CBD. Organize the lines so that each mode (e.g., LRT) is grouped together before beginning the next mode (e.g., commuter rail).
STATION (Station name) the full name of the station (up to 35 characters).
STAT_CODE (Station code) a short name of up to 9 characters used for some column headings.
STAT_GRP (Station group) a numerical group code (generally, 1 to 20 but may be as high as 250) that is used for reporting and for aggregations for station-level calibration. Station groups should be designed to represent groups of similar stations and are a key element of the STOPS internal calibration process. This capability allows the user to define a station
6 This database is several years old and is provided as a starting point to define stations. In some cases, stations will have opened, closed, or moved since this database was created. The user should review each station in the station database to confirm that the station locations are approximately accurate. STOPS only uses the station file coordinates to identify a 25 mile buffer (GTFS files provide more specific locations for purposes of determining walk access). This means that the stations in the station database need only be geolocated to within ¼ mile of the actual station location and that the station data in this section be coded on the record.
25
Federal Transit Administration STOPS v1.50 Users Guide
group that includes similar stations, both existing and new. The self-calibration process adjusts STOPS to match existing stations and then applies these results to new stations.
Version 1.50 Highlight: In previous versions of STOPS, new stations were grouped with similar existing stations. Starting with Version 1.50, new stations associated with projects should be given a new group number that is different from any existing station group. The only exception would be for cases were a single new station is constructed in the vicinity of a similar station serving a similar market. The STOPSType and Newstation variables have additional (or changed) values that should be reviewed when converting older STOPS applications to Version 1.50.
GRP_NAME (Group Name) The name of the group defined in STAT_GRP. Each station group should be given a name just once (i.e., only one station record in each group will have an assigned group name). STOPS will assign that name to all stations with that group number. If multiple names are attached to a single group number then the last name in the file will be applied to all stations in that group.
DAILYBOARD (Daily boardings) the number of counted current year boarding passengers at the station. This number is used for station-level calibration.
STOP_ID1 to STOP_ID4 (GTFS STOP_IDs) -- up to 4 stop_ids defined in the automated schedules (GTFS) that describe the stops that, together, represent the fixed-guideway platforms at the station. A comprehensive discussion of GTFS schedule data is presented in Section 4.8.1. The STOP_ID must agree exactly with the stop_ID used in the path building program (GTFPath). This is most easily accomplished by running Step 5a, 5b, and/or 5c (GTFS Test Steps) which will generate a listing of fixed guideway STOP_IDs that should be included in the station file. Several rules to bear in mind are:
1. Many agencies use separate stop_ids for each platform at a station. The use of multiple (up to 4) fields in the station file allows STOPS to combine each platform into a single station for reporting and comparison to boarding counts.
2. Only those GTFS STOP_IDs representing platforms used by fixed guideway services should be coded. Some agencies also have separate STOP_IDs for buses serving the station that may be labeled with the same station name. These STOP_IDs should not be coded on the station record. If there is any doubt about which stations should be attached to the station record, run the GTFS Test procedures.
3. If a GTFS suffix is needed (See Section 4.8.2.2), this one-character identifier should be included in the GTFS Stop IDs in character position 10. Thus, if the GTFS ID for a station is "2722" and suffix "B" is used for the GTFS file set, then the GTFS STOP_ID in the station file is identified as "2722 B" (5 blanks between the 4-character ID and the suffix).
4. If a string longer than 9 characters must be used as a STOP_ID, then a shorter alias must be used that is organized as nnnnnS# where "nnnnn" is an STOPS-generated integer ID, "S" is the suffix (may be blank), and "#" is a code used to identify alias IDs. Given the complexity of aliases, it is essential that the user run the GTFS Test steps whenever long STOP_IDs occur.
26
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
STOPSTYPE (STOPS Type) a numerical field that indicates whether this station is to be part of the current scenario. Values include: 1. 0 (or missing value): Not part of this run 2. 1: At-grade station without Park-and-Ride (PNR) access 3. 2: At-grade station with Park-and-Ride (PNR) access 4. 3: Grade-separated (1 level up or down, adds 0.5 minutes) station with no Park-andRide (PNR) access 5. 4: Grade-separated (1 level up or down, adds 0.5 minutes) station with Park-andRide (PNR) access 6. 5: Grade-separated (2 levels up/down, adds 1.0 minutes) station without Park-andRide (PNR) access 7. 6: Grade-separated (2 levels up/down, adds 1.0 minutes) station with Park-andRide (PNR) access 8. 7: Grade-separated (3 level up/down, adds 1.5 minutes) station without Park-andRide (PNR) access 9. 8: Grade-separated (3 level up /down, adds 1.5 minutes) station with Park-and-Ride (PNR) access
NEWSTATION (New Station Indicator) an integer field that is used in STOPS to distinguish between new stations (i.e., stations associated with a project) and existing stations. One of four values should be coded: 1. 0: (or missing value): Not a new (project) station 2. 1: New (project) Station7 3. 2: (Rarely used) Not a new project station but used for cases where a project bridges a gap between two sets of existing stations but has no stations itself. A "2" is coded for one side of that gap. 4. 3: (Rarely used) Similar to "2" but represents the other side of the gap. If a trip goes from 2 to 3 then it would be considered a trip on the project even if it doesn't board or alight at a new station. 5. 4: Used to indicate a station that should be reported in the station-to-station matrices but is not part of the project. (In general, stations that are not part of the project are not tallied in the station-to-station matrices that are prepared by STOPS).
7 Prior versions of STOPS used NewStation types 3 and 4 for any case where a project bridges a gap between two existing transit services. With STOPS v1.50, the coding is only necessary if there is no new station on the gap-filling segment.
In cases where a new station does not exist on the project, it is usually easiest to code a dummy station in the station database with a new, unique stop_id. Next, add that new stop_id in the GTFS database (stop.txt and stop_times.txt files) for all routes that use the project. To prevent passengers from boarding or alighting at this stop, use the GTFS pickup_type and drop_off_type fields set to 1 for these stops.
STOPS will still accept NewStation types 3-4 to define gap-bridging projects for cases in which this form of project identification is easier.
27
Federal Transit Administration STOPS v1.50 Users Guide
WALK_PEN (Optional additional walk access penalty) a floating point field that contains the additional (penalty) time (in minutes) required to use the station above and beyond the time required by either the horizontal separation (i.e., latitude and longitude differences) and vertical separation (i.e., differences implied by the grade separation parameter). This value can be used to represent both actual walking times and other contributors to impedance such as fare or service perceptions. This parameter is added to all centroid-tostop walk access connectors.
KNR_PEN (Optional additional kiss-and-ride access penalty) Similar to WALK_PEN, this parameter contains the number of minutes to be added to all centroid-to-stop kiss-and-ride access connectors.
PNR_PEN (Optional additional kiss-and-ride access penalty) Similar to WALK_PEN, this parameter contains the number of minutes to be added to all centroid-to-stop kiss-and-ride park-and-ride access connectors.
SAMEGTFX (Optional additional stop-to-stop transfer penalty for stops appearing in the same GTFS directory) Similar to WALK_PEN, this parameter contains the number of minutes to be added to all centroid-to-stop kiss-and-ride park-and-ride access connectors.
DIFFGTFX (Optional additional stop-to-stop transfer penalty for stops appearing in different GTFS directories) Similar to WALK_PEN, this parameter contains the number of minutes to be added to all centroid-to-stop kiss-and-ride park-and-ride access connectors.
The station file may also have additional fields for user notes. These fields but are not used by STOPS and have no effect on forecast outcomes.
4.2.1 Creating the Station Data File
To create or edit the station file, click on "2. Specify Station Locations" in the STOPS Main Menu. When this is done, STOPS will create a new station data file if this is the first time this function is selected and then open a GIS window displaying the station data file (shown in Figure 13). Use the GIS system to:
1. Select active systems by setting the STOPSType field
2. Add or move stations by using the GIS capabilities to click on a map location to create a point or drag an existing point to a new location
3. Edit each of the data fields for each active station to accurately reflect:
Station sequence Station name Station code Station group Group name At least one (but up to four) GTFS ID(s) New Station status
28
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
A tabular view of the data appears in Figure 14. It is likely that the user will not know all of this data at the beginning of the STOPS process. STOPS allows the user to return to this screen during the course of the STOPS set-up process to add information as it becomes available. This is particularly helpful for entering GTFS IDs which may not be fully known before the GTFS files are created. However, it is important that the user know what states and what geography type will be used at the very beginning of the STOPS process. Care should be taken to make sure that all or nearly all8 existing, no-build, and build stations are identified the first time this step is run.
8 It is possible to add stations later so long as it does not affect the assessment of which states comprise the corridor and what geographic analysis type is appropriate for the corridor.
29
Federal Transit Administration STOPS v1.50 Users Guide
Figure 13. Station Map View (with user-added state/county boundaries)
30
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 14. Station Definition in TransCAD If you are using TransCAD to edit stations, then STOPS created an editable TransCAD geographic database from the ESRI shape file that is used as the input to STOPS. After the user closes TransCAD, then STOPS asks if it is OK to copy this file back to the ESRI shape file format. Click "Yes" to copy this data back to ESRI Shape File format or "No" to skip this step and lose the changes entered into TransCAD. This dialogue is shown in Figure 15.
Figure 15. TransCAD Confirmation After Station Editing
31
Federal Transit Administration STOPS v1.50 Users Guide
4.3 Define STOPS Parameters (Part 1 - Run Names and Geography)
After the stations have been located, it is possible for the user to do a geographic analysis to determine what states are present within a 25 mile radius of existing and future stations (the "corridor") and whether the corridor lies entirely within a metropolitan area in which TZ or BG geography types are available. These analyses are typical GIS activities and are assumed to be performed by an analyst outside of STOPS9.
With this understanding, the user can begin to define the STOPS parameter file.
To begin this process, click on "3. Edit Parameter File". When this is done, the screen shown in Figure 16 appears.
Figure 16. STOPS Parameter Screen
Begin by filling in the Run Name and System Name. These fields appear in the STOPS output reports. The run name defines the project represented with this STOPS run and the system name is used to record the scope of the transit systems included in the analysis. At this point, the user should also select the geography type, states and MPO code from the drop down lists.
9 The analysis could be performed selecting "2. Specify Station Locations" to open the station file and then creating a 25-mile buffer and adding state and county layers to determine states and other characteristics.
32
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
When this is accomplished, the screen should look like the example shown in Figure 17. If GTFS and parameter information are known at this time, that data can be entered. However, a later step will update the parameter file if this information is not yet known. Click Save and Exit to save the coded parameters and exit the data entry screen. The parameter file may still be shown as "File Not Found" at this point. STOPS checks to make sure that GTFS information has been defined for the run and if no information has been provided, then STOPS does not consider this file to be complete. For the moment, the GTFS file definitions are not necessary and this warning can be ignored. GTFS information will be entered into the parameter file during a later step, at which time the status will change to "FILES FOUND!".
Figure 17. STOPS Parameter Screen With Geography Type, State, and MPO Codes
33
Federal Transit Administration STOPS v1.50 Users Guide
4.4 List and Check TAZ and CTPP Files
After the Geography Type, States, and MPO Codes are entered, STOPS can generate a list of required files and the directories where this data should be stored. This is accomplished by clicking on "4. List and Check TAZ and CTPP Files". When that is done, the screen shown in Figure 18 appears.
After each file is a label indicating whether or not the file was found in the required directory. When all files are found, this step is marked as "FILES FOUND!" in the main menu.
Figure 18. Screen Showing Location of CTPP and MPO TAZ Files
4.5 Obtaining Census and CTPP Data
The Year 2000 Census and CTPP provide five types of input data to STOPS:
1. One geographic information system (GIS) file in ESRI Shape (.shp) file format for each state in the corridor being modeled that describes the boundaries of the census geography used in the remaining CTPP files.
2. One CTPP Part I file (workers by residence location) for each state in the corridor being modeled.
3. One CTPP Part II file (workers by employment location) for each state in the corridor being modeled.
4. One or more CTPP Part III (Journey-to-Work flows) file (one file for corridors where local zones or Block Group data are available; otherwise one file per state in the corridor).
5. One Census Block boundary file in ESRI shape file format for each state in the corridor being modeled.
34
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
The required CTPP data is available from the FTA STOPS website. These data were obtained from the Census Bureau (geographic boundary files) and the Bureau of Transportation Statistics (CTPP Parts I, II, and III).
4.5.1 CTPP and Census File Names
STOPS generally uses the same CTPP file names and file structures as originally assigned by the Census Bureau and BTS. The only exception occurs with the block file names which are assigned a shorter name on the FTA STOPS website. In cases where corridors span multiple states, separate CTPP and Census Files (one for each state) are downloaded from the FTA STOPS website.
File names are related to the corridor state FIPS10 codes and the MPO codes11 as shown below. In these file names, "XX" refers to the first state's FIPS code. In multi-state corridors, "YY" refers to the second state's FIPS code and "ZZ" refers to the third state's FIPS code. Four digit MPO codes are represented with "9999". Different files use the numeric and alpha codes as indicated below
CTPP Boundary Files (all files stored in the inputs\ subdirectory) Numeric FIPS o All projects: tzXX_d00_shp.zip (projects with a TZ geography type) bgXX_d00_shp.zip (projects with a BG geography type) trXX_d00_shp.zip (projects with a TR geography type) o Additionally, for corridors with 2 or more states: tzYY_d00_shp.zip (projects with a TZ geography type) bgYY_d00_shp.zip (projects with a BG geography type) trXX_YY_d00_shp.zip (projects with a TR geography type) o Additionally, for corridors with 3 or more states: tzZZ_d00_shp.zip (projects with a TZ geography type) bgZZ_d00_shp.zip (projects with a BG geography type) trZZ_d00_shp.zip projects with a TR geography type)
CTPP JTW Part I file(s) (all files stored in the inputs\ subdirectory) Alpha FIPS o XX_ctpp1_t030_t046.dat o YY_ctpp1_t030_t046.dat (additionally, for corridors with 2 or more states) o ZZ_ctpp1_t030_t046.dat (additionally, for corridors with 3 states)
CTPP JTW Part II file(s) (all files stored in the inputs\ subdirectory) Alpha FIPS o XX_ctpp2_t001_t017.dat o YY_ctpp2_t001_t017.dat (additionally, for corridors with 2 or more states) o ZZ_ctpp2_t001_t017.dat (additionally, for corridors with 3 states)
CTPP JTW Part III file(s) (all files stored in the inputs\ subdirectory) Alpha FIPS o If the project uses TZ or BG geography types: MPO9999_ctpp3_sumlv944.dat o If the project will use Tracts (TR): XX_ctpp3_sumlv140.dat YY_ctpp3_sumlv140.dat (additionally, for corridors with 2 or more states) ZZ_ctpp3_sumlv140.dat (additionally, for corridors with 3 states)
10 FIPS (The Federal Information Processing Standard) defines a two-digit numeric and 2-character alpha code identifying each state and is presented in Section 9.1. 11 MPO Codes are defined by the Census Bureau and are presented in Section 9.2.
35
Federal Transit Administration STOPS v1.50 Users Guide
Census Block Files Alpha FIPS o CensusBlocks_XX.shp o CensusBlocks_YY.shp (additionally, for corridors with 2 or more states) o CensusBlocks_ZZ.shp (additionally, for corridors with 3 states)
4.5.2 Downloading CTPP and Census Geographic Boundary File Data
The FTA STOPS website has a link that allows users to download a compressed (zip) file that contains all of the CTPP and Census data need to run STOPS. Project corridors located in a single state need just one state file and project corridors that span multiple states will need the zip files for each state.
After downloading the appropriate state zip files, the user must extract the files identified on the screen shown in Figure 18. These files are all stored in the inputs\ subdirectory.
Hint: The State level block files are often quite large and include block data for the entire state. STOPS processing speeds may be improved by updating the Block shape file to delete blocks that are located beyond the boundaries of the metropolitan area. This editing is optional and users should take care to delete only those blocks that are well beyond the limits of the metropolitan area. If there is any doubt whether a block is or is not part of a metropolitan area, then the blocks should be left in the data set. This edit is only recommended for the very largest states such as California and Texas.
4.5.3 Splitting CTPP Geography
In some cases, the CTPP geography will be too coarse to support detailed analysis of transit ridership potential. To improve (to some degree) the geographic precision of the model, STOPS allows users to split Census Geography. This is done by using a GIS package to edit the census boundary files in ESRI shape file format. A Census TAZ, block group or tract that is too big, can be split into one or more smaller subdivisions. The user must take care to ensure that the original FIPS state , county, and TAZ (or tract or block group) designations appear in each split zone. That way, STOPS knows to associate CTPP Journey-to-Work records with each of the split zones. The user is responsible for assigning a new and unique zone identifier (up to 6 characters) for each split zone and coding this identifier in the LSAD_TRANS field. If STOPS detects multiple records in the Census geography shape file that are not renamed with a unique zone identifier in LSAD_TRANS, then STOPS will display an error message and direct the user to a report that identifies the duplicate entries. In some cases, the original Census files have duplicate zone TAZs that also must be given an alternative identifier in LSAD_TRANS.
During processing, STOPS will detect census zones that have been subdivided and allocate trips according to the relative population and employment (from the MPO data files) in each sub-zone.
4.5.4 Controlling the Geographic Extent of the Analysis
Special coding can also be used to control the geographic extent of the analysis. By default, STOPS processes all CTPP zones within 25 miles of a coded station. In some cases, this rule extends the STOPS analysis into nearby regions that are not served by the modeled transit agency. To limit STOPS to a specific service area for the modeled transit agencies, STOPS allows users to enter special codes in the LSAD field of the Census geographic files. These codes are defined as follows:
36
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
<blank>: The default value which tells STOPS to include the zone and trips as long as the zone centroid is within 25 miles of an active station.
YY: Include this zone in the STOPS analysis area only process CTPP Journey-to-Work trips that travel to/or from a zone coded with a blank in LSAD. If both ends have "YY" in LSAD, then do not process any CTPP trips for this zone-to-zone interchange12.
XX : Exclude this zone from the STOPS analysis
4.6 Metropolitan Planning Organization Data
STOPS uses data from the local Metropolitan Planning Organization (MPO) to represent: Current and projected future-year population and employment to "grow" the 2000 CTPP JTW tables to represent current and future conditions Zone to zone automobile travel times and distances
Because current MPO zones may or may not align with the Census geographic definitions, the MPO information must be conveyed in a form that allows STOPS to convert MPO zone data to the same geographic area system used by STOPS. This is accomplished by creating an MPO zone layer in ESRI Shape File format that contains information on the model zone number and existing and future population. The remainder of this section describes the two key datasets that must be obtained from the MPO forecasting process.
4.6.1 MPO Data Filenames
The following filenames are required with STOPS. All files must reside in the "inputs\" subdirectory. MPO zone layer with existing and forecasting population and employment named
"MPO9999TAZPopEmp.shp", where 9999 is the Census MPO designation. MPO Auto Time Matrix named "STOPS_PATH_Auto_skim.csv"
4.6.2 MPO Zone Layer with Existing and Forecasted Population and Employment
The MPO zone layer conveys information on the boundaries of each zone in the regional travel forecasting model, the numeric zone number used in that model, and existing and forecasted population and employment.
12 This capability is most useful when modeling a suburban carrier that serves a local market in the suburbs and also carries commuters into the central city. The suburban zones would have a blank in LSAD and the central city zones would be coded with "YY" in LSAD. This tells STOPS to estimate transit trips for suburbsuburb, suburb-city, and city-suburb trips but not city-city. GTFS should be provided for both the suburban carrier and for urban transit system since suburban commuters may transfer to the urban system to reach their final destination. The number of coded unlinked trips for calibration would be set to the ridership on the suburban carrier plus an allowance for the estimated number of boardings that suburban customers will make when transferring to the urban transit system.
37
Federal Transit Administration STOPS v1.50 Users Guide
This file should be constructed using a GIS package (e.g., TransCAD or ArcMap) and saved as an ESRI shape file. Coordinates should be expressed as degrees of longitude and latitude. It should include the fields described below. Other fields may exist in this file (and will be ignored) although some field names ("District") are not allowed.
Required geographic information o Boundary of each zone in the MPO modeling system.
Coordinate system o Decimal degrees of longitude and latitude
Required data fields o Model TAZ zone number (integer). Any user-selected name. o Year 2000 Population (numeric). Any user-selected name.13 o Year 2000 Employment (numeric). Any user-selected name. o Current Year Population (numeric). Any user-selected name. o Current Year Employment (numeric). Any user-selected name.
Optional data fields14 o Opening Year Population (numeric). Any user-selected name. o Opening Year Employment (numeric). Any user-selected name. o 10-Year Horizon Population (numeric). Any user-selected name. o 10-Year Horizon Employment (numeric). Any user-selected name. o 20-Year Horizon Population (numeric). Any user-selected name. o 20-Year Horizon Employment (numeric). Any user-selected name.
In some cases, MPOs will provide a TAZ layer in a coordinate system other than longitude and latitude. This can be easily checked in either TransCAD or Arc Map by opening the shape file and observing whether or not coordinates are reported in degrees of longitude and latitude. Figure 19 and Figure 20 show the file coordinate system identification in TransCAD and Arc Map, respectively.
13 In some cases, MPO data may not be available for the Year 2000 or the current year. In general, FTA will accept data representing a point in time one or two years away from these dates if the corridor is not changing dramatically and if the alternate years would result in similar growth factors as would have been produced by Year 2000 and the current year data. Otherwise, users are advised to speak with their FTA project coordinator to determine the best approach for proceeding with the analysis. 14 If these optional fields are not present, STOPS can still be used but the forecast years will be limited to the cases where data fields are available.
38
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 19. TransCAD Shape File Opening Dialog with Longitude/Latitude (Left) and NonLongitude/Latitude Coordinates (Right)
39
Federal Transit Administration STOPS v1.50 Users Guide
Figure 20. Arc Map Screen with Longitude/Latitude Coordinates (Top) and NonLongitude/Latitude Coordinates (Bottom)
40
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
If the coordinates are in not longitude/latitude format, the user must convert this file to longitude and latitude coordinates consistent with the coding of shape files from the Census Bureau. This conversion can be accomplished in both TransCAD, Arc Map and many other packages. In TransCAD, this can be done by using the Tools>Export command. Select the ESRI shape file format and specify the desired file name. TransCAD exports default to Longitude/Latitude coordinates so no other action is required. In Arc Map, use the Arc Toolbox button on the menu bar, and open Data Management Tools>Projections and Transformations>Feature and then double click on "Project" (see Figure 21). This will open a dialog that allows the user to specify the output coordinates as shown in Figure 22.
Figure 21. Select the Projections and Transformations Project Tool
41
Federal Transit Administration STOPS v1.50 Users Guide
Figure 22. Arc Map Dialog to Convert Coordinates to Longitude/Latitude
In both TransCAD and Arc Map, the user must export the shape file to name that is different from the original file. Accordingly, it may be necessary to rename the file to the desired file name after the export is complete. When renaming shape files, be sure to re-name all of the components of the file (i.e., all extensions).
The user should reopen the revised file to confirm that the MPO shape file has been successfully converted to longitude/latitude coordinates.
4.6.3 MPO Auto Time Matrix
The MPO Auto Time Matrix is obtained by extracting zone-to-zone current year peak period automobile travel times from the regional travel demand forecasting model. The file that is used by STOPS is organized as a text file in comma-separated format with one line for each origindestination zone pair containing:
Integer origin zone number from the travel model Integer destination zone number Real automobile distance for the current year (in miles) Real automobile time for the current year (in minutes) Real automobile distance for the opening year (in miles) Real automobile time for the opening year (in minutes) Real automobile distance for the mid-range forecast year (10 year forecast) (in miles) Real automobile time for the mid-range forecast year (10 year forecast) (in minutes)
42
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Real automobile distance for the long-range forecast year (20 year forecast) (in miles) Real automobile time for the long-range forecast year (20 year forecast) (in minutes) If highway travel time data for the opening or forecast years are not available, then these fields may be left empty. Any times or distances that are left blank or set to zero are given the same time or distance values that were entered for the current year. A portion of a sample auto time matrix file appears in Figure 23.
Figure 23. Sample MPO Auto Time Matrix File
43
Federal Transit Administration STOPS v1.50 Users Guide
4.7 Check File Status
After the TAZ and CTPP files have been obtained and loaded into the proper subdirectory, the STOPS Main Menu should appear as shown in Figure 24. The label "FILES FOUND!" should appear next to Steps 2 and 4. If not, click on the "Update File Status" button. If Steps 2 or 4 are still not found, click on "4. List and Check TAZ and CTPP Files" to see which files do not exist in the proper subdirectory. As needed, obtain the proper files and click "Update File Status" until Steps 2 and 4 are listed as "FILES FOUND!".
Figure 24. STOPS Main Menu After All TAZ and CTPP Files Are Loaded
4.8 Transit Agency Schedule and Supplemental Data
The General Transit Feed Specification (GTFS) is used to represent existing and scenario-specific transit services. STOPS also uses several extensions to this specification to represent opportunities for park-and-ride (PNR) access and for users to code an editlist file that can be used to make relatively simple changes to represent different scenarios (e.g., the introduction of a new rail line or rerouting buses to serve as feeder routes).
44
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
4.8.1 Overview of GTFS File Formats
Full documentation of GTFS is provided at https://developers.google.com/transit/gtfs/reference. This section provides an overview of the specification and indicates which GTFS components are used by STOPS to represent transit levels of service.
GTFS consists of a series of files that, together, represent the stops, routes, and scheduled operation of a transit system. In some areas, all transit services are provided by a single operator and in such cases a single set of GTFS files represent all or nearly all fixed route services in a region. In other areas, multiple operators provide service and GTFS files may be available separately for each operator or may be combined into a single master GTFS dataset. It is important for the user to know exactly which services are covered in each file so that STOPS has an accurate representation of transit services in the project corridor. Section 4.8.3 describes a publicly-available visualization tool that can help the user to understand the services coded in a GTFS file.
STOPS only uses a sub-set of the GTFS file structure as is briefly described, below. The full documentation (referenced above) provides a more comprehensive description of the full capabilities of GTFS. STOPS processes GTFS data using a program called GTFPath. This program reads GTFS data and a set of zone centroids and creates a matrix of zone-to-zone transit times that is similar in concept to transit skim files generated by conventional travel forecasting models.
GTFS uses a fully relational data model that depends on a series of ID fields to store key aspects of the schedule. These ID fields include:
Service_id uniquely identifies a set of dates when service is available for one or more routes. A GTFS file can include routes that operate on Saturdays, Sundays, weekdays or any combination. GTFS files can also include different schedule "picks" so one file might include bus schedules for the spring, summer, and fall. The service_id is used to select just that portion of the schedule that operates on a given day. The "calendar.txt" file defines the beginning and ending dates and days of the week that apply to each service_id.
Stop_id uniquely identifies a stop or station. Multiple routes may use the same stop. Many agencies separately code stops on each side of the street or each platform on a rail line. Stop_IDs are defined in the "stops.txt" file.
Route_id uniquely identifies the route and is defined in the file "routes.txt." A route is a collection of [bus or rail] "trips" that generally follow the same alignment. All "trips" identified as a single "route" must share the same name, description, and type (e.g., bus, rail, light rail, etc.). Different trips within a route may serve a different series of stops allowing one route to include short-turn trips, route deviations and branches. The route information includes one data item of critical importance to STOPS--the route_type. A Route_type of "3" indicates "bus". All other route_types are considered by STOPS to be a fixed guideway option and thus can be used to estimate trips-on-project on a station-by-station basis. Users should carefully consider the most appropriate way to code a BRT project. BRT lines that are operating in a fully grade separated right-of-way may be perceived as being fixed guideway and probably should be coded as as route_type=0 (streetcar or tram). BRT routes that represent enhancements to bus service but operate in mixed traffic may be perceived as a more convenient bus route and should probably be coded as route_type=3.
Trip_id uniquely identifies a [bus or rail] trip. A trip is equivalent to each row [or column] in a typical time table and represents the departure of one bus or train from the originating
45
Federal Transit Administration STOPS v1.50 Users Guide
or turnback point of the route through to that vehicle's arrival at the destination terminal for the route (or turnback point).
In STOPS and GTFPath, service_id is a string variable that can be up to 100 characters wide. The other ID fields (stop_id, route_id, and trip_id) are also character strings of up to 100 characters wide for processing with STOPS and GTFPath. However, STOPS and GTFPath are much faster if the string length for these latter fields is limited to 9 characters. In some cities, the ID fields are much longer than 9 characters but most of these characters duplicate the service ID or another non-relevant character string. STOPS includes the capability to define a subset of the ID character string that can uniquely identify an ID within the 9 character limit.
Figure 25 presents a portion of the trip file from a GTFS file that represents service operated in 2010. The highlighted section of the file shows the trip_ids. Characters 1 to 8 represent the unique part of the trip_id and the remaining characters duplicate the service_id and are not needed to uniquely identify each trip.
Figure 25. Sample trip file with Long Trip IDs
In this example, the user could significantly increase the processing speed by limiting the trip_id field to characters 1 to 8. Similar character ranges can also be defined for route_ids and stop_ids if that helps to identify a short, yet unique string within each ID field.
46
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 25 also illustrates another GTFS concept. GTFS files are structured as comma separated text files (with a .txt extension) that can include data in any order on a record. The contents of each file are defined in a header record. STOPS and GTFPath reads the header record and uses this information to determine where in each record the relevant data is found. GTFS files to be read by STOPS and GTFPath can process the required data in any order as long as it is properly identified in the header record. Extra fields can be included in the file and STOPS will ignore this extra information. STOPS and GTFPath use the following GTFS files to prepare the level-of-service matrices:
Calendar.txt (Required unless the calendar_dates file is provided): This file contains a listing of valid dates and days-of-week for each "Service_ID." Calendar.txt is a comma separated file with a header displaying the structure of the file followed by one record for each service_id. Each record includes: o Service_ID: a character ID that uniquely identifies a set of dates that appears at most once in the calendar file. o Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday: A series of binary fields that if set to 1 indicates that the service is operated that day. A 0 (zero) is used to indicate that this service is not operated. o Start_date and end_date. The starting and ending dates for the service in YYYYMMDD format.
A simple calendar file is shown in Figure 26.
Figure 26. Sample GTFS Calendar File
47
Federal Transit Administration STOPS v1.50 Users Guide
Calendar_dates.txt (Optional unless the calendar.txt file is not provided then calendar_dates is required): This file contains a listing of dates and exceptions to the schedule previously defined in the calendar.txt file. If the calendar.txt file is not provided, then each day of operation is an exception to the schedule and all dates and service_IDs must be coded. Calendar_dates.txt is a comma separated file with a header displaying the structure of the file followed by one record for each combination of day and service_ID for which an exception record is required. Each record includes: o Service_ID: a character ID that is coded on the route record to indicate the type of service operated (e.g., weekday, Sunday, holidays). o Date. The day that this exception applies to o Exception_type. Equals 1 if the service_ID is to be operated on that day. Equals 2 if the service_ID is not to be operated on that day. If multiple records are coded with the same service_ID, then the last record is used in processing.
Stops.txt (required): This file contains a list of stop_ids, stop locations, and names to define stops and stations where passengers can board and alight from transit. The file has a header record followed by one record for each station or stop in the system. The following fields are required: o Stop_id: a unique 100-character identifier that identifies the stop or station. As noted above, STOPS is much faster if the stop_id is limited to 9 (or fewer) characters or if a character range can be specified that identifies a unique 9 (or fewer) character substring that leads to a unique stop_id. o Stop_name. A character string that names the stop. o Stop_lat. A real number containing the latitude of the stop. o Stop_lon. A real number containing the longitude of the stop.
A sample stop file is shown in Figure 27.
48
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 27. Sample GTFS Stop file Routes.txt (required): This file contains a list of route_ids, route descriptions and route
types (transit modes). The file has a header record followed by one record for each route in the system. The route_id must appear at most once in the routes.txt file and is used to identify the name of the route as it appears in schedules and on transit vehicles. Most [bus or transit] trips generally follow the same basic alignment but trips within routes may offer turnbacks, route deviations, and branches. Of critical importance to STOPS, all trips on a route have the same route_type allowing STOPS to distinguish between fixed guideway and bus routes. That means that bus routes that are considered to be fixed guideway routes (e.g., BRT routes on exclusive rights-of-way) should be coded as type 0 (tram or streetcar). Routes.txt has the following fields:
o Route_id. A unique id used to identify the route. o Route_short_name. A short description such as the route number which describes
the route but not the destination. o Route_long_name. The full name of the route. o Route_type: A one-digit integer that best describes the type of transit. The value of 3
is used to denote non-fixed guideway bus routes. All other types are considered to be fixed guideway services. Projects can be comprised of any route type15. The full list of potential route-types are: 15 The stops that comprise a project are identified in the station file. It is necessary to identify all bus stop_ids must be associated with a "station" in the station file that has a NewStation Code of "1".
49
Federal Transit Administration STOPS v1.50 Users Guide
0 - Tram, streetcar, LRT, (and BRT for STOPS) 1 Subway, Metro 2 Rail (intercity and long-distance 3 Bus (short- and long-distance but not BRT in STOPS) 4 Ferry 5 Cable car 6 Gondola or suspended cable car 7 Funicular
A sample route file appears in Figure 28.
Figure 28. Sample GTFS Route File
Trips.txt (required): This file contains a header record followed by one record for each [bus or rail] trip. A trip in this context refers to a transit vehicle [bus or rail] trip that occurs when a bus or train departs from the route beginning point (or a turnback point) and lasts until it arrives at the destination terminal or turnback. Required fields are as follows:
o Trip_id. A unique ID identifying the trip. o Route_id. The ID of the route that describes this trip. o Service_id. The ID that describes the days this trip operates in the calendar.txt file.
50
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Version 1.50 Highlight: GTFS trip files can also include an optional block_id field. This field is used to indicate groups of trips that are served by the same vehicle. Starting with Version 1.50, passengers are allowed to remain on the bus between trips when the same block_id is used for each trip. This is particularly important in systems that interline routes. For example, route "A" on the north side of town may continue as route "B" on the south side. In this case, as long as two trips have the same block_id, through passengers have a no-transfer trip even though the route and trip have changed during the course of the journey.
A sample trip file is shown in Figure 29.
Figure 29. Sample GTFS Trip File Stop_times.txt (required): This file contains one record for each stop served by each trip
and defines the times that the trip serves that stop. This file corresponds to each time value in a printed schedule. The key difference between the stop_time.txt file and printed schedules is that each stop on the route has a time record in the stop_time file16 as
16 In cases where the time is not known (i.e., the stop is not a time point and the agency does not estimate times for non-time points), then times may be left blank. In this case, STOPS interpolates the time based on the preceding and following time points and the relative straight line distance between stops. Note that 0:00:00 is considered to be midnight at the beginning of the schedule day. It is not the same as a blank value which is treated as a non-time point to be interpolated.
51
Federal Transit Administration STOPS v1.50 Users Guide
compared to most printed time tables in which time values are present for selected stops only (known as time points). The following fields are required:
o Trip_id. The ID of the trip represented by this record. o Stop_id. The ID of the stop represented by this record. o Arrival_time. The time that the trip arrives at the stop. This value is left blank if the
time is not known and the time is to be interpolated based on preceding and following time points. o Departure_time. The time that the trip departs from the stop.17 This value is left blank if the time is not known and the time is to be interpolated based on preceding and following time points. o Stop_sequence. A sequential number that indicates whether this record is the first, second, third, etc. stop that this trip makes.
Optionally, the stop_times file may include two other fields:
o Pickup_type. A "1" denotes that passengers may not board the vehicle at this stop18 o Drop_off_type. A "1" denotes that passengers may not alight the vehicle at this stop
A sample stop_time file appears in Figure 30.
Figure 30. Sample GTFS Stop_Time File
17 In most cases arrival and departure times are the same. They are different when the bus or train is scheduled to wait at the stop for more time than is necessary to receive and discharge passengers. 18 GTFS uses codes "0" (the default) to indicate that passengers may board and alight at the stop. Codes"2" and "3" to identify stops that may be used by special arrangement with the driver or agency. STOPS treats codes 0, 2, or 3 as indicating that the pickup or drop-off can occur.
52
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Frequencies.txt (optional): This is an optional file that, if present, provides a start- and end- time interval during which a trip from the trips.txt file is repeated according to the headway specified in the frequencies file. When trips are defined in frequencies.txt, STOPS and GTFPath ignore the absolute values of the arrival_time and departure_time fields for those trips in stop_times.txt. Instead, the stop_times table defines the sequence of stops and the time difference between each stop. The exact times are generated from information in the frequencies file. The frequencies file includes the following fields: o Trip_id. The ID of the trip to be repeated. o Start_time. The first departure time from the first stop on the trip. o End_time. The latest departure time from the first stop on the trip. o Headway_secs. The headway in seconds between successive departures. A sample frequencies file appears in Figure 31.
Figure 31. Sample GTFS Frequencies File Transfers.txt (optional).: The transfers.txt file contains information on the amount of time
required to complete a transfer. If this file is not provided or if a transfer is not coded in this file, then STOPS automatically generates transfers between stops located within 0.25 miles of each other and computes the transfer time based on the straight line distance between the two stops traversed at a speed of 3 miles per hour. Any station grade separation time (0.5 minutes per level) and any transfer penalty time coded in the station file are added19 to this time estimate. The GTFS station file provides the opportunity to override this estimate in cases where time is materially different. This file has the following fields
19 Grade separation and penalty times for both the "from" station and the "to" station are added to the computed transfer time.
53
Federal Transit Administration STOPS v1.50 Users Guide
o From_stop_id. The stop_id used to define the stop where the transfer begins o To_stop_id. The stop_id used to define the stop where the transfer ends o Transfer_type. A code defined as follows
0 recommended transfer point (ignored by STOPS) 1 timed transfer point where the to bus will wait for passengers (ignored
by STOPS) 2 requires a time specified in min_transfer_time to make the connection 3 transfers not allowed at this location o Min_transfer_time. (Optional) The number of seconds required to complete this transfer for transfer_type = 2. If this field is not available, the min_transfer_time is assumed to be zero. PNR.txt (optional STOPS extension to GTFS standard): The PNR file is a STOPSextension to the GTFS standard and allows the user to specify locations where travelers can park their cars prior to making a transit trip. One record is specified for each potential parking location which is defined in terms of latitude and longitude. STOPS and GTFPath compare this location to stops identified in the stops.txt file and all stops within 0.25 miles are connected to the PNR lot. The PNR.txt file has the following required fields. o Pnrname A character string with the PNR lot name. o Latitude. A real number with the latitude in degrees. o Longitude. A real number with the longitude in degrees. o Pnrtype. An integer that is used to define the scale of the PNR and its likely catchment area. In STOPS, these values are defined as follows: 1 End-of-line fixed guideway station attracts trips up to 25 miles away.
Also used when a major highway intersects the fixed guideway facility and the station effectively serves as an end-of-line station for these travelers. 2- Formal fixed guideway or bus PNR lot-attracts trips up to 10 miles away. 3 Officially designated PNR lot in a shared facility attracts trips up to 6 miles away. This designation is applied to lots in churches, shopping centers and similar settings with posted signage permitting transit PNR. 4 Unsanctioned PNR lots. Lots where parking for transit occurs but is not identified by the transit operator as a sanctioned PNR lot. This could include cases where private land owners make their property available for a fee and other cases where parking occurs without permission. Because this usage is dependent on driver knowledge of the local situation, this type of parking is limited to access distances of less than 3 miles.
Version 1.50 Highlight:
The pnr.txt file also has an optional field, call "PNRCost" that, if present, contains the amount of additional impedance (in equivalent minutes of travel time) that should be added to the connection between the parking lot and nearby transit stops. PNRCost can be used to represent additional time required for vertical circulation in a parking structure or to represent a shadow price for purposes of constraining modeled parking utilization to parking capacity.
A sample PNR file is presented in Figure 32 showing examples with and without the PNRCost field.
54
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Case 1. Without optional PNRCost Field
Case 2. With Optional PNRCost Field Figure 32. Sample GTFS PNR File.
4.8.2 Managing GTFS Files and Creating Project Scenarios in STOPS
The GTFS file format provides a flexible structure for defining an individual transit operating agency's schedule of service. This is an important foundation for generating estimates of trips on a project but is only the beginning. STOPS must read multiple sets of GTFS files to represent:
Corridors where transit service is provided by multiple agencies and schedule data is coded into multiple GTFS file sets.
Multiple scenarios representing existing service, future year no-build and project-related service.
This section introduces several of the concepts that make it possible to read multiple GTFS files to cover both circumstances.
55
Federal Transit Administration STOPS v1.50 Users Guide
4.8.2.1 Separate Sub-Directories for Representing Multiple GTFS Files
In GTFS, simple file names such as calendar.txt, trips.txt, and stops.txt are used to define a set of schedules for one agency. With this structure, GTFS file sets for multiple agencies or different scenarios must be stored in different sub-directories.
This requirement is satisfied in STOPS through the concept of a "Subdirectory Prefix" ("Directory" or "Dir"). The Subdirectory Prefix is a character string that is added to the beginning of each GTFS file name to differentiate subdirectory locations. This capability can be used to do the following:
Identify a set of subdirectories where each transit operator's files may reside. In San Diego, two GTFS files are used (Metropolitan Transit System and North County Transit District). In this case, two subdirectories might be used to represent existing schedules: o MTS2013\ o NCTD2013\20
Identify different scenarios. Continuing the San Diego example, assume that NCTD is constructing a project and that both MTS and NCTD have future year no-build scenarios. In that case, the following subdirectories might also be defined o MTSNoBuild\ o NCTDNoBuild\ o NCTDBuild\
These names are sub-directories of the inputs\ folder which is a subdirectory of the project folder where the control file is located. If the project control file is d:\STOPS\SD\sandiego.ctl, then the GTFS folders described above would be:
D:\STOPS\SD\Inputs\MTS2013\ D:\STOPS\SD\Inputs\NCTD2013\ D:\STOPS\SD\Inputs\MTSNoBuild\ D:\STOPS\SD\Inputs\NCTDNoBuild\ D:\STOPS\SD\Inputs\MTSBuild\
The combination of root directory name and the sum of all of the GTFS subdirectory names may have as many as 200 characters. Much shorter name lengths are recommended for readability of reports and screens.
4.8.2.2 Simultaneous Processing of Multiple GTFS Files
As discussed in the previous section, transit service in some metropolitan areas is provided by multiple agencies and, in some cases, these agencies each generate their own GTFS files. STOPS provides the capability to read multiple GTFS files and generate a single set of paths that considers routes operated by all agencies. The STOPS User Interface requires the user to code at least one non-blank subdirectory name for all scenarios (e.g., existing, no-build, and build). Up to nineteen
20 In a STOPS subdirectory prefix, a subdirectory is indicated when the prefix ends with a "\" character. If no "\" is present at the end of the subdirectory prefix, then STOPS will treat the prefix as a character string to insert at the beginning of each GTFS file name. This approach works in STOPS. However, the prefix + file name without an intervening "\" will not work with the GTFS data validation or visualization tools and are, therefore, not recommended.
56
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
additional GTFS files with non-blank subdirectory names may also be provided for each scenario to represent multiple operators.
Although a non-blank subdirectory prefix is required for each scenario, it is important to note that the same subdirectory prefix can be used for multiple scenarios. This could happen if the no-build and existing scenarios are the same or if the user wishes to test STOPS to determine "project" ridership for an existing rail line. In such cases, the user might type "MTS2013\" and "NCTD2013\" as the subdirectory prefix for the "Existing", "No-Build", and "Build" scenarios.
In many cases, this is all the user needs to do--specify all of the subdirectories that together should be read to generate a complete set of origin to destination paths for the modeling region. In some cases, however, this strategy will lead to an error caused by different agencies using the same stop, route, or trip designation to refer to different things. When this happens, the user can supply a 1character suffix in the 10th character of each stop_id, route_id, and trip_id for the user-selected GTFS file set. For instance if the user supplies "A" as a suffix then trip 121 would be renamed as "121 A" and stop "65112" would be renamed "65112 A" in all references to these fields.
The user does not need to add the suffix to any field in the GTFS file set; STOPS does that automatically. The only places where the suffix needs to be hand-coded by the user are:
1. In the parameter file where other GTFS information is identified 2. In the station file (see Section 4.2) where the user needs to add the suffix to the GTFS ID
fields.
The use of the suffix is an area where the user must know the nature of the data contained in GTFS files. In at least one city, an operator appeared to reference a stop node in another operator's GTFS. In this case the user should not specify a suffix (or specify the same suffix for both operators) so that STOPS can find the appropriate record. In another city, GTFS files contained many duplicate stop_ids21 and the suffix function is an easy way to make sure that each file properly references GTFS components supplied by the originating agency.
4.8.2.3 Using STOPS to Automatically Edit GTFS Files to Create Alternative Scenarios (Editlist.txt file)
GTFS files are highly detailed representations of a transit operator's service that are designed to allow on-line mapping software provide directions to potential transit users. In most transit agencies, these files are prepared by the scheduling department using their timetable/run-cutting software systems. The GTFS files are the final product of a complex process to prepare efficient, accurate schedules to be used by drivers, dispatchers, and the traveling public.
STOPS takes advantage of this detailed information to calibrate the model to represent current year conditions. However, STOPS must also read GTFS files representing future year conditions with and without the project. These files must be created by the user unless the scheduling department has already been engaged to develop a proposed timetable for the project.
The simplest approach (for the forecasters) to generate the future no-build and build GTFS files is to utilize the schedule writers to build a future time table using their timetable/run-cutting software systems. This approach has the advantage that the resulting schedules will be based on the experience gained by the scheduling staff over many years and may result in a schedule that is
21 Duplicate stops in this case appeared to refer to consistent points but the suffix capability eliminates the need to manually confirm that observation as being true throughout the region.
57
Federal Transit Administration STOPS v1.50 Users Guide
more accurate and more likely to be implemented. Unfortunately, scheduling staff are often focused on preparing the next round of schedules and may be unable to perform this task.
One alternative for developing a set of future year GTFS files is to use one of the software packages that provide GTFS editing capabilities. Some products with this capability may prove useful although they undoubtedly will require time to learn how to operate the software before the user can generate new GTFS files.
Another option is for the user to construct GTFS files by hand by editing the underlying text files to represent future scenarios. Since GTFS files are extremely complex with many inter-relationships, the resulting files should be carefully checked to confirm that the GTFS files are accurate representations of each scenario. This approach could be practical in cases where the schedule changes are relative simple between the existing GTFS files and the proposed future services.
The final option is to use the STOPS capability to read a file called editlist.txt (stored in the same subdirectory identified by the subdirectory prefix that contains a series of commands to adjust GTFS files. This capability is another STOPS extension to the GTFS standard.
4.8.2.4 Using Editlist
Even with the editlist function, the user is still responsible for manually editing the relatively simple files in the GTFS standard (stops.txt, routes.txt, trips.txt, and frequencies.txt). Editlist.txt is used to simplify the process of making routing changes to existing services in the stop_time.txt file. An important concept is that the stop_times.txt file contains the service that is offered to the traveling public. The other files (stops.txt, routes.txt, trips.txt, and frequencies.txt file) play a supporting role. If a route or trip exists, but there is no stop_time record, then no transit service is available for a traveler to use.
This means that if the user wishes to discontinue a route, it is sufficient to remove all of the route's stop_time records. There is no reason to eliminate the route from the route file or trips from the trip file and, depending on how these tools are used, deleting these records could cause errors. It is helpful to bear the following principle in mind:
GTFS files are extremely complex and many opportunities exist to introduce serious errors. Therefore the user should make as few changes as possible to represent potential service changes. Nearly always that means adding necessary stops, routes, trips, and stop_times but seldom, if ever, deleting anything directly from the files. Existing services are best modified or deleted using the editlist.txt capability.
The following process can be followed to create a new GTFS file to represent a new scenario.
1. Copy an existing GTFS file set to a new directory.
2. Open the calendar.txt file in a simple text editor and make a note of the service_ids that can be used to represent weekday services (often Wednesday offers the most typical representation of a weekday) on a date that is consistent with other routes represented in the GTFS file. In most cases an existing service_id can be used although it is also possible to create a new service_id.
3. Open the stops.txt file in a simple text editor and add any new bus or fixed guideway stops. In most cases, the user should not delete or move an existing stop since these physical points still exist. Even though the user may delete service in later steps, STOPS still checks
58
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
the integrity of all routes and stopping patterns and will generate an error if these stop locations do not exist. When adding new points, search the existing stop database to make sure that duplicate stop_ids are not defined. STOPS will flag a duplicate stop_id as an error.
4. Open the routes.txt file in a simple text editor and add any completely new routes to the route database taking care not to re-use any existing route_id. New routes could include a new fixed guideway line or new feeder bus routes. Do not delete any existing route_ids unless the user also deletes all references to the route in the trips.txt, stop_times.txt, and frequencies.txt files. It is not necessary to change existing routes that are truncated or modified unless the user wants to modify the route description fields to reflect the new name.
5. Open the trips.txt file in a simple text editor and add a new trip for each new route in each direction. It is only necessary to add one new trip for each new route and direction since the frequencies.txt file can be used to generate the entire schedule over the course of a day. If trips are to be added to existing routes, then the user can either code one new trip for every added trip or to create one new trip and use the frequencies.txt file to add additional runs. The user should not delete trips from the trips.txt file unless all references to the trip in the stop_times.txt and frequencies.txt files are also removed using a text editor.
6. Open the stop_times.txt file and add all stop_time entries for the new trips. Existing routes that are modified need not be edited here since the editlist.txt command can be used to change existing routes more easily. If the user does modify stop_time entries for existing routes in this file, make sure to change all of the relevant entries since each route can have one record for each trip and each stop unless the frequencies.txt file is used.
7. Open (or create) the frequencies.txt file and add frequency records for each new trip to specify the peak and off peak frequency of service. STOPS considers waiting times for two periods of the day: Peak (7:00 AM to 8:59 AM) and Off-peak (12:00 noon to 1:59 AM). Since scheduled trips serving these time periods may begin before and extend beyond these time periods, the user should create schedule information for a broader period (e.g., 6-9 AM and 11 AM- 3 PM to make sure that all trips operating in the modeled periods are properly represented.
8. Open or create the editlist.txt file. This extension to the GTFS standard allows users to update existing services using a series of editing commands that are designed to apply to multiple trips and/or routes and facilitate consistent modification to trip routing.
An example editlist.txt file is shown in Figure 33. This file represents changes made to a GTFS file with an LRT (Route 501) to make it representative of bus-only services that existed before the introduction of the LRT. As shown in this example, the file is located in the PreLRT subdirectory and is, therefore, associated with that set of GTFS files.
59
Federal Transit Administration STOPS v1.50 Users Guide
Figure 33. Sample GTFS Editlist File
The Editlist file begins with a header line that must contain the exact string of characters shown in the example. The first non-blank line following the header begins with a "!" that indicates that this line contains a comment which is skipped by STOPS when processing the editlist file.
All non-comments consist of a command followed by one or more parameters. Each command type can apply to a route, trip, stop or combination that exists in the stop_time file. The command only affects the stop_time file--the stop, route, and trip definitions contained in those files continue to exist without change even after the editlist commands are applied. The editlist commands that are applicable to STOPS are as follows:
ExcludeRoute,[route_id]. Directs STOPS to exclude all stop_time records for all trips operating with the route indicated by "route_id". This command is generally used in cases where a route no longer operates in a scenario. This might happen if a parallel route is eliminated when a new fixed guideway system is implemented. If "*" is coded as the route_id, then all routes are excluded but this wildcard should only be used if a later "include route" reinstates some of this service. Otherwise all routes are excluded and no transit paths can be built. In the sample file, route_id 501 (the LRT line) and several bus routes are removed from the schedule.
ExcludeTrip,[trip_id]. Directs STOPS to exclude all stop_time records for the trip specified by "trip_id". This command is used when a new fixed guideway service results in a loss of some trips on an existing route. If "*" is coded then all trips are excluded but this wildcard should only be used if a later "include trip" record reinstates some of this service.
60
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Re-RouteBetwnStopsonRoute,[stop_id-1],[stop_id-2],[route_id],[replacement string]. Re-RouteBetwnStopsonTrip,[stop_id-1],[stop_id-2],[trip_id],[replacement string]. These commands instruct STOPS to look for cases where a route or trip travels between stop_id-1 and stop_id-2 (with or without intermediate points) and then replaces the sequence of nodes in the original stop_time file with the nodes and travel times contained in the replacement string. This command can be used to code a short turn-back on a route or to define a new deviation off of an existing alignment. In the sample file, Route 12 between 46443 and 29260 is replaced with a new beginning that involves traveling from 45047 to 25270 in one minute and then continuing to 29260 for another 3 minutes of travel time. Re-route commands are subject to the following rules:
o Both stop_id-1 and stop_id-2 must exist in the stop_time file with stop_id-1 being before stop_id-2 in the order sequence for the trip being modified. Two re-reroute commands are required for 2-way routes to cover each direction of travel.
o The replacement string consists of a series of stop_ids representing the new sequence of stops. Between each pair of stop_ids, the user must code the transit running time required to travel between the stops.
o The replacement string must be anchored to the existing stop_id sequence at one or both ends. This means that the first stop_id in the replacement string must match stop_id-1 and/or the last stop_id in the replacement string must match stop_id-2. There are 3 kinds of replacements possible.
The first stop ID in the replacement string matches stop_id-1 and the last stop ID in the replacement string matches stop_id-2. Example 1 (new routing between existing stops):
Original Route: Rte1,stopA,stopB,stopC,stopD,stopE Re-routeBetwnStopsonRoute, stopB,stopE,Rte1,stopB,2,stopF,3,stopE Revised Route: Rte1,stopA,stopB,stopF,stopE Times. Original route up to B. Then, 2 minutes B-F, 3 minutes F-E
The first stop ID in the replacement string matches stop_id-1 and the last stop ID in the replacement string does not match stop_id-2.
Example 2 (extension to the end of the line):
Original Route: Rte1,stopA,stopB,stopC,stopD,stopE Re-routeBetwnStopsonRoute, stopD,stopE,Rte1,stopD,2,stopE,3,stopF Revised Route: Rte1,stopA,stopB,stopC,stopD,stopE,stopF Times. Original route up to D. Then, 2 minutes D-E, 3 minutes E-F
Example 3 (replacement to the end of the line):
Original Route: Rte1,stopA,stopB,stopC,stopD,stopE Re-routeBetwnStopsonRoute, stopC,stopE,Rte1,stopC,2,stopF,3,stopG Revised Route: Rte1,stopA,stopB,stopC,stopF,stopG Times. Original route up to C. Then, 2 minutes C-F, 3 minutes F-G
Example 4 (short turn back at end of line):
Original Route: Rte1,stopA,stopB,stopC,stopD,stopE Re-routeBetwnStopsonRoute, stopC,stopE,Rte1,stopC,2,stopD
61
Federal Transit Administration STOPS v1.50 Users Guide
Revised Route: Rte1,stopA,stopB,stopC,stopD Times. Original route up to C. Then, 2 minutes C-D
The first stop ID in the replacement string does not match stop_id-1 and the last stop ID in the replacement string matches stop_id-2.
Example 5 (extension to the beginning of the line):
Original Route: Rte1,stopA,stopB,stopC,stopD,stopE Re-routeBetwnStopsonRoute, stopA,stopB,Rte1,stopQ,2,stopA,3,stopB Revised Route: Rte1,stopQ,stopA,stopB,stopC,stopD,stopE Times. Original route after B. Prior to B times are computed backwards using 3 minutes A-B, 2 minutes Q-A
Example 6 (replacement to the beginning of the line):
Original Route: Rte1,stopA,stopB,stopC,stopD,stopE Re-routeBetwnStopsonRoute, stopB,stopC,Rte1,stopQ,2,stopR,3,stopC Revised Route: Rte1,stopQ,stopR,stopC,stopD,stopE Times. Original route after C. Prior to C times are computed backwards using 3 minutes R-C, 2 minutes Q-R
Example 7 (short turn at beginning of the line):
Original Route: Rte1,stopA,stopB,stopC,stopD,stopE Re-routeBetwnStopsonRoute, stopA,stopC,Rte1,stopB,2,stopC Revised Route: Rte1,stopB,stopC,stopD,stopE Times. Original route after C. Prior to C times are computed backwards using 2 minutes B-C
o Except in the case of a new beginning to the route, the arrival/departure times in the stop_time file are retained for the section of route prior to the change. Travel times following the insertion of the new stops are updated based on the stop-to-stop travel times contained in the replacement string. When a new beginning is coded, then the stop_time arrival/departure times for the existing route after the insertion point are retained and the arrival/departure times for the new beginning sequence are estimated from the stop-to-stop running times contained in the replacement string.
4.8.3 Visualizing GTFS Data
GTFS data are very complex and must be carefully checked before using this data as an input to STOPS. Review is particularly important when new files are created to represent proposed services such as a new rail line and the related bus service changes. The Google developers web site includes two tools that can be used to verify and to visualize a GTFS feed.
The following steps are required to use the feed validator and feed visualization tools:
1. Download the latest version of transitfeed-windows-binary-v.v.vv.zip (v is version information) and extract the contents to a directory on your hard drive. The zip file can be downloaded from https://developers.google.com/transit/gtfs/reference. Select the "Tools" option and then "feedvalidator" and "project download page". Then click on the most recent version of "Prebuilt Windows versions of FeedValidator, ScheduleViewer and other tools"
62
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
2. Locate the subdirectories containing GTFS data to be tested and viewed. These subdirectories may be a one of the input directories described in Section 4.8.2.1 or an output GTFS file generated by STOPS22. The end of this section describes the advantages of reviewing output files rather than the input files.
3. Drag the directory identified in Step 2 to the feedvalidator application located in the directory created in Step 1. The program will open a browser and display the results of the analysis as shown in Figure 34.
Figure 34. Output from GTFS Feed Validator 4. Drag the directory identified in Step2 to the schedule_viewer application located in the
directory created in Step 1. The program will open a console window as shown in Figure 35 which (after a few minutes) directs the user to open a browser window and type a localhost http: address. After this is done, the window shown in Figure 36 appears. Select each route and a trip time to view that route's coding. As shown in this example, the re-routing of 22 STOPS Step 5a can be used to generate two sets (peak and off-peak) of output GTFS files for the Existing (EXST) scenario for use with feedvalidator and ScheduleViewer. These files appear in the GTFOUTPUT\PK_TR_EXST\ and GTFOUTPUT\OP_TR_EXST\ subdirectories. Steps 5b and 5c generate similar GTFS outputs for the no-build (NOBL) and project (BLD-) scenarios. These output files include the effects of the multiple GTFS files, the editlist commands, the frequency specification, and hand-entered edits to the GTFS file set.
63
Federal Transit Administration STOPS v1.50 Users Guide
some trips on Route 12 (using the STOPS editlist capability) was mis-coded leading to an unintended route diversion. When the mis-coded stop was corrected, the route returned to the intended alignment.
Although scheduler_viewer is a powerful tool, the user should be aware of several limitations. First, it is not programmed to handle PNR or editlist files (STOPS extensions to the GTFS standard) so these changes are not displayed. Second, it does not combine GTFS files from multiple agencies, and third, it does not process the frequencies.txt file so the route and trip listing may not be complete.
To work around these limitations, STOPS and the GTFPath program can be used to generate an output GTFS file that includes combines GTFS from multiple agencies and apply frequency and editlist commands. The use of this command is described in Section 4.8.7.5.
Figure 35. GTFS Schedule Viewer Console Window
64
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 36. GTFS Scheduler Viewer Window Showing Error in Route 12 Re-Routing
4.8.4 Obtaining GTFS Files
In many cities, GTFS files for the current transit schedule are available on-line for public use. A listing of publicly-available GTFS files is found at: http://code.google.com/p/googletransitdatafeed/wiki/PublicFeeds Many agencies that do not make their feeds public still create these files so that on-line mapping tools can help customers plan trips. One good way of determining whether an agency generates this data is to go to Google Maps, select "Get Directions" and choose the transit option. Try to build a path between an origin and destination in the corridor to see if the agency has provided Google Maps with a transit feed. In cases where the transit feed is not publicly available, it might be obtained from the agency's scheduling department. Even if the agency does not generate a feed, the agency's scheduling software may be able to generate a GTFS file set for use in STOPS.
65
Federal Transit Administration STOPS v1.50 Users Guide
4.8.5 Setting up GTFS File Characteristics and STOPS Parameters in the Parameter File
This section illustrates the steps needed to configure the STOPS parameter file to recognize the different GTFS files that will be used in STOPS. This process begins by selecting "3. Edit Parameter File" and reopening the parameter screen and entering information for GTF File Set 1. If the corridor has multiple agencies and multiple GTFS file sets, then it may also be necessary to complete GTF File Set 2, 3, and 4. An example screen is shown in Figure 37. In this example, King County Metro (KCM) was selected to be GTF File Set 1 and Sound Transit (SND) was selected to be GTF File Set 2.
Begin with GTFS File Set 1. This block is always part of the STOPS analysis since there always must be at least one corridor agency for STOPS to run. If there are multiple agencies in the corridor, select one to appear in this block (In the case of multiple agencies, it doesn't matter which agency is stored in which block). Define the subdirectory names that are desired for the existing, no-build, and build alternatives. In the example, these subdirectory prefixes are "KCMEXIST\", "KCMNOB\", and "KCMBLD\", respectively. As can be seen in File Set 2, it is possible for the same directory names ("SND\") to be used in all three fields if the service is the same in all three scenarios.
Next define the Optional Suffix as described in Section 4.8.2.2 and the date of a typical weekday that is covered by the GTFS file. In this example, no suffix was required so this field is left blank and a typical day is specified as 2/13/2013. This date was found by reading the calendar file and selecting a weekday (a Wednesday in this example) that is included in the file. It is important that the selected day be included in the GTFS file set but any qualifying day will generate the same STOPS results.
Finally, select the character position ranges for Route ID, Trip ID, and Stop ID. As discussed in Section 4.8.1, STOPS is faster if a 9-character string can be used to uniquely identify each route, trip, and stop. In the example, character numbers 1-9 were selected for King County Metro while Sound Transit was left at the default values of 1-100. As it happens, both transit agencies always use short keys of 9 characters or fewer so it isn't necessary to restrict the character position numbers except to illustrate the point. In most cases, GTFS files use relatively short keys so the column restrictions are seldom necessary. The user should, however, confirm this fact by examining each agency's GTFS files prior to use.
Repeat this entire process for the second, third, and fourth agencies with separate GTFS files as needed to represent corridor transit services. If more than 4 GTFS files are required, the "Next page..." and "Previous page..." buttons may be used to bring up GTFS file sets 5 to 20.
Before leaving the parameter file, the user should also set the STOPS parameters at the bottom of the dialog. The first six parameters represent the ratios of various trip purposes and are prepopulated with national averages from on-board transit surveys obtained from the STOPS calibration cities. These ratios can be updated with information from local on-board transit surveys if a reliable estimate exists. Ratios that may be entered into STOPS include:
The ratio of Home-Based Other (HBO) linked transit trips to Home-Based Work (HBW) linked transit trips separately for traveler households with 0, 1 or 2 or more cars.
The ratio of Non-Home Based (NHB) linked transit trips to all Home-Based (HB) linked transit trips, separately for traveler households with 0, 1, or 2 or more cars.
The user is also allowed to enter a parameter that indicates the degree to which fixed guideway transit is more visible to the traveling public than local bus. In general this parameter should be set to 1.0 unless the fixed guideway system has some characteristic that makes it more similar to local bus than is usual.
66
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Finally, the user can select the Station Group Calibration Approach that will be employed when running stops. Options are:
00 (none selected). The user has not selected a Station Group Calibration Approach. In this case, STOPS defaults to Type 1, no calibration.
01 No Group Calibration. In this case, STOPS will not use station group information that was provided for the existing scenario to adjust model results for the base, no-build, or build. A no-group calibration run should always be prepared to help understand the expected ridership without any of the adjustments introduced by station calibration. In many cases, the ridership estimate generated with this option may be the most reasonable since it skips the process of applying station group adjustments that run the risk of distorting transit ridership patterns.
06 Static Group Calibration. In this case, STOPS computes station group adjustments for the existing scenario and then applies the exactly same set of zone-to-zone adjustments for the no-build and build scenarios. This means that even when a zone-to-zone trip changes station from the existing scenario to the no-build or build scenario, the same adjustments that were developed for the existing scenario will be applied in the no-build and build case. This approach has the advantage that estimates of the change in regional linked or unlinked trip will be directly related to the change in level-of-service between the no-build and build scenarios and not influenced by trip factors increasing or decreasing because of use of different station factors. The downside of this approach is that these factors are applied to specific access mode and path-type combinations so a project that involves a different mode or a different access type will not have the benefit of the station group factor.
07 District Ks-limited. In this case, STOPS generalizes the factors that were developed in for the existing scenario to the district level. These factors are still developed for individual combinations of access mode and path type but because they are generalized to the district level, these values are less subject to upward and downward spikes in type 06 that could affect individual interchanges. In type 07, the adjustments are limited to the range of 0.60 to 1.40. This means that the adjustments attempt to make minor corrections to observed ridership but do not correct for more serious problems that may cause estimated ridership to vary from observed ridership.
08 District Ks-full. This case is similar to type 07 except that a broader range of factors are allowed. In this type, factors are limited to the range of 0.30 to 2.00.
09 Full Group Calibration. This option is most like the STOPS v1.01 v1.04 station group calibration process. In this case, factors are developed for each on- and off-stop group combination for the existing scenario and applied to the no-build and build cases depending on the stops used in each alternative. For cases where there is a comprehensive database of station (and/or bus stop) ridership and where the project is unlikely to change the assigned station group, then this technique may be most appropriate. If the station groups change, this method does introduce the risk that estimates of changes to overall linked or unlinked trips may not be reasonable.
67
Federal Transit Administration STOPS v1.50 Users Guide
Version 1.50 Highlight:
The recommended setting for the visibility factors is different in STOPS Version 1.50 than in prior versions. Be sure to update the visibility factor to 1.0 unless there is some characteristic of the fixed guideway system that causes passengers to perceive this mode as being more similar to bus. In such cases, a visibility factor less than 1.0 (as low as 0.0) may be appropriate.
STOPS v1.50 has a new parameter that affects the approach used for Station Group calibration. Type 9 is most like earlier version of STOPS. If the user does not specify a calibration approach when creating a new run (or converting from earlier versions of STOPS) then STOPS will now run without any station group calibration. The examples shown in the remainder of the documentation assume that Calibration Type 9 is selected by the user. Note that the user must change the selection from Type 0 to Type 9 in order to replicate the examples in this manual.
Figure 37. Defining GTFS File Characteristics and STOPS Parameters
4.8.6 Identifying Required GTFS Files and Sub-Directories
Once the GTFS file characteristics have been defined, select "5. List and check GTFS files" to generate a listing of all required and optional GTFS files that will be used in the analysis. A series of three screens will appear identifying all GTFS files to be used in the Existing Scenario, the No-Build Scenario, and the Build Scenario. An example is shown in Figure 38.
68
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 38. Example GTF File Status Screen
69
Federal Transit Administration STOPS v1.50 Users Guide
4.8.7 Creating GTFS Sub-Directories and Data Files
In many cases, the GTFS files obtained from the transit agency represent the existing case without modification and can be copied into the "Existing" subdirectory. In the example discussed in the previous section, the user should create a subdirectory of the "inputs\" directory that is named "KCMEXIST\". The existing King County Metro GTFS Files would be copied into this subdirectory if they properly represent the existing calibration scenario. Likewise in the example given above, the user would create a "SND\" subdirectory and store GTFS files from Sound Transit in that location. The contents of each of these directories are shown in Figure 39. Note that there are fare, agency and other files present that are part of the GTFS file set but are not read by STOPS. These files are present to ensure that the feed validator works properly and should always accompany the other GTFS files.
Figure 39. Contents of KCMEXIST\ and SND\ GTFS Subdirectories
Next, the user must create GTFS files for the King County Metro No-Build Build Alternatives and place these files in the "KCMNOB\" and "KCMBLD\" subdirectories of "Inputs\". The easiest approach (for the modeler) is to obtain pre-built GTFS files representing each scenario from the scheduling department and copy them to these subdirectories.
70
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
The remainder of this section assumes that this isn't possible and that the user must hand-code the project modifications.
4.8.7.1 Description of Illustrative No-Build and Build Scenarios
This section illustrates principles associated with coding GTFS scenarios for STOPS. It will build on the Seattle example already discussed. Two scenarios will be defined23:
No-Build. Assume that the existing South Lake Union (SLU) streetcar that currently terminates at Westlake/Olive is programmed to be extended south one stop to a new transfer point that also serves the Sound Transit Central Link Westlake station. No other service changes are foreseen.
Build. Assume a new streetcar line is constructed between Madison/5th Avenue and Madison/Broadway with an intermediate stop at Boren Avenue. Assume that the line runs on 10 minute headways in the peak period and 15 minutes in the off-peak. Also assume that buses on 3rd Avenue deviate off of their existing route to service the 5th Avenue station.
The example that follows assumes that the user has already downloaded the existing GTFS files for King County Metro and Sound Transit and stored these files in the "Inputs\Exist\" and "Inputs\SND\" subdirectories.
4.8.7.2 Coding the Existing Alternative
In most cases, the GTFS files obtained from the local transit agency can be used without modification. Occasionally, however, these files must be adjusted for use in STOPS. Seattle presents one of these cases. If a fixed guideway service and a bus use the same set of stop_ids (e.g., in the Seattle Bus/LRT tunnel), then the user should create a separate set of stop_ids for the LRT and reroute the LRT onto the alternative stop_ids. As shown Figure 40, stop_ID 501 is copied and named 99501 to represent a new LRT-only stop at the same location (Pioneer Square). As always, when new stop_IDs are added to the stop file, it is important to confirm that this stop doesn't duplicate the ID of another stop. The following new LRT-only stops are defined24:
91108 and 91121 Westlake Station 99455 and 99565 University Street 99501 and 99532 Pioneer Square 99623 and 99621 International District
After all separate LRT stop_IDs are defined, editlist can be used to reroute the LRT onto the LRTspecific stop_IDs as shown in Figure 41. In the first non-comment line, the portion of Route 100479 between 1108 (Westlake Station in the original file/to be used for buses only) and 99101 (LRT-only station in original file at Royal Brougham Way) is rerouted to the following sequence of stops and times:
Start at 91108 (new LRT-only Westlake Station), travel 2.13 minutes to 99455(new LRTonly University Street Station)
23 These examples are intended to illustrate project coding techniques. They were developed by the STOPS development consultant and are in no way reflective of any planned projects in the Seattle area. 24 Two nodes are required--one for each direction of travel since the existing bus/LRT tunnel stations are coded separately for each direction.
71
Federal Transit Administration STOPS v1.50 Users Guide
Travel 2.62 minutes to 99501 (new LRT-only Pioneer Square Station) Travel 2.00 minutes to 99623 (new LRT-only International District) Travel 1.53 minutes to 99101 (existing LRT-only Royal Brougham Way) where the route
continues on following the original line coding. A similar re-route command is coded for routes traveling in the opposite direction.
Figure 40. Addition of Fixed-Guideway-only STOP_IDs
Figure 41. Editlist Re-Route to Use LRT-specific STOP_IDs
4.8.7.3 Coding the No-Build Alternative
The no build alternative is relatively simple to code: 1. Copy all GTFS files from the "KCMEXIST\" subdirectory to the "KCMNOB\" subdirectory
72
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
2. Investigate the files (see Figure 42).
a.
Route_ids are generally 6 characters and trip_ids have 8 characters. This means that
no column definition is required
b. The route file shows that the SLU Streetcar is coded as route_id "100340" with a short name of "98".
c.
The trip file shows that most weekday trips on route_id 100340 have a trip_id
between "19032246" and "19032387".
d. The stop_time file shows that the first northbound trip begins at stop_id 26680
e.
The stop file files show that stop_id 26680 is Westlake Avenue and Olive Way.
f.
Investigation of additional routes using the schedule_viewer shows that Northbound
trips all begin at Stop 26680 while south-bound trips terminate at Stop 1630. This is
determined by clicking on each route pattern for route 98 in the left hand box, and
then clicking on the Westlake Station to see the node number. This is shown in
Figure 43. This process can also be used to show that northbound trips beginning at
26680 next travel to 26689. Southbound trips that end at 1630 all come from 1619.
3.
The Central Link Westlake Station is 2 blocks south at Pine and 4th Avenue where the
illustrative new streetcar station would also be located (See Figure 44).
4. Edit stops.txt to add the new Westlake Transfer station at (47.611762,-122.336562). Search the King County Metro and Sound Transit Database to confirm that 26681 is not used and define a new streetcar stop with this stop_id (See Figure 45).
5. Start with the existing editlist file to keep the edits previously entered. Add a re-route command to extend all southbound trips from 1630 to 26681. Add another command to begin all northbound trips at 26681 before traveling to 26680. This is done by identifying links to re-route (links are used instead of nodes so that directionality can be taken into consideration). Figure 46 shows the completed editlist. As shown in this figure, one editlist command is created for each direction. Each line uses two stop_ids to identify a link to be modified in terms of the first stop and last stop in the section that is to be changes. A replacement string shows how these two stops become three stops after the re-route. For the southbound service, the new routing begins at 1619, travels to 1630 in 0.88 minutes (same as the original file), and then continues to 26681 in 1.5 minutes. In the reverse direction, the new extension will begin at 26681, travel to 26680 in 1.5 minutes and continue to 26689 in 1.17 minutes where it resumes the originally scheduled run.
Make sure that the new station is also coded in the station file ("2. Specify Station Locations" from the STOPS Main Menu) and that it references the stop_id (26681). When this is done, the no-build alternative is ready for processing.
This is all that needs to be coded since there is no need to add any routes or trips. (See the description of the build scenario coding for an example of these steps). Section 4.8.7.5 discusses the steps that can be used to confirm the accuracy of GTFS coding for each alternative.
73
Federal Transit Administration STOPS v1.50 Users Guide
Figure 42. GTFS File Investigation
74
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 43. Westlake Terminus of SLU Streetcar
75
Federal Transit Administration STOPS v1.50 Users Guide
Figure 44 Westlake Terminus of Central Link LRT
Figure 45. New Stop Added to Stop File
76
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 46. Re-route existing Streetcar to Extend Service to New Station
4.8.7.4 Build Alternative Coding
In many ways a brand new alternative is easier to code than an extension to an existing line since much less investigation is required into the nature of the existing service. The build example described in Section 4.8.7.1 inserts a brand new rail line with all new stations. It does, however require that routes on 3rd Avenue be diverted to 5th & Madison. The other route direction operates on 4th Avenue, is only a block away from the streetcar line, and will not be diverted as part of this illustrative scenario.
1. Copy the "KCMNOB\" directory to the "KCMBLD\" directory. This will result in the build directory containing all of the improvements already made to the no-build scenario.
2. Continue the investigation of routes to identify what re-routing is required. As shown in Figure 47, when no route is selected and the user clicks on a stop, the schedule_viewer will display all routes serving that stop. Clicking on the stops on 3rd Avenue, reveals the fact that Routes 26 and 358 travel between stop_id 468 at 3rd Avenue and Seneca Street then to stop 490 at 3rd Avenue and Columbia. For this example, we will assume that the bus deviates to stop 1400 at Madison Street and 5th Avenue. In a real alternative, more research would be conducted to find a list of all buses that should be re-rerouted and separately consider trips in either direction.
3. Update the editlist file to add the project re-routes to the editlist file (keeping the NOBL edits, previously entered). This reroute uses a "*" wildcard to indicate that all buses serving stops 468 and 490 (in that order but not necessarily adjacent) regardless of route will be rerouted to stop 1400 with a travel time of 1.2 minutes to 1400 and 1.2 minutes back to the original route. This change is shown in Figure 48.
77
Federal Transit Administration STOPS v1.50 Users Guide
4. Create three new stop ids for the new streetcar route (26682, 26683, and 26684) and enter them into the stop file. (See Figure 49).
5. Edit the route file to create a new route making sure that the route ID is not duplicated in either this file or the SND\ route.txt file. (See Figure 50).
6. Edit the trip file to create two unique trips for this route (one in each direction), making sure that the trips IDs are not duplicated in this or the SND\ trip files. In this example, this is accomplished by using characters to describe the new routes. These are legal GTFS trip IDs and are case sensitive. (See Figure 51).
7. Edit the stop_time.txt file to create time points for each stop on each trip. (See Figure 52).
8. Edit the frequency.txt file to indicate the frequencies for this route. (Figure 53).
Figure 47. Exploration of Routes Serving Third Avenue Stops
78
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 48. Records Added to Edit List File to Represent Re-Route of 3rd Avenue Routes
Figure 49. Records Added to Station File to Represent New Streetcar Stations
Figure 50. Record Added to Route File to Represent New Streetcar Route
79
Federal Transit Administration STOPS v1.50 Users Guide
Figure 51. Records Added to Trip File to Represent New Streetcar Trips
Figure 52. Records added to the Stop_Time file for New Streetcar Trips
Figure 53. Records Added to Frequency File
80
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
4.8.7.5 Confirmation of GTFS Coding
GTFS Coding is complex and it is sometimes difficult to know if the changes are coded correctly without testing the networks for accuracy. This is further complicated by the fact that the schedule_viewer program does not process the editlist or frequency commands. Optional STOPS commands are available to use GTFPath to read the existing, no-build, and build networks and construct a GTFS file set that converts editlist and frequency commands into a series of peak and off-peak oriented networks that can be mapped with scheduler-viewer. This process is accomplished by clicking on "5a EXST GTFS Test", "5b NOBL GTFS Test", or "5c. PROJ GTFS Test". This step will cause GTFPath to build peak and off-peak networks for the existing, no-build, or build scenarios, respectively. Output networks are generated and placed in subdirectories of the GTFOutput\ directory. Subdirectories are identified according to the time period ("PK" or "OP" for peak and off-peak) and ("EXST", "NOBL", or "BLD-" for each scenario) The GTFS Test procedures separately test the peak and off-peak networks. After each run, STOPS asks if the user would like to review Fixed Guideway STOP_IDs. If the user clicks "Yes", then STOPS opens notepad and displays a file showing the internal STOP_IDs served by Fixed Guideway lines. Examples of the message box and the sample file from Nashville are shown in Figure 54. The last station in this example shows a station with a long (greater than 9 characters) STOP_ID that was given a shorter alias in place of the long ID. The alias is formatted as nnnnnS# where "nnnnn" is an internally generated numeric ID (1 in this example), the S is the suffix (may be blank and is "A" in this example), and "#" which is a code indicating an alias. The STOP_IDs (or alias if provided) is what is coded in the station file GTFS STOP_IDs. To view the transit networks:
Drag the desired subdirectory (e.g., "PK_TR_BLD-" for the peak build scenario) to the schedule_viewer application
Select on each relevant line to determine whether the GTFS edits were properly implemented. The three key schedule changes to the build network example are displayed in Figure 55, Figure 56, and Figure 57.
81
Federal Transit Administration STOPS v1.50 Users Guide
Figure 54. Listing of Fixed Guideway STOP_IDs
82
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 55. Scheduler Viewer Showing Extension of SLU Streetcar
Figure 56. Schedule Viewer After Addition of New Streetcar
83
Federal Transit Administration STOPS v1.50 Users Guide
Figure 57. Southbound Route 26 Deviation to 5th/Madison
4.8.8 Confirming that All GTFS Files are Present
When all GTFS Files are present, the status next to "5. List and Check GTFS Files" changes to "FILES FOUND!" as shown in Figure 58. If all files are not present, then click on "5. List and Check GTFS Files" to see which files are missing.
84
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 58. STOPS Main Menu After All GTFS Files are Found
4.8.9 Final Review of Station File
After all of the GTFS Files are updated, make sure that all stations are present in the Station file. If necessary, select "2. Specify Station Locations" to add any stations that were missed earlier as shown in Figure 59. The user should also check the coding of each field, particularly the STOP_ID fields which may have been left blank during earlier edits. The user should run the GTFS Test steps described in Section 4.8.7.5 to confirm that all relevant STOP_IDs are assigned to a station.
85
Federal Transit Administration STOPS v1.50 Users Guide
Figure 59. Adding New Stations to Station File
4.9 Define Forecast Years
The next step involves specifying the parameters associated with each of the forecast years that will be used in STOPS. This process begins by clicking "6. Define Forecast Years" on the STOPS Main Menu. The first time that this option is selected, a dialog will appear asking the user if it is OK to create a new file (see Figure 60). Click "Yes" to continue. Next the dialog shown in Figure 61 appears. This dialog defines each of the analysis years, variables in the MPO zone layer file, and other related ridership information. Most items relate to the MPO zone layer file described in Section 4.6.2. Field names are selected from drop down lists containing the available field names in the MPO zone data file. Year fields are character strings that generally contain the year numbers that are used to identify reported data and file names for results. Linked and unlinked trips are numeric fields that are entered by the user and are used by STOPS as part of its self-calibration routine. The following data are entered in this dialog:
Numeric TAZ Field Name (required). The field in the MPO zone layer file containing the MPO TAZ number used to identify origins and destinations in the auto skim file.
CTPP Year (2000) Population Field Name (required). The field in the TAZ layer file containing the MPO estimate of Year 2000 population.
CTPP Year (2000) Employment Field Name (required). The field in the TAZ layer file containing the MPO estimate of Year 2000 employment.
Current Year (required). A character string identifying the current year for the model calibration and application.
Current Population Field Name (required). The field in the TAZ layer file containing the MPO estimate of current year population.
86
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Current Employment Field Name (required). The field in the TAZ layer file containing the MPO estimate of current year employment.
Current Year Regional Transit Unlinked Transit Trips (weekday transit boardings, optional). If this number is entered, then STOPS will self-calibrate to match the number of regional transit boardings. STOPS will adjust the modeled number of unlinked trips traveling within the 25-mile corridor and using the coded GTFS services to match this entry. It is very important that the coded number reflect both the geographic corridor definition and the GTFS systems included in the model run. If significant services for one of the agencies included in the GTFS inputs serve areas outside of the 25-mile corridor radius then any trips occurring in whole or in part outside of the corridor should be excluded from the unlinked trip estimate. Likewise, travel on smaller operators that are not represented by the GTFS files should be excluded from the estimate of regional ridership.
Current Year Home-to-Work and Work-to-Home Linked Trips (weekday linked journey-to-work and from-work transit trips, optional). If a recent transit survey was conducted, it may be possible to generate a more refined estimate of travel--linked transit trips occurring between home and work and work back to home. This definition is equivalent to journey-to-work plus journey-from-work trips--which comprise both traditional home-based work trips and other travel that involves a stop-over on the way to or from work. This entry should also reflect the corridor definition and GTFS file constraints that apply to unlinked trips.
Optional Years and Field Names for Opening Year, 10-Year, and 20-Year Forecasts (optional). STOPS allows definition of up to 3 additional years that represent the project opening year, a medium-term horizon year, and a long term horizon year. These entries are optional.
Growth Factor Geography. This flag indicates whether STOPS will factor trips on a zoneby-zone basis or on a district-by-district basis. Generally zone level factoring is preferred unless the estimates of zone-level population and employment are not consistent between years and should not be used for updating the CTPP. District level factoring will generate much more consistent growth between the zones in the corridor while zone factoring will show greater differences in growth among zones. The decision of which to use depends on the nature of the MPO forecasts. If the MPO estimates of zone-specific growth assumptions are thought to be representative of future plans, then zone factoring should be used. If the zonal variation is thought to represent spurious differences in data sources then district factoring should be used.
87
Federal Transit Administration STOPS v1.50 Users Guide
Figure 60. Dialog to Confirm Creation of Year Definition File
Figure 61. Year Definition Dialog
88
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
5. DATA PREPARATION STEPS
In the previous chapter, the user defined the STOPS run and prepared input information that will be used to estimate project ridership. If every initial set-up step was successfully completed, then the STOPS Main Menu should show the status as being "FILES FOUND!" through Step 6. (See Figure 62).
Figure 62. STOPS Main Menu At Beginning of Data Preparation This chapter describes the next round of STOPS preparation steps, focusing on additional data that is required to generate estimates of Fixed Guideway boardings. Four steps must be accomplished to complete data preparation as described in the following sections. The steps described in this section are different from the previous section in a very important way. In the previous section, the user is setting up the model run and the steps need not be accomplished sequentially. As the documentation notes, the user may go back and forth between editing stations, specifying parameters, and coding GTFS scenarios until all files are fully defined. Beginning with this section, STOPS steps are highly sequential. Any change to an earlier step affects many down-stream steps. If it becomes necessary to recode a data item in an earlier step, then all later elements of Data Preparation must be re-run to ensure that all data is properly updated throughout STOPS.
89
Federal Transit Administration STOPS v1.50 Users Guide
5.1 Create Station Buffers
This step is a completely automated process that builds a series of buffers around the stations that were defined in Section 4.2 and compares them to the CTPP geography (TZ, BG, or TR) file defined in Section 4.5.1. The principal result is a file containing a listing of each CTPP zone (TZ, BG, or TR) to be included in the modeling file and the proximity of each zone to any fixed guideway station and the distance to the nearest PNR station. This program also creates a blank district file in ESRI shape format that is pre-populated with district=99 (i.e., unknown district) or whatever districts were assigned after an earlier run of this program. See Section 5.2 for more information about the process of defining districts.
The step is initiated by clicking on "7. Create Station Buffers". This command will call the program "StatBuffZone" which run for several minutes without any need for user intervention. When done, the program will return to the STOPS Main Menu.
It is possible (including with the Sample data) that you will receive an error message that says:
"Error: Duplicate zone names found. Split Zones (or duplicate zones form the original census files) must have alternate name specified in LSAD_TRANS field of CTPP Zone File.
A follow-up message will direct you to a file that contains a list of duplicate names.
When this happens, open up your TAZ (or BG or TR) census geography file and code a unique override zone label in the LSAD_TRANS field. (see the discussion on split zones in Section 4.5.3 for a more complete discussion of this process). As long as the value is unique, it can be any 6 character string. When this changes is made, re-run the Create Stations Buffer step. Once all duplicates have been resolved, the error message will not be generated and this step will be labeled with "FILES FOUND!"
5.2 District Definitions and Zonal Data
Districts are groups of one or more zones25 that are used by STOPS to aggregate travel data to a level suitable for model calibration and reporting. Depending on the type of growth factoring selected by the user, districts also define the unit of geographic analysis used to update the Year 2000 CTPP to represent current and forecast year population and employment. Given this important role inside STOPS, districts must be defined that represent groups of similar stops along the project and other existing fixed guideway lines. Districts should represent areas with levels of walk and drive accessibility to stations that are relatively close to one-another and share similar levels of transit service. A basic district system for the LRT line in Houston, TX is shown in Figure 63.
25 In this section, the word "zone" will be used to describe any of the geography types (TZ, BG, or TR)
90
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 63. Sample District System for Houston, TX Districts are defined in an ESRI shape file that contains one contains one record for each zone in the corridor. As noted above, the original file is created in Step 7. Create Station Buffers which creates a "starter" district file with one record for each zone in the modeling area. If a district file had been previously created, then Step 7 copies the district definition to the new file. If this is the first time that Step 7 is run, then it creates a district file with all districts set to "99" (defined as the "Other" district). After the starter district file is created, the User can update the District file and assign a specific district number and name to each zone. This is done by clicking on "8. Define Districts and Zonal Data". When this button is clicked, STOPS goes directly to TransCAD or ARCGIS and opens the screen shown in Figure 64 (TransCAD implementation). The map shows the location of each fixed guideway station that had previously been entered in the station file and a thematic map showing each zone and the district number assigned to that zone. The user can update the following data to be representative of the intended district system:
ST-CO-TAZ the full name of the TAZ (or block group or tract). This field is the full name of each zone as is prepopulated in the data file and should not be changed.
DISTRICT District number (required and entered for every zone). This 2-digit integer is used to identify the geographic district used for data summarization and mapping. Typical districts might include the CBD and a system of wedge-shaped districts that relate to key transportation corridors radiating outward from the CBD. The wedges may also be segmented by the characteristics of the area (e.g., urban, suburban, and exurban). Generally the reports are most readable if 10 to 15 districts are defined.
DIST_NAME - Description (required but entered once for each district--most zones left blank). A description field is provided for every zone but the user should name each district just once. The zone that is selected for the description will be used later in STOPS to define a representative location for mapping travel times to the district. The description,
91
Federal Transit Administration STOPS v1.50 Users Guide
itself, is used to label district-to-district tables If multiple labels exist for a district, then STOPS uses the description from the highest numbered row in the data file as the description. In Figure 65 zone "53033 136" is identified as the representative zone for District 1, the CBD. This field can be up to 18 characters wide. The first 5 characters are used as headings in district-to-district matrices so it is important that the first 5 characters be recognizable as a label for the district. This can be accomplished by using an abbreviation and a more complete description (e.g., "CBD Cent Bus Dist", "OTHRE Other East", "OTHRW Other West")
CLONE_TAZ - CloneTAZ (optional and only coded in cases where a zone completely changes its character). When forecasting CTPP JTW into the future, STOPS grows demand according the relative size of Year 2000 and forecast year population and employment. In areas with moderate growth, this is sufficient to generate a reasonable estimate of future travel. Some areas, however, are likely to change their character dramatically (e.g., from farm land to suburban activity center). The clone zone allows the user to indicate that a given zone represented by the row in the database should be treated as though it has the population, employment, and CTPP flows of one or more nearby zones that are a "clone" of what is expected to occur.
Example: assume that zone "08012 1201" "the borrower zone" had an employment of 10 in 2000 but is expected to have 2,000 employees in 2010. Also assume that zones "08012 1202" and "08012 1203" (the "clone" zones) are nearby and together had a Year 2000 employment of 10,000. In that case, the user might code record "08012 1201" so that it borrows the characteristics of clone zones "08012 1202" and "08012 1203".
There are two ways to attach a clone zone to a borrower zone.
o Case 1 A borrower zone uses just a single clone. In this case, find the record in the district file for the borrower zone (field "ST-CO-TAZ" contains the borrower zone) and code the clone zone in the CLONE_TAZ field. If the user wants zone "08012 1206" to borrow trips from clone zone "08012 1207", then go to the record in which ST-CO-TAZ is equal to "08012 1206" and code the data as follows:
ST-CO-TAZ 08012 1206
CLONE_TAZ 08012 1207
o Case 2 A borrower zone uses the CTPP records for a group of zones. In this case, the CLONE_TAZ file is used to define a series of group labels that identifies the clone group that a zone might contribute to and also the clone group that the zone borrows from. This is done by coding two groups "(group to contribute to" and "group to borrow from" separated by a comma) in CLONE_TAZ. Any combination is possible: Zone contributes to a group and borrows from that group (or any other group) both groups are specified, separated by a comma. Zone contributes to a group but does not borrow from a group a group is specified before the comma but nothing appears after the comma. Zone borrows from a group but does not contribute a group is specified after a comma but not before Zone is not involved in cloning, the CLONE_TAZ field is blank.
92
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
If zones "08012 1202" and "08012 1203" contribute to "GRPA"26 and "08012 1201" borrows from GRPA, then the following data would be coded:
ST-CO-TAZ 08012 1201 08012 1202 08012 1203
,GRPA GRPA, GRPA,
CLONE_TAZ
Records representing both Case 1 and Case 2 can be mixed in a single file but no one record can be both Case 1 and Case 2.
Hint: Clone zones should be selected that had characteristics in Year 2000 of what the "borrower" zone will have in the forecast years. If the borrower zone has dense employment and no population then the clone zones should be a set of nearby zone(s) that had (have) an employment node in 2000. If the borrower zone will have little employment but significant population in 2035 then the clone zone should be a set of nearby zone(s) with significant population in 2000 but little employment. If the borrower zone has significant levels of population and employment, then the clone group should have had significant levels of population and employment in 2000.
26 The CLONE_TAZ field is 12 characters wide. Clone group names should be used that are 5 characters or less if a single zone may both contribute to a group and borrow from a group. If that never happens, then group names may be 11 characters wide.
93
Federal Transit Administration STOPS v1.50 Users Guide
Figure 64. District Definition in TransCAD
Figure 65. District Map Following District Definition
94
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
5.3 Create MPO-TAZ Equivalency and File and Generate Zonal Socioeconomic Forecasts
This is a fully automated step that (1) creates an equivalency file between the CTPP geography and the MPO zone system and (2) generates a file with one record for each unit of CTPP geography containing MPO forecasts of population and employment for each year defined in the forecast year parameter file. It is important that this program be re-run any time the MPO zone file or the forecast year definitions are changed. This step is initiated by clicking on "9. Create MPO-TAZ Equivalency and Generate Zonal SE Forecasts". This procedure will start a program that will run for several minutes, and return to the STOPS Main Menu. No user actions are required during this process.
5.4 Prepare Pedestrian Environment Data
This is a fully automated step that generates an estimate of the number of Census blocks contained in each unit of CTPP geography. This statistic is used to provide an indication of the completeness of the street grid in a zone which is often indicative of the walkability of an area. This step is initiated by clicking on "10. Prepare Pedestrian Environment Data". This action will start a program that will run for several minutes, and return to the STOPS Main Menu.
95
Federal Transit Administration STOPS v1.50 Users Guide
6. RUN STOPS BATCH STEPS
After all set-up and data preparation steps are finished, the STOPS Main Menu should indicate "FILES FOUND!" for all steps in the left hand column (see Figure 67). The next step is to run the batch steps. This part of the STOPS process may take between one and twelve hours depending on the speed of the computer, the number of regional zones, and the complexity of the regional transit system.
This step is performed by:
1. Selecting a year to model (any of the previously defined years: Current, Opening Year, 10Year Forecast or 20-Year Forecast)
2. Clicking on "11. Run Batch Steps"
The user can optionally select which batch steps are run using the check boxes. STOPS defaults to running all of the following steps:
1. CTPP Extract. This step calls the CTPPExtract program which reads the CTPP files and prepares an output dataset with one record for each zone-to-zone pair containing the number of CTPP JTW flows. This file also contains space for later posting of zone-to-zone travel times and other data. A separate zone-to-zone file is created for each scenario (existing, no-build, and build). Until travel time data is posted (in GTF Post, below), these three files are identical to one-another.
Hint: This step should be skipped if CTPP Extract has already been run and nothing in the parameter file or station ESRI shape file has changed. Even if these files have changed then CTPP Extract should not be re-run unless the stations have changed so much that the corridor definition would change or unless the parameter file changed the states in the corridor or type of zone (TZ, BG, or TR). The advantage of not re-running CTPP Extract is that if the GTF Path file can be skipped, the GTF Post step can also be skipped, saving considerably on STOPS execution times. This will frequently occur when the user wishes to re-run STOPS with a different forecast year or if the user wishes to change clone zones or other socioeconomic data.
2. GTF Path. This step calls the GTFPath program which reads the GTFS files and generates estimates of zone-to-zone transit travel times. This program is called 18 times--once for each combination of:
i. Peak (PK) and off-peak (OP) times-of-day ii. All transit (TR), fixed guideway transit only (FG), and bus transit only (BS)
service type combinations iii. Existing (EXST), no-build (NOBL), and build (BLD-) scenarios
96
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Hint: The GTF Path step can be skipped if GTF Path has already been run for the current zone system, the current definition of GTFS subdirectories, and if the contents of the GTFS subdirectories have not been changed since GTF Path was originally run. This could save considerable processing time and is most useful if the user wishes to re-run STOPS with a different forecast year or for a different set of clone zones or SE data.
3. GTF Post. This step calls GTFPost which reads each zone-to-zone JTW flow file and posts the appropriate travel times to each record.
Hint: The GTF Post step can be skipped if GTF Post has already been run for the current set of skims and CTPP Extract tables. Skipping this step will save considerable time. It needs to be re-run only after CTPP Extract is re-run (since that program clears the posting) and any time the GTF Path skims are updated.
4. Prepare Forecast Years. This step calls the program that reads each zone-to-zone JTW flow file (with posted time estimates) and grows the file to represent the user-selected forecast year.
5. Run STOPS. This step calls STOPS, the program that generates estimates of fixed guideway ridership for each scenario for the year specified at the beginning of this phase.
After the User selects the steps to run, STOPS will ask for confirmation that it is OK to run Batch steps. Next, STOPS give the user the opportunity to de-select the current, no-build, or build elements of GTF path, GTF Post, and preparing forecast years. The option to de-select these steps is only active if STOPS detects the presence of the appropriate files generated by an earlier run. It is the responsibility of the User, however, to confirm that these earlier results are still correct for the intended run. The de-select option is provided since in many analyses, the existing and no-build runs are unchanged from earlier runs and skipping these steps can save considerable time. The dialogue that allows the user to de-select elements of certain steps is shown in Figure 66. Dialogue for Running Batch Steps and De-Selecting Scenarios.
Figure 66. Dialogue for Running Batch Steps and De-Selecting Scenarios
97
Federal Transit Administration STOPS v1.50 Users Guide
No user action is required during the remainder of the process. A series of similar windows will open that describe the progress of each step. When all steps are done, the program returns to the main menu.
Figure 67. STOPS Main Menu Before Batch Steps
STOPS can be re-run for each of the defined years by selecting each one of the radio buttons (Current, Opening Year, 10 Year and 20 Year) and re-running the batch processes. As suggested in the hints above, after the first run is complete, the user can save considerable processing time by unchecking "CTPP Extract", "GTFPath", and GTFPost". Unless the user changes the GTFS directories or edits the GTFS files, the only steps that differ from year-to-year are the steps associated with "Prepare Forecast Years" and "STOPS".
98
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
7. REPORTING RESULTS
When STOPS is finished with the batch processing steps, the STOPS Main Menu will show that all steps are complete as shown in Figure 68. Once this milestone has been achieved, the user can open up a report describing STOPS results and prepare a series of maps that display the characteristics of trips and travel times. This chapter describes both of these steps.
Figure 68. STOPS Main Menu After Completion of Batch Steps
99
Federal Transit Administration STOPS v1.50 Users Guide
7.1 Report STOPS Results
The STOPS results are found in the "reports\" subdirectory in a text file with a name that indicates the nature of the run represented in the report. In the Seattle example, this file is named:
TZ_KCMEXIST-SND#KCMNOB-SND#KCMBLD-SND_STOPSY2010Results.PRN
This filename has the following components:
Whether the analysis was conducted at the TAZ, Block Group, or Tract Level ("TZ", "BG", "TR"). "TZ" in the Seattle example.
Underscore ("_") as a separator The GTFS subdirectory name (or names separated by a hyphen) that make up the Existing
Scenario. KCMEXIST-SND (to represent that this scenario includes both the KCMEXIST and SND GTFS subdirectories). "#" as a separator The GTFS subdirectory name (or names separated by a hyphen) that make up the No-Build Scenario. KCMNOB-SND. "#" as a separator The GTFS subdirectory name(or names separated by a hyphen) that make up the Build Scenario. KCMBLD-SND Underscore "_" as a separator "STOPS" The Analysis Year. Y2010. Results.prn"
The report can be opened by clicking on "12. Report STOPS Results". STOPS will open up a notepad window and display the report for the selected year. The beginning of this report is shown in Figure 69.
Figure 69. Example Report File
100
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
The report file begins with a table of contents describing the 15 sections of the report and the tables that are provided in each section. Each report section is described below.
7.1.1 Summary of Key Inputs
Section 1 provides a summary of key model and run parameters including: Years for the demand matrices that are associated with the base, no-build, and build scenarios Key STOPS model coefficients Key parameters associated with each scenario
This part of Section 1 is shown in Figure 70. Section 1 also contains a summary of the station data that was used for this model run as shown in Figure 71.
Figure 70. Section 1 - Run Parameters
101
Federal Transit Administration STOPS v1.50 Users Guide
Figure 71. Station Listing
7.1.2 Summary of Existing Scenario Results Before Station Group Calibration
Section 2 summarizes STOPS results for the existing scenario before the station group calibration process begins. The information in this section provides an indication of how well STOPS can calibrate itself to local conditions using just CTPP estimates of attraction district transit share, regional unlinked trips, and HBW linked trips, (if provided). This information can be helpful in determining how well STOPS understands the particular markets being modeled and may provide an indication that additional refinement to the inputs are required before STOPS is used to forecast project linked trips.
Table 2.01 (see Figure 72) provides a summary of the CTPP person and transit trips and compares these numbers to the linked trips estimated from user-coded estimates of linked and unlinked trips.
This information is followed by a district summary of CTPP Journey-to-Work productions and attractions by transit and for all modes of travel and by production and attraction transit constants computed by STOPS during initial calibration. The information in the district-level summary can be copied into the "ImportDistrictCalibration" worksheet of the STOPS replication spreadsheet.
Figure 72. Initial Calibration Statistics
102
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Table 2.02 (Figure 73) provides a listing of trips by production district and station group. Table 2.03 provides a similar table for trips by attraction district. Together these two tables can be useful in determining where modeled group volumes begin and end their trips. This can be an important clue about the reasonableness of STOPS estimates of transit demand. If calibration Types 7 or 8 are selected, Tables 2.02 and 2.03 are repeated 5 more times for each iteration of the district calibration process. Tables 2.04 and 2.0527 are shown in Figure 74. Table 2.04 presents the station group-to-station group ridership for the existing scenario and current year prior to group calibration. Table 2.05 shows the factors that were computed during the station group calibration that will be used to create the final set of model results. Ideally, the ridership estimates shown in the "TOTAL" row match the "COUNTS" and the "GOAL" role reasonably well. When this happens, the factors in Table 2.05 are approximately equal to 1.0 and (0.8 to 1.2) and the station group factors result in modest changes to demand. As shown in the Seattle example, this is true for the existing SLU streetcar and much of the Central Link system. On the other hand, the Tacoma Link (TL) and Vashon Ferry (FEVash) have much larger factors. This does not present a problem for this analysis since neither service has a large impact on the project but could be problematic for a ferry analysis or a project to extend the Tacoma Link streetcar project. In the case of the later, it would be necessary to add Pierce County bus service to fully understand the role of the streetcar in Tacoma28. Immediately following Table 2.04 is a statement that "all GTFS stations found in station input. This means that all Fixed Guideway stop_ids that are part of paths used by each CTPP JTW flow record were found in the station data base. On occasion, STOPS may find some stations in the CTPP JTW flow records that are not included in the station file. In this case, STOPS will generate a message similar to:
WARNING: 1 GTFS station(s) were missing from station input 1: scenario= 1, GTFS Station_ID=55656
In general, the user should code all fixed guideway stop_ids into a station record29. This is done by returning to Step 2. Specifying Station Locations and adding the stop_id to an existing or new station record. When this is done, the STOPS batch step can be rerun. It is not necessary to re-run any other step.
27 These station group-to-station group ridership tables before calibration appear as Tables 2.04 and 2.05 for Group Calibration Types 00, 01, 06, and 09. They appear as Tables 2.16 and 2.17 for Group Calibration Types 07 and 08. 28 When Pierce County transit is added, Tacoma Link ridership is properly estimated. 29 If the stop_id is completely irrelevant to the project being modeled, this step can be skipped. For instance, Tacoma Link stop_ids can be removed from the station file with little or no impact on the Seattle Streetcar.
103
Federal Transit Administration STOPS v1.50 Users Guide
Figure 73. Production District - Station Group Results
Figure 74. Station Group Boardings Prior to Adjustment
104
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
7.1.3 Summary of Station Group Calibration Process
Section 3 summarizes the results of the station group calibration process. Tables 3.01, 3.02, and 3.03 (Figure 75) shows the group-to-group ridership for the existing, no-build, and build scenarios. In the example provided, these tables reveal that:
Existing daily linked trips in 2010 (317,222) would have grown to 317,991 with the extension of the SLU streetcar to the West Lake Central Link station in the 2010 no-build scenario. Streetcar ridership would have grown from 2,919 to 3,633.
Daily linked trips in the 2010 build scenario would have grown to 319,418. Although not shown in this screen shot, the new Madison Streetcar (group 5) would attract 3,378 trips in the 2010 build scenario.
Figure 75. Station Group Boardings After Adjustment The next set of tables in Section 3 present an assessment of the number of trips added by station factoring. These Tables include
Table 3.05 Group-to-Group Build Unlinked Transit Trips Table 3.06 Group-to-Group Build Unlinked Transit Trips (Trips added by Group Factors) Table 3.07 Group-to-Group Project Unlinked Transit Trips Table 3.08 Station-to-Station Project Unlinked Transit Trips (Trips added by Group
Factors)
105
Federal Transit Administration STOPS v1.50 Users Guide
These tables show the total number of modeled trips and those that were added by the group factoring process for the total Build system and for just those trips that are identified as being project trips.
7.1.4 Summary of Project Results
Section 4 presents the trips on the project made by travelers from all household types using all modes of transit. Table 4.01 presents district-to-district flows (in production/attraction format) for all transit trips in the Build scenario. Table 4.02 presents the number of incremental trips (build no-build) and Table 4.03 presents the district-to-district flows for just those trips that use the project at some point during the journey. As shown in the example, the Madison Street Streetcar will generate 1,427 new transit tips and attract 3,378 trips on the project.
Figure 76. Summary of Project Results
The next table, (Table 4.04 shown in Figure 77) shows the origin (boarding) and destination (alighting) station for project trips. In this sample, only project stations are shown. This happens when (as in this example) all existing stations are coded as NewStation=0 (or blank) and the project itself is coded with NewStation=1. This table will be expanded to include more stations if NewStation is set to 2, 3, or 430.
When stations other than project stations are added to this report, the number of boardings may exceed the total number of linked trips on the project. This happens because project trips may be able to transfer from the project to a connecting station and therefore appear as a station boarding in 2 or more places.
30 Newstation=4 should be used if the only purpose is to cause the station to print on this report since "2" and "3" are used to flag project trips connecting between two existing sections.
106
April 29, 2015
Figure 77. Origin Station to Destination Station Project Flows
Federal Transit Administration STOPS v1.50 User Guide
7.1.5 Summary of Project Results for Trips on Fixed Guideway (FG) Modes
This section provides information similar to that presented in Section 4 except that reported trips are just those that are attracted to the fixed guideway portion of the system.
7.1.6 Summary of Project Results for Trips Made by 0-Car Households
This section provides information similar to that presented in Section 4 except that trips are reported for members of 0-car households only.
7.1.7 Summary of Project Results for Trips on Fixed Guideway (FG) Modes Made by 0-Car Households
This section provides information similar to that presented in Section 4 except that trips are reported for members of 0-car households making trips on the fixed guideway portion of the system.
7.1.8 Summary of Impacts on Automobile Person Miles of Travel
Table 8.01 (see Figure 78) presents the incremental (build minus no-build) estimate of automobile person miles of travel that are a result of the project. These results are displayed on a district-todistrict (production/attraction) basis. This statistic can be converted to vehicle miles of travel saved by the project by using locally-derived estimates of vehicle occupancy to convert person miles to vehicle miles.
107
Federal Transit Administration STOPS v1.50 Users Guide
Figure 78. Incremental Automobile PMT
7.1.9 Comparison of Existing, No-Build and Build Station Boardings by Station Mode of Access
Table 9.01 (shown in Figure 79) shows the station boardings by mode of access for each station in the station database. Boardings are shown for the existing, no-build, and build scenarios. This table represents the mode of access for trips boarding at each station and is the result of the origindestination assignment. For example, a round trip from suburban station A to urban station B where the passenger drives to station A, takes the train to Station B, and walks to work in the morning (and the reverse in the afternoon) would be shown as 1 PNR boarding at Station A (for the morning trip) and 1 walk boarding at Station B for the afternoon trip. The station activity at each station (boardings and alightings) is typically twice as high as the boarding information shown in this table unless travel is highly asymmetrical.
Figure 79. Average Weekday Station Utilization by Scenario and Mode of Access
108
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
7.1.10 Comparison of Existing, No-Build and Build Route Boardings by Route Mode of Access
Section 10 consists of two tables (10.01 and 10.02) which shows usage of each route by productionend mode of access.31 Table 10.01 (shown in Figure 80) presents a condensed table with one line in the report for each route. Table 10.02 presents an expanded table with routes broken out by station groups so that the contribution of each station group to each route can be understood. This capability is important in cases where stations are shared by multiple routes but only some of those routes are of interest to the analysis. Tables 10.03 and 10.04 summarize route-level operating statistics (revenue vehicle miles and vehicle hours) by alternative and analysis time period.
Figure 80. Weekday Route Ridership
7.1.11 Summary of Trips by Submode, Access Mode, Auto Ownership, and Scenario
Section 11 presents a summary of linked transit trips by submode, access mode and auto ownership for each scenario (existing, no-build, and build) and for build trips that are identified as linked trips using the project. Four tables are provided:
Table 11.01: home-based work trips (sample shown in Figure 81) Table 11.02: home-based other trips Table 11.03: non-home based trips All model results (including access mode) are presented in production/attraction format. Linked trips are reported in separate columns for the existing, no-build, and build scenarios. The last set of columns reports project trips which are the defined as any build trips boarding, alighting, or passing through a new station.
31Production-end mode of access is the access mode used to connect home to the first transit station/stop used during the trip. This statistic is in production/attraction format.
109
Federal Transit Administration STOPS v1.50 Users Guide
Figure 81. Summary of Linked Transit Trips by Submode, Access Mode, and Auto Ownership
7.1.12 Summary of CTPP Workers and Employees and MPO Estimates of Population and Employment by Scenario
Table 12.01 (shown in Figure 82) presents a district-level summary of the CTPP and assumed level of population and employment that were used to grow the CTPP to represent current and horizon years. The CTPP columns report the workers (the number of employed persons living in each district) and employment (employed persons working in each district). The MPO columns report the Year 2000 estimates of population and employment that are matched to the CTPP and also show the estimates/forecasts for the existing, no-build, and build scenarios that were used to create the demand tables for each scenario.
110
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 82. Summary of District Level CTPP, Population, and Employment
7.1.13 Summary of Highway Time, Distance and Speed
Section 13 reports highway times, distances and speeds for each district-to-district pair. The following tables are provided:
Table 13.01 Existing scenario, district-to-district highway time (in minutes) Table 13.02 No-build scenario, district-to-district highway time (in minutes) Table 13.03 Build scenario, district-to-district highway time (in minutes) Table 13.04 Existing scenario, district-to-district highway distance (miles) Table 13.05 No-Build scenario, district-to-district highway distance (miles) Table 13.06 Build scenario, district-to-district highway distance (miles) Table 13.07 Existing scenario, district-to-district highway speed (mph) Table 13.08 No-Build scenario, district-to-district highway speed (mph) Table 13.09 Build scenario, district-to-district highway speed (mph) A sample report (existing scenario highway time) is shown in Figure 83.
111
Federal Transit Administration STOPS v1.50 Users Guide
Figure 83. Average Highway Time for Existing Scenario
7.1.14 District to District Analysis of Gains and Losses Between No-Build and Build
Section 14 provides a number of tables that help the user understand the degree to which the project appears to change the level of transit coverage or reduce service to existing customers. Each table shows linked transit trips on a district-to-district basis. The following tables are provided:
Table 14.01. Build Walk Access Transit Trips on Interchanges with Significant Transit Gain (>5%) and Zero No-Build trips. This table shows the number of build transit trips occurring in situations where no one uses transit in the no-build (presumably because no transit is provided). The presence of trips in this category suggests a change in transit service coverage has occurred.
Table 14.02. Build Walk Linked Transit Trips on Interchanges with Significant Transit Gain (>5%) and Non-Zero No-Build trips. This table is the shows cases where transit grows significantly off of a non-zero base. Generally, trips in this table will be located in geographic proximity to the project or other service enhancements. If not, this table may help the user understand where unintended changes were made to the transit system.
Table 14.03 Build Walk Access Linked Transit Trips on Interchanges with Significant Transit Loss (>5%). This table shows the number of build trips occurring in places where the number of transit linked trips declines between the no-build and build scenarios.
Table 14.04 Build Walk Access Linked Transit Trips on Interchanges with no-significant change in transit. This table shows the remaining linked transit trips in the build alternative for cases where the project had little impact on ridership.
Tables 14.05 through 14.08 repeat Tables 14.01-14.04 but shows no-build trips in the same categories.
These eight tables are repeated in Tables 14.09-14.16 for KNR trips, in Tables 14.17-14.24 for PNR trips, and 14.25-14.32 for All Access Mode trips.
112
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
7.1.15 Detailed District-to-District Linked Trips and Selected Station-Station Flows
Section 15 provides a complete set of district-to-district linked trips for each combination of scenario, access mode, auto ownership, trip purpose, and submode. The index provided at the top of the report provides the table number for each condition. For some cases, station-to-station or project trips are also reported.
7.2 Mapping Results
STOPS includes the capability to map many of the results. This option is selected by clicking on "13. Map STOPS Results". When this is done, the dialog shown in Figure 84 appears. The program allows the user to select what types of trips to map including:
Transit sub-modes. Fixed Guideway only, fixed guideway and bus, bus only and all (default) Transit access modes. Walk, kiss-and-ride, park-and-ride, and all (default) Trip purpose: Home-based work, home-based other, non-home based, and all (default) Household auto ownership: 0 car, 1 car, 2+ car and all (default) Production (home) location of trips or attraction (non-home) location Destination district (for Production Plots) or origin district (for attraction plots): Any one
district or all (drop down list with the default of blank meaning all districts) Scenario: existing, no-build, build (map all transit trips associated with the project
scenario), project (map project trips, default), trip gains (increases in linked trips for build vs. no-build), or trip losses (decreases in linked trips for build vs. no-build).
When the defaults are selected, a GIS screen appears showing the origin location for all trips using the project (shown in Figure 85). When a district, a submode, and an access mode are selected, STOPS also displays the travel times to a specific zone in the destination district (the zone in the district definition file where the district label is coded). A sample map showing walk-to-Fixed Guideway Only trips to the CBD is shown in Figure 86. A small black square marks the destination zone for the travel time estimates. Blue, green and gray shading is used to denote travel times that have no bus time as part of the skim. Orange, yellow and red are used to denote travel times that do have bus travel times. Since bus is not part of the Fixed Guideway Only path, no zones are shaded with yellow or red.
113
Federal Transit Administration STOPS v1.50 Users Guide
Figure 84. Dialog for Specifying Map Output Options
Figure 85. Map of Project Trips to All Destinations
114
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
Figure 86. Map of Walk Access Fixed Guideway Only Project Trips to CBD
7.3 Querying Zone-to-Zone Impedances and Trips
Option 14 ("Z2Z Query") allows the user to prepare a report summarizing travel times and trips by mode for a specific zone-to-zone interchange. This information can be entered into the STOPS replicator spreadsheet to show how STOPS estimates the travel demand for a specific interchange. To use the queary function, the user must type a valid zone name in both the "From Zone" and "To" text boxes and then click "14. Z2Z Query." When typing a zone name, remember to zero fill all state and county FIPS codes (SSCCC) and then have another 6 characters (7 characters for block groups) with containing the TAZ, tract or block group. This second part is right justified and is blank filled. Examples:
State 3, county 1, TAZ 123: 03001 123 (3 blanks) State 31, county 37, TAZ 1442: 31037 1442 (2 blanks) State 15, county 12, tract 10001 15012 10001 (1 blank) State 15, county 12, block group 100011: 15012 10001 (1 blank)
115
Federal Transit Administration STOPS v1.50 Users Guide
When the Z2Z Query button is clicked, STOPS will read the datasets that were prepared by the most recent run and report on impedances and times for each combination of:
Scenario (no-build, build, and build) Access mode (walk, kiss-and-ride, and park-and-ride) Path (fixed guideway+bus [all transit path], fixed guideway only, and bus-only)
Sections of this report can be pasted and copied into the STOPS replicated spreadsheet to review the computations made by STOPS to estimate ridership.
116
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
8. PROCEDURES FOR HANDLING LARGE PROBLEMS, BUS PROJECTS, AND UNUSUAL SCHEDULING ISSUES
This section describes procedures for handling large problem, bus projects, and unusual scheduling issues.
8.1 Large Problem Sizes
STOPS is designed to estimate fixed guideway transit trips on a project using data representing travel demand and transportation supply that is available throughout an entire metropolitan area. It was developed and tested for many of the largest cities in the United States including Houston, Denver, Seattle, and San Diego. Some metropolitan areas are larger or have more complex transit services and in these cases, the data storage requirements of STOPS or the execution times may become too large to be practical.
In these circumstances, STOPS can be configured to process only a portion of a metropolitan area. This is done by opening the ESRI shape file for each state in a metropolitan area32 with a GIS application and coding an "XX" in the LSAD field for any zone which should be completely excluded from the STOPS analysis. In some cases, the user may not wish to completely exclude a zone since it serves as a destination for the corridor being modeled. This could happen if STOPS is being used to simulate a suburb-to-central city service and doesn't include calibration information or GTFS schedules for the central transit service. In this case, the user can code "YY" in the LSAD field. These zones will be included in the STOPS modeling region but trips between zones coded with "YY" will not be modeled. These adjustments should be coded prior to running Step 7.
This action can dramatically reduce file sizes and program execution times. If a metropolitan area has 4,000 zones within 25 miles of a fixed guideway station but only 2,000 zones have a noticeable impact on a particular project, then it is possible that file sizes and execution times might be ¼ of file sizes and running times for the full region. This factor presumes that transit services are generally available in all 4,000 zones and that these zones had population, employment and trips in the Year 2000 Census--actual results could show less of an improvement if many of the eliminated zones are empty or are located in areas without transit.
Dropping zones also complicates the process of defining regional unlinked trips (part of the calibration process). Since the exact number of unlinked trips may not be known for the modeled geography, some trial and error may be required to determine the proper value of this input variable. The trial and error process would entail running STOPS with a regional estimate of unlinked trips and then examining station and route-level ridership in the area of the project and then updating the unlinked trip estimate upward or downward until volumes are properly aligned.
32 Files named tzXX_d00_shp.zip (projects with a TZ geography type), bgXX_d00_shp.zip (projects with a BG geography type), or trXX_d00_shp.zip (projects with a TR geography type) where XX is the state FIPS numeric code.
117
Federal Transit Administration STOPS v1.50 Users Guide
8.2 Bus Projects
STOPS is designed to estimate fixed guideway transit trips on a project. As mentioned above, fixed guideway projects (including BRT projects) are generally assumed to involve a series of welldefined stations and the service is perceived as being substantially different from local bus service. In these cases, STOPS users are encouraged to code BRT projects as type 0 (streetcar) to reflect the fact that the BRT is likely to be perceived as being more reliable or faster than conventional bus.
Some BRT projects, however, might not have sufficient differentiation to warrant treatment as a separate type of transit. All STOPS forecasts of project ridership or station-to-station flows show volumes traveling between stops for all transit service types (bus and fixed guideway) not just fixed guideway movements as long as "stations" are defined (with a Newstation flag set to "1") that represent the bus project. This has several important implications for analysis of bus projects:
If existing bus routes serve BRT stations that are with Newstation=1, then existing bus ridership on conventional routes that board, alight or pass through these stations will be reported as being project riders. Consult with FTA staff to determine if this designation is warranted.
A BRT project can be coded as bus (Type 3). Since these routes are included in the bus skims, this will result in ridership forecasts based solely on the performance of the BRT routes as a faster or more frequent version of a local bus rather and exclude any impact of the BRT as a separate service. The treatment may be most appropriate for cases where the BRT service offers well defined stations but does not offer a recognizable right-of-way or other features associated with a fixed guideway service.
118
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
9. APPENDICES
9.1 State FIPS Codes
Table 2. State FIPS Codes
State Name
Numeric
Alpha
FIPS Code FIPS Code
Alabama
1
AL
Alaska
2
AK
Arizona
4
AZ
Arkansas
5
AR
California
6
CA
Colorado
8
CO
Connecticut
9
CT
Delaware
10
DE
District of Columbia
11
DC
Florida
12
FL
Georgia
13
GA
Hawaii
15
HI
Idaho
16
ID
Illinois
17
IL
Indiana
18
IN
Iowa
19
IA
Kansas
20
KS
Kentucky
21
KY
Louisiana
22
LA
Maine
23
ME
Maryland
24
MD
Massachusetts
25
MA
Michigan
26
MI
Minnesota
27
MN
State Name
Missouri Montana Nebraska Nevada New Hampshire New Jersey New Mexico New York North Carolina North Dakota Ohio Oklahoma Oregon Pennsylvania Rhode Island South Carolina South Dakota Tennessee Texas Utah Vermont Virginia Washington West Virginia
Numeric Alpha FIPS Code FIPS Code
29
MO
30
MT
31
NE
32
NV
33
NH
34
NJ
35
NM
36
NY
37
NC
38
ND
39
OH
40
OK
41
OR
42
PA
44
RI
45
SC
46
SD
47
TN
48
TX
49
UT
50
VT
51
VA
53
WA
54
WV
119
Federal Transit Administration STOPS v1.50 Users Guide
State Name Mississippi
Numeric
Alpha
FIPS Code FIPS Code
28
MS
State Name
Wisconsin Wyoming
Numeric Alpha FIPS Code FIPS Code
55
WI
56
WY
9.2 Census MPO Codes
MPO Code
MPO Name
0581 1001 0451 2881 3441 5241 2031 2651 5161 2181 8601 0381 2461 2621 6201 8521 9361 3341 3701 4401 2581 6241 8951 2721 7121 1621 2841 0681 4941 7361 6921 7321 8121
Auburn-Opelika Birmingham RPC Calhoun Area MPO Gadsden-Etowah MPO Huntsville MPO Montgomery Division of Planning North-Central Alabama Regional COG Northwest Alabama COG South Alabama RPC Southeast Wiregrass MPO West Alabama PDC Anchorage MATS Fairbanks MATS Flagstaff MPO Maricopa Association of Governments Pima Association of Governments Yuma MPO Hot Springs MPO Jonesboro MPO Metroplan Northwest AR Regional Planning Commission Southeast AR Regional Planning Commission West Memphis Area Transportation Study Western Arkansas PDD Association of Monterey Bay Area Governments Butte County Association of Governments Council of Fresno County Governments Kern County Council of Governments Merced County Association of Governments Metropolitan Transportation Commission-Oakland Sacramento Area COG San Diego Association of Governments San Joaquin County COG
Area Name
Auburn-Opelika, AL Birmingham, AL Anniston, AL Gadsden, AL Huntsville, AL Montgomery, AL Decatur, AL Florence, AL Mobile, AL Dothan, AL Tuscaloosa, AL Anchorage, AK Fairbanks, AK Flagstaff, AZ Phoenix-Mesa, AZ Tucson, AZ Yuma, AZ Hot Springs, AR Jonesboro, AR Little Rock-North Little Rock, AR Fayetteville-Springdale-Rogers, AR Pine Bluff, AR West Memphis, AR Fort Smith, AR-OK Salinas, CA Chico-Paradise, CA Fresno, CA Bakersfield, CA Merced, CA San Francisco-Oakland-San Jose, CA Sacramento-Yolo, CA San Diego, CA Stockton-Lodi, CA
120
April 29, 2015
MPO Code 7461 7481 6691 4471 5171 8781 2081 2996 2671 1721 6561 0910 0909 0905 0912 0907 0902 0904 0911 0915 0903 0908 0901 0913 0906 0914 2191 9161 8841 4901 2681 6581 5346 8281 3601 2751 2901 8701 2701 8131
MPO Name
San Luis Obispo Council of Governments Santa Barbara County Association of Governments Shasta County RTPA Southern CA Association of Governments Stanislaus council of Governments Tulare County Association of Governments Denver Regional COG Grand Valley MPO North Front Range MPO Pikes Peak Area COG Pueblo Area Council of Governments Capitol Region COG Central Connecticut RPA Central Naugatuck Valley COG Connecticut River Estuary RPA Greater Bridgeport / Valley MPO Housatonic Valley Council of Elected Officials Litchfield Hills Council of Elected Officials Midstate Regional Planning Agency Northeastern Connecticut COG Northwestern Connecticut COG South Central Region COG South Western Regional Planning Agency Southeastern Connecticut COG Valley Regional Planning Agency Windham Regional Planning Agency Dover/Kent County MPO Wilmington Area Planning Council Metropolitan Washington COG Brevard County MPO Broward County MPO Charlotte County - Punta Gorda MPO Collier County MPO District 7 FDOT First Coast MPO Okaloosa-Walton TPO Gainesville Urbanized Area MPO Indian River County MPO Lee County MPO Martin County MPO
Federal Transit Administration STOPS v1.50 User Guide
Area Name
San Luis Obispo-Atascadero-Paso Robles, CA Santa Barbara-Santa Maria-Lompoc, CA Redding, CA Los Angeles-Riverside-Orange County, CA Modesto, CA Visalia-Tulare-Porterville, CA Denver-Boulder-Greeley, CO Grand Junction, CO Fort Collins-Loveland, CO Colorado Springs, CO Pueblo, CO Hartford, CT Brisol, CT Waterbury, CT Old Saybrook, CT Bridgeport, CT Danbury, CT Torrington, CT Middletown, CT Putnam, CT Warren, CT New Haven, CT Stamford-Norwalk, CT New London-Norwich, CT Derby-Shelton, CT Willimantic, CT Dover, DE Wilmington-Newark, DE-MD Washington, DC-MD-VA Melbourne-Titusville-Palm Bay, FL Fort Lauderdale, FL Punta Gorda, FL Naples, FL Tampa-St. Petersburg-Clearwater, FL Jacksonville, FL Fort Walton Beach, FL Gainesville, FL Vero Beach, FL Fort Myers-Cape Coral, FL Stuart, FL
121
Federal Transit Administration STOPS v1.50 Users Guide
MPO Code 5961 5001 5791 8961 6016 6081 3981 7511 2711 8241 2021 0121 0501 0521 0601 7521 1801 1251 4681 6911 8821 3321 6341 3461 1081 1961 1401 1601 3741 2041 1041 6881 7881 6121 3921 1021 5281 2441 3481 3851
MPO Name
Area Name
Metroplan Orlando Miami-Dade Metropolitan Planning Organization Ocala-Marion County MPO Palm Beach County MPO Panama City MPO Pensacola MPO Polk Transportation Planning Organization Sarasota-Manatee MPO St. Lucie MPO Tallahassee-Leon County MPO Volusia County MPO Albany Dougherty County Planning Commission Athens-Clarke County MPO Atlanta Regional Commission Augusta Richmond County PC Chatham County-Savannah Metropolitan Planning Comm. Columbus-Phenix City Transportation Study Brunswick Area Transportation Study Macon Area Transportation Study Rome-Floyd County Planning Commission Warner Robins MPO Oahu Metropolitan Planning Organization Bannock Planning Organization Bonneville MPO Community Planning Association of Southwest Idaho Bi-State Regional Commission Champaign County RPC Chicago Area Transportation Study Kankakee County RPC Macon County RPC McLean County RPC Rockford Area Transportation Study Springfield-Sangamon County RPC Tri-County Regional Planning Commission--IL Tippecanoe County Area Planning Commission Bloomington Area Transportation Study Delaware-Muncie MPC Evansville Urban Transportation Study Indianapolis MPO Kokomo-Howard County Governmental Coordinating
Orlando, FL Miami, FL Ocala, FL West Palm Beach-Boca Raton, FL Panama City, FL Pensacola, FL Lakeland-Winter Haven, FL Sarasota-Bradenton, FL Fort Pierce-Port St. Lucie, FL Tallahassee, FL Daytona Beach, FL Albany, GA Athens, GA Atlanta, GA Augusta-Aiken, GA-SC Savannah, GA Columbus, GA-AL Brunswick GA Macon, GA Rome, GA Warner Robins, GA Honolulu, HI Pocatello, ID Idaho Falls,ID Boise City, ID Davenport-Moline-Rock Island, IA-IL Champaign-Urbana, IL Chicago, IL Kankakee, IL Decatur, IL Bloomington-Normal, IL Rockford, IL Springfield, IL Peoria-Pekin, IL Lafayette, IN Bloomington-Normal, IN Muncie, IN Evansville-Henderson, IN-KY Indianapolis, IN Kokomo, IN
122
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
MPO Code
0401 7801 2761 2961 8321 8921 2121 2201 3501 1361 7721 4151 8441 9041 1141 3411 5991 4521 4281 0761 3961 3881 5561 7681 5201 0221 3351 4241 0731 6401 7471 0721 1901 3181 6321 1121 0741 9241 1126
MPO Name
Area Name
Council Madison County COG Michiana Area Council of Governments Northeastern Indiana Reg. Coordinating Council
Northwestern Indiana RPC
West Central Indiana Economic Development District Black Hawk Metropolitan Area Transportation Policy Board Des Moines Area MPO Dubuque Metropolitan Area Transportation Study Johnson County COG Linn County Reg. Planning Commission Siouxland Interstate Metropolitan Planning Council Lawrence-Douglas MPO Topeka-Shawnee County MPO Wichita-Sedgewick County MPO Bowling Green-Warren County Ashland Urbanized Area Green River Area Development District Kentuckiana Reg. Planning and Development Agency Lexington-Fayette Urban County Government Capital Region Planning Commission Imperial Calcasieu Regional Planning & Dev. Commission Lafayette City - Parish Consolidated Government New Orleans RPC Northwest Louisiana COG Ouachita Council of Governments Rapides Area Planning Commission Houma-Thibodaux MPO Androscoggin Transportation Resource Center Bangor Area Comprehensive Transportation System Greater Portland COG Southern Maine RPC Baltimore Metropolitan Council Cumberland Urbanized Area Hagerstown-Eastern Panhandle MPO Berkshire County Regional Planning Commission Boston MPO Cape Cod Commission Central Massachusetts RPC Central Transportation Planning
Anderson, IN South Bend, IN Fort Wayne, IN Gary, IN Terre Haute, IN Waterloo-Cedar Falls, IA Des Moines, IA Dubuque, IA Iowa City, IA Cedar Rapids, IA Sioux City, IA-NE Lawrence, KS Topeka, KS Wichita, KS Bowling Green, KY Ashland, KY Owensboro, KY Louisville, KY-IN Lexington, KY Baton Rouge, LA Lake Charles, LA Lafayette, LA New Orleans, LA Shreveport-Bossier City, LA Monroe, LA Alexandria, LA Houma, LA Lewiston-Auburn, ME Bangor, ME Portland, ME Sanford, ME Baltimore, MD Cumberland, MD-WV Hagerstown, MD Pittsfield, MA Boston, MA Barnstable-Yarmouth, MA Worcester, MA Boston metro, MA
123
Federal Transit Administration STOPS v1.50 Users Guide
MPO Code 3101 4861 4161 2601 5301 4561 1201 8001 2481 0781 0801 2641 3001 3721 3311 3521 6961 2161 0871 4041 5291 2241 5121 6821 6981 3561 0921 3286 1741 7041 3711 3761 7921 7001 3041 5141 0881 4361 5921 4121
MPO Name
Franklin Regional COG Marthas Vineyard Commission Merrimack Valley Planning Commission Montachusett RPC Nantucket Planning and Economic Devp. Commission Northern Middlesex COG Old Colony Planning Council Pioneer Valley Planning Commission Southeastern Regional Planning and Economic Dev. Battle Creek Area Transportation Study Bay City Area Transportation Study Genesse County MPO Grand Valley Metropolitan Council Kalamazoo Area Transportation Study Macatawa Area Coordinating Council Region 2 Planning Commission Saginaw Co Metro Planning Commission Southeast Michigan COG Southwestern Michigan Commission Tri-County RPC--MI West Michigan Shoreline RDC Arrowhead Regional Development Commission Metropolitan Council of the Twin Cities Area Rochester-Olmsted COG St. Cloud Area Planning Organization Central Mississippi Planning and Development District Gulf Regional Planning Commission Hattiesburg-Petal-Forrest-Lamar MPO Columbia Area Transportation Study East-West Gateway Coordinating Council Joplin Area Transportation Study Organization Mid-America Regional Council Springfield Area Transportation Study Org. St. Joseph Area Transportation Study Organization Great Falls City-County Planning Board Missoula Transportation Policy Coordinating Commit Yellowstone County Board of Planning Lincoln-Lancaster MPO Omaha-Council Bluffs Metro Area Planning Agency Southern Nevada RTC
Area Name
Greenfield, MA Martha's Vineyard, MA Lawrence, MA Fitchburg-Leominster, MA Nantucket, MA Lowell, MA Brockton, MA Springfield, MA Fall River, MA Battle Creek, MI Bay City, MI Flint, MI Grand Rapids, MI Kalamazoo, MI Holland, MI Jackson, MI Saginaw-Bay City-Midland, MI Detroit-Ann Arbor, MI Benton Harbor, MI Lansing-East Lansing, MI Muskegon, MI Duluth-Superior, MN-WI Minneapolis-St. Paul, MN-WI Rochester, MN St. Cloud, MN Jackson, MS Biloxi-Gulfport-Pascagoula, MS Hattiesburg, MS Columbia, MO St. Louis, MO-IL Joplin, MO Kansas City, MO-KS Springfield, MO St. Joseph, MO Great Falls, MT Missoula, MT Billings, MT Lincoln, NE Omaha, NE-IA Las Vegas, NV-AZ
124
April 29, 2015
MPO Code 9371 6721 5351 7061 6451 4761 5641 0561 4101 0201 7491 2976 0961 0161 2336 6841 1281 8681 3511 3836 5601 5661 2281 8161 0481 3111 1861 6641 3606 2261 2561 2966 2981 3121 3151 3291 1521 6896 3301 9181
MPO Name
Tahoe MPO Washoe County RTC Nashua Regional Planning Commission Salem/Plaistow MPO Sea Coast MPO Southern NH Planning Commission North Jersey Transportation Planning Authority South Jersey Transportation Planning Organization Las Cruces MPO Mid Region MPO Santa Fe MPO Adirondack-Glens Falls Transportation Council Binghamton Metropolitan Transportation Study Capital District Transportation Committee Elmira-Chemung Transportation Committee Genesee Transportation Council Greater Buffalo Niagara Transportation Commission Herkimer-Oneida Counties Transportation Study Ithaca-Tompkins County Transportation Council Kingston MPO New York Metropolitan Transportation Council Newburgh/Orange County Transportation Council Poughkeepsie-Dutchess County Transportation Council Syracuse Metropolitan Transportation Council Asheville Urban Area MPO Burlington-Graham MPO Cabarrus-South Rowan MPO Capital Area MPO City of Jacksonville Durham-Chapel Hill-Carrboro MPO Fayetteville Area Metropolitan Planning Organization Gaston Urban Area MPO Goldsboro Urbanized Area MPO Greensboro Urban Area MPO Greenville Urban Area MPO Hickory-Newton-Conover MPO Mecklenburg-Union MPO Rocky Mount Urban Area MPO High Point Urban Area MPO Wilmington Urban Area MPO
Federal Transit Administration STOPS v1.50 User Guide
Area Name
Zephyr Cove, NV Reno, NV Nashua, NH Salem, NH Portsmouth-Rochester, NH-ME Manchester, NH Newark, NJ Atlantic-Cape May, NJ Las Cruces, NM Albuquerque, NM Santa Fe, NM Glens Falls, NY Binghamton, NY Albany-Schenectady-Troy, NY Elmira, NY Rochester, NY Buffalo-Niagara Falls, NY Utica-Rome, NY Ithaca, NY Kingston, NY New York, NY Newburgh, NY-PA Dutchess County, NY Syracuse, NY Asheville, NC Burlington, NC Concord, NC Raleigh, NC Jacksonville, NC Durham-Chapel Hill, NC Fayetteville, NC Gastonia, NC Goldsboro, NC Greensboro, NC Greenville, NC Hickory-Morganton-Lenoir, NC Charlotte, NC Rocky Mount, NC High Point, NC Wilmington, NC
125
Federal Transit Administration STOPS v1.50 Users Guide
MPO Code 9201 1011 2521 2986 0081 8081 8011
9321 5651 4321 2001 1841 1681 1641 4801 1321 8401 5881 8561 4201 2401 6441 7081 4991 0281 3681 8051 6161 2361 7561 4001 5401 0241 9141 7611 6681 6281 3241 9281
MPO Name
Winston Salem/Forsyth County MPO Bismarck-Mandan MPO Fargo-Moorhead Metropolitan COG Grand Forks-East Grand Forks MPO Akron Metropolitan Area Transportation Study Brooke-Hancock-Jefferson Metropolitan Planning Com Clark County-Springfield Transportation Coordinating Committee Eastgate Regional COG Licking County Area Transportation Study Lima-Allen County RPC Miami Valley Regional Planning Commission Mid-Ohio RPC Northeast Ohio Areawide Coordinating Agency Ohio-Kentucky-Indiana Regional COG Richland County RPC Stark County Area Transportation Study Toledo Metropolitan Area COG Association of Central Oklahoma Governments Indian Nations COG Lawton Metropolitan Area PC Lane Council of Governments Metro Salem Keizer Area Transportation Study Rogue Valley COG Blair County Planning Commission Cambria County Planning Commission Centre Region MPO Delaware Valley Regional Planning Commission Erie MPO Lackawanna-Luzerne Transportation Study Lancaster County Transportation Coordinating Committee Lawrence County Planning Department Lehigh Valley Transportation Study Lycoming County Planning Commission Shenango Valley Area Transportation Study Reading Area Transportation Study Southwestern Pennsylvania Commission Harrisburg Area Transportation Study York County Planning Commission
Area Name
Winston-Salem, NC Bismarck, ND Fargo-Moorhead, ND-MN Grand Forks, ND-MN Akron, OH Steubenville-Weirton, OH-WV Springfield, OH
Youngstown-Warren, OH Newark, OH Lima, OH Dayton, OH Columbus, OH Cleveland, OH Cincinnati-Hamilton, OH-KY-IN Mansfield, OH Canton-Massillon, OH Toledo, OH Oklahoma City, OK Tulsa, OK Lawton, OK Eugene-Springfield, OR Portland, OR Salem, OR Medford-Ashland, OR Altoona, PA Johnstown, PA State College, PA Philadelphia-Wilmington-Atlantic City, PA-NJ-DE-MD Erie, PA Scranton--Wilkes-Barre--Hazleton, PA Lancaster, PA New Castle, PA Allentown-Bethlehem-Easton, PA Williamsport, PA Sharon, PA Reading, PA Pittsburgh, PA Harrisburg-Lebanon-Carlisle, PA York, PA
126
April 29, 2015
MPO Code 6481 0406 1761 1441 2656 3161 6861 7821 8141 2971 6661 7761 1161 1561 1661 3581 3661 3831 3841 4921 5361 0041 0321 1241 1261 0641 1881 2321 3201 4881 3361 3811 4081 4421 4601 1921 5801 7201 7241 0841
MPO Name
RI Statewide Planning Program Anderson MPO Central Midlands COG Charleston Area Transportation Study Florence Area Transportation Study Greenville Area Transportation Study Rock Hill-Fort Mill Area Trans. Study Policy Spartanburg Area Transportation Study Sumter Area Transportation Study Waccamaw RPC Rapid City Area MPO Sioux Falls MPO Bristol Urban Area MPO Chattanooga Urban Area MPO Clarksville Urban Area MPO Jackson MPO Johnson City MPO Kingsport Urban Area MPO Knoxville MPO Memphis MPO Nashville Area MPO Abilene MPO Amarillo MPO Brownsville MPO Bryan-College Station MPO Capital Area MPO Corpus Christi MPO El Paso MPO Harlingen-San Benito MPO Hidalgo County MPO Houston-Galveston Area Council Killeen-Temple Urban Transportation Study Laredo Urban Transportation Study Longview MPO Lubbock MPO North Central Texas COG Permian Basin RPC San Angelo MPO San Antonio-Bexar County MPO South East Texas Regional Planning Commission
Federal Transit Administration STOPS v1.50 User Guide
Area Name
Providence, RI Anderson, SC Columbia, SC Charleston, SC Florence, SC Greenville, SC Rock Hill, SC Spartanburg, SC Sumter, SC Georgetown, SC Rapid City, SD Sioux Falls, SD Bristol, TN Chattanooga, TN-GA Clarksville-Hopkinsville, TN-KY Jackson, TN Johnson City, TN Kingsport, TN Knoxville, TN Memphis, TN-AR-MS Nashville, TN Abilene, TX Amarillo, TX Brownsville, TX Bryan-College Station, TX Austin-San Marcos, TX Corpus Christi, TX El Paso, TX Harlingen-San Benito, TX McAllen-Edinburg-Mission, TX Houston-Galveston, TX Killeen-Temple, TX Laredo, TX Longview-Marshall, TX Lubbock, TX Dallas-Fort Worth, TX Odessa-Midland, TX San Angelo, TX San Antonio, TX Beaumont-Port Arthur, TX
127
Federal Transit Administration STOPS v1.50 Users Guide
MPO Code 7641 8641 8751 8801 9081 8361 4411 6971 6521 7161 1306 6141 5721 2801 4641 6761 6801 1541 1951 6741 4416 7601 5261 8691 7841 5911 8946 0861 9261 9001 3401 5251 1481 6021 3081 3086 0461 3621 3871 4721
MPO Name
Sherman Denison MPO Tyler MPO Victoria MPO Waco MPO Wichita Falls MPO Texarkana MPO Cache MPO Dixie MPO Mountainland Association of Governments Wasatch Front Regional Council Chittenden County MPO Crater Planning District Commission Hampton Roads Planning District Commission Fredericksburg Area MPO Central Virginia MPO Richmond Regional Planning District Commission Roanoke Valley Area MPO Thomas Jefferson Planning District Commission West Piedmont Planning District Commission Benton-Franklin COG Longview-Kelso-Rainier MPO Puget Sound Regional Council Skagit COG Southwest Washington Regional Transportation Council Spokane Regional Transportation Council Thurston Regional Planning Council Wenatchee Valley Transportation Council Whatcom COG Yakima Valley COG Bel-O-Mar Regional Council KYOVA Interstate Planning Commission Morgantown, WV MPO Regional Intergovernmental Council WWW Interstate Planning Commission Bay-Lake Regional Planning Commission Brown County Planning Commission East Central Wisconsin Regional Planning Commission Janesville Area Transportation Study La Crosse Area Planning Committee Madison Area MPO
Area Name
Sherman-Denison, TX Tyler, TX Victoria, TX Waco, TX Wichita Falls, TX Texarkana, TX-Texarkana, AR Logan, UT St George, UT Provo-Orem, UT Salt Lake City-Ogden, UT Burlington, VT Petersburg, VA Norfolk-Virginia Beach-Newport News, VA-NC Fredericksburg, VA Lynchburg, VA Richmond, VA Roanoke, VA Charlottesville, VA Danville, VA Richland-Kennewick-Pasco, WA Longview, WA Seattle-Tacoma-Bremerton, WA Mount Vernon, WA Vancouver, WA Spokane, WA Olympia, WA Wenatchee, WA Bellingham, WA Yakima, WA Wheeling, WV-OH Huntington, WV Morgantown, WV Charleston, WV Parkersburg-Marietta, WV-OH Sheboygan, WI Green Bay, WI Appleton-Oshkosh-Neenah, WI Janesville, WI La Crosse, WI-MN Madison, WI
128
April 29, 2015
MPO Code 8941 5081 0866 2291 1351 1581
MPO Name
Marathon County Metro Planning Commission South East Wisconsin Regional Planning Commission Stateline Area Transportation Study West Central Wisconsin RPC Casper Area Transportation Planning Process Cheyenne Area Transportation Planning Process
Federal Transit Administration STOPS v1.50 User Guide
Area Name
Wausau, WI Milwaukee-Racine, WI Beloit, WI Eau Claire, WI Casper, WY Cheyenne, WY
129
Federal Transit Administration STOPS v1.50 Users Guide
9.3
State
Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alabama Alaska Alaska Arizona Arizona Arizona Arizona Arizona Arizona Arizona Arkansas Arkansas Arkansas Arkansas
MPO Geography Types by County
FIPS STCOU FIPS MCD
MPO Name
01081 01073 01117 01015 01121 01081 01113 01015 01055 01083 01089 01001 01051 01101 01043 01079 01083 01103 01033 01077 01097 01045 01067 01069 01125 02020 02090 04005 04013 04021 04025 04019 04021 04027 05051 05059 05031 05023
Auburn-Opelika Birmingham RPC Birmingham RPC Calhoun Area MPO Calhoun Area MPO Columbus-Phenix City Transportation Study Columbus-Phenix City Transportation Study Gadsen-Etowah MPO Gadsen-Etowah MPO Huntsville MPO Huntsville MPO Montgomery Division of Planning Montgomery Division of Planning Montgomery Division of Planning North Central Alabama Regional COG North Central Alabama Regional COG North Central Alabama Regional COG North Central Alabama Regional COG Northwest Alabama COG Northwest Alabama COG South Alabama RPC Southeast Wiregrass Area MPO Southeast Wiregrass Area MPO Southeast Wiregrass Area MPO West Alabama PDC Anchorage MATS Fairbanks MATS Flagstaff MPO Maricopa Assn. Of Gov. Maricopa Assn. Of Gov. Maricopa Assn. Of Gov. Pima Assn. Of Gov. Pima Assn. Of Gov. Yuma MPO Hot Springs MPO Hot Springs MPO Jonesboro MPO Metroplan
MPO
MPO
Code Geography
0581 1001 1001 0451 0451 1801 1801 2881 2881 3441 3441 5241 5241 5241 2031 2031 2031 2031 2651 2651 5161 2181 2181 2181 8601 0381 2461 2621 6201 6201 6201 8521 8521 9361 3341 3341 3701 4401
TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG BG BG TAZ BG BG BG BG BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG BG TAZ TAZ TAZ TAZ TAZ Tract BG BG BG BG
130
April 29, 2015
State
Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas Arkansas California California California California California California California California California California California California California California California California California California California
Federal Transit Administration STOPS v1.50 User Guide
FIPS STCOU FIPS MCD
MPO Name
05029 05045 05053 05059 05085 05105 05117 05119 05125 05141 05145 05007 05015 05087 05143 05025 05069 05091 05035 05033 05131 06001 06047 06053 06069 06079 06081 06085 06087 06007 06019 06029 06047 06001 06013 06041 06055 06075 06081 06085
Metroplan Metroplan Metroplan Metroplan Metroplan Metroplan Metroplan Metroplan Metroplan Metroplan Metroplan Northwest Arkansas RPC Northwest Arkansas RPC Northwest Arkansas RPC Northwest Arkansas RPC Southeast Arkansas RPC Southeast Arkansas RPC Texarkana MPO West Memphis MPO Western Arkansas PDD Western Arkansas PDD Association of Monterey Bay Area Governments Association of Monterey Bay Area Governments Association of Monterey Bay Area Governments Association of Monterey Bay Area Governments Association of Monterey Bay Area Governments Association of Monterey Bay Area Governments Association of Monterey Bay Area Governments Association of Monterey Bay Area Governments Butte County Association of Governments Council of Fresno County Governments Kern County Council of Governments Merced County Association of Governments Metropolitan Transportation Commission-Oakland Metropolitan Transportation Commission-Oakland Metropolitan Transportation Commission-Oakland Metropolitan Transportation Commission-Oakland Metropolitan Transportation Commission-Oakland Metropolitan Transportation Commission-Oakland Metropolitan Transportation Commission-Oakland
MPO
MPO
Code Geography
4401 BG 4401 BG 4401 BG 4401 BG 4401 BG 4401 BG 4401 BG 4401 BG 4401 BG 4401 BG 4401 BG 2581 BG 2581 BG 2581 BG 2581 BG 6241 BG 6241 BG 8361 TAZ 8951 BG 2721 TAZ 2721 TAZ 7121 BG 7121 BG 7121 BG 7121 BG 7121 BG 7121 BG 7121 BG 7121 BG 1621 TAZ 2841 TAZ 0681 TAZ 4941 TAZ 7361 TAZ 7361 TAZ 7361 TAZ 7361 TAZ 7361 TAZ 7361 TAZ 7361 TAZ
131
Federal Transit Administration STOPS v1.50 Users Guide
State
California California California California California California California California California California California California California California California California California California California California California California California California California California Colorado Colorado Colorado Colorado Colorado Colorado Colorado Colorado Colorado Colorado Colorado Colorado Colorado Colorado
FIPS STCOU FIPS MCD
MPO Name
MPO
MPO
Code Geography
06095 06097 06017 06061 06067 06101 06113 06115 06073 06077 06079 06083 06089 06025 06037 06059 06065 06071 06111 06099 06017 06061 06019 06029 06031 06107 08001 08005 08013 08019 08031 08035 08039 08047 08059 08093 08123 08077 08013 08069
Metropolitan Transportation Commission-Oakland 7361 TAZ
Metropolitan Transportation Commission-Oakland 7361 TAZ
Sacramento Area COG
6921 TAZ
Sacramento Area COG
6921 TAZ
Sacramento Area COG
6921 TAZ
Sacramento Area COG
6921 TAZ
Sacramento Area COG
6921 TAZ
Sacramento Area COG
6921 TAZ
San Diego Association of Governments
7321 TAZ
San Joaquin County COG
8121 TAZ
San Luis Obispo COG
7461 TAZ
Santa Barbara County Association of Governments 7481 TAZ
Shasta County RTPA
6691 BG
Southern CA Association of Governments
4471 BG
Southern CA Association of Governments
4471 BG
Southern CA Association of Governments
4471 BG
Southern CA Association of Governments
4471 BG
Southern CA Association of Governments
4471 BG
Southern CA Association of Governments
4471 BG
Stanislaus COG
5171 TAZ
Tahoe MPO
9371 BG
Tahoe MPO
9371 BG
Tulare County Association of Governments
8781 BG
Tulare County Association of Governments
8781 BG
Tulare County Association of Governments
8781 BG
Tulare County Association of Governments
8781 BG
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 TAZ
Denver Regional COG
2081 BG
Denver Regional COG
2081 TAZ
Grand Valley MPO
2996 TAZ
North Front Range MPO
2671 BG
North Front Range MPO
2671 BG
132
April 29, 2015
State
FIPS STCOU FIPS MCD
MPO Name
Colorado Colorado Colorado Colorado Colorado Connecticut
Delaware Delaware Delaware Delaware Washington,
DC Washington,
DC Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida
08123 08041 08093 08119 08101 New England states are shown at the end of this file 10003 10001 10005 10003 11001
11001
12009 12011 12015 12027 12071 12115 12021 12017 12053 12057 12081 12083 12101 12103 12105 12031 12001 12061 12015 12021 12071 12085 12111 12095
North Front Range MPO Pikes Peak Area COG Pikes Peak Area COG Pikes Peak Area COG Pueblo Area Council of Governments
Delaware Valley RPC Dover/Kent Co MPO Dover/Kent Co MPO Wilmington Planning Council Metropolitan Washington COG
Baltimore Metropolitan Council
Brevard MPO Broward County MPO Charlotte County-Punta Gorda MPO Charlotte County-Punta Gorda MPO Charlotte County-Punta Gorda MPO Charlotte County-Punta Gorda MPO Collier County MPO District 7 FDOT District 7 FDOT District 7 FDOT District 7 FDOT District 7 FDOT District 7 FDOT District 7 FDOT District 7 FDOT First Coast MPO Gainesville Urbanized Area MPO Indian River County MPO Lee County MPO Lee County MPO Lee County MPO Martin County MPO Martin County MPO Metroplan Orlando
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
2671 BG 1721 TAZ 1721 BG 1721 BG 6561 TAZ
6161 2191 2191 9161 8841
Tract BG BG BG TAZ
0721 Tract
4901 2681 6581 6581 6581 6581 5346 8281 8281 8281 8281 8281 8281 8281 8281 3601 2901 8701 2701 2701 2701 8131 8131 5961
TAZ TAZ TAZ Tract TAZ TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG BG BG
133
Federal Transit Administration STOPS v1.50 Users Guide
State
Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Florida Georgia Georgia Georgia
Georgia
Georgia
Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia
FIPS STCOU FIPS MCD
MPO Name
12097 12117 12086 12083 12091 12131 12099 12005 12033 12113 12105 12081 12115 12111 12073 12035 12127 13095 13177 13059
13195
13219
13013 13015 13035 13045 13057 13063 13067 13077 13085 13089 13097 13113 13117 13121 13135 13139
Metroplan Orlando Metroplan Orlando Miami-Dade MPO Ocala-Marion County MPO Okaloosa-Walton TPO Okaloosa-Walton TPO Palm Beach County MPO Panama City MPO Pensacola MPO Pensacola MPO Polk TPO Sarasota-Manatee MPO Sarasota-Manatee MPO St. Lucie MPO Tallahassee-Leon County MPO Volusia County MPO Volusia County MPO Albany Dougherty Regional Transportation Study Albany Dougherty Regional Transportation Study Athens Clarke Oconee Regional Transportation Study Athens Clarke Oconee Regional Transportation Study Athens Clarke Oconee Regional Transportation Study Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission
MPO
MPO
Code Geography
5961 BG 5961 BG 5001 BG 5791 TAZ 2751 TAZ 2751 TAZ 8961 TAZ 6016 TAZ 6081 TAZ 6081 TAZ 3981 BG 7511 TAZ 7511 TAZ 2711 BG 8241 TAZ 2021 BG 2021 BG 0121 TAZ 0121 TAZ 0501 TAZ
0501 Tract
0501 TAZ
0521 BG 0521 TAZ 0521 BG 0521 BG 0521 TAZ 0521 TAZ 0521 TAZ 0521 TAZ 0521 BG 0521 TAZ 0521 TAZ 0521 TAZ 0521 TAZ 0521 TAZ 0521 TAZ 0521 BG
134
April 29, 2015
State
Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Georgia Hawaii
Idaho Idaho Idaho Idaho Idaho Idaho Idaho
Federal Transit Administration STOPS v1.50 User Guide
FIPS STCOU FIPS MCD
MPO Name
13143 13149 13151 13157 13159 13171 13199 13217 13223 13227 13231 13233 13247 13255 13285 13293 13297 13073 13245 13127 13029 13051 13103 13047 13083 13295 13215 13021 13169 13115 13153 13225 15003 16005 16077 16019 16001 16015 16027 16039
Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Atlanta Regional Commission Augusta Richmond County PC Augusta Richmond County PC Brunswick Area Transportation Study Chatham County-Savannah MPC Chatham County-Savannah MPC Chatham County-Savannah MPC Chattanooga Urban Area MPO Chattanooga Urban Area MPO Chattanooga Urban Area MPO Columbus-Phenix City Transportation Study Macon Area Transportation Study Macon Area Transportation Study Rome-Floyd County PC Warner Robins MPO Warner Robins MPO Oahu MPO Bannock Planning Organization Bannock Planning Organization Bonneville MPO Community Planning Assoc. of Southwest Idaho Community Planning Assoc. of Southwest Idaho Community Planning Assoc. of Southwest Idaho Community Planning Assoc. of Southwest Idaho
MPO
MPO
Code Geography
0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0521 0601 0601 1251 7521 7521 7521 1561 1561 1561 1801 4681 4681 6911 8821 8821 3321 6341 6341 3461 1081 1081 1081 1081
Tract Tract TAZ BG Tract Tract Tract BG TAZ BG Tract Tract TAZ BG Tract Tract BG TAZ TAZ BG BG TAZ BG BG BG BG TAZ TAZ TAZ BG TAZ TAZ BG BG BG TAZ TAZ Tract TAZ Tract
135
Federal Transit Administration STOPS v1.50 Users Guide
State
Idaho Idaho Idaho Idaho Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois
FIPS STCOU FIPS MCD
MPO Name
16045 16073 16075 16055 17073 17131 17161 17019 17007 17031 17037 17043 17063 17089 17091 17093 17097 17099 17111 17197 17201 17085 17119 17133 17163 17091 17115 17113 17031 17037 17043 17063 17089 17091 17093 17097 17111 17197 17007 17037
Community Planning Assoc. of Southwest Idaho Community Planning Assoc. of Southwest Idaho Community Planning Assoc. of Southwest Idaho Spokane RTC Bi-State Regional Commission Bi-State Regional Commission Bi-State Regional Commission Champaign County RPC Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Dubuque MATS East-West Gateway Coordinating Council East-West Gateway Coordinating Council East-West Gateway Coordinating Council Kankakee County RPC Macon County RPC McLean County RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Rockford Area Transportation Study Rockford Area Transportation Study
MPO
MPO
Code Geography
1081 1081 1081 7841 1961 1961 1961 1401 1601 1601 1601 1601 1601 1601 1601 1601 1601 1601 1601 1601 1601 2201 7041 7041 7041 3741 2041 1041 2961 2961 2961 2961 2961 2961 2961 2961 2961 2961 6881 6881
Tract Tract Tract BG TAZ TAZ TAZ TAZ TAZ TAZ Tract TAZ TAZ TAZ TAZ TAZ TAZ Tract TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG
136
April 29, 2015
State
Illinois Illinois Illinois Illinois Illinois Illinois Illinois Illinois Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana
Indiana
Indiana
Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana
Federal Transit Administration STOPS v1.50 User Guide
FIPS STCOU FIPS MCD
MPO Name
17141 17177 17201 17167 17201 17143 17179 17203 18105 18089 18127 18035 18135 18051 18129 18163 18173 18011 18057 18059 18063 18081 18097 18109 18145 18019
18043
18067
18095 18039 18049 18085 18087 18091 18099 18113 18131 18141
Rockford Area Transportation Study Rockford Area Transportation Study Rockford Area Transportation Study Springfield-Sangamon County RPC Stateline Area Transportation Study Tri-County Regional Planning Commission Tri-County Regional Planning Commission Tri-County Regional Planning Commission Bloomington Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Delaware-Muncie MPC Delaware-Muncie MPC Evansville Urban Transportation Study Evansville Urban Transportation Study Evansville Urban Transportation Study Evansville Urban Transportation Study Indianapolis MPO Indianapolis MPO Indianapolis MPO Indianapolis MPO Indianapolis MPO Indianapolis MPO Indianapolis MPO Indianapolis MPO Kentuckiana Regional Planning and Development Agency Kentuckiana Regional Planning and Development Agency Kokomo-Howard County Governmental Coordinating Council Madison County COG Michiana Area COG Michiana Area COG Michiana Area COG Michiana Area COG Michiana Area COG Michiana Area COG Michiana Area COG Michiana Area COG Michiana Area COG
MPO
MPO
Code Geography
6881 BG 6881 BG 6881 TAZ 7881 TAZ 0866 TAZ 6121 TAZ 6121 TAZ 6121 TAZ 1021 BG 1601 TAZ 1601 TAZ 5281 TAZ 5281 BG 2441 TAZ 2441 TAZ 2441 TAZ 2441 TAZ 3481 TAZ 3481 TAZ 3481 TAZ 3481 TAZ 3481 TAZ 3481 TAZ 3481 TAZ 3481 TAZ 4521 TAZ
4521 TAZ
3851 TAZ
0401 BG 7801 TAZ 7801 BG 7801 TAZ 7801 BG 7801 TAZ 7801 TAZ 7801 TAZ 7801 BG 7801 TAZ
137
Federal Transit Administration STOPS v1.50 Users Guide
State
Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana Indiana
Iowa Iowa Iowa
Iowa
Iowa
Iowa
Iowa
Iowa
Iowa Iowa Iowa
FIPS STCOU FIPS MCD
MPO Name
18149 18169 18183 18001 18003 18033 18069 18113 18151 18179 18183 18089 18091 18127 18029 18115 18007 18015 18023 18045 18107 18157 18171 18181 18167
19139 19163 19013
19017
19019
19023
19037
19075
19015 19049 19099
Michiana Area COG Michiana Area COG Michiana Area COG Northeastern Indiana Reg. Coordinating Council Northeastern Indiana Reg. Coordinating Council Northeastern Indiana Reg. Coordinating Council Northeastern Indiana Reg. Coordinating Council Northeastern Indiana Reg. Coordinating Council Northeastern Indiana Reg. Coordinating Council Northeastern Indiana Reg. Coordinating Council Northeastern Indiana Reg. Coordinating Council Northwestern Indiana RPC Northwestern Indiana RPC Northwestern Indiana RPC Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Tippecanoe County Area Planning Commission Tippecanoe County Area Planning Commission Tippecanoe County Area Planning Commission Tippecanoe County Area Planning Commission Tippecanoe County Area Planning Commission Tippecanoe County Area Planning Commission Tippecanoe County Area Planning Commission Tippecanoe County Area Planning Commission West Central Indiana Economic Development District Bi-State Regional Commission Bi-State Regional Commission Black Hawk Metropolitan Area Transp. Policy Board Black Hawk Metropolitan Area Transp. Policy Board Black Hawk Metropolitan Area Transp. Policy Board Black Hawk Metropolitan Area Transp. Policy Board Black Hawk Metropolitan Area Transp. Policy Board Black Hawk Metropolitan Area Transp. Policy Board Des Moines Area MPO Des Moines Area MPO Des Moines Area MPO
MPO
MPO
Code Geography
7801 7801 7801 2761 2761 2761 2761 2761 2761 2761 2761 2961 2961 2961 1641 1641 3921 3921 3921 3921 3921 3921 3921 3921 8321
BG BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ Tract Tract Tract Tract Tract TAZ Tract Tract BG
1961 TAZ 1961 TAZ 8921 TAZ
8921 TAZ
8921 TAZ
8921 TAZ
8921 TAZ
8921 TAZ
2121 BG 2121 TAZ 2121 BG
138
April 29, 2015
State
Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Iowa Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kansas Kentucky Kentucky Kentucky Kentucky Kentucky Kentucky Kentucky
Federal Transit Administration STOPS v1.50 User Guide
FIPS STCOU FIPS MCD
MPO Name
MPO
MPO
Code Geography
19121 19125 19127 19153 19169 19181 19045 19055 19061 19097 19103 19103 19113 19129 19155 19149 19193 20045 20045 20091 20103 20121 20209 20043 20177 20015 20035 20079 20095 20155 20173 20191 21019 21089 21227 21047 21101 21059 21029
Des Moines Area MPO
2121 BG
Des Moines Area MPO
2121 BG
Des Moines Area MPO
2121 BG
Des Moines Area MPO
2121 TAZ
Des Moines Area MPO
2121 BG
Des Moines Area MPO
2121 TAZ
Dubuque MATS
2201 TAZ
Dubuque MATS
2201 TAZ
Dubuque MATS
2201 TAZ
Dubuque MATS
2201 TAZ
Johnson County COG
3501 TAZ
Linn County RPC
1361 TAZ
Linn County RPC
1361 TAZ
Omaha-Council Bluffs Metro Area Planning Agency 5921 BG
Omaha-Council Bluffs Metro Area Planning Agency 5921 TAZ
Siouxland Interstate MPC
7721 TAZ
Siouxland Interstate MPC
7721 TAZ
Lawrence/Douglas County MPO
4151 TAZ
Mid-America Regional Council
3761 TAZ
Mid-America Regional Council
3761 TAZ
Mid-America Regional Council
3761 TAZ
Mid-America Regional Council
3761 TAZ
Mid-America Regional Council
3761 TAZ
St. Joseph Area Transportation Study
7001 TAZ
Topeka-Shawnee County MPO
8441 BG
Wichita-Sedgwick County MPO
9041 BG
Wichita-Sedgwick County MPO
9041 BG
Wichita-Sedgwick County MPO
9041 BG
Wichita-Sedgwick County MPO
9041 BG
Wichita-Sedgwick County MPO
9041 BG
Wichita-Sedgwick County MPO
9041 BG
Wichita-Sedgwick County MPO
9041 BG
Ashland Urbanized Area
3411 BG
Ashland Urbanized Area
3411 BG
Bowling Green-Warren County
1141 TAZ
Clarksville Urban Area MPO
1661 BG
Evansville Urban Transportation Study
2441 TAZ
Green River Area Development District
5991 TAZ
Kentuckiana Regional Planning and Development Agency
4521 TAZ
139
Federal Transit Administration STOPS v1.50 Users Guide
State
Kentucky
Kentucky
Kentucky Kentucky Kentucky Kentucky Kentucky Kentucky Kentucky Kentucky Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana
Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana Louisiana
FIPS STCOU FIPS MCD
MPO Name
21111
21185
21067 21113 21015 21037 21077 21081 21117 21191 22005 22033 22047 22063 22121 22007 22051 22057 22089 22093 22095 22101 22109 22019
22001 22045 22055 22097 22099 22113 22051 22071 22075 22087 22089 22093 22095 22103
Kentuckiana Regional Planning and Development Agency Kentuckiana Regional Planning and Development Agency Lexington Area MPO Lexington Area MPO Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Capital Region PC Capital Region PC Capital Region PC Capital Region PC Capital Region PC Houma-Thibodaux MPO Houma-Thibodaux MPO Houma-Thibodaux MPO Houma-Thibodaux MPO Houma-Thibodaux MPO Houma-Thibodaux MPO Houma-Thibodaux MPO Houma-Thibodaux MPO Imperial Calcasieu Regional Planning & Dev. Comm. Lafayette Consolidated Government Lafayette Consolidated Government Lafayette Consolidated Government Lafayette Consolidated Government Lafayette Consolidated Government Lafayette Consolidated Government New Orleans RPC New Orleans RPC New Orleans RPC New Orleans RPC New Orleans RPC New Orleans RPC New Orleans RPC New Orleans RPC
MPO
MPO
Code Geography
4521 TAZ
4521 TAZ
4281 TAZ 4281 TAZ 1641 TAZ 1641 TAZ 1641 BG 1641 BG 1641 TAZ 1641 BG 0761 TAZ 0761 TAZ 0761 BG 0761 TAZ 0761 TAZ 3351 BG 3351 TAZ 3351 BG 3351 BG 3351 BG 3351 BG 3351 BG 3351 TAZ 3961 TAZ
3881 BG 3881 BG 3881 TAZ 3881 BG 3881 BG 3881 BG 5561 TAZ 5561 TAZ 5561 TAZ 5561 TAZ 5561 TAZ 5561 BG 5561 BG 5561 TAZ
140
April 29, 2015
State
Louisiana Louisiana Louisiana Louisiana
Maine
Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland Maryland
FIPS STCOU FIPS MCD
MPO Name
22015 22017 22073 22079 New England states are shown at the end of this file 24003 24005 24013 24015 24017 24021 24025 24027 24031 24033 24035 24510 24001 24015 24043 24003 24005 24009 24013 24017 24021 24025 24027 24031 24033 24035 24037 24043 24510 24015
Northwest Louisiana COG Northwest Louisiana COG Ouachita COG Rapides Area PC
Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Cumberland Urbanized Area Delaware Valley RPC Hagerstown-Eastern Panhandle MPO Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Wilmington Planning Council
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
7681 TAZ 7681 TAZ 5201 TAZ 0221 TAZ
0721 0721 0721 0721 0721 0721 0721 0721 0721 0721 0721 0721 1901 6161 3181 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 9161
TAZ TAZ TAZ Tract Tract Tract TAZ TAZ Tract Tract Tract TAZ BG Tract TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG
141
Federal Transit Administration STOPS v1.50 Users Guide
State
FIPS STCOU FIPS MCD
MPO Name
Massachusetts
Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan
New England states are shown at the end of this file
26025 26017 26049 26087 26093 26125 26145 26155
26157
26081 26139 26005 26015 26025 26077 26081 26159 26005 26081 26121 26139 26021 26027 26059 26075 26091 26017 26049 26057 26111 26145 26155 26157 26093 26099 26115
Battle Creek Area Transportation Study Bay City Area Transportation Study Genesee County MPO Genesee County MPO Genesee County MPO Genesee County MPO Genesee County MPO Genesee County MPO Genesee County MPO Grand Valley Metro Council Grand Valley Metro Council Kalamazoo Area Transportation Study Kalamazoo Area Transportation Study Kalamazoo Area Transportation Study Kalamazoo Area Transportation Study Kalamazoo Area Transportation Study Kalamazoo Area Transportation Study Macatawa Area Coordinating Council Macatawa Area Coordinating Council Macatawa Area Coordinating Council Macatawa Area Coordinating Council Michiana Area COG Michiana Area COG Region 2 Planning Commission Region 2 Planning Commission Region 2 Planning Commission Saginaw Metropolitan Area Transportation Study Saginaw Metropolitan Area Transportation Study Saginaw Metropolitan Area Transportation Study Saginaw Metropolitan Area Transportation Study Saginaw Metropolitan Area Transportation Study Saginaw Metropolitan Area Transportation Study Saginaw Metropolitan Area Transportation Study Southeast Michigan COG Southeast Michigan COG Southeast Michigan COG
MPO
MPO
Code Geography
0781 TAZ 0801 TAZ 2641 TAZ 2641 TAZ 2641 TAZ 2641 TAZ 2641 TAZ 2641 TAZ 2641 TAZ 3001 TAZ 3001 TAZ 3721 TAZ 3721 TAZ 3721 TAZ 3721 TAZ 3721 TAZ 3721 TAZ 3311 TAZ 3311 TAZ 3311 TAZ 3311 TAZ 7801 TAZ 7801 TAZ 3521 BG 3521 TAZ 3521 BG 6961 BG 6961 BG 6961 BG 6961 BG 6961 TAZ 6961 BG 6961 BG 2161 TAZ 2161 TAZ 2161 TAZ
142
April 29, 2015
State
Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Michigan Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota Minnesota
Federal Transit Administration STOPS v1.50 User Guide
FIPS STCOU FIPS MCD
MPO Name
26125 26147 26161 26163 26021 26027 26159 26115 26037 26045 26065 26121 26139 27137 27027 27119 27055 27169 27003 27019 27025 27037 27049 27053 27059 27079 27085 27095 27123 27131 27139 27141 27143 27163 27171 27109 27009 27141 27145
Southeast Michigan COG Southeast Michigan COG Southeast Michigan COG Southeast Michigan COG Southwestern Michigan Commission Southwestern Michigan Commission Southwestern Michigan Commission Toledo Metropolitan Area COG Tri-County RPC Tri-County RPC Tri-County RPC West Michigan Shoreline RDC West Michigan Shoreline RDC Arrowhead RDC Fargo-Moorhead Metropolitan COG Grand Forks-East Grand Forks MPO La Crosse Area Planning Committee La Crosse Area Planning Committee Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Rochester-Olmsted COG St. Cloud Area Planning Organization St. Cloud Area Planning Organization St. Cloud Area Planning Organization
MPO
MPO
Code Geography
2161 TAZ 2161 TAZ 2161 TAZ 2161 TAZ 0871 BG 0871 BG 0871 BG 8401 TAZ 4041 TAZ 4041 TAZ 4041 TAZ 5291 TAZ 5291 TAZ 2241 TAZ 2521 TAZ 2986 TAZ 3871 TAZ 3871 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 5121 TAZ 6821 TAZ 6981 BG 6981 BG 6981 BG
143
Federal Transit Administration STOPS v1.50 Users Guide
State
Mississippi
Mississippi
Mississippi
Mississippi Mississippi Mississippi Mississippi Mississippi Mississippi
Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri Missouri
Missouri
Missouri Missouri Montana Montana
Montana Nebraska Nebraska Nebraska Nebraska Nebraska Nevada
FIPS STCOU FIPS MCD
MPO Name
MPO
MPO
Code Geography
28049
28089
28121
28045 28047 28059 28035 28073 28033 29019 29071 29099 29183 29189 29510 29097 29145 29037 29047 29049 29095 29107 29165 29177 29043
29077
29003 29021 30013 30063
30111 31109 31055 31153 31177 31043 32003
Central Mississippi Planning & Development District Central Mississippi Planning & Development District Central Mississippi Planning & Development District Gulf RPC Gulf RPC Gulf RPC Hattiesburg-Petal-Forrest-Lamar MPO Hattiesburg-Petal-Forrest-Lamar MPO Memphis MPO Columbia Area Transportation Study East-West Gateway Coordinating Council East-West Gateway Coordinating Council East-West Gateway Coordinating Council East-West Gateway Coordinating Council East-West Gateway Coordinating Council Joplin Area Transportation Study Organization Joplin Area Transportation Study Organization Mid-America Regional Council Mid-America Regional Council Mid-America Regional Council Mid-America Regional Council Mid-America Regional Council Mid-America Regional Council Mid-America Regional Council Springfield Area Transportation Study Organization Springfield Area Transportation Study Organization St. Joseph Area Transportation Study St. Joseph Area Transportation Study Great Falls City-County Planning Board Missoula Transportation Policy Coordinating Committee Yellowstone County Board of Planning Lincoln-Lancaster MPO Omaha-Council Bluffs Metro Area Planning Agency Omaha-Council Bluffs Metro Area Planning Agency Omaha-Council Bluffs Metro Area Planning Agency Siouxland Interstate MPC Southern Nevada RTC
3561
3561
3561
0921 0921 0921 3286 3286 4921 1741 7041 7041 7041 7041 7041 3711 3711 3761 3761 3761 3761 3761 3761 3761 7921
7921
7001 7001 3041 5141
0881 4361 5921 5921 5921 7721 4121
BG
BG
BG
BG BG BG TAZ TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ BG BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ
TAZ
TAZ TAZ BG BG
Tract TAZ TAZ TAZ TAZ TAZ Tract
144
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
State
Nevada Nevada Nevada Nevada
New Hampshire
New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey
FIPS STCOU FIPS MCD
MPO Name
32005 32031 32510 32031 New England states are shown at the end of this file 34001 34005 34007 34011 34015 34019 34021 34023 34025 34029 34033 34035 34003 34013 34017 34019 34021 34023 34025 34027 34029 34031 34035 34037 34039 34041 34003 34013 34017 34019 34023 34025
Tahoe MPO Tahoe MPO Tahoe MPO Washoe County RTC
Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority
MPO
MPO
Code Geography
9371 BG 9371 BG 9371 BG 6721 TAZ
6161 6161 6161 6161 6161 6161 6161 6161 6161 6161 6161 6161 5601 5601 5601 5601 5601 5601 5601 5601 5601 5601 5601 5601 5601 5601 5641 5641 5641 5641 5641 5641
TAZ TAZ TAZ TAZ TAZ Tract TAZ Tract Tract Tract TAZ Tract BG BG BG BG BG BG BG BG BG BG BG BG BG BG BG BG BG BG BG BG
145
Federal Transit Administration STOPS v1.50 Users Guide
State
New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Jersey New Mexico New Mexico New Mexico New Mexico New Mexico New Mexico New Mexico New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York
New York
FIPS STCOU FIPS MCD
MPO Name
MPO
MPO
Code Geography
34027 34029 34031 34035 34037 34039 34041 34001 34009 34011 34033 35013 35013 35001 35043 35057 35061 35049 36091 36113 36115 36007 36107 36001 36083 36091 36093 36015 36037 36051 36055 36069 36073 36099 36117 36121 36123 36029
36063
North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority North Jersey Transportation Planning Authority South Jersey Transportation Planning Organization South Jersey Transportation Planning Organization South Jersey Transportation Planning Organization South Jersey Transportation Planning Organization El Paso MPO Las Cruces MPO Mid Region COG Mid Region COG Mid Region COG Mid Region COG Santa Fe MPO Adirondack-Glens Falls Transportation Council Adirondack-Glens Falls Transportation Council Adirondack-Glens Falls Transportation Council Binghamton Metropolitan Transportation Study Binghamton Metropolitan Transportation Study Capital District Transportation Committee Capital District Transportation Committee Capital District Transportation Committee Capital District Transportation Committee Elmira-Chemung Transportation Council Genesee Transportation Council Genesee Transportation Council Genesee Transportation Council Genesee Transportation Council Genesee Transportation Council Genesee Transportation Council Genesee Transportation Council Genesee Transportation Council Genesee Transportation Council Greater Buffalo Niagara Transportation Commission Greater Buffalo Niagara Transportation Commission
5641 5641 5641 5641 5641 5641 5641 0561 0561 0561 0561 2321 4101 0201 0201 0201 0201 7491 2976 2976 2976 0961 0961 0161 0161 0161 0161 2336 6841 6841 6841 6841 6841 6841 6841 6841 6841 1281
1281
BG BG BG BG BG BG BG Tract Tract Tract Tract TAZ TAZ TAZ TAZ TAZ TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ Tract TAZ TAZ TAZ Tract Tract TAZ Tract Tract TAZ
TAZ
146
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
State
FIPS STCOU FIPS MCD
MPO Name
New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York New York
New York
New York
New York
New York
New York
New York
New York New York New York North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina
36043 36065 36109 36111 36005 36027 36047 36059 36061 36071 36079 36081 36085 36087 36103 36105 36111 36119 36071 36021
36027
36071
36079
36087
36111
36119
36053 36067 36075 37021 37087 37089 37115 37175 37001 37081
Herkimer-Oneida Counties Transportation Study Herkimer-Oneida Counties Transportation Study Ithaca-Tompkins County Transportation Council Kingston MPO New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC New York MTC Newburgh-Orange County Transportation Council Poughkeepsie-Dutchess County Transportation Council Poughkeepsie-Dutchess County Transportation Council Poughkeepsie-Dutchess County Transportation Council Poughkeepsie-Dutchess County Transportation Council Poughkeepsie-Dutchess County Transportation Council Poughkeepsie-Dutchess County Transportation Council Poughkeepsie-Dutchess County Transportation Council Syracuse Metropolitan Transportation Council Syracuse Metropolitan Transportation Council Syracuse Metropolitan Transportation Council Asheville Urban Area MPO Asheville Urban Area MPO Asheville Urban Area MPO Asheville Urban Area MPO Asheville Urban Area MPO Burlington-Graham MPO Burlington-Graham MPO
MPO
MPO
Code Geography
8681 TAZ 8681 TAZ 3511 TAZ 3836 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5601 BG 5661 TAZ 2281 BG
2281 BG
2281 BG
2281 BG
2281 BG
2281 BG
2281 BG
8161 BG 8161 TAZ 8161 BG 0481 BG 0481 BG 0481 BG 0481 BG 0481 BG 3111 BG 3111 BG
147
Federal Transit Administration STOPS v1.50 Users Guide
State
FIPS STCOU FIPS MCD
MPO Name
North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina North Carolina
37135 37025 37159 37037 37069 37085 37101 37183 37133 37001 37037 37063 37069 37077 37085 37101 37135 37145 37183 37051 37085 37093 37071 37191 37081 37147 37003 37023 37027 37035 37057 37067 37081 37151 37119 37179 37065 37127 37019 37129
Burlington-Graham MPO Cabarrus-South Rowan MPO Cabarrus-South Rowan MPO Capital Area MPO Capital Area MPO Capital Area MPO Capital Area MPO Capital Area MPO City of Jacksonville Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Durham-Chapel Hill-Carrboro MPO Fayetteville Area MPO Fayetteville Area MPO Fayetteville Area MPO Gaston Urban Area MPO Goldsboro Urbanized Area MPO Greensboro Urban Area MPO Greenville Urban Area MPO Hickory-Newton-Conover MPO Hickory-Newton-Conover MPO Hickory-Newton-Conover MPO Hickory-Newton-Conover MPO High Point Urban Area MPO High Point Urban Area MPO High Point Urban Area MPO High Point Urban Area MPO Mecklenburg-Union MPO Mecklenburg-Union MPO Rocky Mount Urban Area MPO Rocky Mount Urban Area MPO Wilmington Urban Area MPO Wilmington Urban Area MPO
148
MPO
MPO
Code Geography
3111 BG 1861 TAZ 1861 TAZ 6641 BG 6641 TAZ 6641 TAZ 6641 TAZ 6641 TAZ 3606 TAZ 2261 BG 2261 TAZ 2261 TAZ 2261 TAZ 2261 TAZ 2261 TAZ 2261 TAZ 2261 TAZ 2261 TAZ 2261 TAZ 2561 TAZ 2561 TAZ 2561 BG 2966 TAZ 2981 TAZ 3121 BG 3151 TAZ 3291 TAZ 3291 TAZ 3291 TAZ 3291 TAZ 3301 BG 3301 BG 3301 BG 3301 BG 1521 TAZ 1521 TAZ 6896 BG 6896 BG 9181 BG 9181 TAZ
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
State
FIPS STCOU FIPS MCD
MPO Name
North Carolina North Carolina North Carolina North Carolina North Carolina North Dakota North Dakota North Dakota North Dakota
Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio
Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio
37141 37057 37059 37067 37169 38015 38059 38017 38035 39007 39019 39029 39035 39055 39085 39093 39099 39103 39133 39151 39153 39155 39169 39013 39081 39023
39099 39155 39087 39045 39089 39127 39003 39057 39109 39113 39041 39045 39049
Wilmington Urban Area MPO Winston Salem/Forsyth County MPO Winston Salem/Forsyth County MPO Winston Salem/Forsyth County MPO Winston Salem/Forsyth County MPO Bismarck-Mandan MPO Bismarck-Mandan MPO Fargo-Moorhead Metropolitan COG Grand Forks-East Grand Forks MPO Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Akron Metropolitan Area Transportation Study Bel-O-Mar Regional Council Brooke-Hancock-Jefferson MPC Clark County-Springfield Transportation Coord. Committee Eastgate Regional COG Eastgate Regional COG KYOVA Interstate Planning Commission Licking County Area Transportation Study Licking County Area Transportation Study Licking County Area Transportation Study Lima-Allen County RPC Miami Valley RPC Miami Valley RPC Miami Valley RPC Mid-Ohio RPC Mid-Ohio RPC Mid-Ohio RPC
MPO
MPO
Code Geography
9181 9201 9201 9201 9201 1011 1011 2521 2986 0081 0081 0081 0081 0081 0081 0081 0081 0081 0081 0081 0081 0081 0081 9001 8081 8011
Tract BG BG TAZ BG BG BG TAZ TAZ TAZ Tract Tract TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ
9321 TAZ 9321 TAZ 3401 TAZ 5651 BG 5651 TAZ 5651 BG 4321 TAZ 2001 TAZ 2001 TAZ 2001 TAZ 1841 BG 1841 BG 1841 BG
149
Federal Transit Administration STOPS v1.50 Users Guide
State
Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Ohio Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma
FIPS STCOU FIPS MCD
MPO Name
39089 39097 39129 39159 39007 39035 39055 39085 39093 39103 39133 39151 39153 39155 39169 39015 39017 39025 39057 39061 39109 39113 39165 39139 39019 39151 39051 39095 39123 39143 39173 39167 40017 40027 40051 40083 40087 40109 40125 40037
Mid-Ohio RPC Mid-Ohio RPC Mid-Ohio RPC Mid-Ohio RPC Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Northeast Ohio Areawide Coordinating Agency Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Ohio-Kentucky-Indiana Regional COG Richland County RPC Stark County Area Transportation Study Stark County Area Transportation Study Toledo Metropolitan Area COG Toledo Metropolitan Area COG Toledo Metropolitan Area COG Toledo Metropolitan Area COG Toledo Metropolitan Area COG WWW Interstate Planning Commission Association of Central Oklahoma Governments Association of Central Oklahoma Governments Association of Central Oklahoma Governments Association of Central Oklahoma Governments Association of Central Oklahoma Governments Association of Central Oklahoma Governments Association of Central Oklahoma Governments Indian Nations COG
MPO
MPO
Code Geography
1841 1841 1841 1841 1681 1681 1681 1681 1681 1681 1681 1681 1681 1681 1681 1641 1641 1641 1641 1641 1641 1641 1641 4801 1321 1321 8401 8401 8401 8401 8401 6021 5881 5881 5881 5881 5881 5881 5881 8561
BG BG BG BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG Tract TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ
150
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
State
FIPS STCOU FIPS MCD
MPO Name
Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma Oklahoma
Oregon Oregon Oregon Oregon Oregon Oregon Oregon Oregon Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania
40097 40101 40111 40113 40117 40131 40143 40145 40147 40031 40079 40135 41045 41039 41005 41051 41067 41029 41047 41053 42001 42133 42115 42013 42021 42027 42011 42017 42029 42045 42071 42077 42091 42095 42101 42049 42055 42041 42043 40271
Indian Nations COG Indian Nations COG Indian Nations COG Indian Nations COG Indian Nations COG Indian Nations COG Indian Nations COG Indian Nations COG Indian Nations COG Lawton Metropolitan Area PC Western Arkansas PDD Western Arkansas PDD Community Planning Assoc. of Southwest Idaho Lane Council of Governments Metro Metro Metro Rogue Valley MPO Salem Keizer Area Transportation Study Salem Keizer Area Transportation Study Baltimore Metropolitan Council Baltimore Metropolitan Council Binghamton Metropolitan Transportation Study Blair County Planning Commission Cambria County Planning Commission Centre Region MPO Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Delaware Valley RPC Erie MPO Hagerstown-Eastern Panhandle MPO Harrisburg Area Transportation Study Harrisburg Area Transportation Study Harrisburg Area Transportation Study
MPO
MPO
Code Geography
8561 8561 8561 8561 8561 8561 8561 8561 8561 4201 2721 2721 1081 2401 6441 6441 6441 4991 7081 7081 0721 0721 0961 0281 3681 8051 6161 6161 6161 6161 6161 6161 6161 6161 6161 2361 3181 3241 3241 3241
Tract Tract Tract TAZ Tract BG TAZ TAZ Tract TAZ BG TAZ Tract TAZ BG BG BG BG BG BG Tract Tract BG Tract BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG TAZ TAZ TAZ TAZ
151
Federal Transit Administration STOPS v1.50 Users Guide
State
FIPS STCOU FIPS MCD
MPO Name
MPO
MPO
Code Geography
Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Pennsylvania Rhode Island
South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina
42075 42099 42133 42069 42079 42071 42073 42025 42077 42095 42081
42001
42055 42133 42011 42085 42003 42005 42007 42019 42051 42059 42063 42125 42129 42133 New England states are shown at the end of this file 45007 45003 45063 45079 45015 45019 45035 45031 45041 45007
Harrisburg Area Transportation Study Harrisburg Area Transportation Study Harrisburg Area Transportation Study Lackawanna-Luzerne Transportation Study Lackawanna-Luzerne Transportation Study Lancaster County Transp. Coordinating Committee Lawrence County Planning Department Lehigh Valley Transportation Study Lehigh Valley Transportation Study Lehigh Valley Transportation Study Lycoming County Planning Commission Metopolitan Washington COG Metopolitan Washington COG Metopolitan Washington COG Reading Area Transportation Study Shenango Valley Area Transportation Study Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission Southwestern Pennsylvania Commission York County PC
3241 3241 3241 7561 7561 4001 5401 0241 0241 0241 9141 8841 8841 8841 6681 7611 6281 6281 6281 6281 6281 6281 6281 6281 6281 9281
BG TAZ TAZ BG BG BG BG Tract TAZ TAZ BG Tract Tract Tract TAZ Tract BG BG BG BG BG BG BG BG BG TAZ
Anderson Area Transportation Study Augusta Richmond County PC Central Midlands COG Central Midlands COG Charleston Area Transportation Study Charleston Area Transportation Study Charleston Area Transportation Study Florence Area Transportation Study Florence Area Transportation Study Greenville Area Transportation Study
0406 TAZ 0601 TAZ 1761 TAZ 1761 TAZ 1441 TAZ 1441 TAZ 1441 TAZ 2656 TAZ 2656 TAZ 3161 TAZ
152
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
State
FIPS STCOU FIPS MCD
MPO Name
South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Carolina South Dakota South Dakota South Dakota South Dakota South Dakota
Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee Tennessee
45045 45059 45077 45083 45091 45083 45085 45043 45051 46093 46103 46083 46099 46127 47163 47065 47115 47125 47113 47019 47171 47179 47073 47163 47179 47001 47009 47093 47105 47155 47173 47047 47157 47021 47037 47043 47119 47125 47147 47149
Greenville Area Transportation Study Greenville Area Transportation Study Greenville Area Transportation Study Greenville Area Transportation Study Rock Hill-Fort Mill Area Transportation Study Spartanburg Area Transportation Study Sumter Area Transportation Study Waccamaw RPC Waccamaw RPC Rapid City Area MPO Rapid City Area MPO Sioux Falls MPO Sioux Falls MPO Siouxland Interstate MPC Bristol Urban Area MPO Chattanooga Urban Area MPO Chattanooga Urban Area MPO Clarksville Urban Area MPO Jackson MPO Johnson City MPO Johnson City MPO Johnson City MPO Kingsport Urban Area MPO Kingsport Urban Area MPO Kingsport Urban Area MPO Knoxville MPO Knoxville MPO Knoxville MPO Knoxville MPO Knoxville MPO Knoxville MPO Memphis MPO Memphis MPO Nashville Area MPO Nashville Area MPO Nashville Area MPO Nashville Area MPO Nashville Area MPO Nashville Area MPO Nashville Area MPO
MPO
MPO
Code Geography
3161 3161 3161 3161 6861 7821 8141 2971 2971 6661 6661 7761 7761 7721 1161 1561 1561 1661 3581 3661 3661 3661 3831 3831 3831 3841 3841 3841 3841 3841 3841 4921 4921 5361 5361 5361 5361 5361 5361 5361
TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG BG TAZ TAZ TAZ TAZ BG BG BG TAZ TAZ Tract TAZ BG BG BG BG TAZ TAZ BG BG BG BG TAZ BG BG BG BG BG BG BG
153
Federal Transit Administration STOPS v1.50 Users Guide
State
Tennessee Tennessee Tennessee
Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas
FIPS STCOU FIPS MCD
MPO Name
47165 47187 47189 48253 48441 48375 48381 48061 48041 48021 48055 48209 48453 48491 48355 48409 48141 48061 48215 48039 48071 48157 48167 48201 48291 48339 48473 48027 48099 48281 48479 48183 48203 48401 48423 48459 48303 48085 48113 48121
Nashville Area MPO Nashville Area MPO Nashville Area MPO Abilene MPO Abilene MPO Amarillo MPO Amarillo MPO Brownsville MPO Bryan-College Station MPO Capital Area MPO Capital Area MPO Capital Area MPO Capital Area MPO Capital Area MPO Corpus Christi MPO Corpus Christi MPO El Paso MPO Harlingen-San Benito MPO Hidalgo County MPO Houston-Galveston Area Council Houston-Galveston Area Council Houston-Galveston Area Council Houston-Galveston Area Council Houston-Galveston Area Council Houston-Galveston Area Council Houston-Galveston Area Council Houston-Galveston Area Council Killeen-Temple Urban Transportation Study Killeen-Temple Urban Transportation Study Killeen-Temple Urban Transportation Study Laredo Urban Transportation Study Longview MPO Longview MPO Longview MPO Longview MPO Longview MPO Lubbock MPO North Central Texas COG North Central Texas COG North Central Texas COG
154
MPO
MPO
Code Geography
5361 BG 5361 BG 5361 TAZ 0041 TAZ 0041 TAZ 0321 TAZ 0321 TAZ 1241 TAZ 1261 TAZ 0641 TAZ 0641 TAZ 0641 TAZ 0641 TAZ 0641 TAZ 1881 TAZ 1881 TAZ 2321 TAZ 3201 TAZ 4881 TAZ 3361 TAZ 3361 TAZ 3361 TAZ 3361 TAZ 3361 TAZ 3361 TAZ 3361 TAZ 3361 TAZ 3811 TAZ 3811 TAZ 3811 TAZ 4081 TAZ 4421 TAZ 4421 TAZ 4421 TAZ 4421 TAZ 4421 TAZ 4601 TAZ 1921 TAZ 1921 TAZ 1921 TAZ
April 29, 2015
State
Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Texas Utah Utah Utah Utah Utah Utah Utah Utah Utah Utah Utah
Federal Transit Administration STOPS v1.50 User Guide
FIPS STCOU FIPS MCD
MPO Name
48139 48251 48257 48349 48363 48367 48397 48439 48497 48135 48329 48451 48029 48091 48187 48493 48181 48199 48245 48361 48037 48423 48469 48309 48009 48077 48485 49005 49053 49043 49049 49051 49011 49029 49035 49045 49049 49057
North Central Texas COG North Central Texas COG North Central Texas COG North Central Texas COG North Central Texas COG North Central Texas COG North Central Texas COG North Central Texas COG North Central Texas COG Permian Basin RPC Permian Basin RPC San Angelo MPO San Antonio-Bexar County MPO San Antonio-Bexar County MPO San Antonio-Bexar County MPO San Antonio-Bexar County MPO Sherman-Denison MPO South East Texas RPC South East Texas RPC South East Texas RPC Texarkana MPO Tyler MPO Victoria MPO Waco MPO Wichita Falls MPO Wichita Falls MPO Wichita Falls MPO Cache MPO Dixie MPO Mountainland Association of Governments Mountainland Association of Governments Mountainland Association of Governments Wasatch Front Regional Council Wasatch Front Regional Council Wasatch Front Regional Council Wasatch Front Regional Council Wasatch Front Regional Council Wasatch Front Regional Council
MPO
MPO
Code Geography
1921 1921 1921 1921 1921 1921 1921 1921 1921 5801 5801 7201 7241 7241 7241 7241 7641 0841 0841 0841 8361 8641 8751 8801 9081 9081 9081 4411 6971 6521 6521 6521 7161 7161 7161 7161 7161 7161
TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ Tract Tract TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG BG TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ
155
Federal Transit Administration STOPS v1.50 Users Guide
State
Vermont
Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia
FIPS STCOU FIPS MCD
MPO Name
New England states are shown at the end of this file
51013 51059 51107 51153 51510 51600 51610 51683 51685 51191 51520 51009 51019 51031 51680 51041 51053 51149 51570 51670 51730 51033 51099 51177 51179 51630 51073 51093 51095 51199 51550 51650 51700 51710 51735 51740
Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Baltimore Metropolitan Council Bristol Urban Area MPO Bristol Urban Area MPO Central Virginia MPO Central Virginia MPO Central Virginia MPO Central Virginia MPO Crater Planning District Commission Crater Planning District Commission Crater Planning District Commission Crater Planning District Commission Crater Planning District Commission Crater Planning District Commission Fredericksburg Area MPO Fredericksburg Area MPO Fredericksburg Area MPO Fredericksburg Area MPO Fredericksburg Area MPO Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC
156
MPO
MPO
Code Geography
0721 0721 0721 0721 0721 0721 0721 0721 0721 1161 1161 4641 4641 4641 4641 6141 6141 6141 6141 6141 6141 2801 2801 2801 2801 2801 5721 5721 5721 5721 5721 5721 5721 5721 5721 5721
Tract Tract Tract Tract Tract Tract Tract Tract Tract TAZ TAZ BG BG BG BG TAZ TAZ TAZ TAZ TAZ TAZ BG TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ
April 29, 2015
State
Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia
FIPS STCOU FIPS MCD
MPO Name
51800 51810 51830 51169 51013 51033 51043 51047 51057 51059 51061 51069 51099 51107 51137 51153 51157 51177 51179 51187 51193 51510 51600 51610 51630 51683 51685 51840 51036 51041 51075 51085 51087 51127 51145 51760 51019 51023 51161 51770
Hampton Roads PDC Hampton Roads PDC Hampton Roads PDC Kingsport Urban Area MPO Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Richmond Regional PDC Richmond Regional PDC Richmond Regional PDC Richmond Regional PDC Richmond Regional PDC Richmond Regional PDC Richmond Regional PDC Richmond Regional PDC Roanoke Valley Area MPO Roanoke Valley Area MPO Roanoke Valley Area MPO Roanoke Valley Area MPO
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
5721 5721 5721 3831 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 8841 6761 6761 6761 6761 6761 6761 6761 6761 6801 6801 6801 6801
TAZ TAZ TAZ BG TAZ Tract TAZ TAZ Tract TAZ TAZ Tract TAZ TAZ Tract TAZ Tract TAZ TAZ TAZ Tract TAZ TAZ TAZ TAZ TAZ TAZ Tract TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ BG TAZ TAZ TAZ
157
Federal Transit Administration STOPS v1.50 Users Guide
State
Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Virginia Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington
FIPS STCOU FIPS MCD
MPO Name
51775 51003 51015 51065 51079 51109 51125 51137 51540 51143 51590 53005 53021 53071 53015 53027 53041 53049 53069 53009 53029 53031 53033 53035 53045 53053 53057 53061 53067 53029 53055 53057 53061 53073 53011 53063 53027 53041 53045 53053
Roanoke Valley Area MPO Thomas Jefferson PDC Thomas Jefferson PDC Thomas Jefferson PDC Thomas Jefferson PDC Thomas Jefferson PDC Thomas Jefferson PDC Thomas Jefferson PDC Thomas Jefferson PDC West Piedmont RPC West Piedmont RPC Benton-Franklin COG Benton-Franklin COG Benton-Franklin COG Longview-Kelso-Rainier MPO Longview-Kelso-Rainier MPO Longview-Kelso-Rainier MPO Longview-Kelso-Rainier MPO Longview-Kelso-Rainier MPO Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Puget Sound Regional Council Skagit COG Skagit COG Skagit COG Skagit COG Skagit COG Southwest Washington Regional Transp. Council Spokane RTC Thurston RPC Thurston RPC Thurston RPC Thurston RPC
MPO
MPO
Code Geography
6801 1541 1541 1541 1541 1541 1541 1541 1541 1951 1951 6741 6741 6741 4416 4416 4416 4416 4416 7601 7601 7601 7601 7601 7601 7601 7601 7601 7601 5261 5261 5261 5261 5261 8691 7841 5911 5911 5911 5911
TAZ TAZ Tract Tract Tract Tract Tract Tract TAZ TAZ TAZ TAZ TAZ TAZ BG BG BG BG BG Tract BG Tract TAZ TAZ Tract TAZ TAZ TAZ BG BG BG TAZ BG TAZ BG TAZ Tract Tract Tract Tract
158
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
State
FIPS STCOU FIPS MCD
MPO Name
Washington Washington Washington Washington Washington Washington Washington Washington Washington Washington West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia West Virginia Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin
53067 53007 53017 53047 53029 53055 53057 53061 53073 53077 54051 54069 54009 54029 54057 54003 54037 54011 54099 54003 54027 54037 54061 54005 54015 54039 54079 54107 55031 55117 55009 55059 55101 55105 55127 55043 55015 55039 55087 55139
Thurston RPC Wenatchee Valley Transportation Council Wenatchee Valley Transportation Council Wenatchee Valley Transportation Council Whatcom COG Whatcom COG Whatcom COG Whatcom COG Whatcom COG Yakima Valley COG Bel-O-Mar Regional Council Bel-O-Mar Regional Council Brooke-Hancock-Jefferson MPC Brooke-Hancock-Jefferson MPC Cumberland Urbanized Area Hagerstown-Eastern Panhandle MPO Hagerstown-Eastern Panhandle MPO KYOVA Interstate Planning Commission KYOVA Interstate Planning Commission Metropolitan Washington COG Metropolitan Washington COG Metropolitan Washington COG Morgantown, WV MPO Regional Intergovernmental Council Regional Intergovernmental Council Regional Intergovernmental Council Regional Intergovernmental Council WWW Interstate Planning Commission Arrowhead RDC Bay-Lake RPC Brown County Planning Commission Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Chicago Area Transportation Study Dubuque MATS East Central Wisconsin RPC East Central Wisconsin RPC East Central Wisconsin RPC East Central Wisconsin RPC
MPO
MPO
Code Geography
5911 8946 8946 8946 0861 0861 0861 0861 0861 9261 9001 9001 8081 8081 1901 3181 3181 3401 3401 8841 8841 8841 5251 1481 1481 1481 1481 6021 2241 3081 3086 1601 1601 1601 1601 2201 0461 0461 0461 0461
TAZ BG BG BG BG BG TAZ Tract TAZ TAZ TAZ TAZ TAZ TAZ Tract TAZ TAZ TAZ TAZ TAZ Tract TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ TAZ
159
Federal Transit Administration STOPS v1.50 Users Guide
State
Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wisconsin Wyoming Wyoming
FIPS STCOU FIPS MCD
MPO Name
55105 55063 55081 55121 55123 55025 55073 55033 55093 55095 55109 55105 55059 55079 55089 55101 55127 55131 55133 55105 55017 55035 56025 56021
Janesville Area Transportation Study La Crosse Area Planning Committee La Crosse Area Planning Committee La Crosse Area Planning Committee La Crosse Area Planning Committee Madison Area MPO Marathon County Metro Planning Commission Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Metropolitan Council of the Twin Cities Area Rockford Area Transportation Study South East Wisconsin RPC South East Wisconsin RPC South East Wisconsin RPC South East Wisconsin RPC South East Wisconsin RPC South East Wisconsin RPC South East Wisconsin RPC Stateline Area Transportation Study West Central Wisconsin RPC West Central Wisconsin RPC Casper Area Transportation Planning Process Cheyenne Area Transportation Planning Process
MPO
MPO
Code Geography
3621 3871 3871 3871 3871 4721 8941 5121 5121 5121 5121 6881 5081 5081 5081 5081 5081 5081 5081 0866 2291 2291 1351 1581
TAZ TAZ Tract Tract Tract TAZ TAZ Tract TAZ TAZ TAZ TAZ BG BG BG BG BG BG BG TAZ TAZ TAZ BG BG
160
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
New England States
Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut
FIPS STCOU
09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09003 09013 09013 09013 09013 09013 09013 09013 09003 09003 09003 09003 09003 09003 09005 09005 09005 09005
FIPS MCD
MPO Name
02060 05910 12270 22070 22630 24800 25990 27600 31240 32640 37070 44700 45820 52140 65370 68940 71390 74540 82590 84900 87000 87070 01080 06260 25360 37910 69220 76290 78250 04300 08490 10100 50440 60120 70550 60750 04930 75730 80490
CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CAPITOL CENTRAL CONNECTICUT CENTRAL CONNECTICUT CENTRAL CONNECTICUT CENTRAL CONNECTICUT CENTRAL CONNECTICUT CENTRAL CONNECTICUT CENTRAL CONNECTICUT CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY
MPO
MPO
Code Geography
0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0910 TAZ 0909 TAZ 0909 TAZ 0909 TAZ 0909 TAZ 0909 TAZ 0909 TAZ 0909 TAZ 0905 TAZ 0905 TAZ 0905 TAZ
161
Federal Transit Administration STOPS v1.50 Users Guide
New England States
Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut
FIPS STCOU FIPS MCD
MPO Name
09005 09009 09009 09009 09009 09009 09009 09009 09009 09009 09015 09007 09007 09007 09007 09007 09007 09007 09011 09011 09001 09001 09001 09001 09001 09001 09001 09001 09001 09001 09001 09001 09001 09001 09005 09005 09003 09005 09005 09005 09005
87910 03250 14160 46940 49950 58300 62290 69640 80070 87560
all 14300 15350 19130 26270 40710 57320 81680 44210 57040 08070 23890 26620 48620 74190 77200 04720 08980 18500 50860 52980 63480 63970 68310 08210 52630 37140 02760 16050 32290 37280
CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY CENTRAL NAUGATUCK VALLEY Central Transportation Planning CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY CONNECTICUT RIVER ESTUARY GREATER BRIDGEPORT GREATER BRIDGEPORT GREATER BRIDGEPORT GREATER BRIDGEPORT GREATER BRIDGEPORT GREATER BRIDGEPORT HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY HOUSATONIC VALLEY LITCHFIELD HILLS LITCHFIELD HILLS LITCHFIELD HILLS LITCHFIELD HILLS LITCHFIELD HILLS
162
MPO
MPO
Code Geography
0905 TAZ 0905 TAZ 0905 TAZ 0905 TAZ 0905 TAZ 0905 TAZ 0905 TAZ 0905 TAZ 0905 TAZ 0905 TAZ 1126 TAZ 0912 TAZ 0912 TAZ 0912 TAZ 0912 TAZ 0912 TAZ 0912 TAZ 0912 TAZ 0912 TAZ 0912 TAZ 0907 TAZ 0907 TAZ 0907 TAZ 0907 TAZ 0907 TAZ 0907 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0902 TAZ 0904 TAZ 0904 TAZ 0904 TAZ 0904 TAZ 0904 TAZ
April 29, 2015
New England States
Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut
FIPS STCOU FIPS MCD
MPO Name
09005 09005 09005 09005 09005 09005 09007 09007 09007 09007 09007 09007 09007 09007 09001 09005 09009 09013 09015 09015 09015 09015 09015 09015 09015 09015 09015 09015 09005 09005 09005 09005 09005 09005 09005 09005 09005 09009 09009 09009 09009
43370 49460 51350 53470 76570 86440 18080 20810 22280 22490 35230 47080 47360 61800
all all all 77830 09190 12130 21860 40500 59980 61030 62710 73420 75870 88190 10940 17240 40290 54030 65930 66420 67960 79510 79720 04580 07310 22910 34950
LITCHFIELD HILLS LITCHFIELD HILLS LITCHFIELD HILLS LITCHFIELD HILLS LITCHFIELD HILLS LITCHFIELD HILLS MIDSTATE MIDSTATE MIDSTATE MIDSTATE MIDSTATE MIDSTATE MIDSTATE MIDSTATE New York MTC New York MTC New York MTC NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHEASTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN NORTHWESTERN CONN SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
0904 TAZ 0904 TAZ 0904 TAZ 0904 TAZ 0904 TAZ 0904 TAZ 0911 TAZ 0911 TAZ 0911 TAZ 0911 TAZ 0911 TAZ 0911 TAZ 0911 TAZ 0911 TAZ 5601 BG 5601 BG 5601 BG 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0915 TAZ 0903 TAZ 0903 TAZ 0903 TAZ 0903 TAZ 0903 TAZ 0903 TAZ 0903 TAZ 0903 TAZ 0903 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ
163
Federal Transit Administration STOPS v1.50 Users Guide
New England States
Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut
FIPS STCOU FIPS MCD
MPO Name
09009 09009 09009 09009 09009 09009 09009 09009 09009 09009 09009 09001 09001 09001 09001 09001 09001 09001 09001 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09011 09013 09001 09009 09009
35650 44560 46520 47535 52070 53890 54870 57600 78740 82870 87700 18850 33620 50580 56060 73070 83430 83500 86370 06820 15910 23400 29910 33900 34250 42600 43230 48900 52350 55500 56270 62150 66210 71670 73770 78600 80280 72090 68170 01220 19550
SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH CENTRAL SOUTH WESTERN SOUTH WESTERN SOUTH WESTERN SOUTH WESTERN SOUTH WESTERN SOUTH WESTERN SOUTH WESTERN SOUTH WESTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN SOUTHEASTERN UNDEFINED TOWNS VALLEY VALLEY VALLEY
164
MPO
MPO
Code Geography
0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0908 TAZ 0901 TAZ 0901 TAZ 0901 TAZ 0901 TAZ 0901 TAZ 0901 TAZ 0901 TAZ 0901 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0913 TAZ 0916 TAZ 0906 TAZ 0906 TAZ 0906 TAZ
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
New England States
Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut Connecticut
Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine
FIPS STCOU FIPS MCD
MPO Name
09009 09011 09013 09013 09013 09013 09015 09015 09015 09015 09015 23001 23001 23001 23001 23001 23001 23001 23001 23001 23001 23001 23001 23001 23001 23005 23005 23005 23005 23011 23011 23011 23011 23023 23023 23023 23023 23019 23019 23019 23019
67610 42390 16400 17800 44910 85950 01430 13810 36000 67400 86790 02060 19105 29255 38565 38740 40035 40665 40770 44585 46160 60020 64570 77800 79585 08430 26525 48820 60685 40175 46405 80880 86970 03355 06260 76960 81930 02795 06680 06925 22535
VALLEY WINDHAM WINDHAM WINDHAM WINDHAM WINDHAM WINDHAM WINDHAM WINDHAM WINDHAM WINDHAM Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Androscoggin Transportation Resource Center Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study
MPO
MPO
Code Geography
0906 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 0914 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 4241 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ
165
Federal Transit Administration STOPS v1.50 Users Guide
New England States Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
FIPS STCOU FIPS MCD
MPO Name
23019 23019 23019 23019 23019 23019 23019 23019 23019 23019 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031
27645 30795 32510 33490 45670 55225 55565 55680 57937 78780
00275 00730 01605 04720 04860 09410 14485 16725 22955 33665 36535 36745 37270 38425 39195 39405 41750 48750 50325 54980
Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Bangor Area Comprehensive Transportation Study Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
MPO
MPO
Code Geography
0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 0731 TAZ 1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
166
April 29, 2015
New England States Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine
FIPS STCOU FIPS MCD
MPO Name
23031
23031
23031
23031
23031
23031
23031
23031
23031
23001 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23005 23023 23023 23023 23031 23031 23031
55085
56870
64675
65760
67475
70030
80530
81475
87985 19105 08430 10180 15430 24495 26525 28240 28870 31390 41067 48820 53860 60545 60685 61945 66145 71990 73670 82105 86025 87845 03355 76960 81930 00730 01605 04860
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401 6401
Tract BG TAZ TAZ TAZ BG TAZ Tract Tract Tract Tract BG TAZ Tract Tract TAZ TAZ TAZ TAZ TAZ TAZ Tract Tract Tract Tract Tract BG
167
Federal Transit Administration STOPS v1.50 Users Guide
New England States Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine
FIPS STCOU FIPS MCD
MPO Name
23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031
09410 16725 33665 36535 36745 41750 55085 64675 65760
00275 00730 01605 04720 04860 09410 14485 16725 22955 33665 36535 36745 37270 38425 39195 39405 41750 48750 50325 54980 55085
Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Greater Portland COG Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO Sea Coast MPO
168
MPO
MPO
Code Geography
6401 6401 6401 6401 6401 6401 6401 6401 6401 6451
TAZ Tract TAZ Tract Tract TAZ BG BG Tract TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
April 29, 2015
New England States Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine
Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine
FIPS STCOU FIPS MCD
MPO Name
23031
23031
23031
23031
23031
23031
23031
23031
23005 23017 23017 23017 23017 23017 23017 23017 23017 23017 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 23031
56870
64675
65760
67475
70030
80530
81475
87985 02655 08150 17250 26910 33315 41365 60405 74510 74685 75595 00275 00730 01605 04720 04860 09410 14485 16725 22955 33665 36535 36745 37270 38425 39195 39405 41750 48750 50325
Sea Coast MPO
Sea Coast MPO
Sea Coast MPO
Sea Coast MPO
Sea Coast MPO
Sea Coast MPO
Sea Coast MPO
Sea Coast MPO
Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ
169
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Maine Maine Maine Maine Maine Maine Maine Maine Maine Maine Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
23031 23031 23031 23031 23031 23031 23031 23031 23031 23031 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003 25003
54980 55085 56870 64675 65760 67475 70030 80530 81475 87985 00555 00975 04545 13345 14010 16180 21360 24120 26815 28180 30315 34340 34655 34970 42460 43300 44385 45420 46225 51580 53050 53960 56795 59665 60225 61065 67595 71095 73335 77990 79985
Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Southern Maine RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC Berkshire County RPC
170
MPO
MPO
Code Geography
7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 7471 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ 6321 TAZ
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25003 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017
80685 05595 16250 21850 26150 27900 32310 37490 37560 37995 38400 41095 43580 52490 57880 59105 60015 68645 70150 74595 00380 01605 02130 04615 05070 07350 09840 11000 11525 15060 21990 24925 30700 31085 31540 35215 35425 35950 37875 38715 39625
Berkshire County RPC Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
6321 TAZ 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG
171
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021
39835 40115 43895 45560 48955 56130 61380 62535 67665 68050 68260 72215 72600 73440 73790 77255 80230 80510 81035 04930 07665 09175 11315 14640 16495 17405 24820 25100 30455 39765 39975 41515 41690 44105 46050 50250 55745 55955 60785 67945 72495
Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO
MPO Name
172
MPO
MPO
Code Geography
1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25021 25021 25021 25021 25023 25023 25023 25023 25023 25023 25023 25023 25025 25025 25025 25025 25027 25027 25027 25001 25001 25001 25001 25001 25001 25001 25001 25001 25001 25001 25001 25001 25001 25001 25027 25027 25027 25027 25027 25027 25027
74175 78690 78865 82315 17895 28285 30210 31645 38855 50145 57775 60330 07000 13205 56585 80930 06365 41165 63165 03600 07175 07980 12995 16775 19295 23105 29020 39100 51440 55500 59735 70605 74385 82525 02760 03740 05490 06015 07525 09105 12715
Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Boston MPO Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Cape Cod Commission Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 1121 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 0741 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG
173
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25001
25001
25001
25001
25001
17300 17685 18560 26430 28740 30560 30945 34795 40255 41340 41585 45105 46820 46925 47135 50670 51825 52420 55395 58825 61800 63270 66105 68155 68610 71480 71620 73090 73895 75015 75155 75400 82000
03600
07175
07980
12995
16775
Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Massachusetts RPC Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
174
MPO
MPO
Code Geography
9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 9241 BG 1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts Massachusetts Massachusetts
Massachusetts
Massachusetts
Massachusetts Massachusetts
Massachusetts
Massachusetts
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25001
25001
25001
25001
25001
25001
25001
25001
25001
25001
25005 25005 25005
25005
25005
25005 25005
25005
25005
25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25007 25007
19295
23105
29020
39100
51440
55500
59735
70605
74385
82525 00520 02690
05280
16425
16950 20100
22130
23000
25240 38225 45000 46575 49970 56060 56375 60645 62430 68750 69170 77570 01585 13800
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning Central Transportation Planning Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG 1126 BG 1126 BG
1126 BG
1126 BG
1126 BG 1126 BG
1126 BG
1126 BG
1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG
175
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25007
25007
25007
25007
25007
25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009 25009
21150
26325
50390
69940
78235 01185 01465 05595 07420 16250 21850 25625 26150 27620 27900 29405 32310 34550 37490 37560 37995 38400 40430 40710 41095 43580 45175 45245 46365 52490 57880 58405 59105 59245 60015 68645 70150 74595
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
176
MPO
MPO
Code Geography
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25009 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017
77150 00380 01605 01955 02130 03005 04615 05070 05805 07350 09840 11000 11525 13135 15060 17475 17825 21990 24925 27480 30360 30700 31085 31540 35215 35425 35950 37000 37875 38715 39625 39835 40115 43895 45560 48955 52805 56130 61380 61590 62535
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG
177
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25017 25019 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021 25021
67665 68050 68260 69415 71025 72215 72600 73440 73790 76135 77255 80230 80510 81035 43790 02935 04930 07665 09175 11315 14640 16495 17405 24820 25100 30455 39765 39975 41515 41690 44105 46050 50250 54100 55745 55955 60785 67945 72495 74175 78690
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
178
MPO
MPO
Code Geography
1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
Massachusetts
Massachusetts
Massachusetts
Massachusetts
25021 25021 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25025 25025 25025 25025 25027
25027
25027
25027
25027
78865 82315 00170 08085 09000 11665 17895 18455 27795 28285 28495 30210 31645 33220 33920 38540 38855 39450 40850 50145 52630 54310 54415 57600 57775 60330 27985 75260 79530 07000 13205 56585 80930
01885
02480
02760
03740
05490
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Central Transportation Planning
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG 1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
179
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027
06015 06365 07525 09105 12715 14395 17300 17685 18560 23875 25485 26430 28740 28950 30560 30945 31435 34165 34795 35075 37420 40255 41165 41340 41585 45105 46820
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
180
MPO
MPO
Code Geography
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027
46925 47135 50670 51825 52420 53120 53225 55395 58580 58825 61800 63165 63270 66105 67385 68155 68610 69275 71480 71620 73090 73895 75015 75155 75400 77010 80405
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
1126 BG
181
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25027
25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25011 25007 25007 25007 25007 25007 25007 25007 25009 25009 25009 25009 25009 25009
82000 02095 05560 09595 12505 14885 15200 16670 21780 25730 27025 29475 29650 35180 35285 42040 42285 45490 47835 51265 58335 61135 61905 68400 73265 74525 79110 01585 13800 21150 26325 50390 69940 78235 01185 01465 07420 25625 27620 29405
Central Transportation Planning
Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Franklin Regional COG Marthas Vineyard Commission Marthas Vineyard Commission Marthas Vineyard Commission Marthas Vineyard Commission Marthas Vineyard Commission Marthas Vineyard Commission Marthas Vineyard Commission Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC
182
MPO
MPO
Code Geography
1126 BG
3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 3101 BG 4861 BG 4861 BG 4861 BG 4861 BG 4861 BG 4861 BG 4861 BG 4161 BG 4161 BG 4161 BG 4161 BG 4161 BG 4161 BG
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25009 25009 25009 25009 25009 25009 25009 25009 25009 25017 25017 25017 25017 25017 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25027 25019 25017 25017 25017 25017 25017 25017 25017 25017 25017
34550 40430 40710 45175 45245 46365 58405 59245 77150 01955 03005 27480 61590 70360 01885 02480 14395 23875 25485 28950 31435 34165 35075 37420 53120 53225 58580 67385 69275 77010 80405 43790 05805 13135 17475 17825 37000 52805 69415 71025 76135
Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Merrimack Valley PC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Montachusett RPC Nantucket Planning & EDC Northern Middlesex COG Northern Middlesex COG Northern Middlesex COG Northern Middlesex COG Northern Middlesex COG Northern Middlesex COG Northern Middlesex COG Northern Middlesex COG Northern Middlesex COG
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
4161 BG 4161 BG 4161 BG 4161 BG 4161 BG 4161 BG 4161 BG 4161 BG 4161 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 2601 BG 5301 BG 4561 BG 4561 BG 4561 BG 4561 BG 4561 BG 4561 BG 4561 BG 4561 BG 4561 BG
183
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25005 25021 25021 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25023 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25013 25015 25015 25015
20100 02935 67945 00170 08085 09000 18455 27795 28495 33220 52630 54310 54415 75260 79530 00765 06085 08470 13485 13660 19645 26675 28075 30665 30840 36300 37175 42145 42530 52105 58650 65825 67000 70045 72390 76030 77850 79740 01325 04825 13590
Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Old Colony Planning Council Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC
184
MPO
MPO
Code Geography
1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 1201 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG
April 29, 2015
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts Massachusetts
25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25015 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25005 25021 25023 25023 25023 25023
16040 19330 26290 26535 27690 29265 31785 40990 46330 52560 54030 62745 64145 72880 76380 79915 82175 00520 02690 05280 16425 16950 22130 23000 25240 38225 45000 46575 49970 56060 56375 60645 62430 68750 69170 77570 54100 11665 33920 38540 39450
Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Pioneer Valley PC Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev.
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 8001 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG 2481 BG
185
Federal Transit Administration STOPS v1.50 Users Guide
New England FIPS STCOU FIPS
States
MCD
MPO Name
Massachusetts
Massachusetts
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
25023 25023 25023 33013 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005 33005
40850 57600 72985
Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev. Southeastern Reg. Plan. & Econ. Dev.
37300 00820 12260 19140 26500 29220 34420 36660 38500 39300 45460 45700 50580 64420 64580 65700 73700 74900 75300 75700 77380 78420 82660 85540
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
186
MPO
MPO
Code Geography
2481 BG 2481 BG 2481 BG
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
April 29, 2015
New England States
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
FIPS STCOU FIPS MCD
MPO Name
33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011 33011
01300 08100 37140 37940 42260 44580 47540 48020 49140 50260 59940 85220 04500 29860 45140 50740 79780 01700 04900 17780 27140 31540 31940 33700 36180 46260 51940
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
187
Federal Transit Administration STOPS v1.50 Users Guide
New England States
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
FIPS STCOU FIPS MCD
MPO Name
33011 33011 33011 33011 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013 33013
60580 68820 76260 85940 00660 01460 06260 06500 06980 09860 12420 14200 16980 19460 24900 27380 35540 35860 37540 43380 50900 52100 54260 60020 61940 66980 75460
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
188
MPO
MPO
Code Geography
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
April 29, 2015
New England States
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
FIPS STCOU FIPS MCD
MPO Name
33013 33013 33013 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015
78580 80020 84900 02340 17140 32900 40100 52900 62500 66660 67620 85780 07220 21380 24660 25380 27940 31700 33060 33460 39780 50980 51380 51620 52340 54580 56820
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
189
Federal Transit Administration STOPS v1.50 Users Guide
New England States
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
FIPS STCOU FIPS MCD
MPO Name
33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33015 33017 33017 33017 33017 33017 33017 33017 33017 33017 33017 33017 33017 33017 33011
57460 62900 66180 68260 71140 74340 02820 09300 12100 17460 17940 43220 64020 03460 18820 19700 26020 41460 44820 47700 48660 51220 65140 65540 69940 73860 01300
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Nashua RPC
190
MPO
MPO
Code Geography
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
1126 TAZ
5351 BG
April 29, 2015
New England States
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
FIPS STCOU FIPS MCD
33011
08100 Nashua RPC
MPO Name
33011
37140 Nashua RPC
33011
37940 Nashua RPC
33011
42260 Nashua RPC
33011
44580 Nashua RPC
33011
47540 Nashua RPC
33011
48020 Nashua RPC
33011
49140 Nashua RPC
33011
50260 Nashua RPC
33011
59940 Nashua RPC
33011
85220 Nashua RPC
33015
02340 Salem Plaistow Windham MPO
33015
17140 Salem Plaistow Windham MPO
33015
32900 Salem Plaistow Windham MPO
33015
40100 Salem Plaistow Windham MPO
33015
52900 Salem Plaistow Windham MPO
33015
62500 Salem Plaistow Windham MPO
33015
66660 Salem Plaistow Windham MPO
33015
67620 Salem Plaistow Windham MPO
33015
85780 Salem Plaistow Windham MPO
33003
07940 Sea Coast MPO
33003
78180 Sea Coast MPO
33015
07220 Sea Coast MPO
33015
21380 Sea Coast MPO
33015
24660 Sea Coast MPO
33015
25380 Sea Coast MPO
33015
27940 Sea Coast MPO
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
5351 BG
5351 BG
5351 BG
5351 BG
5351 BG
5351 BG
5351 BG
5351 BG
5351 BG
5351 BG
5351 BG
7061 TAZ
7061 TAZ
7061 TAZ
7061 TAZ
7061 TAZ
7061 TAZ
7061 TAZ
7061 TAZ
7061 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
191
Federal Transit Administration STOPS v1.50 Users Guide
New England States
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
FIPS STCOU FIPS MCD
33015
31700 Sea Coast MPO
33015
33060 Sea Coast MPO
33015
33460 Sea Coast MPO
33015
39780 Sea Coast MPO
33015
50980 Sea Coast MPO
33015
51380 Sea Coast MPO
33015
51620 Sea Coast MPO
33015
52340 Sea Coast MPO
33015
54580 Sea Coast MPO
33015
56820 Sea Coast MPO
33015
57460 Sea Coast MPO
33015
62900 Sea Coast MPO
33015
66180 Sea Coast MPO
33015
68260 Sea Coast MPO
33015
71140 Sea Coast MPO
33015
74340 Sea Coast MPO
33017
03460 Sea Coast MPO
33017
18820 Sea Coast MPO
33017
19700 Sea Coast MPO
33017
26020 Sea Coast MPO
33017
41460 Sea Coast MPO
33017
44820 Sea Coast MPO
33017
47700 Sea Coast MPO
33017
48660 Sea Coast MPO
33017
51220 Sea Coast MPO
33017
65140 Sea Coast MPO
33017
65540 Sea Coast MPO
MPO Name
192
MPO
MPO
Code Geography
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
6451 TAZ
April 29, 2015
Federal Transit Administration STOPS v1.50 User Guide
New England States
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire
New Hampshire Rhode Island
Rhode Island
Rhode Island
Rhode Island
Rhode Island
Rhode Island
Rhode Island
Rhode Island
Rhode Island
Rhode Island
Vermont
Vermont
Vermont
Vermont
Vermont
Vermont
Vermont
Vermont
FIPS STCOU 33017
FIPS MCD
69940 Sea Coast MPO
MPO Name
33017
73860 Sea Coast MPO
33011
04500 Southern New Hampshire PC
33011
29860 Southern New Hampshire PC
33011
45140 Southern New Hampshire PC
33011
50740 Southern New Hampshire PC
33011
79780 Southern New Hampshire PC
33013
37300 Southern New Hampshire PC
33015
02820 Southern New Hampshire PC
33015
09300 Southern New Hampshire PC
33015
12100 Southern New Hampshire PC
33015
17460 Southern New Hampshire PC
33015
17940 Southern New Hampshire PC
33015
43220 Southern New Hampshire PC
33015
64020 Southern New Hampshire PC
44001 44003 44005 44007 44009 44001 44003 44005 44007 44009 50001 50001 50001 50001 50001 50001 50001 50001
all all all all all all all all all all 00325 08575 09025 16000 26275 28600 29575 31525
Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Central Transportation Planning Rhode Island Statewide Planning Program Rhode Island Statewide Planning Program Rhode Island Statewide Planning Program Rhode Island Statewide Planning Program Rhode Island Statewide Planning Program Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO
MPO
MPO
Code Geography
6451 TAZ
6451 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
4761 TAZ
1126 TAZ 1126 TAZ 1126 TAZ 1126 TAZ 1126 TAZ 6481 TAZ 6481 TAZ 6481 TAZ 6481 TAZ 6481 TAZ 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG
193
Federal Transit Administration STOPS v1.50 Users Guide
New England States
Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont
FIPS STCOU FIPS MCD
MPO Name
50001 50001 50001 50001 50001 50001 50001 50001 50001 50001 50001 50001 50001 50001 50001 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50007 50011 50011 50011 50011 50011 50011 50011 50011
39325 40075 44350 45550 48700 53725 53950 59650 62575 65050 70075 74650 76075 83275 83800 06550 10300 10675 13300 14875 24175 33475 34600 36700 45250 59275 62050 64300 66175 73975 80350 84475 85150 02500 05425 23875 24925 25225 26500 27100 27700
Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO
194
MPO
MPO
Code Geography
1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 TAZ 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG
April 29, 2015
New England States
Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont Vermont
FIPS STCOU FIPS MCD
MPO Name
50011 50011 50011 50011 50011 50011 50011 50013 50013 50013 50013 50013 50015 50015 50015 50015 50015 50015 50015 50015 50015 50015 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023 50023
33025 45850 59125 61675 61750 64600 71725 00700 29275 35875 50650 67000 04375 11500 23500 23725 35050 37075 46675 70525 77425 85375 03175 03250 05650 11125 11350 18550 21925 25825 43600 44500 46000 46225 50275 55825 60625 75325 76525 76975 85525
Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO Chittenden County MPO
Federal Transit Administration STOPS v1.50 User Guide
MPO
MPO
Code Geography
1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG 1306 BG
195
Federal Transit Administration STOPS v1.50 Users Guide
New England States
Vermont
FIPS STCOU FIPS MCD
MPO Name
50023
86125 Chittenden County MPO
MPO
MPO
Code Geography
1306 BG
196
April 29, 2015
Microsoft Word 2010