Section

Definition

A Section models the presence and approximate extent of a theme. Unlike a Unit, the boundary of a Section does not explicitly model a physical, vertical barrier or obstruction. The boundary of a theme may be a threshold or an indeterminate border.

When a Section is covered by the boundary of a Unit, Fixture or Kiosk, then and only then is the theme delimited by a physical, vertical barrier or physical asset.

Feature Structure

  • Section objects are Feature objects
  • Section objects MUST have an "id" member with a FEATURE-ID value
  • Section objects MUST have a "feature_type" member with the value "section"
  • Section objects MUST have a "geometry" member with a POLYGONAL value

Property Keys

Property Type Description
category SECTION-CATEGORY The category that best describes the function of the Section.
restriction null or RESTRICTION-CATEGORY The category that best describes a restriction that applies to the entire Section.
accessibility null or JSON array of ACCESSIBILITY-CATEGORY Indicates the type of accessibility provided by the Section to a pedestrian that experiences disabilities.
name null or LABELS The name of the Section as declared by the Venue Organization.
alt_name null or LABELS Alternative name for the Section that may be recognized by the Venue Organization.
display_point null or DISPLAY-POINT The curated location to use as the point-based representation of the Section.
level_id LEVEL-ID Unique identifier of the Level the Section possesses a spatial relationship with.
address_id null or ADDRESS-ID ID reference to Address record.
correlation_id null or UUID Correlation ID shared among similar Sections that occupy different floors of the physical Venue.
parents null or JSON array of SECTION-ID Unique identifier of the Section(s) that this Section possesses a child→parent relationship with.

Example

{
  "id": "11111111-1111-1111-1111-111111111111",
  "type": "Feature",
  "feature_type": "section",
  "geometry": {
    "type": "Polygon",
    "coordinates": [
      [
        [100.0, 0.0],
        [101.0, 0.0],
        [101.0, 1.0],
        [100.0, 1.0],
        [100.0, 0.0]
      ]
    ]
  },
  "properties": {
    "category": "parking",
    "restriction": "restricted",
    "accessibility": "wheelchair",
    "name": {
      "en": "Parking"
    },
    "alt_name": null,
    "display_point": {
      "type": "Point",
      "coordinates": [ 100.0, 1.0 ],
    },
    "level_id": "22222223-2222-2222-2222-222222222222",
    "address_id": null,
    "correlation_id": null,
    "parents": ["44444444-4444-4444-4444-444444444444"]
  }
}

Property Capturing Rules

CORRELATION_ID

  • MUST be present when the intent is to create an association between multiple Sections.

PARENTS

  • MAY reference a Section.
  • MUST NOT reference any other feature type.
  • MUST NOT contain duplicate entries.
  • MUST NOT be self-referential.
  • MUST NOT introduce circular dependencies between Sections.
  • MUST reference the id of a Section when the intent is to create a child→parent relationship.
  • MUST only reference a parent, NOT a child.

Geometry Capturing Rules

Section Extent

  • The Venue Organization SHOULD NOT, at first, be overly concerned with Units, Kiosks, and Fixtures that could or should be within a Section. The Venue Organization SHOULD first assess the physical environment and attempt to conceptualize a Section's extent as an operational and psychological theme:
    • Venue Infrastructure & Operations.
      • Physical infrastructure and facilities that exist in support of the operational theme. This includes the personnel and equipment that exist to support manned, semi-automated and automated operations within the physical environment that would not otherwise exist if the underlying business function(s) did not exist.
    • Business Services & Amenities.
      • Business services, amenities, facilities, and utilities that exist solely for use by a pedestrian as they pass through and/or when they temporarily remain within the conceptual extent of the operational theme.
    • Traversal Capabilities.
      • Equipment and physical structures that convey a pedestrian into and out of the physical environment that would not otherwise exist if the business function(s) did not exist.
    • Psychology. The Venue Organization MUST take into account:
      • The pedestrian's perception of reality and conceptualize a thematic extent that includes feature types that a pedestrian would "naturally" associate with the operational theme.
      • The pedestrian's conscious awareness and their belief about where they are physically located in a Venue and how tightly coupled that belief is to the proposed extent of an operational theme.
  • A Section SHOULD model a theme whose interpreted extent is entirely or only partially enclosed by physical, vertical barriers. (Illustration)
  • Depending upon the map context, "gaps" MAY exist among Sections to facilitate visibility of the underlying "walkway" Unit that is intended for pedestrian use. (Illustration)
  • An Opening SHOULD NOT be used to model an entrance to a Section.

    Occasionally, this is an illusion that is the consequence of a Unit legitimately requiring an Opening, and the Unit covers the boundary of a Section.