A Kiosk models the presence and physical extent of furniture that facilitates the distribution of products and/or services.

  • A manned kiosk
    • Including but not limited to the distribution of consumables such as newspapers, magazines, cigarettes, confections, health & beauty products, electronics, food & beverage
  • Vending kiosk
    • Including but not limited to the vending of electronics, cosmetics, food and beverage
  • A manned or automated information kiosk

A Kiosk models the extent of the physical object, only. It is not used to describe the business or service that is operating out of the Kiosk. An Occupant (via Anchor) or Amenity would model the operation.

Feature Structure

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

Property Keys

Property Type Description
name null or LABELS The name of the Kiosk as declared by the Venue Organization
alt_name null or LABELS Alternative name for the Kiosk that may be recognized by the Venue Organization
anchor_id null or ANCHOR-ID ID reference to Anchor record
level_id LEVEL-ID Unique identifier of the Level feature the Kiosk possesses a spatial relationship with
display_point null or DISPLAY-POINT The curated location to use as the point-based representation of the Kiosk


  "id": "11111111-1111-1111-1111-111111111111",
  "type": "Feature",
  "feature_type": "kiosk",
  "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": {
    "name": null,
    "alt_name": null,
    "anchor_id": null,
    "display_point": null,
    "level_id": "2222222-2222-2222-2222-222222222222"

Geometry Capturing Rules

  • The Venue Organization is responsible for establishing the scope and purpose of a Kiosk. They are NOT defined by IMDF. When deciding the scope of the map data requirements, a Venue Organization SHOULD consider:
    • Venue Organizational (internal) needs
    • General map purpose
    • The use case model "driving" the map application
    • The value that is derived through augmentation of the map with Kiosks
    • Map data context, map scale and the relevance of a Kiosk at each of the viewable map-scales
    • The expected level of interaction between a pedestrian and the Kiosk, and the degree to which the map application can enrich that "experience" through presentation of a Kiosk
    • Map aesthetic quality considerations
  • A Kiosk that is, in reality, comprised of more than one physical component, MAY be captured as a multi-part feature
  • An Occupant MUST be positioned (via Anchor) within a Kiosk that models a space that is leased to a business entity


Physical objects that would be candidates for capture as a Kiosk. In this scenario, an Occupant would be positioned (via Anchor) within a Kiosk.

Several Kiosks within a "walkway" Unit.

  • An Amenity MAY be positioned within a Kiosk
  • A Kiosk SHOULD possess an area measurement that exceeds 0.5 square meters (exceeds 5.3 square feet)
  • Horizontal positional accuracy MUST be within tolerance