Import cad file into arcview

Content feedback is currently offline for maintenance. Please try again in a few minutes. Is This Content Helpful? Back to top.

Procedure Before performing the following process, the projection for the CAD data must be defined. Rename the file geodabase if desired, but the. If possible create the new file geodatabase on the local hard drive. Browse to the CAD file on disk and select it as the input. The software automatically creates a feature dataset in the default geodatabase to contain the data, although the name can be changed if desired.

The name cannot contain spaces, although underscores can be used. Instructions are provided below for determining an appropriate reference scale for the data.

The features from the CAD file are imported to feature classes in the feature dataset. Alternative instructions for importing the CAD annotation to the geodatabase are provided below. These alternative steps preserve the font used to create the text, as well as the color and size of the original text entities from the CAD file. Alternative import method Create a new file geodatabase, then right click on the geodatabase, and create a new feature dataset, defining the projection to match the coordinate system in which the CAD data was created.

Importing annotation by this method creates another point feature class, with each point at the anchor point for the annotation string. The annotation string is preserved in the TextString field in the geodatabase feature class. Click OK. The feature types selected are imported to the feature dataset in the geodatabase.

To determine an appropriate reference scale for the annotation, open a new, empty map in ArcMap, and draw the CAD annotation. On the General tab, set the map and display units to the units in which the data was created, for example, feet, meters or other units.

Zoom in to the annotation until in the screen display of the annotation is rendered at a suitable size for viewing or printing. Once the reference scale is set for the new annotation feature class in the geodatabase, it cannot be changed. The reference scale should be set to a map scale which is typical for the data, either for plotting or on-screen display. Glen Pearson. I am trying to import location plans from ARCView 8.

I have tried importing as a bitmap and JPEG but the data is not transfered across at the scale required. The data needs to remain at to comply with Land Registry requirements.

Can anyone give me any advice on how to do the above. Message 2 of 7. Message 3 of 7. Message 4 of 7. Are you saying the data IS transferred, just not at the required scale? You would need to scale the images manually to get them to full-size, and then print the drawing at Message 5 of 7. The data is being transferred as a bitmap image and inserted as an OLE.

Postprocessing will be required if you need to perform any joins of the data or relationships. The output is data from the CAD inputs and no relationships exist. Its flattened structure allows it to be put back together however you want. CAD property tables are created in the output workspace. 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.

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. The Import from CAD tool does not support the creation of annotation feature classes.

The CAD property tables can be accessed from the output workspace in a model or script using the Select Data tool. Likewise, the feature classes generated from the CAD data can be accessed using the Select Data tool on the output feature dataset.

CAD text and attribute entities are converted to point features. 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. For information about limitations of your ArcSDE geodatabases, see your system administrator.

Portions of the information in these fields are duplicated in other fields. They have a shorter field length, so they can be moved to an ArcSDE geodatabase.