I caught wind of Transitmix while scrolling through my new reads on Pulse Reader. Jarrett Walker’s blog (Human Transit) has this to say about the tool, which was created by a group of Code for America developers:
Transitmix is simple way to think about transit in terms of bus requirements and real costs. Basically, the user draws a route on a map and plugs in span and frequency. The app then calculates a vehicle requirement and cost in both hours and dollars, factoring in an adjustable layover ratio, average speed and dollar cost per service hour.
Transitmix theoretically works for any city on the map, as any city-related data such as operating cost per service hour is inputted by the user. This tool could theoretically also be used to layout and plan rapid transit lines (including rail) with the insertion of the appropriate “average speed” and “operating cost” values, albeit with the present limitation that lines snap to roads and cannot use other rights of way.
It’s made by the same people who created Streetmix, an urban road visualization tool that I previously featured on this blog.
See also: StreetMix lets you create the perfect urban road
See also: Human Transit – Transitmix: a new tool for armchair transit planners (and pros too?)
I tried it out here in Vancouver to conceptualize one new transit route I had in mind, based on a City of Vancouver (and more recently, Mayors’ Council-approved) proposal to introduce a B-Line type service from Commercial-Broadway station down Victoria Ave. (Pictured above – separate article coming soon)
On the Transitmix Experience
One of the reasons Transitmix is currenty able to work with so many cities around the world without issue is because it currently relies solely on user-inputted data.
That means, making effective use of the tool means knowing the average cost of service in your area (operating cost per revenue service hour) because this is not provided for you by the tool. I tracked this down for Metro Vancouver by checking TransLink’s bus performance reviews and other documents.
Unfortunately, that single value for operating cost is valid for all routes on the map and cannot be changed per route – meaning it is currently not possible to accurately compare the costs of standard bus services vs. less-costly community shuttle bus services (or mixes of both). It is, however, possible to create a completely separate map with the appropriate value inputted for those routes.
TransitMix is also currently not able to tell which roads are arterial roads, freeways, or local neighbourhood streets. That means that any speed calculations – which have an effect on operating cost and service levels – will have to be done manually, outside of the tool. At present, they will also have to be converted to mph.
These are the only limitations I’ve found. Among the strengths, previously made maps can be easily shared or remixed – and kept for future re-access – via the numbered URL.
Transitmix will become an important tool to empower individuals who have an interest in transit. It takes out a lot of the effort in visualizing and presenting a proposal, and makes instant what would otherwise be a plethora of calculations.
The tool is available at www.transitmix.net.