Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

YVR and the Indoor Mapping Experience


Published on

The world is going mobile, and with that, comes the need to deliver mapping data & info to the masses. As a leading world airport, YVR has developed a mobile app to assist customers, staff, and partners with their travel plans at our terminals. We'll discuss the trials & tribulations of getting our terminal maps from CAD to GIS (with FME), and delivering the data (via FME Server) to our YVR Digital Gateway and its API. It will also touch on things to be aware of when creating good indoor maps, not just for your organization but other mapping platforms (Google Maps, Apple Maps, OSM, etc)

Published in: Technology
  • Login to see the comments

  • Be the first to like this

YVR and the Indoor Mapping Experience

  1. 1. YVR & the Indoor Mapping Experience Carlos Silva GIS Specialist, Vancouver International Airport
  2. 2. CHALLENGING Mapping Vertical Space in 2D can be
  3. 3. YVR: 4 yrs ago (pre-GIS) Internal: Mostly CAD, Floor Layouts updated 3-6 mo post construction (as-builts) Rooms/BOMA shapes & Room #s key to Mapping All Things Public Terminal Maps: graphic design pamphlet (PDF) ers/navigate-yvr/terminal- maps
  4. 4. How the Mapping Process Works @YVR 1st Stage "Internal", FME: CAD BOMA polygons (10+ CAD files; 4200+ Rooms) & lease/operational database attributes collected (internal); QA/QC'd (ArcMap/SQL); weekly attribute updates 2nd Stage "Public", FME: Rooms merged/aggregated on specific attributes (pre/post security, back of house, passenger areas, based on Sector, Security, Room Description); further QA/QC (FME) & manual substitutions/edits (via ArcMap) 3rd Stage "Uploads" via FME: Nightly auto conversion to GeoJSON & uploaded to YVR Digital Gateway for YVR App Developers & YVR Website Developers with HTTP calls 4th Stage, "Apple AVF": further FME refinement of "Public Rooms" & process other internal datasets (doors, jurisdictional boundary, etc) to AVF spec; (manual upload to Map Connects)
  5. 5. STAGE 1: Make an Internal Floor Map(OMG, WTF Clean this up ASAP!!!) Imagery via,, from the TV Show “Scrubs”:
  6. 6. STANDARDS MATTER! (so does documentation & great schema)
  7. 7. Courtesy of XKCD: Creative Commons: Attribution-NonCommercial 2.5 Generic (CC BY-NC 2.5)
  8. 8. YVR Rooms = BOMA shapes/polygons DocOffice Buildings: Standard Methods of Measurement (ANSI/BOMA Z65.1- 2010),
  9. 9. FME: CAD BOMAS à GIS
  10. 10. STAGE 2: Floor Plans for a Public App Imagery via,, from the TV Show “The Muppet Show”:
  11. 11. FME: GIS BOMAS à GIS “Public Rooms”
  12. 12. YVR MAIN TERMINALS L3 “Public Room”
  13. 13. ArcMap: QA/QC Map Production; Data Verification & Edits; Map & Feature Services (Internal Only)
  14. 14. QA/QC LIKE CRAZY
  15. 15. Automate, Automate, Automate Avoid Spatial Substitutions As Much as Possible TAKE MY ADVICE:
  16. 16. STAGE 3: DATA DELIVERY Imagery via,,
  17. 17. YVR Digital Gateway
  18. 18. STAGE 4: APPLE VENUE FORMAT (AVF) • More conversions of the “public data” • Totally separate FME workbench • “GeoJSON files wrapped in a ZIP” • TIP: make your door entrances lines not points (for “Openings”) CONTACT APPLE FOR MORE INFO & DETAILS; SIGN UP @ Apple Maps Connect
  19. 19. Where is YVR now? 1) Public Terminal Maps (PDFs, Hard Copy Pamphlet, Website Maps (Leaflet with GeoJSON) 2) Internally: CAD 2 GIS via FME, accessible on an internal GIS application 3) YVR App & Website: Data Delivery via YVR Digital Gateway
  20. 20. Typical Issues/Solutions • Timeliness (room closures/areas open/notifications) • Spatial errors/topology • Additional data points (sources) changing & in-conflict • Schema Changes (YVR doors (points)/Apple AVF doors (lines)) • Data Holes: single wall lines vs plenty of CAD arch’l lines • software & DB updates (backend time away from QA/QC) • I.T. updates (eg. changes to servers; software) KEY: Automate the conversions, & non-spatial attribute sources KEY: use common data standards (GeoJSON 2.0!); data schemas pre-defined; DOCUMENTATION HELPS A LOT! KEY: API access (minimal manual uploads/downloads)
  21. 21. THANK YOU! E: Twitter: @arcvancouver