Numéro d’ID de bogue |
BUG-000112461 |
Envoi | March 15, 2018 |
Dernière modification | June 5, 2024 |
S’applique à | ArcGIS Runtime SDK |
Version trouvée | 100.2.1 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | 10.0 64 Bit |
Statut | Will Not Be Addressed
L’équipe de développement a examiné le problème ou la demande et a décidé qu’ils ne seraient pas traités. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
If the deconfliction strategy is unspecified in the labeling definition for the layer, then ArcGIS Runtime will default to deconfliction strategy option static to ensure best performance. In static mode, the API will try the specified/default location (e.g. above center) and if the label cannot be placed on the view at that location due a conflict with an existing feature or label, that label will not be placed on the view. By contrast, ArcGIS Desktop (ArcMap and Pro) defaults to a value of Best Position. That means multiple positions will be tried to determine if each label can be placed and then not placed if no viable position is found. The deconfliction strategy value is persisted in the rendering information in the mobile geodatabase for layers when published from ArcGIS Pro to ArcGIS Online, to ArcGIS Enterprise/Portal, or as a Mobile Map Package. If the label deconfliction strategy is undefined, it is possible via the API to modify the label definition for feature layers to set/override the deconfliction strategy property. Label definitions are currently specified for FeatureLayers via JSON. For more information see https://developers.arcgis.com/net/latest/wpf/guide/add-labels.htm.
Étapes pour reproduire
ID de bogue: BUG-000112461
Logiciel: