- Esri Geodatabase Reader/Writer
- Geodatabase Quick Facts
- Overview
- Reader Workbench Parameters
- Writer Workbench Parameters
- Feature Types
- Table Representation
- Improving the Speed of Translations Using the Geodatabase Writer
- Tips for Using the Geodatabase Writer
- Technical Reference: Mapping File Directives
- Reader Mapping File Directives
- Reader Directives - All Geodatabase Types
- Reader Directives: Geodatabase Feature Classes
- Reader Directives: Raster Dataset
- Reader Directives - Enterprise Geodatabase
- Reader Directives - Enterprise Geodatabase Feature Classes
- Reader Directives - Personal Geodatabase
- Improving the Speed of Translations Using the Geodatabase Reader
- Simple Reader Example
- Writer Mapping File Directives
- Writer Directives - Feature Classes for all Geodatabase Types
- Writer Directives - All Geodatabase Types
- Writer Directives - Enterprise Geodatabase
- Writer Directives - Enterprise Geodatabase Feature Classes
- Writer Directives - Personal and File Geodatabase
- Writer Directives - Geodatabase Raster Datasets
- Writing Subtypes and Domains
- Reader Mapping File Directives
You are here: Popular Formats > Esri Geodatabase Reader/Writer > Table Representation > Writing Annotations
Troubleshooting
Writing Annotations
Translating annotations from one geodatabase to another results in annotations showing up incorrectly. This occurs on annotations, which in the source, had symbols defined.
This is because symbol IDs are not translated when writing to a new geodatabase.
Prior to writing, a destination geodatabase must be created with an annotation feature class that has predefined symbol IDs.
Related Links