Key:type - OpenStreetMap Wiki
Key:type
From OpenStreetMap Wiki
Jump to navigation
Jump to search
Help
Key:type
In other languages
Afrikaans
asturianu
azərbaycanca
Bahasa Indonesia
Bahasa Melayu
bosanski
brezhoneg
català
čeština
Crnogorski
dansk
eesti
Esperanto
euskara
Frysk
Gàidhlig
galego
hrvatski
Ido
interlingua
íslenska
italiano
Kreyòl ayisyen
kréyòl gwadloupéyen
kurdî
latviešu
Lëtzebuergesch
lietuvių
magyar
Nederlands
norsk
norsk nynorsk
occitan
polski
português
română
sardu
shqip
slovenčina
slovenščina
srpski (latinica)
suomi
svenska
Tagalog
Tiếng Việt
Türkçe
Zazaki
Ελληνικά
беларуская
български
македонски
монгол
русский
српски / srpski
українська
հայերեն
עברית
العربية
سرائیکی
فارسی
پنجابی
پښتو
नेपाली
मराठी
हिन्दी
বাংলা
ਪੰਜਾਬੀ
தமிழ்
മലയാളം
සිංහල
ไทย
မြန်မာဘာသာ
한국어
ქართული
ⵜⴰⵎⴰⵣⵉⵖⵜ
中文（简体）
中文（繁體）
粵語
Other languages...
type
Description
Type of a relation.
Group:
properties
Used on these
elements
Documented values:
21
See also
*:type
=*
Status:
de facto
type
More details at tag
info
Tools for this tag
taginfo
AD
AT
BE
BR
BY
CH
CN
CZ
DE
DK
FI
FR
GB
GR
HU
IE (N+S)
IN
IR
IT
LI
LU
JP
KP
KR
NL
NO
PL
PT
RU
ES
AR
MX
CO
BO
CL
EC
PY
PE
UY
VE
TW
UA
US
VN
overpass-turbo
QLever
Postpass via overpass-turbo
OSM Tag History
type
=*
on a
relation
object specifies its type and interactions among its members. Established and proposed relation types are listed below.
type
has been also occasionally used as an add-on tag to specify a "variant" of a feature category on ways and points. This approach conflicts with its use in relations and
should be avoided
. Also, for elements with multiple
top-level tags
, it is not clear to which one the
type
refers to. Instead, use suffix-based or subtag-based approach, as described in
*:type
=*
Contents
Established relations
Uncommon relations
Proposed uses
3.1
Junctions, intersections, grade separated crossings, and embankments
3.2
Area hierarchies and other relations for areas
3.3
Addressing
3.4
Others
Possible tagging mistakes
Quality Assurance
See also
Established relations
Type
Status
Members
Comment
Statistics
Image
multipolygon
de facto
Areas
where the outline consists of multiple ways, or that have holes.
route
de facto
An established (often signposted) route over multiple highways for a given transport mode (hiking, cycling, bus or motorized traffic)
route_master
approved
Contains closely related (parallel, opposite, variant, ...) routes only; heavily used to group route variants in public transport.
restriction
de facto
Permitted turns on a highway junction.
boundary
de facto
Political, administrative and similar boundaries not always observable on the ground. Defined in similar manner as multipolygons.
public_transport
approved
Part of the
OSM public transport scheme
. Mainly used by
public_transport
stop_area
destination_sign
approved
Destination signs at or before intersections.
waterway
approved
Groups multiple segments of a named
waterway
=*
enforcement
approved
Traffic enforcement devices; speed cameras, redlight cameras, weight checks, ...
connectivity
approved
Indicates how the lanes in the "from" member connect to those in the "to" member.
Uncommon relations
Type
Status
Members
Comment
Statistics
Image
associatedStreet
controversial
House numbers related to a street. See
Karlsruhe scheme proposal
. Banned by community in a few countries.
street
proposed
Bind all parts of a street together and everything else that belongs to it. See
Relations/Proposed/Street
superroute
controversial
Groups "concatenable" route relations that form one long route. Its usefulness is disputed.
network
in use
Groups route relations that belong to the same network, but are not usually contiguous ("concatenable").
site
in use
Groups elements of a "site" with
node
members, instead of using a
multipolygon
. See
Relations/Proposed/Site
multilinestring
in use
A discontiguous series of unclosed ways that semantically represents a single physical object.
building
in use
Sometimes used to group elements that form a building in simple 3D modelling, but not usually required.
bridge
proposed
Groups together all elements of one bridge. See
Relations/Proposed/Bridges and Tunnels
tunnel
proposed
Groups together all elements of one tunnel. See
Relations/Proposed/Bridges and Tunnels
user defined
All commonly used values
according to
Taginfo
Taginfo
Proposed uses
Abandoned and obsolete proposals not included.
Junctions, intersections, grade separated crossings, and embankments
Relations/Proposed/Bridges and Tunnels
grouping all ways using a common bridge or tunnel
Relations/Proposed/Junctions
all the ways that make up a junction (such as a motorway intersection)
Relations/Proposed/Turn hints
Hints for whether a turn is a slight left, sharp left, fork, etc.
Relations/Proposed/turn lanes
which turns are allowed from a given lane
Area hierarchies and other relations for areas
Relations/Proposed/Area
to define areas between ways and lanes (linear crossover), virtual and physical dividers and crossover-possibilities, etc.
Relations/Proposed/Label
Manually placed labels or icons in areas
Relations/Proposed/Level
For floors in 3D-Objects (Subway stations, buildings, etc.).
Relations/Proposed/Sled
for grouping together all relevant items of a sled run.
Addressing
Relations/Proposed/Cluster
for grouping features with a collective name or address etc.
Karlsruhe Schema
Relations/Proposed/Postal Addresses
Others
Relations/Proposed/Defaults
defines a set of default values (speed limits, oneways, access) for a country, a state
Relations/Proposed/Provides feature
to associate an object such as a restaurant, hotel or museum with one or more map features such as addresses or entrances.
Proposed_features/Group_Relation
a relation to create groups of objects (e.g. when they have a common name as group) without requiring additional tags (they are defined through their members).
Relations/Proposed/Node
a relation to have several node objects at the same location without adding actual geometry objects (e.g. for things attached to a pole, antennas on a mast, etc.)
Possible tagging mistakes
type
More details at tag
info
type
=*
‒ This key should only be used on relations. Other object types should be sub-classified using one of schemes described in
*:type
=*
or a different tag.
If you know
places with this tag
, verify if it could be tagged with another tag.
Automated edits are
strongly discouraged
unless
you really know what you are doing
Quality Assurance
Review relations with no
type
=*
tag (
OSM Community topic
Overpass query
See also
*:type
=*
Retrieved from "
Categories
Key descriptions for group "properties"
Key descriptions
Key descriptions with status "de facto"
Properties
Tagging Mistakes
Relations
Hidden categories:
Tag and key pages with missing images
Item with no description in language FI
Item with no description in language HU
Item with no description in language ZH-HANS
Item with no description in language ZH-HANT
Navigation menu
US