- 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 > geodb_type <geodb_type>
geodb_type <geodb_type>
When the Geodatabase writer creates a new table, it looks for the geodb_type specified on the feature type.
For a list of the valid geodb_types, see Feature Representation. If the geodb_type is not valid or is not found on the feature type, then the geodb_type attribute will be retrieved from the first feature headed for that table.
In the unlikely occurrence that the feature does not have a valid geodb_type or any geodb_type, then a warning will be logged, the writer will assume that the geodb_type is geodb_type, and a non-spatial table will be created. As a result, all features of that feature type will have their geometry ignored.