Morgantown is a small city of 30,000 people in West Virginia, which grows by another 30,000 people when classes start each year at West Virginia University. The university has two campuses two miles apart and transported students and staff on free buses between them. The mountain and river geography causes all roads to lead through the city center, and the many buses along with other motor vehicles created gridlock. The university also has over 9,000 faculty and staff.
The current Mountain Line Transit Authority buses of Morgantown are part of the vast collection of transit schedules, maps, and associated APIs, that Transitland provides, but the city's unique Personal Rapid Transit system of small vehicles – they look like vans or miniature buses – driving autonomously on a track stands out.
Here's how Personal Rapid Transit at WVU works: A rider at one of the five stations approaches a turnstile, pays 50 cents for the ride, and selects a button that designates one of the four destinations. Pressing the button tells the computer controller to dispatch a vehicle to that station and programs it to stop at a specific position on the platform. After the rider boards, the vehicle is programmed to drive directly to that station without stopping. The vehicles can bypass three intermediate stations on extra "express" tracks.
In demand mode, the controller may wait until more people request the same destination, but sends the vehicle after five minutes anyway. During low-demand times, the system may be switched to circulate vehicles in a fixed route, and isn't responsive to rider requests.
The vehicles in Morgantown were designed by Boeing and seat eight people alongside space for 13 standees, so it's sometimes referred to as Automated Group Rapid Transit. It began transporting students in October 1975.
Back in the 1960s, when the United States Department of Housing and Urban Development housed the Urban Mass Transportation Administration, the department published a study on innovative public transit technologies. PRT was thought to be a cost effective way to move people, but it hadn't been built and tested anywhere. The UMTA set out to change that and solicited propoals from around the country.
A WVU engineering department head named Samy Elias gathered support from the mayor and West Virginia legislators to get a grant from the UMTA to study PRT in the late 1960s, which resulting in selecting one of the three manufacturers promising they could build a PRT. The federal Department of Transportation, due to pressure from a WV senator, decided to fund construction of the world's first PRT in Morgantown.
Alden staRRcar, the product selected after the study, however, was deemed unfit to construct it and the UMTA ordered the Jet Propulsion Laboratory – yes, the same federal research facility at Caltech that built sends probes to Mars – to manage the program.
At around the same time, the U.S. DOT was also funding experimental transit technologies that led to the construction of the People Movers in Detroit and Miami. In the 1970s, there was a proposal to extend the Seattle Center Monorail – built for the Seattle World's Fair called Century 21 Exposition – that would use funds from the UMTA.
If you're familiar with the General Transit Feed Spefication-based feeds that power countless apps and mapping websites that tell you how to get around a city via transit, you might question how an on-demand transit network like Morgantown's PRT fits into that scheme. The GTFS specification generally requires that a feed list fixed routes that have fixed schedules.
The PRT's feed, however, uses the optional
frequencies.txt file that defines frequencies (also called headways), which is the time between departures at the same bus stop or train station. When a feed provides that file, then fixed schedule stop patterns aren't necessary. The Morgantown PRT's feed lists five minute frequencies, but the system is technically capable of running vehicles 15 seconds apart.
Interact with the PRT's feed in the Transitland Feed Registry.
Transitland's Valhalla doesn't currently support routing queries for transit systems that use frequencies instead of fixed schedules, but it's something the Mapzen Mobility Team intends to include. Given that all of our work is done in the open, and open source, we welcome contributors.