- Esri Geodatabase Reader/Writer
- Geodatabase Quick Facts
- Overview
- Reader Workbench Parameters
- Esri Geodatabase (ArcSDE Geodb) Reader Parameters
- Esri Geodatabase (ArcSDE Geodb Raster Catalog) Reader Parameters
- Esri Geodatabase (ArcSDE Geodb Raster Dataset) Reader Parameters
- Esri Geodatabase (File Geodb ArcObjects) Reader Parameters
- Esri Geodatabase (File Geodb Raster Catalog) Reader Parameters
- Esri Geodatabase (File Geodb Raster Dataset) Reader Parameters
- Esri Personal Geodatabase MDB Reader Parameters
- Writer Workbench Parameters
- Table Representation
- Feature Representation
- Improving the Speed of Translations Using the Geodatabase Writer
- Tips for Using the Geodatabase Writer
- 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 FormatsEsri Geodatabase Reader/WriterTable RepresentationCreating Relationship Classes
Currently, FME cannot be used to create relationship classes. These should be created before the translation using ArcCatalog. FME can then be used to populate these existing relationship classes from source origin and destination features that are related to one another.