Using the Import From CAD tool |
|
|
Release 9.2
Last modified August 15, 2007 |
Print all topics in : "Geoprocessing tools for CAD translation" |
The Import From CAD tool is generally for more sophisticated solutions when creating your own custom translations. This tool recasts native CAD files into feature classes and a series of tables. This is called a staging geodatabase, which is intended to be a staging area from which custom feature classes will be created. It is recommended that new custom feature classes be written to an alternative location and leave the staging area unmodified. This preserves the staging geodatabase to create new custom feature classes, since the data has not been modified.
The staging geodatabase is a flattened structure of the CAD file recast as a GIS geodatabase. With the flattened structure, you are given the flexibility to reconstruct your own custom feature classes. Each piece of geometry translated from a CAD file will have multiple attributes that can be associated with it. A single line could have the obvious entity table attributes and layer-by-layer information about the same piece of geometry in the CadLayer table. This illustrates how joining multiple tables to a single set of features is often needed. There are key-named fields that can be used to join the geometry to the attributes.
Fields such as EntID and ObjectID can be used for the joins and allow the geometry to get the attribute information needed to minimize the data loss during this semantic translation process, for example, by joining the Point feature class with the Txt Prop table to get the text value with the point locations. By joining the tables to the feature classes, you are constructing your own custom translations to create user-specified feature classes. The Import From CAD tool adds a level of complexity but allows more low-level control.
This process of joining feature classes may be more involved than what you require, so it is reasonable to use the CAD feature dataset. These CAD feature classes are similar to the staging geodatabase, except all the information and the geometry has been joined. Think of the CAD feature classes as an ESRI-enforced schema that joins features with attribute information.
| Tip |
|