Checks & results

Demos by Request

Within a Record.
Across the Map.

Check individual values, inspect geometry, and compare related layers. Explore each check family to see what it examines and how to review its findings.

Explore the Checks

What Do You Need to Check?

Choose a group below, then select a check family for an example.

ZZ

Within a record

Are the required fields present? Are their values valid and consistent?

Across the map

Do roads connect, and do addresses agree with roads and service areas?

Against other records

Do GIS values agree with your MSAG and ALI records?

Schema

The Fields Your Data Needs.

Required fields, field widths, and missing or blank values.

Example Finding

A required field is absent from a supplied layer.

What to Review

Check the field mapping and applicable schema. Is the field missing, or does it use a different name?

Required fieldMissing

Map the existing field, or add the missing field in your GIS workflow.

Illustrative example. Results depend on your data and configuration.

MSAG and ALI comparisons need the records and related GIS layers you supply. The report distinguishes checks that could not run from checks that found no issue.

Result Files

Four Outputs.
One Review Workflow.

Get spatial results for GIS, a complete JSON record, a readable report, and a receipt of the files written.

Geodatabase

Locate the Finding.

Map findings where usable geometry is available. A complete table retains every finding and its source identifier, including results that cannot be placed on the map.

For reviewing locations and spatial relationships in GIS.

JSON

Keep the Detail.

Keep full finding values, rule references, source identifiers, and review context, including values that exceed GIS field widths.

Inspect the JSON excerpt
Offline HTML

Share a Readable Report.

Open the run summary offline. A single file brings together counts, review statuses, check coverage, and selected findings.

Open the report excerpt (new tab)
Output receipt

Know Which Files Were Written.

The receipt lists the output files and integrity information. If writing is interrupted, an incomplete marker identifies the unfinished output.

This records whether output writing finished, separately from what the data checks found.

Reading the Results

Read the Results in Context.

Finding counts are useful when you also know what ran, what could be checked, and what still needs review.

Severity and Review Status

Critical, Advisory, Watch, and N/A describe the check’s assessment. Unreviewed, Active, Flagged, and Reviewed track human review. Marking a finding Reviewed does not edit the source data.

Findings on the Map and in the Table

A finding may stay in the table when geometry is empty or invalid, an identifier is ambiguous, or the coordinate system prevents a map location. The table records the reason.

Findings and Check Coverage

A finding describes an issue the check identified. Coverage shows what the run could examine, including missing inputs, skipped records, and unknown counts.

Local Conventions and External Standards

A documented local convention can change which findings appear in the attention queue. It does not change the external standard or a receiving system’s acceptance requirements.

Complete Check Reference

The check families, example findings, and questions to consider during review.

Schema

Required fields, field widths, and missing or blank values.

Example: A required field is absent from a supplied layer.

Review: Check the field mapping and applicable schema. Is the field missing, or does it use a different name?

Domains

Values compared with applicable code lists, including states, directionals, street types, parity, and one-way codes.

Example: A road centerline contains ZZ in its state field.

Review: Compare the source value with its field mapping and configured domain.

Attributes

Identifiers, range order, parity, lifecycle dates, and coordinate attributes compared with geometry.

Example: A road segment’s from-address is greater than its to-address.

Review: Check whether the range is reversed or has a valid local explanation.

Topology

Disconnected endpoints, duplicate or self-intersecting roads, and spatial gaps or overlaps between relevant boundaries.

Example: Two road endpoints that should connect are separated.

Review: Check the reported location against the street layout, including legitimate road ends.

Cross-layer

Address points against matching roads, ranges, public safety answering point (PSAP) boundaries, and law, fire, or EMS coverage.

Example: An address point lies outside a supplied EMS boundary.

Review: Compare the address location with the service boundary, then identify who can resolve the discrepancy.

Fishbone

Address locations compared with range-based positions on matching roads, using connector lines to show the relationship.

Example: An address point has a long connection to its range-based road position.

Review: Check the matched street, address range, road side, point location, and geometry.

MSAG

Supplied Master Street Address Guide records: required values, range order, parity, emergency service numbers (ESNs), overlaps, and centerline agreement.

Example: A guide entry’s community differs from the matching road record.

Review: Confirm the authoritative community name and whether a documented alias applies.

ALI

Supplied Automatic Location Identification records against address points, centerline ranges, required values, and communities.

Example: An ALI address cannot be matched to a supplied address point.

Review: Look for a missing record, a different address format, or incomplete data.

Put the Workbench to Work.

See the local setup, inputs, result files, and roles involved in using the Workbench.