You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually I would say, that the supportedTransitModes can be retrieved from the api (named travelOptions see e.g. https://api.stadtnavi.de/routing/v1/router/ and http://dev.opentripplanner.org/apidoc/1.0.0/json_TravelOption.html) so we do not need to have them in the configuration file at all. As removing them would be a breaking change, I would suggest to document the option anyway and mention that they can be retrieved from the api, so the option shouldn't be used, so that it can be removed in a new major release of this repo?
However I would appreciate some thoughts on that :)
I found that in
transport-apis/data/de/ulm-otp.json
Line 19 in 236d88d
transport-apis/data/de/stadtnavi-otp.json
Line 19 in 236d88d
So imho it would make sense to add it there and maybe link to the possible values (e.g. this https://docs.opentripplanner.org/en/dev-2.x/RoutingModes/ if I'm not mistaken).
If you agree I could make a little PR adding the documentation
The text was updated successfully, but these errors were encountered: