For foreign schemas, the Bulk Copy operation uses the first geometry it finds to create the geometry in the target data store. If there are multiple spatial indexes for the geometry properties in the original data store, the geometry property in the resulting data store’s schema will be different from the order in the original data store. As a result, the geometry in the new data store may not match the geometry in the source.
To fix a Bulk Copy geometry problem in the original data store
- Remove the unwanted spatial indexes from the geometric properties in the original data store.
If only one geometric property is indexed, it is chosen as the main geometry for the feature class.
To fix a Bulk Copy geometry problem in the resulting data store
- Connect to the new data store before you perform the Bulk Copy operation.
- Using the Schema Editor, save the source data store to an XML file.
- Edit the XML file and add the following to the <xs:complexType> entry for the feature class in question, where {geom_prop_name} is the name of the geometric property to use:
fdo:geometryName="{geom_prop_name}"
- Import the modified XML file into the target data store and apply the changes.
- Bulk Copy the data from the source to the target data store, making sure to map the geometry properties properly before executing the Bulk Copy.