Match Review · 06

How to fix unmatched or ambiguous map names

A reliable data map keeps uncertain place names visible instead of guessing which boundary should receive the value.

The short answer

Check the map source, final administrative level, and parent scope before changing the text. Then compare the original input with the standardized map name. Use a complete name, a supported alias, or a common code only when the intended area is clear.

First check
Level and scope
Safe rule
No silent guessing
Review
Original + matched

Understand the three review states

StatusMeaningAction
MatchedOne candidate exists in the current scopeConfirm the standardized name and value
AmbiguousSeveral candidates remain possibleAdd the parent place or full official name
UnmatchedNo candidate exists at this level and scopeCheck source, level, spelling, and language

These states are part of the workflow, not errors to hide. A visible unresolved row is safer than a plausible but incorrect colored area.

Verify map source, level, and parent scope

A county name cannot match while the final level is set to Province. A city outside Guangdong cannot match if Guangdong is the only parent scope. Correct the selection before repeatedly editing the input name.

  • World Map: countries and regions.
  • First-level Divisions: states, provinces, regions, departments, and equivalent units.
  • Detailed China Map: provinces, prefecture-level cities, and counties.

Use complete names before relying on fuzzy forms

EasyMap can normalize common suffix differences and accept unique contained names inside the current scope. This makes 广州 match 广州市 or 南沙 match 南沙区 when only one candidate exists. It must not force a result when several areas remain possible.

Reliable sequence: full exact name → normalized unique name → unique contained name. Misspellings and multiple candidates stay visible for review.

Separate input language from display language

The original-input column preserves the user text. The matched-area column follows the selected administrative-name language. A Chinese input can therefore be reviewed against an English display name, or an English country name against a Chinese label, without rewriting the source row.

Correct rows without losing the draft

Switching between paste and file input should not clear the existing draft. Edit values in Match Review, click a map feature to locate its row, and save a local project only when the current state is worth keeping. Resolve ambiguous rows before export.

Authoritative sources and further reading

These sources support the data-format, classification, labeling, or public-map guidance on this page.

Common questions

Why does a correct name remain unmatched?

The most common cause is the wrong map source, final level, or parent scope rather than spelling. Check those three settings first.

Will EasyMap automatically choose between duplicate names?

No. When multiple candidates remain, the row stays ambiguous so the user can narrow the scope or provide a fuller name.

Review before styling

Confirm every place before trusting the colors

Start with the correct level and parent scope, then resolve only the rows that remain uncertain.

Open Match Review →