Is This Content Helpful?
We're glad to know this article was helpful.
In ArcMap, when geocoding a table exported from an Excel file, the values may be rounded to the nearest tenth. For example, a field value of '2008030257' becomes '2008030260' after geocoding.
This issue occurs when the precision and scale of a field from the imported table does not match the precision and scale of the output field after geocoding is performed.
When a table from an Excel file is imported into ArcMap, the 'long' field property changes to 'double' by default, causing an incorrect output when the table is geocoded.
When merging, importing, or exporting, input datasets into output datasets, all input dataset fields are mapped to the output dataset.
The default field mapping setting must be modified to resolve this issue.
To do this, use the Table to Table tool as it allows to modify or set the Field Map parameters. Hence, users can increase the precision and scale values of the problematic field.