It’s here: The MTA has officially launched its redesigned website, complete with a spiffy new look, access to multiple trip planners, and a convenient way to quickly check on the status of subway and bus lines.
While there’s much to say about the site’s new design, what excites us most is the developer center, which I think is the most important announcement of the day. Here’s a quick rundown of the news, starting with…
Before talking about the new stuff, it’s useful to think about just how far things have come in a relatively short amount of time. Just five months ago, developers were being threatened with legal action by the MTA, the only way to get any raw schedule data was to submit a formal FOIL request (and get a CD weeks later with data in an undocumented and cryptic format), and there was no good avenue for developers to positively engage with the agency.
Contrast that with the situation today: The MTA has released GTFS data for the entire subway system, NYCT buses, Metro-North Railroad, Long Island Rail Road, and Long Island Bus. This is a tremendous and welcome step forward. With the click of a button, developers now have access to the majority of the schedule data for NYC trains and buses, all in a standard format.
Also encouraging is that the MTA has expanded its Twitter (and Facebook) presence. Follow @MTAInsider for updates from inside MTA HQ. Here’s hoping the agency uses this as an opportunity to listen as well as talk to the transit riders.
…What needs to be improved
Personal information shouldn’t be required just to download the GTFS. I understand why the agency has an interest in collecting developers’ email addresses, but I think the download process should be as simple and straightforward as possible. Right now, the process is overly complicated, requiring everything from a street address to your phone number to the IP address range where your application will be used. This information should all be optional. You should only need to enter your address if you want to receive emails when new schedules are posted.
There is no MTA developer mailing list. Such a list would be a fantastic resource and would greatly improve communications between the MTA and the developer community. This could be easily implemented and hopefully will be soon. Other agencies, such as MassDOT, have seen great success using a public mailing list to engage with developers.
Another issue is that there’s still not a clear path for applications to freely and easily use the standard route markers to properly identify lines. A clear, click-through license that explicitly grants usage of these symbols for such purposes — for both commercial and non-commercial use — would be another important step forward. It would also further the social goal of trademarks: reducing consumer confusion in the marketplace, making it easier for riders to get information on their preferred bus and subway routes.
Missing from the data sets released today is schedule data for the MTA Bus Company, which operates a significant portion of the buses in New York City,
and the Staten Island Railway (Update: Looks like the NYCT Subway GTFS includes the SIR schedule!). However, my guess is that it is only a matter of time until this data is also released. Other datasets — from ridership numbers to greater facility information — would also be welcomed. Hopefully these and other datasets are on the way.
One such dataset that’s of particular interest to me is subway entrance and geometry data. The MTA has previously made the argument that releasing such data would pose a security threat, but this seems far fetched, particularly since all of this data has already been released, just in a manner that’s less useful for developers. The neighborhood subway maps, which are displayed prominently in subway stations throughout the city, show the station entrances and geometries, and the NYCityMap operated by NYC DoITT has a GIS layer with the location of every single subway entrance.
The final big omission is the lack of real-time data. Since such data doesn’t exist for most of the system, it’s unreasonable to expect it to be released today. However, there is some real-time transit data in New York — namely for the L train and the 34th st buses in Manhattan — and this information should be released for developers to build applications on top of.
One big unknown is how weekly service advisories will be handled. With so much weekend track work going on, everybody knows that subway service can change dramatically come Friday nights. Weekly service alerts and schedule changes, provided in a well structured and machine-readable format, would be immensely useful and help ensure that transit apps provide riders with the most accurate information possible. With the MTA now defaulting to Google’s trip planner on its homepage, the need to get updated GTFS data out on a regular basis is particularly acute.
The second big unknown is how responsive and open to developer feedback the agency will be. The announcement today suggest they are serious about leveraging the outside development community, and I have witnessed a palpable shift in the agency’s willingness to engage over the past several months. Here’s hoping that things will continue moving in the right direction.
These improvements did not come about easily. There were substantial logistical, legal, and political hurdles to overcome, and I know many people, both inside and outside the agency, worked hard to bring about these changes.
The NY Open Transit Data group has long been advocating for these changes and working to constructively engage with the MTA. I’m pleased to say that today’s announcements incorporate some of the core recommendations we’ve made to the agency on open data policy. Our group’s next meetup is Wednesday, January 20 at 6:30pm. Come join us to talk about what these developments mean, what’s next, and, most importantly, how we can use this newly opened data to improve transit in New York.
I’m proud that the city I call home has joined the ranks of those providing open transit data, and I can’t wait to see what comes next, both from the the MTA and the New York tech community. It’s going to be another great year for open data.
Update 1/15/2010: Two days after writing this post, the MTA has already addressed several of these issues!