SEPTA has adopted a newer version of the GTFS spec for their feed which has caused our version of OTP (1.4) to break. Support for the new format was added in OTP 2, but version 2 is a complete rewrite that isn't backwards compatible and doesn't include all the features that version 1 did. We should evaluate whether it is feasible for us to switch to OTP 2. We should investigate the ways that we use OTP 1.4 and ensure that OTP 2 has viable replacements. Off the top of my head, we should look into the following features:

• Elevation-based routing for cyclists
• Safe ride / fast ride routing for cyclists
• Bikeshare integration
• Travelshed generation
• How routing is handled in the Android app (I think we just delegate to the mobile site, but we should confirm that).

But there may be others that I'm forgetting, so we should look at all the ways OTP is used.

We should generate:

1. A go/no-go decision on whether it is feasible to migrate to OTP 2
2. Assuming that migrating is feasible then we should also generate a task list and effort estimates.