Deployment Options

  • OpenPlans and other organizations can host an instance of OTP customized for your organization and seamlessly integrated with your web presence.
  • OTP can also be deployed on your own servers. As OTP is written largely in Java, it can run on your server platform of choice. Existing deployments package the OTP components in Tomcat but other .war files will work.
  • Map tiles, routes, schedules, and other data can be stored on your local system data or fetched from remote locations online.
  • Hardware requirements can be estimated as follows:
Server RAM and Processor Core Requirements for OTP
Your System Size Small City or County Mid-sized City or Metro (100s of square miles) Large City or Region (>1000 square miles)
<1,000,000 Daily Trips 2G RAM, 1 core 4G RAM, 1 core 16G RAM, 1 core
1,000,000+ Daily Trips 2G RAM, 2+ cores 4G RAM, 2+ cores 16G RAM, 4+ cores

Customization & Support

  • OTP can be customized to accommodate your agency’s brand and graphics, as well as local fare rules, geocoding, and the specifics of your system.
  • Enterprises that use OTP in key applications will also want a level of service agreement, on-call technical support, bug fixes, and updates.
  • Please contact a supporting organization for competitive rates for customization, integration, and support.

Modularity

  • OTP’s modular components integrate easily into existing systems.
  • The routing engine can be used without mapping front end modules.

Data Required

  • General Transit Feed Specification (GTFS) files for schedule, route, stop location, basic fare, and transfer information, including if available pathways.txt for entrance and accessibility information.
  • Base map information, such as OpenStreetMap data or ESRI Shapefiles, for your service area to provide contextual location information and background.

Optional Data Supported

  • Centerline files and shapefiles for your roads, pedestrian paths, and bike lanes if your area is served by a bike or trail network that you would like to integrate with.
  • National Elevation Dataset data for US locations for purposes of planning bike trips according to topography as well as some accessibility features.
  • Your agency’s graphic standards and iconography.

  • What your trip planner should be:

    • Multimodal:

      Your riders are walkers and bikers, too

    • Map-based:

      Riders want to see where they are going, not just follow the directions

    • Accessible:

      Making it easier for mobility-challenged riders to use your fixed route services - saving you money

    • Yours:

      Giving you total control over the schedules, branding, and messages your riders see

    • Open:

      Easy to update and support without vendor lock-in

    • Affordable:

      Cheap enough for you to adopt it right now, and keep it running for years without dedicated staff