Back in 2011, Vince Angelo mentioned the following workflow for improving feature class performance:
[When exporting a feature class, you can develop a workflow to] query in spatial index order, which would optimize created feature order, which should result in improved performance with every query. And if you're going to do that, then you should also optimize your coordinate reference to reduce storage and improve query performance.
https://community.esri.com/t5/data-management-questions/maintain-objectid-values-when-importing-a/m-...
If I understand correctly, that optimization isn’t done automatically when exporting/importing a feature class.
Could a geoprocessing tool be added that would perform that workflow out of the box? Or provide an option to do that as part of the export GP tool?
