Add stopTimes field to MOTIS
#130
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch adds a new `stopTimes` field to the options for MOTIS apis. This field can specify a set of parameters to be set as part of the request when using the `stoptimes` api. Currently the option includes `radius=200` for Transitous and no values for RNV MOTIS. While the MOTIS web interface defaults to a radius of 200 meters, setting this for all MOTIS endpoints unconditionally causes wrong departures to be listed for deployments with well maintained parent stations, such as the RNV MOTIS. See derf/travelynx#341
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds a new
stopTimesfield to the options for MOTIS apis. This field can specify a set of parameters to be set as part of the request when using thestoptimesapi.Currently the option includes
radius=200for Transitous and no values for RNV MOTIS.While the MOTIS web interface defaults to a radius of 200 meters, setting this for all MOTIS endpoints unconditionally causes wrong departures to be listed for deployments with well maintained parent stations, such as the RNV MOTIS.
See derf/travelynx#341