If you need to translate an ISO 19157-1:2023 geographic data quality report, the first job is to preserve what the dataset was tested against, which features were included, and what the reported quality measures actually mean. A multilingual GIS quality assessment is not simply a list of map errors. It connects a data product specification, an evaluation method, a defined population, measurement results, limitations and the judgement that a particular use may or may not be supported. This practical guide focuses on geospatial data quality translation, positional accuracy, completeness, logical consistency, thematic correctness and the evidence behind those terms.
The 2023 standard provides general requirements for describing, evaluating and reporting geographic data quality. Its public scope does not set universal minimum quality thresholds for every map. A dataset that is adequate for a national overview may be unfit for utility excavation or navigation at street level. When translating a GIS validation report, never turn a measured positional error into a guarantee, a sample statistic into a claim about every record, or a data-quality evaluation into the assertion that a map is objectively accurate for all purposes. Keep the intended application, sampling assumptions and product specification beside the finding.
Quick information: identify the dataset version and spatial reference system; preserve the data product specification and evaluation universe; keep completeness, positional accuracy, logical consistency, thematic accuracy and temporal quality separate; retain sampling methods, denominators, confidence statements and measurement units; distinguish results from thresholds and pass or fail judgements; label hypothetical examples clearly; and refer suitability decisions to the accountable data owner. This is an educational guide to translation, not an authorised reproduction of the full standard or a certification.
What the standard covers—and what this translation guide does not claim
The official ISO catalogue describes a framework for quality components, measures, evaluation procedures and reporting. It applies both to those producing quality information and those deciding whether a geographic dataset is suitable for a specific use. Geographic quality is therefore always relational: evaluated against an identified requirement, using an identified process. The page deliberately does not turn the catalogue abstract into fabricated requirements or invent numerical acceptance limits.
The key practical test is whether GIS analysts, geospatial data publishers, survey contractors, municipal mapping teams, environmental scientists and technical translators can take the same appropriate action after reading the translated report as after reading the original. A translation is not made correct by sounding more confident, using fashionable terminology or removing complex details. It succeeds when readers can distinguish a requirement from a result, a fact from an assumption and a checked finding from a promise. The examples below are deliberately fictional educational exercises, not extracts from the copyrighted ISO standard and not official thresholds.
For the primary scope and edition, consult the official ISO catalogue entry for ISO 19157-1:2023. The normative full text is not reproduced here. A project that requires compliance must work from the licensed standard, the relevant laws and the organisation’s own controlled records. That distinction is especially important when a translated file will be used for procurement, field operations, management decisions or legal communication.
How to read the evidence before translating
Start with the data product specification
A quality result has meaning only relative to a declared requirement such as positional tolerance, completeness of road centerlines or allowed attribute categories. The product specification should identify feature type, spatial extent, reference date, expected attributes and intended application. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
A translated phrase such as "meets the map standard" is too vague when the original cites a particular product specification and a defined test. The translator must preserve the controlled document identifier and revision. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Ask whether two readers using different languages would select exactly the same reference requirement when deciding whether the dataset conforms. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Identify dataset identity, extent and version
A GIS delivery can contain multiple tiles, coordinate reference systems, layers, refresh dates, database snapshots and municipal boundaries. Quality may cover one of these and not the whole enterprise dataset. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
Replacing a file version with a publication date or calling a sampled city tile the complete national dataset overstates coverage. Naming conventions and coordinate codes are identifiers, not prose to translate freely. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Trace each translated conclusion back to an actual layer, release, spatial footprint and temporal snapshot. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Separate dimensions of quality
Completeness, logical consistency, positional accuracy, thematic accuracy and temporal quality answer different questions. A feature may exist but be in the wrong place; an attribute may be correct but out of date; a geometry may be valid but missing a street. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
A fluent translation can collapse all these into "data precision" or "map reliability". That sounds plausible, yet it destroys the diagnostic value and may hide what remediation is required. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Give each dimension its own glossary entry and compare it with the test method, not just with a bilingual dictionary. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Keep the denominator visible
Error rates depend on what is counted. Ten missing hydrants out of one hundred expected hydrants is not the same as ten missing objects out of one thousand visited positions. The reference population and exclusions matter. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
If the source says "10 of 100 reference features omitted", changing it to "10% of submitted features defective" can shift the population and the interpretation even when the percentage is ten. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Repeat the count and denominator in the target language and show their relationship in an independent arithmetic check. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Preserve spatial reference information
Coordinates, datums, axis orders, map projections, units, epoch references and transformation methods affect spatial interpretation. Easting and northing are not interchangeable. Degrees cannot be casually substituted for metres. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
Words such as "local grid", "geographic coordinates", "height above datum" and "projected coordinates" often look routine, but small alterations can shift real-world locations. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Check EPSG identifiers, axis labels, unit codes and any transformation notes against the actual data file and its metadata. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Distinguish measurement and decision
A survey might report a mean error, an RMSE, a percentile, a maximum deviation or a count of outliers. Each statistic answers a different question. A conformity decision depends on both the statistic and the specified rule. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
Translating "RMSE was 0.45 m" as "all points were accurate to 0.45 m" is an incorrect universal claim. Similarly, a confidence expression is not permission to invent a safety margin. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Require the numerical term, sample size, comparator and decision criterion to remain present if the source contained them. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Handle reference data and ground truth carefully
A comparison dataset may itself contain uncertainty. Field-verified points, authoritative mapping, imagery interpretation and a third-party database have different provenance and temporal currency. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
Calling every comparator "ground truth" can imply a level of certainty not substantiated by the original method. The translator should preserve the source’s word for the benchmark and disclose its limitations. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Look for documentation of the comparator, acquisition date, quality class and whether the same reference was used for development. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Report limitations without rhetorical improvement
A quality report may mark a result conditional, incomplete, preliminary or unsuitable for a particular workflow. Those labels prevent overstating knowledge. The first question for a translator is not which dictionary synonym sounds elegant. It is which subject, event, measurable feature or controlled document the phrase actually points to. A reader working in another language needs the same boundaries before drawing conclusions. In geographic data quality and GIS evaluation, changing the reference object can make an otherwise grammatical paragraph misleading.
Promotional rewriting often removes caveats, changes "may" into "will" or merges assessment findings with the data supplier’s marketing claims. That is not faithful technical translation. This kind of change is difficult to catch through spelling or grammar review because the target sentence can sound polished. Compare the statement to its underlying table, annex, diagram or approved record. Keep the distinction between what the source explicitly establishes and what a reviewer might infer after further investigation.
Reconstruct the actual decision the recipient could make and ensure the target text permits no stronger conclusion than the source. If the answer depends on data not supplied in the source, preserve the uncertainty rather than filling the gap with professional-sounding speculation. A short translator note or a question to the document owner often does more to protect a global reader than an unsupported sentence added for fluency.
Controlled terminology: words that change the decision
The glossary below is not a complete bilingual dictionary and should not be treated as an official ISO terminology list. It is a decision-oriented explanation of terms frequently encountered when translating geographic data quality and GIS evaluation reports. The safe translation can differ across jurisdictions and target languages; the method is to protect the meaning demonstrated by the source, not to force one English expression into every document.
Data quality
Meaning in context: Degree to which specified data characteristics meet a stated need or requirement; not an abstract guarantee that a map is always reliable. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Rendering it as universal accuracy without its declared use or product specification. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Preserve the specified quality dimension, reference requirement, evaluation date and relevant user purpose. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Data product specification
Meaning in context: The defined description of the dataset that says what is supposed to exist and how it should behave. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Replacing its identifier with a generic phrase like cartographic standard. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Retain its version, scope and reference, then translate its descriptive label without changing the controlled identifier. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Quality measure
Meaning in context: A formal way of quantifying or reporting a particular quality characteristic under stated conditions. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Treating a named measure as an informal opinion or changing the measuring population. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Preserve the measure name or code, units, sample base and evaluation procedure. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Evaluation method
Meaning in context: Procedure and data used to obtain a reported quality result; the choice of method affects comparability. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Calling manual review a full independent field verification. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Translate the exact examination, sampling or comparison activity and its stated limitations. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Completeness
Meaning in context: Extent to which expected geographic features or attributes are present in the assessed scope. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Confusing missing entities with inaccurately located entities. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Keep omission and commission language distinct and retain reference inventory. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Omission
Meaning in context: An expected record, feature or property absent from the dataset relative to the declared requirement. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Describing a wrong attribute value as a missing feature. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Explain which reference item was expected and where its absence was observed. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Commission
Meaning in context: A feature or attribute included when it should not be under the product specification or reference set. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Translating an extra record as a missing record or an ordinary addition. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Preserve the direction of the error and the membership rule used by the evaluator. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Logical consistency
Meaning in context: Adherence to stated rules about structure, relationships, domains, topology or format. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Treating a self-intersection as proof that the mapped location is wrong. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Name the rule violated and separate structural validity from real-world accuracy. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Topological consistency
Meaning in context: Conformity of geographic relationships such as connectivity, adjacency, overlaps or gaps to defined rules. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Claiming a valid geometry also proves roads connect in reality. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Keep the topology rule, geometry type and whether the checking was automated. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Positional accuracy
Meaning in context: Closeness of spatial positions to positions accepted as references under the assessment approach. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Turning a sampled error metric into a guaranteed per-feature tolerance. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: State reference, metric, dimensionality, sample size and uncertainty when present. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Absolute positional accuracy
Meaning in context: Comparison of feature coordinates with an external reference position. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Confusing it with internal relative alignment among features. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Preserve the external comparator and the relevant coordinate reference frame. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Relative positional accuracy
Meaning in context: Correctness of positions relative to other features in the defined spatial relationship. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Translating it as a universal global-coordinate guarantee. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Explain which features and relative geometry are being compared. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Thematic accuracy
Meaning in context: Correctness of non-spatial classifications and attributes against a declared reference. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Replacing a category error with a spatial alignment error. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Keep attribute names, class definitions, permissible values and confusion-matrix counts. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Classification correctness
Meaning in context: Whether features have been assigned the appropriate class under the classification scheme. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Simplifying class labels so that distinct source categories merge in the target language. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Keep codes unchanged and give a controlled translation for the category description. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Temporal quality
Meaning in context: Correctness and validity of time-dependent information such as event dates and update status. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Treating the age of a file as proof that every record has a matching observation date. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Maintain event, observation, revision, publication and effective dates separately. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
RMSE
Meaning in context: Root mean square error; a statistic sensitive to larger squared deviations in a sample. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Calling RMSE the maximum observed error or the arithmetic mean of absolute distances. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Preserve the formula label, numeric unit, axis convention and sample definition. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Outlier
Meaning in context: Observation identified as unusually discrepant under a specified detection or treatment rule. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Silently removing large errors or describing all outliers as corrupted records. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Record the detection rule and whether the result includes or excludes flagged observations. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Sample
Meaning in context: Subset of the defined evaluation population used to estimate quality. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Implying that a sample-based estimate checked every feature in the database. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Keep sample size, selection strategy and evaluated population visible. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Confidence statement
Meaning in context: Expression about uncertainty or reliability of an estimate under declared statistical conditions. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Replacing it with a warranty that all geographic locations meet a threshold. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Translate probability wording, confidence level and interval boundaries exactly when provided. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Conformance
Meaning in context: Finding that a specified requirement or rule has been met under a defined evaluation. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Presenting conformance as freedom from every possible defect. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Link the verdict to a concrete rule, dataset version and evidence source. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Lineage
Meaning in context: Information about a dataset’s sources, processes and transformations that help readers interpret provenance. A careful translator should first see where the term sits in a sentence, table or process and then decide whether the target-language expression preserves the same subject and predicate. An abbreviation can be retained when the audience recognises it, but the first use should be explained clearly.
Typical mistranslation: Translating transformation history as a quality score. This mistake matters because it changes the reader’s understanding of what is established, required or merely possible. A translator who catches it early can also check adjacent numbers, dates and qualifiers before the mistake spreads to captions, summaries and dashboards.
Safer handling: Preserve input sources, processing actions, dates and responsible entities. In bilingual quality assurance, compare the target term with at least one complete original sentence and the corresponding evidence record. If the source uses the same word in several technical senses, create distinct context-specific entries rather than choosing one universal equivalent.
Worked translation cases: source, error, repair and proof
These are hypothetical teaching examples designed to expose common semantic failures. They are not official examples, mandated numerical limits, verified site observations or quotations from ISO 19157-1:2023. Each case follows an incident-like sequence: what the source says, how translation might change it, what a faithful reader should understand, and the independent document that would settle uncertainty.
Missing water-valve points
Situation: In a hypothetical utility layer, 14 of 280 valves documented in a field register are absent from the delivery. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The draft calls this fourteen incorrect coordinates and labels the failure positional inaccuracy. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Translate it as omission of fourteen expected features in the assessed scope; do not invent their locations. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Match the reference register, population 280, and omission count 14 before calculating any rate. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Extra road segments
Situation: A road-centerline dataset contains six segments with no counterpart in the agreed reference inventory. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: A reviewer calls them six new roads without demonstrating they exist on the ground. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Report commission relative to the defined inventory rather than asserting an error in real-world road construction. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Preserve inventory date, six record identifiers and the rule for treating unreferenced geometry. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Roundabout topology
Situation: Four connected roads appear visually joined, but a routing engine sees one unconnected endpoint. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: A translator replaces topology failure with a statement that the physical road is missing. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Describe a connectivity violation in the digital network while retaining any uncertainty about actual road access. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Compare node identifiers and snapping tolerance; do not infer field conditions from a screen image alone. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Coordinate axis reversal
Situation: An export lists coordinates as northing/easting but the target table relabels them easting/northing. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: Both values look like plausible numbers, making the mistranslation difficult to spot. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Retain field order and coordinate reference system semantics; translate labels only after checking actual metadata. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Round-trip a sample point in GIS and verify its mapped location. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Boundary snapshot
Situation: A municipal boundary file was valid as at 1 January in a specific year, but a later release contains changes. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The target omits the as-at qualifier and implies the boundary is legally current today. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Keep the effective date and clarify that a later legal or administrative update may exist. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Read the source’s publication and validity fields separately. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Land-cover classes
Situation: One record uses woodland while another uses shrubland in a coded classification. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The translation collapses both into green area because that is colloquial and shorter. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Keep the codes and distinct class definitions; give clear readable equivalents in explanatory text. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Compare the translated legend with the data dictionary and sampled records. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Positional RMSE
Situation: A fictional sample of surveyed control points yields 0.42 metre planimetric RMSE. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The draft promises every mapped point lies within 42 centimetres of reality. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: State the sample statistic, its unit and the assessed population without making a maximum-error promise. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Compare metric name, horizontal dimensions and supporting sample report. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Reference imagery age
Situation: A quality assessor compares a newly surveyed parcel layer against imagery captured three years earlier. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The target says the parcel layer is wrong whenever its boundaries disagree with the old image. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Preserve the comparator date and acknowledge possible genuine change between observations. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Review acquisition dates and evidence notes before assigning error direction. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Road name spelling
Situation: A street name differs from the authoritative name registry in twelve records. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The translator treats each discrepancy as a spatial error because it concerns a map. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Classify it as an attribute or thematic issue under the specified register, not position. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Verify spelling policy, official-language forms and registry version. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Attribute null values
Situation: The field "surface_type" is null for 39 lanes in a transport database. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The target equates null with unpaved, turning missing information into a physical classification. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Translate null as an unrecorded or unavailable attribute, as defined by the data model. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Examine allowed domain values and any separate unknown code. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Sample exclusion
Situation: Three survey points are excluded because their reference coordinates were unreliable. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The summary quietly drops their existence, so recipients believe every selected point was analysed. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Preserve the count, justification and statistical treatment of excluded observations. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Reconcile selected, excluded and analysed sample totals. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Tile-based assessment
Situation: Two map tiles pass a geometry validation; neighboring tiles were not in scope. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: A marketing version says the nationwide mapping product has passed. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Retain the two tile IDs and the limitation to the tested delivery. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Check the assessment boundary and list of delivered files. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Height datum
Situation: Elevation values are measured against a national vertical datum rather than mean sea level in an informal sense. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: Translation substitutes sea level and loses the controlled vertical reference. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Keep datum identifier, units and any geoid conversion explanation. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Inspect the coordinate system metadata and reported vertical transformation. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Quality threshold
Situation: An evaluation reports 96 percent conformity where the product specification requires at least 95 percent. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The target changes it into a claim of perfect suitability for every downstream operation. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: State the measured percentage and the named acceptance rule; contextual suitability remains a separate decision. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Recalculate the ratio and consult the specific specification revision. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Use decision
Situation: A dataset passes a regional planning use but is not suitable for on-site construction staking. Before translating, identify the reporting unit, whose observation is involved and the time or scenario to which the source refers. A number can remain numerically identical while its meaning changes if the translator swaps the denominator, population, event status or reference date.
The tempting but wrong reading: The translation drops the use restriction because it sounds negative. Fluent prose is not a defence here: the target sentence would invite a different interpretation or decision. Ask what an uninformed recipient would assume was measured, completed or verified if this wording appeared alone in a report summary. The answer reveals why context must travel with terminology.
Correct translation decision: Keep the explicit fit-for-purpose boundary; technical honesty makes the report more valuable. Keep the original record’s strength of assertion and its technical distinctions. An explanatory note may be appropriate when the target language has no compact exact equivalent; that note should explain an ambiguity rather than silently revise the finding.
Evidence check: Trace the acceptance memo to the product requirement and responsible reviewer. If this supporting material is unavailable, keep the uncertain element open for clarification. Do not make up a source reference, approval status or numerical limit. This is especially important when the translated document is sent beyond the producing organisation to regulators, suppliers, contractors or the public.
Ten-stage practical review before release
1. Read the source purpose
Identify exactly what question the document answers and who relies on it; preserve the same decision purpose in the translation. If a heading is ambiguous, use the source’s definitions and appendix references rather than guessing from familiar everyday vocabulary. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
2. Lock the referenced edition
Verify the complete standard number, part and year in the source. If an amendment is identified, preserve that relationship instead of silently replacing the edition or creating a fictitious new issue. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
3. Create the bilingual term ledger
List recurrent technical terms with definitions from the current source context. Keep abbreviations, coded values and controlled labels stable, while allowing natural prose to remain readable in the target language. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
4. Map scope, exclusions and ownership
Write down the entity, date range, dataset or operational boundary, responsible reviewer and exclusions. These details prevent a result about one subpopulation or one location from becoming a sweeping promise. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
5. Protect numbers before prose revision
Extract units, decimal separators, percentages, dates, identifiers, negative signs and denominators into an independent checklist. A precise sentence with one wrong number remains an inaccurate technical record. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
6. Mark claim strength
Distinguish proposal, requirement, plan, observation, estimate, investigation, approval and verified conclusion. Underlining verbs in both languages often exposes accidental upgrades from uncertainty to certainty. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
7. Translate tables with definitions
For each table, record the meaning of its headings, unit, measurement basis, comparison point and missing-value code. Read footnotes before shortening labels for space. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
8. Work through the cases
Select at least three high-consequence records and reproduce their interpretation in ordinary language. If the target wording changes the recipient’s likely decision, the translation needs correction. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
9. Run independent QA
Compare all figures, named entities, technical symbols, section identifiers, dates, ranges and source references with the original. Ask a bilingual subject reviewer to inspect the highest-risk passages. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
10. Record open questions and release version
Resolve source ambiguities with the document owner. If unresolved, clearly document the ambiguity rather than invent facts; retain approvals, revision identity and glossary decisions with the deliverable. For a ISO 19157-1:2023 file, connect the check to the actual evidence and the decisions a recipient would make. Mark discrepancies in a bilingual change log with a source location, proposed resolution, reviewer and status. The objective is to ensure that a correction remains traceable when a report or spreadsheet is updated later.
Frequently asked questions
Does ISO 19157-1:2023 set one universal acceptable map error?
No. Its publicly described framework supports describing and evaluating quality, but acceptable values depend on a particular product specification and intended application. A translator should not invent a universal spatial tolerance. The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
Should EPSG codes be translated?
Keep the codes unchanged. Translate the accompanying names only if a recognised equivalent exists and do not change axis order, datum or units. The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
Can a GIS report describe all errors as inaccurate locations?
No. Missing features, extra features, incorrect attributes, invalid relationships and outdated dates are different findings with different remedies. The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
Does a 0.5 metre RMSE mean all features are within 0.5 metre?
No. RMSE summarizes squared deviations over a sample. It is not the same as the maximum observed error or an absolute guarantee. The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
How should the translator handle unclear reference datasets?
Record the uncertainty, ask the assessor which authoritative source was used, and avoid substituting a guessed "ground truth". The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
Can machine translation handle a data-quality report?
It may help draft ordinary prose, but metadata, quantities, coded terms, statistics and conformance findings need bilingual technical checking against the original source and data files. The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
What is the most important final review?
Confirm that the target-language reader knows exactly what was evaluated, what result was found, what requirement applied and what remains unproven. The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
How does this relate to broader translation learning?
Use the existing master translation guide for cross-language principles and vocabulary resources for term learning. This specialist article covers only geographical quality evidence. The practical rule is to retain the original document’s scope and evidence. If a reader needs a stronger conclusion, it must come from authorised analysis rather than from a translator’s unrecorded assumption.
How this specialist guide connects to language learning
For the general principles of meaning transfer, read Master Art of Translation | The Complete System for Moving Meaning Between Languages. For conceptual language and words whose meanings shift by domain, use the existing Vocabulary Learning Hub. For how English clauses, modifiers, claims and logical relationships work, see How English Works | Translation and Meaning Across Languages. Those are the established conceptual owners. This article adds a narrow worked application to geographic data quality and GIS evaluation; it does not establish a new master hub or replace them.
Source and responsibility note
Primary standard information: ISO 19157-1:2023 — ISO catalogue. The standard’s text is copyrighted. The terminology explanations and fictional worked cases here are independent educational interpretation and must not be treated as the normative standard. Before using a translation for professional safety, accreditation, legal, financial or regulatory purposes, compare it with the actual source edition and obtain competent domain review.