I'm having problems with Experience Builder Exports (shapefiles and FGDB's) reversing the ring order for polygons with holes. This causes a negative (inverse) acreage to appear when GIS acres are calculated.
By allowing non-GIS savvy staff members to export polygons and submit them to various organizations outside of our own, it cuts down on the work I have to do and provides staff with autonomy since they don't have to wait on me. Several outside agency folks have reported issues with these EB exports when calculating acreages (having negative values) and they have to run a "repair geometry", which corrects the ring order, before the acreage will appear as a positive number.
So, I ran a repair geometery on the original feature and no problems are reported (ring orders are correct). However, every time I export the feature via EB the rings are reversed. Is this a bug and can it be fixed?
Exporting to geojson and converting it to a feature class retains the original ring order, but this would be an extra step the end user has to perform and isn't ideal.
I've attached the original feature along with the same feature exported from EB.
