We have several File Geodatabases with custom XY Resolution and XY Tolerance settings that differ from the Esri defaults. For example, one dataset has an XY Resolution of 0.00005 m and an XY Tolerance of 0.0004 m.
Our long-term goal is to migrate all of our data to Esri's standard XY Resolution and XY Tolerance values. However, due to the size of our existing data holdings and dependent applications, this migration will take time. During this transition period, we need to be able to publish hosted feature services that preserve the legacy XY Resolution and XY Tolerance settings.
However, when we publish this data as a hosted feature service to an ArcGIS Enterprise data store, these settings appear to revert to the Esri default values (XY Resolution = 0.0001 m, XY Tolerance = 0.001 m).
We do not understand the technical background behind this behavior. When we inspect the File Geodatabase contained in the service definition (.sd) file, the custom resolution and tolerance values are still present. Nevertheless, the resulting hosted feature service operates with the Esri default values.
Our questions are:
- Is it possible for hosted feature services to preserve custom XY Resolution and XY Tolerance settings?
- If so, are there any ArcGIS Enterprise or data store configuration settings that need to be adjusted?
- Is this expected behavior by design, or could it indicate a publishing limitation or issue?
- Has anyone else encountered this situation while transitioning from legacy XY Resolution and XY Tolerance settings to the Esri defaults?
Any insights into the underlying implementation or recommendations for handling this transition would be greatly appreciated.
