cad to esri geodatabase conversion
TRANSCRIPT
Source: http://autodesk.blogs.com/between_the_lines/autocad-release-history.html
Source: http://www.gisuser.com/content/view/11991/53/
Source: http://www.esri.com/news/arcnews/winter0001articles/anewworld.html
Source: http://store.autodesk.com/store/adsk/en_US/buy/productID.226491200
Source: http://store.esri.com/esri/search.cfm?SID=2&
Source: http://map3d.wordpress.com/2010/08/09/a-history-class/
Arc
/Info
R1
rele
ased
1981 1983 1985 1987 1989 1991 1993 1994 1997 1999 2001 2005 2007 2010
1982 1984 1986 1988 1990 1992 1994 1996 1997 1999 2001 2005 2007 2010
Arc
/Info
R2
rele
ased
–
17 s
yste
ms
in u
se
Arc
/Info
R3
rele
ased
Arc
/Info
R4
rele
ased
Arc
/Info
R5
rele
ased
Arc
/Info
R6
rele
ased
–
7000
+ s
eats
in u
se
Arc
Vie
w is
rel
ease
d –
“a
ffo
rdab
le”
des
kto
p G
IS
Arc
/Info
R7
& A
rcV
iew
2
rele
ased
100,
000
use
r se
ats
– A
rcV
iew
Arc
\Info
pri
ce $
10K
Arc
/Info
8 &
Arc
Vie
w 3
.2
rele
ased
500,
000+
use
r se
ats
Arc
GIS
8.1
rel
ease
d
Arc
GIS
des
kto
p 9
.1
rele
ased
Arc
GIS
des
kto
p 9
.3
Arc
GIS
des
kto
p 1
0
Au
toC
AD
v1.
0
Au
toC
AD
v2.
0
Au
toC
AD
v2.
5
Au
toC
AD
R10
Au
toC
AD
R11
Au
toC
AD
R12
Au
toC
AD
Map
rel
ease
d
pri
ce $
4,49
5
Au
toC
AD
R14
Au
toC
AD
R20
00
Au
toC
AD
R20
02 C
OG
O
too
ls &
an
no
tati
on
Au
toC
AD
R20
06
Au
toC
AD
R20
08
Au
toC
AD
R20
11
ESRI GIS Software Release Timeline
Autodesk Software Release TimelineSo
ld 4
0,00
0 p
acka
ges
by
1985
Arc
Vie
w 1
0 st
arti
ng
at
$1,5
0020
12 C
ivil
3D p
acka
ge
star
tin
g a
t $3
,495
PC
Arc
/Info
rel
ease
d -
$4,
500
Au
toC
AD
R13
GIS MilestonesTransition from CAD-based map to GIS-based map
1992-93 Release of ArcView – Affordable desktop GIS - point and click vs. command line – ease of use
1999 Release of ArcView 3.2 – enhanced CADReader extension, Projection utility
2001 ArcGIS Desktop 8.1 – ArcEditor option, improved CAD rendering, annotation, on-the-fly coordinate and datum projection, three application user interface.
CAD to ESRI Geodatabase
General process, considerations, tips & tricks
Document CAD data
• Thorough documentation is critical– List layers along with descriptions
• Are CAD attributes such as color and line type important?
– Layer forms polygon boundary?– Layer is no longer needed in GIS
environment?– Etc…
•Combine CAD layers into single feature classes
•Use geodatabase subtypes
Tools Used
• Mostly standard ArcGIS tools– Select Level from CAD Export selected
features to feature class– Copy/Paste– Import CAD Annotation
• CAD file needs a .prj file for this to work
• Data Interoperability extension– Great for automating repeated conversions
CAD lines for highway shields and other symbology are unneeded in the geodatabase
Example 1:
Example 2: Do not convert these lines. Use geodatabase annotation properties
Example 3: Do not convert these lines. Use geodatabase point feature
CAD lines that will form polygon feature classes need to be inspected closely for gaps
Example 1: PLSS lines Polygons
Mtext is a problem
Mtext does not convert to GDB
Exploded Mtext….
Converts to single GDB annotations
Fix misalignment of stacked lines with the Integrate tool
Gap
Double section lines
Integrate tool with .5 foot cluster tolerance will make these lines coincident.
Attribution techniques
•Buffer + Spatial Join
•Attribute Transfer Mapping (last resort)
•Spatial Join – point in poly
•Join PIN to database for subdivision attributes
Buffer + Spatial Join
Attribute Transfer Mapping
2 Spatial join methods
1) Count field shows number of points within poly
2) Poly receives attributes of closest point. Distance = 0 indicates the point is within the poly boundary.
Join for Count catches errors
Spatial join for attributes produces some erroneous attributes
Spatial join for attributes:distance > 0 indicates either non-
parcel polygons or errors.
Watch out for crazy stuff!!
Original CAD
Converted usingImport from CAD tool
Converted usingSelect Export
More crazy stuff • Workaround for Export to CAD bug w/ ellipse features
• DGN DWG GDB
The End