Select to view content in your preferred language

ArcGIS Pro data export results in consolidation to single location

470
12
Jump to solution
11-21-2024 11:51 AM
JasonWeis_Westwood
Occasional Contributor

This week, after updating ArcGIS Pro to version 3.4.0, when I attempt to export a selection of points collected with Field Maps in an ArcGIS Online hosted feature layer to a file geodatabase feature class, all of the exported points show up in a single location (the location of one of the exported points).  This occurs with both a right-click on the layer name (with Data: Export Features), and also with starting directly from the Export Features geoprocessing tool. The other attributes appear to maintain their original values - it is simply the location that gets modified.

I have been using this workflow frequently in the past (exporting a subset of collected points to a project-specific geodatabase), and the points always exported to the correct location, even if specifying a new coordinate system. I did not notice this "consolidation" until this week, which just happens to coincide with my v3.4.0 update.

When I tested this with other ArcGIS Online point data that was NOT populated using Field Maps, the points exported correctly. Likewise, when exporting selected points from a local source (file geodatabase), the points also exported correctly.

I am attempting to find ArcGIS Pro installations within the organization that have not upgraded to 3.4.0 to see if it is version specific. Has anyone else encountered this issue?

Tags (1)
1 Solution

Accepted Solutions
JasonWeis_Westwood
Occasional Contributor

From another post: https://community.esri.com/t5/arcgis-pro-questions/problem-exporting-features-from-feature-service-t...

It sounds like a bug has been logged (BUG-000172816) and is being reviewed by Esri. A temporary workaround seems to involve disabling the export of attachments in the feature layer (Environments / uncheck Maintain Attachments).

Hopefully a 3.4.1 patch will be issued soon, since this is an important part of my workflow.

View solution in original post

0 Kudos
12 Replies
KathleenCSki
Regular Contributor

When all your point stack up it's a sign that your display cache is full. 

Esri recommends clearing the cache regularly in ArcGIS Pro. To do this, navigate to ArcGIS Pro Project menu > Options > Display > Local cache, check the Clear cache check box and click OK. Note, this is not located in the Temp directory, but the Local Caches directory in C:\Users\<username>\AppData\Local\ESRI\Local Caches. 

If you want this to clear regularly you can check the box to Clear Cache each time the application closes.

0 Kudos
DylanTurner
New Contributor

Thanks for this! Clearing the cache appears to have worked for me. 

0 Kudos
DarrylAlbert
Regular Contributor

Thanks you, however this did not work for me either. 

0 Kudos
KathleenCSki
Regular Contributor

Sorry Darryl. This worked for me in several previous versions, but I am not yet on version 3.4. After clearing the display cache make sure you have enough free memory for the location you are saving the file, at min at least 2 times the size of the file you are downloading if you know this. Then try to re-export the feature. 

0 Kudos
JoannaTaylor
New Contributor

I'm having the same issue and have also recently updated to 3.4.0.  I use this workflow frequently so need to find a solution.

I've tried clearing the local cache, no luck with that.

JasonWeis_Westwood
Occasional Contributor

I cleared the display cache, and there was no change in the behavior.  The points are definitely being exported on top of each other - not simply displayed.

I found a workstation with version 3.3.1, and the feature export worked exactly as expected, using the same data source and APRX.  Therefore, it appears that there is something with version 3.4.0 that is causing the Field Maps points to be exported on top of each other.

Tags (1)
Richard_Caprio
New Contributor

Also having the same issue, just reached out to Esri Tech Support to report bug.

JasonWeis_Westwood
Occasional Contributor

Thank you for reporting the bug to Esri - I don't have "bug reporting rights" in my organization, so hopefully this will get it on their radar. Based on this thread and the one that I posted on the ArcGIS Pro forum, it appears that several people are experiencing the same issue. If you receive an update from Esri, please keep us posted.

0 Kudos
JuanitaBorden
Occasional Contributor

I am adding my name here as I had the same issue happen. I tested multiple layers and it's doing the same thing, so hoping to see if there is a fix for this.