Bulk Copy

Use Bulk Copy to copy a Display Manager layer or a feature source. Bulk Copy uses the current definition of the layer (including any filters you applied, any joins you created, and any calculated properties). For feature sources, you can specify a subset based on specified schemas, feature classes, or properties.

To copy data from one feature source to another

In Map Explorer, click ToolsBulk Copy.


Connection Name

Select a Display Manager layer or connected feature source in the Connection Name list as feature source from which the data will be copied. Filtered layers display a filter icon in the list.

If you select a survey data store, you can select only a survey point group as the source. To copy multiple point groups, copy them one by one.


If the selected feature source supports versioning, select a version from the list to use for copying.

Select Items To Copy

Select the individual schemas, features classes, and properties to copy to the destination feature source.

Selecting any schema element automatically selects all its child elements (selecting a feature class also selects all its properties, for example). A square (instead of a check) in a check box means that only some of that element’s children are selected.

Calculated fields are appended after the native properties. If there are joined fields, they are grouped under a node representing the join. If there are multiple joins, they appear as they do in the Manage Layer Data dialog box.


Connection Name

Select a feature source in the top list as the destination feature source.


If the destination feature source supports versioning, select a version from the list as the version to use for copying.

Click On An Item To Select A Different Input Name

Click the arrow for each item whose counterpart you selected in the left-hand tree to map the source item to its destination item.


The Info area displays information about the selected connection or feature class.

Connection (or Class)

If you select the schema node, this area is blank.

Source Coordinate System

If there are multiple coordinate systems for the classes under the selected connection, this field displays “VARIES.”

Filter Info

If the selected item is a filtered layer, this area will display “Filter,” “Spatial Filter,” “Property Filter,” or “Spatial And Property Filter.”

Target Coordinate System

If there are multiple coordinate systems for the classes under the selected connection, this field displays “VARIES.”

Ignore The Following Errors During The Copy Process

Select the error types to ignore during processing. If you leave error types unselected, Bulk Copy stops processing and reports these errors when they occur.

Insert Errors

Select this option to continue Bulk Copy if there is an error inserting an object. Objects that fail are skipped. Errors can occur if there are any anomalies in the object data being copied.

Anomalies can include an unmatched feature ID, a value that is outside the range allowed for a property, a constraint violation (for example, each item must be unique and the source is trying to copy over an object that already exists in the target), or an inappropriate value (for example, a string value that is too long).

Unmatched Data Or Geometric Type Errors

Select this option to skip association and object properties that the target data store does not support.

NoteAutoCAD Map 3D does not support either association or object properties, but they may be present in existing schemas created outside AutoCAD Map 3D.

Some dimension properties are also skipped. For example, if you copy 3D data to a 2D target, the z-coordinate is silently removed. Some fields can be converted, for example, from int32 to int64, from int32 to double, or from int32 to string. However, if a target does not support a data type (for example, blob or polygon geometry), the data cannot be converted and the object is skipped.For information about how fields are converted, see Understanding How Bulk Copy Converts Data Types.

When the geometry coordinate system is Lat/Long, SQL Server Spatial considers the inside of a polygon to be to the left of the outer boundary. If a polygon with a clockwise boundary is inserted, the polygon actually covers the rest of the world, excluding what appears to be inside the polygon from an onscreen perspective. If you check Unmatched Data Or Geometric Type Errors as an error type to ignore, the geometry and orientation are adjusted when the target is SQL Server Spatial. If you do not check this option and you copy a polygon with the wrong orientation to SQL Server Spatial, that object will fail to copy.

Coordinate System

Select this option to copy the geometry without performing a coordinate system transformation, for example, if information for the source or target coordinate systems is missing, but you are sure that the geometry coordinate systems are the same. If you are not sure of one of the coordinate systems, this option can produce undesired results.

For example, if you are missing the .PRJ file for the .SHP file you are copying, but you know that the coordinate system is the same as the target, use this option.

Schema Mapping


To save the current settings in an XML mapping file, click Save. Click Load to open a saved mapping file.

NoteBefore loading a mapping file, connect to the source and destination feature sources.
Copy Now

Copy the data for the specified schema elements. Bulk Copy reports warnings and errors depending on the data formats of the two feature sources, and the copying options you selected.

Click View Log to see details.