OpenTripPlanner

OpenTripPlanner
Name	OpenTripPlanner
Developer	OpenTripPlanner Community
Released	2012
Programming language	Java
Operating system	Cross-platform
License	BSD

OpenTripPlanner is an open-source multimodal journey planning system designed to compute routes across transit, walking, cycling, and driving networks. It integrates schedule-based transit data, street networks, and map geometries to provide itinerary planning for cities, regions, and metropolitan areas. Implementations have been used by transportation agencies, municipal governments, and technology vendors to power trip planning on web portals, mobile apps, and kiosks.

Overview

OpenTripPlanner is a route-finding engine that combines public transit schedules with street-based routing to produce multimodal itineraries linking points of interest such as Times Square, Union Station (Washington, D.C.), King's Cross station, Shinjuku Station, and Gare du Nord. The project ingests datasets including General Transit Feed Specification (GTFS) feeds from agencies like Metropolitan Transportation Authority (New York City), Transport for London, Société de transport de Montréal, Deutsche Bahn, and JR East, and map data from contributors to OpenStreetMap. Outputs can integrate with mapping platforms such as Leaflet (JavaScript library), Mapbox, Google Maps, Esri, and HERE Technologies to display results in user interfaces. Implementations often interact with standards and organizations like GTFS Realtime, General Transit Feed Specification (GTFS), Transitland, Open Data Institute, and regional agencies including Port Authority of New York and New Jersey and Transport for Greater Manchester.

History

The project originated in the early 2010s from collaborations among researchers and practitioners involved with institutions such as University of Minnesota, Massachusetts Institute of Technology, Harvard University, New York University, and technology firms that worked on transit modeling like Trapeze Group and Conveyal. Early demonstrations were presented at conferences including Transportation Research Board, Open Source Routing Machine (OSRM) Summit sessions, and workshops hosted by Smart Cities initiatives and European Commission programs. Major deployments and pilot programs occurred alongside events such as London 2012 Summer Olympics planning exercises, regional transit integration efforts like Transit Authority of River City pilots, and municipal modernization programs in cities such as Portland, Oregon, Seattle, Minneapolis–Saint Paul, Birmingham, and Auckland. Academic citations and case studies appeared in proceedings of ACM SIGSPATIAL, IEEE Intelligent Transportation Systems, and journals associated with Transportation Research Board.

Architecture and Components

OpenTripPlanner's architecture centers on a graph model that merges transit timetable graphs with street graphs derived from OpenStreetMap. Key components include a graph builder that imports GTFS feeds and OSM extracts, a routing engine implemented in Java (programming language) that performs multi-criteria searches, and a web API exposing results via RESTful API endpoints. Supporting modules integrate with databases and services like PostgreSQL, PostGIS, Redis, ElasticSearch, and cloud platforms such as Amazon Web Services, Google Cloud Platform, and Microsoft Azure. The system can be front-ended by client libraries in JavaScript, Kotlin, Swift (programming language), and Python (programming language), and often pairs with tile servers like Mapnik, TileMill, and MapServer for cartographic rendering. Monitoring and continuous integration have been implemented using tools like Jenkins (software), GitHub Actions, Travis CI, and CircleCI.

Features and Functionality

OpenTripPlanner supports schedule-aware transit routing with transfers, headway-based services, and frequency-based modeling used by agencies including SNCF, Amtrak, Metra (railroad), and VIA Rail. It provides pedestrian and bicycle routing influenced by datasets from Strava Metro and municipal bicycle networks, and can incorporate vehicle modes such as ride-hail services from companies like Uber Technologies and Lyft, Inc. through integration layers. Advanced features include isochrone generation for accessibility analysis, elevation-aware routing used in regions like San Francisco, real-time trip updates via GTFS Realtime, and support for accessibility attributes in stops and stations such as those in Amsterdams metro and Berlin U-Bahn. The engine supports itinerary filtering, fare computation compatible with systems like Oyster card and ORCA card, and multimodal planning that combines ferries, commuter rail, and microtransit services. Analytical workflows pair OpenTripPlanner outputs with tools like QGIS, R (programming language), ArcGIS, and Tableau for transport planning and equity studies.

Deployment and Use Cases

Deployments have ranged from municipal trip planners for City of Portland (Oregon), university campuses such as University of Minnesota, regional aggregators like Transitland, to transport authority integrations in Metropolitan Transportation Authority (New York City), Transport for London, and Regional Transportation Commission of Southern Nevada. Use cases include journey planning on public websites, integration into mobile apps for companies like Moovit, demand-responsive transit scheduling in pilot programs with vendors such as TransLoc, and mobility-as-a-service demonstrations in collaboration with entities like Siemens Mobility and Hitachi. Planners use OpenTripPlanner for scenario analysis in projects funded by bodies like Federal Transit Administration grants, Horizon 2020, and metropolitan planning organizations such as Metropolitan Council (Minnesota).

Development and Community

The project is maintained by a distributed community of contributors drawn from academic groups, transit agencies, consultancies like AECOM, Arup, SYSTRA, and tech companies. Development discussions and coordination occur on platforms such as GitHub, Apache Software Foundation-style issue trackers, and mailing lists used by communities including Urban Transport Group and Open Mobility Foundation. Documentation, tutorials, and case studies are shared at conferences such as State of the Map, Conveyal Conference, Transportation Research Board Annual Meeting, and meetups organized by local chapters like NYC Open Data and San Francisco Transit Riders.

Licensing and Governance

OpenTripPlanner is released under a permissive BSD-style license and governed through community norms and contribution guidelines. Governance involves steering by active maintainers, major stakeholders from transit agencies, and institutional contributors such as University of Minnesota and technology partners. The project interfaces with standards bodies and data stewards like the General Transit Feed Specification (GTFS) working groups, OpenStreetMap Foundation, and interoperability projects under the aegis of organizations like Open Data Institute and Open Mobility Foundation.

Category:Open-source software