Checks & results
In development
Within a record.
Across the system.
Examine individual values, the geometry around them, and the layers that need to agree. Each family helps ask a different question of the data.
What are you looking at?
Choose a relationship to explore the checks behind it.
Schema
The shape of the data.
Required fields, field widths, and missing or blank values.
A condition to examine
A required field is absent from a supplied layer.
What a reviewer considers
Field mapping and the applicable schema definition. Is the field genuinely absent, or present under a different name?
Map the local field, or supply it through the source-data workflow.
Illustrative condition. Actual findings depend on the supplied data and configuration.
MSAG and ALI comparisons use records you supply. A condition that cannot be evaluated is different from a passing result.
Results you can work with
Four outputs.
Different jobs.
The value is what you can do with the result: locate an issue, inspect its full context, share the explanation, and account for the files produced.
See the finding in place.
Spatial result features and a complete finding table connect results to source identifiers. A finding without usable geometry remains in the table with a reason.
For the GIS analyst reviewing locations and relationships.
Keep the full record.
Retain typed finding values and context that may exceed the widths of GIS fields. Inspect the rule, source identity, and review information together.
Inspect the JSON excerptShare a readable result.
Open the run summary without a hosted dashboard. See counts, workflow states, coverage context, and a selection of findings in a single file.
Open the report excerpt (new tab)Account for the files.
A file inventory and integrity information document completed output writing. Interrupted writes retain an incomplete marker for inspection.
Describes output completion, separately from what the data checks found.
Reading a result
Keep the distinctions visible.
A low finding count only means something when you know what was examined.
Severity and human review
Critical, Advisory, Watch, and N/A describe the check’s assessment. Unreviewed, Active, Flagged, and Reviewed describe human review. Reviewed does not mean the source data was automatically fixed.
Mapped findings and table-only findings
Empty or invalid geometry, ambiguous identifiers, and coordinate-system problems can prevent a spatial attachment. The finding remains in the table with the reason.
Findings and evaluation coverage
A finding tells you about an observed condition. Coverage describes what could be examined. Missing dependencies, skipped records, and unknown counts need their own explanation.
A local convention and an external standard
A recorded local exception can affect which findings need attention. It does not rewrite the external standard or establish acceptance by a receiving system.
All check families
A text reference for the conditions above.
Schema
Required fields, field widths, and missing or blank values.
Example: A required field is absent from a supplied layer.
Review: Field mapping and the applicable schema definition. Is the field genuinely absent, or present under a different name?
Domains
Values against applicable code lists, including states, directionals, street types, parity, and one-way codes.
Example: A road centerline contains ZZ in its state field.
Review: The source value, the field mapping, and the 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: Whether the range is reversed or the record needs other local context.
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: Local street layout, legitimate road termini, and the specific condition reported.
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: The address placement, the supplied service boundary, and which authority can resolve a disagreement.
Fishbone
Range-based positions along matching roads, with connector lines exposing placement and matching conditions.
Example: An address point has a long connection to its range-based road position.
Review: The matched street, range, side, address placement, 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: Which community name is authoritative for the task 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: Whether the record is missing, the address representation differs, or the available data is incomplete.
See how the pieces fit your workflow.
Review the local setup, data boundaries, and information that would help start an evaluation conversation.