Fa:Editing Standards and Conventions

این مقاله یک ترجمهٔ ناتمام از Editing Standards and Conventions است: کامل نیست یا کاملاً اصلاح نشده یا هنوز بخش‌هایی از آن ترجمه نشده.
اگر به مقالهٔ اصلی تسلط دارید (زبان انگلیسی)، لطفاً در ترجمهٔ آن کمک کنید. آشنایی با شیوهٔ ترجمه در این ویکی.
به‌نظر می‌رسد هم‌اکنون کسی روی این ترجمه کار نمی‌کند.

برای پیشنهادهای عمومی بیشتر و پیشنهادهای تگ‌گذاری، Fa:Good practice را ببینید.

متن زیر برخی از استانداردها و قواعد ویرایش نقشه است.

تگ‌نویسی

• عوارض نقشه - رایج‌ترین تگ‌های OSM
• راهنمای تگ‌نویسی کشورها - قواعد تگ‌نویسی مخصوص هر کشور یا ناحیه
• عوارض - دسته‌بندی تگ‌ها بر اساس هدف یا عملکرد آنها
• تگ‌های پیشنهادی - پیدا کردن تگ جدید و غیرمعروف
• فهرست کامل روش‌های یافتن تگ

جاده‌ها

در ابتدا، هندسهٔ جاده، خیابان، پیاده‌رو و... با یکسری از نقاط کشیده می‌شود که با یکدیگر راهی را تشکیل می‌دهند. سپس بایستی به آن راه تگ highway=* و نام داده شود.

اغلب راه‌ها در ویرایشگرهای OSM شبیه به هم به نظر می‌رسند، با وجود این، بسته به تگ‌هایی که دارند در زمان رندر شدن با رنگ و عرض متفاوتی نشان داده می‌شوند.

اسامی خیابان‌ها و قواعد نام‌گذاری

عارضه : Fa:Editing Standards and Conventions

توضیحات

To provide details of the name for a feature included in OpenStreetMap.

برچسب‌ها

name=*

To provide details of the name for a feature included in OpenStreetMap.

Name keys

Key	Value	Element	Comment
name	User defined		The common default name. Notes: For disputed areas, please use the name as displayed on, e.g., street signs for the name tag Put all alternatives into either localized name tags (e.g., name:tr/name:el) or the variants (e.g., loc_name/old_name/alt_name) Do not abbreviate words: abbreviations For details refer to Names#Good_practice.
name:<xx>	User defined		Name in different language; e.g., name:fr=Londres. Note that all key variants below can use a language suffix. See: Multilingual names.
name:left[:<xx>], name:right[:<xx>]	User defined		Used when a way has different names for different sides (e.g., a street that's forming the boundary between two municipalities).
int_name[:<xx>]	User defined		International name. Consider using language specific names instead; e.g., name:en=.... International does not (necessarily) mean English. It is used to give the name transliterated to Latin script in Belarus, Bulgaria, Greece, Kazakhstan and Northern Macedonia
loc_name[:<xx>]	User defined		Local name.
nat_name[:<xx>]	User defined		National name.
official_name[:<xx>]	User defined		Official name. Useful where there is some elaborate official name, while a different one is a common name typically used. Example: official_name=Principat d'Andorra (where "name" is name=Andorra).
old_name[:<xx>]	User defined		Historical/old name, still in some use.
ref_name[:<xx>]	User defined		Unique, human-readable name of this object in an external data management system.
reg_name[:<xx>]	User defined		Regional name.
short_name[:<xx>]	User defined		Should be a recognizable commonly-used short version of the name, not a nickname (use alt_name for that), useful for searching (recognized by Nominatim).
sorting_name[:<xx>]	User defined		Name, used for correct sorting of names — This is only needed when sorting names cannot be based only on their orthography (using the Unicode Collation Algorithm with collation tables tailored by language and script, or when sorted lists of names are including names written in multiple languages and/or scripts) but requires ignoring some parts such as: ignoring leading articles, or lowering the relative importance of first names cited before a last name, ignoring the generic part of a street name when it occurs before the specific name (e.g., in French with "rue", "boulevard", "place", etc.), all of them being ignored at the primary sort level and not easily inferable by a preprocessing algorithm.
alt_name[:<xx>]	User defined		Alternative name by which the feature is known. If there is a name that does not fit in any of the above keys, alt_name can be used; e.g., name=Field Fare Road and alt_name=Fieldfare Road, or name=University Centre and alt_name=Grad Pad. In rare cases, the key is used for multiple semicolon-separated names; e.g. alt_name=name1;name2;name3, but this usage is not preferred.
nickname[:<xx>]	User defined		Nickname (e.g. "Warschauer Allee" for BAB 2 in Germany 3140168 3140168).
name_1 , name_2 , ...			Do not use this tag, suffixed name tagging for multiple values is deprecated.

This table is a wiki template with a default description in English. Editable here.

Good practice

OSM follows the on the ground principle, which means that street names and other proper names are generally entered as they appear on signs, even if those names deviate from the general spelling rules. Possible exceptions are described in some of the following sections.

If you're wondering why how brands (McDonald's etc) have preset suggestions in iD, Every Door, and other apps, the answer is in the Name Suggestion Index. Here you can add presets for brands so they get uniform spelling and tagging.

Uppercase characters

Names are adapted to the local capitalisation rules; title case is generally preferred, but regional rules have preference over general rules. Note that multiple capitalisation styles could be right, so be careful and don't over correct. For example in German both "An der alten Brücke" and "An der Alten Brücke" (meaning "at the old bridge") could be considered correct names. In Flemish, capitalisation of last names gives a hint about the nobility status of the person. Street or company names derived from those last names should copy the same capitalisation. In non-Latin based languages, it's often not even possible to capitalise a name.

Abbreviation (do not)

مقالهٔ اصلی: Abbreviations

An extreme example of abbreviation: Lake Washington Boulevard Northeast and Main Street

If the name can be spelled without an abbreviation, then don't abbreviate it. Computers can easily shorten words, but not the other way (St. could be Street or Saint).

Proper name spelling

If the name isn't present on any signs, follow the local spelling rules. Make sure that the name is really locally known and you're not inventing or constructing a name. However signs are not required for a name to exist. Most natural features like woods and lakes do not have signs. In many countries with weaker governments or lower literacy levels, the names of hamlets and streets will not be written down, but can be verified by asking the local people. You can use source:name=* to explicitly indicate how you determined the name of the feature.

If multiple different spellings are used locally, the most common or most correct is preferred. The other spelling can be entered as alt_name=*.

Conflicting signs "Karlstraße"/"Karlstrasse" for the same street. In this case, Karlstraße would be the correct spelling in Germany.

Obvious mistakes (like John-F.-Kennwdy Square) or deviating spellings that only occur because some characters were not transcribed or printed correctly should be replaced with the proper spelling, but within reason. If there is a "Jolin Tsai Street" in an English-speaking country, do not restore the original spelling of the name as something like "蔡依林 Street", but a sign with "GROSSER WEG" in Germany should be turned into name=Großer Weg, which would be considered the correct local spelling, instead of "Grosser Weg", which would be considered incorrect. (The uppercase version of "ß" was only officially adopted in the German language in 2017 and its usage is still optional.)

When old/outdated and new spelling variants are both present, the newer spelling should be used as name=*. Exceptions are possible, for example, if a city or region explicitly prefers the old spelling of a name for historic reasons and any signs with the new spelling are obviously an oversight. Proper names included in street names usually shouldn't be adjusted to new spelling variants.

Avoid including emoji and other special characters that are not pronounced, are decorative, or substitute normal letters (e.g. "♥" used for "heart" or "love", "!" used for "i"). Stylized spellings of trademarks and company names should be adapted to the regular capitalisation and spelling rules, e.g. a sign that says "TACO 🔔 BELL" would be written as name=Taco Bell. However do not change spellings/capitalization if doing so would cause confusion or if the original spelling is much more common in everyday usage.

Not all signs contain names. Descriptive text, alphanumeric IDs, advertising slogans and similar items should not be included in names.

If local signs do not match the data in official publications/databases/directories, the official name can be tagged as official_name=*, but make sure you're allowed to use that data. Note that databases can be outdated, contain mistakes or might have limitations in maximum entry length or allowable characters.

If a sign is obviously in error, use not:name=* to prevent mappers without local knowledge from propagating the error in OpenStreetMap.

In principle, not all special cases and exceptions can be mapped into rules. When still in doubt, use common sense. You may also find the following questions helpful:

• How would you write the name in a mailing address, e.g. when sending a letter?
• How would a navigation system pronounce the name and what name would a user enter to search for the feature?
• How does the name appear in official directories? Are any discrepancies to signs or to proper spelling rules intended or likely mistakes?

Watch out for apostrophes

If the street sign has an apostrophe, the OSM data should have an apostrophe. There is no obvious consistency; the London Underground station Barons Court is adjacent to Earl's Court, one with an apostrophe, one without.

Name is the name only

The names should be restricted to the name of the item in question only and should not include additional information not contained in the official name such as categories, types, descriptions, addresses, refs, or notes. However - if something has the official name "East 110th Street" this full name should be in the name notwithstanding the fact that the "street", the "110" and "east" might be deducible from some other information. If something really doesn't have a name, don't add a name to OpenStreetMap. Any additional information should be included in separate tags (see, e.g., aforementioned links) to identify its meaning.

Some examples of incorrect usage:

• "Multipolygon Baldo Forest" : do not include the object type or other OSM terminology, if it does not apply outside of OSM
• "The Royal Albert Hall, London" : do not otherwise include the location London as part of the name, even if there are multiple objects of the same name
• "closed pub (due for demolition)" : do not describe the object in lieu of a name. Consider the description tag and also adding an old_name tag. No longer existing objects should be deleted. Disused objects such as shops can be tagged with lifecycle prefixes. See also nonexistent features page for more info.
• "no name" : (see #No name, below)
• "Football pitch" : this describes the feature, and is likely not the actual name. Instead make sure to use sport=soccer (the same for other sport pitches).
• "Interstate 5 southbound lanes" : do not separately name parts of the same object where they are separate in OSM, but not outside of OSM.
• "Interstate 5" : When a name would only be duplicating the information in the ref=* tag, then the ref and noname=yes is almost always more appropriate.
• "Wildwood Boardwalk (seasonal)" : Do not include time-related access restrictions in the name. Instead, use conditional restrictions tags (or opening_hours=* for non-highways). example: access:conditional=no @ (Nov-Apr)
• "Manchester City" : (for a city named Manchester, do not add a descriptive City; however note that New York City may be correct as the common name for The City of New York)
• "Foobar Mountain, 8000 ft" : tag height in a separate tag (like ele=* or ele:ft=*), not as part of the name
• "Lower Hell Hole 1030-002 Dam" : do not embed a reference number in a name just because a source (here USGS GNIS) does so; use a separate ref=* tag, for example, name=Lower Hell Hole Dam and ref:gnis=1030-002
• "Union Pacific Railroad" : a name=* which was assigned during the USA's 2007-8 TIGER import (of roads and rail); the correct value is the name of the Subdivision/Branch/Line and this railroad name is properly the value of operator=* and/or owner=* (there are many other incorrect values besides Union Pacific). It is OK to precede a railroad name with an operator when two or more otherwise-identically named lines in close proximity would create serious confusion. For example, naming "CN Joliet Subdivision" and "UP Joliet Subdivision" or "BNSF Fort Worth Subdivision" and "UP Fort Worth Subdivision" is sensible. (For now. Even this convention may disappear in the future as operator=* and owner=* become more widespread and avoid such ambiguities).
• "alternate summit trail" describing role of part of hiking route. For signed routes, you can use roles for recreational route relations

It is certainly wrong for a mapper to invent a name for an airstrip; however most names were invented at some point in history, so if someone invents a name and it catches on and a sizeable group of people refer to the thing by that name, then it's ok to be mapped.

No name

Streets which have no name are tagged noname=yes by most mappers. The idea is to clearly indicate that the street genuinely doesn't have a name. Absence of a name tag is increasingly used to indicate areas which need to be surveyed still.

Left and right names

For way objects, names can differ by side of the object.

For example, a street may be on the boundary between Belgium and the Netherlands, Belgium gives it the name "Amsterdamsestraat" and the Netherlands gives it the name "Brusselsestraat".

This is solved by using the name:left=* and name:right=* tags to name both sides separately (using the direction of the way to determine left and right) . The name=* tag can still include both names in order to support different tools.

Example:

• name:left=Amsterdamsestraat
• name:right=Brusselsestraat
• name=Amsterdamsestraat - Brusselsestraat

note: different left-and-right names doesn't preclude the existence of multilingual names (which also happens more often on country borders). So tags like name:left:fr=* are possible.

Multiple names

If you have multiple names for a feature, first try to choose a rich semantic tag like any of the ones in the table (like short_name=*, old_name=*, etc.). If none of them works, choose the alt_name=* tag. If there are multiple names that do not fit, alt_name=* can be used with semicolons.

Sometimes name=* itself can contain multiple values separated by semicolons:

• In multilingual regions or localities, multiple names in different languages may be relevant enough to include in name=*. A separator other than a semicolon, such as "/" or "-" (spaced or not), may be customary locally. This is not a substitute for language-specific keys, such as name:en=* for English.
• Some international boundary features (often bodies of water) have multiple values in name=*, so as not to favour one country's preferred name over another's.
• In relatively rare cases, there may be a tie on less prominent features such as points of interest. For example, a single business may go by two names interchangeably and post each name on different sides of the building. Before overloading name=* with multiple values, make sure it is truly a tie and there is not a more structured way to represent the naming situation.

Some renderers turn semicolon delimiters into something more aesthetically pleasing, such as an em dash or line break, but many other data consumers assume only a single value in name=*, so a semicolon could appear verbatim, surprising users.

Names are not for descriptions

For descriptions please use description=* not the name=*.

While it is welcome to tag building=house, it is wrong to add also name=house. Or name=Mosque to amenity=place_of_worship + religion=muslim. Validators may detect and propose to remove the most obvious and common incorrect descriptive names, but undetected ones also are incorrect. This is a form of tagging for the renderer.

Though note that some lakes are actually named "The Lake", in such case adding it as a name is fine.

Do not construct names for features by combining the name of an enclosing feature with a description. For example, an unnamed fountain in XYZ Park should not be tagged with name=XYZ Park Fountain. Internal features to a named area should only be tagged with a name when they have a commonly-used local name, or some other indication (such as signage) of the feature's name. If the internal feature is named, it should still not be combined with the enclosing area's name. A feature named 'Smith Fountain' within 'XYZ Park' should be tagged name=Smith Fountain but not name=XYZ Park Smith Fountain.

For example, The Lake The Lake in New York City's Central Park Central Park is tagged with name=The Lake and not a constructed name like "Central Park Lake". However, actual names referencing location of object are fine, as long it is actual name. For example the Central Park Tennis Center Central Park Tennis Center does include "Central Park" in the name, because "Central Park Tennis Center" is the tennis center's actual name.

Despite this principle, historically, public transit route relations were expected to have name=* set to a description of the route in a rigid format.

Disputed names

If the dispute can not be resolved through discussion, then the simple default rule is whatever name are used by the people on the ground at that location are used. For further information see Solving Disputes and the Official OpenStreetMap Foundation statement on the project's practices regarding disputed boundaries, borders, names, and descriptions.

Localization

همچنین ببینید: Multilingual names

By now the majority of rendering systems can deal with unicode characters, so you can use the local script for the default name tag. There is no need to use the Latin script.

For adding localized names in different languages, add additional name:code=* tags with a suffix on the name key, where code is a language's ISO 639-1 alpha-2 code (in the second column), or ISO 639-2/T (alpha-3) code (technical/terminologic codes, including possibly codes for macrolanguages, but excepting codes allocated to group of languages, do not use bibliographic codes) if an ISO 639-1 code doesn't exist, or ISO 639-3 (alpha-3) codes (for isolated languages or macrolanguages) otherwise; do not use ISO 639-5 codes allocated for language families.

For example, name:fr=* for the name in French and name:en=* for the name in English. The default name (occupying the 'name' tag without suffix) should be the name in whatever language is used locally.

Here is an example of the usage. All these tags might appear on the same element:

name=Irgendwas        (the default name, used locally)
name:en=Something     (the name in English)
name:el=Κάτι          (the name in Greek)
name:de=Irgendwas     (the name in German)
name:pl=Coś           (the name in Polish)
name:fr=Quelque chose (the name in French)
name:es=Algo          (the name in Spanish)
name:it=Qualcosa      (the name in Italian)
name:ja=何か           (the name in Japanese)
name:ko=아무것          (the name in Korean)
name:ko-Latn=Mweonga  (the name in Romanised Korean)   (conforming to BCP 47 standard. Deprecated: ko_rm)

This leads to a more precise definition of alternative names.

Example of language codes according to the alpha-2 (= two-letter-)code of ISO 639-1:

de  German
pl  Polish
el  Greek
en  English
es  Spanish
fa  Persian
fr  French
it  Italian
ja  Japanese
ko  Korean
ru  Russian
zh-Hans  Simplified Chinese
zh-Hant  Traditional Chinese
ko-Latn  Romanised Korean (conforming to BCP 47 standard. Deprecated: ko_rm)

A short discussion on this language suffixes can be found on the discussion page.

Renderer support: Some rendering systems display these localised names. See Map Internationalization

Import: using osm2pgsql allows users to define new .style files which can include other language's name columns and bring them into the database. In order to render from these columns it is necessary to set up PostGIS views which present these columns as 'name' instead of 'name:languagecode'. An easier alternative might be to use a lua style file to move "name:XX" if it exists to "name". An example is seen in this diary.

Editor support: JOSM builds 1044 and newer support the display of local names. It detects the current system locale and tries to display names in this language first. You can change the order JOSM looks for names in the JOSM expert settings. Example: To display names written in Thai first, even if the current locale is 'en' set the following property:

mappaint.nameOrder=name:th;name:en;int_name;name

Transliteration

Transliteration is the process of taking a name in one language, and changing letters from one script to another. For some languages, this is necessary, particularly those which have multiple orthographies, such as Punjabi or Serbian. Some languages which are typically tagged separately necessarily have a transliterative relationship with one another in most cases; for example, Hindi and Urdu do not differ grammatically or phonetically and tend to contain the same strings in the Devanagari and Perso-Arabic scripts respectively. In most cases, it is not possible to transliterate automatically, so it is advisable to add and review these manually.

Some countries which use an official local language not written in the Latin script (notably in India, Arabic countries, and CJK character using region) have official Romanization or other transliteration schemes which may be tagged with the appropriate tag for the target language code.

When to avoid transliteration

There are many situations where transliteration is generally avoided. Everything with a name could hypothetically be transliterated into language (city names, roads, cafes), but it's not necessarily desirable for every possible transliteration to be mapped. See also Good practice#Map what's on the ground.

Situations where transliterations should be avoided include:

• Bulk import of transliterated names from sources such as Wikipedia.
• "Manufactured" transliterated names which are not in regular use (e.g., adding an Inuktitut transliteration of a small village in Indonesia)
• Names in fictional languages such as Klingon, Tengwar, or Na'vi.
• Brand and shop names which do not have a commonly used transliteration.

Some developers have attempted to demonstrate that mappers do not need to manually translate or transliterate obscure map features' names because fully automated alternatives are available:

• Sven Geggus has demonstrated the principle of rendering with auto-generated transliterations.
• The German OpenStreetMap (Mapnik style) and OpenMapTiles transliterate many scripts to Latin using OSM map l10n functions.

However, these fully automated approaches are fundamentally unreliable. Text can only be properly transliterated if the original source language is known, but name=* does not indicate a language explicitly. Any language-agnostic transliteration tool, such as ICU, is unsuitable for transliterating from some writing systems such as CJK to Latin, because they were designed for collation rather than user display. Machine translation can also be unreliable on very short strings, such as the names of map features, due to a lack of context.

Instead, popular data consumers retrieve manual translations and transliterations from Wikidata. While many of Wikidata's translations come from the same automated tools, they are often more reliable because the original language was fed into the transliterator and users have the opportunity to correct the results.

Language-specific names

name=* contains the common, default name in the local language. name:<lang_code> is used to tag the name in a specified language in cases where the name differs by language, for example name:ru=Москва gives the city's name in Russian (language code ru) while name:en=Moscow gives the English language name (language code en).

In cases where multiple languages are tagged for a name, the local-language name tag should be duplicated with the language-specific sub-key. For example, Moscow is tagged with name=Москва, with the same value as name:ru=Москва. This tagging is important because it ensures that data consumers don't need to infer the local language. Guessing name language based on location is unlikely to always succeed - there are places in Russia where name=* is not in Russian, there are places in USA where correctly mapped name=* is not in English. For example, a tourist-oriented gift shop or a grocery that caters to an immigrant community may be named in a foreign language.

On the other hand, do not tag names that do not exist. An unremarkable village somewhere in Poland might have only one name (recorded in name=*). In all other languages, this village would be called by its Polish name, because it has no other name. Just because all other languages use the Polish name, you should not add name:<lang_code> tags for all other languages containing the Polish name!

Rationale

Tagging both say name=Kraków and name:pl=Kraków is useful for displaying localized names with fallback languages. If someone wants to

• display names in Polish
• in case of Polish name being unavailable, show English name (with "Beijing" being preferred over "北京市")
• otherwise display the default name=*, assuming one exists

In such case the solution would be to

• display name:pl=*
• if it is unavailable display name:en=*
• if both are not present display name=*

But note what would happen if name=* would be in Polish, name:pl=* would be not tagged and name:en=* would be tagged:

• display name:pl=* - skipped, as not present
• if it is unavailable display name:en=* - done!
• if both are not present display name=* - not reached

Alternative would be adding guesses about language of name=* (what is tricky, complicated for many languages and areas impossible, fragile and error-prone).

Or explicitly tagging both name=* and name:<lang_code>.

Local names (loc_name)

loc_name=* is for the name of a feature as it is known locally, but only where this is deemed to be too much of a slang name or otherwise unofficial-sounding. Ordinarily though, the name which local people use is the name we set in the name=* tag! Examples where we have used loc_name=*:

• There is a bridge in Glasgow known as the Squinty Bridge, but its official name is the Clyde Arc. I have never heard anyone calling it that, so the bridge is tagged loc_name=Squinty Bridge name=Clyde Arc.
• In Reading there's Union Street, but it's been known for decades as Smelly Alley on account of the fishmongers that lined it. The loc_name=* is ideal.

The tag nickname=* is also in use for slang names or other obviously unofficial, but widely known names, especially when the slang name is known globally/nationally and not only locally. For example the German "Bundesautobahn 2"[۱] has the nickname "Warschauer Allee".

Alternate names (alt_name)

Apply when an alternative name exists (e.g., a street name has different syntax) sometimes even on street signs, although it is not only for street names.

Don't use it for abbreviations and only when one of the other name types don't apply; e.g., reg_name=* or name:xx=* for regional translations.

These alternative names are usually not rendered, but can be used by applications like Nominatim.

Sorting names (sorting_name)

sorting_name=* is a proposed approach to supply an alternate name which systems can use for the purpose of sorting alphabetically. This would be useful for street names in some languages/countries, particularly Russian, where words like "Street" are frequently used as a prefix. This is problematic if you simply sort on the main name=* tag.

Historical names

The date namespace suffix can be used for historical names, e.g., name:1953--1990=Ernst-Thälmann-Straße.

Deprecated tags

The suffixed tags name_1=* and alt_name_1=* should no longer be used for tagging. They are the result of old imports that were not defined very well.

See also

• name:pronunciation=*
• name:etymology=* - The subject commemorated in the name of an element
• Multilingual names
• noname=yes - Used to mark the absence of a name, where something really does not have a name in reality
• strapline=* - Official strapline used in an advertising slogan next to the name, commonly seen on signs
• unnamed=* - Used to mark the absence of a name, when it was verified to have no name defined in reality. Consider using noname=* instead
• Key:description - to describe a feature.

External links

• United States Postal Service Official Abbreviations, e.g., street-type abbreviations.
• Falsehoods programmers believe about geography
• Eighth United Nations Conference on the Standardization of Geographical Names

خیابان‌های یکطرفه

اگر ترافیک تنها در یک جهت است باید راه را در همان جهت کشید و سپس تگ oneway=yes اضافه کرد.

معابر جداشده

معبر جداشده به هر معبری گفته می‌شود که جریان آمدوشد در آن با استفاده از مانع (مانند چمن، بتن یا فلز) به‌طور فیزیکی مجزا شده باشد. درحالی که بیشتر معابر جداشده از دو جریان ترافیکی مخالف تشکیل می‌شوند، مانند بلوارها یا جاده‌های دوبانده، اما می‌توانند از سه بخش یا بیشتر نیز تشکیل شده باشند و ترکیبی از جریان‌های هم‌جهت و مخالف تشکیل بدهند، مانند معابری که خطوط «کندرو» و «تندرو» دارند (که ورود به و خروج از معبر فقط از طریق خط کندرو ممکن است).

معابر جداشده باید با راه‌های جدا رسم شوند. معمولاً هر کدام از این راه‌ها oneway=yes (یعنی یکطرفه) هستند و هر جا لازم است باید همین‌گونه تگ‌گذاری شوند. راهی که راه‌های جداشده را به هم پیوند می‌دهد باید در مکانی رسم شود که حرکت بین راه‌های جداشده ممکن باشد، به‌عبارتی در جایی که جداسازی فیزیکی وجود نداشته باشد (مثلاً [۲]. همچون همیشه، محدودیت‌های قانونی را با تگ‌های access مشخص کنید). در جایی که راه‌های جداشده موازی هستند (اغلب، اما نه همیشه) چینش گره‌های آن‌ها باید به‌گونه‌ای باشد که در همسایگی هم قرار بگیرند. این کار جلوهٔ زیباشناختی دلپذیری در پرداخت راه‌ها و به‌خصوص در خم‌ها، ایجاد می‌کند. همچنین اطلاعاتی مربوط به فاصلهٔ متقابل آن‌ها از هم در تمام طول مسیر، بدین گونه حفظ می‌شود.

در هر راهی، بر اساس نیازی که برای نمایش خم‌ها داریم فاصلهٔ بین گره‌ها مشخص می‌شود (زیر را ببینید):

نادرست.

درست. گره‌ها جفت‌جفت منظم شده‌اند.

فلکه‌ها

Roundabouts را ببینید

تقاطع‌ها

همچنین ببینید Fa:Node#گره‌های_روی_راه‌ها

تقاطع جاده‌ها باید در قالب گرهی رسم شود که راه‌ها را به هم متصل می‌کند (دو یا چند راه در یک گره اشتراک داشته باشند).

استفاده از دو گره که دقیقاً (یا تقریباً) در یک موقعیت باشند اما در حقیقت یکی نباشند، درست نیست. هرچند شاید درست به نظر برسد، اما با این روش، اتصالی که بین دو جاده برقرار می‌شود اتصال معتبر قابل‌مسیریابی‌ای نیست. بنابراین اگر در واقعیت، آن راه‌ها به هم متصل هستند برای حل این مشکل باید در نرم‌افزار ویرایشگر، آن دو گره را با هم ادغام کنید.

اگر سبک نقشه در ویرایشگری که استفاده می‌کنید گره‌های مشترک را برجسته و قابل‌تشخیص نمی‌کند، این ترفند را به کار ببرید: گره موردنظر را کمی جابه‌جا کنید و ببینید کدام راه‌ها با این حرکت تکان می‌خورند. لطفاً حواستان باشد که این جابه‌جایی آزمایشی را «واگرد» کنید (این کار را با استفاده از قابلیت «واگرد» یا undo در نرم‌افزار انجام دهید و خودتان آن را دستی برنگردانید!).

ابزارهای تضمین کیفیتی وجود دارد که چنین مشکلات بالقوه‌ای در اتصالات را پیدا می‌کنند (پایان‌یافتن راه در نزدیکی راه دیگر، بدون اتصال به آن)

• 

  تقاطعی ساده و معتبر (نقطهٔ سیاه وسط جزئی از هر دو راه سفید است)

• 

  تقاطعی که نادرست رسم شده است

پل‌ها

راه مربوط به پل تگ‌های bridge=yes و layer=1 می‌گیرد.

پل با راه جداگانه رسم می‌شود. این یکی از وضعیت‌هایی است که جاده با فقط یک راه رسم نمی‌شود، بلکه چندین راه که سربه‌سر به هم وصل می‌شوند جاده را تشکیل می‌دهند و هر کدام از این راه‌ها نیز تگ‌های متفاوتی دارند. برای این منظور، در ویرایشگرها به‌آسانی می‌توانید راه‌ها را در گره موردنظر به دو نیم تقسیم کنید.

تگ highway و تگ name به همهٔ قسمت‌ها داده می‌شود. راه کوتاهی که پل را مشخص می‌کند، تگ‌های bridge=yes و layer=x را نیز می‌گیرد. x عدد لایهٔ پل است و باید یکی بیشتر از لایهٔ راه زیرین باشد (یا اگر راه زیرین شمارهٔ لایه نداشت برابر با 1 است).

اغلب، پل مستقیماً به تقاطع وصل نمی‌شود. در این صورت باید با جادهٔ کوتاهی پل و تقاطع را به هم وصل کنید (تصویر را ببینید):

پل نزدیک تقاطع

برای جزئیات بیشتر Key:bridge را ببینید.

تگ‌گذاری محوطه‌ها

محوطه‌ها راه‌های بسته هستند

On some occasions the feature you wish to tag is not represented by a line (as is the case of a road, river, rail line etc), but by an area. For instance a wooded area, a park, or a lake are all Map features which are areas. Create a new closed way which represents the outline of the required area. Annotate this way with the required tagging from the map features page, such as natural=water (for a lake), landuse=forest (for a forest), or leisure=park (for a park), etc.

استفاده از محوطه برای راه‌ها

Most ways are assumed to be areas if they are closed (i.e.--if the way connects back to itself). However, there are some exceptions to this, such as highways, which are generally assumed to be ways. If the highway is meant to be an area (for example, a pedestrian square), then an area=yes tag should also be added, to imply that this feature is not just representing the way that forms the border, but the area within it, too.

Areas and Ways Sharing Nodes

There is not clear consensus yet on how to draw areas adjacent to ways. They may be drawn either by leaving a small gap between the area and the way or by connecting them so that the area shares nodes with the way. That being said, when the way is a highway, it usually is most accurate to include a gap, so that the area ends by the side of the road and does not share nodes with the road's way. This is because highway ways usually are traced along the centerline of the road, and it is unlikely that the area being tagged actually extends to the center of the road.

دقت

See main article: Accuracy

Accuracy is important during mapping. Beware of systematic errors of aerial imagery (see for example Bing#Precision). Remember, that when tracing roads — particularly winding, rural ones — you should add enough points to make each curve look like a curve. Of course, this is entirely subjective, as curves made entirely of lines will only ever approximate a "true" curve (which has an infinite number of nodes), and will always look like a series of lines when zoomed in past a certain point no matter how many nodes there are.

To generalize, though, sharp curves (those having a small radius) require many, closely-spaced nodes, while broad, long-radius curves can consist of fewer nodes having more distance between them. Without a hard-and-fast rule, it is best said to simply use good judgement and strive to seek a balance.

Small example using GPS traces

Below there is an example of a very roughly-traced rural 2-kilometer road. It's rather crude, particularly on the sharp curves. We would normally expect mappers to represent this kind of road with more nodes than that.

How it shouldn't be done

This is the same 2-kilometer road - but this will look much better on the map, and gives the map user a better sense of the curves of the road. You can see the road on the map. You can see, that ... other mapping services] have a similar degree of accuracy.

How to do it

Note: Keep in mind that the road in the diagram below is about 2 km long. For very short roads you do not need to add that many nodes. If a road is perfectly straight then a node at either end is always sufficient, regardless of how long it is.

It's easy enough to "fix" these things i.e. enhance the detail of the road. Normally you should just add more nodes to the existing way. If you choose to delete and redraw a whole road, check that the nodes don't themselves have tags e.g. a highway=crossing node. Potlatch and JOSM] will highlight tagged nodes.

تاریخ و ساعت

تعریف ساده

تاریخ باید در قالب ISO 8601 باشد، یعنی YYYY-MM-DD.

تگ‌نویسی دقیق

• Key:opening_hours#Examples or more complex and precise Key:opening hours/specification
• Category:Time data standards contain overview of all tags involved in specifying time

متفرقه

• Intersections and interchanges - These are most likely to be always improved by someone else, no matter how much detail you put in

  The initial level of detail should include correct connections from/to each road and link road and the existence of any bridges and underpasses; remember to set oneway tags where applicable.

  For intersections any pedestrian crossings are valuable information; add a node in the way they cross at their location

  After that there's still lots of detail that can be added (as with all roads: number of lanes, speed limits, lit=yes/no

• Accuracy. How do you judge and or indicate the accuracy? How accurate is good enough? Is a rough approximation better than nothing (i.e. inaccurate roads get refined the way wikipedia articles do).

  A GPS trace is almost always more accurate than other sources available to us. Still several, even tens of traces can be used to improve the accuracy. Do note though:

  • Sometimes and in some environments the GPS trace can wander off to some direction (often 15-30 meters but even 90 meters); compare the trace with your memory, photos and notes to see if straight roads appear as a reasonably straight set of trace points.
  • If it's a new road (nothing previously entered in the area) and there aren't any aerial images available, draw it in anyway
  • If there are already other roads around and your trace seems bad, try to deduce the "real" form from the trace by not crossing roads that don't intersect with the road you traced.

  How accurate is good enough varies with each user:

  For most uses it's accurate enough when it's not misleading: say when a cycleway drawn on the map

  • shows all correct bends and intersections
  • and no nonexistent ones
  • and is on the right side of the nearby road / stream / railway
  • and is roughly the correct distance away from those features (some editors have support for measuring distances)

  Some may later want to draw fences, hedges and walls around the houses (where they exist); they will have mapped their locations to within a few meters by repeated traces and considerable amount of deducing and aligning things in lines

  Not only inaccurate roads, but those lacking secondary information, are refined later anyway. When contemplating on whether to approximate some road, try to consider if a user would find any value in the approximated form - is it likely to be within, say, 50 meters from the real location at all times (in otherwise unmapped territory)? If you approximate, do add a source=approximation or similar tag to the way.

• Is it constructive/helpful to mark a road that you know is roughly in the right place but don't have any supporting GPS data?

  This depends again on what else is there:

  • If an urban road is missing in a rectangular grid and you confirmed its existence and it was, say, roughly halfway between the parallel roads: the position is likely to be almost as good as the position of those parallel streets when you draw it in.
  • If the missing road ventures into the unmapped territory winding along the way, it's likely better to draw just a stub for the starting point and add a FIXME=continue on the last node. If one were to draw the full way freehand, it would very likely be too short/stretched/skewed - unless there are good aerial images available.

• Landmarks, footpaths, etc.?
• How do you indicate that one road passes over or under another? - See the description for bridges above, and Key:bridge.
• If a road is made up of several/many ways, all ways should carry the name and/or ref tags.

توپولوژی

• اهمیت توپولوژی صحیح از دقت مکانی بیشتر است یا کم‌تر؟
  • در نهایت هردو مهم هستند و تناقضی با هم ندارند اما زمانی که ابزارهای ما در تعیین توپولوژی به همان میزان موقعیت، دقیق باشند بایستی درست کشیده شوند، حتی اگر منجر به این شود که بعضی تقطه‌ها چند متر جابجا باشند.
• اگر جاده‌ای دو بانده است حتماً بایستی دو جاده جدا کشیده شود مانند بلوارها
• اگر جاده‌ای دارای جزیره ترافیکی باشد (مانند جاهایی که به میدان نزدیک می‌شود) بایستی به صورت مثلث کشیده شود یا نه؟ چقدر بزرگ باید باشد تا ترسیم شود؟
  • هم می‌توانید رسم کنید و هم می‌توانید رسم نکنید. محدودیتی وجود ندارد. ولی طبیعتا هر چه طول مسیر جدایی بیشتر باشد، احتمال اینکه کسی اقدام به رسم جداگانه مسیرها بکشد بیشتر می‌شود.

هشدار: OpenStreetMap بسیار اعتیادآور است. هر از چندگاه استراحت کنید، خیلی چیزها برای انجام دادن هست.