| Numéro d’ID de bogue |
BUG-000122795 |
| Envoi | June 3, 2019 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcSDE/Enterprise Geodatabase |
| Version trouvée | 10.2.1 |
| 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
Unfortunately this is a known limitation of geometric network, and more specifically logical networks. Since the geometric network maintains a live connectivity graph (via the logical network) as edits are performed features snap together. This snapping can occur in two ways:
1. The user, via rubber banding in ArcMap, physically moves a single feature, but can see the other features also move to the new location based on their connectivity.
2. The user uses a tool which does not show the snapping (such as the vertex editing tools) and the logical network behind the scenes maintains the geographic coincidence of those features which the network identifies as connected.
In the case of a geometric network having corrupted (inconsistent) connectivity, where features are not coincident but the logical network has connectivity between them - the result of an edit to any feature results in the connected features snapping to the new location. The logical network is unaware of the specific editing process that resulted in this internal snapping of edges. Therefore, this snapping is not blocked because it would, in actual fact, end up preventing the editing of related features altogether.
Étapes pour reproduire
ID de bogue: BUG-000122795
Logiciel:
- ArcSDE/Enterprise Geodatabase