Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feature: stopSequence #3

Open
brechtvdv opened this issue Sep 10, 2015 · 0 comments
Open

Feature: stopSequence #3

brechtvdv opened this issue Sep 10, 2015 · 0 comments

Comments

@brechtvdv
Copy link
Contributor

Now we make use of stopSequence and maxStopSequence to know if the trip ends. (gtfs2arrdep)

What if stopSequence is not set? Can we still calculate arrivals and departures?

The consequence of not using above feature is that we'll be reading (and loading in memory) arrivals 'till end of stream, because of no match. This will definitely give memory issues.

A solution without the feature is to set a time-offset that arrivals are possible after a departure, e.g. 4 hours.
brechtvdv added a commit to brechtvdv/arrdep2connections that referenced this issue Sep 11, 2015
@brechtvdv
Fix linkedconnections#3. Arrivals possible between time offset.
120ad4e
@brechtvdv brechtvdv mentioned this issue Sep 11, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brechtvdv