How is everyone handling feature linked annotation when migrating to the UN? We have feature linked annotation for material, diameter, and year built related to our watermains. I know I could probably add a temporary field to the featureclasses and recreate the relate after migration. I am wondering if just using labels would be better at this point. Labeling capabilities have gotten better over the years.
Solved! Go to Solution.
Using labels doesn't require you to migrate any feature, so it is certainly easier. Migrating feature-linked annotation can be tricky, as it requires creating the corresponding feature-linked annotation classes in the target environment related to the new objects in the utility network.
It is up to you as to whether you want to consolidate your annotation classes or keep them separate. Consolidating them will require additional configuration to modify the filters for each annotation class to ensure it only applies to the corresponding asset group.
Using labels doesn't require you to migrate any feature, so it is certainly easier. Migrating feature-linked annotation can be tricky, as it requires creating the corresponding feature-linked annotation classes in the target environment related to the new objects in the utility network.
It is up to you as to whether you want to consolidate your annotation classes or keep them separate. Consolidating them will require additional configuration to modify the filters for each annotation class to ensure it only applies to the corresponding asset group.