OpenTripPlanner and the year-old dateline in its own history section
An open source multi-modal trip planner
At a glance
- What is it?
- A Java trip planner for scheduled transit, walking, cycling and ride hailing, built from GTFS and OpenStreetMap and exposed over GraphQL. Its README dates itself to September 2025, sends bug reports to an organization name it no longer uses, and explains three of its ten build modules.
- Who is it for?
- OpenTripPlanner fits a transit agency, a regional transport body or a researcher who has GTFS data and needs itineraries that account for real-time disruptions rather than a timetable on its own. It does not fit anyone hoping for a hosted planner or a tutorial.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- opentripplanner/OpenTripPlanner2,776 ★ · +28
| Repository | 2026-10-04 | 2026-11-15 |
|---|---|---|
| opentripplanner/OpenTripPlanner | 2.7k | 2.8k |
28 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
This branch is the only supported version, and it is called dev-2.x
The note under the overview is the first thing to read, because it decides what the rest of the file applies to. This branch contains OpenTripPlanner 2, the second major version, which has been under development since 2018 and is now described as the dominant one and the only one being supported. There is no version switch in the README and no second branch to try, so a deployment on the older line is on a version that receives nothing. The branch itself is named dev-2.x, and that string is not decoration: every documentation address in the file carries it, with the history page, the deployments page, the governance page and the developers guide all served under a dev-2.x path. The releases are versioned separately from that branch name, with v2.10.0 published on 2026-09-09, v2.9.0 on 2026-03-18 and v2.8.1 on 2025-09-22, which puts a minor release roughly every six months and the last one a fortnight before the last push to the branch.
The history section dates itself to September 2025
The development history paragraph says the project was launched by Portland, Oregon's transport agency TriMet in July 2009, and then adds, as of this writing in September 2025, that it has been in development for over 16 years. That sentence is a year behind the file it sits in. The newest release is v2.10.0, named for September 2026 and published on 2026-09-09, and the branch itself took a push on 2026-09-24, so a reader who takes the dateline at face value will underestimate the age of the current release by about a year and will read the development history as current when it is a snapshot. Nothing marks it as a snapshot. The same paragraph sends readers onward for a fuller history and for a list of the cities and regions running the software, so the two things a newcomer most wants, who uses it and how it got here, are both delegated to pages the README does not reproduce.
Bug reports are pointed at the organization the project left
The getting in touch section routes three different things to three different places, and one of the addresses is stale. The Gitter chat room is named as the fastest way to get help, with most of the core developers there, and the same sentence tells you not to use the mailing list or the issue tracker for support questions. The mailing list, a Google group, is for project announcements almost exclusively. Bug reports are filed on the GitHub issue tracker, and the address given there is the openplans organization rather than opentripplanner, while every other link in the file, including the contributor graph, the Docker Hub image and the chat bridges, uses the current one. That single mismatch is the kind of link that redirects rather than fails, so nothing looks broken and a newcomer never learns that the file mixes two organization names. With 153 open issues on the repository, the tracker is where the work is, which makes the address worth checking before filing.
The bundled client is for testing, and the jar is one file
The repository layout section explains three things and then stops. The Java server code is in application/src/main/. A Javascript client built on the MapLibre mapping library is in client/src/, and the sentence that matters is the one about it being used for testing, with most major deployments building custom clients from reusable components. So the interface in the tree is a reference, not the product, and the reusable pieces are the point. The third thing is the packaging: the Maven build produces a unified, shaded JAR at otp-shaded/target/otp-shaded-VERSION.jar containing all the code and dependencies needed to run the planner. One artifact, any JVM, since the overview says the server runs on any platform with a Java virtual machine, including Linux, Mac and Windows. What the README does not give is the command that produces it, which sits in the developers guide instead.
Ten modules in the tree, three of them explained
The top level of the repository holds application, astar, client, core, gtfs-realtime-protobuf, otp-shaded, raptor, street, test and transit as directories, and the layout section accounts for three of them: application for the server, client for the Javascript front end, and otp-shaded for the packaged jar. The other seven are named nowhere in the README, so a reader has to infer that they are Maven modules of the same build from the pom.xml at the root and from the shaded jar claim that all code and dependencies end up inside one file. Alongside them sit the files that shape the build and the project rather than the program: checkstyle.xml, codecov.yml, maven-settings.xml, openrewrite.yml, renovate.json5 for dependency updates, magidoc.mjs, publiccode.yml, mkdocs.yml and a .git-blame-ignore-revs file. And the prose side has ARCHITECTURE.md, DEVELOPMENT_DECISION_RECORDS.md, CLAUDE.md and doc/, none of which the README links.
Licensing rests on two files and no statement
There is no licence section in this README. The terms live in the tree instead: a LICENSE file at the root and, beside it, a file named lgpl-3.0.txt. No licence is recorded for the repository either, so the machine-readable answer is empty while the files answer for themselves, and a reader has to reconcile three sources where one would do, or read the two files and decide. That is worth doing before any of this reaches a deployment, because the whole of the rest of the project is infrastructure for other people's transit data, and the obligations that come with a copyleft text and with a permissive one are not the same. The repository is not archived and the branch was pushed to on 2026-09-24, so there is no dormancy argument for skipping the question.
Every merge is measured, on a dashboard outside the project
Performance is treated as part of the merge process rather than as an occasional report. A speed test included in the code is run for every pull request merged into the project, and its results are published on a dashboard at otp-performance.leonard.io, a personal domain rather than anything under the project name. The README then points at test/performance/README.md for how to set it up and run it, which is where the real instructions live. Coverage has its own badge and a codecov.yml at the root, and the badge row also carries the Gitter and Matrix rooms, a contributors graph, and a Docker Hub image for opentripplanner, which is the only mention of a published container anywhere in the file. What none of this covers is the cost of the data side: GTFS feeds, OpenStreetMap extracts and the real-time feed all have to be supplied before any of the measuring says anything about your network.
Editorial conclusion
OpenTripPlanner fits a transit agency, a regional transport body or a researcher who has GTFS data and needs itineraries that account for real-time disruptions rather than a timetable on its own. It does not fit anyone hoping for a hosted planner or a tutorial. Before committing, settle four things. The terms come from the files, not from anywhere else: the root carries a LICENSE and a file named lgpl-3.0.txt, the README has no licence section, and no licence is recorded for the repository. The bug report link in the README points at the openplans organization rather than opentripplanner, so check where an issue actually lands before filing one. The bundled Javascript client is described as being for testing, so plan on building your own interface from components if you deploy. And the history paragraph is written as of September 2025, a year behind the v2.10.0 release, so treat any age figure in the README as dated.
Frequently asked questions
how to use opentripplanner
The repository carries no tutorial of its own. It points to the documentation site for a quick introduction and for the developers guide, and it names the Gitter chat room as the fastest way to get help, with most core developers there. The issue tracker is for bug reports and the mailing list is for announcements, not support questions.
what is open trip planner
OpenTripPlanner is an open source multi-modal trip planner focused on travel by scheduled public transportation combined with bicycling, walking and mobility services such as bike share and ride hailing. Its server runs on any platform with a Java virtual machine, it exposes GraphQL APIs for clients, and it builds its network representation from open data, primarily GTFS and OpenStreetMap.
Which version of OpenTripPlanner is supported?
The branch this README sits on contains OpenTripPlanner 2, under development since 2018 and described as the dominant version and the only one supported. The default branch is named dev-2.x, and the newest release is v2.10.0, published 2026-09-09, after v2.9.0 in March 2026 and v2.8.1 in September 2025.
What does OpenTripPlanner build, and into what file?
The Maven build produces a unified shaded JAR at otp-shaded/target/otp-shaded-VERSION.jar containing all the code and dependencies needed to run it. The Java server code is in application/src/main/ and a Javascript client built on MapLibre is in client/src/, which the README says is now used for testing while most major deployments build custom clients from reusable components.
How does OpenTripPlanner measure its own performance?
A speed test included in the code is run for every pull request merged into the project, and the results are published on a dashboard at otp-performance.leonard.io. The instructions for setting it up live in test/performance/README.md, and the README itself carries no build or run command of its own.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/opentripplanner-opentripplanner)Star history chart for your README
[](https://hysenlabs.com/projects/opentripplanner-opentripplanner)Was this useful?