Once we understand the requirements
that support the mapping of individual
features into the utility network data
model, we can evaluate the current data
against these requirements to determine
where remediation needs to occur.
Esri developed a preconfigured solution
using ArcGIS Data Reviewer that provides
a starting point for this quality control
step. The solution configuration provides
exhaustive checks on the input data but would have to be configured to include the
specific fields and conditions identified in the data modeling step.
An added benefit of having the data mapping document is that it will narrow down
the fields that are fundamentally necessary for a successful migration. These are the
fields that should be prioritized for cleanup. If a field itself is irrelevant to the
migration, why should we spend time fixing it?
A good place to start the QC program is to focus on the fundamental requirements of
the utility network and apply them to the incoming data. There are a few hard and
fast rules that we can start with:
1. Data should be snapped. If migrating from an existing geometric network this
may not be an issue, but for non-networked data, topological coincidence
should be verified and enforced. Develop a snapping strategy utilizing snap
tool and defining environments with snap rules, ranks, and tolerances to
minimize the potential of introducing overlaps into the data.
2. Line segments cannot self-intersect or have complex geometry. Data
Reviewer does a good job here and is a great way to begin the QC journey.
Every time line segments share a vertex (as opposed to an endpoint); an error
will be generated in the utility network. Lines that are self-overlapping or are
multipart are also not allowed. ArcGIS provides many tools to deal with the
errors in this category, including repair geometry, Multipart To Singlepart,
simplify line, etc.
3. Features of the same geometry cannot intersect. This situation occurs when
points features or lines vertexes share the same x,y,z. With regards to lines,
this situation is specific to line vertexes. Line segments crossing without
sharing a vertex or lines connecting at an endpoint are allowed. Although this
configuration is technically not supported in the geometric network, this error
is extremely common in many of the datasets we have seen. Evaluate at the