Migrating GIS Data (Bulk Copy)
Concept Procedure
 
 
 

You can use Bulk Copy to copy data from one feature source to another, either in the same format or in a different one.

Using Bulk Copy, you can copy the complete feature source or a subset based on a specified schema, feature class, or property. You can also filter a Display Manager layer using an expression, and then use Bulk Copy to create a data store that contains only the filtered data.

What You Can Do With Bulk Copy

Use Bulk Copy to do the following:

Bulk Copying To SDF Format

If you create a new SDF file in AutoCAD Map 3D, you can use it as a target for Bulk Copy. However, you must delete the default schema before copying data to the new SDF file.

Bulk Copying to SHP Format

A single SHP file can hold only one class. To copy multiple classes, to an empty folder through the FDO SHP provider. When you copy to that connection, Bulk Copy creates a new SHP file for each class you copy. Do not create a new SHP file in Schema Editor and use the new SHP as your Bulk Copy target.

A SHP schema cannot be modified once it is applied.To avoid this limitation when you copy SDF data to SHP, export the SDF schema. Then, when you create the target SHP schema, delete its default schema and import the SDF schema. This way, you can fix any errors in the schema. During the Bulk Copy, select the feature class and property names in the To column and match them exactly to the From column.

Depending on the size of the file, you can also import the SDF data and export it as SHP.

Bulk Copying To or From SQL Server Spatial

When you copy data from an FDO-enabled SQL Server Spatial data store to a non-FDO data store, class and property names may not be accepted by the destination data store because naming rules vary between providers. You can use schema mappings to rename schema elements that you copy, to be sure they meet the naming rules of the destination data store.

You can also pass in a set of schema capabilities to the target data store, so the cloned schemas conform to the capabilities of that data store.

When you copy geodetic polygons with clockwise rings to SQL Server Spatial, check Unmatched Data Or Geometric Type Errors as an error type to ignore.

For geography, 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 ignore unmatched geometry type errors when using Bulk Copy, 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.

Also, SQL Server Spatial does not currently support such polygons that are bigger than one hemisphere.

Other Ways to Migrate Data

If you are moving data from DWG format to any other format, you cannot use Bulk Copy. Instead, see Migrating DWG Data to GIS.

If you are moving geospatial data into SDF format, it may be easier to save or export its Display Manager layer to SDF, without going through Bulk Copy. See Saving or Exporting a Display Manager Layer.

Things to Remember

When using Bulk Copy, keep in mind the following points :

Tell me more

Animation

Procedure

Tutorial

Workflows

GIS Skill

Related topics