Skip to content
novalis edited this page May 3, 2012 · 14 revisions

OTP supports dynamic bike rental/bike sharing systems like Bixi.

To use it, edit your application-context.xml thus: <property name="url"

value="http://data.keolis-rennes.com/xml/?version=2.0&amp;key=CFQKOUGDWGDO8NY&amp;cmd=getbikestations&amp;network=levelostar&amp;station=all" />

If you already have a periodic updater for GTFS-realtime, you can just add the bike rental updater to that.

We support two bike rental APIs at present: KeolisRennesBikeRentalDataSource, and BixiBikeRentalDataSource (used in DC, for instance). Just change the class and URL above.

If your city's bike rental API is anything like Bixi or Keolis, it's trivial to add support for it.

If your city's bike rental API is like Velib (with a separate query needed for availability data, for no good reason), I would recommend simply not providing any availability data and assuming that all stops are available for pickup/dropoff. We haven't implemented Velib as apparently the people who run it get cranky when people use their API.

Realtime availability is only used for trips planned for times near now anyway; for future trips, we assume that everything is available.

You can also enable static bike rental data from OSM at graph build time, if you prefer. Just set the staticBikeRental property on OpenStreetMapGraphBuilderImpl to true, and OTP will do the rest.

The documentation on this wiki is outdated and should not be used

unless you are intentionally working with legacy versions of OpenTripPlanner. Please consult the current documentation at readthedocs

Clone this wiki locally