Resolution of input strings and positions to reference records with scored outcomes, and the tests, anomalies and defect handling that keep the register trustworthy.
geocoding-and-matching
Geocoding and address matching outcomes
The normalisation and parsing that precede matching, the reference dataset version matched against, the score and type of a match, the threshold that separates automatic acceptance from review, and the explicit representation of ambiguity, partial matches and interpolation.
Questions
- What normalisation and parsing steps precede matching, and against which reference dataset version was the match run?process
Expected answer
- Normalisation rule set and version
- Parser and its component output
- Reference dataset identifier and version
- What match score, match type and matched component set does the operation return?measurement
Expected answer
- Match score
- Match type code
- Components matched and unmatched
- Which score threshold accepts a match automatically, and what routes a candidate to human review?decision
Expected answer
- Acceptance threshold
- Review trigger conditions
- Reviewer role and turnaround
- Is the result stored as an attribute of the address or as a separate derived observation with its own timestamp and inputs?provenance
Expected answer
- Storage form decision
- Observation timestamp
- Inputs and engine version
- How are ambiguous, partial and interpolated results represented rather than silently resolved to one answer?exception
Expected answer
- Candidate set with scores
- Interpolation flag and method
- Disclosure to the consumer
Artifacts
- Geocoding or matching result recordThe reproducible record of one matching run: input, normalisation applied, reference dataset version, engine version, candidates, chosen result, score and timestamp.
quality-tests-and-anomalies
Quality tests, anomaly status and defect handling
The tests a record must pass — syntax, completeness, conformity to the governing reference system, duplication and positional containment — the anomaly status recorded when it fails, whether an anomalous address remains usable, and how defects are notified and resolved with retained evidence.
Questions
- Which quality tests does this record pass or fail, and against which rule set version were they run?validation
Expected answer
- Test identifiers and definitions
- Pass or fail per test
- Rule set version
- What anomaly status applies when the address is not correct under its governing reference system, and may it still be used?quality
Expected answer
- Anomaly status value or explanatory note
- Usability decision
- Consumers warned
- Who is notified of a defect, within what period must it be resolved, and what status applies meanwhile?process
Expected answer
- Notified role or party
- Resolution deadline
- Interim record status
- What evidence is retained to show that a test was executed against a specific record version?evidence
Expected answer
- Test execution timestamp
- Record version tested
- Executor and tooling version
- Is the validation rule set published so that consumers can check records before submitting them?interoperability
Expected answer
- Published schema or rule set location
- Publication licence
- Version alignment with the register
Artifacts
- Quality and conformance test reportThe published outcome of running the declared test suite over a register or delivery, listing measures, failures, anomaly counts and the record versions and rule set versions involved.
quality-elements-measures-and-reporting
Quality elements, measures and reporting
ISO 19160-3 is a profile of ISO 19157 that establishes data quality elements and measures for address data, procedures for reporting, and guidelines for use. Elements include completeness, logical consistency, positional accuracy, temporal quality, thematic accuracy and usability. The standard does not define minimum acceptable quality; fitness depends on use.
Questions
- Against which dataset or record scope, product specification and intended use was quality evaluated?measurement
Expected answer
- quality-scope
- product-specification
- intended-use
- What completeness, logical consistency, positional accuracy, temporal quality, thematic accuracy and usability results were obtained?measurement
Expected answer
- completeness-result
- logical-consistency-result
- positional-accuracy-result
- temporal-quality-result
- thematic-accuracy-result
- usability-result
- When was the evaluation performed, by which method, and is the result still current relative to subsequent updates?temporal
Expected answer
- evaluated-at
- evaluation-method
- evaluator
- currency-flag
- Does the consumer impose a minimum quality threshold that ISO 19160-3 itself does not define, and is that threshold recorded as a local constraint?constraint
Expected answer
- local-threshold
- pass-fail
- constraint-id
Artifacts
- Address quality reportEvaluation results against ISO 19160-3 elements for a stated scope and use