Incorporating CAD Data in GIS

Don KuehneESRI Product Management, CAD

Specialist

1

Overview

• Definition of Standards & Interoperability

• ESRI CAD Interoperability Solutions

• Interoperability Demonstrations

2

GIS/CAD are Complementary

• GIS gives CAD context of existing world (Base Map)

• CAD provides GIS with New Content

3

Distinctions Between CAD / GIS

Tools leverage formally defined database schema for editing

Tools for unconstrained data creation

Medium-small scaleLarge scale

Topographic/ thematic mapsAEC Content

Database paradigmDrawing/ model/ document paradigm

Data-centricGraphic-centric

Cartography / spatial analysis / modeling

AEC/CAD Design & Analysis / Mapping

Horizontal applicationsAEC/CAD applications

GISCAD

4

What is Interoperability?Common Definitions

• Multiple Data Types In Single Editor

• Single Data Source Multiple Editing Environments

• Semantic Translation

5

Standards Approach To Interoperability

• CAD Standards Improved Data Quality And Usability– Digital data asset rather than printed map or

construction plan

• Result Of Extending Scope of Standards Beyond Local Use:

1. Lowest Common Denominator2. All of Everything

6

ESRI CAD/GIS Interoperability Solutions

• Direct Read

• Bi-Directional Semantic Translation

• CAD-Based GIS Data Access

7

Direct Read

ArcGIS CAD Data Sets &ArcGIS Data Interoperability Extension

– In- Memory– Spatial Database View– Custom/Composite Views (Interop Extension)– Supports Points, Lines, Areas, Text, Blocks/Cells,

Attribute Tags, 3D Features– Objects Treated Equally With Other GIS Data

Sources

8

ArcGIS CAD Tools

9

Directions MagazineBridging the Worlds of CAD and GIS

Part 1 of a Series on CAD-GIS

“ The development of formalized semantics is crucial to achieving the true integration of CAD and GIS. First, the semantics (of geometry and other information) within a domain need to be formalized ”

-Peter Van Oosterom

10

CAD/GISSemantic

Translation

CAD Drawing Files GIS Layers

Entity Type = LINE

Color = RED

Layer = WATER_LINE

Linestyle = STANDARD

Geometry = [LINE]

******

Entity Type = TEXT

Color = BYLAYER

Layer = PIPE_TEXT

Font = STANDARD

Value = 8”

Multiple CAD ObjectsAnd Properties

Pipe ID Owner

Date InstalledMaterial Type

GeometryDiameter

Single GIS Pipe Feature With Attributes

8 inch

1985

Cast Iron

[Line]

8” 8”

11

ModelBuilder

12

Geoprocessing Semantic Translation Demo

13

GP IMPORT FROM CAD Tool• ArcView GP Tool

• CAD Staging PGDB

• Multiple File Support

• Highly Normalized

CAD Document Feature Class (Area)

Point Feature Class (Point)

Area Feature Class (Area)

Line Feature Class (Line)

CADStaging Feature Data Set

Standard Property TablesEntity Property Table (Entity)

Text Property Table (TxtProp)

Layer Property Table (CADLayer)

Extended Attribute TablesScratch Table of XData (XData)

Attribute Tags (Attrib)

Enumerated XData Table (XtrProp)

MSLink Table (MSLink)

Created By Don Kuehne, ESRI Product Management CAD Specialist, 2003

Contains the geometry of all objects that can be interpreted as point features from imported CAD files

Contains the geometry of all objects that can be interpreted as line features from imported CAD files

Contains the geometry of all objects that can be interpreted as polygon features from imported CAD files

Contains a record for each CAD entity and its entity specific properties.

Contains the geometry of the coordinate extents of all imported CAD files, and document specific properties

Contains a record for each text or attribute tag entity and its text specific properties.

Contains a record for each CAD layer and its layer specific properties.

Contains a record for each entity that has XData and an XML string of all the extended entity data, EED. (AutoCAD only)

Contains a record for each attribute tag entity and its attribute tag specific properties (Many-to-One) To make use of this table with more than one tag value per SetName, you must pivot this table.

Normalized table of extended entity data, created from XData table. Column names based on AutoCAD registered application name and ADE string or type value.

Contains a record for each MSLink value and properties on each entity found in the imported CAD files. (Many-to-One, Microstation Only)

The ArcGIS IMPORT FROM CADThe ArcGIS IMPORT FROM CADStaging GeodatabaseStaging GeodatabaseSchema MapSchema MapThe CAD Staging Geodatabase is the output of the IMPORT FROM CAD Geoprocessing tool. Included here is a map of the schema of the CAD Staging Geodatabase. Lines drawn show the relationship between the various primary and secondary foreign keys. You can use this information to join the tables indifferent combinations.

Often CAD data schemas may not be conducive to using the predefined database view of the direct file read CAD feature data set. In such cases you need the flexibility of to assemblethe CAD information depending on the desired result. Unlike the direct file read CAD Feature data set, you can create your own database view of one or more CAD files using the normalized tables contained in a CAD Staging Geodatabase.

Sample: Pivoted Attrib Table

When working with AutoCAD blocks and Microstation tag set with more than one attribute it is most useful to pivot the Attrib table to obtain a normalized table of attributes linked to the OwnerID.

15

Creating CAD DataDemo

16

Data Interop Extension: WorkBench

17

Data Interoperability Extension

• Custom datasources are added in ArcCatalog, useful for merging multiple CAD files or reconfiguring

– Direct Read 70 New Formats including:– AutoCAD, MapGuide, Microstation, MGE, Geographics– Includes Workbench schema mapping tool to build custom/composite data

sources

• DIE’s Workbench provides translation functionality, but may require use with geoprocessing to do more complex spatial translation and to combine the derived data in various workflows that include geoprocessingoperations.

• DIE created data sources are valid input feature sources for GP translation tools.

CAD Translation in Geoprocessing• All Direct Read options are potential data sources:

– ESRI CAD Feature Data Sets (ArcView)– Data Interoperability Extension: Custom Direct Read (Extension)

19

CAD-Based CAD/GIS Applications• ESRI’s, ArcSDE CAD Client

• Bentley Systems’ ArcGIS Connector

• Haestad Methods’ GIS Connect

ESRI’s ArcSDE CAD Client Haestad’s GIS Connect Bentley's ArcGIS Connector

20

CAD Versions Supported by ArcGIS 9.0• ArcGIS Direct Read (R/O)

– Autodesk DWG/DXF R14-2004– Bentley DGN V7, V8

• Data Interoperability Extension (R/W)– Autodesk: DWG/DXF R14-2004. MapGuide– Bentley MGE/Geographics, DGN V7, V8

• Geoprocessing Translation (R/W)– Autodesk DWG/DXF R14, 2000, 2004– Bentley DGN V8(R/W), V7 (R/O)

21

ArcGIS Data Interoperability Extension

Demo

22

CAD Solutions by User Requirement• “ArcGIS User” Wants to Use a CAD file without Conversion As Data Source

– Native CAD file read (ArcView)– DIE (Extension $2500)

• “ArcGIS User” Wants to Merge Multiple CAD Files without Conversion As Data Source– DIE (Extension $2500)

• “ArcGIS User” Needs to Extract Simple Features from CAD files– Native CAD file read with Simple Data Loader

• “ArcGIS User” Needs to Build Geodatabase from CAD Data– DIE with or without Geoprocessing depending on need of translation task (Extension $2500)– Native CAD file read used in Geoprocessing (ArcView)– [Import from CAD] tool in Geoprocessing for more flexibility (ArcView)

• “ArcGIS User” Needs to Create CAD Files from GIS Data– DIE (Extension $2500)– Geoprocessing tool [Export to CAD] (ArcInfo)

• “CAD User” Wants Access to ArcSDE Enterprise Geodatabase– ArcSDE CAD Client (Read/Only)– Read/Write for ArcSDE Simple Feature Layers not registered with the Geodatabase

• “CAD User” Wants to Edit Geodatabase and other ArcGIS Data– Haestad’s GIS Connect for AutoCAD (Requires ArcInfo)– Bentley’s ArcGIS Connector for Microstation (Requires ArcInfo)

• “You” Your Application…