FME in Urban Information Modeling


Published on

This presentation shows the use of FME technology in complex data model transformation tasks such as the creation of CityGML from diverse data inputs as well as transformation of data out of the CityGML format into industry standards.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

FME in Urban Information Modeling

  1. 1. CONNECT. TRANSFORM. AUTOMATE. FME in Urban Information Modeling Lutz Ross / Jens Frolik Head of System Integration / Geodata Engineer
  2. 2. LoD2 Model Frankfurt Airport
  3. 3. Berlin 3D City Model
  4. 4. 3D SDI Hamburg
  5. 5. Table of Content  Who we are and what we do  Urban Information Modeling (UIM)  FME and CityGML Examples  Summary CONNECT. TRANSFORM. AUTOMATE.
  6. 6. Who we are and what we do  virtualcitySYSTEMS GmbH, Berlin  14 employees  Consulting, Training, Software, and Services  Our Focus  3D GeoIT solutions based on CityGML data  OGC Services WMS/WFS/WPVS integration  Web-based 3D GIS
  7. 7. Urbanization Source:
  8. 8. Urbanisation  Cities are getting bigger, more complex, and need to serve more needs than ever before  Big challenges:  Urban planning, security, infrastructure and building maintenance, traffic control, energy planning, event managment, …  Require new solutions  Smart Cities, „rich-in context design“ - Integrated planning, analysis, and simulation
  9. 9. Urban Information Models Source: Prof. Dr. Thomas Kolbe, TUM
  10. 10. CityGML as Data Model
  11. 11. CityGML  Pro: Semantics, Geometry, Topology and Appearance on man-made and natural topographic features  Con: Complex data model, few commerical tools, no CityGML editor, few viewing solutions  And still: There is a growing adoption worldwide
  12. 12. 3D City Database  CityGML database solution  Open Source project:  Relational database model for Oracle Spatial and PostGIS  In use by many municipal/federal agencies in Germany  virtualcityDATABASE is build on top of the Open Source version
  13. 13. CityGML Database
  14. 14. 3D Wepmapping  Based on CityGML database
  15. 15. 3D Weppmaping Application
  16. 16. FME and CityGML  FME supports reading and writing CityGML!  FME can:  Read and extract information from CityGML  Transform heterogeneous data into CityGML  Be used to automate processes  Has become a core technology in our solutions
  17. 17. FME and CityGML Examples  Transforming Data to CityGML  Importing and Cataloging Data  Data Distribution
  18. 18. Example: Transforming to CityGML  Growing list of Transformations  Shape (PolygonZ) to CityGML building features  DWG/DXF TIN data to CityGML ReliefFeature  Points + terrain data + 3d tree models to CityGML SolitaryVegetationObject  …  Current Challenge: IFC to CityGML
  19. 19. Workspace
  20. 20. CityGML Result
  21. 21. Courthouse Square LoD3
  22. 22. IFC2CityGML  Transformation is possible  Outcome looks fine and validates  Still: Not as it should be from the conceptual idea of CityGML  Current mapping: IFC Wall (Solid) -> CityGML Wall (MultiSurface)  Should map to: IFC Wall (Solid) -> OuterWallSurface and InteriorWallSurface  Solution: IFC views
  23. 23. Example: Importing and Cataloging  Task: Transform well-defined input data to CityGML and  Create a metadata record in Geonetworks  Import the CityGML data to the 3DCityDB  Solution: One FME Workspace does it all
  24. 24. Example: Importing and Cataloging SHP TIF FLT CSV RGB 1. Transformation to CityGML 2. Creating a metadata record 3. Inserting metadata to CSW 4. 3DCityDB-Importer Configuration Shutdown Script triggers 3DCityDB Import 3DCityDB FME Server Geonetworks CSW insert operation via HTTPUploader
  25. 25. CityGML database grows
  26. 26. Example: Data distribution  Remember? CityGML is not supported by most GIS/CAD/BIM tools natively.  Potential users of the 3D data need it in a format supported by their tools  Solution: A FME workspace  Custom reader for our CityGML database  Data transformation in common 3D formats  Published parameters  For FME Desktop and Server
  27. 27. Workspace
  28. 28. Data distribution  Users can easily  Select the features/area they want to extract  Select the required LoD and appearance  Select the target format  Data extraction and transformation is automated  FME Desktop or FME Server
  29. 29. What you see is what you get  Export functionality integrated into our web- visualization solution
  30. 30. FME completes our 3D SDI solution
  31. 31. FME completes our 3D SDI solution
  32. 32. Summary  FME enables our customers to transform existing 3D data into CityGML  FME supports us and our customers to build up and maintain 3D geodatabases based on the CityGML standard  FME enables our customers to transform CityGML data into formats required by their customers (end-users)  FME is fun and has great support!
  33. 33. Thank You!  Questions?  For more information:  Lutz Ross,  Jens Frolik,  virtualcitySYSTEMS GmbH CONNECT. TRANSFORM. AUTOMATE.