Kaart: Name Tags/sandbox

Introduction

Names are important for navigating roadways, identifying locations and finding specific places on the map. As the major component in routing and identification, we want to make sure that we put in correct information when editing on OSM. In this document you will find the basic tags we use for names and the uses for these tags as well as some rules when using these tags.

Prerequisites

When putting in names, you need to have a reliable source of information. This can come from a variety of sources such as data sets, ground footage, government data, etc. No editor should put in names without a reliable source of information.

Be sure to check the country pages to find the primary language and any other languages of the country you are working in.

Skill Instruction

Good Practice

Street names play a vital role in routing so it’s important that they be as correct and accurate as possible. That being said, it’s not always easy to add or update street names due to context, lack of or partial street signage, etc. Here are some good practices to keep in mind when working with street names.

• The value used for any name keys should be restricted to the name only.
  • This tag should not contain address information, categories, descriptions or other information that can be added in separate tags.
• Use the name that is found on an official street sign.
  • When faced with multiple conflicting signed street names, choose the most signed(2 or more) or most complete name for the name=* field. Add the other names to the alt_name=* field.
• The name should be capitalized in title case.
  • Also check the spelling, spacing and look for missing, known, accent marks.
  • Note: There are some exceptions to this like highways that have a long name and use the abbreviation instead.
• It is discouraged to use any abbreviations in the name tag. Instead, they should be put as a secondary name tag such as loc_name=* or old_name=*.
• Update the name in the name=* field to the most complete version. These are typically found on street signs and in some cases the surrounding data.
• Expand all known abbreviations.
  • e.g. Francisco Ugarte vs. F. Ugarte
  • Leave unknown abbreviations as is.
• Check Y-junctions to make sure both parts of the junction have a name.
  • These are short segments at the end of a street where it splits into two oneways. In rare cases, these are sometimes bi-directional. See the Kaart: Road Classifications Guide for more info.

When to Leave Names Alone

This is just as important as adding/updating names. Ideally, we always want the most complete form, with the correct spelling, accent marks, etc., but we don’t always know that information. Here are some tips on when to leave a street name alone.

Tips:

• The name has abbreviations and you don't know them.
  • Expand the ones you do know, look up the ones you don't, and leave it alone if you can't figure it out.
• Two names have similar spellings.
  • Try to find signage to confirm which spelling is correct(2 or more signs). If you can't find anything to confirm one or the other, leave both as is.
• A common name has two different versions, one with an accent and the other without.
  • Try to confirm if the accent mark is correct. These aren't typically found on street signs so asking a native speaker or sometimes looking it up can help. If you're not sure, leave it.
• There's another name or something in parentheses() in the name.
  • Try to confirm if it's an alt_name=*, a description=*, etc. and move it to the correct tag.
  • If it's unclear, leave it alone.
• You want to extend a name.
  • Does the surrounding context support it and make sense? Satellite imagery, nearby naming conventions, etc. Extend it!
  • If the context doesn't support it, leave it.

There are many more. For any naming issues you'e uncertain about, always ask questions to see if you can figure it out, but in some cases it's always safer to leave it and let the locals update it later.

When to Remove/Move Name Tags

Some street names contain information that isn't a name at all. It's your job to identify these and determine what should be done with that information.

Here are some common things that may be added as names:

• Turn information
  • e.g. U_turn
• Destination information
  • This could be any destination information: street, ref, location, etc.
  • Check local conventions to see if this is part of the tagging.
• Ref information
  • Sometimes refs will be added as street names.
  • Note: There are some exceptions to this. See the Ref section for more info.
• Descriptions
  • Information describing the road, destination, feature, etc.
• Multiple names
  • One or more names can be moved to the alt_name=* or other appropriate tags.
• Etc.

For most of these situations you should be able to move them to a tag that is better suited for that information. In rare cases you are allowed to delete a name tag.

Frequently Used Tags

name=*

This key is set to the primary name or the most complete name of the feature in the real world. Names should always be in the local language of the area you are mapping in (translations being in a separate tag). Typically this is the name that you will see on a prominent road sign indicating the name of the road. This key typically only has one value, but some countries may allow more like Morocco. Names with multiple values are very rare and should be investigated thoroughly. As with most things on OSM, there are standards that each country has set up that should be followed. Be sure to check country wiki pages for tagging guidelines as well as other credible sources.

Note: Some languages like Tamazight(Berber) get distorted as empty squares in JOSM when combined with other names. You can see how that part of the name should look under name:zgh=* in the screenshot.

In certain cases, the name of a major hgihway may be the names of the major cities or destinations that it connects. These are usually separated with a hyphen.

• e.g. name=Blue City - Red City

name:<Ig>=*

This tag is used for translated names that are translated into a specific language. when using this tag the <Ig> will be replaced by a (ISO 639-1) language code. The list of two letter language codes can be found here. See the above screenshot for an example of name:ar=*(Arabic), name:fr=*(French), and name:zgh=*(Standard Moroccan).

Transliterations

Transliterations are generally reserved for objects that do not have names that can be directly translated into Latin script or the transliterated name is used and preferred by the local community. It is strongly discouraged to add both the translated name and transliterated name for the same object in any secondary language. Translated names are names that are directly translated into another language whereas transliterated names are names that can’t be directly translated into another language, but are instead represented in another language’s alphabet. An example would be: Benghazi and بنغازي. However, different regions of the world may follow a different format such as Hong Kong. When adding any name with this key it is strongly encouraged that the editor uses a verifiable source for the data.

Here is an example of transliterations in Athens, Greece on a destination sign.

alt_name=*

The alt_name=* tag is reserved for a secondary name that doesn't fit into any of the other name categories. This is also often used as a generic secondary name if the type of secondary name is not known or apparent.

If there are multiple alternative names make sure to add them with a semicolon and no spaces between them. This is one of the few tags where multiple values are acceptable for the tag.

ref=*

This is what is known as the reference tag. A ref=* tag is generally a code or number that is used for major highways, roads or routes. Despite not being a name tag, there are a large number of cases where the ref tag is the only displayed tag on the object. In these cases it is the de facto name=* tag.

• DO NOT duplicate the ref tag value in a name tag.

Things to Keep in Mind

Since ref=* tags may appear as name=* tags here are some things to look out for.

• Some ref tags may be used as a street name or vice versa. Try to confirm if these are actual refs or not. Often times the local municipality will use numbers to plan out an area and that information may be referred to as a ref=* tag.
  • There are 3 ways to handle this situation:
    • Confirmed as a "ref": Change it to a more appropriate ref tag like local_ref=*, old_ref=*, etc.
    • Ref is just a street name: Move it to the name=* tag if not already present and remove the ref=* tag.
    • Unsure: Leave it as is and add a note=* or fixme=* so other editors can find it and verify it.

• In some cases, the ref(s) can be used as a street name such as "Highway 6 & 50". Use all available resources to confirm these(ground imagery, government data, local knowledge, etc.). Make sure the ref tags are also correct.

For more information on refs and ref networks see the ref doc(link) or Ref Wiki page.

Less Frequently Used Tags

These are other name tag variants that aren't commonly used, but should be used in some cases.

int_name=*

For specific international languages use the above translated name tagging. This International name tag is used to put a name into a transliterated Latin based script. This is a common occurrence in places such as Belarus, Bulgaria, Greece, Kazakhstan and Northern Macedonia.

official_name=*

This is the official name used for names that are long and/or elaborate so they are not as commonly used when referring to the feature. An example of this would be the official name United Kingdom of Great Britain and Northern Ireland which is more commonly known as Great Britain/UK.

nat_name=*

This tag is for the national name. Typically this is used as a nickname or alternate name that is only nationally used. An example can be found here with the tags name=Yellowhead Highway and nat_name=Trans-Canada Highway are both on this way.

reg_name=*

This tag is for the regional name. Typically this is used as a nickname or alternate name that is only regionally used. An example for this would be a way that has a ref=* tag, no name=* tag, but has a reg_name=*.

loc_name=*

This tag is for the officially recognized local name. Typically this is used as a nickname or alternate name that is only locally used for an object. Here's an example.

old_name=*

This type of tag is used for a disused name that used to be the most complete name and for some reason it has been changed. This is because a number of sources still use the old name instead of the official name. We can see this on the previous example.

short_name=*

This tag is used in situations where a feature is commonly referred to by a prominent part of its name and not the complete name. This is also where abbreviated or acronym names should be put in if they are added for an object. An example of this would be the "United States Postal Service" or more commonly "USPS".

Unused Tags

These are tags that we may see that are not valid or deprecated.

False Names

This is referring to names that are really just a description. For example, name=highway, unknown, tree, no name, etc. While these may be in use they add little to no benefit to OSM and can either be removed or moved to a more appropriate tag.

name_1=*, name_2=*, etc.

This tag has been deprecated. DO NOT put these into OSM.

Tips for Specific Object Types

Names for Roads

• Almost all major highways will have a name and/or ref tag. Make sure to verify your information if it is missing this.
• Lower hierarchy roads such as tracks or service ways do not typically have names.
• Names can change back and forth between different areas. Look out for areas where the name may be different on your road.
• As stated above, some roads only have a ref=* tag with no name.
• As described by the Key:name page, highway names can sometimes be named after a person, but this may differ depending on the region of the world. These typically appear at a junction or only at the start or end of a road. In some cases this may appear at both the start and end of a road. In regards to motorways, it may sometimes be named by just the route number. The following tag key combination you should use for general usage is name=*, if necessary you can also use official_name=* or alt_name=*.
• In rare cases some links may have a name like this one in Costa Rica.
  • Note: In Costa Rica this is part of the local naming custom to improve navigation.

Naming Consistency

In addition to making sure the name itself is correct we also need to check that the correct name is on the right street(s). This process is called Naming Consistency.

Note: This process may vary from country to country as each country may have a unique naming scheme. Double check the tagging guidlines for naming for more insight on how they handle naming consistency.

Naming consistency can be a tricky thing to learn. How names are laid out varies around the world, since no two countries have the same city structure. A lot of naming consistency is based on context or the look and feel category. There are some basic fundamentals that remain consistent around the world that can help you learn when/where a name would change.

Before you make any changes, ask yourself these questions:

• Would the name change or stay the same?
• What does the context of the streets tell you about the naming consistency of that area?
• Are the turns gradual or hard/sharp?
• What does the quality of the road(s) look like in satellite imagery?
• What does the country wiki page say about naming?

Using Context Clues

Learning how to use context clues and available resources will help you improve the naming consistency of any area.

The name will typically change in these instances:

• 90 degree angles
• Hard/sharp turns
• Higher class roads (tertiary and above)
• When the grade(surface type) changes
  • This relies heavily on context.
• When leaving an urban area

90 Degree Angles

A 90 degree angle on a road is a good indication that the name would change. These are very common in residential areas where a grid layout is common.

Things to keep in mind:

• These are not always hard angles, they can also be soft turns.
  • Split these at the approximate corner where appropriate.
  • Depending on the context the name may extend around the corner.
• DO NOT split at every 90 degree angle.
  • Keep in mind that the name will not change at every block.
  • Keep the roads/names long and continuous so they're easier to work with.

Hard/Sharp Turns

A hard/sharp turn is another indicator that the name would change. These can bee found just about everywhere.

Things to keep in mind:

• These are common in rural areas and some densely populated cities like Mexico City and Ho Chi Minh, Vietnam.
• Often a drastic change in direction.

Higher Class Roads (Tertiary and above)

When a lower class road intersects with a higher class road, the name will typically change. This is common in all parts of the world.

Things to keep in mind:

• Just because the classification of a road changes doesn't mean the name of the road will change. Use ground imagery, context, and other sources to help verify when it's unclear.

When the Grade(Surface Type)Changes

This is where satellite imagery comes into play and helps us get a better idea of the context of an area.

Things to keep in mind:

• Check all available satellite imagery to see which one is the most up-to-date for your area.
• Use ground imagery when available to look for signage and to verify surface quality.
  • Not just limited to street signs. Address plaques and company banners with addresses can be used as well.
  • Ground imagery is almost always more current than satellite imagery which could play a huge role in deciding to extend a name or not.
• Does the surface type drastically change?(paved to dirt)
• Is the context of the road continuous?
• What does the area look like? Are there houses? Is it an industrial area?
  • The context of the buildings/area can be big clues when it comes to deciding if a name should be extended or not.
• Is there a connection in the data, but not in satellite or ground imagery or vice versa?

When Leaving an Urban Area

This is an important thing to consider when adding names to a street that extends outside of an urban area.

Things to keep in mind:

• How long is the way in OSM?
• Does it extend outside of an urban area?
• What can you learn from the available imagery?
  • Satellite imagery: Does the grade of the road change? Context of the buildings/lack of buildings? Etc.
  • Ground imagery: Are there signs suggesting the street name continues outside of the urban area?
• Split the way as needed to keep the name and proper road classification where it applies.

Dual Carriageways/Bridges/Tunnels

It is common for two different names to abruptly end at an intersection of a dual carriageway or a bridge/tunnel since it's unclear which name should extend through.

Dual Carriageways:

For dual carriageways the choice is a little easier, but context still plays a role.

• If an HPR(high priority road) extends through the intersection you should extend the name of the HPR.
• If it's a lower class road, simply choose one name to extend through and add the other as an alt_name=*.

Bridges/Tunnels

Naming for bridges and tunnels is very similar with one difference. Bridges can be also be drawn as a man_made=* feature.

There are a few ways to add names to a bridge:
man_made=bridge	This tag is added as a polygon around the bridge and is attached to the bridge. The purpose of this is to add additional information about the bridge like the bridge name, the type of bridge, etc.
Street signs:	Street sign is the bridge name: Add as the name=* tag. Street sign is the same as the current street name: Extend the street name and add the name of the bridge as bridge:name=*.
Different street names on either side and no bridge name:	Extend one of the names and add the other as an alt_name=*.
There are a couple ways to add names to a tunnel:
Street signs:	Street sign is the tunnel name: Add as the name=* tag. Street sign is the same as the current street name: Extend the street name and add the name of the tunnel as tunnel:name=*.
Different street names on either side and no tunnel name:	Extend one of the names and add the other as an alt_name=*.

Kaart Style/Validator Tips

The Kaart paint style and JOSM validator also have ways to help improve naming consistency.

Kaart Style

The Kaart Style has settings that make working with names a lot easier. These can all be found under the Name Settings in the Kaart Style.

These settings include:

• Display large street names
  • Makes the street names larger and easier to read than the JOSM standard.
• Remove street name labels
  • This is useful when working with geometry and classifications when you don't need to see names.
• Flag roads with uncapitalized words in the name.
  • Highlights a way with an orange casing and removes the name until the capitalization error has been fixed.
  • Some false positives may occur in other languages.
• Highlights ways with name tags
  • This adds a unique color to every street with a name=* tag. This will help you visually see differences in names for an area and see which streets are missing names.
  • In rare cases, two streets with different names may have the same color. Keep street names visible when using this setting so you can read the street names as well.
• Flag roads without names
  • This highlights any roads without a street name with a red casing, making them easier to spot and see where a street name could be extended or added.
• Dynamically hide street names
  • This setting is similar to the Remove street name labels setting, but has added functionality. It removes street names at high zoom levels to declutter when working with geometry, but will show names at low zoom levels.

JOSM/Kaart Validator

The validator has a handful of useful checks for naming consistency.

These include:

• Similarly named ways
  • Check to see if names are different or if it's a spelling error.
• Suspicious tag combination - Same value of name and alt_name
  • alt_name=* should be removed. Click fix on validator warning.
• Kaart - Possible duplicated words in name
  • Remove duplicates if they are incorrect. Check signage.
• Kaart - First word is capitalized, additional words are probably capitalized
• Unnamed ways

Suggested Bookmarks

• Key:name
• Names
• Kaart: Kaart Paint Style/sandbox