Transit organizations typically offer two distinctly different types of service: Demand Responsive Transportation (DRT) and fixed route transportation. Fixed route transportation operates according to prescribed routes and schedules whereas DRT does not. In this lesson, we will look at both of these types of transit.
Demand Responsive Transportation (DRT)
DRT is generally designed to provide curb to curb or door to door service for individuals who have special transportation needs such as seniors and persons with disabilities. The availability of DRT services can vary significantly from state to state and even county to county based on funding availability. DRT differs from taxi service in two fundamental ways:
- To use DRT, a rider must make an advance reservation (generally, at least 24 hours in advance).
- DRT is a shared-ride type service where multiple riders can be serviced at the same time and a rider is generally not taken directly from their point of origin to their point of destination. Consequently, DRT trips can have substantially longer ride time than taxi trips.
DRT services are generally designed to serve rural areas where fixed route transit is not practical due to low ridership and also to complement fixed route services for those who live near a fixed route but are unable to use it due to physical or cognitive limitations.
ADA Complementary Paratransit
The Americans with Disabilities Act (ADA) of 1990 prohibits discrimination against persons with disabilities in a number of areas including public transportation. The FTA has defined a series of requirements public transit providers need to meet to comply with the ADA. These requirements are found in Title 49 Part 37 of the Code of Federal Regulations (CFR). In these regulations, the FTA requires fixed route providers to provide DRT service, comparable to the level of service provided to individuals who are able to utilize fixed route services, to persons with disabilities. DRT services designed to address the needs of persons with disabilities is known as paratransit service. Specifically, bus or rail fixed route providers are required to offer paratransit services to individuals who are unable to use the fixed route service due to physical and/or cognitive limitations, who live within ¾ of a mile of a fixed route and are traveling to a destination which is also within ¾ of a mile of a fixed route. This requirement is challenging and costly for transit providers to fulfill. It applies to all providers, and not just those who are receiving federal funding. It is also an unfunded mandate in that FTA does not provide grant monies to transit agencies to help offset the cost of compliance. You’ll complete an assignment next week to evaluate the eligibility of a series of trips for complementary paratransit service.
Technologies for DRT Services
Providing DRT services in a way which is both cost effective and customer friendly is a very challenging task. The number of riders requesting service can vary substantially from day to day as can the trip origins and destinations. Service requests are initiated by riders through a call to a Customer Service Representative (CSR). Reservations typically need to be made at least 24 hours before service. Generally, the day before services are delivered, schedulers need to determine how to accommodate all of the reservations for the day with a limited number of vehicles and drivers. Further, the schedulers need to ensure a wide variety of constraints are met including promised pickup time, required drop off times (e.g., for medical appointments) and total ride time. On the day of service, dispatchers work with the drivers to ensure all trips are successfully completed. Drivers follow a trip manifest which defines which stops they will visit and the order in which they will visit them. Drivers also need to track a variety of data elements at each stop including arrival and departure times, the passengers boarding and alighting at each stop, the vehicle odometer reading, and the amount of money collected from each passenger.
For all but the smallest providers, it would be very difficult to manage DRT service without technology. The most important technology which providers use is DRT software. Most DRT software assists the providers with all of the key tasks associated with delivering and reporting on the service. Many systems incorporate Automatic Vehicle Location (AVL) technology, which allows the dispatcher to monitor the location of all of their vehicles. This can be extremely useful in terms of ensuring drivers stay on task and follow the manifest. Some of the more sophisticated packages can do automated scheduling. These systems determine the best vehicle for a given trip reservation. DRT scheduling is very complex owing to the large number of variables involved, many of which are related to human behavior, and as a result, even software that can do automated scheduling cannot produce good schedules without significant scheduler oversight.
Interactive Voice Response (IVR) technology is also playing an increasingly important role in DRT operations. Typically, systems which incorporate IVR will configure the system to automatically call riders the night before a scheduled trip to remind them of the trip and give them an opportunity to cancel the trip. Systems will also generally automatically call the riders when the vehicle is approaching their location. These calls, known as imminent arrival calls, are valuable for both the provider and riders. Providers benefit because the calls ensure riders will be ready, and riders benefit since the calls give them a clear idea of when to be ready and eliminate the need for them to wait outside for a prolonged period. IVR plays a significant role in reducing “No-Shows” where the driver gets to a location to pick up a rider and the rider is not there. No-shows add additional costs to a service which is already expensive to provide.
Many providers give their drivers Mobile Digital Computers (MDC) which serve a variety of functions. More and more DRT software vendors are shifting to tablet technology instead of using proprietary hardware. MDCs provide additional communications with dispatch via canned or ad hoc text messages. The MDCs also generally present the trip manifest information to the driver in an electronic form and tell the driver their next stop location, how well they are adhering to the schedule, how many passengers should be boarding and alighting at each stop, and how much money they should collect from each person. The driver also uses the MDC to capture the information they need to collect such as the stop arrival time, the passengers who boarded and who alighted the vehicle at the stop, how much they collected from each rider, and what time they departed from the stop. MDCs can also be configured to provide the driver with turn by turn directions and eliminate the need for a separate GPS device.
Transit agencies use a number of different methodologies to establish a fare structure for their DRT services. The three most common are listed below:
Flat – In a flat fare structure, as the name implies, the cost of the trip is the same regardless of origin and destination, assuming both are within the agency’s service area.
Zone-Based – In a zone-based fare structure, the agency divides its service area into zones. The zones are generally comprised of a series of concentric circles or a rectangular grid which blankets the service area. Fares are then established for each origin and destination zone.
Mileage-Based – In a mileage-based fare structure, the agency develops a series of mileage-based tiers and associates a fare with each. The mileage associated with each trip depends only on the origin and destination and not on other pickups or drop-offs the driver may have performed while the passenger is in the vehicle. Consider the following example:
Ellen makes a reservation to go to the senior center on Monday at 10 am. On Friday afternoon, the agency’s scheduler is working with their paratransit software to finalize the driver manifests (i.e., schedules) for Monday morning. This process involves determining the most efficient way to deliver the service while at the same time observing customer service policies such as ensuring all riders get to their appointments on time and do not exceed the maximum onboard time established by the agency. On Monday morning, the drivers depart the transit agency and begin to execute the manifests (i.e., schedules) that have been prepared for them. The driver assigned to pick up Ellen arrives at her house to pick her up at 8:45 am. The driver then drives to Allen’s house to pick him up and on to Sue’s house to pick her up. He then drives to the VA hospital to drop off Allen and to Walmart to drop off Sue. Finally, he drives to the senior center and drops Ellen off at 9:50 am.
The driver may have visited many stops while Ellen was on the vehicle, but the mileage used for fare determination is based only on the route from her origin to her destination. When an agency uses a mileage-based fare structure, they can base the mileage on the fastest route from the origin to destination or the shortest distance route from the origin to destination.
Assignment 9-1 (20 points)
In this assignment, you’ll use Network Analyst to examine the revenue impacts of changing the way a transit agency calculates fares for DRT service. Address the items below, and submit your responses in the form of an M.S. Word document to Assignment 9-1 in Canvas.
ABC Transit, a fictitious transit agency in San Francisco, has a mileage-based fare structure which is based on the following 7 tiers:
|Trip Distance (miles)||Fare|
ABC Transit bases the trip distance on the fastest route between the origin and destination. However, some riders have measured the distance of their trips themselves and have complained that ABC Transit is not using the correct mileage. To avoid these types of rider complaints, ABC Transit is considering using the short route to determine trip distances for fare determination. However, before doing so, they want to determine what impact this change will have on their annual revenue. In this assignment, you will use a day’s worth of trip requests to estimate the impacts on annual revenue. In practice, you would use a much larger sample of historical data (perhaps 3 months).
For this assignment you should complete the following steps:
- Create a new map document.
- Add the network dataset you created for San Francisco in Lesson 5.
- Download and unzip the TripODs shapefile which contains the origins and destinations for the trips ABC Transit delivered over the course of 1 day.
- Add the TripODs to the map document you created. Note that the TripODs feature class has attributes named “RouteID” and “Sequence.” “RouteID” is used to indicate which origins and destinations are paired together. “Sequence” is used to indicate their order. Features with a Sequence of 1 are origins and those with a Sequence of 2 are destinations.
- Use the Route Solver in Network Analyst to determine the trip distances based on shortest travel time:
- Create a new Route Solver analysis.
- Right-click Stops in the Network Analysis window and select Load Locations.
- In the Load Locations dialog box make sure the TripODs feature class is specified in the “Load From” drop-down and that the RouteID field is mapped to the RouteName property in the “Location Analysis Properties” section of the dialog. Also, select the Sequence field in the “Sort Field” drop-down. Click “Ok” to load the locations. After a short time, you should see that 734 stops were loaded.
- Open the Analysis Properties dialog (top right corner of the Network Analyst window) and set the Impedance to “Travel Time (minutes)” on the Analysis Settings tab. Also, check the Accumulation Attributes “TravelTime” and “Meters” on the Accumulation tab. Click “Ok” to close the window.
- Click the Solve icon on the NA toolbar to find the fastest route for each trip.
- Include a screenshot of the map showing the fastest routes. (2 points)
- Use the Copy Features tool to make a copy of the Routes feature class. Name the copy “FastestRoutes”.
- In the newly created FastestRoutes feature class, add two new fields. The first should be named “FastestDistance” (data type – double), and the second should be named “FastestFare” (data type – Short Integer).
- Use the field calculator to populate the newly created FastestDistance field with the trip distance in miles. (Hint: Use the Total Meters field and the conversion factor 1 mile=1609 meters.)
- Use the field calculator to populate the newly created Fastest Fare field. To do this select the Python parser, check the “Show Code Block” checkbox, and paste the following Python function into the “Pre-Logic Script Code” box:
def Fare(TripDist): if TripDist < 1: return 8 elif TripDist < 2: return 10 elif TripDist < 3: return 15 elif TripDist < 5: return 20 elif TripDist < 10: return 25 elif TripDist < 20: return 35 else: return 50
Then enter “Fare(!FastestDistance!)” in the lower box of the field calculator window. This will call the custom function you pasted in the “Pre-Logic Script Code” box. Click “Ok” to close the dialog and calculate the Fastest Fare.
- Examine the attribute table for the FastestRoutes feature class and enter the following data for Trips 113 and 139 into the Word document: Total_TravelTime, Total_Meters, FastestDistance, and FastestFare. (5 points)
- Rerun the analysis to find the shortest routes:
- Change the impedance to “Meters (Meters)” and click the Solve icon on the NA toolbar.
- Include a screenshot of the map showing the shortest routes. (2 points)
- Use the Copy Features tool to make a copy of the Routes feature class. Name the copy “ShortestRoutes”.
- In the newly created ShortestRoutes feature class add two new fields. Name the first field “ShortestDistance” (data type – double) and name the second “ShortestFare” (data type – Short Integer).
- Use the field calculator to populate the newly created ShortestDistance field with the trip distance in miles.
- Use the field calculator to populate the newly created ShortestFare field. To do this select the Python parser, check the “Show Code Block” checkbox and paste the following Python function into the “Pre-Logic Script Code” box:
def Fare(TripDist): if TripDist < 1: return 8 elif TripDist < 2: return 10 elif TripDist < 3: return 15 elif TripDist < 5: return 20 elif TripDist < 10: return 25 elif TripDist < 20: return 35 else: return 50
Then enter “Fare(!ShortestDistance!)” in the lower box and click Ok to close the dialog and calculate the Shortest Fare.
- Examine the attribute table for the ShortestRoutes feature class and enter the following data for Trips 113 and 139 into the Word document: Total_TravelTime, Total_Meters, ShortestDistance, and ShortestFare. (5 points)
- Use the Copy Features tool to make a copy of the FastestRoutes feature class. Name the copy “RouteCompare”.
- Add a new field to the RouteCompare feature class called “ChangeInRevenue”.
- Join the “ShortestRoute” feature class to the “RouteCompare” feature class.
- Use the field calculator to populate the ChangeInRevenue field with the difference between the ShortestFare and the FastestFare.
- Right-click on the “ChangeInRevenue” field and select “Statistics”. How will the adjustment in fare determination methodology change the revenue collected for the day? (3 points)
- Assuming the day we analyzed is representative of their service throughout the year and assuming they operate 7 days a week, what is the expected annual impact of changing the fare determination method from fastest distance to shortest distance? (3 points)
Fixed Route Transit
Fixed route transit services can be defined as services which operate on predefined routes according to a set schedule. The services can be divided into a number of more specific modes including:
- Local Bus
- Commuter Bus
- Express Bus
- Bus Rapid Transit
- Light Rail
- Ferry Boat
Routes and Patterns
Fixed route buses operate on designated routes according to a published schedule. One can think of routes as generalized paths buses follow. For example, Route 1 may be structured to provide service along Market Street. It may begin at a transit center where riders can transfer from one route to another or even to a different mode such as light rail or subway and travel along Market Street until it reaches some terminal point at which time it returns along Market Street to the transit center. The specific path each route traverses can depend on the time of the day, the day of the week, and even the time of year (e.g., summer service). Each distinct path associated with a route is called a pattern. As an example, Figure 1 and Figure 2 show two patterns for the same route. The route generally follows Pattern 1, but at times during the day when the YMCA is busiest, it follows a somewhat different pattern.
Trips, Headway, Interlining, and Vehicle Blocks
When one uses the term trip in regards to DRT, it generally refers to the transport of a rider from their point of origin to their desired destination. In fixed route, the term trip has a different meaning. Over the course of a day, service along a route will generally be offered a number of times. For example, service along Market Street, in the above example, may occur at a frequency of twice an hour from 9 am to 4:30 pm, with a bus leaving the transit center every 30 minutes. In the world of fixed route, a trip corresponds to a bus completely traversing the route one time. The period of time between each trip is called the headway. In this example then, there are 16 trips and the headway is 30 minutes. If it takes more than 30 minutes to complete a single trip, then it will take multiple buses to provide service along Market Street. Sometimes a bus will operate a single route the entire day, and sometimes a bus will service multiple routes. When a bus completes a trip on one route and then begins a trip on a second route, it is referred to as interlining. A bus's schedule for an entire day is called a block. For example, Bus 2a may operate on Route 1 from 9 am to 12:30 pm, at which time it is used on Route 2 from 1 pm to 5 pm. The block for Bus 2a would be the sequential set of trips it completes over the course of the day on Routes 1 and 2.
Stops, Time Points, and On-Time Performance
A stop is a designated location along a route where riders can get on or get off the bus. The bus is obligated to stop at certain stops known as time points. These are stops that appear on the bus schedule. Generally, a transit agency will have a policy that a bus should not depart a time point before the scheduled time. How well a transit provider adheres to its published schedule is referred to as its on-time performance. It is important for transit providers to adhere to their schedules since riders depend on transit to get to their destinations on time. There are also stops along a route which are not time points. The bus will only stop at these stops if a rider is waiting at the stop or if a rider wishes to alight the vehicle at the stop. In addition to defined stops, some providers accommodate flag stops. A flag stop is an arbitrary location along the route where a rider wishes to board or alight the bus. The rider needs to flag the bus down in order to board or alert the driver they wish to alight the bus at that location.
Runs and Run Cutting
Sometimes a single driver will operate on the same bus and route all day long. At others times, the driver may operate on a number of buses and/or routes over the course of the day. The collection of trips a driver performs over the course of their shift is known as a run. Just as a block represents a bus' schedule for the day, a run represents the driver's schedule for the day. Matching drivers with the pieces of work a transit provider needs to staff is known as run cutting. Run cutting can be a complex process at least in part because drivers and other staff often belong to a union, and the labor agreements which have been negotiated can have many different rules which need to be followed.
Fixed Route Technologies
Fixed route providers use a large number of technologies to manage operations and provide good customer service. The most significant of these technologies are described briefly below:
There are a variety of fare collection technologies which fixed route providers use to collect and securely store fares. Some fare boxes are able to assist the driver in verifying that cash-paying riders provided the correct fare. Registering fare boxes are able to count coins and bills, but they cannot differentiate between different denominations of bills. For example, a registering farebox can’t tell the difference between a one dollar bill and a twenty dollar bill. Validating fare boxes can do everything a registering fare box can do and, in addition, can differentiate between different denominations of bills. Registering and validating fareboxes also generally allow the drivers to keep track of the types of passengers who are boarding (e.g., seniors, persons with disabilities, children, etc.). For providers who have relatively low ridership, it is difficult to justify the cost of registering or validating fare boxes. For these types of providers, a vault style fare box is often the most logical choice. A vault style fare box does not count cash payments. Instead, the upper compartment is generally transparent which allows the driver to confirm the correct fare was provided before it is dropped into the lower compartment. Many providers are moving toward providing more flexible payment options. Touch cards are a convenient type of fare media which are growing in popularity. Riders can generally add additional value to these cards using a ticketing machine or via the web.
Computer Aided Dispatch / Automatic Vehicle Location (CAD/AVL)
Many transit organizations who operate a fixed route bus service use CAD/AVL. CAD/AVL systems consist of onboard hardware to track the buses, and software which helps the dispatchers to manage service as it occurring and resolve issues as they arise. CAD/AVL allows the dispatcher to see where all the agency's vehicles are on a map and to quickly determine which are on schedule and which are ahead of schedule or behind schedule.
Automatic Passenger Counters (APC)
APCs are simple devices which are mounted by each door and count the number of passengers boarding and alighting the bus. While there are different types of APCs on the market, the most common employ a series of infrared beams. Each time the beams are broken, the system counts it as either a boarding or alighting. During busy times, the devices can miss a passenger here and there. The devices can also have a hard time with children, especially if they are carried onto the bus. The data collected via APCs can be used to determine the current onboard passenger count, a piece of information that is sometimes made available to the riding public along with other real-time bus information. Transit agencies sometimes also use APC data to fulfill part of their reporting NTD requirements to the FTA but, in order to do so, they need to demonstrate that their APCs meet certain accuracy requirements. You'll learn about NTD reporting later in this lesson.
Automated Announcement Systems (AAS)
In order to comply with ADA requirements, fixed route vehicles are generally equipped with an AAS which provides both audible announcements and visual announcements about upcoming stops and points of interest. These systems are generally triggered based on the vehicle's position as it approaches a designated location. Most systems utilize geofences to determine when an onboard announcement should be made.
Most fixed route vehicles are equipped with camera systems which record activities on the bus as well as outside the bus. It is common for a bus to have 6 separate audio and video streams with some of the larger articulated buses being equipped with 8 separate streams. The video from these buses is stored in onboard DVRs and can be streamed by dispatch if needed. The DVR capacities are generally sufficient to store a few weeks of video before overwriting. The systems are configured to automatically flag sections of video in the event the system senses any unusual forces due to a collision or abrupt deceleration or turn. The driver can also press a button to manually flag a section of the video. When the system flags a section of the video, it preserves a window of time which brackets the triggering event for later review. Flagged sections of video are often wirelessly downloaded when the bus returns to the depot. Vehicle surveillance systems are extremely useful for identifying undesirable driver behaviors and incidents onboard the bus, as well as helping to determine the cause of any bus-related accidents. Local police are also sometimes interested in this video if they believe it may be of use in solving or prosecuting a case.
Real Time Passenger Information
Real time passenger information systems have become extremely popular in recent years. These systems make real-time bus information available to riders via web applications, smartphone applications, and dynamic message boards which are sometimes located as transit centers or other high traffic stops. In Lessons 8 and 9, we looked at an example of one which CATA uses called MyStop.
Transit providers often offer rider alert systems to notify users about disruptions in services or to provide other types of notifications. Riders can typically sign up for alerts related to specific routes and/or system-wide alerts.
Developing and adjusting routes, patterns, stops, trips, and blocks can be challenging especially for larger transit providers. Scheduling software is designed to assist agencies in this regard. Scheduling software also often incorporates some functions to assist with run cutting as well.
Vehicle Health Monitoring
Many buses come equipped with vehicle diagnostics that can transmit various vehicle health information back to the transit agency. This technology helps to ensure problems are taken care of before they lead to vehicle breakdown. Some vehicle health systems integrate with maintenance management systems and can automatically schedule vehicles for preventative maintenance.
Trip Planning/Google Transit
Many fixed route providers offer trip planning services to their riders. These services are generally web-based and allow the rider to indicate their origin, destination, and desired date and time of departure or date and time of arrival. The trip planning service then presents options which define a combination of walking and fixed route options that best meet their needs. The options may involve one or more transfers between fixed route vehicles. The most popular fixed route trip planning service is Google Transit. The idea for what has become Google Transit was first spawned by TriMet, a transit agency which services Portland, Oregon. TriMet approached MapQuest, Yahoo, and Google to see if they would be interested in incorporating transit data into their map products, but only Google replied. The Google Transit Trip Planner launched on December 7, 2005. Google transit incorporates stops, routes, schedule, and fare information for a provider’s bus, subway, rail, and/or light rail service. The service is automatically available as a free service via Google Maps in any area where one or more local transit providers publish their data to Google.
For most of the first year, TriMet was the only operator available on Google Maps. In September 2006, five more cities got on board: Eugene, OR; Honolulu, HI; Pittsburgh, PA; Seattle, WA; and Tampa, FL. Today, Google Transit spans many hundreds of cities.
In order for transit providers to submit their fixed route information to Google in a consistent way, a data specification was required. The specification which was developed for this purpose is discussed in the next section. As mentioned above, Google Transit is a free service to transit agencies and to the public who can perform trip planning in Google Maps. However, if you wish to tie into the capabilities programmatically to incorporate the power of Google Transit (or more generally Google Maps) into your own software application, there are often associated fees you need to consider. A popular and robust alternative open source trip planning system is Open Trip Planner.
General Transit Feed Specification (GTFS)
The specification which was developed to allow transit agencies to publish their fixed route data to Google Transit is known as GTFS. Originally it stood for the Google Transit Feed Specification, but in 2010, Google changed the name to the General Transit Feed Specification given its growing status as the default specification for transit data. GTFS is an open data standard which represents fixed-route schedule, route, and bus stop data in a series of 13 comma-delimited text files compressed into a ZIP file. Each of the 13 text files contains a series of fields or attributes about a component of the fixed route service. Some of the files and fields are optional (see Table 1).
A description of each table along with the meaning of each field is provided here.
The primary use of GTFS data is to publish fixed route schedule data to Google Transit so that riders can perform trip planning. However, there are many other potential uses for GTFS data. For example, transit planning software systems such as TBEST commonly allow users to upload route, stop, and schedule data in GTFS format. In the past few years, Google has created a new specification based on GTFS which incorporates real-time information in addition to the static schedule data. The new specification is known as GTFS Real Time and is starting to gain some traction among transit agencies, but is not yet widely used.
In Assignment 9-2 you’ll have a chance to work with GTFS data from a transit agency in Tampa, Florida. Specifically, you’ll use the route geometry contained in the shapes.txt component of the GTFS data to establish the zone for ADA complementary paratransit.
Assignment 9-2 (15 points)
In this assignment, you will use GTFS data to evaluate a series of trip requests to determine which are eligible for ADA complementary paratransit service. You will include all of the requested elements in an M.S. Word document and upload it to Assignment 9-2 in Canvas. To complete this assignment, download the DRT Trips shapefile and perform the following steps:
- Download the latest GTFS file for Hillsborough Area Regional Transit (HART).
- Create a new map document in ArcGIS.
- Add the Streets base map that is included in ArcGIS.
- Unzip the data in HART’s GTFS.zip file.
- Add the data in the Shape.txt file to the new map document.
- Create linear features from the points in the Shapes table by using the “Points to Line” tool in ArcToolbox. Each route pattern is designated with a unique value in the “Shape_ID” field. The “Sequence” field specified the order of the points in the pattern. Grab a screenshot of the resulting map showing the route patterns. (4 points)
- Create a single polygon representing the ADA complementary paratransit zone. (Hint: Use the “Buffer” tool and dissolve the resulting polygons). Symbolize the polygon in a way that makes it easy to identify but does not completely obscure the base map. Grab a screenshot of the resulting map. (4 points)
- Add the Trips files to the map and convert them to 2-point linear features as well. Display the linear trip features on the map and use the Trip ID (i.e., the value in the “Trip” field) to label the features. Include a screenshot of the resulting map. (4 points)
- Examine the trips to see if they are all eligible for ADA complementary paratransit. Report your findings. (3 points)
The following assignment is optional. You do not need to complete this assignment to fulfill the requirements of the course. TBEST is a powerful tool for transit planning and is available for free. If you have an interest in the tool, this assignment will help you to get some hands-on experience using it.
In this assignment, you’ll get a chance to get some hands-on experience with TBEST as you explore some of its many features. Prior to doing this assignment, you will need to download and install TBEST Version 4.4 for ArcGIS 10.5. As part of Assignment 8.6, you reviewed some tutorial videos which are available to help users learn how to use the features TBEST offers. In preparation for this assignment, watch the tutorial videos on scenarios, network tools, TBEST reporting, and the attribute search tool. TBEST also has a comprehensive users' guide available from both the website and the help menu within TBEST. Complete the following activities.
- Open TBEST.
- Download Socio-Economic data, GTFS Data, and a transit system logo
- Create a new transit system
- For this assignment, you’ll model Hillsborough Area Regional Transit (HART) which services Tampa in Hillsborough County.
- In the TBEST explorer window, right click “Transit Systems” and select “New System”.
- You will be prompted to select the source socioeconomic data. The only option you have is the data you downloaded in step 2. Select it and click “Ok”.
- On the “New Transit System” dialog, enter HART as the transit system name.
- Select Hillsborough County as the extent.
- Leave the remaining settings alone and click “Ok”.
- It will likely take 60-90 minutes to compile the socioeconomic data and parcel data for Hillsborough County, Florida.
- Create a new TBEST Scenario.
- In the TBEST explorer window, expand the HART transit system you created in step 5.
- Right click “Scenarios,” and select “Create a New Scenario…”
- Name the new scenario “2017 Base Conditions”.
- Select “TBEST Land Use Model 2016” as the scenario model (it is the only option).
- Enter “2017” as the Forecast Year.
- Select an average annual wage for Hillsborough County and enter it as the mean annual wage for the scenario.
- Enter “2” as the annual growth rate.
- Click “Ok” to create the new scenario.
- Create HART’s Fixed Route Network.
- You’ll create HART’s fixed route network by importing their latest GTFS data file. As an alternative, you could manually create the network in TBEST, but that would be time-consuming.
- In the TBEST explorer window, right click on the “2017 Base Conditions” scenario and select “Import Routes from GTFS”.
- On the TBEST GTFS Network Import dialog, select the GTFS.zip file downloaded in step 2b as the source GTFS zip file.
- Select the top three checkboxes (i.e., Weekday, Saturday and Sunday) to select all service periods.
- Click “Load Routes” to load all routes.
- Check “Select All” in the lower left corner of the dialog to select all routes.
- Click the “Import” button to begin importing the network.
- You will be prompted for confirmations 2 times. Click “Ok” to both.
- Once the network has been successfully imported (it should take about 10 minutes), you can exit the GTFS Network Import screen.
- Exploring HART’s Fixed Route Network.
- Right mouse click on the newly created “2017 Base Conditions” scenario and select “Open Scenario”.
- Grab a screenshot of the resulting map showing HART’s routes. (5 points)
- In the routes window, expand Route 1 – Florida Avenue.
- Expand the Northbound Patterns.
- Double click Pattern 40317.
- TBEST automatically highlights the pattern and associated stops on the map.
- In addition, the segments and stops are automatically populated in their respective windows.
- Grab a screenshot of the entire TBEST window with Pattern 40317 selected (2 points).
- TBEST has powerful search capabilities which allow you to find and select a group of stops, segments, or routes based on attribute filters. The search tool is available on the main TBEST toolbar (binoculars) or via the Scenario menu.
- Open the search tool and search for stops associated with express routes.
- To do so, select “Stops” as the Category, “Route Type” as the attribute, “Equal To” as the Operator (i.e., “Is”), and “Express” as the Value.
- Click “Add to Search Criteria” to add the filter.
- Click “Apply” perform the search.
- Grab a screenshot of the map showing the express route stops selected. (3 points)
- Group selecting routes, segments, and stops in this manner is useful for mass adjusting attributes for alternative scenario modeling. For example, you could use the stop calculator to adjust the headway of all currently selected stops to 20% less than each stop’s current headway setting.
- Set Socio-Economic Growth Rates and Base Fares.
- Under the Scenario menu, select the “Set Socio-Economic Growth” submenu, and finally “Enter Growth Rates”, to bring up the “Socio-Economic Data Growth Rates” dialog.
- Enter 2% in total population. By default, this rate will be used for the other factors as well.
- Click “Set Growth Rates” to apply the rates and close the dialog.
- To establish the base fares, open the System Fare Levels Dialog ($ Icon on the main TBEST toolbar, or select “System Level Fares” from the “Scenario” menu )
- Base fares are set according to the route type. All of HART routes are of one of three types: Circular, Radial, and Express.
- In the dialog enter $6 for the express routes and $4 for the circulator and radial routes.
- Click “Ok” to apply the fares and close the dialog.
- Running the Model.
- You are now ready to run the model. To do so, right-click the “2017 Base Conditions” scenario in the TBEST explorer window and select “Execute Model Run”.
- On the “Scenario Model Run” dialog, you will use the default settings and click “Run”.
- You will be asked to confirm the run and whether you want to save changes to the scenario. Click “Yes” to both.
- It will take about 20 minutes to run the model.
- Examining Model Results.
- On the “Scenario” menu, select “Model Reports” and then “Scenario Summary Tool”.
- Select the HART transit system and the “2017 Base Conditions” scenario.
- Leave the default “Summary Span and Time Period” settings as is, and click “Show Report”.
- Explore the results presented here.
- Examine the performance measures “Boardings Per Service Hour” and “Boardings Per Stop Visit”
- Which route has the highest “Boardings Per Service Hour”? (2 points)
- Generate a chart showing these 2 performance measures for the HART express routes and a handful of the non-express routes (Hint: You can use the TBEST search tool to identify express routes).
- Examine how the relationship between these 2 performance measures in general differs between express routes and other routes (e.g., “Boardings Per Service Hour” are high and “Boardings Per Stop Visit” are low).
- Grab a screenshot of the chart. Identify the routes which are express routes. Describe any difference in relationship you observe. How might you account for your observations? (3 points)
- Title VI Analysis
- To run a Title VI Analysis, you need to have all scenarios closed. You can close any open scenarios by clicking “Close Scenario” on the main TBEST toolbar.
- Right mouse click on Title VI Analysis in the TBEST explorer window and select “New Title VI Analysis”.
- Name the new analysis “Route 1 Title VI Analysis”.
- Select “HART” as the transit system.
- Select “2017 Base Conditions” as the scenario.
- Leave the buffer distance as 0.25 miles and click “Next”.
- Leave the service area setting as Hillsborough County and click “Next”.
- On the Poverty Levels screen, adjust the poverty incomes to reflect the 2017 values from the Department of Health and Human Services and, once done, click “Next”.
- On the “Route Selection” screen select Route 1 and click “Next”. (Note: we are running just 1 route for this exercise, so the analysis will complete faster.)
- Upload the transit system logo for HART and click “Next”.
- Click “Next” on the “Jurisdictional and Rex Route Input” screen.
- The Major Roads screen already has the correct shapefile selected. For states other than Florida, you would need to download the correct TIGER road data. Click “Next”.
- Click “Finish” on the “Title VI Setup Screen”.
- Click “Yes” on the confirmation screen.
- After a few minutes, the Title VI Analysis will finish, and the “Title VI Analysis Console” appears. On the left side of the console, there a variety of maps, and on the right side, there are a series of reports. Maps open in ArcMap.
- Spend a few minutes exploring the variety of output. Grab a screenshot of 1 map and 1 report you find interesting and briefly describe each. (5 points)