---
metadata:
  - name: generator
    content: Diplodoc Platform v5.48.2
alternate:
  - https://yandex.com/support/mapeditor/en/attr_name.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com/support/mapeditor/en/llms.txt

# 3.1.3. Map item naming rules

All items on Yandex Map Editor have a <q>Name</q> attribute, even though some of them (such as forests) may not have names. 

{% note alert %}

Any map item names that contain vulgar language; incite violence; promote hostility; or disparage a person or group based on their gender, race, nationality, language, origin, religious beliefs, or membership in a particular social group are **forbidden**. This includes obscenities where part of the letters are replaced by stars or other symbols, yet the intended meaning is read and understood by native speakers.

{% endnote %}

When you enter the name of an item, you must refer to the [techniques for naming items](https://yandex.com/support/mapeditor/en/attr.md#name_object) as well as the following guidelines:

- [3.1.3.1. Name types: general rules](#name_rules_3.1.3.1)
- [3.1.3.2. Rules for entering all types of names](#names_all_3.1.3.2)

Rules for various types of items are described in the subsections of section [3. Global mapping rules](https://yandex.com/support/mapeditor/en/rules_2.md#rules_2).

## 3.1.3.1. Name types: general rules {#name_rules_3.1.3.1}

There are several types of map item names:

- [3.1.3.1.1. Official](#3.1.3.1.1)
- [3.1.3.1.2. For caption on map](#3.1.3.1.2)
- [3.1.3.1.3. As part of the address](#3.1.3.1.3)
- [3.1.3.1.4. Abbreviated](#3.1.3.1.4)
- [3.1.3.1.5. Renaming](#3.1.3.1.5)
- [3.1.3.1.6. Also known as, historical](#3.1.3.1.6)

### 3.1.3.1.1. Official {#3.1.3.1.1}

#### 3.1.3.1.1.1 {#3.1.3.1.1.1}

 
Enter **Official** names for each of the languages you're adding the item name in (other than in the exceptional case described under [3.1.3.1.1.4](#3.1.3.1.1.4)).

#### 3.1.3.1.1.2 {#3.1.3.1.1.2}

 
You should enter the **full official** item name.
    
    
    
Do not map descriptive names, technical names, or names indicating an item's location relative to other nearby items even if they are confirmed by official sources, except in cases where:

- There are child items linked directly to them.

- The descriptive administrative division unit name is the address of an organization (that receives external visitors) that has no specific house number but is listed in official documents and other sources (for example, news websites or organization websites).
    
    
    
These item types include: forestry district numbers, territories <q>near a locality</q>, fields, bridges, tunnels, and squares with names like <q>Bridge at...</q>.
    
    
    
Examples:
    
    
- _Forecourt Park_ in Pokhvistnevo (this is a descriptive name because it indicates the location of the park).
- 1 Minskoe Highway, 35 km + 500 meters (despite the fact that the address indicates the item's location relative to other local items, it is confirmed by the register and mentioned on the organization's website).
    
    <q>Minskoe Highway, 35 km + 500 meters</q> is marked on the map as a level 7 division (Block).

 
As an exception, you can name point, linear, and polygonal bridges, tunnels, squares, hydrography, vegetation, and relief items as well as streets in localities without official names if they are used as city landmarks in official documents (as well as in media and public transport stop names) or on major local internet forums and websites, provided the naming is consistent across all sources. If the name of an item is only mentioned in historical sources, don't name it on the map.

 
{% note info %}
    
In some rare cases, employees can list multiple versions of the item's proper name in the **Official** field. In this case, one of them is written in parentheses.
    
{% endnote %}

#### 3.1.3.1.1.3 {#3.1.3.1.1.3}

 
The official name generally includes the type of item.

 
The item type is not included with the following names:
    
    
    
- items whose names never include their item type (whether it's official documentation or everyday speech). Examples: Wilhelmstraße road, Marsh Wall, Stoney Summit
    
    {% note info %}
    
    Items located in Russia, Ukraine, Belarus, Moldova, Kyrgyzstan, or Kazakhstan should always use an item type. The type is also always specified for names written in Russian, Ukrainian, Belarusian, Kyrgyz, and Kazakh.
    
    {% endnote %}
    
- Items whose proper names already contain their type.
    
    For example, Salt Lake City (the <q>City of</q> type is omitted).
    
- Ground transport stops (see point [3.14.2.2.1](https://yandex.com/support/mapeditor/en/cat_tram_rul2.md#3.14.2.2.1)).

 
With items of the <q>Location</q> type, only include the type in the official name if it's used to clarify a [category](https://yandex.com/support/mapeditor/en/app_poi.md#app_poi). For more information, see [3.6.2.2.3.2. Name formatting](https://yandex.com/support/mapeditor/en/cat_organizations_rul2.md)

Official names of railway platforms don't include the type.

 
{% note info %}
    
The policy for items whose type is not clear is described in Section [4. Rules for regional mapping](https://yandex.com/support/mapeditor/en/rules_3.md#rules_3).
    
{% endnote %}

#### 3.1.3.1.1.4 {#3.1.3.1.1.4}

 
Don't set an official name if the item doesn't have a proper name or the name's unknown.

 
This rule doesn't apply to administrative divisions and the items ([Places](https://yandex.com/support/mapeditor/en/cat_organizations_rul2.md#cat_organizations_rul2)) of the following categories: _Medicine and pharmaceutics, Education and science, Finance, Trade, State and society, Religion, Food, Auto, Sport, Culture and attractions, Leisure and tourism, Businesses and services, Construction and realty, Production and materials_. 
    
{% note alert %}
    
**Don't** set other types of names for objects that don't have an official name.
    
{% endnote %}

#### 3.1.3.1.1.5 {#3.1.3.1.1.5}

 
Abbreviations are not used in official names, with the exception of:

 
- Initials (including the first letter of a name).
    
- Abbreviations that are commonly known (such as UNESCO, UN, MIT, and so on).
    
    Abbreviations that are not commonly known must be spelled out in official names.
    
    {% note info %}
    
    Some terms that are abbreviations in one language may not be abbreviations in other languages (for example, names of the cardinal directions such as NW, SW, and so on).
    
    The official name for such an item in English and Russian must be set as follows: <q>NW Street</q> and <q>Severo-Zapadnaya ulitsa</q>, respectively.
    
    {% endnote %}

#### 3.1.3.1.1.6 {#3.1.3.1.1.6}

 
If an item has more than one name (for example, it might have a historical or local name in addition to the official one), then enter the second name under the <q>also known as, historical</q> type using the same language).

### 3.1.3.1.2. For caption on map {#3.1.3.1.2}

The **For caption on map** name type is used if the item's caption on the map should differ from the official name.

Only enter names in the **For caption on map** type when it is explicitly required by the naming rules for a particular layer and country.

{% note info %}

In some rare cases, employees can list multiple versions of the item's proper name in the **For caption** field. In this case, one of them is written in parentheses.

{% endnote %}

### 3.1.3.1.3. The address contains {#3.1.3.1.3}

Set the names of the **Address contains** type for administrative divisions, the names of which, when used in the address, differ from the official name (see also [3.2.2.2.5](https://yandex.com/support/mapeditor/en/cat_adm_rul2.md#3.2.2.2.5)), and for rapid transport stations (see p. [3.13.2.2.2](https://yandex.com/support/mapeditor/en/cat_speed_rul2.md#m_el_3.13.2.2)).

For example, if a locality has the <q>City</q> status (see [3.2.2.5. Administrative divisions as cities](https://yandex.com/support/mapeditor/en/cat_adm_rul2.md#3.2.2.5)), the **Address contains** field should only include the locality's proper name without the type:

- Official name — _City of Moscow_
- The address contains — _Moscow_.

For rapid transit stations, specify **The address contains** name in the format <q>type + proper name</q>. For example:

- Official name — _Tyoply Stan_
- The address contains — _Metro Tyoply Stan_.

**Don't enter** a name in this field for other types of map items.

### 3.1.3.1.4. Abbreviated {#3.1.3.1.4}

The **Abbreviated** name field is **not currently in use**.

### 3.1.3.1.5. Previously called {#3.1.3.1.5}

The **Previously called** field is only used in cases where the official name of an item recently changed.

For example: the city of Dnipro was called _Dnepropetrovsk_ until recently, and the sub-district of Savchenko was previously _Molodogvardeyets_.

{% note info %}

The following time limits apply to this category:

- For cities, districts, and villages ~ 5 years.

- For small localities ~ 3 years.

- For streets and squares ~ 2 years.

- For metro stations and railways ~ 2 years.

- For vegetation, hydrography, and terrain ~ 2 years.

{% endnote %}

### 3.1.3.1.6. Also known as, historical {#3.1.3.1.6}

Use the **Also known as, historical** type to enter well-known alternate, local, or historical names, legacy names that are still in use, and official registered organization names.

{% cut "Examples" %}

- Well-known alternate and local names: _Chuvashia_ for the Chuvash Republic, _Yekb_ and _Yekat_ for Yekaterinburg, _Piter_ and _SPb_ for Saint Petersburg, _Kompros_ for Komsomolsky prospekt, and so on.
- Historical names: _Alma-Ata_ for Almaty, _Leningrad_ for Saint Petersburg, _Vyatka_ for Kirov, and so on.
- Long-standing former names still in use: _ulitsa 9 Yanvarya_ for ulitsa Borisa Yeltsina in Yekaterinburg (ulitsa Odinarnaya and ulitsa Fetisovskaya aren't added as "Also known as, historical" names because they are no longer in use); _16А_ for building No. 28 after an address renumbering.
- Registered organization name: _AO Tander_ for the Magnit supermarket.

{% endcut %}

If new administrative divisions are formed in place of older ones, you can set the older names as synonyms for the newer ones as long as the old names are still in use locally.

Don't enter a name in the "Also known as, historical" field if it's an official name of another item on the same layer and that item is located:

- In the same country (for the administrative division layer).
- In the same populated place (for all other layers).

{% note info %}

Time periods that must pass before a name is considered "no longer in use":

- For regions and districts ~ 15 years
- For streets and squares ~ 30 years.
- For address points ~ 15 years.

- For railway stations and public transport stops ~ 5 years.

- For hydrographic items, vegetation, and relief ~ 100 years.

- For localities and metro stations, there is no minimum number of years that must pass before a name is considered "no longer in use".

{% endnote %}

## 3.1.3.2. Rules for entering all name types {#names_all_3.1.3.2}

- [3.1.3.2.1. Language](#3.1.3.2.1)
- [3.1.3.2.2. Rules for entering names](#3.1.3.2.2)

### 3.1.3.2.1. Language {#3.1.3.2.1}

If you enter the item name in any language, it will be displayed on Yandex Maps. If a user selects a language for which you haven't added a name, the item will be automatically transliterated in that language in the end product.

{% note alert %}

Rules for adding names in a specific country are also the rules for adding names in the language of this country.

For example, adding a Russian name to an item in France should be done according to the rules for adding names in the territory of Russia.

{% endnote %}

#### 3.1.3.2.1.1 {#3.1.3.2.1.1}

 
Names and attributes of map items within a given country **must** be written in at least one of that country's official languages (or in Russian or English).
    
    
    
You also have the option to enter names in any language available on Yandex Map Editor.
    
    
    
If an item name consists exclusively of numbers, it's only set in the local language.
    
    
    
If a house number without letters is specified in the address point in more than one language, you may keep the extra names, but it's preferable to specify it in only one language.
    
    
    
For example, the village of _Vysokaya gora_ can also be named _Biektau_ in Tatarstan.
    
    
    
For territories that different states recognize differently, set the locally used name (in the local language) for toponyms. Don't enter names for such items in other languages without specifying the name used locally.
    
    
    
{% note info %}
    
If an organization name doesn't contain a toponym, you can set its name in any language.
    
{% endnote %}

#### 3.1.3.2.1.2 {#3.1.3.2.1.2}

 
In countries where the national language uses both the Latin and the Cyrillic alphabets, the preferred option is to write names twice (using each alphabet).
    
    
    
{% note info %}
    
If an item name contains only Cyrillic letters and numbers, you can enter it for one language (such as Russian) and not repeat it for another (such as Ukrainian).
    
{% endnote %}

#### 3.1.3.2.1.3 {#3.1.3.2.1.3}

 
In countries where the national language uses **an alphabet other than Latin or Cyrillic**, you can **enter the name** twice using both the national alphabet and Latin (or just enter it using Latin letters).

#### 3.1.3.2.1.4 {#3.1.3.2.1.4}

 
Naming organizations (companies, institutions, establishments).
    
    
1. If an organization officially uses an adapted brand name (translation into the national language of the country of presence), it should be indicated as its official name.
    
    For example, for the Russian Federation: _Касторама, Вестерн Юнион_.
    
    You can also enter the official name of the organization in its <q>native</q> language or using Latin script.
    
    For example:
    - Official, Russian: _Ресторан быстрого питания Макдоналдс, ИКЕА_
    - For caption, Russian: _Макдоналдс, ИКЕА_
    - Official, English (advanced): _McDonald's, IKEA_
    
1. If the organization officially uses the brand name in its native language in the region of presence, it should be specified as the official local name.
    
    For example, for the Russian Federation: _Nike, Dunkin’ Donuts_.
    
    If necessary, the official name may also include the type of organization written in the national language of the country being mapped (for example, for the Russian Federation: <q>Store</q>).
    
    You can also enter the official name of the organization in its <q>native</q> language or using Latin script.
    
    In addition, a transliterated name may be entered as the <q>Also known as</q> name in the national language of the country being mapped.
    
    For example:
    - Official, Russian: _Nike, Qiwi_
    - For caption, Russian: _Nike, Qiwi_
    - Official, English (additional): _Nike, Qiwi_
    - Also known as, Russian (additional): _Найк, Киви_
    
    
    
For clarity, here are examples for setting names according to the rules in Kuwait:
    
    
- Example 1 —
    
    - Arabic, official: ماددونالدد
    - English, official: _McDonald's_
    - Russian, official: _Макдоналдс_
    
- Example 2 —
    
    - Arabic, official: اللنسياغا
    - English, official: _Balenciaga_
    - Russian, official: _Balenciaga_

#### 3.1.3.2.1.5 {#3.1.3.2.1.5}

 
If the **traditional name** of a foreign administrative division (such as a city) is used in the language (especially in the media) much more frequently than the name in the official dictionary of names, then you should enter the more common variant under the <q>official, for caption, and address contains</q> fields. In this case, enter the name from the dictionary in the <q>also known as</q> field.
    
    
    
{% note info %}
    
You can use tools like [https://wordstat.yandex.ru](https://wordstat.yandex.ru) in Russia to view search statistics on name usage.
    
{% endnote %}
    
    
    
For example:
    
    
    
- _Official, English: City of Aleppo_
- _For caption on map, English:_
- _Address contains, English:_
- _Also known as, English: City of Halab_

#### 3.1.3.2.1.6. Rules for name transcription and translation {#3.1.3.2.1.6}

 
If the country you're mapping has a definitive official document regulating translation and transcription of its place names into other languages, then it takes precedence over the Rules. That being said, it is best to add translations of names done according to the general rules to the **Also known as, historical** field.
    
    
    
The names of items located on disputed territories are translated into the languages of neutral countries based on the position of the country into whose language the name is translated.
    
    
    
{% note info %}
    
In rare cases, the translated or transcribed name may be set as the item's official name, even if that contradicts this rule.
    
{% endnote %}

 
:   **3.1.3.2.1.6.1** {#3.1.3.2.1.6.1}
    
     
    :   Use **practical transcription** when transcribing names, i.e. relay the names of the source language by using the historical conventions of the target language's writing system.
        
        
        
        {% note info %}
        
        In regions where Russian is actively used along with the local language, you can decline names when specifying commonly accepted names in Russian.
        
        
        
        - _Cyrillic characters: Ш. Уәлиханов көшесі_.
        - _Using Latin characters: Sh. Ýálıhanov kóshesi_;
        - _Russian: улица Ш. Уалиханова_.
        
        {% endnote %}
        
        
        
        Practical transcription should be based on the common symbols (letters) of the target language, with no extra additions.
        
        
        
        When transcribing diacritics within the same alpabet, the diacritics are omitted.
        
        
        
        When transcribing into Russian, use Cyrillic letters that come closest to retaining the word's original sound as well as possible writing conventions or traditions of the source language.
    
    **3.1.3.2.1.6.2** {#3.1.3.2.1.6.2}
    
     
    :   1. When you translate the official name of an item, you should transliterate the proper name of the item and translate the item type (if it exists and is not part of the item's proper name).
        
            Examples of official name translations:
        
            - _Rue du Faubourg Saint-Martin (FR) — Du Faubourg Saint-Martin Street (EN)_.
            - _площадь Гагарина (RU) — Gagarina Square (EN)_.
        
            When translating item types, please take local naming into account. If there is a specific name used for your item in the region, you should use that name. If there is no specific naming convention, translate with a name commonly used for such items. You need to also take into account the language-specific word order in the name (<q>type</q> + <q>proper name</q>, or <q>proper name</q> + <q>type</q>) and maintain it when naming the item.
        
            {% note info %}
        
            You can omit the type in the item name when translating it into nonlocal languages (except Russian, Ukrainian, Belarusian, Kyrgyz, and Kazakh) if it isn't used or its spelling is unknown.
        
            {% endnote %}
        
            Caption names are specified according to the general rules. For example:
        
            - Official name: _Park Kultury Metro Station, Fabriki Pervogo Maya Settlement._
            - Caption name: _Park Kultury, Fabriki Pervogo Maya._
        
        1. If an item type is already included in the item name of a public transport stop, translate the item type, but transcribe the proper name.
        
            Example: _Кинотеатр Рубин ─ Rubin Cinema, Улица Горчакова ─ Gorchakova Street_.
        
        1. Enter less common translations and transcriptions in the <q>Also known as, historical</q> field.
        
            If a less common translation or transcription was initially set for an item, don't delete it when adding a correct name. Instead, transfer the old name to the <q>Also known as, historical</q> field.
        
            Avenue of the Americas ─ _6th Ave._, Kantschtrasse ─ _Kantstr._
        
        1. When translating numerals, keep in mind the numeral abbreviation rules of the language you're translating to. If an item name combines a numeral with a letter, do not translate (transcribe) the letter.
        
            Example: _1-я Новокузьминская улица_ → _1st Novokuzminskaya Street_, _3J Street → улица 3J_.
        
        1. Do not transcribe single-letter street notation or administrative division units.
        
            For example: _Avenue F → авеню F; Cluster B → кластер B_.
        
        1. You should give a full translation to names of items that belong to the <q>places</q> category, don't have a proper name, and use their item type instead.
        
            For example: unnamed flower shop, official name _Цветы → Flowers_.
        
        1. If the item name consists of two parts containing numerals, then in the translation, both parts are given in the nominative case. The numeral in the additional part is entered without a suffix.
        
            For example:
        
            - Official, Russian: _4-й переулок 1-й улицы_ or _1-я улица, 4-й переулок_
            - Official, English: _1st Street Lane 4_
        
        1. If an item has a commonly recognized translation, it should be specified as the official name (for example, _Красная площадь_ → _Red square_).
        
            If an item name contains an abbreviation that has no commonly recognized equivalent in Russian, leave the abbreviation in its original form when translating it (write it using Latin characters).
        
            At the same time, the rest of the name that doesn't contain the abbreviation is translated or transcribed according to the general rules for naming items on the map, and the caption name is not specified.
        
            For example: _JVT District 4 → район JVT 4_.
        
        1. The rules for using initials in each language are determined by official documents. If the exact spelling is unknown, you can set the initials used locally.
        
            If the format of spelling name or initials (and whether they're used at all) is different for different languages, follow the name format in each language.
        
            For example:
        
            - _Мұхаиед Хайдар Дулати көшесі (Kz)_
            - _улица Дулати (Ru)_
        
        1. When translating Russian item names to other languages, omit the word <q>имени</q> for items on all layers except administrative division.
        
            For example:
        
            - _Улица имени Генерала Костицына — Generala Kostitsyna Street_
            - _Посёлок имени Куйбышева — Imeni Kuybysheva Settlement_
        
        1. When adding a name in a new language, you can ignore errors in the transcriptions/translations of names already specified for that item, provided that the toponym names themselves are not different (for example: translated to English, the same island is called <q>Green</q> in one language and <q>Faraway</q> in another).
		
		1. If you rename an item, make sure to update the official name in every language that you've already added. If you cannot create a new name in one of the languages (for example, by translating the item type and transliterating its proper name), delete the outdated name for that language.



### 3.1.3.2.2. Rules for entering names {#3.1.3.2.2}

#### 3.1.3.2.2.1 {#3.1.3.2.2.1}

 
Proper names of items are **never enclosed in quotation marks** unless otherwise specified in the rules for drawing that item type in Yandex Map Editor.

 
{% note info %}
    
Regional exception ─ Bulgaria.
    
    
    
It's preferrable to use the "..." (<q>double</q>) quotation marks when naming items and their types. Therefore, („…“) should be changed to ("...") in applicable names. Doing the reverse is considered a mistake.
    
    
    
At the same time, the names of items in the <q>Places</q> category are always written without quotation marks.
    
{% endnote %}

#### 3.1.3.2.2.2 {#3.1.3.2.2.2}

 
The use of uppercase (capital) and lowercase letters, as well as special characters (such as <q>№</q>, <q>No.</q>, <q>#</q>, or <q>-sonli</q>) should follow the applicable language rules.

#### 3.1.3.2.2.3

 
Abbreviations in names are always capitalized.

#### 3.1.3.2.2.4 {#3.1.3.2.2.3}

 
You can't use **parentheses** in map item names unless otherwise specified in the rules for adding attributes to a layer.

#### 3.1.3.2.2.5 {#3.1.3.2.2.4}

 
If an organization uses capital letters in the middle of its name, you can write it this way on the map provided that the name doesn't have two or more capital letters in a row. For example: _ElektroSetServis_, _StroiMashServis_, _Krasnoe&Beloe_.

#### 3.1.3.2.2.6 {#3.1.3.2.2.5}

 
If the name of an item includes initials, then **you shouldn't** put a space between them.

 
For example: _проспект им. В.И. Ленина_ (rather than _В. И. Ленина_).

#### 3.1.3.2.2.7 {#3.1.3.2.2.6}

 
You are not required to use diacritics and other special characters in item names, although it is preferable.
    
    
    
You can use simplified diacritics and other special characters (entered without using keyboard shortcuts for special characters).
    
    
    
{% note info %}
    
Using diacritics and other special characters is the best solution and they should not be replaced with simplified alternatives.
    
{% endnote %}
    
    
    
For example, in the Uzbek language, the letters **o** and **g** are used in combination with the <q>**ʻ**</q> mark (**Oʻ oʻ Gʻ gʻ**), while other letters are used with <q>**ʼ**</q>:
    
    
    
 ![](_assets/name_10.png)
    
    
    
It is considered correct to use these characters, but it is acceptable to use an apostrophe instead — <q>**'**</q>.

#### 3.1.3.2.2.8 {#3.1.3.2.2.7}

 
Enter the proper name of the transport infrastructure for transport items (in both official and caption fields). Do not enter the name of the organization that manages that transport item in these fields.

 
{% note info %}
    
You can either add the name of the managing organization under the <q>also known as</q> field or add it to the map as a separate [<q>Location</q>](https://yandex.com/support/mapeditor/en/cat_organizations.md#cat_organizations) item (if the organization has a permanent location).
    
{% endnote %}

 
This rule applies to airports, railways, vehicle stations, and ports.

 
Capitalize item type in accordance with English grammar rules for proper names.

 
For example: _Kazansky River Port_ is correct, but _Tatflot Shipping Company, JSC_ is not.

#### 3.1.3.2.2.9

 
For items whose names contain decimal fractions, separate the fraction from the integer in the official name with a dot. In a synonym, you can set the name using a comma.

#### 3.1.3.2.2.10

 
In item names that refer to the route's start and end points and contain a hyphen, the hyphen is separated by spaces on both sides.
    
    
    
For example: the Ponga-Onega ice crossing.

[Contact support](https://yandex.com/support/mapeditor/en/troubleshooting/fb_nmaps.md){.button}

<!-- source: en/_includes/styles.md -->
#### {#href-button}


<!-- endsource: en/_includes/styles.md -->