OpenTripPlanner

Notable Changes

• Make GTFS GraphQL API an official API #5339
• Make Transmodel GraphQl API an official API #5573, #5637
• Deprecate REST API #5580
• Transit group priority #4999, #5583, #5638
• Transmodel GraphQL API for pass-through searches #5320
• Migrate to Java 21 #5421
• New debug client #5334
• Update to latest GTFS Flex spec draft #5564, #5655
• Restructure walk/bicycle/car preferences in router-config.json #5582

The full changelog is available at https://docs.opentripplanner.org/en/v2.5.0/Changelog/

Notable Changes

• Improved support for Fares V2 #4917 #5227
• Improved error and timeout handling #5047 #5092 #5121 #5114 #5133 #5130 #5192
• Enable GTFS GraphQL API by default, remove the word "legacy" from its name and documentation #5202
• Access and egress penalty on time and cost #5180
• Improve support for GBFS geofencing zones #5201
• Reduce memory consumption by 5-8% #5223
• Stop count limit for access/egress routing and new accessEgress configuration object #5214

Notable Changes

• The performance for trip search of large networks (> 100k stops) is improved
• Run only a single heuristics request (instead of two) #4537
• Parse NeTEx fare zones from a FareFrame #4563
• Initial implementation of via search #4554
• Relaunched documentation theme #4575
• Add carpool and taxi modes #4641
• New filter API #4657
• Adaptive street graph island pruning #4688
• Experimental support for GBFS geofencing zones #4741
• Update GBFS support to v2.3 #4809
• Improve support for EPIP NeTex profile #4863
• Uber ride hailing #4979

Notable Changes

• The performance for trip search is improved by ~20-30%
• Support for GTFS-RT Vehicle Positions #3981
• Support for NeTex DatedServiceJourneys #3889
• Cost-based wheelchair-accessible routing #4045
• Improve stop linking by taking OSM platform polygons into account #4116
• Provide an OCI container image on DockerHub #4168
• Re-add block-based interlining #4264
• Add walk safety to street routing #4328
• Experimental support for GTFS Fares V2 #4338
• Document JVM configuration options #4492
• Support for HTTPS datasource during graph building #4482
• Metrics for realtime trip updaters #4471
• Configuration Documentation generated programmatically #4478

OpenTripPlanner 2.1

This is the biggest OTP release ever by many metrics: not just the amount of code or issues addressed, but also the number of active contributors. It is the first major update to the 2.0 release and represents over a year of continuous collaboration between international organizations.

Notable Changes

• GBFS 2.2 is supported including "form factors" (bike, scooter, car) and floating vehicles (with no fixed station)
• Constrained Transfers (Netex interchanges / GTFS transfers.txt)
• Transfers for bicycle and wheelchair users distinct from walking paths
• Support for GTFS-Flex v2
• Support for frequency-based trips (GTFS frequencies.txt, does not exist in Netex)
• Many 1.5 features not fully implemented in 2.0 have been reintroduced
• Improved result quality relative to both 1.5 and 2.0: filtering of itineraries and selection of transfer points between routes
• Car and bicycle parking has been combined into vehicle parking (enhanced with real-time details like remaining parking spaces)
• New system for paging of routing results via cursor token
• Response times should be roughly stable since 2.0. Performance much improved over OTP1 for long searches, may be somewhat slower for short searches. Extremely dependent on data set used, so test on your specific data.
• System integration tests for ongoing performance measurement

Version 1.5 of OpenTripPlanner was released just before version 2.0. It is intended to serve as a final release integrating any bugfixes backported from the 2.x development as the 1.x track moves into legacy/maintenance status. OpenTripPlanner 2 has changed significantly from OTP1 so there are reasons you may still want to work with this 1.x release or a fork of it. See http://docs.opentripplanner.org/en/latest/Version-Comparison/ for more information.

OpenTripPlanner 2.0 is the second major release of OTP, the result of several years of hard work and increasingly international coordination led by Entur in Norway. The transit routing engine of OTP2 has been completely rewritten, yielding major improvements in performance, scalability, and variety of itineraries over OTP1. It also has other important new features like the ability to read EU-standard NeTEx transit data and SIRI realtime.