If you use a PRJ file for the spatial reference parameter, be sure to set your x,y,z domain. If this is not the case, be sure to expand the domain in your first model to be large enough so all will fit. Import from CAD calculates the domain for the entire DGN file from the first model.
If a DGN file has multiple models, be sure the first model has the largest domain.
Only MicroStation version 8 supports the use of multiple models in a single design file. Be sure the model with the greatest extent is used as the default model in a DGN drawing. This means that if there are entities outside the extents of the default CAD field extents, they could be rejected. When generating a default spatial reference for the staging geodatabase, you should always use the extent default model of the CAD file as the foundation. If multiple CAD files are used as inputs the spatial reference will be taken from the first CAD file which has a projection file, in the input list. If a projection file exists for the input CAD file it will automatically populate the spatial reference parameter with the projections information. These tables contain the tabular attributes of the layer properties, text properties, entity properties, block or cell attributes, and extended entity data or MSLink values. Normalized tables are generated in the specified output workspace.
This function is generally used in the process of translating CAD data to an existing geodatabase using a series of other geoprocessing functions in a script or ModelBuilder model and as such, the resulting data from this function is typically temporary. The DocName field contains portions of the DocPath field, and the TextValue field contains portions of the TextMemo field. They have a shorter field length, so they can be moved to an ArcSDE geodatabase. Portions of the information in these fields are duplicated in other fields. For information about limitations of your ArcSDE geodatabases, see your system administrator. The DocPath field in the CadDoc feature class and the TextMemo field in the TxtProp table each have a memo field that is too long to fit in an ArcSDE geodatabase. If you are going to copy the DocPath field in the CadDoc feature class or the TextMemo field in the TxtProp table from the staging geodatabase to a ArcSDE geodatabase, there are some limitations you need to be aware of. Import from CAD cannot output to an ArcSDE feature class it will create a new personal geodatabase. Likewise, the feature classes generated from the CAD data can be accessed using the Select Data tool on the output feature dataset.ĬAD text and attribute entities are converted to point features. The CAD property tables can be accessed from the output workspace in a model or script using the Select Data tool. The Import from CAD tool does not support the creation of annotation feature classes. If a table in the output feature dataset or workspace has the same name as one created by ImportCAD, the table will be deleted and re-created. These normalized tables can be linked together using key fields, such as the EntID that is also found in the feature classes created by the Import CAD tool. The Input files parameter will allow the addition of different kinds of CAD data (DGN, DWG, DXF) in one operation.ĬAD property tables are created in the output workspace. Its flattened structure allows it to be put back together however you want. The output is data from the CAD inputs and no relationships exist. Postprocessing will be required if you need to perform any joins of the data or relationships.
This tool creates a new geodatabase and will not append to an existing one. These feature classes contain the geometry for the lines, areas, points, and document extent, and optionally, point feature classes can be generated for each unique block or cell name. This tool will output a File based Geodatabase (.GDB) by default, but will also output an Personal Geodatabase (.MDB) if the user defines the proper extension.Ī fixed set of feature classes will be generated in the specified output feature dataset. This functionality has been replaced by CAD To Geodatabase. To learn more about how this tool works click here.