Editing a corrupt geometric network feature should not alter the geometry of a line feature in another feature geometry in a different geographic location.
最後に公開された状態: September 11, 2019ArcSDE/Enterprise Geodatabase
不具合 ID 番号
BUG-000122795
送信されました
June 3, 2019
最終更新日
June 5, 2024
適用対象
ArcSDE/Enterprise Geodatabase
見つかったバージョン
10.2.1
ステータス
Known Limit
開発チームによる確認後に、この問題が、Esri の管理の範囲外にあるソフトウェアの既知の制限に関するものであると判断されました。 問題の「参考情報」セクションに、さらに詳細な説明が示されていることがあります。
参考情報
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.