A place can have several legitimate names in Roman letters.

北京 is internationally written Beijing, but historical English sources often use Peking. Москва may be romanized as Moskva, while English convention uses Moscow. القاهرة can become Al Qāhirah under a formal Arabic geographic-name system, yet English maps generally label it Cairo. 부산 is officially Busan in South Korea, although older maps and books frequently use Pusan.

These differences arise because geographic names are not ordinary words.

A place name may simultaneously have:

• An official local-script name
• A nationally standardized Roman form
• A United Nations-recommended romanization
• A BGN/PCGN geographic form
• An established English exonym
• A historical or colonial-era spelling
• A minority-language or Indigenous name
• A locally preferred name
• Several searchable aliases

Cartographers, governments, publishers, travelers, search engines, and geographic information systems do not always need the same form.

A map requires concise, standardized labels. A historical database must preserve names used in older sources. A navigation application must connect common spellings to the same coordinates. A national naming authority may prioritize locally official forms, while an English-language atlas may retain selected conventional names familiar to its audience.

The correct question is therefore not:

What is the one universally correct Roman spelling of this place?

It is:

Which name, language, romanization system, authority, historical period, and use case does this spelling represent?

Quick Answer

Romanizing a geographic name means converting a place name written in a non-Latin script into Roman letters according to a defined system.

For official or technical use, begin with the nationally standardized name and the romanization system officially implemented by the country concerned. For international mapping, also check applicable United Nations, BGN/PCGN, or institutional standards. Preserve conventional English, historical, minority-language, and alternative names as labeled variants rather than discarding them.

A practical priority order is:

1. Official name in the original script
2. Official national Roman-script form
3. Nationally approved romanization system
4. Applicable UN-recommended or BGN/PCGN form
5. Established conventional name for the publication’s language
6. Historical, regional, minority-language, and searchable variants

UNGEGN’s Working Group on Romanization Systems seeks agreement on a single internationally usable romanization system for each non-Roman writing system used in geographic names. Proposed systems are expected to be scientifically sound, officially supported, substantially implemented by the proposing country, and sufficiently reversible for their purpose.

What Is a Geographic Name?

A geographic name is a name applied to a feature on or associated with the Earth.

Geographic features include:

• Countries and territories
• Provinces and administrative regions
• Cities and villages
• Rivers and lakes
• Mountains and valleys
• Islands and coastlines
• Roads and railway stations
• Deserts and forests
• Seas and oceans
• Undersea features
• Cultural landscapes
• Neighborhoods and localities

The study of place names is called toponymy. A place name is also called a toponym.

Toponymy examines more than spelling. It may investigate:

• Language of origin
• Meaning
• Pronunciation
• Historical development
• Naming authority
• Local usage
• Cultural associations
• Political changes
• Alternative and former names
• Relationship to the geographic feature

Geographic names are critical identifiers in mapping and geospatial data. Unlike roads, rivers, coastlines, and buildings, a name usually cannot be identified from satellite imagery alone. It depends on linguistic, administrative, historical, and community evidence. PCGN therefore describes names as a map attribute requiring authoritative research rather than visual interpretation alone.

National and International Standardization

National Standardization Comes First

UNGEGN’s approach begins with national standardization.

A country is expected to determine:

• The official names of features within its jurisdiction
• The correct spelling in the relevant local language
• The appropriate writing system
• Rules for capitalization and word division
• Treatment of administrative terms
• Official Roman-script forms
• The romanization system used when the original script is non-Latin

The purpose is to create consistent names for:

• Government records
• Maps
• Road signs
• Postal systems
• Emergency services
• Statistical data
• Education
• Transportation
• Property administration
• Geographic information systems

The United Nations manual on national standardization treats transliteration, transcription, translation, endonyms, exonyms, name authorities, field collection, gazetteers, and databases as connected parts of geographic-name administration.

International Standardization

International standardization does not ordinarily mean inventing a foreign spelling independently of local authorities.

Instead, it aims to promote consistent international use of nationally standardized names and romanization systems.

UNGEGN has recognized romanization as a core geographic-name issue since the first United Nations conference on name standardization in 1967. Its current website lists 30 language or script systems recommended by the United Nations, along with additional systems supplied for information.

International standardization is particularly important for:

• Cross-border maps
• International aviation
• Maritime navigation
• Diplomatic communication
• Humanitarian operations
• Global statistics
• International shipping
• News reporting
• Scientific research
• Multilingual geographic databases

Endonyms, Exonyms and Conventional Names

Understanding geographic-name romanization requires distinguishing local names from names used in other languages.

Endonym

An endonym is a name used in an official or well-established language occurring in the area where the geographic feature is located.

UNGEGN examples include:

• Vārānasī, rather than the English historical form Benares
• Aachen, rather than French Aix-la-Chapelle
• Krung Thep, rather than English Bangkok
• Al-Uqşur, rather than English Luxor

The exact status of a name may depend on language, jurisdiction, and local usage.

Exonym

An exonym is a name used in a particular language for a feature situated outside the area where that language is spoken, when the form differs from the locally used name.

Examples include:

English exonym	Local name or endonym
Moscow	Moskva
Florence	Firenze
Munich	München
Cologne	Köln
Vienna	Wien
Cairo	Al-Qāhirah
Athens	Athína

An exonym is not necessarily a mistaken romanization. It may be an established name in another language with centuries of usage.

Conventional English Name

A conventional English name is an established English-language name that differs from the locally official or directly romanized form.

PCGN recommends retaining English conventional names in selected cases, particularly where they are well established, recognizable, and useful to English-language audiences. Its guidance treats conventional names as a distinct editorial category rather than as automatic replacements for every local name.

Romanization Is Not an Exonym

These categories should not be confused.

For Москва:

• Original Cyrillic endonym: Москва
• Direct Roman-script representation: Moskva
• English exonym: Moscow

For القاهرة:

• Original Arabic endonym: القاهرة
• Systematic Roman form: Al Qāhirah
• English exonym: Cairo

A Roman form attempts to represent the local name in another script. An exonym is a separate name used by another language community.

Romanization, Transliteration and Transcription

Romanization

Romanization converts a name written in a non-Roman script into Roman letters.

The target is always the Latin script, but the conversion method may be transliteration, transcription, or a hybrid.

Transliteration

Transliteration follows the written characters of the source name.

A transliteration-oriented system may prioritize:

• Character-by-character correspondence
• Reversibility
• Preservation of spelling
• Distinction between source letters
• Consistency across a database

Transcription

Transcription follows pronunciation.

A transcription-oriented system may:

• Change according to neighboring sounds
• Supply vowels absent from the source spelling
• Reflect a standard spoken form
• Merge source letters pronounced alike
• Produce a more reader-friendly result

Geographic Systems Are Often Hybrid

Many geographic-name systems combine the two approaches.

A system may:

• Map most letters consistently
• Apply contextual pronunciation rules
• Use digraphs to guide readers
• Simplify specialist marks
• Retain established place-name conventions
• Apply special rules to articles and generic terms

UNGEGN defines romanization as converting writing into Roman script and emphasizes systematic methods so that different users produce consistent results.

Why Geographic Names Need Dedicated Romanization Rules

A general transliteration chart does not resolve every mapping problem.

Geographic names frequently contain:

• Administrative terms
• Definite articles
• Directional elements
• Generic feature words
• Compound names
• Personal names
• Tribal or clan names
• Historical spellings
• Dialect forms
• Locally abbreviated forms

For example, a place name may contain a generic term meaning:

• river
• mountain
• lake
• city
• province
• island
• bay
• pass

A geographic-name standard must decide whether that generic element is:

• Romanized as part of the name
• Translated
• Omitted at a particular map scale
• Capitalized
• Joined to the specific element
• Separated by a space or hyphen

This is why geographic-name standards usually include more than alphabet tables.

Major Geographic-Name Authorities

National Naming Authorities

A national naming authority may be a:

• Mapping agency
• Geographic-name board
• Survey department
• Language commission
• Interior ministry
• Statistical authority
• Local-government department
• Hydrographic office

It usually has the strongest authority over official names within its jurisdiction.

National authorities may maintain:

• Official gazetteers
• Place-name registers
• Geographic databases
• Naming policies
• Romanization rules
• Historical-name records
• Administrative-boundary names

UNGEGN

The United Nations Group of Experts on Geographical Names promotes national and international geographic-name standardization.

Its work includes:

• Romanization systems
• Toponymic terminology
• Country guidelines
• Gazetteers
• Data modeling
• Training
• Exonyms
• Indigenous and minority names
• Cultural heritage
• International cooperation

UNGEGN sessions bring together specialists in geography, cartography, geospatial information, linguistics, history, and geographic-name administration.

BGN and PCGN

The United States Board on Geographic Names and the United Kingdom’s Permanent Committee on Geographical Names jointly develop or approve romanization systems for foreign geographic names.

These systems establish standardized Roman-script spellings for names written in:

• Arabic script
• Cyrillic
• Greek
• Hangul
• Han characters
• Indic scripts
• Other non-Latin writing systems

They also provide spelling conventions for Roman alphabets containing letters not normally used in English.

The official PCGN collection was updated on January 28, 2025. It states that the systems listed are currently approved and regularly reviewed, and that each system should be applied with the relevant regional policy.

Geographic Names Server

The National Geospatial-Intelligence Agency’s Geographic Names Server is the official repository of foreign geographic-name decisions approved by the U.S. Board on Geographic Names.

In addition to approved current names, it includes:

• Variant spellings
• Historical names
• Non-Roman-script forms
• Geographic coordinates
• Feature classifications
• Administrative information

The database can be searched and downloaded for use in geographic information systems and other structured applications.

For names within the United States, the corresponding federal resource is the Geographic Names Information System maintained through the U.S. geographic-names program rather than the foreign-name GNS.

UN Romanization Systems

A UN-recommended system is not selected merely because its spelling looks convenient.

The approval process considers whether the proposed system:

• Is based on sound linguistic principles
• Has been officially proposed
• Is nationally implemented
• Can be applied consistently
• Is sufficiently reversible
• Avoids unnecessary ambiguity
• Can be used on maps and in databases
• Has been reviewed by technical experts
• Is suitable for international adoption

The 2026 UNGEGN approval-process guidance states that implementation may be demonstrated through use in national maps, geographic-name databases, signs, and official publications. After technical consultation and UNGEGN approval, a system can proceed for adoption as a United Nations standard.

This process helps prevent an international system from being disconnected from actual national practice.

BGN/PCGN Systems and Agreements

BGN/PCGN documents fall into several categories.

BGN/PCGN System

A jointly designed system created for a language or writing system.

BGN/PCGN Agreement

An agreement adopting or aligning with a national system after that system has achieved suitable official implementation.

Table of Correspondences

A table connecting an existing Roman-script national convention with forms useful for British and American official applications.

The distinction matters because a nationally developed system may replace an older BGN/PCGN-created table.

Examples of geographic systems may have different adoption years and policies even when their source scripts are related. A database should therefore record the exact language and system version, not merely “BGN romanization.”

How Geographic Names Change

Place names can change because of:

• Independence
• Administrative reform
• Language policy
• Decolonization
• Restoration of an Indigenous name
• Changes in official orthography
• A new romanization standard
• Municipal consolidation
• Political transition
• Correction of an earlier mapping error
• Local referendum or government decision

A Latin spelling may change even when the original-script name remains unchanged.

For example, replacing one romanization system with another can alter:

• Initial consonants
• Vowel spellings
• Diacritics
• Hyphenation
• Word division
• Treatment of articles
• Capitalization

The feature has not moved, but its standardized Roman label has changed.

Historical Names Should Not Be Deleted

A current official name should normally be the primary modern label, but former names remain essential data.

Historical names support:

• Archive searches
• Genealogical research
• Historical maps
• Military records
• Travel writing
• Newspaper databases
• Academic research
• Museum collections
• Legal records
• Migration history

A strong geographic database may classify names as:

• Approved
• Official
• Variant
• Former
• Historical
• Conventional
• Local
• Minority-language
• Short form
• Long form

The GNS’s inclusion of current, variant, historical, and non-Roman forms demonstrates why a place-name record should support multiple linked names rather than one overwritable text value.

Examples of Multiple Geographic-Name Forms

Beijing, Peking and Pei-ching

For 北京:

• Current Hanyu Pinyin: Beijing
• Historical conventional form: Peking
• Wade–Giles-style form: Pei-ching

These spellings reflect different systems and periods.

For current official geographic use, Beijing is the appropriate modern form. Historical texts and established institutional names may retain Peking.

Tokyo and Tōkyō

For 東京:

• Fully marked Hepburn-style form: Tōkyō
• Established international form: Tokyo
• Kana-based long-vowel spelling: Toukyou

A reference work may display Tōkyō, while most general English maps use Tokyo.

Busan and Pusan

For 부산:

• Revised Romanization: Busan
• McCune–Reischauer: Pusan

South Korea’s current public system uses Busan. Older maps, institutions, and historical scholarship may retain Pusan.

Kyiv and Kiev

For Київ:

• Ukrainian national Roman form: Kyiv
• Historical English form influenced by Russian: Kiev

The forms are associated with different source-language traditions. Current use should follow the Ukrainian official form, while historical documents should be quoted accurately.

Moskva and Moscow

For Москва:

• Direct Roman form: Moskva
• Conventional English exonym: Moscow

A Russian-language transliteration database may use Moskva. An English general-reference map normally uses Moscow.

Al-Qāhirah and Cairo

For القاهرة:

• Arabic geographic romanization: Al Qāhirah
• Conventional English exonym: Cairo

The choice depends on whether the map is presenting a local-name romanization or conventional English nomenclature.

Names With More Than One Official Language

Some geographic features lie in multilingual areas.

A city, river, mountain, or region may have official names in:

• Two national languages
• A national and regional language
• An Indigenous language
• Several local administrative languages

A multilingual map may:

• Display all official names
• Select the name appropriate to the map’s language
• Use a combined form
• Apply different labels at different scales
• Record every name in the database but show only one on the map

A data model should store language as an attribute of each name rather than assuming that a feature has only one name.

UNGEGN’s data-modeling guidance treats language and whether a form is an endonym or exonym as attributes of an individual name. It also emphasizes the importance of retaining native-script forms even where romanization is provided.

Cross-Border Geographic Features

Rivers, mountain ranges, lakes, and other features may cross political or linguistic boundaries.

The same feature may have:

• Different endonyms in different countries
• Different official spellings
• Several scripts
• A shared international name
• An exonym in the map’s language

For a cross-border feature, there may be no single local form valid for every part of the feature.

A database should therefore be able to connect:

• One geographic feature
• Several official names
• Different language areas
• Different jurisdictions
• Different spatial extents
• Variant Roman forms

Forcing one country’s name across the entire feature can produce misleading or politically sensitive results.

Disputed Territories and Sensitive Names

Geographic names can be politically sensitive because names may imply:

• Sovereignty
• Territorial control
• National identity
• Ethnic affiliation
• Historical claims
• Administrative legitimacy

A neutral geographic database should distinguish:

• Name approval
• Name source
• Jurisdiction
• Language
• feature coordinates
• political status
• map-display policy

The GNS explicitly cautions that names, variants, and associated data do not necessarily express a U.S. government position on sovereignty over a feature.

For sensitive features, a publication may need to:

• Use the form required by its editorial policy
• Display two competing names
• Add a neutral explanatory note
• Avoid implying recognition through typography alone
• Retain all major variants for search
• Record the source and date of each decision

Romanization software should not attempt to settle political disputes.

Indigenous and Minority-Language Names

Place names carry cultural and historical information.

An Indigenous name may encode:

• Physical characteristics
• Traditional land use
• Sacred meaning
• Flora or fauna
• An event
• Oral history
• Community identity

Standardization should not treat these names merely as text strings.

UNGEGN increasingly emphasizes the preservation and standardized use of culturally significant and Indigenous geographic names as part of cultural heritage and responsible national naming practice.

When romanizing an Indigenous or minority-language name:

• Identify the actual language.
• Use the community’s accepted orthography.
• Consult the relevant naming authority.
• Preserve the original script where one exists.
• Avoid applying the dominant national language’s pronunciation rules automatically.
• Record alternative and historical forms.
• Document consultation and source information.

Maps and Label Selection

A database may store many names, but a map cannot display all of them simultaneously.

Map editors select labels according to:

• Map language
• Scale
• Purpose
• Audience
• Available space
• Political policy
• Feature importance
• Name status
• Legibility
• Local or international context

Small-Scale Maps

A world map may favor:

• Country names
• Capitals
• Major cities
• Major seas and mountain systems
• Familiar conventional names

Large-Scale Maps

A detailed local map may show:

• Official local names
• Neighborhoods
• Minor streams
• Street names
• Indigenous names
• Administrative suffixes
• Diacritics and full local spelling

Tourist Maps

A tourist map may show:

• Official Romanized names
• Local-script forms
• Familiar English names
• Pronunciation assistance
• Transit-station spellings

Historical Maps

A historical map should use names appropriate to the period being represented, with modern equivalents supplied separately when necessary.

The Problem of Map Space

Long romanized names can create cartographic problems.

A single source character may require:

• A digraph
• A trigraph
• A diacritic
• An apostrophe
• A hyphen

A name that is compact in Arabic, Chinese, Cyrillic, or another script may become much longer in Roman letters.

Cartographers may respond by:

• Abbreviating generic terms
• Selecting a short official form
• Reducing font size
• Omitting lower-priority labels
• Using an established conventional name
• Displaying the local script only at larger zoom levels

These decisions should follow a style policy rather than altering the official spelling arbitrarily.

Diacritics on Maps

Diacritics may preserve essential distinctions.

Examples include:

• ā
• č
• ḍ
• ḥ
• ŏ
• ṣ
• š
• ṭ
• ū
• ž

Removing them may merge different source letters or names.

Modern Unicode-compatible mapping systems can usually store and display these characters, but practical problems remain:

• Incomplete fonts
• Poor search normalization
• Legacy databases
• Limited keyboards
• Inconsistent data imports
• Broken combining marks
• Uppercase conversion errors

BGN/PCGN guidance includes technical advice for software and operating systems that display approved geographic names containing Unicode special letters and diacritic combinations.

Best practice is to preserve the fully marked form and generate a separate unmarked search alias.

Geographic-Name Databases

A place-name database should separate the geographic feature from its names.

One feature may have many names, while one name may refer to different features.

Feature Record

The feature record may contain:

• Unique identifier
• Coordinates
• Geometry
• Feature class
• Country
• Administrative divisions
• Elevation
• Source
• Status

Name Record

Each linked name may contain:

• Name text
• Script
• Language
• Romanization system
• Name type
• Official status
• Start date
• End date
• Source authority
• Pronunciation
• Historical period
• Sort form
• Search form

UNGEGN’s data-modeling work emphasizes metadata, language identification, name status, provenance, and the relationship between a name and its geographic feature.

Recommended Data Structure

Field	Purpose
feature_id	Stable identifier for the geographic feature
original_name	Name in its native script
script_code	Writing system
language_code	Language of the name
romanized_name	Standard Roman form
romanization_system	Exact system and version
name_status	Official, approved, variant, historical or other
name_type	Endonym, exonym, conventional, short or long form
authority	Source naming authority
valid_from	Beginning of use
valid_to	End of use
ascii_name	Technical fallback
sort_name	Normalized ordering form
search_aliases	Additional discoverability forms
source_date	Date verified

A single place_name column is inadequate for serious multilingual mapping.

Search and Geocoding

Users often search for a place without knowing its official Roman spelling.

They may enter:

• An old name
• An exonym
• A spelling without diacritics
• A different romanization system
• A local-language form
• An English translation
• A common misspelling
• A name copied from an old book

A robust geocoder should connect these forms to the same feature where appropriate.

For example, searching for a city might reasonably match:

• Native-script name
• Official Roman form
• Conventional English name
• Historical form
• Diacritic-free form
• Alternative spacing
• Older romanization

This does not mean every variant should be displayed as the primary label.

Search and display serve different purposes.

Display Name

The authoritative or editorially selected form shown to the user.

Search Alias

A hidden or secondary form used to improve discovery.

Historical Alias

A previous form retained for research.

Sort Form

A normalized value used for alphabetical ordering.

The GNS supports searching by name, country, administrative division, feature characteristics, and spatial filters, illustrating the need to combine name matching with geographic context.

Geographic Names in URLs and SEO

A web page about a place may need several representations.

Example:

Field	Value
Original script	北京
Official Roman form	Beijing
Historical name	Peking
URL	/beijing/
Search aliases	Beijing, Peking, 北京, Pei-ching

Best practices include:

• Use the current primary name in the title.
• Preserve the original script in the article.
• Mention historically important variants naturally.
• Use one canonical URL.
• Redirect older-name URLs where appropriate.
• Avoid duplicate pages for every romanization.
• Add structured data with alternate names.
• Keep the URL stable after minor style changes.

A URL slug is a technical identifier, not a complete toponymic record.

Choosing the Right Geographic-Name Form

Use the following decision matrix.

Use case	Preferred starting point
Official national map	National naming authority
International map	National form plus relevant international guidance
UK or U.S. official foreign-name use	Applicable BGN/PCGN decision
Historical map	Name valid during the represented period
Tourist map	Official Roman form plus useful local script
Academic publication	Declared system appropriate to the discipline
News article	Current official or established editorial form
Search engine	Original name plus all significant aliases
Navigation application	Official local form, approved display form and searchable variants
Library catalog	Applicable bibliographic romanization standard
Multilingual atlas	Language-specific label policy
Disputed feature	Declared neutral or institutional policy with alternatives
Indigenous feature	Community-supported and officially recognized form

A Practical Geographic-Name Workflow

Step 1: Identify the Feature

Confirm:

• Coordinates
• Feature type
• Country or territory
• Administrative area
• Whether similarly named features exist

Step 2: Find the Official Local Name

Use:

• National gazetteer
• Mapping authority
• Government database
• Local administrative source
• Hydrographic authority
• Official signage

Step 3: Identify the Language and Script

Do not assume the language from the country alone.

A feature may have names in several languages.

Step 4: Check for an Official Roman Form

The country may already publish a Roman-script name.

When an officially implemented form exists, it should usually take priority over a newly generated conversion.

Step 5: Select the Appropriate Standard

Possible standards include:

• National romanization
• UN-recommended system
• BGN/PCGN system or agreement
• Library standard
• Publisher style

Step 6: Check Conventional Names

Determine whether the target language uses a widely established exonym.

Decide whether the publication’s policy prefers:

• Endonyms
• Conventional names
• Both forms on first mention

Step 7: Preserve Variants

Record:

• Historical names
• Previous official names
• Alternative romanizations
• Minority-language names
• Local-script names
• Common misspellings where useful for search

Step 8: Record Provenance

Store the authority, source document, system version, and verification date.

Step 9: Apply the Map Style

Define:

• Capitalization
• Diacritics
• Generic terms
• Hyphenation
• Abbreviations
• Label hierarchy

Step 10: Review Sensitive Cases

Escalate names involving:

• Disputed sovereignty
• Recent official change
• Indigenous naming claims
• Cross-border features
• Conflicting national standards
• Unclear language identification

Best Practices for Romanization.org

Romanization.org should present geographic names as structured name records, not isolated conversion results.

Preserve the Original Name

Always display the local-script form.

Identify the Feature

Include:

• Feature type
• Country or territory
• Administrative area
• Coordinates where appropriate

Identify the Language

A script alone may support several languages.

Name the Standard

Use precise labels such as:

• Hanyu Pinyin
• Japan 2025 Roman-letter table
• Revised Romanization of Korean
• BGN/PCGN Russian
• BGN/PCGN Arabic
• Ukrainian national system
• UN-recommended system
• ALA-LC library form

Separate Name Categories

Show:

Category	Example purpose
Official local name	National use
Official Roman name	International national use
Standardized romanization	Conversion result
English conventional name	English publishing
Historical name	Archive research
Alternative system	Comparison
ASCII form	Technical use

Show System Versions

Romanization systems change. Record the adoption year, revision, or agreement date.

Preserve Diacritics

Generate an ASCII alternative separately.

Include Name Status

Use labels such as:

• Official
• Approved
• Variant
• Historical
• Conventional
• Disputed
• Minority-language
• Local

Avoid Political Conclusions

The tool should explain naming sources without presenting a romanization result as a ruling on sovereignty.

Show Information-Loss Warnings

Examples:

• Diacritics removed
• Original spelling not reversible
• Conventional English name shown
• Historical form
• Multiple official languages
• Transliteration system uncertain

Common Mistakes

Using One Romanization Table for Every Language in a Script

Cyrillic, Arabic script, and Han characters each support multiple languages.

Treating an Exonym as a Direct Romanization

Moscow is not the direct romanization of Москва. Moskva is.

Treating a Romanization as a Translation

A place-name meaning should be stored separately from its Roman-script form.

Deleting Historical Names

Former names remain necessary for research and search.

Applying a Library Standard to a Road Map

Bibliographic and cartographic systems have different purposes.

Removing Diacritics From the Authoritative Record

Keep a marked display form and an unmarked search form.

Assuming One Official Name Per Feature

Multilingual regions and cross-border features may have several official endonyms.

Changing Names Without Recording Dates

Name changes require temporal metadata.

Ignoring Map Language

An English atlas, national road map, historical map, and multilingual tourist map may legitimately select different labels.

Treating Geographic Names as Politically Neutral Strings

Some names carry strong cultural, historical, and territorial implications.

Creating Separate Features for Every Name Variant

Variants usually belong to one feature record unless they genuinely identify different geographic entities.

Frequently Asked Questions

What is toponymy?

Toponymy is the study and administration of geographic or place names.

What is the difference between a geographic name and a romanization?

The geographic name identifies the feature. Romanization is one method of representing that name in Roman letters.

What is an endonym?

An endonym is a name used in an official or well-established language in the area where the feature is located.

What is an exonym?

An exonym is a name used by another language community for a feature outside its language area when that form differs from the locally used name.

Is an English exonym incorrect?

Not necessarily. It may be a long-established English name. The appropriate form depends on the map’s language and editorial policy.

What is UNGEGN?

UNGEGN is the United Nations expert body supporting national and international standardization of geographic names.

Does the United Nations invent place names?

Its approach generally supports nationally standardized names and internationally agreed systems rather than independently inventing local names.

What is BGN/PCGN?

BGN/PCGN refers to jointly developed or approved geographic-name romanization systems used by U.S. and UK authorities for foreign names.

What is the Geographic Names Server?

The GNS is the official repository of foreign geographic-name decisions approved by the U.S. Board on Geographic Names. It includes current, variant, historical, and non-Roman forms.

Why does one city have several Roman spellings?

The spellings may come from different languages, historical periods, romanization systems, or conventional foreign names.

Should maps always use local names?

Many official and international maps prioritize standardized local forms, but language-specific maps may retain established exonyms according to editorial policy.

Should historical maps be updated to modern names?

Not when the historical name is part of the map’s subject. A modern equivalent can be added as a note or linked database field.

Should diacritics be kept?

Yes, when required by the selected standard. An unmarked search or ASCII form can be generated separately.

How should a disputed place name be handled?

Follow a declared institutional policy, cite the relevant authorities, retain major variants, and avoid treating the spelling as an unsupported political judgment.

Can romanization be generated automatically?

Often, but reliable output may require language identification, contextual readings, national exceptions, official-name lookup, and human review.

Which name should be used for SEO?

Use the current primary name in the title and canonical URL, while including significant historical, native-script, conventional, and alternative names naturally for discovery.

Can one place have several official names?

Yes. Multilingual jurisdictions and cross-border features may have multiple official endonyms.

Final Checklist

Before publishing a romanized geographic name, verify:

• The geographic feature has been identified correctly.
• The original-script name has been preserved.
• The source language has been identified.
• The national naming authority has been checked.
• An official Roman-script form has been sought.
• The exact romanization system has been named.
• The system version or adoption date has been recorded.
• Conventional exonyms have been distinguished from romanizations.
• Historical names have been preserved.
• Minority and Indigenous forms have been considered.
• Diacritics have not been removed from the only stored form.
• Search aliases are separate from the display name.
• Name order, spacing, and hyphenation follow the relevant rules.
• Cross-border and disputed features have received special review.
• The source authority and verification date have been recorded.

Conclusion

Romanizing a geographic name is not simply a matter of converting letters.

A geographic name exists within a network of:

• Languages
• Writing systems
• Governments
• Communities
• Maps
• Historical periods
• International standards
• Cultural identities
• Political contexts
• Geographic databases

The official local name may coexist with a national Roman form, a UN-recommended spelling, a BGN/PCGN form, an English exonym, and several historical names.

Each serves a different purpose.

A modern map may use Beijing, while an archive must recognize Peking. A Russian transliteration database may use Moskva, while an English atlas uses Moscow. A local Arabic record may contain القاهرة, an international geographic system may produce Al Qāhirah, and an English publication may use Cairo.

A trustworthy geographic-name reference should therefore preserve:

1. The original local-script name
2. The language and script
3. The nationally standardized Roman form
4. The exact romanization system
5. Conventional names in other languages
6. Historical and alternative forms
7. Name status and authority
8. Geographic coordinates and feature identity
9. The date and source of each naming decision

Romanization.org should not merely convert a place name. It should explain the toponymic record behind it: who uses the name, which system produced the Roman form, what alternatives exist, and which spelling is appropriate for a particular map, database, publication, or historical context.

FAQ

What is the difference between an endonym and an exonym?

An endonym is the name used locally for a place, written in the local language or script. An exonym is the name used in another language, often adapted to that language’s spelling and pronunciation.

Which romanization system should I use for Chinese place names?

For official Chinese geographic names, use the nationally standardized Hanyu Pinyin system. For historical or non‑official contexts, older systems such as Wade‑Giles may appear.

How does UNGEGN influence geographic name romanization?

UNGEGN develops and recommends internationally usable romanization systems for each non‑Roman script, aiming for scientific soundness, official support, and reversibility.

When should I retain an English exonym instead of the romanized local form?

Retain an English exonym when it is widely recognized, historically entrenched, and improves user comprehension, especially in English‑language publications.

What is the recommended priority order for selecting a geographic name for a map?

1. Official name in original script, 2. Official national Roman form, 3. Nationally approved romanization, 4. UN‑recommended or BGN/PCGN form, 5. Established conventional English name, 6. Historical/minority variants.