-
Notifications
You must be signed in to change notification settings - Fork 3
Home
Note: this wiki is targeted primarily at the OTP development community. For general information about the project, please visit opentripplanner.com
OpenTripPlanner (OTP) is an open source multi-modal trip planner, which runs on Linux, Windows, or potentially any platform with a Java virtual machine. OTP is released under the LGPL. As of Spring 2013, the code is under active development, with a variety of working demos from around the world.
Latest Project Updates:
-
Portland's TriMet relaunched its official trip planner, now powered by OTP, on August 6, 2012, following a successful 10-month beta run. Read more about the project, and see also TriMet's 2009-2011 OTP Final Report.
-
BikePlanner.org and CiBi.me launch in Washington DC and New York City, respectively, showcasing OTP's support for real-time bike rental trip planning as well as a new mobile-friendly, Leaflet-based UI.
-
See schedule/notes for our Weekly Check-In Discussions, held Thursdays at 1:30pm EDT (13:30 GMT-4)
-
For information about the OTP Workshop held in Portland, OR on July 13-15, 2011, see 2011 OTP Workshop
OpenTripPlanner is presently at version 0.9. (see changelog)
The software currently:
- Plans multi-modal walking, wheelchair, biking and transit trips
- Takes travel time, road type/safety, and elevation data into account when planning bike trips, and provides an interface for customizing the weighting of these three factors
- Shows graphical elevation profiles for bike trips
- Imports data from GTFS, shapefiles, OpenStreetMap and the National Elevation Dataset
- Plans trips in about 100ms in a moderate sized city
- Exposes a RESTful API (XML and JSON), which other apps or front-ends can build on
- Supports GTFS-Realtime for service changes and alerts
- Supports Bike rental
- Has experimental support for Raptor
See the Milestones page for more information on what's next.
See for performance characteristics in a larger metropolitan area with extensive transit coverage.
At the core of OpenTripPlanner is a library of Java code that finds efficient paths through multi-modal transportation networks built from [OpenStreetMap] and [GTFS] data. Several different services are built upon this library:
The OTP routing API is a RESTful web service that responds to journey planning requests with initineraries in a JSON or XML representation. You can combine this API with OTP's standard Javascript front end to provide users with trip planning functionality in a familiar map interface, or write your own applications that talk directly to the API. This API is provided by a Java servlet which can be dropped into any servlet container. In simpler terms, the OTP REST API is provided by a plug-in for standards-compliant Java web servers.
"OTP Analyst" refers to modules and services within OTP that apply the routing engine to transportation network analysis rather than end-to-end trip planning. OTP Analyst can be further broken down into:
The OTP Analyst Web Services provide network analysis results such as travel time maps and isochrones as standard web Mercator tiles or GIS rasters via a WMS-derived API. These web services are conceptually separate from the routing API, but are provided by the same servlet: once you have a working OTP trip planner you can also use it to produce travel time maps and other visualizations of transit service. See this blog post for more information.
The OTP Analyst Batch Processor is a command-line tool that handles more complex one-off network analysis tasks. It uses the same routing core and data sources as the other OTP services, but allows for very open-ended configuration and the inclusion of population or opportunity data. While configuration and use are currently somewhat opaque for non-developers, the "Batch Analyst" is becoming a powerful tool for visualizing how transportation networks. See this article for an example case study on the effects of hurricane Sandy in New York.
Users and developers who want to try out OTP without manually building the project or installing a servlet container on their machine may use the following self-contained packages. These zip files combine a pre-built copy of OTP with a lightweight servlet container called Winstone.
- Bleeding edge build: http://maps5.trimet.org/otp-dev/otp.zip (90 megs)
- Release build:
Note: In a production trip planning system, OTP is typically deployed as a plugin ("servlet") in a full-featured server like Tomcat (see architecture notes). Developers and more advanced users may want to simply build OTP from source and deploy the resulting WAR files to such a server.
The following tutorials will guide you through some experiments with the above pre-built zip files:
To browse the source online visit https://github.com/openplans/OpenTripPlanner.
To create a local copy of the repository, use the following command:
$ git clone git://github.com/openplans/OpenTripPlanner.git
- Installation instructions (how to get a development environment set up)
- Developers Guide (code conventions, how to submit patches, etc)
- RESTful API Documentation
- Tutorials (complete list of development tutorials)
- FAQ
- Mailing lists:
- IRC channel:
-
#opentripplanner
on Freenode - You can connect using your favorite IRC client or chat through the web (just enter a username and click Connect)
- Check out and contribute to future ideas for the software
-
- RoutingBibliography articles that have informed development of the OTP routing engine.
- AnalyticsBibliography articles on non-passenger-facing applications of multi-modal routing engines (including OTP) in urban planning, public policy, and the social sciences.
- Discussion/details of other complex issues and proposals requiring more space than a single ticket.
Send questions and comments to the user mailing list.
Chat with us via IRC on Freenode channel #opentripplanner
or chat through the web
- OpenTripPlanner.com has information for agencies, live demos, and details on commercial support for OTP.
- OpenTripPlanner mailing list (for getting help with and discussing the software)
- Frequently asked questions (FAQ) (what is a trip planner? who's behind this?)
- Phase One project plan
- Kick-off workshop (notes from the workshop that launched this project)
The project began a collaborative effort among TriMet, OpenPlans, and the developers of FivePoints, OneBusAway and Graphserver, and has since grown to encompass a global community of users and developers. More information on OTP's origins is available at the Project History page.