How to import coverage, CAD, or VPF annotation into geodatabase annotation

This topic applies to ArcEditor and ArcInfo only.

  1. In ArcMap, add the coverage, CAD, or VPF annotation feature class you want to import.
  2. Zoom to the scale at which you'll normally view the imported annotation.
  3. Symbolize the annotation as you want it to appear once converted.
  4. In the Catalog tree, click the plus signs to expand Toolboxes > System Toolboxes > Conversion Tools > To Geodatabase.
  5. If you're importing coverage or VPF annotation, double-click Import Coverage Annotation. If you're importing CAD annotation, double-click Import CAD Annotation.
  6. Add the layers with the annotation feature class data sources you want to import.
  7. For the Output feature class option, navigate to the location of the new annotation feature class and specify its name.
  8. If you're importing into a new feature-linked annotation feature class, you must specify a feature class in the same feature dataset as the linked feature class or at the root level of the geodatabase if the feature class you're linking to is at the root level of a geodatabase.

  9. Specify the reference scale.
  10. For the Create annotation classes from levels option, check this box if you want to create an annotation class for each level defined by the $LEVEL field.
  11. If you want to combine levels into a single annotation class in the output feature class, leave this box unchecked.

  12. If you're importing a set of annotation feature classes that all use the same symbols and the same $SYMBOL value to refer to each symbol, check the check box for Match symbols from first input. This prevents a symbol from being added to the new feature class's symbol collection more than once.
  13. For the Require symbol to be selected from the symbol table option, see Annotation feature class editing properties.
  14. For the Feature-linked option, if you want to import into a feature-linked annotation feature class, check this box.
  15. If you don't want to import into a feature-linked annotation feature class, skip to step 15.

  16. For the Linked feature class option, navigate to the existing geodatabase feature class to which the new annotation feature class will link.
  17. For the Create annotation when new features are added and the Update annotation when feature's shape is modified options, see Annotation feature class editing properties.
  18. Click Environments.
  19. Expand General Settings.
  20. Set the output coordinate system.
  21. Expand Geodatabase Settings.
  22. If you’re importing into a file or ArcSDE geodatabase and you want to create the feature classes using a custom storage keyword, type the keyword.
  23. If you're importing into a personal or ArcSDE geodatabase and know an optimal spatial index grid size for your data, specify it in map units.
  24. If you’re importing to an ArcSDE geodatabase and have additional grid sizes, type them in.
  25. Set the x,y domain.
  26. Click OK.
  27. On the Import tool, click OK to import the annotation feature classes.
If there are errors, a message and dialog box appear after you import your annotation. You can get more information about the errors by checking the log files listed on the dialog box.
  • A log file is only created if there are errors.
  • The file is created in your user temp directory, which is commonly found under \Documents and Settings\user\Local Settings\Temp.
  • The log file is named GL<feature class name>#.log. For example, if the target annotation feature class is AlbanyAnno, then the first error log file created for this target is GLAlbanyAnno0.log. The second file is GLAlbanyAnno1.log, and so on.
  • The log file lists geodatabase errors associated with loading or changing features.
If you are working with an ArcSDE geodatabase, when possible, import the annotation before you version your data. Doing so eliminates the processing time required for reconciling and posting the edited version back to the parent version.
The row length for an annotation feature varies depending on: the length of the text string, whether or not the text is curved (curved text takes up more space), and the internal symbol storage. For text annotation, row lengths of 80–100 bytes are typical. Graphics stored as annotation require 400 bytes or more per row.
When importing into feature-linked annotation, if your target annotation feature class is linked to a network feature class, you should import the annotation after building the geometric network. This is recommended because when features are snapped in the network building process, their geometry is modified in such a way that linked annotation features are not updated.

Related Topics