This page discusses the Roadmap for the near- and mid-term development and support of OneBusAway by the OneBusAway community.
Note as of June 2013: this Roadmap is currently under active discussion on the onebusaway-developers list, and may change in the near to medium term future.
To understand where we're going, it's important to understand how we got to where we are today. Very briefly:
Given the rapid pace of change that the project has undergone recently, a Roadmap such as is described here is needed to ensure coordinated and effective evolution of the project.
To be very clear: this Roadmap represents a shared understanding amongst the OBA community and its stakeholders about where we all believe the project should go (from a software perspective). It does not imply any commitment whatsoever from any party as to where the resources to go in that direction will come from, nor the timeframe under which we expect to get there.
The objectives driving the Roadmap are to:
The Roadmap proposal is thus as follows:
In general: focus on open standards-based API's and highly intuitive, usable, and beautiful user experiences.
Some likely examples of the types of changes referred to in the final 2 above items are the following.
To include such features and meet the needs of a broad range of deployments likely requires making these new behaviors and others that currently exist (eg so-called "wrap-around" behavior) configurable/pluggable/etc.
One additional note: the UI's in the existing OneBusAway UI's, which are built using GWT, do not use the RESTful API. As such, the deprecation and migration described above can happen independently for the UI's and for the RESTful API's.
To be perfectly clear, the above applies only to data coming out of OneBusAway in the customer-facing UI's and API's. While there are some standards ways of feeding information into OneBusAway (e.g. from existing CAD/AVL systems) it is expected that any given implementation may have its own special requirements for integrating from existing real-time systems into OneBusAway.
In general: support the use of OneBusAway both with and without an existing CAD/AVL system.
One of the major additions of the onebusaway-nyc project is the so-called "Inference Engine" (aka "IE") -- a set of mathematical/probabilistic models and algorithms that transform fairly raw, noisy, incomplete, and often contradictory information directly from buses into a best guess as to what a given bus is actually doing. In the NYC case, this fulfills the role that a CAD/AVL system plays in the existing/traditional OneBusAway deployment use case.
Thus, the specific items would be:
As with any good open source project, as much good, clear, concise documentation as is possible and necessary for people to:
Last edited by Alan Borning,