camsys/otp-buddy

Provides Helper Tools for OpenTripPlanner

otp-buddy

Provides Helper Tools for OpenTripPlanner

Basic Setup Instructions Found Here

https://github.com/DerekEdwards/otp-buddy/wiki/Developers-Setup

otp-buddy's Issues

Replace Intersections Rake Task

Support Global Boundary Call

Refactor Feed ID Call

Right now we call OTP to get the feed ID every time a trip is planned.

Move this to a DB setting and only updated this when OTP is updated.

When Loading Stops, Mark Stations

If a stop is at a station, then set the types to be ['station']

Return All OTP Supported Mode Types

Create Config Page for Settings

Start with

1. open trip planner address (Done)
2. Location of Landmark File (Done)
3. Location of synonym file (Done)
4. Location of blacklist file (Done)
5. Gobal Boundary Text String (Done)

Add Back RealTime in Request.rb

Support Stops Query

Pull in the Emails

Write Instructions on Setup and Maintenance in the Wiki

Write basic developers setup on the wiki.

Support Map Printing

Put Login on Top of Settings Page

Settings should be Admins only. Set that up.

Copy and Update the API Doc

Probably a good idea to break it down by section and not just have a list of 25+ calls in random order.

A User Can Plan a Trip that Matches OTP-Trip-Manager's API Call

Will Supported WALK,TRANSIT only for now.

Merge Legs of the Same Block

If two consecutive legs are on the same block id, then return them as a merged leg.

Support CallNRide Call

Serve out Synonym File

Support Landmarks Query

Setup Emails

Once that is done, enable emailing in the landmarks and stops rake tasks.

Serve out Blacklisted GooglePlaces

Cut Round-Trip Time by 50%

The plan call for a transit trip. Specifically, the one below, takes 3.83 seconds on average. Cut that by 50%.

For reference the 'blacklist' call takes <100ms and the plan call to OTP also takes <100ms. What calculation is taking all this time?

{"source_tag":"internal","trip_purpose":"general_purpose","optimize":"TIME","itinerary_request":[{"segment_index":0,"start_location":{"formatted_address":"3401 E Colfax Ave, Denver, CO 80206, USA","geometry":{"location":{"lat":39.74032700000001,"lng":-104.94736699999999}}},"end_location":{"formatted_address":"1231 S Parker Rd, Denver, CO 80231, USA","geometry":{"location":{"lat":39.69393549999999,"lng":-104.89589339999998}}},"trip_time":"2016-10-18T21:03:00+00:00","departure_type":"depart"}],"modes":["mode_transit"],"max_walk_miles":0.5,"max_bicycle_miles":3,"min_transfer_time":5,"max_transfer_time":3600}

Handle OTP Error Messages

If the result from OTP has an "Error" Attribute, handle that.

Stops Should Match after 3 Characters

Write Stops Import Task

Save and Return All Google Place Details that are Passed

Setup on Heroku to Test Speed

Support Defaults Config

Write Landmarks Import Task

Clean Up API Calls

Create a V2 of the API that is a bit cleaner.

1. Only use Camel Case (in v1 there is a mix of camel case and underscores)
2. Don't refer to requested trip types as mode_trip_name etc.
3. Rename Itineraries Controller to Trips Controller
4. min_transfer_time & max_transfer_time should be min_transfer_seconds & max_transfer_seconds #
5. We only should support 1 way trips. Make that assumption in the controller. No more trip_part = trips_parts.first
6. json_legs should just be legs
7. All Times/Distances columns should be listed with unit e.g., walk_seconds walk_distnance_meters .etc
8. Move Global Boundary Call to settings_controller