Difference between revisions of "OpenTripPlanner"

From TransitWiki
Jump to navigation Jump to search
Line 11: Line 11:
 
==Implementation Suggestions==
 
==Implementation Suggestions==
  
−
A regional-implementation approach for OpenTripPlanner seems to offer the greatest benefit for transit passengers and agencies in a region, as many agencies can pool resources to create a trip planning product that works across multiple connected systems.  To pursue a regional trip planner approach, transit agencies would need to identify and work with partner agencies.  An ideal lead agency should have information technology and/or GIS staff experts to manage the implementation process.
+
A regional implementation approach for OpenTripPlanner seems to offer the greatest benefit for transit passengers and agencies in a region, as many agencies can pool resources to create a trip planning product that works across multiple connected systems.  To pursue a regional trip planner approach, transit agencies would need to identify and work with partner agencies.  An ideal lead agency should have information technology and/or GIS staff experts to manage the implementation process.
 +
 
 +
This regional approach is especially valuable for areas served by demand-responsive transit service. Generally not available in other trip planners, these services can be integrated into OpenTripPlanner via [[GTFS-flex]], presenting passengers with a more complete picture of their mobility options.
  
 
The non-profit organization OpenPlans provides a free “OTP Deployer” service <ref>OpenPlans. "Introducing OTP Deployer." Accessed August 1, 2012 from http://opentripplanner.com/2012/06/introducing-otp-deployer/</ref> for agencies to preview OTP for their transit network.  It is necessary to have GTFS data to upload to use this service.  $5,000 is an estimated baseline cost for basic deployment and maintenance of OTP for one year. This estimate assumes 25 consulting developer hours at $100/hr, and a hosting cost of $2,500.
 
The non-profit organization OpenPlans provides a free “OTP Deployer” service <ref>OpenPlans. "Introducing OTP Deployer." Accessed August 1, 2012 from http://opentripplanner.com/2012/06/introducing-otp-deployer/</ref> for agencies to preview OTP for their transit network.  It is necessary to have GTFS data to upload to use this service.  $5,000 is an estimated baseline cost for basic deployment and maintenance of OTP for one year. This estimate assumes 25 consulting developer hours at $100/hr, and a hosting cost of $2,500.

Revision as of 17:27, 25 November 2019

Introduction

OpenTripPlanner (OTP) is an open-source multimodal trip planner developed over the last several years, with version 1.0 released in September 2016[1]. Currently used by a wide variety of transit agencies and standalone trip planners, it supports integrated trip planning including fixed-route transit, active mobility, and demand-responsive transit via GTFS-flex.

Features

OpenTripPlanner's multimodal functionality enables users to plan many types of trips, including transit-only (with walking), bike and transit, driving and transit (utilizing park and ride locations), bike-only, walking-only, or driving-only trips.

Screenshot of public preview of OpenTripPlanner showing transit and bike trip in Portland, Oregon (rtp.trimet.org)

This multimodal functionality is well-suited for areas with many bike-and-ride customers, or bicycle facilities. Some transit services offer park and ride services, for which OpenTripPlanner would also be useful. Other benefits of OpenTripPlanner include the opportunity to closely control trip planner results and the way in which information is presented to customers by customizing the open-source software.

Implementation Suggestions

A regional implementation approach for OpenTripPlanner seems to offer the greatest benefit for transit passengers and agencies in a region, as many agencies can pool resources to create a trip planning product that works across multiple connected systems. To pursue a regional trip planner approach, transit agencies would need to identify and work with partner agencies. An ideal lead agency should have information technology and/or GIS staff experts to manage the implementation process.

This regional approach is especially valuable for areas served by demand-responsive transit service. Generally not available in other trip planners, these services can be integrated into OpenTripPlanner via GTFS-flex, presenting passengers with a more complete picture of their mobility options.

The non-profit organization OpenPlans provides a free “OTP Deployer” service [2] for agencies to preview OTP for their transit network. It is necessary to have GTFS data to upload to use this service. $5,000 is an estimated baseline cost for basic deployment and maintenance of OTP for one year. This estimate assumes 25 consulting developer hours at $100/hr, and a hosting cost of $2,500.

Mobile client (Android)

The Center for Urban Transportation Research at the University of South Florida developed an open-source Android client application for querying OpenTripPlanner. It is designed to interface with any OpenTripPlanner server via the OTP RESTful API. More information is on the github project page (github.com/CUTR-at-USF/OpenTripPlanner-for-Android)

Known OpenTripPlanner-based Deployments

GTFS-flex Deployments

Standard Deployments

Known Unofficial OpenTripPlanner-based Deployments

References

  1. ↑ Open Trip Planner. "Open Trip Planner" accessed via Github November 25 2019. https://github.com/opentripplanner/OpenTripPlanner
  2. ↑ OpenPlans. "Introducing OTP Deployer." Accessed August 1, 2012 from http://opentripplanner.com/2012/06/introducing-otp-deployer/
Retrieved from "https://www.transitwiki.org/TransitWiki/index.php?title=OpenTripPlanner&oldid=5348"