Airport - Specific Map Production Rules

General Rules

  • Keywords "MUST", "MUST NOT", etc., communicate map data requirements. It is not mandatory for a Venue Organization to comply with the stated keyword unless the Venue Organization intends their delivery to be considered as a candidate for Apple Maps.
  • A Venue Organization that intends their delivery to be a candidate for Apple Maps MAY submit an optional property that is not required by Apple Maps. The property, however, may be systematically ignored.
  • A keyword in a Map Production Rule presumes the existence of the physical object.
    • When the physical object exists, then the keyword is applicable and the described modeling approach is expected.
  • Details MUST NOT be captured.
  • Specific Map Production Rules are an "extension" of IMDF that exist for each feature type. Unless otherwise specified, IMDF takes precedence.

Apple Maps Rules

  • The following property rules apply:
"feature-type" category Rule Property
"amenity" "arrivalgate" MUST possess name
"amenity" "boardinggate" MUST possess name
"fixture" "baggagecarousel" MUST possess display_point, name
"geofence" "concourse" MUST possess display_point, name
"geofence" "terminal" MUST possess display_point, name
"section" "baggageclaim" MUST possess display_point
"section" "checkin" MUST possess display_point
"section" "immigration" MUST possess display_point
"section" "security" MUST possess display_point
"unit" "parking" SHOULD possess display_point, name
"feature-type" category Rule Property
"amenity" "baggagecarousel" MUST possess name
  • The following feature-type/category values MUST be captured:
"feature-type" category Comment
"amenity" "animalreliefarea"
"amenity" "arrivalgate"
"amenity" "babychanging"
"amenity" "baggagecarousel" If preferred over Fixture display_point
"amenity" "baggagecarts"
"amenity" "boardinggate.aircraft"
"amenity" "checkin" If preferred over Fixture ("checkin.desk") display_point
"amenity" "checkin.desk.oversizebaggage"
"amenity" "checkin.selfservice"
"amenity" "defibrillator"
"amenity" "drinkingfountain"
"amenity" "elevator" If preferred over Unit display_point
"amenity" "escalator" If preferred over Unit display_point
"amenity" "firstaid"
"amenity" "immigration" If preferred over Section display_point
"amenity" "information"
"amenity" "lostandfound"
"amenity" "movingwalkway" If preferred over Unit display_point
"amenity" "mothersroom"
"amenity" "parking" If preferred over Unit display_point
"amenity" "peoplemover"
"amenity" "restroom" If preferred over Unit display_point
"amenity" "restroom.family" If preferred over Unit display_point
"amenity" "restroom.female" If preferred over Unit display_point
"amenity" "restroom.male" If preferred over Unit display_point
"amenity" "restroom.unisex" If preferred over Unit display_point
"amenity" "rideshare"
"amenity" "security.checkpoint"
"amenity" "security.inspection" If preferred over "security" Section display_point
"amenity" "smokingarea"
"amenity" "stairs" If preferred over Unit display_point
"amenity" "taxi"
"amenity" "vendingmachine.trainticket"
"amenity" "wheelchairassist"
"fixture" "baggagecarousel"
"fixture" "checkin.desk"
"fixture" "furniture"
"fixture" "immigration.desk"
"fixture" "inspection.desk"
"fixture" "kiosk"
"fixture" "obstruction"
"fixture" "wall"
"fixture" "water"
"fixture" "vegetation"
"geofence" "postsecurity"
"geofence" "presecurity"
"section" "baggageclaim"
"section" "checkin"
"section" "gatearea"
"section" "immigration"
"section" "security"
"unit" "elevator"
"unit" "escalator"
"unit" "movingwalkway"
"unit" "nonpublic"
"unit" "opentobelow"
"unit" "office"
"unit" "parking"
"unit" "platform"
"unit" "ramp"
"unit" "restroom"
"unit" "restroom.family"
"unit" "restroom.female"
"unit" "restroom.male"
"unit" "road"
"unit" "room"
"unit" "stairs"
"unit" "steps"
"unit" "unenclosedarea"
"unit" "walkway"
"unit" "walkway.island"
  • In limited circumstances, when the following categories are not derivable as Units from source data, then the following feature-type/category values MUST be captured::
"feature-type" category
"amenity" "elevator"
"amenity" "escalator"
"amenity" "movingwalkway"
"amenity" "stairs"
  • Either or both of the following category values MUST be captured:
"feature-type" category
"geofence" "concourse"
"geofence" "terminal"
  • The following feature-type/category values MUST NOT be captured:
"feature-type" Section category
"opening" "emergencyexit"
  • Each business entity that owns or leases space MUST be captured as an Occupant.
    • Each Occupant MUST reference an Anchor.
  • A jet bridge MUST NOT be captured.
  • A "restroom" (hierarchy) Unit that models a facility dedicated to wheelchair use MUST possess an Accessibility category of "wheelchair".