Translate | ISO 19112:2019 Place Names, Gazetteers, Geographic Identifiers and Map References
Translating place names for a map is harder than changing a spelling. A city can have an official local name, an established name in English, a historical name and several settlements elsewhere with the same label. ISO 19112:2019 helps explain why reliable geographic referencing uses identifiers and gazetteer records rather than display text alone. This guide shows how to translate geographic identifiers, map legends, administrative-area labels and multilingual gazetteer entries without sending a person to the wrong place or misrepresenting a source dataset.
Imagine a flood notice mentioning Springfield, a heritage catalogue giving an old district name and a delivery system storing a village whose boundary has moved. If a translator copies only the visible label, a user may pick the wrong municipality, lose a historical site or treat an administrative change as a physical movement. A better translation distinguishes the name used in the source, the entity to which the name refers, its authority, its period of validity and its spatial relationship to other places. The practical cases below follow that distinction from small signs to international datasets.
At a glance: identify the geographic entity before choosing its translated name; keep stable reference identifiers separate from labels; record name language and script; preserve the type and level of administrative division; retain historical aliases and validity periods; distinguish coordinates from place-name reference systems; and verify consequential locations with the responsible gazetteer or map authority. This is a specialist learning route within the existing translation architecture, not a replacement world gazetteer.
Quick answer: the safe translation workflow
- Read the source record and determine the precise entity or event it is trying to describe.
- Separate facts, estimates, labels and internal identifiers before drafting prose.
- Translate for a specific reader while retaining what the source does not establish.
- Use a controlled terminology and data-field register, with the original evidence accessible.
- Test the target version in its real interface or document and have the data owner approve consequential changes.
Understanding the standard and the translation question
ISO 19112:2019 establishes a conceptual schema for spatial referencing by geographic identifiers and for gazetteers. Coordinate referencing belongs principally to ISO 19111, although complementary coordinate references may appear in records. This guide teaches translation of geographic identifiers and associated metadata, not a certified GIS implementation or an official place-name registry.
This guide is written for map editors, place-name translators, localization teams, archival cataloguers, civic data teams, geospatial analysts and community researchers. Its narrow search intent is how to translate place names, geographic identifiers, gazetteer records and administrative areas without assigning the wrong location or losing an authoritative reference. It concentrates on the problem a reader has when translating that kind of record. It does not claim that the referenced ISO publication supplies a certified translation, an authoritative government record or a ready-made software system. The fictional examples below are original exercises designed to expose choices that ordinary word-for-word substitutions would hide.
Chapter 1. Why a place name is not a place identity
The word printed on a map is a label; the referenced geographic entity is what the dataset intends to identify. Two different places can share the same name, and one place can have more than one name. Translation needs to preserve the entity link, not only select the most familiar spelling.
Imagine two Saint Marys in different countries. A correct English label without a country or identifier still leaves an ambiguous reference. The ambiguity persists even if the spelling is technically perfect.
For every translated location, record the feature type, jurisdiction and source identifier before discussing whether an exonym or endonym is best for readers.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 2. What ISO 19112 describes
The public ISO scope specifies a conceptual schema for spatial reference systems based on geographic identifiers and a conceptual scheme for gazetteers. This enables data producers to define references consistently and data users to understand them across maps, datasets and text.
The standard should not be mistaken for a global list declaring what every settlement must be called. It describes how identifiers and related location information are organized, not a universal political naming decision.
When citing the standard, explain the conceptual role and reference the relevant national or local authority for authoritative names and boundaries.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 3. Separate identifier, language, script and display label
A gazetteer entry may hold an identity key, preferred name, alternative spelling, language, script, feature type and location context. A translation can change an interface label but should not generate a new identity key for the same place without a controlled migration.
For an English interface, a city may be shown in a familiar English spelling while a source-language record retains Chinese, Japanese, Arabic or another script. Both can point to the same place entry.
Keep a reversible trail between source text, normalized label, translated display name and authoritative identifier. Search aliases should not silently become new places.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 4. Understand feature types before translating administrative words
A ‘province’, ‘county’, ‘district’, ‘prefecture’, ‘ward’ and ‘commune’ do not form one universally interchangeable hierarchy. Their legal powers and nesting vary by country. A translator who replaces unfamiliar terms with a home-country equivalent can create false administrative authority.
One jurisdiction’s ‘district’ may be an electoral unit, another’s planning unit and another’s municipal division. The relevant governing statute or official dataset may be needed to explain the level accurately.
When uncertain, retain the local term with a concise explanation rather than inventing an exact English institutional equivalent.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 5. Respect name histories and temporal validity
Places are renamed, borders change and a settlement can be absorbed into another jurisdiction. A historic name may be correct for an old document even if contemporary navigation needs the modern label. Translation must not erase the period of the source.
An archive caption that uses an earlier city name can be glossed with the current name while retaining the historical wording. A shipping address, by contrast, should reflect present delivery conventions.
Use separate fields for the name as written, current preferred display name, aliases and validity dates. Never turn an uncertain former name into an asserted modern location.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 6. Separate coordinates from name-based reference
A coordinate pair and a geographic identifier do different jobs. A point can suggest a position but may not resolve a named area, and a locality name may refer to a region rather than one coordinate. ISO 19112 addresses name-based spatial referencing, while ISO 19111 handles coordinate referencing.
A postal code, a district name and a latitude/longitude pair can point to overlapping but unequal extents. Treating them as interchangeable is a frequent source of automated geocoding errors.
Ask the data owner whether the destination field expects a point, an area, an address, a place record or an administrative unit, then test the map result.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 7. Design multilingual gazetteer search with visible uncertainty
Readers often search an unaccented spelling, an English exonym, a historical form or an alternate transliteration. A search system can support aliases while still distinguishing candidate results that carry different identifiers.
An interface that automatically selects the first matching ‘Cambridge’ could route a user to a different country. Search-result lists should show the distinguishing geographic context rather than pretend only one match exists.
Test ambiguous labels, transliteration alternatives, missing diacritics and multiple languages with actual users from relevant locations.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 8. Treat indigenous and community names respectfully
A single government-preferred label does not exhaust the social history of a place. Indigenous names, colonial spellings, community usage and official co-naming can coexist, sometimes with different authorities and dates.
The translator should not decide which contested name is politically legitimate by silently deleting alternatives. Instead, cite the source context and use the naming policy of the particular map or collection.
Where names are disputed, describe the uncertainty neutrally, preserve original forms and seek the appropriate local expertise for public-facing publication.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Chapter 9. Audit changes across maps, captions and structured exports
Place-name translation is often distributed across map tiles, popup cards, downloadable spreadsheets, image alt text, route directions and metadata. One correct field does not guarantee consistent meaning across the publication.
An updated English gazetteer label may appear correctly on a page while a linked CSV still contains a deleted district name. The resulting mismatch can mislead analysts and damage search discovery.
Audit a sample from source to map, search, CSV, screen-reader output and print export. Record which fields are labels and which are identifiers.
The practical test in this chapter is to compare the source assertion, the target wording and the record’s purpose side by side. A translator should write down which details survive unchanged and which are only presentation choices. If an editor requests a smoother sentence that erases a limitation, the response should show exactly what fact or inference would be added. Readers need a usable explanation, but usability is not permission to alter the underlying claim.
Worked translation cases: original scenarios and reasoned repairs
The following 28 invented exercises represent distinct document and data situations. The example source phrases are not quotations from the ISO standard. They demonstrate a disciplined habit: identify the referent, make the false inference visible, repair the wording and name a test that would catch the error in actual work. The safer rendering is an English explanatory gloss; translation into another target language must preserve the same conditions and be reviewed by a proficient speaker.
Case 1. Two Springfields
Source situation. A safety notice gives ‘Springfield’ with no state or country. Misleading shortcut. Selecting the first search result assigns a definite location without evidence.
Better reader-facing rendering. “’Springfield [jurisdiction not specified in source].’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. The tempting shortcut is to make the target text look complete, but completeness of typography is not completeness of evidence.
What to verify. Ask for the responsible municipality and preserve the notice’s original identifier if present. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Keep the supporting source field available to the reviewer. If the record owner cannot confirm the missing fact, the published copy should say that it is not established rather than conceal the gap. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 2. A city’s English exonym
Source situation. English-facing tourist signs use ‘Florence’ while source records use ‘Firenze’. Misleading shortcut. Treating them as separate towns duplicates the entity.
Better reader-facing rendering. “’Florence (Firenze)’ as a bilingual display of the same verified city.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. Here the difficulty is not a rare vocabulary item. It is the relationship between the words and the record they purport to describe.
What to verify. Check the official place identifier and the audience’s naming convention. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
In an actual workflow, compare search results, user instructions and any exported record, because a correct sentence can still be attached to the wrong data value. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 3. A Japanese source name
Source situation. Source contains ‘東京都’ in a prefectural dataset. Misleading shortcut. Translating it as a specific ward or the metropolitan city centre shrinks its geographic extent.
Better reader-facing rendering. “’Tokyo Metropolis’, with the source-script value preserved.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. This is a useful test of whether a translator can preserve a distinction while still giving a busy reader an immediately usable sentence.
What to verify. Confirm the administrative feature type and dataset jurisdiction. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Ask the requester to confirm the business or research consequence of this wording. If it changes where someone goes, what they believe or what a program does, sign-off must be explicit. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 4. A multilingual road label
Source situation. Two sign systems transliterate the same street differently. Misleading shortcut. Geocoding each spelling as a separate road fragments its route.
Better reader-facing rendering. “Store both spellings as label variants attached to one verified road entity.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. A second reviewer who sees only the final sentence could reasonably infer more than the source says; that is why the qualification must remain visible.
What to verify. Test whether entrances and street segments share or differ in identifier. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
A faithful translation should remain accurate when copied into a report without its surrounding paragraph. Include enough identifying context and qualification for that realistic reuse. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 5. A province versus a district
Source situation. A foreign source calls an area a ‘provincia’. Misleading shortcut. Replacing it with ‘county’ may assert a different level of government.
Better reader-facing rendering. “’Province’ or ‘provincia’, according to the country’s official usage.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. The tempting shortcut is to make the target text look complete, but completeness of typography is not completeness of evidence.
What to verify. Consult jurisdiction-specific administrative definitions before publication. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Keep the supporting source field available to the reviewer. If the record owner cannot confirm the missing fact, the published copy should say that it is not established rather than conceal the gap. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 6. A historical city name
Source situation. A 1930 archive document uses a city name no longer preferred today. Misleading shortcut. Silently substituting the modern name falsifies the document transcription.
Better reader-facing rendering. “’Historical name [as written]; present-day name [verified].’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. Here the difficulty is not a rare vocabulary item. It is the relationship between the words and the record they purport to describe.
What to verify. Record the years during which each designation was used. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
In an actual workflow, compare search results, user instructions and any exported record, because a correct sentence can still be attached to the wrong data value. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 7. A village with changing boundaries
Source situation. A village was incorporated into a neighboring city after a census. Misleading shortcut. Using the current boundary for historical population totals changes the denominator.
Better reader-facing rendering. “’Village under its 2001 administrative boundaries.’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. This is a useful test of whether a translator can preserve a distinction while still giving a busy reader an immediately usable sentence.
What to verify. Verify the census geography and preserve boundary-version metadata. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Ask the requester to confirm the business or research consequence of this wording. If it changes where someone goes, what they believe or what a program does, sign-off must be explicit. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 8. A postal code entered as locality
Source situation. A map import uses a postal code where a place-name identifier is expected. Misleading shortcut. Treating the code as the town name corrupts the gazetteer.
Better reader-facing rendering. “’Postal code [code] associated with [verified delivery area].’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. A second reviewer who sees only the final sentence could reasonably infer more than the source says; that is why the qualification must remain visible.
What to verify. Distinguish address routing from administrative location. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
A faithful translation should remain accurate when copied into a report without its surrounding paragraph. Include enough identifying context and qualification for that realistic reuse. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 9. A river sharing a city name
Source situation. ‘Jordan’ appears in a dataset of natural features. Misleading shortcut. Assuming the country or person rather than the river misclassifies the record.
Better reader-facing rendering. “’Jordan River’, if the feature type confirms a watercourse.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. The tempting shortcut is to make the target text look complete, but completeness of typography is not completeness of evidence.
What to verify. Inspect the feature-class field before selecting a translated label. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Keep the supporting source field available to the reviewer. If the record owner cannot confirm the missing fact, the published copy should say that it is not established rather than conceal the gap. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 10. An island group versus one island
Source situation. A travel guide says ‘the islands’ while a mapping system stores only the largest island. Misleading shortcut. The target translation narrows a group to a single landmass.
Better reader-facing rendering. “’The island group [official collective name].’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. Here the difficulty is not a rare vocabulary item. It is the relationship between the words and the record they purport to describe.
What to verify. Compare area extent and feature type, not just its popular name. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
In an actual workflow, compare search results, user instructions and any exported record, because a correct sentence can still be attached to the wrong data value. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 11. An accented place name
Source situation. A user’s keyboard omits the accent in a town search. Misleading shortcut. Creating a second canonical entry for the unaccented string splits the location.
Better reader-facing rendering. “Use the accurate display name and an accent-insensitive search alias.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. This is a useful test of whether a translator can preserve a distinction while still giving a busy reader an immediately usable sentence.
What to verify. Verify that search normalization does not replace the authoritative spelling. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Ask the requester to confirm the business or research consequence of this wording. If it changes where someone goes, what they believe or what a program does, sign-off must be explicit. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 12. A place with competing transliterations
Source situation. A source uses one romanization while a local authority publishes another. Misleading shortcut. Mixing forms across captions creates apparent multiple places.
Better reader-facing rendering. “Preferred current form with original transliteration retained as alias.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. A second reviewer who sees only the final sentence could reasonably infer more than the source says; that is why the qualification must remain visible.
What to verify. Track romanization scheme and source date. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
A faithful translation should remain accurate when copied into a report without its surrounding paragraph. Include enough identifying context and qualification for that realistic reuse. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 13. A mountain summit versus park
Source situation. A visitor asks for a mountain while the map label resolves to its wider national park. Misleading shortcut. The route endpoint is wrong even when the visible name overlaps.
Better reader-facing rendering. “Specify ‘summit’, ‘trailhead’ or ‘park area’ as confirmed.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. The tempting shortcut is to make the target text look complete, but completeness of typography is not completeness of evidence.
What to verify. Ask which feature and entrance the user actually needs. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Keep the supporting source field available to the reviewer. If the record owner cannot confirm the missing fact, the published copy should say that it is not established rather than conceal the gap. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 14. An old map’s harbor
Source situation. A nineteenth-century map marks a harbor relocated or infilled today. Misleading shortcut. Placing a current coordinate point as if the old harbor still existed misleads historical readers.
Better reader-facing rendering. “’Former harbor site, shown on the historical map.’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. Here the difficulty is not a rare vocabulary item. It is the relationship between the words and the record they purport to describe.
What to verify. Link the historical map’s edition and show uncertainty in modern position. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
In an actual workflow, compare search results, user instructions and any exported record, because a correct sentence can still be attached to the wrong data value. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 15. A term for ward
Source situation. Japanese ‘ku’ can appear in several administrative contexts. Misleading shortcut. Translating every instance as a generic ‘city’ loses the subdivision.
Better reader-facing rendering. “’Ward’ with the original unit and larger jurisdiction supplied.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. This is a useful test of whether a translator can preserve a distinction while still giving a busy reader an immediately usable sentence.
What to verify. Verify the local administrative system and use official English nomenclature. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Ask the requester to confirm the business or research consequence of this wording. If it changes where someone goes, what they believe or what a program does, sign-off must be explicit. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 16. A disputed boundary
Source situation. Two public datasets assign a settlement to different administrative units. Misleading shortcut. Choosing the favorable border silently makes an unsupported political assertion.
Better reader-facing rendering. “’Boundary depiction follows [named source and date].’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. A second reviewer who sees only the final sentence could reasonably infer more than the source says; that is why the qualification must remain visible.
What to verify. Cite the authority and retain alternative data in controlled notes. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
A faithful translation should remain accurate when copied into a report without its surrounding paragraph. Include enough identifying context and qualification for that realistic reuse. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 17. A walking-tour popup
Source situation. A map marker labels ‘Old Town’ but its linked description covers a broader conservation district. Misleading shortcut. Treating the historical quarter and legal protection area as identical changes scope.
Better reader-facing rendering. “’Old Town area within the designated conservation district.’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. The tempting shortcut is to make the target text look complete, but completeness of typography is not completeness of evidence.
What to verify. Verify whether the labels denote features with different boundaries. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Keep the supporting source field available to the reviewer. If the record owner cannot confirm the missing fact, the published copy should say that it is not established rather than conceal the gap. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 18. A monastery and neighborhood
Source situation. A parish and a neighborhood have the same name in a cultural heritage register. Misleading shortcut. Translating the record as a neighborhood may erase its building-specific identity.
Better reader-facing rendering. “’Monastery of [name]’ or ‘neighborhood of [name]’ according to feature class.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. Here the difficulty is not a rare vocabulary item. It is the relationship between the words and the record they purport to describe.
What to verify. Check record type and geographic identifier. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
In an actual workflow, compare search results, user instructions and any exported record, because a correct sentence can still be attached to the wrong data value. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 19. A translated map legend
Source situation. A shaded polygon is labeled ‘municipal service zone’. Misleading shortcut. Rendering ‘municipality’ makes it appear to be a governmental border.
Better reader-facing rendering. “’Municipal service area’, preserving its service-boundary function.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. This is a useful test of whether a translator can preserve a distinction while still giving a busy reader an immediately usable sentence.
What to verify. Ask whether the polygon describes jurisdiction or operations. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Ask the requester to confirm the business or research consequence of this wording. If it changes where someone goes, what they believe or what a program does, sign-off must be explicit. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 20. A rural hamlet alias
Source situation. Older community members use a local name not in the official street directory. Misleading shortcut. Deleting the name from an oral-history map makes the account hard to find.
Better reader-facing rendering. “Retain the community name as a historical or local alias.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. A second reviewer who sees only the final sentence could reasonably infer more than the source says; that is why the qualification must remain visible.
What to verify. Keep its oral source citation and the separate verified official entity. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
A faithful translation should remain accurate when copied into a report without its surrounding paragraph. Include enough identifying context and qualification for that realistic reuse. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 21. A dataset’s unknown name language
Source situation. A gazetteer string uses Latin letters but its underlying language is not recorded. Misleading shortcut. Guessing ‘English’ from the script assigns false linguistic metadata.
Better reader-facing rendering. “’Name recorded in Latin script; language not established.’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. The tempting shortcut is to make the target text look complete, but completeness of typography is not completeness of evidence.
What to verify. Ask data provider for language tag rather than infer it from letters. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Keep the supporting source field available to the reviewer. If the record owner cannot confirm the missing fact, the published copy should say that it is not established rather than conceal the gap. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 22. A road crossing a border
Source situation. One highway has different labels on either side of a national border. Misleading shortcut. One translated label applied to the full line ignores distinct local authority.
Better reader-facing rendering. “Apply jurisdiction-scoped official labels to appropriate segments.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. Here the difficulty is not a rare vocabulary item. It is the relationship between the words and the record they purport to describe.
What to verify. Audit boundary segmentation and navigation prompts. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
In an actual workflow, compare search results, user instructions and any exported record, because a correct sentence can still be attached to the wrong data value. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 23. A geocoded school campus
Source situation. A school name resolves to the institution’s registered office rather than its teaching campus. Misleading shortcut. Publishing the office pin as the campus gives unusable directions.
Better reader-facing rendering. “’Teaching campus at [verified location]’ separate from registered office.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. This is a useful test of whether a translator can preserve a distinction while still giving a busy reader an immediately usable sentence.
What to verify. Verify address role and destination with the institution. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Ask the requester to confirm the business or research consequence of this wording. If it changes where someone goes, what they believe or what a program does, sign-off must be explicit. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 24. A place named for a person
Source situation. A town and a nearby memorial share a person’s surname. Misleading shortcut. Entity matching on the surname alone merges a built feature and settlement.
Better reader-facing rendering. “Use feature-qualified labels for settlement and memorial.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. A second reviewer who sees only the final sentence could reasonably infer more than the source says; that is why the qualification must remain visible.
What to verify. Check gazetteer identifier, feature category and parent locality. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
A faithful translation should remain accurate when copied into a report without its surrounding paragraph. Include enough identifying context and qualification for that realistic reuse. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 25. An archaeological site
Source situation. An excavation report names ‘Sector B’, but translation drops the site’s parent identifier. Misleading shortcut. ‘Sector B’ alone cannot be located across different projects.
Better reader-facing rendering. “’Sector B, [site name and survey grid].’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. The tempting shortcut is to make the target text look complete, but completeness of typography is not completeness of evidence.
What to verify. Preserve project identifier and coordinate-system provenance. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Keep the supporting source field available to the reviewer. If the record owner cannot confirm the missing fact, the published copy should say that it is not established rather than conceal the gap. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 26. A language-specific endonym
Source situation. Indigenous and majority-language maps label the same river differently. Misleading shortcut. Treating one name as a mistranslation erases legitimate multilingual naming.
Better reader-facing rendering. “Display both authorized names with language context.” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. Here the difficulty is not a rare vocabulary item. It is the relationship between the words and the record they purport to describe.
What to verify. Consult local naming conventions and respect source provenance. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
In an actual workflow, compare search results, user instructions and any exported record, because a correct sentence can still be attached to the wrong data value. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 27. A changing capital
Source situation. A statistical report lists a capital city for a historical reference year. Misleading shortcut. Updating the capital to the current seat of government alters the historical record.
Better reader-facing rendering. “’Capital at the time of the report: [historical city].’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. This is a useful test of whether a translator can preserve a distinction while still giving a busy reader an immediately usable sentence.
What to verify. Verify the effective dates of the governmental change. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
Ask the requester to confirm the business or research consequence of this wording. If it changes where someone goes, what they believe or what a program does, sign-off must be explicit. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
Case 28. A geometry centroid
Source situation. A polygon dataset has a centroid coordinate for a large district. Misleading shortcut. A web map may describe it as the exact point where the district is located.
Better reader-facing rendering. “’Approximate label point for the district area.’” The aim is not to make every target sentence longer, but to preserve the piece of information that determines what the text legitimately means. A second reviewer who sees only the final sentence could reasonably infer more than the source says; that is why the qualification must remain visible.
What to verify. Verify whether the coordinate denotes centroid, entrance, representative point or boundary. This check is not optional decoration: a second-language reader may act on the translated line without access to the original. The review should therefore test the assertion, its limits and its link to the underlying record rather than merely compare dictionary equivalents.
A faithful translation should remain accurate when copied into a report without its surrounding paragraph. Include enough identifying context and qualification for that realistic reuse. For a useful practice exercise, draft a deliberately overconfident one-line translation of this case, then repair it by restoring only the evidence-backed qualification. Explain to a colleague why the shorter version would have misled them.
A complete editorial and data review method
Stage one is intake. Record the source language, target language, audience, document owner, authoritative version, intended display surface and any source identifiers. Separate source quotations from translator commentary. State whether the task is to explain an uncertain record, migrate database content, localize a UI label or prepare a legally consequential notice. These are different deliverables, even if the initial sentence looks the same. A team that skips intake will spend time debating English style while important meaning is lost in an unexamined field or attachment.
Stage two is a controlled bilingual issue log. Create a row for the original expression, its proposed translation, its referent, what is known, what remains uncertain, an alternative rendering and the reason for acceptance. Include the reviewer and date of approval. The log should distinguish a data correction from a translation decision: changing the truth of the record requires an authorized source correction, while changing an explanation may be permitted within the translation brief. For repeat terminology, document the concept as well as the wording so that later translators do not mechanically copy an expression into a different context.
Stage three is testing. Open the translated item as a reader would: mobile page, printed extract, search result, map, schedule, spreadsheet or database export as appropriate. Ask whether the target text still points to the same thing, describes the same period, leaves the same uncertainty and supports the same authorized decisions. Challenge any symbol that looks technical and exact when the source was tentative. Challenge any comforting general term that hides distinct categories. A concise target version is welcome only when the original evidential boundary remains recoverable.
Stage four is publication control. The source owner confirms factual assertions and release scope; a qualified translator checks fluency, register and terminology; a domain reviewer checks consequential meaning; and an editor checks headings, explanations, accessibility and links. Record unresolved questions explicitly. If a source contains a contradiction, do not make up a seamless compromise to protect an attractive headline. Either secure an authoritative correction or tell readers the limitation in plain language.
A four-week practice plan for translators and reviewers
Week one: read the public scope of the cited standard, then build a terminology register from ten authentic but permitted sample records. For each record, identify which fields are labels and which fields establish identity or validity. Produce a short English gloss that preserves the original ambiguity and write one question that would resolve it.
Week two: have a colleague draft ten deliberately plausible but misleading paraphrases. Correct each one with the smallest necessary phrase, not a sprawling warning. Compare the reader’s likely inference before and after the repair. Note where a simple omitted adjective, qualifier or authority label changes the decision.
Week three: place the revised sentences into realistic presentation surfaces: a catalogue, a data table, a browser snippet, a public notice and a bilingual training handout. Check whether the surrounding interface changes what the reader assumes. Test exports and link targets with the same rigor as the main article.
Week four: commission a blind review from a fluent target-language reader and a domain specialist. Give them the target version first and ask what they believe it asserts. Then provide the source evidence and compare the interpretations. Summarize recurrent errors and revise the project’s termbase and review checklist.
Frequently asked questions
Does ISO 19112 tell me the correct English name for every place?
No. It defines a conceptual framework for geographic identifier-based reference and gazetteers. Authoritative names come from relevant place-name sources and policies. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
Can two names identify the same place?
Yes. Multilingual names, aliases, older forms and romanizations may all refer to one geographic entity. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
Are coordinates interchangeable with geographic identifiers?
No. A coordinate is not necessarily the same kind of reference as a named area or entity. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
Should I translate every local administrative term into a familiar English term?
Not automatically. Administrative powers and hierarchy vary by jurisdiction, so apparent equivalents may mislead. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
What do I do when two places have the same name?
Show contextual qualifiers and use an authoritative identifier; do not silently choose the first search result. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
Can I change the name in a historical quotation?
Retain the historical wording, with a modern explanation or cross-reference where helpful. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
How do I handle disputed names?
Preserve source attribution, state the context, use a documented publishing policy and avoid pretending a contested choice is universally accepted. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
How do I QA a gazetteer translation?
Follow each identifier through search, maps, exported data, alt text and captions, checking feature type and geographic context. If your specific document goes beyond this example, preserve the uncertainty in the first published version and obtain a source-owner decision before replacing it with a more definitive statement.
Final principle: truthful clarity is more useful than false certainty
A good geographic translation allows readers to find the same place that the original author intended, even when languages, scripts, borders and institutional names differ. Accurate labels matter, but traceable entity identity matters more.
Professional communication is not an exercise in making every translated phrase appear tidy. A reader needs to understand what the source establishes, why it matters, what remains unknown and where an answer could be checked. Precise translation follows the underlying evidence through changes of vocabulary, script, format and software. It does not manufacture completeness in the gaps left by the original. The most valuable sentence is often the one that gives a practical instruction without hiding the condition that makes it correct.
Verified reference and protected learning routes
Official catalogue, reviewed 5 November 2026: ISO 19112:2019 — public ISO publication description; related official or technical reference: supporting reference. This article offers original translation-training examples and does not reproduce or claim compliance with paid normative clauses. Readers who need to implement a formal ISO profile should consult the licensed standard and the relevant technical or professional authority.
The conceptual owner for this series remains The Master Art of Translation (EDKSG-TRANS-MASTER-WORLD-000). Term and meaning development belongs to the protected Vocabulary Learning Hub. Sentence-level clarity, reference and interpretation connect to How English Works: Translation and Meaning Across Languages. This narrow technical guide is a child application of those resources and does not create a competing translation hub.