Using FME to move from AutoCAD Map 3D to MapGuide Enterprise with SQL Server

2,343 views
2,218 views

Published on

Small cities in Canada have two solitudes: CAD and GIS. Using FME, this chasm can be easily bridged. This session will explore how you can move AutoCAD DWG files to SQL Server Spatial for display within Autodesk MapGuide Enterprise. We'll focus on how FME's recent support for Object Data within DWG opens the doors for seamless migration between CAD and GIS.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,343
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
30
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Using FME to move from AutoCAD Map 3D to MapGuide Enterprise with SQL Server

  1. 1. Using FME to Move from 2010: AutoCAD Map 3D to MapGuide An FME Odyssey Enterprise with SQL Server Gordon Luckett GIS Consultant
  2. 2. AutoCAD to SQL Server with FME Two Solitudes: CAD and GIS
  3. 3. AutoCAD to SQL Server with FME About the Speaker:   Gordon Luckett   GIS Consultant for 14 years   Arrow Geomatics Inc.   Focus on Spatial Databases   SQL Server 2008   Oracle Spatial/Locator 8i and up to 11G   Primary Focus: Government Web GIS
  4. 4. AutoCAD to SQL Server with FME Proof of Concept   SQL Server 2008 City of Grande Prairie, Alberta Task:   Hundreds of DWG files   Contain “Object Data”   Move to SQL Server 2008 automatically   Render in MapGuide Enterprise
  5. 5. AutoCAD to SQL Server with FME Why SQL Server 2008? MapGuide AutoCAD Civil 3D SQL Server AutoCAD Map 3D ArcMap MapInfo
  6. 6. AutoCAD to SQL Server with FME What is Object Data?   Stored within DWG   Custom property   Text   Integer   Double   Only in:   AutoCAD Map 3D   AutoCAD Civil 3D
  7. 7. AutoCAD to SQL Server with FME How to get Object Data out of the DWG traditionally:   Export to SDF   Export to SHP   Export to …   Manual process per layer   Requires re-import into SQL Server
  8. 8. AutoCAD to SQL Server with FME Alternative solution FDO for Map 3D:
  9. 9. AutoCAD to SQL Server with FME Alternative solution FDO:   Push all data into SQL Server   Maintain SQL Server data directly from within Map 3D and Civil 3D with FDO   Directly Draw in Map 3D into SQL Server   Directly enter attribute data into SQL Server
  10. 10. AutoCAD to SQL Server with FME Downside to FDO:   Some Traditional CAD objects not supported (i.e. Leaders, Dimensions, Wipeouts, etc)   Object Data not available to share data once brought back in   New learning curve to technicians and engineers.
  11. 11. AutoCAD to SQL Server with FME Obvious Solution: FME Desktop!
  12. 12. AutoCAD to SQL Server with FME Translator – Choose AUTOCAD_OD type Supports Object Data in the DWG
  13. 13. AutoCAD to SQL Server with FME   Translator – Choose SQL Server Spatial Type
  14. 14. AutoCAD to SQL Server with FME   In – AutoCAD Map DWG with Object Data   Out – SQL Server 2008
  15. 15. AutoCAD to SQL Server with FME   Spatial Data now in SQL Server
  16. 16. AutoCAD to SQL Server with FME   Generate a Batch to Repeat Nightly
  17. 17. AutoCAD to SQL Server with FME   Use Windows Schedule Tasks run nightly
  18. 18. AutoCAD to SQL Server with FME   Show SQL Server Parcels in MapGuide
  19. 19. AutoCAD to SQL Server with FME   Demonstration
  20. 20. AutoCAD to SQL Server with FME Final Note No Longer Two Solitudes: CAD and GIS
  21. 21. Thank You!   Questions?   For more information:   Gordon Luckett gordon.luckett@arrowgeo.com   Arrow Geomatics Inc. Other Resources   fdo.osgeo.org   www.mapguide.ca

×