Select to view content in your preferred language

Exporting data from File GeoDB to SHP ??? attribute data tampering?

816
1
Jump to solution
01-21-2012 11:06 AM
PieterCoetzer
Deactivated User
Hi guys,

I have now come across this problem a couple of times. I have data in a File GeoDB that I export to SHP file format using ArcCatalogue. The spatial data and almost all the attributes exports correctly except for an ID filed (Type Double).

In the GeoDB the ID field is 17100027000010 but when exported to the SHP format it is changed to 17100027000000. This happens with all the values in the same range, leading to all of the records in the range ending with a value of 17100027000000.

Has anyone come across this and if so, id there a fix or workaround to export the data to the correct values?

Cheers,

Pieter
0 Kudos
1 Solution

Accepted Solutions
VinceAngelo
Esri Esteemed Contributor
If you look at the raw data stored in the .dbf file of the shpfile triplet, you'll probably
see that the value is represented in scientific notation with 18 characters:

+1.71000270000E+13

This is an intrinsic limitation to the dBase-III+ format. In the famous words of Chief
Engineer Scott -- "She cannae take any more, Captain!"

If you want to represent this value in dBase, you'll need to convert the value to string
(in Hexadecimal notation it would be 0F8D6908F4CA) or use some other method to
eliminate some zeros.

- V

View solution in original post

0 Kudos
1 Reply
VinceAngelo
Esri Esteemed Contributor
If you look at the raw data stored in the .dbf file of the shpfile triplet, you'll probably
see that the value is represented in scientific notation with 18 characters:

+1.71000270000E+13

This is an intrinsic limitation to the dBase-III+ format. In the famous words of Chief
Engineer Scott -- "She cannae take any more, Captain!"

If you want to represent this value in dBase, you'll need to convert the value to string
(in Hexadecimal notation it would be 0F8D6908F4CA) or use some other method to
eliminate some zeros.

- V
0 Kudos