A node can also be defined as part of a particular layer =* or level =*, where distinct features pass over or under one another; say, at a bridge. Nodes can be used to define standalone point features, but …

This call includes all nodes in the bounding box, all ways referring to any of these nodes, all member nodes of these ways whether these are inside the bounding box or not, all relations that have such a …

recurse relation-node collects the nodes that are members of the above found relations. The result is placed in the variable nodes (we don't need it there anymore, just to keep relations in the default …

combines the results of two tag queries with a union statement, then sends that result to the default set _. It is equivalent to: ( node[name="Foo"]; node[name="Bar"]; )->._; To write elements to a named …

<osm-script output="json"> <query type="relation" into="hr"> <has-kv k="route" v="hiking"/> <has-kv k="name:de" v="Meraner Höhenweg"/> </query> <union> <item set="hr"/> <recurse from="hr" …

node; way; rel; – will revert everything; this is the default value when you don't specify anything node[ford=yes]; – will revert all nodes with ford = yes tag

To make a connection when drawing a way, just click on the way, or node, you wish to connect to. Using the short cuts 'n' or 'a', and then clicking on a node or way, will stem a new way from that point.

In an open way (a linear representation of a feature) the first and last node are not identical. Common examples of linear representation with open ways include most roads, streams and railway lines, …

When clicking on an object, a popup shows all the information of the selected node, way or relation: type and id, tags, coordinates, relationship memberships and meta data are shown, if available.

Node Network mapping is still in development. History and reasoning behind choices are described to help people make up their minds about these matters. If you just want to know how it's done, Jump to …