Numéro d’ID de bogue |
BUG-000178661 |
Envoi | August 12, 2025 |
Dernière modification | October 6, 2025 |
S’applique à | ArcGIS Online |
Version trouvée | June 2025 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | 11.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
This is by design. When exporting a hosted feature layer with the 'Optimize layer drawing' enabled to a file geodatabase, the setting itself is not stored as a flag or property in the geodatabase.
Here is why:
1. The 'Optimize layer drawing' in ArcGIS Online is a service-level performance feature, not an attribute of the dataset.
2. When exporting to a file geodatabase, the raw feature data (points, lines, polygons, attributes) are exported, those cached generalized geometries and the multiScaleGeometryInfo metadata are not written into the file geodatabase tables or schema.
3. In the file geodatabase, only the feature classes and possibly related tables, attachments, domains, subtypes are gotten; no reference to the 'Optimize layer drawing' setting survives the export.
Therefore after exporting:
There is no multiScaleGeometryInfo in the FGDB. The setting is effectively gone. To publish the file geodatabase again as a hosted layer or to update a hosted layer with this file geodatabase, re-enable 'Optimize layer drawing' in the service settings.
Currently, the server automatically enables 'Optimize layer drawing' during publishing if the vertices of any feature exceed 400,000, even though the 'Optimize layer drawing' is disabled. In the example, none of the features has more than 400,000 vertices, so the server would not enable 'Optimize layer drawing'.
Étapes pour reproduire
ID de bogue: BUG-000178661
Logiciel: