Domain mismatches
Source and target domain data types did not always agree. Mapping required explicit decisions about codes and values.
InfraSpatial Solutions / Water utilities
Hydrants, valves and mains still need to work as familiar layers when the data moves into shared Utility Network classes. InfraSpatial Solutions examines the schema, filters and domain decisions that keep those layers useful in maps, applications and data deliveries.
From the principal's project experience · generalized schema pattern
01 / The problem
The existing water data supported network tracing, inspection and maintenance workflows. The migration also had to account for meter information and a separate asset-management integration.
A straight field-to-field transfer was not enough: coded values differed, connectivity needed review, and editing and publishing workflows had to be evaluated alongside the data model.
Migration considerations
Source and target domain data types did not always agree. Mapping required explicit decisions about codes and values.
Service-line tracing and pipes split at vertical bends required connectivity review.
Meter-bank identifiers, GPS collection and billing-system relationships had to fit the migration.
Isolation tracing, editing, publication methods and integrations each need their own acceptance checks.
Practical migration detail / Keeping downstream layers usable
A web map may still need “Hydrants” or “Water mains” after those assets move into shared Utility Network classes. The layer definition has to preserve the intended asset set.
Examples use generalized asset labels and standard Esri concepts.
01 · Legacy layer purpose
A dedicated hydrant feature class gives maps and exports a familiar asset layer.
02 · Utility Network source
WaterDeviceResolve the hydrant asset group, then the required asset types within that group.
03 · Downstream layer
A named feature layer with an explicit definition query, appropriate fields, labels and pop-ups.
Filter design · descriptions shown, codes resolved from metadata
Asset group = hydrant group; asset type = approved hydrant types; lifecycle = the statuses required by this layer.
The check that matters
Distinguish the hydrant device from a hydrant assembly, a hydrant service line or a flushing device. Similar labels do not establish the same asset role.
Interactive explanation of layer design. Switching examples does not query the geodatabase.
A display filter is not an export rule. It controls drawing. A definition query limits the features available through that layer. A standalone feature export also does not carry the full Utility Network’s tracing behavior.
Schema findings / Domains and subtypes
The inspected target uses asset groups as subtypes and asset-type domains assigned within those subtypes. A field-level domain list alone misses part of the model.
Resolve the asset-type domain for the selected group. Build the rule from the class, group and type together; an asset-type value by itself is not a complete classification.
In the inspected line schema, mains and service lines have different material and diameter domains. Subtype assignments and defaults must be reviewed alongside the field definition.
The inspected legacy lifecycle field stores text; the target stores numeric coded values. Map their meanings explicitly, including null, unknown and retired assets.
| Review item | What to inspect | Why it matters downstream |
|---|---|---|
| Classification | Subtype code and label; the asset-type domain assigned to that subtype. | Prevents a layer from including unrelated devices or omitting valid assets. |
| Attribute meaning | Stored code, description, data type, units and approved source-to-target mapping. | Prevents text-to-number conversions and label changes from altering the meaning of a record. |
| Subtype overrides | Effective domain and default for the chosen asset group, not only the class-wide field settings. | Preserves the relevant editing choices and validation rules. |
| Delivered schema | Domains, subtypes and defaults in the exported geodatabase; explicit code-description fields for flat formats. | A successful export does not establish that all schema behavior survived. |
| Feature membership | Expected asset IDs against the filtered output, with exceptions and snapshot dates recorded. | Equal counts alone cannot prove that the old and new layers represent the same assets. |
Verified here: class structure, subtype definitions, domain assignments and stored field types in local copies.
02 / Technical approach
Our approach connects each migration decision to a concrete deliverable and an acceptance check.
Inventory the source classes, coordinate systems, identifiers and workflows that depend on them. Identify the layers needed for inspection, maintenance, web maps and data delivery.
Deliverable: Source inventory and a list of downstream layer requirements.
Map source fields and values to the target class, asset group and asset type. Resolve subtype-specific domains, defaults, units and unmatched values before loading.
Deliverable: Source-to-target mapping and an exception list for unresolved values.
Account for loaded, rejected and intentionally excluded records, including one-to-many transformations. Compare asset identifiers as well as counts.
Deliverable: Loading log, identifier crosswalk and reconciliation report.
Build named layers from approved group/type combinations and lifecycle criteria. Configure fields, labels and pop-ups; verify saved filters and exported schema in the receiving application.
Deliverable: Layer definitions, saved layer files and delivery checks.
Validate the defined network extent, review connectivity and subnetwork configuration, then compare isolation results with an independently reviewed expected asset set.
Deliverable: Topology report, trace settings, expected results and recorded exceptions.
Trace configuration example
A named isolation trace makes its settings explicit. These selected arcpy.un.AddTraceConfiguration parameters show the settings an isolation trace for this workflow needs. The filter barrier stops the trace only at isolating devices that are operable, so it runs past an inoperable valve to the next one that can be closed.
Run that configuration at a known main segment, inspect the returned valves and isolated features, and compare them with an independently reviewed expected result. Then mark a relevant valve inoperable in a test copy and check whether the boundary changes as expected.
trace_config_name = "Valve Isolation Trace"
trace_type = "ISOLATION"
domain_network = "Water"
tier = "Water System"
include_barriers = "INCLUDE_BARRIERS"
validate_consistency = "VALIDATE_CONSISTENCY"
filter_barriers = Category IS_EQUAL_TO "Isolating"
AND Operable status IS_EQUAL_TO "Operable"
include_isolated_features = "INCLUDE_ISOLATED_FEATURES"03 / Validation plan
Use a bounded, authorized network extract to test which valves isolate a selected main and which modeled service connections are affected.
| Test | What to check | Evidence to retain |
|---|---|---|
| Layer continuity | Resolve the asset-group, asset-type and lifecycle filters; compare the resulting assets with the intended legacy layer. | Filter definitions, source-to-target ID comparison, saved layer and export-schema checks. |
| Source-to-target reconciliation | Account for every source asset and relationship, with documented transformations and exclusions. | Count report, ID crosswalk and exception list. |
| Network validation | Validate the defined test area; inspect remaining errors and dirty areas before tracing. | Validation extent, dated error export and review notes. |
| Normal isolation | Compare the returned isolating valves and service connections with an independently reviewed expected set. | Saved starting point, trace settings, result IDs and map. |
| Valve unavailable | Change the relevant valve condition in the test copy and check whether the isolation boundary changes as expected. | Before-and-after result comparison and explanation. |
| Repeatability | Repeat the same scenario on the same data and configuration; explain any differences. | Data version, tool versions, run log and result comparison. |
A trace identifies modeled connectivity. Operational shutdown decisions also depend on verified asset conditions and utility procedures.
04 / Study scope
The completed schema review establishes the shared class structure, subtype definitions, domain assignments and field types used in these examples. Feature-level reconciliation, export and web-map checks, and network traces are planned validation work, set out above; no completed migration or operational acceptance is claimed here.
Work with InfraSpatial Solutions to define your source-to-target mapping, preserve essential asset layers and plan the checks needed for operational readiness.