From the coast to the mountains, from the river to the sea, from the plains to the train, Mapzen is opening transit routing to the world.
Over the past few months, public-transit agency staffers and freelance data enthusiasts have submitted hundreds of GTFS feeds to Transitland, our collaborative effort to aggregate and improve transit data. As an open data platform, Transitland is intended to power apps, visualizations, and analyses by anyone and everyone. As part of the Mapzen Mobility initiative, we’ve also been busy building open-source apps and services on top of Transitland ourselves.
Today we’re excited to share that Mapzen Turn-by-Turn can plan multimodal journeys in over 200 regions around the world, using Transitland data. This makes Mapzen Turn-by-Turn the first open-source routing engine that can plan multimodal journeys (almost) anywhere in the world—and using only open and freely available data.
Easy Options for Developers
With this international coverage, we hope to help even more developers focus on making their own apps and digital experiences—not collecting, licensing, munging, and wrestling data—and now they have useful options available to them for working with open transit data:
- Use the Transitland Datastore API to access information about a transit operator, a stop location, or schedules at a certain time of day.
- Use Mapzen Turn-by-Turn to plan journeys in the 200+ feeds on Transitland that are marked as “routable.”
Even Easier Demos for Everyone
Getting a JSON response from an API is a dependable way to power an app or a visualization, but yes, we know it isn’t that visceral of a way to experience, well, anything. Here’s an interactive drag-and-drop demo that shows off the dense transit coverage in San Francisco, Prague, New York City, Rome, Los Angeles and Vancouver. Try moving those Point A and Point B pins and see what routes, connections and schedules are possible, then advance through the slides to try another city.
Want to hack this demo for your own purposes? It’s only a two-step process:
- Open up your web browser’s developer tools so you can see the demo code making requests to the Mapzen Turn-by-Turn API.
- Sign up for a free Mapzen developer key so you can submit requests like that from your own website, mobile app, or visualization/analysis script.
Actually, there’s a third, optional step:
- If you look closely, you’ll see that demo also looks up Point A and Point B using Mapzen Search. It’s that reverse-geocoding process that allows us to display a street address and a city name, rather than raw latitude and longitude. Mapzen Turn-by-Turn plays nicely with Mapzen Search, or with other open-source and proprietary geocoding options.
If you don’t have the inclination to peer inside your web browser, here’s what the requests look like on ours:
Notice the speed. Mapzen Turn-by-Turn can plan journeys in hundreds of milliseconds. It’s that speed that enables Mapzen Turn-by-Turn to power responsive applications. For example, Remix uses Mapzen Turn-by-Turn to offer near-instant drag-and-drop functionality to the transit planners who use its software to design and improve the arrangement of bus routes.
The Mapzen Turn-by-Turn API offers many more options than we could squeeze into that nice drag-and-drop demo. Try modifying other parameters, like the departure date and time, using our test tool in these other cities:
The Landscape of Transit: Island, Continent, or Archipelago?
These demos may make you feel like a sea captain landing in uncharted territory. Whether it’s an island or the tip of a new continent is unclear. This sense of disorientation is, in fact, progress. Previously every transit-routing engine was an island: You or your technically sophisticated friend had to fetch individual GTFS feeds from transit-agency websites and manually merge and disambiguate stop locations included in multiple feeds. The extent of the territory was always known—and always small. Now, Transitland contributors stitch together coverage for new regions every day, and we’re starting to form an archipelago of interconnected transit islands:
Are you aware of an open transit data feed that’s not yet represented on that map? Contribute it to Transitland and it will appear in Mapzen Turn-by-Turn and on the transit connectivity map shortly.
Expanding the Landscape of Transit Together
That’s the premise of the Mapzen Mobility: that it’s possible to create a “virtuous cycle” with data consumers also contributing back to increase coverage and accuracy for themselves and others:
Toward that goal of sharing the cost and the promise of open transit data, we encourage you to browse the Feed Registry list of 200+ “routable” places, try planning multimodal journeys using Mapzen Turn-by-Turn, and contribute additional coverage.
Already see an operator listed as “routable” in the Feed Registry but having problems planning a trip in their coverage area? Let us know by e-mail, Twitter, or GitHub issue. To provide transit-routing around the world—with interconnected archipelagos of dependable, high-speed transit accessible to all—is a major undertaking. With Transitland, Mapzen Turn-by-Turn, and the other Mapzen Mobility services, we’re working toward that goal together with some motivated and talented partners and collaborators. Join us.