In this presentation, we will explore a phenomenon that FME use with many organizations has evolved from basic format conversion, data extraction and transformation tasks to systems integrations and even creating/generating complete, ready to use solutions which include data, analytics, and web applications. Alternative title for this presentation could be "FME Technology and Disruptive Innovation." We will show examples of building web viewers with raster and vector tiles, automating the generation of floor plans from BIM for TRIRIGA Space Management system, documentation and metadata with restructured text and Sphinx, and use of Box/Google Drive as image management system for 360 photos.

1. FME Technology – “Batteries Included”
University of Massachusetts, Amherst
Alexander Stepanov, GIS Architect, A&F Systems
Mark Anderson, Senior BIM/CAD Designer, DCM
Niels la Cour, Senior Facilities Planner, Campus Planning

2. Introduction

3. FLIGHT PLAN
● Evolution of FME applications in an
organization
● BIM and TRIRIGA CAD translation
● Hybrid approach to build Campus
Utilities Basemaps fast
● FME Integration of 360 Photos/Smart
Phone Photos with GIS and BOX

4. FME Technology – “Batteries included” I
1
new

5. FME Technology – “Batteries included” II
2

6. I. Bringing BIM to TRIRIGA CAD

7. I. BIM to TRIRIGA CAD conversion
● New Physical Science Building
● Restoration of historical West
Experiment Station
● BIM/Revit model of the building
complex
● Business need:
○ Generate TRIRIGA CAD floor plans
(supported by CAD Integrator)
○ Pre-defined layer structure, including
Space layer
○ BIM (3D) to 2Dhttps://www.umass.edu/dcm/psb

8. I. BIM to TRIRIGA CAD conversion
● Source:
○ BIM Model includes two buildings
(potentially modelled separately
○ BIM Model is 3D
○ The model includes multiple
structures and systems
● Destination:
○ 2D CAD
○ ~25 “predefined” layers ( naming
conventions, content/type, colors)
○ CAD drawing should be compatible
with TRIRIGA CAD Integrator

9. I. BIM to CAD Workflow
70+ layers
gaps in walls
21 layers
No Space Layer
Space LayerStoring as SQLite

10. 1. FME Workflow: BIM CAD to TRI CAD remapping

11. 1. FME Workflow: BIM CAD to TRI CAD remapping

12. 1. FME Workflow: BIM CAD to TRI CAD remapping
21 layers
To import to TRIRIGA
~70 unique layers
CAD export from Revit/BIM
FME

13. 2. FME Workflow: 3D cutting planes to get Spaces

14. 2. FME Workflow: 3D cutting planes to get Spaces
3D Cutting Planes
For each Floor
3D SPACE
Objects
3D Space Cross-section
Before flattening to 2D

15. 3. FME Workflow: Aggregating ‘virtual’ Spaces

16. 3. FME Workflow: Aggregating ‘virtual’ Spaces

17. 3. FME Workflow: Space and Door Frames Adjustment

18. 3. FME Workflow: Space and Door Frames Adjustment

19. 1
READ DATA USING
GENERAL SCHEMA
FANOUT DATA WHEN
WRITING
Bulk Processing
I. SUMMARY & TIPS
FME SUPPORTS 3D
OPERATIONS
SWITCH FROM 2D to 3D
AND BACK
Be Fluent & Efficient
UTILIZE REMAPPING
TRANSFORMERS
IMPORT RULES FROM
DATA
SOURCES/DATABASES
Minimize manual work
and configuration
settings
2 3 4
AN OPPORTUNITY FOR FME
TRANSFORMER BIMtoCAD
For TRIRIGA, ARCHIBUS,
CENTERSTONE
Multipel HigherED/FM
FME customers would
benefit from such
solution

20. II. Hybrid approach to Utilities Basemaps

21. II. CAMPUS UTILITY BASEMAP
Overview/value/external and internal drivers

22. II. CAMPUS UTILITY BASEMAP
Overview/value/external and internal drivers
Challenges:
 File based
 Rate of changes on Campus
 Attributes as text or color
 Backlog/existing surveying data
 Efficient access for multiple users
 Search/Navigation
 Inherited different editing standards

23. II. CAMPUS UTILITY BASEMAP
Overview of existing process to maintain Utility Basemap
Challenges:
 File based
 Rate of changes on Campus
 Attributes as text or color
 Backlog/existing surveying data
 Efficient access for multiple users
 Search/Navigation
 Inherited different editing standards

24. II. CAMPUS UTILITY BASEMAP
Overview of suggested process/approach to maintain Utility Basemap
Challenges:
 Rate of changes on Campus
 Attributes as text or color
 Backlog/existing surveying data
 Requires HUMAN interpretation
Advantages:
 All CAD features + Search
 Efficient access for multiple users
 Search/Navigation
 Overlays with Aerial HD Imagery
 Documentation
 Communication/Collaboration
 WebTiling/Indexing – AUTOMATION

25. Hybrid
Utilities
Basemaps
ADVANTAGES:
 All CAD features + Search
 Efficient access for users
 Search/Navigation
 Overlays with Aerial High
Definition Orthophotos
 It can be used with multiple
Web mapping JS/WebGL APIs
UMASS DEMO
VIDEO IS HERE
NO COPYRIGHT LIMITATIONS HERE

26. II. CAMPUS UTILITY BASEMAP
OVERVIEW OF WEB TILING PROCESS / AUTOMATION
Advantages:
 All CAD features + Search
 Efficient access for multiple users
 Search/Navigation
 Overlays with Aerial HD Imagery

27. II. CAMPUS UTILITY BASEMAP
OVERVIEW OF WEB TILING PROCESS / AUTOMATION
Automate, Automate & Automate

28. II. CAMPUS UTILITY BASEMAP
OVERVIEW OF WEB TILING PROCESS / AUTOMATION
MapnikRasterizer to generate Low Def, Med-Def and High-Definition Tiles
MAPNIK rulues are simple – as we use COLOR/THICKNESS/FONT info from CAD

29. II. CAMPUS UTILITY BASEMAP
OVERVIEW OF WEB TILING PROCESS / AUTOMATION
MapnikRasterizer to generate Low Def, Med-Def and High-Definition Tiles
MAPNIK rulues are simple – as we use COLOR/THICKNESS/FONT info from CAD

30. II. CAMPUS UTILITY BASEMAP
OVERVIEW OF WEB TILING PROCESS / AUTOMATION
HARVESTING TEXT LABELS & NOTES TO ENABLE SEARCH IN GIS APPLICATIONS

31. Hybrid
Utilities
Basemaps
ADVANTAGES:
 All CAD features + Search
 Efficient access for users
 Search/Navigation
 Overlays with Aerial High
Definition Orthophotos
 It can be used with multiple
Web mapping JS/WebGL APIs
UMASS DEMO 2
VIDEO IS HERE
NO COPYRIGHT LIMITATIONS HERE

32. 1
MOVE FROM VECTOR
TO RASTER AS NEEDED
Be data centric &
format agnostic
II. SUMMARY & TIPS
HARVEST LABELS,
ANNOTATION AND
TEXT TO BUILD
SEARCH/GEOLOCATOR
Search is one of the
most requested
features in GIS apps
AUTOMATE
RENDERING + RULES
USING MAPNIK
Minimize manual work
and configuration
settings
2 3 4
NEXT STEP: HAVING SUPPORT
FOR MAPPING VECTOR TILES
WOULD BE AMAZING!
Meanwhile, we can use
PostGIS, or GeoPackage
to MVTs (T-REX) now

33. III. Managing mobile/360 photos with
BOX, GIS and FME

34. III. Managing photos/360 with BOX, GIS and FME
1

35. III. Managing photos/360 with BOX, GIS and FME
2
Camera
Monopole
“LocationID”
Demo 3.1

36. III. Managing photos/360 with BOX, GIS and FME
2
Camera
Monopole
“Location ID”
Light cover
LED Lights
Lasers to mark
direction
Manhole
hangers
Setup for taking photos of manholes (upside down)
Demo 3.2

37. III. Managing photos/360 with BOX, GIS and FME
3

38. STEP 1: Image/Photo Collection: use BOX
Demo 3.3

39. STEP 1: Image/Photo Collection: use BOX

40. III. Managing photos/360 with BOX, GIS and FME
4

41. Workflow
Establish
GIS Web-
services
• Sign point geometries +
attributes + links to photos in
cloud storage (BOX)
• Build web-
maps/application/story maps
Derive
Sign’s
Locations
• Using photo location and view
cone + Aerial photo
• Establish sign location
• 1 or more GIS users/editors
Extract
Metadata
and Location
from Photos
• ETL attributes
• ETL XYZ + direction for each
photo
• Automated Process (FME)
• Create GIS Layer with photo
locations
Attribute
Photos
using BOX
• Specify sign attributes
• Enter sign text
• 1 or 2 users (general)
• In Office
• BOX = Image Management
System + web-asset storage
Data
Collection
• Take photos of signs
• Mobile device encodes
XYZ/direction into EXIF header
of an image
• Upload to BOX
• 1 or more users (general)
• Field work

43. ● FME supports BOX as a web connection/OAuth2
2.1 extract images' metadata from BOX into GIS table
Shared, downloadable link, all metadata attributes, including sign
text
2.2 extract XYZ & DIR from photos into a spatial table
3.3 join spatial table of sign locations with an signage
attribute/metadata table.
STEP 2: BOX TO DATABASE + GIS WITH FME

44. STEP2.1 : GET PHOTO METADATA from BOX
● IN: BOX FOLDER ID
● OUT: TABLE WITH ALL ATTRIBUTER INCLUDING SIGNAGE TYPE, CONDITON, TEXT, ETC

45. STEP2.1: GET PHOTO METADATA from BOX
● IN: BOX FOLDER ID
● OUT: TABLE WITH ALL ATTRIBUTER INCLUDING SIGNAGE TYPE, CONDITON, TEXT, ETC

46. ● IN: PHOTOS TABLE – BOX File_Id + URL
● OUT: SQL TABLE (ATTR TABLE – X/Y/Z/DIR + Geometry)
STEP2.2: GET LOCATION/DIRECTION DATA FROM
BOX

47. III. Managing photos/360 with BOX, GIS and FME
5

48. 1
CLOUD STORAGE IS
MORE THAN JUST
STORAGE
Reach APIs,
metadata, 360 viewer
support
III. SUMMARY & TIPS
CLOUD STORAGE
PROVIDES ALL NEEDED
FUNCITONS FOR
USERS
FME ENABLES
INTEGRATION OF
EXISTING SYSTSM VIA
APIs
Minimize manual work
and configuration
settings - automate
2 3 4
TRANSFORMER TO EXTRACT
ONLY EXIF METADATA FROM
CLOUD IMAGES
Ability to read EXIF
metadata w/o
downloading thousands
of images
Easier adopton by
users

49. ACKNOWLEDGEMENTS
● Roxanne Verdi and Nan Wang ( Space Management )
● Jason Venditti and Carl Larson ( Design and Construction Management)
● Joseph Balzano (Design and Construction Management)

50. THANK YOU!
Alexander Stepanov
stepanov@umass.edu