Tricky Transit Data. Is Transiki the Answer? | It’s All About Data

I have always loved working with transit data. It is so similar to road data like TIGER or OSM that we work with so often, but at the same time it is so much different. While a road network stays the same throughout time, a transit network can change depending on the time of day, or day of the week. This makes working with transit data a much more difficult problem than working with street data, in fact transit networks generally include street networks within them!

Services on top of transit data are somewhat more rare than road network services. Google has had Google Transit for several years now and is slowly expanding to include more cities. Microsoft recently added transit data for a few cities to Bing Maps. These services are great, I honestly don’t think I would be capable of using transit anymore without Google Transit on my iPhone, but what about the data?

Google has opened the General Transit Feed Specification interchange format they use to load data from transit companies into their system, and there are some efforts to make public GTFS data easy to get, as well as a number of very powerful tools that can suck in a GTFS dataset along with an Open Street Map road network for analysis and routing (BTW, GTFS is just a standard schema represented in CSV files, so working with it in FME is very easy too – kudos to Michael Grant of BC Transit who had a great presentation on this topic last week).

Transiki is a new project from Steve Coast (yes, the same Steve Coast who started OpenStreetMap) to bring the OSM model to transit data. Steve says he had the idea when Google Transit failed him, leaving him on a platform waiting for a train that did not exist, except in Google’s datasets. With Transiki, Steve may still have been stranded, but at least he could update the dataset to prevent others from being in the same situation. A wiki-esque transit network could also bring the real-time transit data in The Bay Area or Portland to other cities through a Waze like application. The uses for a large, free transit data network are almost limitless.

Will Transiki prove to be the answer to all of our transit woes? The short answer is nobody knows for certain. As with all crowdsourcing initiatives, only time will tell if the support from the community remains and grows. Given the huge success of OpenStreetMap, I am excited and hopeful. To get involved with Transiki, come join me on the mailing list!


Related posts:

  1. Full Speed Ahead with OpenStreetMap
  2. Trends in Spatial and Temporal Data
  3. Open and Accessible Data
  4. GIS Folks, Ever Metadata You Didn’t Like?
  5. Choosing the Right Data Format

One thought on “Tricky Transit Data. Is Transiki the Answer? | It’s All About Data

  1. agdturner

    Transit/traffic data about the movement of people and vehicles is more dynamic than transport/traffic infrastructure data, but in my experience roads and especially junction organisation changes considerably over time. In the UK in particular road improvement often involves road straightening which can shift major roads considerable distances. In part these changes of traffic and infrastructure go together. Increasingly traffic management is dynamic, road speed limits variable, lane directions interchangeable and traffic signalling control flow on the infrastructure to try to cope better with the traffic. I think in the future, the infrastructure will know a lot more about the destination of vehicles apriori and this should enable faster safer travel. To make the dream of safe fast efficient transport a reality a lot of dynamic data about planned and actual movements needs integrating with dynamic data about infrastructure. Thanks for introducing Transiki, I’ll take a closer look.

Comments are closed.