FAQ: When converting, why are some field definitions not consistent with the mapping in the doc?
When converting, why are some field definitions not consistent with the mapping in the doc?
The documentation provides a guideline for how fields are mapped from INFO items and dBase field types into geodatabase field types. However, to accommodate data being imported, in some cases the field mapping will occur differently depending upon the type of database the geodatabase is stored in. The most typical case is where an item maps to a double field when it may have mapped to a floating point or long integer field.
Last Published: 5/5/2016
Article ID: 000003194