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; } } }

Why does it take so long to export a small feature class to shapefile?

Matt-Goodman

Why would it take almost 19 minutes for ArcGIS Pro to export a fairly simple feature class from a file geodatabase (.gdb) to a shapefile (.shp). Both source and export locations are near each other in the C:\ (hard drive) of the machine. Pro is a very recent version and the .gdb matches that version. There are only three (3) polygon features in the feature class!

Find more posts tagged with

Geodatabase

Desktop

Accepted answers

DanPatterson

From Export Features (Conversion)—ArcGIS Pro | Documentation

Note:
Conversion to a shapefile with subtype and domain descriptions may take more time (slower performance) than without descriptions. If subtype and domain descriptions are not required in the output, leave the Transfer field domain descriptions environment unchecked for best performance.

If that applies, but 18 minutes for 3 features is certainly not expected. Give this a try if your output is simple

Copy Features (Data Management)—ArcGIS Pro | Documentation

All comments

snowdrop7934

We've struggled with this issue the past 2 years. Either exporting to shapefiles, file geodatabases, or exporting small areas of a raster. Doesn't matter, takes way too much time. Esri will recommend a soft reset of the user profile or uninstall and reinstall pro. I've done this multiple times, it doesn't really help. Customers should not have to resort to tricks or workarounds or uninstalling 5 times a year to get the software to work. Unfortunately we've just gotten used to starting a process and then coming back to it an hour later.

Maybe check and clear the geoprocessing history?

DanPatterson

From Export Features (Conversion)—ArcGIS Pro | Documentation

If that applies, but 18 minutes for 3 features is certainly not expected. Give this a try if your output is simple

Copy Features (Data Management)—ArcGIS Pro | Documentation

Matt-Goodman

I almost replied "...nah, this isn't causing the issue" (being very 'certain' that I didn't have any subtypes or domains set up in this database). But when I actually checked, I was surprised to see a bunch of domains that were apparently carried-over into the database at some point. Which shows you have to pay attention to the origins of your geodatabase, and what you import into it. The layers associated with those domains were long gone from the database, but the domains remained.

Thanks for mentioning this as a possible cause.

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.