From BIM, CAD to GIS to Mobile Device: Converting SFO Interior Data to IMDF
Download as PPTX, PDF0 likes772 views
The document outlines the GIS data lifecycle for sub-surface utilities, detailing various data models including the exterior and interior data models and related schemas. It presents a comprehensive overview of the San Francisco International Airport's campus statistics, data source integration, and modeling processes for spaces, doors, and openings. The final output consolidates this information into an Indoor Mapping Data Format (IMDF) for improved mapping and navigational purposes within the airport.
From BIM, CAD to GIS to Mobile Device: Converting SFO Interior Data to IMDF
- 2. Sub-Surface Utilities Data Model - UDM Exterior Data Model - EDM Interior Data Model - IDM MUNSYS Schema FAA AGIS (18B) Schema Hybrid SFO Custom Schema SFO GIS
- 3. GIS Data Sources CAD GIS LiDAR Image Survey PDF BIM Tabular Hard Copy JSON XML DEM KML
- 6. Normalized in GIS GIS Exterior Data Model (Based on FAA 18B) Utilities Data Model (MUNSYS) Interior Data Model (Hybrid)
- 7. Campus Stats Campus Area 3.54 square miles Landside (2,246 acres) Buildings ≥ 1,000 sqft. (excluding MOC and USCG) 97 All Interior Area 16,431,155 sqft. (377 acres) Terminal Area 5,049,203 sqft. (115 acres) Terminal Public Area 2,358,000 (54 acres) Employees 43,000 Passengers ~58,000,000
- 9. SFO IDM COMPONENTS • Spaces • Floorplans • Doors • Levels • Building Footprints • Geofences
- 10. SpatialDataTabularData DOORS GIS BIM to GIS Feature Transfer
- 11. CAD to GIS • Door ID: D.2.301A • Space ID: D.2.301 • Tenant: Mosaic • Lease Type: Concession • Lease SubType: Retail • Space Usage: Retail Store • Level: L2 • Level Name: Departures • Building ID: 300D • Access: Public • Security: Post Security
- 12. CAD FLOORPLAN TO GIS PROD
- 13. FLOORPLAN & SPACE TOPOLOGY VALIDATOR
- 15. Output Destinations & Target Systems One Map for All GIS 3D Model CAD PMBSABM AVSEC S/A CAD 911 SFPD SFPD Wayfi nding Apple Maps Airline Maps Google Maps AVM Space Util. Meter Lock- Smith Terminal Systems FIDS ITT WiFi People Flow Lease Structure EMCS CMMS Gate Travel Times FLYSFO .com Internal Apps External Apps Custom Apps and Analysis
- 16. Indoor Mapping Data Format (IMDF)
- 18. IDM AGIMIMDF
- 21. FME Workspace
- 22. Database Model • ERD of IMDF database design featuring all feature types & related tables • Subset of Semantic Model developed with an Airports Council International (ACI) working group
- 23. ArcGIS API
- 24. HTTPCaller
- 26. Level Processor • Geometries reprojected into LL-WGS84 • Display Point extracted • Joined with Buildings to get building_uuid • level_uuid generated • Metadata altered, columns renamed
- 27. Units • IMDF defines Units as spaces with floor to ceiling barriers • Many of the spaces from the source data do not fit that criteria–will need to be dissolved together • Image to the left is color coded by two attribute values: – Blue represents PRIVATE (nonpublic) spaces – Other spaces color coded by manual DISSOLVE CODE – Purple spaces are PUBLIC and do not have a dissolve code
- 28. Unit Processor • Units are joined with corresponding level • Appropriate spaces are dissolved together • 4,569 PRIVATE spaces dissolved into 311 • 148 dissolve codes on 1,034 PUBLIC spaces
- 29. Before vs. After Transformation The simplified geometries reflects the level of granularity desired for a public-facing map
- 30. Openings • Any break in the floor to ceiling barrier • Doors • Service counters • Open entrances • Many were drawn manually (indicated by red lines) • Much of the source data represented doors by points (indicated in green), while IMDF requires Openings to be LINE- STRINGS
- 31. Idea from Dave Campanas (FME Product Expert): • Line-strings are clipped out of Unit boundaries by creating a buffer around the door point the size of the door width and using the Clipper to extract the Opening geometry • Door widths had to be measured manually Opening Processor
- 32. The created Openings are in red. This trick allowed us to leverage our existing data instead of having to recreate each door
- 33. Relationships
- 34. Relationship Spec • Was the most complicated feature type to model • Used to model correlations and directions between certain Openings and Units • We used it for Escalators, Stairs, Elevators, Moving Walkways, and Unidirectional Doors in our model
- 35. Data Model Relationship Data Model • Each relationship has a number of nodes • Origin (1), Intermediary (0+), Destination (1) • Each relationship has a category (Escalator, Elevator, etc.) • Each node has a type (Opening, Unit, Escalator, Elevator, etc.)
- 36. Group items together on common ID’s Merge nodes with generated relationship_uuid Relationship Processor
- 37. Relationships Visualized • Moving walkways in grey • Escalators and stairs scattered throughout • Elevators color coordinated by relationship • Directed Openings represented by circles: • Green for Origin • Red for Destination
- 38. Last Custom Transformer: Clean Geometries All geometries sent through Snapper; grouped by level_uuid
- 39. Final Step: Database to IMDF Normalized relational database consolidated into IMDF model
- 40. Output Model
- 41. IDM IMDF SFO
- 42. Thank you
Editor's Notes
- #6: Agie will mention data – tiers Tier 1: Exclusively maintained by SFO GIS Tier 2: Co-Maintained by SFO GIS and some other stakeholder Tier 3: Exclusively maintained by stakeholder and considered their data (mostly web apps and iPads) Tier 4: Deliverable that will not be modified of maintained and will remain in it’s original state
- #7: Agie will mention data – tiers Tier 1: Exclusively maintained by SFO GIS Tier 2: Co-Maintained by SFO GIS and some other stakeholder Tier 3: Exclusively maintained by stakeholder and considered their data (mostly web apps and iPads) Tier 4: Deliverable that will not be modified of maintained and will remain in it’s original state
- #8: 58 million PAX 43 thousand employees Family and friends Taxi + TNC
- #12: GEOFENCES NAVIGATION and WALKING PATHS