OpenTripPlanner alternatives and similar software solutions
Based on the "MapBBCodeShare" category.
Alternatively, view OpenTripPlanner alternatives based on common mentions on social networks and blogs.
Open Source Routing Machine (OSRM)Open Source Routing Machine - C++ backend
Nominatim7.3 9.7 OpenTripPlanner VS NominatimOpen Source search based on OpenStreetMap data
TileServer GL6.9 2.8 OpenTripPlanner VS TileServer GLVector and raster maps with GL styles. Server side rendering by MapLibre GL Native. Map tile server for MapLibre GL JS, Android, iOS, Leaflet, OpenLayers, GIS via WMTS, etc.
TileServer PHPMBTiles and MapTiler folder hosting with TileJSON, OGC WMTS, UTFGrid interaction and web interface. QGIS & ESRI ArcGIS compatible. Runs on any Apache+PHP webhosting. MapBox Studio Vector Tiles hosting.
μlogger4.3 1.6 OpenTripPlanner VS μloggerμlogger • web viewer for tracks uploaded with μlogger mobile client
Access the most powerful time series database as a service
Do you think we are missing an alternative of OpenTripPlanner or a related project?
Note that this branch contains OpenTripPlanner 2, the second major version of OTP, which has been under development since Q2 2018. The latest version of OTP is v2.1.0, released in March 2022.
If you do not want to test or explore this version, please switch to the final 1.x release
v1.5.0 or the
dev-1.x branch for any patches and bugfixes applied to the v1.5.0 release.
📊 Speed Benchmark We run the SpeedTest (included in the code) to measure the performance for every PR merged into OTP. The test uses a fixed Norwegian Netex data set and Grafana is used to display the results. Each run is listed under the GitHub Actions . If you need to run the test locally you can download the NeTex file from the Continuous Integration Pipeline. There is a [text file](test/ci-performance-test/travelSearch-expected-results.csv) with the expected results which might need to be updated when OTP is changed and the test fails. The OSM data used is the norway-210101.osm.pbf file from Geofabrik OSM extract from January 1st 2021.
The main Java server code is in
Leaflet mapping library in
src/client/. This client is now primarily used for testing, with most
major deployments building custom clients from reusable components. The Maven build produces a
unified ("shaded") JAR file at
target/otp-VERSION.jar containing all necessary code and
dependencies to run OpenTripPlanner.
Additional information and instructions are available in the main documentation, including a quick introduction.
OpenTripPlanner is a collaborative project incorporating code, translation, and documentation from contributors around the world. We welcome new contributions. Further development guidelines can be found in the documentation.
The OpenTripPlanner project was launched by Portland, Oregon's transport agency TriMet (http://trimet.org/) in July of 2009. As of this writing in Q3 2020, it has been in development for over ten years. See the main documentation for an overview of OTP history and a list of cities and regions using OTP around the world.
The main forums through which the OpenTripPlanner community organizes development and provides mutual assistance are our two Google discussion groups. Changes and extensions to OTP are debated on the opentripplanner-dev developers' list. More general questions and announcements of interest to non-developer OTP users should be directed to the opentripplanner-users list. Other details of project governance can be found in the main documentation.
- awesome-transit Community list of transit APIs, apps, datasets, research, and software.