Numéro d’ID de bogue |
BUG-000151318 |
Envoi | August 4, 2022 |
Dernière modification | April 16, 2025 |
S’applique à | ArcGIS Pro |
Version trouvée | 3.0 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | N/A |
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
The arcpy.da.Describe function offers better experience when authoring python code (eg: in a notebook) however it is expected it to be slower than arcpy.Describe, especially with egdb data.
When running `arcpy.Describe(...).name`, the logic requires a few ArcObjects to retrieve that particular property, and very few python objects need to be created (a python describe object + the string object for the name).
For `arcpy.da.Describe(...).name`, create a python dictionary and query and create python object for the exhaustive list of known describe properties on the object found. For a FeatureClass this is 60 distinct properties , hence, 60 distinct python objects we have to create a value for. And while some of these python objects are strings and numbers, some of them are GPDescribe.Index , GPDescribe.Field, and GPDescribe.Children which are a full large-scale GPDescribe object.
In conclusion, arcpy.da.Describe is better to work with but can be slower, while arcpy.Describe is opaque, not as effective to interact with but can be faster. Use arcpy.Describe for production code which has performance issues.
Étapes pour reproduire
ID de bogue: BUG-000151318
Logiciel: