c)

c> US Army Corps

* of Engineers®
Engineer Research and
Development Center
J
LLJ
*
*

CJ)
c)
c* Integrating CAD Data with Geographic
LIi
Information Systems Using AutoCAD
and ARC/INFO Software
Paul T. Cedfeldt and Mark A. Scott March 2000

>> 4* ARCPLOT laBiiUnLiiiinJ

Pan/Zoom
O
li»fl
Harbor Expansion Study Area
O o
05 .Q
CO
gine ing
egio

a: ii
^ui
N\

~u
o c • Borehole
o 05
X:8.97581 Y:10.6975B dx:8.97581 dy:10.69758 Dist 13.96436

Approved for public release; distribution unlimited.

"tync QUALITY IN&PfiC'i^D 8

20000509 102
Technical Report
ERDC/CRREL TR-00-1
US Army Corps
of Engineers®
Cold Regions Research &
Engineering Laboratory

Integrating CAD Data with Geographic

Information Systems Using AutoCAD
and ARC/INFO Software
Paul T. Cedfeldt and Mark A. Scott March 2000

Prepared for
OFFICE OF THE CHIEF OF ENGINEERS

Approved for public release; distribution is unlimited.

PREFACE

This report was written by Paul T. Cedfeldt, Physical Scientist, Geochemical Science
Division, U.S. Army Cold Regions Research and Engineering Laboratory, Engineer Re-
search and Development Center, and Mark A. Scott of the Environmental Systems Re-
search Institute, Redlands, California.
Funding for this project was provided by the U.S. Army Corps of Engineers Alaska
District.
The contents of this report are not to be used for advertising or promotional purposes.
Citation of brand names does not constitute an official endorsement or approval of the use
of such commercial products.
CONTENTS

Preface ii
Introduction 1
Software overview 1
AutoCAD 1
ARC/INFO 2
Datastorage 2
AutoCAD R14 drawings 2
ARC/INFO 7.2 coverages 2
ARC/INFO coverage features 3
Modeling ARC/INFO features with AutoCAD entities 4
Point features 4
Arc features 5
Polygon features 6
Annotation features 6
AutoCAD symbology data and data organization 6
Layers 7
Colors 7
Line types 7
Line width 7
Problems to avoid 7
Using 3-D data 7
Model space and paper space 7
Details and title blocks 7
Groups 7
Multilines and other entities 8
Hatching 8
External references 8
Dimensions and leaders 8
Blocks as grouped graphics 8
Layer 0 8
Georeferencing and coordinate systems 8
Methodology 8
Layering standards and conventions 8
Color and line type schemes 8
Using text or block inserts as data tags 9
Converting the data: DXFOUT and DXFARC 9

III
Summary and process step example 10
Appendix A: ArcView GIS 3.1 15
Appendix B: ARC/INFO 8.0 17
Abstract 19

ILLUSTRATIONS

Figure
1. CAD and GIS software data storage 3
2. ARC/INFO point feature 3
3. ARC/INFO arc/node features 4
4. ARC/INFO polygon features 5
5. Representing ARC/INFO arc features with AutoCAD entities 6
6. AutoCAD drawing containing water data 11
7. Using the ARC/INFO DXFARC command 12
8. Using the ARC/INFO NEAR command 13
9. ARCPLOT canvas showing converted data 13
10. Flowchart showing conversion from AutoCAD to ARC/INFO 14

TABLES

Table
1. AutoCAD data types and ARC/INFO coverage equivalents 11

IV
Integrating CAD Data with Geographic Information Systems
Using AutoCAD and ARC/INFO Software

PAULT. CEDFELDTAND MARK A. SCOTT

INTRODUCTION
This document offers the reader a methodology for objects to AutoCAD objects, and the concepts should
effectively integrating data created using AutoDesk's carry over accurately. For example, layers in AutoCAD
computer-aided design (CAD) software AutoCAD correspond to levels in MicroStation, AutoCAD
(R14) with ESRI's (Environmental Systems Research polylines correspond to linestrings in MicroStation, and
Institute's) ARC/INFO (version 7.2) geographic infor- blocks map to cells.
mation system (GIS) software. Although we intend to
educate CAD and GIS users to ways of facilitating the
SOFTWARE OVERVIEW
creation of data in CAD for use in GIS, it is not within
the scope of this document to consider compatibility CAD and GIS software, while different, are often
issues between every object type in each system. We used in conjunction with one another. The two pack-
do, however, discuss a set of issues that are representa- ages are concerned with three types of data: coordinate
tive of the data integration hurdles faced by many CAD data, descriptive attributes, and graphic symbology.
and GIS users. Traditionally, CAD software stores graphic symbology
At the writing of this paper, AutoCAD 2000 had been and geometric coordinates in the object information in
released but had not yet been tested for this document. the drawing database. The final product is often a
ESRI plans to fully support AutoCAD 2000 in upcom- paper map, so symbology and appearance take prece-
ing versions of its software. ArcView 3.2 is in produc- dence during the data creation process. GIS software,
tion to support AutoCAD 2000 data, and ARC/INFO however, is primarily concerned with the geographic
8.0 is in beta testing. ARC/INFO 8.0, with its coordinates (not to be confused with geometric coordi-
GeoDatabase model, is a new development in ESRI's nates) and descriptive attributes stored in a relational
GIS model. The appendixes and a future revision to database. The GIS database is targeted at providing a
this document will include discussion of Arc View 3.1 continuous digital model, connected to a database of
and ARC/INFO 8.0 in varying levels of detail. attributes, and it is intended for complex query and
CAD and GIS professionals such as engineers, sur- analysis. Symbology is applied map by map, based on
veyors, planners, and cartographers commonly integrate the values in the database.
AutoCAD drawing (.DWG) or drawing interchange
format (.DXF) files, developed internally or by outside AutoCAD
contractors, with ESRI formats such as ArcView AutoCAD is the most widely used PC-based CAD
shapefiles (.SHP) or ARC/INFO coverages. This docu- package on the market. It is primarily used in the
ment assumes that the reader has a professional level design and drafting of models in engineering, architec-
of knowledge of AutoCAD or ARC/INFO or both, but ture, and other disciplines, but it also serves as an
we provide base-level information for the sake of com- excellent generic geometric design tool. An engineer
pleteness. might use AutoCAD to design a site for a new mall,
Although this document is intended for an audience and an architect may use it to design a new building.
of AutoCAD users, MicroStation users can map their Whatever the discipline, the strength of AutoCAD lies
in its ability to allow the user to manipulate graphic tional mode desired. As we will see, this is both a
objects quickly and easily to create a finished hardcopy strength and a weakness when it comes to integrating
product. Traditionally, AutoCAD is concerned with two data. The user can organize data into logical layers and
types of data: each object in an AutoCAD model stores impose a methodology for the symbolization if desired,
its location (geometry) and the characteristics of its but this is not required. Although there is a great deal
appearance (graphics). A line may be drawn in a spe- of control over the geometry of the graphics, there are
cific color or using a specific line style (dashed, dotted, few built-in methods to attach descriptive information
etc.) that conveys information about its use. Further- via a database. This makes AutoCAD an attractive tool
more, AutoCAD uses an organizational approach in its to use for the capture of data because of its powerful
drawing (.DWG) files via a system of layers. These are editing engine. The task now becomes translating that
places where objects can be stored, with the user then work into a format that can be converted easily into
being able to manipulate their display as a group. Lay- ARC/INFO to facilitate advanced GIS data manipula-
ers can be assigned colors, although individual objects tion. The coordinate space upon which an AutoCAD
can have their own color. AutoCAD, being primarily a drawing exists is a double-precision, 3-D system, origi-
graphic system, uses the graphic characteristics of an nating at 0,0, and extending out in all directions.
object to carry information about itself. Primitive meth-
ods exist in AutoCAD to associate data with drawing ARC/INFO 7.2 coverages
entities, such as blocks and object data. One method is As mentioned, ARC/INFO stores data into logical
to simply create text in the drawing that visually units called coverages. A coverage stores a set of vec-
describes an entity but is not rigidly associated with tor-based geographic features, such as roads, soil bound-
the drawing object. Thus, the CAD package uses a aries, zip codes, buildings, city locations, sample wells,
graphic database for symbology and a geometric data- rivers, etc. Coverages are stored in a georelational for-
base for the coordinates of the dimensions of the mat, which means the vector features are associated with
objects. AutoCAD stores true geometry for circles, arcs, a database containing descriptive attributes of the fea-
ellipses, and other types of mathematical curves. tures such as zip code number, soil type, or stream name.
A coverage, taken as a whole, is a directory of files, all
ARC/INFO related together into a model that supports such topo-
ARC/INFO is the most widely used professional GIS logical relationships that may need to be created to sup-
software package. Professionals in many disciplines use port network tracing, polygon overlay, and other spa-
ARC/INFO to analyze relationships among the geo- tial operations. This topology is created by ARC/INFO's
graphic locations of features and the information BUILD and CLEAN commands and generates tables
describing these features. A GIS is a database in the to describe the relationships between coordinates that
fullest sense, relating tables of information that describe define linear features (arc-node topology) and tables
features to point locations, such as monitoring wells; to describe the relationships between linear features that
linear features, such as rivers or roads; and area fea- define closed polygonal areas (polygon-arc topology).
tures, such as county boundaries, parcels of land, or zip These relationships create a seamless, nonredundant
codes. The databases, spatial and attribute, are inter- database that describes the geometry of the geographic
related and can be used to create ad hoc symbology to data. Another key component of a coverage is that it
represent the state of the data, trends in the values, or has a specific coordinate system associated with it,
specific values searched on or queried for. ARC/INFO which can be described by its projection and datum.
stores these data in a series of georelational units called The datum is the ellipsoid upon which the surface of
coverages. The coverages store the coordinates that the earth is approximated, and the projection is the
make up the geometry of the features as well as the mathematical method via which the surface is "flat-
database that describes them. Coverages store this infor- tened" into a Cartesian coordinate mapping space. Fig-
mation as points (single coordinate locations), arcs (lin- ure 1 illustrates data storage concepts for both AutoCAD
ear connected segments), and polygons (closed areas), and ARC/INFO.
and more complex features such as regions.
ARC/INFO coverage features
ARC/INFO is capable of storing data in many simple
DATASTORAGE and complex features. Some examples of complex fea-
AutoCAD R14 drawings ture classes are routes (paths through multiple arcs),
AutoCAD R14 stores its data into files called draw- regions (collections of polygons in potentially overlap-
ings. A drawing can contain any design of graphic ping areas), and raster data sets such as images and grids.
objects that the user wishes to create, in any organiza- We will concern ourselves here with the simple 0-D,
CAD Software GIS Software

Graphic Attribute
Database Database

ARC/INFO Coverage

Figure 1. CAD and GIS software data storage.

1-D, and 2-D features of points, arcs, and polygons. in a LAB file that is linked internally to the point
These will then map through the conversion from attribute table (PAT).
AutoCAD points, block inserts, lines, polylines, light-
weight polylines, circles, arcs, and other drawing enti- Arc features
ties. Each ARC/INFO feature is connected to its fea- Arcs represent both linear features and the borders
ture attribute table via an internal ID system. This is of polygon features. Linear features represented by arcs
not a major concern to the AutoCAD user. However, can have length but no area, such as a contour line, or
creating a way to uniquely identify each entity by a can be long narrow features whose width is not appar-
system-dependent identifier might be a concern. For ent at a given map scale, such as a river. Each linear
example, each fire hydrant in a drawing may have some feature may be made up of many arcs. Since arcs also
unique number assigned by the Public Works Depart- form the basic linear infrastructure from which com-
ment. This ID might be placed in the drawing to iden- plex GIS processes are derived, such as tracing and
tify the hydrant. A CAD user might be satisfied to place surface computation, it is very important that an entity
this on the drawing to be plotted out. The GIS would be continuous. An arc is a continuous string of X,Y
need to store this value with the hydrant in the feature coordinate pairs (vertices), beginning at one location
attribute table, so it can join it to other databases in the and ending at another, stored in an ARC file. Geometri-
future. As we will see, there are various methods to cally, an arc is similar to an AutoCAD Polyline entity,
capture this type of information into ARC/INFO. which is often used to create ARC/INFO arc features.
The topological structure is created so that the starting
Point features and ending points are special locations known as nodes.
Points represent geographic features that have no The in-between points are the vertices that define the
area or length, such as sewer manholes, bank locations, arc's shape. This structure is used to trace linear sys-
accident locations, or features that are too small at a tems and to form the boundary of polygon features. This
given scale to be represented by their dimensions. Points means that there should be no break in the continuity
are stored as single X,Y coordinate pairs. In a GIS, of entities drawn in AutoCAD to represent features in
descriptive data are stored in a database, then related to ARC/INFO. If a text entity is used to indicate the
the spatial database that holds the coordinates. As shown diameter of a water line, it should not break the conti-
in Figure 2, the spatial database stores the coordinates nuity of the water line and should be placed above or

□ LAB (Internal
WELL* X-COORD
File)
Y-COORD
1 150.75 209.45
2 254.12 400.2:-
PAT
AREA PERIMETER WELLU WELL-ID
0.00 0.00 1 1
0.00 0.00 2 2

Figure 2. ARC/INFO point feature.

below the line. The AutoCAD user must, in this situa- ARC/INFO CLEAN command can be used to repair
tion, remember that the final destination of these overlapping and unconnected areas, but it is preferable
mapped data is not a paper plan, used for visual pur- to have the data created appropriately at the time they
poses, but a digital model to be used for analysis. Other are digitized. Polygon features will not be directly cre-
tools in ARC/INFO can be used to manipulate the lo- ated at the conversion level but will be assembled from
cation of descriptive text. The arc attribute table (A AT) the geometry that defines the arc features after using
and node attribute table (NAT) are used to store the CLEAN.
attributes (Figure 3).
Annotation features
Polygon features Annotation features are used to store descriptive text
Polygons are used to represent area features, such that may or may not be connected to spatial features,
as states, counties, lakes, and land-use zones. Polygons such as points, arcs, and polygons, in the coverage.
enclose areas that meet a user-specified set of common Annotation may be derived from the database values
characteristics for the phenomena being represented. of a point, line, or polygon feature, or it can be
In the ARC/INFO model, a series of arc features is used standalone. Annotation can be captured from AutoCAD
to create a closed area that defines the polygon feature. and stored in the coverage for later use, mostly for cre-
A polygon-arc- list (PAL) file defines the relationship. ation of cartographic map output.
Figure 4 illustrates this relationship graphically. The
attributes are stored in the polygon attribute table (PAT).
MODELING ARC/INFO FEATURES WITH
An additional characteristic of a polygon feature is that AUTOCAD ENTITIES
it has a special point that lies within its border called
the label point. A label point is used by ARC/INFO to This section focuses on how to represent informa-
identify the polygon, because the polygon is actually tion in an AutoCAD drawing with AutoCAD entities,
not the arcs that make up its boundary but a set of rela- with the purpose of converting them into ARC/INFO
tionships between those arcs. Any AutoCAD entity that features.
can be used to represent a point feature can be used to
model the label point of a polygon. Polygons can also Point features
model holes or voids in a region. When creating data to Discrete coordinate locations can be represented in
be converted into ARC/INFO polygons, CAD users the drawing in a number of ways, all of which can be
should snap end points of lines together and not create converted into ARC/INFO point features. The
regions where the areas of polygons would overlap. The AutoCAD point entity is a location defined in the draw-

ARC (Internal File)

PIPE» Coordinates
1 «■coordinate scries>
2 <coordmatc scncs>

1 2

AAT ▼
FNODEit TNODEU LPOLY» RPOLYit LENGTH PIPE« PIPE-ID
1 2 0 0 10.25 ll^lll^^pjjl
J { 1 L
A
Ml

1 NAT
RECORD ARCH PIPE» PIPE-ID
1 1 1 0
r 2 1 2 0

Figure 3. ARC/INFO arc/node features.

PAT
AREA PERIMETER GR1DH GR1DID
12.25 5.75 '' 1 • .-
11.75 4.75 2 •iu
1
I

4 1 2
3
i 1

2
j

Figure 4. ARC/INFO polygon features.

ing that can have several shapes. The AutoCAD shape Arc features
entity has its definition stored in a shape font definition AutoCAD line objects are simple two-point objects
file. Either of these can be converted into point fea- that delineate an edge of a 2-D or 3-D entity. These
tures. The AutoCAD block entity can be used to cap- objects translate directly into ARC/INFO arc features.
ture a multitude of data types. A block is a compound The problem from a GIS perspective is that any break
object, defined from a set of other AutoCAD entities. in the line results in a break in the connectivity of the
For example, a fire hydrant symbol could be created feature. Lines that are broken in two, for example, to
from a set of lines, arcs, and polylines, drawn in vari- place a piece of text, can result in difficulty in GIS model
ous colors and on various layers, to look like a fire creation. Several line entities can be strung together to
hydrant. The block is then defined and saved as a tem- form linear boundaries, but they should be snapped so
plate. This block can be placed multiple times in the the end points coincide. A more appropriate AutoCAD
drawing. Each individual instance of the block is called object to use would be the polyline or LWpolyline (light-
an insert. Each block insert can be captured as a point, weight polyline) object. These are multivertex linear
based on the location where it was inserted into the objects that can be used to symbolize a road centerline,
drawing. There are options to create ARC/INFO arc river edge, or any other 2-D object. LWpolylines are
features from the individual geometric parts of the often used when there is no need for 3-D elevations on
block, but these must be valid object types. In addition the vertices, since they take up much less storage in the
to the symbol, a block can contain a set of attributes, AutoCAD database. Each segment of a polyline can
which are items of descriptive text that can accompany contain a bulge factor, making its segment a geometric
the symbol. The block definition contains a set of arc. Again, these entities should be continuous if they
attribute definitions called tags, and each instance of are being prepared as layers to be converted into ARC/
the block (insert) contains the tag attributes. Our hypo- INFO coverage arc features.
thetical hydrant block could have two attributes asso- AutoCAD geometric arcs and circles can be con-
ciated with it: the hydrant ID number and the date of verted to ARC/INFO arc features and will be tessel-
installation. These can be captured as text annotation, lated into segments approximating the curved segment,
but they can also be stored as a point feature. with one segment per degree of arc. The primary entity
used in AutoCAD to digitize linear features is the cates an edge is not necessary, because of the nature of
polyline. An AutoCAD polyline is a multivertex, the coverage model and the CLEAN process.
multisegment, and two-dimensional entity. Three-
dimensional polylines can be created in AutoCAD, but Annotation features
those with vertices at varying Z coordinates should be Text objects are used to indicate additional attributes,
avoided, as the conversion process will ignore them. If such as pipe conditions or installation dates, or simple
the polyline is at a consistent elevation, it can be cap- labels on objects, such as a river name. This text, how-
tured for future use, as we will see. As noted, the light- ever, has no connection to the object, rather it simply
weight polyline, which is a simple, noncurved, 2-D provides a visual aid on the drawing canvas. The text
version of a polyline, may be used. While AutoCAD object represents data that can be captured from the
users often prefer these entities because of their low drawing as ARC/INFO annotation. Each piece of text
overhead, it does not matter for the conversion process, can be captured, along with its size, value, and rotation
and they are treated as a regular polyline. Any further angle, as annotation or as a point feature located at the
reference to an AutoCAD polyline will imply a polyline insertion point of the text. No information concerning
or lightweight polyline object. Note that ARC/INFO the font or AutoCAD text style is needed. While it is
will create nodes at the end points of the line, polyline, useful for the data provider to deliver necessary text
or arc entities when they are converted to ARC/INFO fonts to the ARC/INFO user, it is not crucial to the con-
arc features. Figure 5 illustrates ARC/INFO arc fea- version process because ARC/INFO uses its own set of
tures and corresponding AutoCAD entities. text symbols.
Attributes, as noted in the section on point features
Polygon features above, are textual objects that are part of a compound
As noted previously, an ARC/INFO polygon feature block insert. This text, in addition to being captured as
is created from arc features via the CLEAN command. point data and linked back to the symbol, can be cap-
This being said, information that is intended for con- tured as annotation and treated as such in the GIS data-
version into ARC/INFO arc features, then CLEANed base. These data will follow the same rules and proce-
into polygon features, should be carefully digitized to dures as text.
avoid error. Polylines could be digitized either as closed
(an option when creating the polyline), or open, with
AUTOCAD SYMBOLOGY AND DATA
the start and end points identical. If these methods are
ORGANIZATION
used, closed and snapped polylines will be easily con-
verted into ARC/INFO polygon features. Digitizing AutoCAD organizes its data, stored in file-based
polygons that overlap will result in the creation of mul- drawings, into a series of overlays called layers. In
tiple polygons, as this is not allowed in the polygon addition to layers, the user can utilize methods of sym-
model. This may also lead to undesirable results. If the bolization such as block symbols, color, line type, and
line work is digitized and snapped correctly, CLEAN line width to visually describe the drawing entities.
will create polygons and drop any redundant geometry. Attribute information can be carried along in the form
This means that a closed or open polyline that dupli- of AutoCAD block attributes as well.

AutoCAD Entity ARC/INFO Arc/Node Feature

Line

Polyline

Arc

Figure 5. Representing ARC/INFO arc features with AutoCAD

entities.
Layers Line types
A layer is a free-form storage entity capable of hold- LineType libraries are used in AutoCAD to indicate
ing data in various symbolic patterns and containing varying attributes. For example, a dashed line might be
data of various object types. Although there is no used to indicate an intermittent stream. This method of
requirement to do so, users often organize their layers showing breaks in a linear feature is acceptable for trans-
into different types of information. This organization lation; however, physically "breaking" the line to place
is commonly grouped by some scheme meant to lend text or another symbol there is not acceptable, because
structure to the drawing. For example, a drawing could the continuous nature of the linear feature must be pre-
be broken up into CAD layers called parcels, streams, served.
streets, and hydrants. The parcels layer could contain
the polylines that make up the boundary of the parcels, Line width
as well as the text that describes the parcels. The streams In reference to the example in the Layers section
layer might contain the lines delineating the streams, above, water lines could be drawn using specific line
as well as the stream names. The hydrant layer could widths to represent the pipe diameter: a line with a width
contain AutoCAD block symbols that have a hydrant of 4 could mean a 4-in.-diameter pipe. This methodol-
symbol, as well as some block attributes describing the ogy can break down rather quickly when there is a large
hydrant. Layers can be named using alphanumeric amount of data or a diverse number of diameter values,
names. An effective layering scheme is essential for such as 42 values requiring 42 different line widths.
the conversion process. When possible, all text objects
should be on layers independent of the entities they
PROBLEMS TO AVOID
describe. For example, street centerline entities could
be placed on a layer called GIS_STREET_ LINES, and There are certain entities that should never be used
text labeling for these streets would be stored on a layer for representing CAD data to be converted using ARC/
called GIS_ STREET_TEXT. Using separate layers for INFO. They can be used, but they need to be isolated
data that will be stored in different feature classes in on non-GIS layers.
the coverage is very helpful in the conversion process.
All non-GIS data should be isolated on layers that can Using 3-D data
be easily identified and excluded from the conversion Three-dimensional data can be used on GIS layers,
process. All GIS layers should contain only one feature but there are some limitations. Polylines, or any other
class, such as POINT, LINE, or TEXT, again to facili- object that has multiple parts on different elevations,
tate conversion. will be reduced to the elevation of the first entity. Con-
tour lines and other entities that are at a single eleva-
Colors tion (Z coordinate) can be converted properly.
Proper use of color can convey much information
about the data in a drawing. Colors can be assigned on Model space and paper space
a layer-by-layer basis (BYLAYER), meaning that the Paper space is an environment in the AutoCAD
layer has a default color and all objects drawn on it are drawing in which multiple viewports can be created to
ofthat color, and they can be assigned on an object-by- contain actual drawing data that has been rotated,
object basis (BYCOLOR). Colors can be used to fur- clipped, and annotated for use in plotting to hard copy.
ther refine the definition of objects on a layer. A layer Paper space is, by definition, in the coordinate space of
called WATER_LINES could contain the water pipe the plotted output and can have no connection to the
information on a site plan. The pipe material could then geographic coordinate system. While these data are
be symbolized by colors on this layer; for example, red useful in CAD, paper space objects and viewports are
lines could represent PVC, blue lines cast iron, and invalid for use in ARC/INFO and cannot be converted.
green lines ductile iron. This provides a way for the Therefore, model space should always be used.
AutoCAD user to carry pseudo-attributes on each
object without having to design object data tables Details and title blocks
with another application (such as AutoCAD Map) or Any details, insets, and title block information per-
writing a custom application. Often text objects are tinent to the drafting of the drawing should be isolated
used to indicate additional attributes, such as pipe onto non-GIS layers.
conditions or installation dates or both. This text,
however, has no connection to the water pipe object, Groups
rather it simply provides a visual aid on the drawing An AutoCAD group is a collection of heterogeneous
objects—such as a street line, its name text, and two
sign symbols—organized into one object. This is simi- definitions and attributes are on layer 0, this can make
lar in structure to a block, but it cannot be converted the conversion process quite difficult.
into GIS data and should be avoided.
GEOREFERENCING AND COORDINATE
Multilines and other entities
SYSTEMS
A multiline is a special type of line that can be de-
fined as sets and patterns of parallel lines treated as a Several additional points of interest should be noted
single line. These lines cannot be converted using the as they apply to the conversion of CAD data. Most no-
DXFARC conversion command in ARC/INFO. Rays tably, GIS data need to be associated with a specific
and Xlines are construction objects in CAD and should map projection and datum. For this reason, the CAD
never be used to symbolize GIS information. data should be digitized in a coordinate system that is
agreed to by all parties involved and in an agreed-upon
Hatching set of units (meters, feet, etc.). If the drawing data are
An AutoCAD hatch object is a specially defined not referenced directly, then there should be at least
pattern used to fill in an enclosed area. The hatch is four control points on the drawing at which the geo-
created as an anonymous (unnamed) block in the data- graphic coordinates are known.
base placed at coordinate 0,0,0. Hatch patterns cannot
be converted and should not be used to convey any in-
METHODOLOGY
formation about an enclosed area.
Adoption of a standard and agreed-upon method to
External references create GIS data for use in ARC/INFO will make the
An AutoCAD external reference (XREF) is a refer- data provider's job, and the GIS professional's job,
ence to another AutoCAD drawing, basically placing much easier and more efficient. In this section, we dis-
its contents into another drawing as a block. XREF cuss several concepts that can be very useful.
objects cannot be interpreted by ARC/INFO and should
not be used. Layering standards and conventions
The adoption of a consistent and agreed-upon layer-
Dimensions and leaders ing standard is critical to the success of the conversion.
A dimension (DIM) is a complex object consisting In this way both the data provider and the GIS user
of text, lines, and other symbols used to indicate sizes, know what to expect in the drawing without having to
distances, and other quantities. DIMs cannot be con- be experts in both systems. One of the most effective
verted and should not be used. Simple text objects and simplest concepts is to isolate GIS and non-GIS
should be used instead. A leader is an entity that is used data into their own named sets of layers. For example,
to draw an arrow to point to an object. It should be all GIS data could be stored on layers beginning with
treated as a dimension and similarly avoided. the prefix GIS_. Data for street centerlines could be
stored on a layer called GIS_ STREETJLINES. All lay-
Blocks as grouped graphics ers that do not start with the GIS_ prefix, although still
Blocks are very useful for symbology and locating useful to the CAD drafter, could be ignored by the ARC/
point features, but a block entity should not be used INFO user performing the conversion. Another useful
when it is created as a large-scale collection of graph- standard is to place all feature classes (point, arc, poly-
ics, say, from another drawing. If the CAD designer gon, and annotation) onto separate layers. The layer
inserts a large portion of another drawing into the GIS_STREET_LINES implies that the layer con-
existing one, he can insert it with the explode option, tains only line (arc) data for the street centerlines.
which will break up the graphic elements individually. Text for the street names could be stored on
This is always the necessary procedure. If blocks are GIS_STREET_TEXT. Again, this makes it easier to
used as symbols, the BLOCKS subcommand option of convert the data. Text especially should be placed on
the DXFARC command can be used. an individual layer. It is even useful to place blocks
and attributes on individual layers. If there is a layer
Layer 0 for each attribute tag in a block, the GIS user can easily
Layer 0 (zero) is a special layer in an AutoCAD extract the pieces needed to complete the conversion.
drawing, and it is best not used to draw any objects to
be converted via DXFARC. Blocks should be defined Color and line type schemes
on specific layers, as should their attributes. If all block As mentioned earlier, color can be used to catego-
rize data effectively within a layer. Water lines could this section borrows from that help document but does
be drawn in specific colors to indicate material and with not cover all options.
varying linewidths to indicate pipe size. A line on the There are several components to the use of this com-
layer GIS_WATER_LINES drawn in blue and with a mand, but the most important are the subcommand
line width of 3 might indicate a stainless steel pipe with options and the INFO tables that can be used to capture
a diameter of 36 in. These color categorizations and the AutoCAD properties of the data. The following
line widths would need to be agreed upon beforehand. subcommands can be used to process specific parts of
After that, it is very easy for the ARC/INFO user to the .DXF file:
capture the information.
ALL Converts all entities except BLOCKS.
Using text or block inserts as data tags This option is the default if no option is
Text can be used to create ARC/INFO annotation given. This is the same as specifying
features to help describe features. In addition, ARC/ ARCS, POINTS, INSERTS, TEXT-
INFO point features could be created, then the XCODE POINT, TEXTANNO, ATPOINT, and
file used to get the text value. These values can be used ATANNO for a single layer.
to "tag" the feature. For example, a set of lines indicat- ARCS Converts entities to create coverage arcs.
ing a parcel's boundary could have the parcel ID num- DXF entity types that can be converted
ber placed inside the parcel. The text could be captured to coverage arcs include line, 3Dline,
as a point feature, the text value related via the XCODE trace, solid, 3Dface, circle, arc, polyline,
file, and then a point-in-polygon overlay operation in and LWpolyline.
ARC/INFO could be used to match them together. The POINTS Converts point entities (point, shape)
same technique could be employed with linear features from the layer.
by using the ARC/INFO NEAR command to find the TEXTPOINT Converts text entities (text) from the
closest line feature to a point feature. The same can be layer into point features.
said for block inserts, where the XCODE file contains TEXTANNO Converts text entities (text) as annota-
the block attributes, which contain valuable informa- tion in subclass named DXF. Each layer
tion about the feature. will create a unique annotation level
(sequential, in order of appearance).
Determine the sequential order by
CONVERTING THE DATA: DXFOUT
reviewing the output of DXFINFO.
AND DXFARC
ATPOINT Converts attribute and ATTDEF from
In AutoCAD, the command to export a .DXF file the ENTITIES section of the layer as
is DXFOUT. The menu selection Save As... can point features.
also be used to save the drawing as a .DXF file. ATANNO Converts attribute and ATTDEF from
ARC/INFO can read .DXF files from AutoCAD the ENTITIES section as an annotation
releases 12, 13, and 14 in either ASCII or binary in a subclass named DXF. Each layer
format. The ASCII format creates the largest files, creates a unique annotation level
but they are easier to examine for problems if the user (sequential, in order of appearance).
does not have the AutoCAD software. DXFOUT can Determine the sequential order by
be used to output specifically selected objects or the reviewing the output of DXFINFO.
entire drawing. If desired, the AutoCAD user could INSERT Converts inserts as point features.
export specific layers using the object filtering capa- BLOCKS Performs the equivalent of exploding
bilities. This could help keep the size of the .DXF blocks for all points, lines, or multipoint
files reasonable. Either way, ARC/INFO can integrate lines. Text entities contained within
the layers from the entire file or from subsets of the blocks will be converted if either
file. TEXTANNO or TEXTPOINT is used.
The DXFARC command in ARC/INFO is the pri- Attributes will be converted if either
mary tool via which AutoCAD data, saved as a draw- ATANNO or ATPOINT is used. Inserts
ing interchange format (.DXF) file, are converted into will not be converted as point features.
ARC/INFO coverages. DXFARC can selectively pro-
cess layers from the .DXF file. For a complete descrip- When converting data into ARC/INFO arcs, the
tion of the use of the DXFARC command, refer to the properties of the linear features are stored in an INFO
ARC/INFO documentation or on-line help. The rest of table with the extension .ACODE. The properties of
data converted into point features are stored in an INFO DXF-IID item of all the attribute
table with the extension .XCODE. entities associated with that IN-
When run through DXFARC, a coverage called SERT.
CADDATA would produce an INFO table called
CADDATA.ACODE containing the following items: ARC/INFO users can link attribute information from
the ATTRIB point features to the point features from
CADDATA-ID ID of the coverage feature in its the insert entities using the ARC/INFO RELATE com-
attribute table. mand. See the ARC/INFO documentation for more
DXF-LAYER Layer to which the entity belongs. information.
DXF-COLOR Color of the entity.
DXF-THICKNESS Thickness of the entity. SUMMARY AND PROCESS STEP EXAMPLE
DXF-TYPE Line type (continuous, dashed,
etc.) of the entity. To summarize, Table 1 lists the AutoCAD data types
DXF-ELEVATION A single elevation value for the to use in a drawing and the resulting data types after
entire entity: its Z coordinate. conversion to an ARC/INFO coverage.
The following example is based on an AutoCAD
The CADDATA coverage could also produce an drawing that contains information about the water dis-
INFO table called CADDATA.XCODE containing the tribution system on a site (Figure 6). The water lines
following items for the points: are stored on an AutoCAD layer called GIS_WATER.
The AutoCAD user digitizes these lines using the
DXF-LAYER Same as for ACODE file. AutoCAD POLYLINE command. The AutoCAD
DXF-COLOR Same as for ACODE file. DXFOUT command is used to create the WATER.DXF
DXF-ELEVATION Same as for ACODE file. file. Using DXFARC, the ARC/INFO user can now
DXF-ANGLE Rotation angle in degrees. extract the arc features and use BUILD. This creates
DXF-TYPE Line type for the point feature. the ARC/INFO arc and node features and their associ-
ated attribute tables. The water line information is stored
If a layer is converted by DXFARC with the in an AutoCAD block, with three attribute tags to store
TEXTPOINT option, the XCODE file contains these the pipe length, pipe identifier, and pipe type on an
additional items: AutoCAD layer called GISJWATERDATA. The
AutoCAD user inserts these blocks using the AutoCAD
DXF-ANGLE Angle of the text. INSERT command and fills in the data fields when
DXF-SIZE Size of the text. prompted. The .DXF file is once again exported using
DXF-TEXT Text value for the DXF-ATTRIB. DXFOUT.
If the entity is a point, shape, or Using DXFARC, the ARC/INFO user can now
insert, this field is blank. extract the point features from the layer and BUILD
the point and annotation feature classes. Figure 7
If a layer is converted using the ATPOINT option, details the command syntax used for the DXFARC com-
these additional items are added to the XCODE file: mand. The .XCODE file contains the actual attribute
values for the points created in the DXFARC process.
DXF-ATTRIB Holds the BLOCK name for IN- This file can be joined back to the point attribute table
SERT points, the shape name for (PAT) in ARC/INFO. Features with the same DXF-IID
SHAPE entities, and the tag or field all belong to the same block insert.
item name for ATTRIB and To find the nearest water line to the block insert point
ATTDEF entities. features, use the ARC/INFO NEAR command. Figure
DXF-TEXT Stores the item value for ATTRIB 8 details the command syntax used for the example.
and ATTDEF entities. Note in the figure that no polygon features are actually
DXF-ATTRIB Blank for text and point entities. created at the time of conversion, rather, they are cre-
DXF-IID Used to link attributes to the ated by subsequent use of the ARC/INFO CLEAN com-
corresponding INSERT entity. mand. As discussed above, as long as the geometry of
Each INSERT entity can have the arcs is created correctly, correct polygon topology
multiple attribute entities. IN- will follow.
SERT entities are converted to Figure 9 shows the converted data, and Figure 10
point features with a unique user summarizes the entire conversion process as a flow-
ID. This user ID is stored in a chart.

10
Table 1. AutoCAD data types and ARC/INFO coverage
equivalents.

Draw in AutoCAD: To represent in ARC/INFO:

Point
Insert (block) Point feature
Attribute
Shape

Line
Polyline Arc feature
Arc Polygon feature (after CLEAN)
Circle

Closed polyline Polygon feature (after CLEAN)

Closed lightweight polyline

Text attribute Annotation feature

%Au\wCMi • W„l!or dwn

HE'' §sH $m Jiwejl Fjpwi» fool* Qjw Cirnqpen M«*V äDS §w» tw "" äiüc"

ÜFäitfDÖ xi (DS*S^ j^P^^SSST" 3'JH

CTJMJ'JM.WTäJBainörcB ". ■ '". • iwum. rut

Figure 6. AutoCAD drawing containing water data.

11
Arc: dxfarc
Usage: DXFARC <in_dxf_file> <out_cover> { text_width}
{attrib_width}
Arc: DXFARC WATER.DXF WATER 32 32

Enter layer names and options (type END or $REST when done)

Enter the 1st layer and options : GIS_WATER ARCS

Enter the 2nd layer and options : END
Do you wish to use the above layers and options (Y/N)? Y

Processing D:\WORK\CRREL\COVERS\WATER.DXF ...

No labels, killing XCODE...
Externalling BND and TIC...

172 Arcs written.

0 Labels written.
0 Annotations written.
0 Annotation levels.
Arc: BUILD WATER LINES
Building lines...
Arc: RENODE WATER
288 unique nodes built for D:\WORK\CRREL\COVERS\WATER
Arc: DXFARC WATER.DXF WATERJTAGS 32 32

Enter layer names and options (type END or $REST when done)

Enter the 1st layer and options : GIS_WATER_DATA ATPOINT

ATANNO INSERT
Enter the 2nd layer and options : END
Do you wish to use the above layers and options (Y/N)? Y

Processing D:\WORK\CRREL\COVERS\WATER.DXF ...

No arcs, killing ACODE...
Externalling BND and TIC...

0 Arcs written.
688 Labels written.
516 Annotations written.
1 Annotation levels.
Arc: BUILD WATERJTAGS POINT
Building points...
Arc: BUILD WATERJTAGS ANNO.DXF
Building annotation...
Arc:
Figure 7. Using the ARC/INFO DXFARC command.

12
Arc: near
Usage: NEAR <in_cover> <near_cover> {LINE POINT I NODE}
{ search_radius}
{ out_cover) { NOLOCATION | LOCATION}
Arc: NEAR WATERJTAGS WATER LINE 1.0 WATERJTAGS2
Identifying features in WATER near those in WATERJTAGS.

Figure 8. Using the ARC/INFO NEAR command.

/^ARCPLOT HU
Pan/Zoom

X:5.85630 Y:l.77165 dx:4.06004 dy:-0.99656 Diet 4.18055

Figure 9. ARCPLOT canvas showing converted data.

13
Digitize data in AutoCAD
on appropriate layers

I
DXFOUT entire drawing
or specific layers

I
DXFARC desired layers
into appropriate features

I
BUILD arc, point,
annotation coverage,
CLEAN polygons

JOIN XCODE or ACODE

file into PAT or AAT

Use NEAR for arcs or

IDENTITY for polygons

Figure 10. Flowchart showing conversion from AutoCAD to ARC/INFO.

14
APPENDIX A: ARCVIEW GIS 3.1

ArcView stores data in a format called a shapefile (.SHP). The shapefiles are defined, for
our purposes, as point, line, or polygon shapes. There is no text or annotation data type in a
shapefile. Geometry is stored in a .SHP file, a spatial index is built in a .SHX file, and
database attributes associated with the shapes are stored in a dBase file (.DBF). AutoCAD
data can be read directly using the ArcView CAD Reader extension. Conversion is facili-
tated via the Convert To Shapefile option in Arc View. Custom conversion tools can be
written in ArcView with the Avenue programming language. See the ArcView help docu-
ment for object mapping.
ArcView has two additional features that make it useful for the conversion process. First,
any AutoCAD polyline that is closed, or any open polyline whose beginning and ending
points are identical, is interpreted as a polygon shape. Second, attributes of blocks are auto-
matically associated with the block insertion point, which defines a point shape, by
denormalizing the data in the associated table.
A future version of this document will provide more information on using Arc View GIS
and CAD data.

15
APPENDIX B: ARC/INFO 8.0

Arclnfo 8.0 stores data in a GeoDatabase. This GeoDatabase can exist in a standalone
format using a Microsoft Access file (.MDB), or it may be stored in a relational database
management system (RDBMS) such as Oracle or SQL Server to be used in a multiuser
environment. The GeoDatabase stores information in a similar fashion to an ARC/INFO
coverage, but all in one unit. Since the object models of AutoCAD and ARC/INFO are
visible via Visual Basic or any other Microsoft Windows COM-compliant development
environment, creation of custom translators would be very feasible in this powerful envi-
ronment. See the Arclnfo 8.0 help document for object mapping.
A future version of this document will provide additional information on using ARC/
INFO 8.0 and CAD data.

16
Form Approved
REPORT DOCUMENTATION PAGE OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the
data needed, and completing and reviewing this collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing
this burden to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302.
Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid
OMB control number. PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS.
1. REPORT DATE (DD-MM-YY) 2. REPORT TYPE 3. DATES COVERED (From - To)
March 2000 Technical Report
4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER

5b. GRANT NUMBER

Integrating CAD Data with Geographic Information Systems
Using AutoCAD and ARC/INFO Software
5c. PROGRAM ELEMENT NUMBER

B.AUTHOR(S) 5d. PROJECT NUMBER

Paul T. Cedfeldt and Mark A. Scott

5e. TASK NUMBER

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION REPORT

NUMBER
U.S. Army Engineer Research and Development Center
Cold Regions Research and Engineering Laboratory
72 Lyme Road ERDC/CRRELTR-00-1
Hanover, New Hampshire 03755-1290

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR / MONITOR'S ACRONYM(S)

U.S. Army Corp of Engineers Alaska District

FUDS Program 11. SPONSOR / MONITOR'S REPORT
P.O. Box 898 NUMBER(S)

Anchorage, AK 99506-0898
12. DISTRIBUTION / AVAILABILITY STATEMENT

Approved for public release; distribution is unlimited.

Available from NTIS, Springfield, Virginia 22161.

13. SUPPLEMENTARY NOTES

14. ABSTRACT

Software for computer-aided design (CAD) and geographic information systems (GIS) are often used in conjunction with one another. This
document proposes a methodology for effectively integrating data created using Autodesk's AutoCAD R14, the most widely used CAD
software package, with Environmental System Research Institute's (ESRI's) ARC/INFO 7.2, the most widely used professional GIS soft-
ware package. Abrief discussion of software data models is provided, followed by an enumeration of certain entities that should never be
used to represent AutoCAD data that is going to be converted using ARC/INFO. The document concludes with an example implementation
of the proposed integration methodology.

15. SUBJECT TERMS

ARC/INFO Computer-aided design (CAD) Spatial data translation
AutoCAD Geographic information
16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF 18. NUMBER 19a. NAME OF RESPONSIBLE PERSON
OF ABSTRACT OF PAGES

a. REPORT b. ABSTRACT c. THIS PAGE 19b. TELEPHONE NUMBER (include area code)

u u U u 24

Standard Form 298 (Rev. 8-98)

Prescribed by ANSI Std. 239.18