Closed flaktack closed 3 years ago
I've manually tested, and it seems to work as expected. I've added a fix for another bug, wherein the leg.from
and leg.to
coordinates were not where the actual boarding / alighting were.
Does this address this issue? https://github.com/stadtnavi/digitransit-ui/issues/571
Or this one: https://github.com/mfdz/OpenTripPlanner/issues/92
It addresses the first one (https://github.com/stadtnavi/digitransit-ui/issues/571), #92 requires updating locations.json
with a name
property for each Feature
. If that is done, then the API will reflect that.
Clarification for @hbruch: this doesn't affect the routing but only it simply places the start/end location dot to where the passenger is actually picked up/dropped off.
When creating itineraries for flex trips:
This should fix the leg splitting mentioned in https://github.com/stadtnavi/digitransit-ui/issues/571