Zero length geometries are not valid in the geometric network whether they apply to the geometry associated with entire network features or to the geometry associated with a section of complex edge that has mid-span connectivity.
Multiple scenarios can cause the following error:
The geometry for an edge element may not be zero length.
Some scenarios involve editing and others involve reconcile or conflict resolution. All of the scenarios below involve an edge element being associated with a zero length geometry:
- Scenario 1 - Moving multiple junctions, connected to the same edge feature, to the same location. This causes either the edge geometry or subsections of the complex edge geometry to collapse, resulting in a zero length geometry.
- Scenario 2 - Deleting the vertices along a complex edge feature that are coincident with junctions connected at mid-span. The deletion of the vertices removes the segments of the complex edge, but does not delete the junctions. When the vertices are deleted, the junctions snap to the closest vertex of the complex edge feature, which can result in a zero length segment of the complex edge.
- Scenario 3 - Moving a junction feature connected to two complex edge features at mid-span.
- Scenario 4 - During conflict resolution with the Conflicts dialog.
- Scenario 5 - During reconcile, in which the error message is appended to the end of a "The version failed to reconcile" error.
The error is due to the geometry for an edge element collapsing on itself and forming a polyline or geometry with a length of zero. The geometry may correspond to an entire edge feature or to a segment of a complex edge feature.
Solution or Workaround
Depending on the action that caused the error message to be displayed, the solution to the issue may vary.
- Scenario 1 is an example of when the error is legitimate and the edit attempted is not valid for the geometric network. Moving the junctions to the same location can lead to the geometry collapsing into a zero length geometry.
- Scenario 2 can be resolved by either deleting or disconnecting the mid-span junctions prior to deleting the vertices.
- Scenario 3 can be resolved by either running the Rebuild Connectivity tool over the junctions in question or by using the Disconnect command to disconnect one of the junctions prior to the move.
- Scenario 4 may be resolved if it is possible to determine which feature is raising the error by resolving conflicts at a class or feature level. If determined:
If this error is unresolved, contact Technical Support to troubleshoot this issue.
- Use the Disconnect command on the feature prior to resolving the conflict.
- Determine if the feature has inconsistent connectivity and use the Rebuild Connectivity tool over the feature.
- Assess whether the replacement is necessary or if it can be done in the original version following the post.
- Scenario 5 may be resolved if it is possible to determine which feature is raising the error by resolving conflicts at a class or feature level. If determined, use the Disconnect command on the feature prior to reconciling the version.
If this is not successful, the assistance of Technical Support may be required.