| Numéro d’ID de bogue |
BUG-000165963 |
| Envoi | March 15, 2024 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS Pro |
| Version trouvée | N/A |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 10.0 64 Bit |
| Statut | As Designed
Après examen par l’équipe de développement, il a été déterminé que ce comportement est prévu. Pour plus d’informations, reportez-vous à la section Informations supplémentaires.
|
Informations supplémentaires
Geodatabase data uses a 'spatial reference'. In addition to the coordinate reference system, there are other values used for storage and processing. The storage parameters include the x, y, z, and m resolutions, which are in the unit of the coordinate system and control how precise the stored coordinate values are. The default for x, y and z resolution values is 0.1 mm (0.0001 m) or the equivalent in the unit of the coordinate system. The processing values are the x, y, z, and m tolerance values and the default is 1 mm (0.001 m). By processing, things like deciding two points are coincident or two segments touching at the end point. The parameters for a spatial reference for a shapefile are calculated as needed and are not stored within the shapefile. Zooming in to 1:0.05 is well beyond what is recommended. If you check the coordinate values of the sample point, the original data is more precise than 4 decimal places, while the feature class is at 4 decimal places to match the spatial reference precision. There are some white papers that discuss this, like:
Understanding Coordinate Management in the Geodatabase: https://downloads.esri.com/support/whitepapers/ao_/J9655_Understanding_Coordinate_Management_Esri_Whitepaper.pdf
Understanding Geometric Processing in ArcGIS: https://downloads.esri.com/support/documentation/ao_/J9880_ArcGIS_CoordMgmt_Geometric_Processing.pdf
Étapes pour reproduire
ID de bogue: BUG-000165963
Logiciel: