-
Notifications
You must be signed in to change notification settings - Fork 11
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
Scores for accessibility routing and other preferences #254
Scores for accessibility routing and other preferences #254
Conversation
Before removing OptimizationMethod
OptimisationMethod removed
<xs:enumeration value="environmentalFootprint"/> | ||
--> | ||
</xs:restriction> | ||
</xs:simpleType> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example` to illustrate a Score definition:
Refinement on Preferences
</xs:annotation> | ||
</xs:enumeration> | ||
<!-- The following seem less close to realisation: | ||
<xs:enumeration value="onlyExtraReliableConnections"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add onlyGuaranteedInterchanges, evaluation based on guaranteedConnection (TransferModesEnumeration)?
André: Waiting on some input from Malte before finalising. |
I dislike this change... we should discuss this. |
new version fro Köln |
Removed documentation label, documentation will be done for the follow-up PR. |
This is a proposal addressing #187 in a way that is compatible with the vision / roadmap discussed in #221,
Basic idea: Route plannig tries to optimize Scores which can be defined as a weighted sum over lower level Preferences.
I think to get a list of Trips the user is really happy with, two runs of a planning algorithm will typically be required (unless we had an algorithm optimising multiple Scores in parallel, perhaps as mentioned by Alexandre?):