| 24 | | == Tags == |
| 25 | | A **tag** is a name/value pair assigned to an object. Tags are used to describe an object in detail. If we write `foo`=`bar` we mean ''The tag with key foo is assigned the value bar''. Here are some examples: |
| | 19 | Simplest example is [osmwiki:Key:drinking_water drinking_water=yes] - it is present globally and can be applied to every object that provides water. Other example is [osmwiki:Key:leaf_cycle leaf_cycle]=* of trees, it will have less coverage globally (as trees do not grow just everywhere). |
| | 20 | |
| | 21 | From time to time you will encounter [osmwiki:Named_spots_instead_of_street_names tags that found somewhere else but not in your locality]; it is good idea to check wiki what is tag about, use: [osmwiki:Essential_links_tagging Essential links tagging] as starting point. |
| | 22 | |
| | 23 | [#Tags1 We will cover tags in more detail below], but first will cover all other data primitives. |
| | 24 | |
| | 25 | === Nodes (also an OSM data primitive) === #Nodes |
| | 26 | [[JOSMImage(data/node,24,bottom,margin-right=15,link=)]] A **node** is an individual point with a defined position. ''With respective tags'' it can be used to indicate shops, benches, individual trees or points of drinking water. |
| | 27 | |
| | 28 | Only nodes have [wikitr:/Help/Concepts/Coordinates Coordinates] in the OSM data model. Ways and relations simply refer to nodes. |
| | 29 | |
| | 30 | ==== Common nodes ==== |
| | 31 | |
| | 32 | Nodes can be re-used between multiple ways. Multiple ways can refer to a single node (common node). |
| | 33 | |
| | 34 | A practical meaning of this is demonstrated at the [wikitr:/Help/Action/Draw#Commonnodes Draw Nodes] page. The [wikitr:/Help/Action/MergeNodes Merge Nodes] tool can be used to create common nodes. |
| | 35 | |
| | 36 | === Ways (also an OSM data primitive) === #Ways |
| | 37 | [[JOSMImage(data/way,24,middle,margin-right=15,margin-bottom=5,link=)]] A **way** is a sequence of nodes ([https://en.wikipedia.org/wiki/Polygonal_chain a "polygonal chain" from ordinary geometry]). OSM **way** used to represent linear objects, ''with respective tags'' it can used to describe: a river bank, tree row, kerbs in the streets (among other uses). |
| | 38 | |
| | 39 | ==== Direction ==== |
| | 40 | Since nodes are ordered in OSM; every way in OSM has a direction. This gives us possibility to add tags (details about object) such as [osmwiki:Key:conveying conveying=*] - to specify direction of escalators and moving walkways or [osmwiki:Key:incline incline=*] which can be used toghter with roads and footways. There [osmwiki:Category:Way_Direction_Dependent more examples] and we can't cover them all. |
| | 41 | |
| | 42 | **Note**: Rendering of direction in [wikitr:/Help/MapView MapView] can be set in Preferences under [wikitr:/Help/Preferences/DrawingPreference OSM Data]. |
| | 43 | |
| | 44 | ==== Segment ====#Segment |
| | 45 | Is **a fragment between two consequent points of the way** ([https://en.wikipedia.org/wiki/Line_segment "line segment" from ordinary geometry]). This is not a part of OSM data model, but users often distinguish because of tools than operate on segment level (rather than on complete way); please, distinguish a segment(s) from complete "way"s. |
| | 46 | |
| | 47 | **Note**: Rendering of segments in [wikitr:/Help/MapView MapView] can be set in Preferences under [wikitr:/Help/Preferences/DrawingPreference OSM Data]. |
| | 48 | |
| | 49 | ==== Areas ==== #Areas |
| | 50 | [[JOSMImage(data/closedway,24,middle,margin-right=15,margin-bottom=5,link=)]] If a **way** is closed, i.e. if the last node is the same as the first node, it is also called an **area**. Old term for this is ''Closed Ways'' (it is still present at wiki, used in software and by some mappers; other part uses "geometry" when talking just about shape of the objects, without tags). |
| | 51 | |
| | 52 | Sometimes single area is not enough to represent an object (for example, a lake with an island in it), then you have to use a [wikitr:/Help/Concepts/Object#typemultipolygon multi-polygon] |
| | 53 | |
| | 54 | === Relations (also an OSM data primitive) === #Relations |
| | 55 | |
| | 56 | ==== In most cases you don't need them ==== |
| | 57 | If some object can be represented with single ''node'' or ''way'' and ''multiple tags supported by software'', then there is no need in relations. But there are some rare cases where it is theoretically and practically impossible ''only with nodes, ways and tags'' (ex. turn restrictions, will be covered below). |
| | 58 | |
| | 59 | This means **you can [#Tags1 skip this big "Relations" section], until you decide to add or edit a relation**. |
| | 60 | |
| | 61 | ==== Simple explanation ====#SimpleExplanation |
| | 62 | [[JOSMImage(data/relation,24,middle,margin-right=15,margin-bottom=5,link=)]] A **relation**: |
| | 63 | * is a sequence of other objects (nodes, ways and relations) |
| | 64 | * as other objects (node, way) - every relation can have their own "tags" |
| | 65 | * can be used as members in other relations (nested or hierarchical structures) |
| | 66 | * tag type=* used to define one of [osmwiki:Types_of_relation many types of relations] |
| | 67 | |
| | 68 | Additionally, each object participating in a **relation** can be assigned a **role**, for instance "via" node and "from", "to" ways in type=restriction relation. |
| | 69 | |
| | 70 | [wikitr:/Help/Relations Relation Help] covers the most basic tools to create relations in JOSM ([wikitr:/Help/Dialog/RelationList Relations window], [wikitr:/Help/Dialog/SelectionList Selection], [wikitr:/Help/Dialog/RelationEditor Relation editor]). |
| | 71 | |
| | 72 | ==== Most popular types ==== |
| | 73 | |
| | 74 | ===== type=multipolygon =====#typemultipolygon |
| | 75 | |
| | 76 | A water object ({{{natural=water}}}), a building ({{{building=*}}}) or administrative boundary ({{{admin_level=*}}} tag) usually consist of the multiple spatially separated parts belonging to the one object. More importantly, each of these parts can have exclusions ([https://en.wikipedia.org/wiki/Enclave_and_exclave enclaves/exclave] or simply islands or swamps in the water basins). |
| | 77 | |
| | 78 | * Parts are created using "{{{outer}}}" role. ''Each multi-polygon should have at least one outer part''. |
| | 79 | * Holes inside parts - using "{{{inner}}}" role. ''Each part can have from 0 to N holes''. |
| | 80 | * Ways that form a ring where all ways are connected between each other using common nodes (JOSM will warn you about mistakes during validation) |
| | 81 | * Rarely, holes can be nested. If nesting is more complex than ''single outer'' and ''single inner ring'', role swapping can continue: outer-inner-outer-inner-... |
| | 82 | * Outer and inner rings shouldn't have common nodes (but validator will warn you about this and other mistakes) |
| | 83 | |
| | 84 | Multi-polygon specific tools: |
| | 85 | * [wikitr:/Help/Action/CreateMultipolygon create a multipolygon] |
| | 86 | * [wikitr:/Help/Action/UpdateMultipolygon update existing multipolygon] |
| | 87 | |
| | 88 | ===== type=route ===== |
| | 89 | |
| | 90 | [osmwiki:Relation:route Route-Relation] describe common routes for all kind of transport modes and transportation services like [osmwiki:Tag:route=road roads], [osmwiki:Tag:route=bicycle bicycle], [osmwiki:Tag:route=hiking hiking], [osmwiki:Public_transport public_transport] or even electric [osmwiki:Tag:route=power power lines] |
| | 91 | |
| | 92 | ===== type=restriction ===== |
| | 93 | |
| | 94 | Can be used to describe turn restrictions according to signs and road marking. JOSM has a plugin to support this type of relations: [osmwiki:JOSM/Plugins/Turnrestrictions Turnrestrictions plugin],[osmwiki:Relation:restriction#Examples Examples] |
| | 95 | |
| | 96 | |
| | 97 | == Tags ==#Tags1 |
| | 98 | More precisely, a **tag** is a name/value pair assigned to an object. If we write `foo`=`bar` we mean ''The tag with key foo is assigned the value bar''. Here are some examples: |
| 47 | | == Object ids == |
| 48 | | The OSM server assigns each object a unique number, the **object ID** or **OSM ID**. A new object doesn't have an ID (it's ID is 0) until it is uploaded the first time to the OSM server. |
| 49 | | * Under **''Preferences -> [[Image(source:trunk/images/preferences/display.png,20)]] [Preferences/Display Display Settings] -> Look and Feel''** it is possible to en- or disable the display of objects ids in the toggle dialogs. |
| 50 | | * With **''File -> [[Image(source:trunk/images/downloadprimitive.png)]] [Action/DownloadObject Download object ...]''** it is possible to download **objects** by Ids. |
| 51 | | * **''View -> [[Image(source:trunk/images/about.png)]] [Action/InfoAboutElements Advanced info]''** opens seperated windows with informations about selected objects in text format. |
| 52 | | * **''View -> [[Image(source:trunk/images/about.png)]] [Action/InfoAboutElementsWeb Advanced info (web)]''** opens the **objects' pages** of selected objects on the [http://www.openstreetmap.org OSM website] in your web browser. |
| | 120 | == Technical properties == |
| | 121 | |
| | 122 | === Object id ===#ObjectId |
| | 123 | The OSM server assigns each object a unique number, the **object ID** or **OSM ID**. |
| | 124 | |
| | 125 | In JOSM, a new object doesn't have an ID (its ID is 0) until it is uploaded the first time to the OSM server. |
| | 126 | * Under **''[[JOSMImage(preference)]] [wikitr:/Help/Action/Preferences Preferences]''** (or **''`F12`''**) -> [[JOSMImage(preferences/display,24,link=,middle)]] **''[wikitr:/Help/Preferences/Display Display]''** it is possible to en- or disable the display of objects ids in the windows. |
| | 127 | * With **''File -> [[JOSMImage(downloadprimitive)]] [wikitr:/Help/Action/DownloadObject Download object ...]''** it is possible to download **objects** by Ids. |
| | 128 | |
| | 129 | **Note**: The display of object ids in the [wikitr:/Help/Dialog/SelectionList Selection List] can be set in Preferences under **''[wikitr:/Help/Preferences/Display Display]''**. |
| | 130 | |
| | 131 | |
| | 132 | === Object versions and history ===#Objectversionsandhistory |
| | 133 | Version numbers (versions) were introduced to simplify wiki-style editing. Unfortunately, to track changes to ways/relations you need to use more complex tools than simple comparison by version number. |
| | 134 | |
| | 135 | * Contents of the relation can change without change in version or id of the relation (a way can be changed, a node can be changed, a child relation can be changed). |
| | 136 | * Contents of the way can change without change in version or id of the way (a child node can be moved back and forth several times, but id of the way may stay the same). |
| | 137 | |
| | 138 | But you can always track complete history of one node based on history. |
| | 139 | Also, you can use time sliced data (region extracts by date) to inspect how objects were changing (and refer to object id and point in time from the database). |
| | 140 | |
| | 141 | **Note**: The display of object versions in the [wikitr:/Help/Dialog/SelectionList Selection List] can be set in Preferences under [wikitr:/Help/Preferences/Display Display]. |
| | 142 | |
| | 143 | ==== Information about latest version ==== |
| | 144 | * **''View -> [[JOSMImage(info)]] [wikitr:/Help/Action/InfoAboutElements Advanced info]''** (or Keyboard shortcut:**''`Ctrl+I`''**) opens separated windows with informations about selected objects in text format. |
| | 145 | * **''View -> [[JOSMImage(info)]] [wikitr:/Help/Action/InfoAboutElementsWeb Advanced info (web)]''** (or Keyboard shortcut:**''`Ctrl+Shift+I`''**) opens the **objects pages** of selected objects on the [osmwww: OSM website] in your web browser. |
