Site Entrance qualifier
Aurige opened this issue · 9 comments
Shouldn't we have an qualifier on SiteEntrance to say that it is a main Entrance/Exit, secondary
Entrance/Exit, service Entrance/Exit or Emergency Entrance/Exit ?
Probably to be added to SiteEntranceGroup
I don't know how it is in France, but in The Netherlands I would consider even the back entrances of a stations to be 'very prominent'. Obviously there are less important entrances, but if you take a journey planner, wouldn't you want to enter the station were it is close by? Can you give a use case what this solves?
For journey planning, when you don't know yet from where you will arrive, it's often that the main entrance is used as destination for a site (unless the journey planner supports multiple destination points, of course). Also when drawing a map, you usually have a bigger pitcogram for the main entrance. But I agree with you the closest is always the best.
Also it is not only about "main" but to qualify the entrance, that could also be "emergencyEntrance", etc.
Relative importance /purpose of entrance could be added as a further EntrancePurpose enum . Note that various other classifications are already defined on SiteElementProperties, such as whether it is for public or private or staff use only
Proposed revision (This views showing all the inherited properties of a SITE ENTRANCE).
Ok with @nick-knowles proposal PR to be drafted
just remove Staf value
Through shop is secondary. Entrance has AvailabilityCondition. only enumeration. and attribute.
@trurlurl will do a first draft
@trurlurl is there anything in this issue that is not in the PR? If not, I suggest to close the issue (not the PR).
I see that we don't want to wait for the merge of the PR, so I close the issue.