nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error 002809 Field OID unsupported in shapefile export

AndrewFletcherWTS

I am using ArcGIS Pro 3.2 and have come across the Error 002809: FIeld OID in xyz is of an unsupported type for the output workspace. I have not been able to find this error in ESRI resources or community chat. It seems like an obvious problem that should not exist given the limited options for export from the geodatabase in Catalog. The geodatabase requires the OID and fails to export as FID or appropriate for shapefile. Any ideas gratefully appreciated. Screenshot 2023-11-29 152147.png

Find more posts tagged with

Content Management

Geodatabase

Desktop

Accepted answers

All comments

AndrewFletcherWTS

Work around, use Geoprocessing Feature Class to Shapefile tool, right clicking and selecting Export to Shapefile in the Catalog is fraught.

DanPatterson

Try Copy Features (Data Management)—ArcGIS Pro | Documentation

from ArcToolbox

SIGMOSELLEAVAL

Same problem here...
I have tried the first work around with success.

SThor1

I am getting this error too. I was not able to resolve using Feature Class to Shapefile. I have a join on my layer that I want to export as a standalone SHP. Keep getting this error. Must have something to do with the new field type "Big Integer" because that is the only one giving me grief here.
Edit: My work around was to delete the "Big Integer field" in my target layer. Not really ideal but got me past the hurdle

MadanThapaChhetri

The same things worked previously, but now, when I try to export, copy, or clip and make the output layer in a folder other than the working geodatabase, I face problems like yours.

ERROR 002809: Field acq_date in delta is of an unsupported type for the output workspace.

MadanThapaChhetri

I tried this but did not work when I tried to export the shapefile to different folder connections.

MadanThapaChhetri

You can add new fields and calculate field operations for added fields, then delete the previous field that hinders your process and try to export it. It will help you to do that.

KFung_TLC

I experienced the exact same issue: what to export a gdb to shapefile on another folder, & this error prevent me from doing so. It never happens before, nor do I know where to locate the issue. How can that be resolved?

WindsorConnecticut

I've tried all of these work arounds and still have an error. I export this exact shapefile on a monthly basis and I've never had a problem until now. This seems like it must be some type of bug with the newest updates from 3.2.2 or 3.2.1... Can we get an ESRI rep in the chat please???

konsta_kuorikoski

This is really odd issue. Nothing so far said here was working. Its almost like having "Big Interger" there from start taints data somehow. I tried to export in project geodatabase, then export again as shapefile. Then manually adding field to Big Integer values and copying them to text field, then removing this supposedly problematic field. This did not work, as I could also read from this thread.

Workaround was to open same geodatabase in QGIS and export to shapefile with that. Looking at field types, QGIS automatically converts field type to Double.

DanHardwick

I have also ran into this problem, and I think one solution is to go into ArcGIS Pro 'Options' and within 'Map and Scene' enable "Use field types that are compatible with ArcGIS Pro 3.1 and earlier...".

Then create a new geodatabase and import your data, it should now allow you to export the data to shapefile.

WindsorConnecticut

I ran into this same issue. I have another computer with an older version of ArcPro, 2.9.1, and this was my workaround until this is resolved.

I have another issue when publishing this layer to my enterprise, which is 10.9.1. I used the same work around of using the older version of ArcPro and I did not have an issue. If this works in 2.9.1 but not the most recent update, it sounds like this is an ESRI issue/bug they need to address.

IanLadd_Tourmaline

Had the exact same issue, "Big Integer"....

KFung_TLC

Still no solutions in sight? I post on this thread last year, & now I need to export features to shapefile & the same error occurred again?

My job needs constantly provide data to municipalities or other agencies, which shapefiles remain the most common type. But everytime I attempt to export from features to shapefiles this bugs me, and they never provide us WHICH field(s) has the problems. For the records, I checked my features in question is 32 bit ObjectID.

Com'on how can this problem remain for so long.

UPDATE: Fortunately I checked the attribute table again (Parcel data in question) & the only one field has the issue is regarding the "Date only". So I change that field from "Date only" to "Date" following the solution I found via here:

https://support.esri.com/en-us/knowledge-base/error-arcgis-pro-002809-field-name-in-location-is-of-an-000032156

Hopefully that annoying bugs can be resolved for good.

ConCon

Still having this issue in ArcGIS Pro 3.4.2 and checking the box in the Map and Scene in options does not allow me to export to a shapefile. I had to copy the data and delete the Big Integer fields. This is not ideal when I am trying to export a live feature service.

KejiLi

I tried, it didn't work......

WindsorConnecticut

The solution I’ve been using is to change the field type from “Date Only” to “Date” when you’re going to export the file. Expand the “Fields” dropdown and find the problematic columns. It doesn’t change anything in the output really. I’m sure there’s some catch with this one but it’s been working for my use.

ehill

My workaround for this is just to export it from the geodatabase to a shapefile in QGIS. I could not figure out how to fix this in arcgis pro.

It's sad this is an issue years later (On version 3.5.4), but hopefully checking the "Use field types that are compatible with ArcGIS Pro 3.1 and earlier...." in map and scene will make it not happen in the future.

SpatialSam

SOLUTION: I had Big Integer fields in my table. A workaround for this was creating a new feature in create feature class (no template layer). Then you can copy the fields over from the layer that was not exporting into this new feature. Update all the field types from Big to Long. Then you can append in the data from the feature that was not exporting into the new feature you just created. Export this new feature to a shapefile. This will allow you to maintain the field names and you essentially just change the field types.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.