Geoprocessing tool reference > Conversion toolbox > To CAD toolset > Tools
Create CAD XData (Conversion) (ArcInfo only) |
|
|
Release 9.2
Last modified April 2, 2008 |
Print all topics in : "Tools" |
Changed tool description to: Creates a field called 'XDList' in the attribute table.
Usage tips
-
All input feature classes and/or feature layers are valid inputs to this tool.
-
XData is only read by AutoCAD
-
The XDList field that is created by this function is read by the Export to CAD tool when exported to AutoCAD .
-
Extended Entity Data though, allows you to attach up to 16K of information to each and every entity in the drawing.
-
You can also keep the XData separate from other information because it uses a uniquely registered name
-
If you would like to learn more about how CAD data can be used as direct input to Geoprocessing tools, or a sample workflow involving the Create CAD XData tool.
-
If your function fails with "Output exceeds field length", then include less fields in your XData string. The XData field that is added has a maximum field length of 2049 characters.
-
The following environments affect this tool: extent, scratchWorkspace, and workspace.
Command line syntax
An overview of the Command Line window
CreateCADXData_conversion <in_table> <fields;fields...> <RegApp> <ADE | Traditional XData>
| Parameter | Explanation | Data Type |
| <in_table> |
This table contains the fields used to generate an XML string of values recognized by the Export to CAD tool. This enables XData to be created on output objects, based on values of fields from the Input Table. |
Table View |
| <fields;fields...> |
The selected field values for the encoded XData. The Add Field button, which is used only in ModelBuilder, allows you to add expected field(s) so that you can complete the dialog and continue to build your model. |
Field |
| <RegApp> |
The AutoCAD extended entity data registered application name. Required by only AutoCAD to identify the XData. This application name is an identifier of the newly created XData. |
String |
| <ADE | Traditional XData> |
Format of the AutoCAD XData.
|
String |
Command line example
CreateCADXData_conversion WaterPipes WaterPipe_xdata "diameter, length, material, reynolds_no, installed" "KYPIPE" NO_ADE
Scripting syntax
About getting started with writing geoprocessing scripts
CreateCADXData_conversion (in_table, fields, RegApp, Output_Type)
| Parameter | Explanation | Data Type |
| in_table (Required) |
This table contains the fields used to generate an XML string of values recognized by the Export to CAD tool. This enables XData to be created on output objects, based on values of fields from the Input Table. |
Table View |
| fields (Required) |
The selected field values for the encoded XData. The Add Field button, which is used only in ModelBuilder, allows you to add expected field(s) so that you can complete the dialog and continue to build your model. |
Field |
| RegApp (Required) |
The AutoCAD extended entity data registered application name. Required by only AutoCAD to identify the XData. This application name is an identifier of the newly created XData. |
String |
| Output_Type (Required) |
Format of the AutoCAD XData.
|
String |
Data types for geoprocessing tool parameters
Script example
# To create XData from a feature class and export it to a CAD file with the Extended Entity Data.
# Create the Geoprocessor object
import arcgisscripting
gp = arcgisscripting.create()
# Local variables...
Roads2 = "C:/Test_data/Personal GDB/OrangeCounty.mdb/Roads"
OrangeCounty_mdb = "C:/Test_data/Personal GDB/OrangeCounty.mdb"
Roads = "C:/Test_data/Personal GDB/OrangeCounty.mdb/Roads"
roads_dwg = "C:/Test_data/CAD/roads.dwg"
# Process: Select Data...
gp.SelectData_management(OrangeCounty_mdb, "Roads", )
# Process: Create CAD XData...
gp.CreateCADXData_conversion(Roads, "'MINOR2';'MAJOR3';'MINOR3';'MAJOR4';'MINOR4';'DESCRIPT';'Shape_Length'", "ArcGIS", "ADE", )
# Process: Export to CAD...
gp.ExportCAD_conversion("'C:/Test_data/Personal GDB/OrangeCounty.mdb/Roads'", "DWG-R2000", roads_dwg, "Use_Filenames_in_Tables", "Overwrite_Existing_Files", "")