Global Locations Database in scoreio: 43,000 Cities with Bilingual Search

It looks like a trifle — picking a city in a registration form. Yet this is exactly the step where participants get stuck more often than anywhere else. A long dropdown with no search, in which the right city is missing — or present, but spelled in an unrecognizable way — turns a simple action into a quest. We rebuilt this node completely: scoreio now has a global locations database — 218 countries, 1,558 regions and 43,230 cities with names translated into Russian and English, and selection is handled through cascading lists with substring search.

How It Used to Be

City selection used to be one of the form's most painful spots. The city list was long and had no search: to find their town, a participant scrolled through dozens or hundreds of entries by eye. For a large region that meant literally minutes on a single field — and a high risk of picking the wrong city out of sheer fatigue.

City translations were a separate problem. They were stored right in the interface translation file — meaning every new name had to be added by hand, and it simply couldn't scale. Coverage was incomplete: for many cities no English spelling existed at all, and a foreign participant saw Cyrillic where they expected Latin script. Adding a new country or region meant editing files rather than simply topping up a reference book.

The upshot: a form built for an international audience worked against it at the "choose your city" step — a Russian-speaking participant scrolled for ages, and a foreign one couldn't find a familiar spelling.

What Changed

We moved geography into a proper structured database and made location selection fast and predictable — no matter where in the world a team registers from.

Global Coverage: 218 Countries, 1,558 Regions, 43,230 Cities

At the core is a single geographic reference: 218 countries, 1,558 regions and 43,230 cities. This isn't a hand-built list for one country — it's a global database built for international events. A participant from any country finds their location in it.

Names Translated into Russian and English

Country, region and city names are stored with translations in dedicated translation tables — not in the interface translation file, as before. That means geography scales separately from button labels and isn't bottlenecked by manual upkeep. A Russian-speaking participant sees familiar Cyrillic; an English-speaking one sees correct Latin script.

Cascading Country → Region → City Lists

Selection is a cascade: first the country, then the region, then the city — each next list filtered by the previous one. For brands with a simplified form, a short Country → City cascade is available without the intermediate region step. Either way, the participant doesn't pick a city from a single list of tens of thousands — they work only with a relevant subset.

Substring Search

The key convenience is search within the list. The participant starts typing a name, and the list instantly narrows to substring matches. For a reference of thousands of cities this is critical: what used to be minutes of scrolling now takes a couple of seconds of typing.

Fallback: If There's No English Name, the Russian One Is Shown

Translation coverage isn't one hundred percent, so we built in a safety net. If a city has no English name, the Russian one is shown instead of an empty value — the participant always sees a readable label, not a blank. The form doesn't "break" on a rare town.

Idempotent Import with No Duplicates

The database is populated by import from a global geographic reference, and that import is idempotent — re-running it doesn't spawn duplicates. The reference can be topped up and updated without fear of ending up with two identical cities in the list. Adding a new country or region is a matter of extending the database, not editing code.

What This Gives You

• Seconds instead of minutes to pick a city. Substring search removes the scrolling of long lists — a participant finds their town in a couple of keystrokes.
• Fewer data errors. When a city is chosen from a structured database with search, the share of "wrong" cities picked out of fatigue or by mistake drops sharply.
• Readiness for an international audience. 218 countries and 43,230 cities with translations mean a participant from any country finds their location in their own language — with no per-market rework.
• No empty fields. The fallback to the Russian name guarantees a readable label even for cities without an English translation.
• Clean data on updates. Idempotent import rules out duplicates, so the reference can be expanded with confidence.

Scenarios Where This Solves the Problem

A large national event with hundreds of entries. Teams arrive from dozens of cities within one big region. Earlier, each participant spent a minute scrolling a shared list; now they type the first letters of the name and pick the city from a filtered list in seconds. Across hundreds of entries that saves hours of combined time and eliminates the stream of "you picked the wrong city" corrections.

An international tournament. Clubs from different countries register. Each picks their country, then region and city — in their own language, thanks to the translations. A foreign coach sees Latin script, a Russian one sees Cyrillic, and neither hits an unfamiliar spelling.

Entering a new market with no rework. An organizer accepts teams from a country they've never worked with before. That country's cities are already in the global database with translations — no separate reference prep is needed, and the form is ready to accept the participant right away.

Frequently Asked Questions

How many countries and cities are in the database? 218 countries, 1,558 regions and 43,230 cities. Names are stored with Russian and English translations in dedicated translation tables.

Is there a city search? Yes. The dropdowns support substring search — the list narrows instantly as you type. For a reference of thousands of entries this is the key convenience.

What happens if a city has no English name? The fallback kicks in: the Russian name is shown instead of an empty value. The participant always sees a readable label.

How does selection work — is the region required? By default it's a Country → Region → City cascade. For brands with a simplified form, a short Country → City variant is available without the region step.

Can new locations be added? Yes. The database is populated by import from a global geographic reference, and the import is idempotent — re-running it creates no duplicates.

The Bottom Line

City selection is no longer the weakest spot in the registration form: a global database of 43,230 cities with translations and substring search turns an agonizing scroll into a couple of seconds of typing — and makes the form equally convenient for a participant from any country. It works in tandem with other platform capabilities: labels and the form itself are localized as part of full RU/EN localization, the simplified Country → City cascade is enabled through white-label settings, and fast responsive lists are part of the new platform engine.

Accepting participants from different regions and countries? Request a demo or a pilot launch of scoreio — we'll show how city search and cascading location selection work for your disciplines and your audience.