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.