[Task] Pedestrian Access

[apds-change-control]

There seems to be a disconnect between the current model's capabilities of describing Pedestrian Access and its representation in the API.

Tasks:

• identify discrepancies and adjust the API accordingly
• compare the current model (in this regard) with NeTEx and DATEX II to assess its completeness compared to the two related standard specifications

[plexxdigital]

I have now assigned this item to me as I have been involved in the conversations with the NeTEx and DATEX II folks.
One question will obviously be what level of detail we're aiming for. Comments on this appreciated.

[plexxdigital]

pedestrian access

intro

A further analysis showed that the APDS specification documents actually do contain a Pedestrian Access package. This means that there are two resulting tasks:

• check if the current classes in the package cover everything we think we need
• expose them in the API (which is currently not the case)

spec check

The Pedestrian Access package comprises

• one class PedestrianAccess as a specilisation of an IdentifiedArea and
• one enumeration PedestrianAccessType
  • cargoShippingDoor
  • door
  • doorWithAccessCredential
  • doorWithSecurityReview
  • emergencyExitDoor

NeTEx

The NeTEx standard foresees details such as e.g.

• whether the entrance is external from the actual parking site,
• if it is entry only / exit only / entry and exit,
• height and width dimensions,
• whether the neares crossing to this entry has a dropped kerb
• whether there is a drop-off point close to this entry
    

questions:

1. the HierarchyElementGeneral class allows to specify type of a hierarchy element
   for this purpose, it offers HierarchyElementTypeEnum to specify one of campus, identifiedArea, place, space, subplaceElement
   what is the correct way to indicate the specilisation (PedestrianAccess) of the IdentifiedArea?
   (or is this done implicitly by using the properties of the specialisation?)

2. do we want to cover all NeTEx properties, too?

API enhancement

The API enhancement will be specified once we have clarified the open questions (see spec check)