-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE]: Allow Offset for Departures for local Zones, similar to Connections #58
Comments
The immediate consequence is that you may have no realtime data on this anylonger depending on the offset. |
Maybe i think too non-logical programming-wise, but have a look at the other referenced Feature Request. Maybe it can be solved not by setting the offset in the attribute for that stop, but by filtering the Departure Lines, before they get added to the "Array"? |
That is not what you asked for, you wanted to have a offset to incorporate possible time to get to the stop...the consequence is what I described above and it does not matter which approach: future departures have less chance in having a matching realtime component. |
I decided to scratch my head a bit, as i had the Feeling im am a bit more slow on the uptake today than usual 😝 And maybe there is a chance for a change regarding the Request with delayed Connections (which is way more important to me anyway) so... |
Too late...in 0.4.4.8 ...you can decide to not apply it of course |
Describe the solution you'd like
When setting up a connection between A and B, an Offset can be set (e.g. the Minimum Time needed to get to the Station).
This Feature Request is to be able to set such an Offset for Static local Stops (defined by Zones) as well.
Describe alternatives you've considered
Maybe a post processing in the displaying Cards like custom:flex-table-card could be set up as well, to filter out connections that are impossible to get
The text was updated successfully, but these errors were encountered: