GIS consulting for local government, utilities and engineering firmsServing clients across the United Statesinfo@infraspatialsolutions.com
All projects

InfraSpatial Solutions / Water utilities

Keeping water asset
layers usable
after migration.

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

Project context
Municipal water distribution
Technology
ArcGIS Pro · Enterprise · SQL Server
Technical focus
Asset classification · Domains · Layer definitions
Scope of this case study
Schema review, asset layers and validation planning

01 / The problem

Moving the features was only part of the migration.

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

Domain mismatches

Source and target domain data types did not always agree. Mapping required explicit decisions about codes and values.

Connectivity

Service-line tracing and pipes split at vertical bends required connectivity review.

Meter relationships

Meter-bank identifiers, GPS collection and billing-system relationships had to fit the migration.

Operational workflows

Isolation tracing, editing, publication methods and integrations each need their own acceptance checks.

Practical migration detail / Keeping downstream layers usable

One shared class. Several familiar layers.

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

Find and inspect hydrants

A dedicated hydrant feature class gives maps and exports a familiar asset layer.

02 · Utility Network source

WaterDevice

Resolve the hydrant asset group, then the required asset types within that group.

03 · Downstream layer

Hydrants

A named feature layer with an explicit definition query, appropriate fields, labels and pop-ups.

Filter design · descriptions shown, codes resolved from metadata

Select the intended hydrant assets.

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.

ArcGIS Pro

Configure a usable layer

Use subtype group layers for asset-group organization, or a feature layer with a definition query when the required subset spans specific groups and types.

Web maps

Preserve the filter in the service workflow

Configure the supported service and web-map layer settings, then check the saved filter, fields, labels and pop-ups in the receiving application. Support depends on the publishing route and client.

Data delivery

Export the intended subset

Pass the filtered layer to the export tool, check for unintended selections, and verify the delivered IDs and counts. Reading the raw feature-class path can bypass the layer’s filter.

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 labels are readable. The stored values need checking.

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.

01

Asset type belongs to an asset group

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.

02

The same field can have different rules

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.

03

Legacy text can become a numeric code

The inspected legacy lifecycle field stores text; the target stores numeric coded values. Map their meanings explicitly, including null, unknown and retired assets.

Review itemWhat to inspectWhy it matters downstream
ClassificationSubtype code and label; the asset-type domain assigned to that subtype.Prevents a layer from including unrelated devices or omitting valid assets.
Attribute meaningStored 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 overridesEffective domain and default for the chosen asset group, not only the class-wide field settings.Preserves the relevant editing choices and validation rules.
Delivered schemaDomains, 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 membershipExpected 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

From source schema to dependable asset layers.

Our approach connects each migration decision to a concrete deliverable and an acceptance check.

01Assess the source data and workflows

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.

02Resolve field, domain and model differences

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.

03Load and reconcile the migration

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.

04Define the layers users need

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.

05Validate network workflows

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

What the isolation trace is configured to do

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.

How to check the result

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.

Selected isolation-trace parameters
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"
Selected parameters, not a full configuration. Network paths, attribute names and starting locations are deployment-specific.

03 / Validation plan

Prove one shutdown scenario, end to end.

Test plan

Use a bounded, authorized network extract to test which valves isolate a selected main and which modeled service connections are affected.

TestWhat to checkEvidence to retain
Layer continuityResolve 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 reconciliationAccount for every source asset and relationship, with documented transformations and exclusions.Count report, ID crosswalk and exception list.
Network validationValidate the defined test area; inspect remaining errors and dirty areas before tracing.Validation extent, dated error export and review notes.
Normal isolationCompare the returned isolating valves and service connections with an independently reviewed expected set.Saved starting point, trace settings, result IDs and map.
Valve unavailableChange the relevant valve condition in the test copy and check whether the isolation boundary changes as expected.Before-and-after result comparison and explanation.
RepeatabilityRepeat 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

What this study establishes.

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.

Planning a water network migration?

Work with InfraSpatial Solutions to define your source-to-target mapping, preserve essential asset layers and plan the checks needed for operational readiness.

Discuss your migration