3/14/2017 Southeast Florida STOPS Planning Model Overview Southeast Florida FSUTMS Users Group Meeting Florida Department of Transportation, District 4 March 10, 2017 1 Introductions u Department Contacts u Hui Zhao / [email protected] / 954-777-4635 u Shi-Chiang Li / [email protected] / 954-777-4655 u Instructors u Ashutosh Kumar / [email protected] / 754-812-7240 u Sujith Rapolu / [email protected] / 754-812-7241 u Hongbo Chi / [email protected] / 305-514-2431 u Yongquiang Wu / [email protected] / 954-637-1612 2 1 3/14/2017 Agenda u Overview of STOPS u Overview of the SEFL STOPS Planning Model u Motivation and user interface u Input data u Post processing user interface u Calibration results u Forecasting for Your Project u Model Applications u Central Broward Transit u SR 80 3 STOPS Overview and Motivations for SEFL STOPS Planning Model 4 2 3/14/2017 STOPS Overview u Simplified Trips On Project Software – for transit ridership forecasting u Developed and maintained by FTA u Limited implementation of the conventional ‘four-step’ trip-based model u Uses readily-available inputs such as census, ACS, MPO Population and Employment, GTFS etc. u Nationally calibrated, with adjustments made for local transit and fixed guideway systems 5 STOPS’ Purposes u Primary Focus – To provide a simplified method to produce measures for fixed-guideway projects applying for FTA’s Capital Investment Grant (CIG) funding u Using STOPS beyond its primary purposes… u QA/QC ridership forecasts u Systems planning SEFL STOPS Planning Model u Service planning u Sizing of stations and mode-of-access facilities u Before-After comparisons 6 3 3/14/2017 FTA’s website currently has STOPS version 1.50. STOPS Interface and FTA Resources SEFL STOPS uses version 2.0 beta. FTA provides example application and other resources at https://www.transit.dot.gov/funding/grant-programs/capital- 7 investments/stops-%E2%80%93-documentation-and-software Other Resources u FTA Planning Staff u Check for most recent STOPS versions, data and guidelines u Provide technical guidance on STOPS u FTA’s “Forecasting with STOPS” course materials from workshops held in Orlando and Los Angeles (May and June 2016) u National Transit Institute will offer this course again in 2017 u FDOT’s “Guidebook for Florida STOPS Applications” http://www.fsutmsonline.net/index.php?/site/comments/guidebook_for_florida_stops_applications/ 8 4 3/14/2017 Resource Requirements Hardware Software Personnel/Staff • 8GB RAM required • Windows 7 or later • Good understanding of • 4- or 8-core processor • ArcMap version 10.1+ travel forecasting • 40-100GB of hard disk • Good text editor • Experience with GIS storage per project • Good spreadsheet software packages • GTFS visualizer • Familiarity with the transit system and local area 9 Advantages of Using STOPS u FTA requires substantially less review time of STOPS ridership forecasts for CIG projects u STOPS models can typically produce more analyses than regional travel models within the same time u STOPS has embedded mapping routines that easily display and communicate results 10 From FDOT’s workshop on Guidebook for Florida STOPS Application 5 3/14/2017 Limitations to Using STOPS u STOPS does not provide a direct interaction with the roadway network u The GTFS editing process can be cumbersome u STOPS’ representation of non-work trips is less certain than its representation of work trips u STOPS is limited in its ability to analyze alternatives beyond its supplied metrics (Example: transit capacity analysis has to be performed offline) u Future year travel patterns are based on existing patterns and the user-supplied population and employment forecasts (Other variables such as accessibility are not considered) 11 From FDOT’s workshop on Guidebook for Florida STOPS Application Not mentioned in the v1.50 documentation Additional STOPS 2.x Features currently on FTA’s website u ACS 2006-2010 data can be used to represent Journey-to-Work (JTW) flows u Calibration to linked transit trips by purpose (HBW, HBO and NHB) and by market segment (0-car, 1-car, 2-car HHs) u Boarding/transfer penalty can be changed, which directly impacts the overall transfer rate u Transit O/D survey can be used to develop “Incremental” STOPS model u Ability to model ‘special’ markets 12 6 3/14/2017 Motivations u Why STOPS? u Quicker turnaround for ridership forecasting and analysis u Provide basis for FTA Capital Investment Grant applications (“New/Small Starts”) u An independent tool to QA/QC forecasts from SERPM or data-driven models u Why SEFL STOPS Planning model? u Provide a common “ready to go” platform for upcoming transit corridor studies u Utilize a common set of reconciled data and assumptions for all corridors u Fewer resources needed for corridor calibration/validation, compared to SERPM 13 SEFL STOPS Planning Model 14 7 3/14/2017 SEFL STOPS Planning Model Characteristics u Developed using STOPS version 2.0 beta (2/19/2016) u Covers the three SERPM counties Miami-Dade, Broward and Palm Beach u A separate Excel user interface let’s users apply the model for one county u Represents average weekday travel u Model base/current year: 2015 u Horizon year: 2040 u STOPS input files already prepared à should be reviewed/updated for individual corridors 15 Define folder structure so that the STOPS The Model You Received control file is <80 characters in length u ~500 MB zipped file u Model Data/Interface SEFL STOPS Planning model user guide and calibration 16 report supplements FTA’s STOPS user guide. 8 3/14/2017 SEFL STOPS Planning Model User Interface Motivations u Model runtime for the tri-county region can be up to 4-7 hours u Most projects will only have localized impacts within a given county/corridor u Better quality and more detailed data may be available at a county/corridor level u STOPS ASCII report file not easy to process/analyze 17 SEFL STOPS Planning Model User Interface What it Does? u Automates the preparation of “some” input files for any corridor in the region u Uses data already collected and reconciled as part of this effort u Extracts user specified table numbers from the STOPS output report file into Excel u Prints extracted worksheets to PDF format in batch mode 18 9 3/14/2017 Initial files should be developed using the User Interface and Folder Setup interface to save significant setup time Excel Macro file containing the user interface Module 1: Prepare Input files Module 2: Post Processing 19 of STOPS results Input Module and Data Assembled 20 10 3/14/2017 Input Module: What it Does? u Copies all the required input files for a selected geography u Creates a scenario folder and a default STOPS control file, appropriately edited to reflect the attributes of the geographic region selected 21 Geographic region selection discussed User Interface: Input Module late r. 1. Location of ArcMap exe file 2. Location of Python exe file A new folder containing 3. User specified scenario name preliminary input data is created using the Scenario Name 4. User specified STOPS control file name 22 11 3/14/2017 Wait for the confirmation window for User Interface: Input Module (Contd.) successful completion of Prepare Input Files step. This step can take up to a minute to complete. 23 User Interface: Input Module (Contd.) u Three folders and STOPS control file are copied 24 12 3/14/2017 Input Module: What is Copied? u STOPS software files u Pre-defined districts definition for the tri-county region u ACS Part I, II and III files, Census block boundary files u ACS state shape layer; depends on the geographic region selected u GTFS files; depends on the geographic region selected u MPO population and employment data u Auto skim file; depends on the geographic region selected u STOPS stations shape layer containing the existing fixed guideway stations and bus stops with ridership data; depends on the geographic region selected u STOPS control file, appropriately edited to reflect the attributes25 of the geographic region selected Input Module: What is Copied? (Contd.) Files copied in the ‘Inputs’ folder Page 26 13 3/14/2017 Input Module: What is Copied? u STOPS software files u Pre-defined districts definition for the tri-county region u ACS Part I, II and III files, Census block boundary files u ACS state shape layer; depends on the geographic region selected u GTFS files; depends on the geographic region selected u MPO population and employment data u Auto skim file; depends on the geographic region selected u STOPS stations shape layer containing the existing fixed guideway stations and bus stops with ridership data; depends on the geographic region selected u STOPS control file, appropriately edited to reflect the attributes27 of the geographic region selected Input Module: What is Copied? STOPS Software u 2.0 Beta Version (2/19/2016) u No formal 2.0 documentation from FTA u Version used for FTA’s STOPS course in May and June u Use the interface to open STOPS menu 28 14 3/14/2017 Input Module: What is Copied? u STOPS software files u Pre-defined districts definition for the tri-county region u ACS Part I, II and III files, Census block boundary files u ACS state shape layer; depends on the geographic region selected u GTFS files; depends on the geographic region selected u MPO population and employment data u Auto skim file; depends on the geographic region selected u STOPS stations shape layer containing the existing fixed guideway stations and bus stops with ridership data; depends on the geographic region selected u STOPS control file, appropriately edited to reflect the attributes29 of the geographic region selected Users must define districts for their Input Module: What is Copied? corridor.