Combine existing feature-linked annotations

Summary

Note:
ArcSDE software, including the application server, command tools, and SDK with C and Java APIs, was deprecated at ArcGIS 10.2.2 and is no longer distributed.

Note:
This article pertains to ArcGIS versions 9.x. Later versions of ArcGIS may contain different functionality, as well as different names and locations for menus, commands and geoprocessing tools.

Instructions provided describe how to combine feature-linked annotations and their related features from different geodatabases into one geodatabase to maintain already established feature-linked annotations locations.

Procedure

Normally, new feature-linked annotations are created in an associated feature class when new features are added to the linked feature class. If annotations in the source are relocated for display purposes, follow the procedure below to move existing feature-linked annotations into the target instead of creating new ones and repositioning them. This procedure is for merging data with the same feature class/feature linked annotation schemas defined in each geodatabase.

Note:
Test this procedure and ensure that the results are satisfactory before using it in a production environment.

Note:
Combine all data in either a personal geodatabase or Spatial Data Engine (SDE) as there is an issue with user_defined fields in the annotation feature class when appending from a personal geodatabase to SDE. If work is done in a personal geodatabase, copy the final feature class and feature-linked annotation to SDE before creating the relationship class (see step 12).

The feature class and the feature-linked annotation are linked by ObjectID in the feature class and linked by FeatureID in the feature-linked annotation. Each individual source feature class/feature-linked annotation pair may have the same ObjectIDs and FeatureIDs, so it is important to preserve the old links and maintain unique linking identifiers during the merge process.

1. Take a screenshot of the relationship class properties. This information is needed to recreate the feature-linking relationship at the end of the procedure.
2. Delete the feature-linked annotation relationship classes of each geodatabase; this turns the annotation into a standard annotation feature class. If working in a new geodatabase, all data can be copied to the new geodatabase using the copy and paste feature.
3. Create a TEXT field in the feature class called Old_OID. To render all Old_OID values for the primary and foreign keys unique in the reconstructed relationship class, a factor ("new factor") must be added. Select a numeric factor or an alpha factor. If combining more than two datasets, alpha factors are easier to use as it is not necessary to keep track of the highest numeric value in Old_OID. Alpha factors are used in these steps.
   1. For each feature class/feature linked annotation pair, determine a unique alpha factor that is referred to as 'newfactor'. For example, 'a' for FC1/FLA1, 'b' for FC2/FLA2 and so on until all pairs are assigned a unique newfactor.
   2. In ArcMap calculate Old_OID = [objectid] & "newfactor". Make sure to use double quotes.
4. Create a TEXT field called Old_FID in the annotation feature class. The same factor as in step 3 ("new factor") is added to the corresponding Old_FID of feature linked annotation, since it keeps track of its related feature class ObjectID.
   1. Include the newfactor identifiers as described above.
   2. Calculate Old_FID = [featureid] & "newfactor".

Note:
The above steps must be completed for all feature class and feature linked annotation pairs.

5. In ArcCatalog, use the Simple Data Loader to load source feature classes into the target feature class:
   1. Right-click on target feature class > Load > Load Data.
   2. To input data, browse to and select FC2.
   3. Click Add.
   4. If combining more than two datasets, browse to and add the others, if desired.
   5. Click Next for the other dialog boxes.
6. In ArcToolbox use the Append Annotation Feature Classes tool to append the source feature linked annotations to the target feature linked annotation.
   1. For input features, browse to and select source feature linked annotations.
   2. For output feature class, browse to and select target FLA1. Click OK.

Note:
All unplaced annotations in the source are also appended to the target. Do not append across geodatabase types; for example, personal geodatabase to SDE.

7. Once all data loading or appending is complete, if using SDE, register the final feature class/feature linked annotation as versioned.
8. Add the final feature class and feature-linked annotation to ArcMap and start an edit session.
9. Join the feature class to the feature-linked annotation on Old_FID, Old_OID respectively.
   1. Right-click on FLA > Joins and Relates > Join.
   2. Click the first drop-down menu and click Join attributes from a table.
   3. Click the second drop-down menu and click the Old_FID field.
   4. Click the third drop-down menu to choose the feature class. If the feature class is not currently part of the map, click the Browse button to search for it on disk.
   5. Click the fourth drop-down menu and click the Old_OID Field.
   6. Click OK.

Note:
Do not create an index on the Join field. Doing so may create problems getting rid of Old_OID.

10. Open the feature linked annotation attribute table and calculate FLA.FeatureId = FC.Objectid.
11. Save edits, stop editing, remove Join and exit ArcMap.
12. Use the screenshot of the relationship class properties from step 1 to create a new relationship class. If the previous name of the relationship class is already in use, specify another name for the new relationship class.
13. In ArcCatalog, remove the Old_OID and Old_FID fields that were added. If a general function failure is received, check whether there is a temporary index on Old_OID on the indexes tab. If there is, remove it.