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.
Upcoming SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Loading in …3
×
1 of 67

Bridging Between CAD & GIS: 8 Ways to Automate Data Integration

0

Share

Download to read offline

Converting between CAD and GIS is a common requirement for projects involving infrastructure, buildings, city plans, and more. Unfortunately, the workflow presents many challenges, like translating geometry, attributes, annotations, symbology, geolocation, and other elements.

So how do you allow data to flow freely between these disparate data types, without losing the precision offered by CAD and the spatial context offered by GIS?

This webinar will explore the power of automated data integration workflows for CAD and GIS.

First, we’ll discuss challenges and scenarios for CAD-to-GIS translations, and demo how to use FME to power a digital plan submission portal that validates CAD data and integrates it into the central GIS repository. Next, we’ll discuss challenges and scenarios for GIS-to-CAD conversions, and demo how to build an automated FME workflow for requesting CAD data from GIS.

At the end of the webinar, you'll know how to achieve harmony between CAD & GIS by automating its integration.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Bridging Between CAD & GIS: 8 Ways to Automate Data Integration

  1. 1. Bridging Between CAD & GIS: 8 Ways to Automate Data Integration
  2. 2. Meet the Presenters Dale Lutz Jovita Chan
  3. 3. Agenda for today: ● Migrating CAD drawings to GIS ○ Challenges (complex geometry, annotations) ○ Real-world solutions ○ Demo: Digital plan submission workflow ● Sharing GIS data with CAD users ○ Challenges (coordinate systems) ○ Real-world solutions ○ Demo: Requesting CAD data from GIS workflow ● Q&A
  4. 4. Our Mission To help you maximize the value of data.
  5. 5. FME® Integration Platform Connect. Transform. Automate. FME Desktop FME Server FME Cloud Build & Run Data Workflows Automate Data Workflows (on-premises) Automate Data Workflows (hosted FME Server) Mobile Apps Access the Power of FME Wherever You Are Get a free trial of FME Desktop and FME Server at safe.com
  6. 6. CAD vs. GIS: Different Perspectives CAD users have a drawing perspective: ● Layers & levels ● Styles & Symbology ● Dimensions & Labels
  7. 7. CAD vs. GIS: Different Perspectives GIS users have a feature perspective: ● Attributes and geometry ● Data structure, model ● Relational tables, domains ● Location (including Coordinate System) ● Connectivity and proximity ● Analysis
  8. 8. Scenario 1: Building Areas Part 1: Migrating CAD Drawings to GIS
  9. 9. Scenario 1: Building Areas for GIS The Task Convert Microstation drawn Forest Cover maps to be used in GIS analysis The Problem Forest Cover maps store boundary lines and interior points to represent areas. GIS wants areas with attributes. The Solution Use FMEʼs AreaBuilder and PointOnArea Overlayer to create the areas with correct attributes The Result GIS ready data from a process easily automated and able to run over thousands of input files.
  10. 10. Input
  11. 11. Solution
  12. 12. Recap: Building Areas for GIS The Task Build areas from CAD linework Tips for Success ● Discover the names FME assigns to CAD properties to filter/route data ○ Feature Information Window ○ Feature Type -> Format Attributes ○ Tester ● Use Geometric operations to convert representation to information ○ AreaBuilder ○ PointOnAreaOverlay The Solution Use FMEʼs transformation capabilities to quickly convert CAD lines and points into GIS ready data
  13. 13. Scenario 2: Transforming from CAD to GeoJSON Migrating CAD Drawings to GIS
  14. 14. Transforming from CAD to GeoJSON The Task Create a GeoJSON File containing geometries and text from original CAD files. The Problem DWG file has rooms drawn as closed polylines, all in 1 layer. Within each polyline, there are 2 text labels on different layers. The Solution Extract CAD properties into unique attributes and combine multiple entities into one. The Result Data where it needs to be! The rooms are transformed to geometries and text labels are properties of the geometries. Scenario 2
  15. 15. Thanks to our community for this great question! Ask a question & get answers at safe.com/community
  16. 16. Input: Township of Langley Open Data
  17. 17. Solution
  18. 18. Recap: Transforming from CAD to GeoJSON The Task Produce a single GeoJSON file. Tips for Success ● Extract CAD properties into unique attributes with TextPropertyExtractor ● Use PointOnAreaOverlay to combine multiple entities into one ● Use Tester to do sanity checks The Solution Extract CAD properties into unique attributes and combine multiple entities into one.
  19. 19. Canʼt Remember 400+ Transformers? Find your perfect transformer safe.com/transformers You donʼt need to! Use the FME Transformer Gallery. ● Filter by category ● Quick Add aliases (verb + ʻerʼ) ● Access it in Workbench (View > Windows > Transformer Gallery)
  20. 20. Scenario 3: Moving From Labels To Attributes with Proximity Migrating CAD Drawings to GIS
  21. 21. Scenario 3: Moving From Labels To Attributes with Proximity The Task Transfer label information to nearby lines. The Problem Containment is not an option. The Solution Proximity matching with the NeighbourFinder. The Result Label information is transferred to nearby lines.
  22. 22. Input:
  23. 23. Solution
  24. 24. Recap: Moving From Labels To Attributes with Proximity The Task Transfer label information to nearby lines. Tips for Success ● Use NeighborFinder to do proximity matching ● Automate QA using Tester ○ Humans may need to do final QA ● Consider LineCombiner to join short lines into longer ones ○ Pseudo-node removal The Solution Proximity matching.
  25. 25. Scenario 4: Battling Schema Drift Migrating CAD Drawings to GIS
  26. 26. What is Schema Drift? Solve more schema drift: safe.com/webinars A change in the source or target data definition. Usually accompanied by frustration and time loss. “Theyʼve added yet another column to my excel spreadsheet – this schema drift has got to stop!”
  27. 27. Schema Drift Example 1: No naming specification followed Road, Street, Roads, Streets, StreetLines, ...
  28. 28. Overcoming Schema Drift Example 1: No naming specification followed The Task Migrate CAD linework to a new CAD standard for use in both CAD and GIS. The Problem No specification was followed (or it changed) and the input layers have a wide range of names The Solution Scan for the complete set of names and make a mapping to the desired CAD/GIS naming. Apply the mapping on translation. The Result A flexible input process created with a minimum of manual effort and a cleaned up CAD file ready for sharing or GIS import!
  29. 29. Recap: Moving to a Naming Specification The Task Modify CAD data to conform to a naming convention for layers Tips for Success ● Use DuplicateFilter to find unique layer names ● Track the layer mapping in spreadsheet ● Apply the layer mapping using a DatabaseJoiner ● Use Feature Type Fanout to route data to the new, correct layers The Solution Extract existing names, create a mapping spreadsheet, apply to create conformant CAD files
  30. 30. Schema Drift Example 2: Decode Attribute-rich Layer Names Layer Name: xxxYYYYMMDDzz xxx = 3 character code for road type YYYYMMDD = 8 digits for date of last update zz = 2 characters to represent collection method
  31. 31. Overcoming Schema Drift Example 2: Decode Attribute-rich Layer Names The Task Extract attributes encoded in CAD layer names for use in GIS The Problem A comprehensive specification embedded attributes in parts of the layerʼs name, making it very hard to understand or otherwise use the data. The Solution Split attributes to pick out the parts, then apply lookups to decode to useful values. The Result Understandable, GIS-ready dataset.
  32. 32. Recap: Decode Attribute-rich Layer Names The Task Extract attributes encoded in CAD layer names for use in GIS Tips for Success ● AttributeSplitter to break apart the layer name ● Expose the resulting list elements result{}->result{0},result{1}... ● Decode the parts using a DatabaseJoiner or AttributeValueMapper ● Route to an attribute-rich GIS dataset The Solution Split layer names into parts, apply lookups to create understandable attribute values
  33. 33. Scenario 5: Digital Plan Submission Migrating CAD Drawings to GIS
  34. 34. CUSTOMER STORY “We chose FME for this project because the interface is easy to use and allows us to provide an adaptable solution to enhance interaction with the Cityʼs partners” - Erika Provost, City of Henderson PROJECT Digital Plan Submission Project SOLUTION FME provides self-serve CAD data upload, validation, and integration into GIS RESULTS ● Reduced data integration time by 75% ● Eliminated the risk of manual error ● Removed duplicate work ● Faster processing of submissions ● Ensured CAD data validation City of Henderson
  35. 35. Scenario 5: Digital Plan Submission The Task Create a digital plan submission to automatically check and upload CAD drawings to ArcGIS Online. The Problem It takes time and manual effort to process development plans (clean up geometry, and extract data), to combine into GIS data. The Solution Use FME to validate CAD submissions before automatically uploading to ArcGIS Online. The Result Submissions that meet requirements are uploaded to ArcGIS Online, and ones that donʼt are sent back for fixing.
  36. 36. Input: DWG Parcels
  37. 37. Demo CAD Standards: ● Attribution: ○ Layer schema (specific layer naming) ○ Parcels contain ID ○ Roads have names ● Geometry ○ Layers contain specific geometry (ex. roads are lines) ○ Parcels are polygons ○ Blocks are points
  38. 38. Next stop... Enable event-driven automations using a web user interface. FME Server
  39. 39. Results in ArcGIS Online: Parcels Layer Roads Layer
  40. 40. Recap: Digital Submission Plan The Task Create a digital plan submission from DWG to AGOL. Tips for Success The Solution Use FME to check CAD submissions for criteria before automatically uploading to ArcGIS Online. ● Preserve labels and attribution from text, blocks or dimensions ● Interpret layers, styles or symbols as attributes ● Improve geometry: ○ Creating connectivity ■ Snapper ■ Intersector ○ Forming areas from lines ■ AreaBuilder ● Combine geometry and attributes using proximity ○ PointOnAreaOverlay ○ NeighborFinder
  41. 41. Part 2: Sharing GIS data with CAD users
  42. 42. GIS to CAD Challenges ● Creating visually appealing CAD drawings ● Represent GIS intelligence ● Use expected symbology
  43. 43. Sharing GIS data with CAD users Scenario 6: Applying Styling
  44. 44. Scenario 6: Applying Styling The Task Produce output conforming to the CAD styling specification of the engineering department. The Problem GIS data doesnʼt have explicit styling information, but a CAD styling specification is available. The Solution Use the DWGStyler or DGNStyler to prepare data for output to CAD. Store styling information in a spreadsheet and apply it during translation. The Result Happy CAD technicians and an effortless flow of data between departments and disciplines.
  45. 45. Input: Source: City of Gävle Open Data
  46. 46. Solution:
  47. 47. Output:
  48. 48. Recap: Applying Styling The Task Produce output conforming to the CAD styling specification of the engineering department. Tips for Success ● Hold styling specifications external to the FME Workspace ● Use a Template CAD file to provide symbol and layer definitions ● Apply using a DatabaseJoiner ● Use DWGStyler to set appropropriate styling format attributes The Solution Store styling information in a spreadsheet and apply it during translation.
  49. 49. Sharing GIS data with CAD users Scenario 7: Self Serve Data Requests
  50. 50. CUSTOMER STORY Project Automated “One Call” system Solution FME automatically extracts information from GIS and asset management systems to fulfill underground information packages. Results ● Reduced package turnaround time from 3 days to 3 minutes. ● Re-allocated dedicated staff resource to other high-value services. ● Removed the risk of manual errors. City of Burnaby “Because of FME we were able to process tickets 24/7 - anytime, anywhere.” Herman Louie, City of Burnaby
  51. 51. Self Serve Data Request The Task Deliver data and assets around the office to the departments that need it, whenever they need it. The Problem The only way to access data is by talking with the stakeholders. This leaves employees waiting for responses and wasting time. The Solution Build a self-serve data portal using FME. The Result Improved collaboration as users can serve themselves accurate data whenever they want to.
  52. 52. Solution Using the Geometry Picker in FME Server
  53. 53. Template DWG
  54. 54. Recap: Self Serve Data Request The Task Deliver data and assets around the office to the departments. Tips for Success The Solution Build a self-serve data portal using FME ● Use styler transformers to easily set format attributes ○ DWGStyler ○ DGNStyler ● Use labeller transformers to generate labels ○ LabelPointReplacer ○ Labeller ○ MapTextLabeller (extra cost)
  55. 55. Achieve harmony between CAD & GIS by automating its integration.
  56. 56. Tutorials in the FME Community ● GIS to CAD: Convert Parcel Polygons and Lines from Geodatabase to DGN ● How to Convert DGN to Shapefile (CAD Levels to GIS Attributes) ● Getting Started with AutoCAD ● Using the Geometry Picker in FME Server
  57. 57. Thank you! Try FME for free: safe.com/trial Please type in your questions.

×