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

Optimize SSP distances in update computed attributes #1000

Closed
doublestranded opened this issue Mar 1, 2017 · 1 comment
Closed

Optimize SSP distances in update computed attributes #1000

doublestranded opened this issue Mar 1, 2017 · 1 comment
Assignees
@irees @doublestranded
Labels
issues / quality checks performance improvement

Comments

@doublestranded
Copy link
Contributor

No description provided.

@doublestranded doublestranded self-assigned this Mar 1, 2017
@doublestranded doublestranded mentioned this issue Mar 1, 2017
Closed
@doublestranded
Copy link
Contributor Author

This does not take into account the possibility of stops (or even stop pairs) repeating themselves along the RSP. The only way this implementation can be accomplished would be if the ScheduleStopPairs themselves had sequence numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@irees irees

@doublestranded doublestranded

Labels
issues / quality checks performance improvement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Optimizing update computed attrs transitland/transitland-datastore
2 participants
@irees @doublestranded