-
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
Add AccessibilityFeatures to PathLinkStructure, additional AccessFeatures, rename lift to elevator #237
Conversation
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.
I think the typo (AccousticAnnouncements) has to be corrected and the more easily understandable enumerations should be used.
André will update PR with the additional input. |
All enums, as discussed in the meeting.
Comments
…nd-new-Accessibility-Features-attribute-(replaces-#236)
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.
PR #239 should remain intact when doing the merge.
Additional AccessFeatureTypes and new AccessibilityFeatures attribute.
In the context of PR#234 and #235, I thought it would be good to add accessibility-related data like the following:
PathLink.AccessibilityFeatures: visualSigns, elevatorAccousticAnnouncements, elevatorTactileButtons, etc. This allows for returning accessiblity information attached to PathLinks.
I made AccessFeatureTypes more consistent and complete regarding the possible access equipments by adding singleStep, travelator, etc.
I also changed lift to elevator, to be consistent with NeTEx.