You are here:
About importing coverage or CAD annotation into geodatabase annotation
Geodatabases and ArcSDE
Building a geodatabase
Working with geodatabase datasets
NOTE: ArcEditor or ArcInfo is required to import into a feature-linked annotation feature class.
You can import one or more coverage annotation feature classes with the Import Coverage Annotation tool
. Similarly, you can import one or more CAD annotation feature classes with the Import CAD Annotation tool
. Both tools import into a new standard or feature-linked annotation feature class they create in the process. Importing from these formats into a feature-linked annotation feature class does not link annotation to features, but does create the relationship class.
Learn how to link the imported annotation
Values stored in regular text attributes in the annotation feature classes you import are carried over to the new feature classes.
Coverage and CAD annotation import into the geodatabase as they appear in ArcMap. For this reason, you should carefully set up the display of the annotation before you import. If you’re importing several tiled annotation feature classes at the same time, you need only to set up symbology for the first annotation feature class you list in the Import Coverage Annotation or Import CAD Annotation tool. The tools allow you to apply the same symbology to all the other feature classes you import.
Coverage pseudo items and annotation appearance
When you display a coverage annotation feature class in ArcMap or ArcInfo Workstation, pseudo item fields in the coverage's text attribute table determine how the annotation displays. Pseudo items are used differently in ArcMap than they are in ArcInfo Workstation, and geodatabase annotation feature classes do not store pseudo items. Consequently, there are a couple of rules to keep in mind when importing coverage annotation:
- Because the following text symbol properties are stored in pseudo items, you can't change them with ArcMap: vertical and horizontal alignment, x and y offset and—if $SIZE doesn't equal zero—the text size. If you want to change any of these properties, change the pseudo item property with ArcInfo Workstation before displaying and importing the annotation with ArcMap. Another approach is to change the property in the new annotation feature class after import.
- If you want to carry over pseudo item values when converting—for example, for the purposes of querying—you should use ArcInfo Workstation beforehand to create regular items (not pseudo items) in the text attribute table that stores these attributes.
The values in the pseudo item $SIZE determine how the text size is set for the imported annotation. If the value is zero, the ArcMap text symbol size is used. This means you must display the annotation in the correct text symbol size before importing. The size you choose is the size in which the new annotation will display at the scale you’re zoomed to.
If the $SIZE value is not zero, you cannot change the size of the annotation in ArcMap. In this scenario, the $SIZE value is used as the size instead of the ArcMap text symbol size.
Learn more about coverage annotation pseudo items
How to import coverage or CAD annotation into geodatabase annotation
- In ArcMap, add the coverage or CAD annotation feature class you want to import.
- Zoom to the scale at which you'll normally view the imported annotation.
- Symbolize the annotation as you want it to appear once converted.
- Open the ArcToolbox window, click Toolboxes, click System Toolboxes, click Conversion Tools, and click the plus sign to expand To Geodatabase.
- If you're importing coverage annotation, double-click Import Coverage Annotation. If you're importing CAD annotation, double-click Import CAD Annotation.
- Add the layers with the annotation feature class data sources you want to import.
- For Output feature class, navigate to the location of the new annotation feature class and specify its name.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.
- Specify the reference scale.
- For Create annotation classes from levels, check this box if you want to create an annotation class for each level defined by the $LEVEL field. If you want to combine levels into a single annotation class in the output feature class, leave this box unchecked.
- 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 Match symbols from first input. This prevents a symbol from being added to the new feature class's symbol collection more than once.
- For the 'Require symbol to be selected from the symbol table' option, see Annotation feature class editing properties.
- For Feature-linked, if you want to import into a feature-linked annotation feature class, check this box. If you don't want to import into a feature-linked annotation feature class, skip to step 15.
- For Linked feature class, navigate to the existing geodatabase feature class to which the new annotation feature class will link.
- For the 'Create annotation when new features are added' and 'Update annotation when feature's shape is modified' options, see Annotation feature class editing properties.
- Click Environments.
- Expand General Settings.
- Set the output coordinate system.
- Expand Geodatabase Settings.
- 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.
- 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.
- If you’re importing to an ArcSDE geodatabase and have additional grid sizes, type them in.
- Set the x,y domain.
- Click OK.
- On the Import tool, click OK to import the annotation feature classes.
- You can run the Import Coverage Annotation tool from ArcCatalog as well. However, all imported annotation is assigned the default font Arial and—if the $SIZE value is zero—the default size is 14 pt.
- If there are errors, an error message and dialog box will appear after you import your annotation. You can get more information about the errors by checking the log files listed in 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 will have the name 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 will be named GLAlbanyAnno0.log. The second file will be named GLAlbanyAnno1.log, and so on.
- The errors listed in the log file are 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. This will eliminate 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 will 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.
Please visit the Feedback
page to comment or give suggestions on ArcGIS Desktop Help.
Copyright © Environmental Systems Research Institute, Inc.