ArcGIS Pro failing to export shapefile even after Big Integer field deleted

1383
5
10-16-2024 02:18 AM
Labels (1)
YusefSamari
Frequent Contributor

I am working with a SQLite database feature class from a Geopackage which I want to export as a shapefile:

YusefSamari_1-1729069888413.png

It has a Big Integer type field which I understand is not supported by the shapefile format. However, even after deleting the Big Integer field, and then exporting, I get the following error message:

ERROR 010672: The output workspace does not support database fields containing 64 bit integer values.

If I delete the Big Integer field, then export the feature class from the Geopackage to a File Geodatabase Feature Class, and then try and export that as a shapefile, I get the same error message. If I buffer the feature class, then use the original as clip features to clip out the same boundary from the buffer, and try and export that, I get the same error message. This is all after deleting all fields except OBJECTID, Shape_Length and Shape_Area from the original. It is as if some memory of the Big Integer field once being there is being copied over again and again.

Most bizarrely of all, if I create a new, empty file geodatabase feature class, draw a big polygon around the SQLite feature class (or any file geodatabase feature class derived from it), then use the SQLite feature class / derived product to clip the boundary out from the new polygon, which has no fields beyond those of a newly created feature class, I still get the same error message.

Attempting to export the SQLite class to a shapefile from QGIS works fine. I find this 'ghost-like' behaviour, of error messages popping up for things that have had all traces of what caused the error removed, crops up fairly often for me on ArcPro. Does anyone have any idea what is going on? I am using Pro version 3.3.1.

0 Kudos
5 Replies
RobertCao
Esri Contributor

Hello @YusefSamari ,

 

It seems you may be encountering a known software defect in this case: https://support.esri.com/en-us/bug/geopackage-feature-class-objectids-are-read-as-64bit-in-bug-00016...

0 Kudos
SeaRM
by
Frequent Contributor

Yes, I agree with @RobertCao . It is caused by OID 64bit field that the input geopackage IDs are considered like. You may try XTools Pro Modify Table tool. It creates shapefiles with simple FIDs.

https://help.xtools.pro/agp/24.1/en/XTools_Pro_Components/Table_Tools/Modify_Table.htm

0 Kudos
YusefSamari
Frequent Contributor

Thanks for the replies. Good to know this is a bug as suspected. I don't have access to XTools but thanks for the info.

0 Kudos
RobertCao
Esri Contributor

It seems that downgrading your ArcGIS Pro to version 3.1.x could serve as a workaround in this situation.

0 Kudos
YusefSamari
Frequent Contributor

Thanks. The quicker and easier workaround for me right now is just to run the operation in QGIS, but thanks for the help.

0 Kudos