NG9-1-1 GIS Validation · ArcGIS Pro
Groundtruth 911 Validation Workbench
Run checks locally in ArcGIS Pro, follow findings to their source, and document the decisions your team makes.
For GIS teams responsible for the roads, addresses, and boundaries behind 911.
See the Work From Your Perspective
Choose your role to explore the checks, review process, and technical details most relevant to you.
Inside Workbench
From a Reported Issue
to a Documented Review.
Run checks on local GIS data in ArcGIS Pro. Each finding links to its source record and keeps the check’s assessment separate from a reviewer’s decision.
The data
Road records, address points, and emergency-service boundaries. A source record is one item in that data, such as a particular road segment.
The finding
A condition reported by a check, linked to the record and the value or relationship that needs review.
The review
A reviewer records a decision and reason. The responsible steward makes any source correction in GIS, then an updated copy can be checked.
Where it fits
Review Data
Before It Moves On.
Review local GIS data before it moves through your organization’s delivery process. Workbench gives analysts, GIS managers, and 911 programs a shared record of the check and the review.
01 / Authoritative GIS
Maintain the source.
Maintain roads, addresses, and service boundaries in your authoritative GIS. Reviewers can work from a copy.
02 / Validation Workbench
Check. Review. Recheck.
Run checks and document review decisions. Make corrections in GIS, then check an updated copy.
03 / Existing delivery process
Submit through your program.
Use your existing aggregation, acceptance, and provisioning process. Receiving agencies and systems set their own requirements.
The Workbench addresses local GIS validation and review. It does not operate call routing or replace receiving-system acceptance.
The work after the check
A Finding Is More Useful With the Reasoning.
An analyst needs to know what needs attention. A manager needs to understand the decision. A 911 program may need both when the question crosses organizational boundaries.
Keep the Review.
Check the Updated Data.
- 01 / Supplied copyExamine the data
The Workbench reads the supplied records.
- 02 / Human reviewRecord the reasoning
The finding and decision remain separate facts.
- 03 / Authorized GIS workMake any source correction
The responsible steward edits the source in GIS.
Recheck an updated copy. If the same condition returns, it is Unreviewed again, with the earlier decision available for context.
Recorded Output · Fictional Data
Follow One Record
Through the Review.
Start with a state-code mismatch. Read the finding, record a review, then recheck the same value to see what changes and what stays.
Try the exception example too: change the value or revoke an approval to see how the review queue responds.
Three facts that stay separate
| Severity | Critical The check’s assessment. |
|---|---|
| Review status | Reviewed A person recorded a decision. |
| Current condition | Still present Reviewing a finding does not edit the source value. |
A review can be complete while the data still needs a correction in GIS.
Inputs and Outputs
Your Data Stays Local.
Select local layers in ArcGIS Pro and confirm their field mappings. Workbench writes findings to new result files and leaves your source data unchanged.
Prepare
Choose the Input.
Select local layers and the configuration for your data. Confirm the field mappings before running checks.
Examine
Read the findings.
Review schema, attribute, and spatial findings, including checks against supplied comparison records such as MSAG or ALI.
Continue
Use the Results.
Take spatial results, the full JSON record, or an offline HTML report into your team’s review and correction workflow.
See Workbench in Action.
Watch a finding move through a check, a review decision, and a recheck. Bring your questions about your data and your team’s workflow.