1. Indiana University Migrating from AutoCAD to a Geodatabase Theresa Thompson ththomp@indiana.edu

2. Total enrollment 2004-05 (7 campuses): 92,070 students 15,831 faculty and staff 714 buildings (7 campuses ) 26,525,251 gross sq. feet of building space 2,963 acres

3. For the Bloomington campus 13 Utility Systems Chilled Water, Condensate, Communications, Electric, Exterior Lighting, Irrigation, Natural Gas, Sewer, Steam, Storm Water, Tunnel, Telephone, Water Basemap

5. Indiana University Utility Information Group

8. AutoCAD Map linked to Access via object data

9. GIS database

10. Database forms

11. Why move from AutoCAD Map to a SDE Geodatabase environment?  Ease-of-Use for Editors  Centralized Database/Graphics Environment  Enterprise level data sharing  Easier to bring CAD into ArcGIS than GIS into CAD without conversion

12. IU GIS system Windows based ArcGIS 9.1 – editors Windows ArcReader 9.1 - viewers Unix ArcSDE/Oracle for geodatabase Unix ArcIMS for web mapping Testing ArcGIS Server Geodatabase – IU Bloomington Data Layers = over 58 basemap over 100 utilities

14. Data Preparation for moving from AutoCAD Map to a Geodatabase D atabase model in place create a geodatabase and set up boundary polygon for spatial reference data naming/object/relationship standards for features domain tables (lookup tables) Clean your CAD and Attribute data before you convert objects on correct layers / CAD Standards correct blocks / object linking Expect data problems: there is no “perfect conversion”

15. http://downloads.esri.com/support/ whitepapers/ao_/CAD_Translation_ in_Geoprocessing_1004_J9324.pdf Read this!

16. Approaches to converting CAD CAD with no data linking but with block attributes – use Direct Read CAD file export into geodatabase (via ArcCatalog / ArcToolbox) CAD linked to database/object data – use AutoCAD Map export to shapefiles or coverage, then load into SDE/Oracle CAD annotation – use ArcToolbox \ Conversion Tools \ To Geodatabase \ Import CAD Annotation CAD text or blocks linked to polygons – use ArcToolbox\ CAD Translation \ PolygonsfromCADLinesandPoints

17. Simple CAD with no data linking but with block attributes Use Direct Read CAD file export into geodatabase (via ArcCatalog) “The direct read functionality treats the CAD file as a database of spatial features” CAD files are rich in attribute data – don’t lose this during conversion

19. Filter out certain CAD blocks Rename field names

20. Lists all the block names in the dwg

21. “Text_” field = blockname Attribute fields in feature class have new field names

24. CAD linked to database/object data – use AutoCAD Map export to shapefiles or coverage, then load into SDE/Oracle There are currently no ESRI tools out there to bring in database linked attributes via object data or link templates in AutoCAD Map AutoCAD Map 2006 has direct read capability to SDE/Oracle

25. Narrow what you convert in AutoCAD Map by a query

27. Make sure your data source is connected and the link templates you need are active

28. For complex closed polylines you might need to convert to a coverage first, then geodatabase or shapefile

30. Select both drawing property attributes and link template attributes to migrate over.

32. Here is your chance to change the Output Field Names

33. AutoCAD dwg property attributes and linked database attributes are now part of the converted feature class.

36. Create a new personal geodatabase or new feature layers in SDE to import your shapefile data into

38. Here is another chance to change the field names or decide not to bring in some attribute fields your geodatabase

40. You can do similar functions several ways...this time you use the Export to Geodatabase command.

43. CAD annotation – use ArcToolbox \ Conversion Tools \ to Geodatabase \ Import CAD Annotation Finally! A great tool for converting AutoCAD Text into geodatabase annotation.

44. Preview AutoCAD text to make sure it isn’t mtext

45. You need to explode all mtext for conversion. Set up a selection filter for only mtext, then explode this.

46. Once you explode the mtext, save the dwg and preview again in ArcCatalog

47. Be sure to select the dwg file annotation class for conversion

48. You need to determine a reference scale. We use 1:5000 for our campus maps based on units of feet.

49. This is how the converted CAD annotation looks in the geodatabase annotation feature class

50. You will be able to edit geodatabase annotation easily in a ArcGIS edit session with Annotation edit tools

51. CAD text or blocks linked to polygons – use ArcToolbox\ CAD Translation \ PolygonsfromCADLinesandPoints There are several powerful geoprocessing tools/scripts in the CAD Translation toolbox.

52. Download this free ArcToolbox

55. Notice the parcel number is just text, not a block attribute.

56. We have filtered out just the parcel number layer to pull as an attribute for the parcel polygons

57. Parcel polygons now have the enclosed text from the CAD dwg as a parcel attribute

58. Approaches to exporting from GIS to CAD Set up a CAD template.dwg (with preinserted blocks, layers, linetypes) Create geodatabase fields for CAD mapping like LAYER, ROTATION, LINETYPE, CADTYPE, REFNAME For conversion to CAD – use ArcToolbox \ Conversion Tools \ Export to Geodatabase \ Export to CAD

59. Select all the Chilled Water feature classes to export into one CAD file

60. Exported from SDE – this CAD file now has mapped blocks and attributes, layers and linetypes automatically from the CAD template file (seed file)

61. For mapping geodatabase attributes back to CAD you need to make sure you have fields for CADtype = insert and the REFNAME = blockname

63. In an ArcGIS edit session – use the Field Calculator to populate the REFNAME with the correct CAD blockname

64. 2 new geodatabase fields you created to export to CAD

65. Create a AutoCAD template file – make it read-only

66. Point feature class in SDE is exported to new CAD file and block attributes automatically populated to block inserts. Note: open up newly created dwg in AutoCAD first, zoom extents and save before viewing in ArcCatalog.

67. Questions ??? ththomp@indiana.edu