All of this work should target the feature/trip-planner feature branch.
User story
as a transit rider going to a new place
I want to plan a trip
so I know how to get to my destination
Acceptance criteria
[x] If the OTP URL and the Geocoder API key in .env are set, show the trip planner tab in the search pane. if they are not set, don't show the tab.
[x] Add from and to text fields and a "Plan Trip" button, wire it up to the /api/otp/plan endpoint.
[x] add fromPlace and toPlace params to the new /api/otp/plan endpoint
[x] Geocode the fromPlace and toPlace on the backend
[x] perform some basic interperation of the results from the API and show them in the frontend (this can even be in the console). This could look like a search results pane that shows a list of itineraries, similar to searching for a route in the current search box.
aaronbrethorst
commented
2 days ago
Note
All of this work should target the
feature/trip-plannerfeature branch.User story
as a transit rider going to a new place I want to plan a trip so I know how to get to my destination
Acceptance criteria
/api/otp/planendpoint.fromPlaceandtoPlaceparams to the new /api/otp/plan endpointUI inspiration
https://www.soundtransit.org/tripplanner/to/location:3b65b1283888ac0c5603a4bf18c2b526/from/location:11db49ecc87c7fde0e95dbbf92c3d371/now/1730868300000/travel-by/bus,train/route-option/fastest%20trip/max-walk/1609
Sample cURL command
here's a cURL command to query the Puget Sound OTP server to request itineraries from my neighborhood to Microsoft: