Numéro d’ID de bogue |
BUG-000107358 |
Envoi | August 14, 2017 |
Dernière modification | June 5, 2024 |
S’applique à | ArcGIS for Desktop |
Version trouvée | 10.3.1 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | 7.0 64 Bit |
Statut | Known Limit
Après examen par l’équipe de développement, il a été déterminé que ce problème est lié à une limitation connue du logiciel sur laquelle Esri n’a aucun contrôle. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
The Buffer tools dissolve ALL option actually runs the dissolve first, not second, and internally something is going on with this that is probably causing the slowdown in 10.3. We made an enhancement to this in 10.5.1 which is why you see the performance recover. However, we also made buffer and dissolve much more accurate up to and including 10.5.1 so some of the slowdown you see there as compared to 10.2 is due to better output.
Workaround 1
Run Buffer with dissolve NONE and then run Dissolve on the output of the buffer operation.
This takes seconds for a number of buffer distances I tried using the Planar option.
Workaround 2
Pro only... run using PairwiseBuffer. By default this runs in parallel. For various buffer distances running buffer with the dissolve ALL option it completed in under 1 minute.
Suggestion
I noticed that the x,y resolution of this data is much finer than default x,y resolution for the specified Spatial Reference. This is leading to a much larger storage and processing size, which also will lead to other performance issues with any tool that is used to process this data (for buffer it looks like a 30-40% performance hit over using the default x,y resolution). If the data was recorded with a device that actually had this x,y resolution, I am guessing this performance hit is acceptable to you.
Solution de contournement
Run the Buffer tool with Dissolve set to NONE, and run the Dissolve tool separately.
Étapes pour reproduire
ID de bogue: BUG-000107358
Logiciel: