search

ibi-group / otp-middleware

Proxies requests from OpenTripPlanner UI to API, enhancing OpenTripPlanner with user storage, real-time trip monitoring, and more!
MIT License
6 stars 2 forks source link

Itinerary check returns no monitorable days #172

Open binh-dam-ibigroup opened 2 years ago

binh-dam-ibigroup commented 2 years ago

Observed behavior

When saving one of the transit itineraries for monitoring, no monitorable days are returned.

https://atl-rides.ibi-transit.com/#/?fromPlace=%2833.784854448488915%2C-84.37362670898439%29%3A%3A33.784854448488915%2C-84.37362670898439&toPlace=217%20Thirkield%20Ave%20SW%2C%20Atlanta%2C%20GA%2030315-3500%2C%20United%20States%3A%3A33.714059324224124%2C-84.39285278320314&date=2022-07-15&time=16%3A41&arriveBy=false&mode=WALK%2CBUS%2CSUBWAY%2CTRAM%2CFLEX_EGRESS%2CFLEX_ACCESS%2CFLEX_DIRECT&showIntermediateStops=true&walkSpeed=1.34&ignoreRealtimeUpdates=true&wheelchair=true&numItineraries=3&otherThanPreferredRoutesPenalty=900

Expected behavior

There should be monitorable days returned by the checkitinerary endpoint.

Steps to reproduce the problem

While signed in, perform the check above and attempt to save one of the transit trips for monitoring. Observe that all days are crossed out, indicating no day can be monitored.

Any special notes on configuration used

NA

Version of otp-middleware and/or OpenTripPlanner if applicable (exact commit hash or branch name)

Current dev version of otp-middleware.

JymDyerIBI commented 1 month ago

At this writing, this problem has been fixed by changes on otp-middleware's dev branch when queries come from otp-react-redux's middleware-graphql branch.

The fromPlace is happier as: "Lake Clara Meer, Midtown, Atlanta" and the toPlace is "217 Thirkield Ave SW, Atlanta, South Atlanta, Georgia" with multiple weekdays in September 2024.