Hi everyone,
I have a hosted feature layer in AGO that contains 9 polygon layers and 1 point layer. I add that layer to ArcGIS Pro and then I have a selecting polygon layer. I use the Select by Location to select features from 4 of the polygon layers and the point layer. All of the layers select the correct features except for one of the polygon layers. I'm using Intersect, but it also fails with Completely Contains. What could be wrong with this one layer? or what's wrong with AGO?
If I export the data to a file geodatabase feature class first then the select by location works.
If I try the select by location within an AGO map (Analysis - Tools - Find by Attributes and Location) , it also fails.
Thank you,
A
There’s no current ArcGIS Online incident reported, so this is unlikely to be an AGO outage. When one sublayer in a hosted feature layer consistently fails spatial selection in both ArcGIS Pro (Select By Location) and ArcGIS Online (Find by Attributes and Location)—but works after exporting to a file geodatabase—that strongly suggests the hosted sublayer contains problem geometries (for example null/empty geometry, self-intersections, bad ring ordering, unclosed rings) and/or true curve geometry that’s not being handled as expected server-side.
Try these steps:
Hi @Robert_LeClair ,
Thank you for the response. I exported 2 polygons from the layer and ran check geometry and there weren't any problems. I can run the full layer in future to check.
I reached out to Esri tech support and as a test, I have republished the whole hosted feature layer using the same data and the Select by Location works now. So I will have to overwrite the original hosted feature layer to move forward. I have a View Layer on this original layer though, so, sadly, I will have to delete View Layer, overwrite feature layer, Recreate View Layer using the same name, and reshare View Layer. I wish the View Layer didn't lock down the original layer from being overwritten.
Thank you for your ideas. Have a good weekend,
A