The document provides a timeline and history of releases for both Autodesk's AutoCAD and ESRI's ArcGIS software. It discusses the transition from earlier CAD-based systems to newer GIS-based systems. It also provides tips and considerations for converting CAD data, such as thorough documentation and inspection of layers, into a geodatabase format within ArcGIS.

1. 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 released Arc/Info R2 released – 17 systems in use Arc/Info R3 released Arc/Info R4 released Arc/Info R5 released Arc/Info R6 released – 7000+ seats in use ArcView is released – “affordable” desktop GIS Arc/Info R7 & ArcView 2 released 100,000 user seats – ArcView Arcnfo price $10K Arc/Info 8 & ArcView 3.2 released 500,000+ user seats ArcGIS 8.1 released ArcGIS desktop 9.1 released ArcGIS desktop 9.3 ArcGIS desktop 10 AutoCAD v1.0 AutoCAD v2.0 AutoCAD v2.5 AutoCAD R10 AutoCAD R11 AutoCAD R12 AutoCAD Map released price $4,495 AutoCAD R14 AutoCAD R2000 AutoCAD R2002 COGO tools & annotation AutoCAD R2006 AutoCAD R2008 AutoCAD R2011 ESRI GIS Software Release Timeline Autodesk Software Release Timeline Sold 40,000 packages by 1985 ArcView 10 starting at $1,500 2012 Civil 3D package starting at $3,495 PC Arc/Info released - $4,500 AutoCAD R13 2010 2007 2005 2001 1999 1997 1996 1994 1992 1990 1988 1986 1984 1982 2010 2007 2005 2001 1999 1997 1994 1993 1991 1989 1987 1985 1983 1981

3. CAD to ESRI Geodatabase General process, considerations, tips & tricks

7. CAD lines for highway shields and other symbology are unneeded in the geodatabase Example 1:

8. Example 2: Do not convert these lines. Use geodatabase annotation properties

9. Example 3: Do not convert these lines. Use geodatabase point feature

10. CAD lines that will form polygon feature classes need to be inspected closely for gaps Example 1: PLSS lines  Polygons

11. Mtext is a problem

12. Mtext does not convert to GDB

13. Exploded Mtext…. Converts to single GDB annotations

14. 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.

16. Buffer + Spatial Join

17. Attribute Transfer Mapping

18. 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.

19. Join for Count catches errors

20. Spatial join for attributes produces some erroneous attributes

21. Spatial join for attributes: distance > 0 indicates either non-parcel polygons or errors.

22. Watch out for crazy stuff!! Original CAD Converted using Import from CAD tool Converted using Select  Export

24. The End