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

InfraSpatial Solutions / GIS automation

Know what depends
on your GIS data.

Before changing a feature class or retiring a service, trace the maps and applications that rely on it. Our dependency workflow connects the source data to the people-facing tools it supports.

Real application · synthetic demonstration data

See the application results

01 / The requirement

A layer in one map can serve several workflows.

A request to change an inspection layer starts in a web map. The same source may also feed another service, a public map or a third-party application. The change review needs those connections and the records that establish them.

Start from the exact item

Identify the selected layer, service URL, web map ID or data-source key. Similar titles and partial-name matches need review before tracing.

Follow the right direction

Use “Used by” to find potential consumers of a change. Use “Depends on” to investigate the resources an application requires. Keep sharing relationships separate from runtime dependencies.

Retain the evidence

Carry the relationship record, source and target keys, route and snapshot date into the change review. A connection shows potential exposure; its operational effect still needs testing.

02 / The workflow

From scattered GIS records to a controlled change.

InfraSpatial Solutions brings inventory collection, dependency evidence and operational review into one repeatable process.

GIS dependency and change-review workflow
ArcGIS Online / Enterprise
Items, web maps and applications
ArcGIS Server
Services, manifests and usage
External application register
Maintained service references
  1. 01

    Collect & scope

    Capture accessible records, permissions, scan errors and snapshot time.

    Output: dated inventory
  2. 02

    Connect & check

    Resolve identifiers and relationships; flag duplicates and missing targets.

    Output: dependency index
  3. 03

    Trace the change

    Follow consumers from the selected source or dependencies from an application.

    Output: affected-item routes
REVIEW GATEEnough evidence to plan the change?

Check coverage, unresolved references, ownership and usage context.

NO · RESOLVE GAPS

Investigate & refresh

Confirm missing records and external consumers with owners. Correct the inventory and repeat the trace.

Return to collection and checks
YES · PREPARE VALIDATION

Review & test

Agree the change plan, test affected workflows and record rollback steps. An inventory result alone does not authorize a production change.

Approved change → refresh inventory → compare resultsRetain the change record, relationship evidence and validation results.

The chart describes our delivery process. The application captures below demonstrate the dependency-tracing stage.

03 / Application results

One source. Eight connected items. Every route visible.

What would need review if the Hydrant inspections data source changed? We selected that source in the desktop application and ran an Impact trace through four levels.

8Connected items
2Directly dependent services
3Applications reached
Desktop application showing an impact graph from Hydrant inspections through two services to three consuming applications
The complete impact graph

Two service branches reach web maps, a portal service item and three applications. The graph shows eight distinct relationship links; arrowheads show which item depends on another.

Select the screenshot to inspect it at full size.

Actual desktop application captures using a purpose-built synthetic inventory. All names, identifiers and usage values are fictional, and the demo uses neutral table prefixes and source labels; the application's tracing logic is unchanged.

The three application routes

The following routes summarize the captured impact result. Arrows here read “is used by,” from the selected source toward its consumers.

3 LEVELS · FIELD OPERATIONS

Hydrant inspections → Inspection editing → Inspection field map → Inspection dashboard

2 LEVELS · THIRD-PARTY CONSUMER

Hydrant inspections → Inspection editing → Asset work-order portal

4 LEVELS · PORTAL CONTENT

Hydrant inspections → Public asset reference → Asset reference item → Public asset map → Operations workspace

From a result to its evidence

Verify the furthest application connection.

The Connected Items view places Operations workspace four levels from the source. Opening its relationship evidence exposes the application-to-map record:

Application key
DEMO-APP-B
Web map key
DEMO-MAP-B
Relationship record
LINK-09
Evidence
Application web map reference

This establishes a recorded dependency, the evidence to carry into the change review.

04 / Inventory quality

The application also exposes gaps in the evidence.

The same synthetic run contains 13 inventory items and 12 relationship rows. Its Data Health view identifies three findings for investigation.

1 missing target

A dashboard references a web map absent from the inventory. Check collection coverage and the source configuration before treating it as a broken live application.

1 duplicate relationship

The inspection dashboard-to-map relationship occurs twice. The impact trace reaches the dashboard once; Data Health retains the duplicate finding.

1 unconnected item

Archived survey has no recorded relationships. Confirm collection scope, external consumers and usage context before considering retirement.

05 / Scope and evidence

A practical workflow, with its coverage visible.

This case study demonstrates a Python desktop application for GIS dependency analysis. The captured run follows a source through its consumers, opens the underlying relationship records and checks inventory health using synthetic data.

A trace covers only what the inventory collected, and the documented collection scope excludes private ArcGIS Online content. Collection permissions, missing records, scan failures and snapshot age therefore belong in every impact review.

InfraSpatial Solutions uses this approach to structure GIS change reviews: identify potential consumers, show why they are connected, and make the remaining checks explicit.

Planning a GIS change?

Start with the data source or service you need to change. InfraSpatial Solutions can help define the dependency review and evidence needed for the next step.

Discuss your environment