This is Transitland v1. We're in the process of migrating content to Transitland v2.
Where half of the ground is heading northbound and the other is inching southward. (Remember from elementary school? That's what causes earthquakes.)
Also epically disjoint is our mass transit: over 30 public agencies, an ever-increasing number of private shuttles, not to mention jitneys and carpools welcoming those in the know.
Our goal at Transitland is to make sense of the jumble here in the SF Bay Area. We're mapping those buses, trains, streetcars, ferries, and even cable cars.
We're aggregating existing geographic and temporal data from authoritative sources; we're connecting the dots using common identifiers; and we're equipping ourselves, our collaborators, and perhaps also you to edit and improve this "community datastore" with knowledge from boots on the ground.
It's with these station locations, agency identifiers, and route schedules that we can join together the "tectonic plates" of mass transit. Transitland is for you to build your apps (the next big thing?), your sat. nav. gadgets, your flashy visualizations, and even your plans and analyses (that, with luck, Congress will fund some day).
The Bay Area was our initial laboratory. The world has become our goal. Seriously, transit-network data is useful in many places big, small, rich, poor. So, we've created a modular, open-source data service that works all over. Transitland now aggregates data from 50+ countries.
Search a list of the ~2,500 operators listed in the Transitland Feed Registry, which provides metadata for each operator.
Try the Mobility Explorer to browse an interactive map of stops, routes, and more transit features worldwide.
Read documentation on the Datastore API, which powers all of these clients. It can also power your app, analysis, or map!
Since Transitland's start in 2014, the platform has grown through participation from many organizations and individuals. We also welcome more users and contributors.