Key:operator - OpenStreetMap Wiki
Key:operator
From OpenStreetMap Wiki
(Redirected from
Key:operator:fr
Jump to navigation
Jump to search
Help
Key:operator
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...
operator
Description
Сompany, corporation, person or any other entity who is directly in charge of the current operation of a map object
Group:
properties
Used on these
elements
Documented values:
29
Useful combination
operator:type
=*
operator:wikipedia
=*
operator:wikidata
=*
operator:short
=*
operator:website
=*
operator:phone
=*
operator:email
=*
See also
network
=*
owner
=*
ownership
=*
brand
=*
manufacturer
=*
builder
=*
Status:
approved
operator
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
The operator tag is used to name a company, corporation, person or any other entity who is directly in charge of the current operation of a map object.
Contents
How to use
1.1
Name of the operator
1.2
Owner or brand name isn't necessarily the operator
1.3
What the operator does and does not do
1.4
When there is no operator
Examples
2.1
Fast food
2.2
Hotel
2.3
Postal Services
2.4
Public transport
2.5
Shopping malls
2.6
Other
Further details
See also
Possible tagging mistakes
How to use
Name of the operator
When choosing the appropriate value for the
operator
=*
tag, it is beneficial to use exactly the same text including capitalization across all entities managed by the same structure. Please refer to
taginfo
, or the title of the associated Wikipedia article for the organization as a starting point. The
Name Suggestion Index
can help standardize an operator's tags.
Unlike
network
=*
operator
=*
is always a human-readable value. Some operators have been tagged by their legal registration name, while others have been tagged by their
trade name
. Sometimes mappers
abbreviate legal entity types
despite the general rule against
abbreviations
in names. In many cases, rail or public transport companies' names are abbreviated in
network
=*
but spelled out in full in
operator
=*
, with the abbreviation going in
operator:short
=*
Organization names are not required to be unique globally. An organization's name may be spelled differently depending on the location or language. To give data consumers and QA tools more certainty when working with operator tags, set
operator:wikidata
=*
to the operator's globally unique, language-independent Wikidata ID.
Owner or brand name isn't necessarily the operator
An operator isn't necessarily the owner of the map feature. Many chains (store, restaurants...) use a
franchise
system, where the brand does not operate the point-of-presence.
For example, a lot of transport, power and communication networks had been built by public administrations and are now operated by private companies. Railways may still be owned and maintained by the national government through its instrumentalities, agencies, and institutions (e.g. the UK, most of Western Europe, South Korea), but trains using them may be operated by different companies.
Bus operators may contract or franchise services to a different company (e.g. Flixbus routes, some public transport bus networks). Related infrastructure (stops, bus stations, bus-only roads) may remain under ownership of the transport agency or the bus company itself.
What the operator does and does not do
If multiple parties are involved in the existence of an object, then this may be helpful to decide who should be tagged as
operator
=*
(adapted from
[1]
):
The operator is tasked with the responsibility and care to ensure that the object meets its function. This includes the systematic planning, budgeting, preparation, and execution of activities aimed at sustaining the current function of the object.
The operator is thus not (necessarily) tasked with activities intended to change the function of the object, e.g. by modifying the object or by changing usage restrictions.
The operator may execute its tasks on behalf of some other party or governing authority, for example on behalf of the owner (who can be indicated with
owner
=*
).
The operator might delegate some of its tasks to specific other parties (who can be indicated with prefixed keys like
internet_access:operator
=*
toll:operator
=*
salting:operator
=*
etc.). However, if most or all operational tasks are delegated to one single party, then instead that party should be considered to be the (main)
operator
=*
When there is no operator
Since
operator
=*
should always contain a human-readable value,
operator
no
should be avoided. A feature that is known to have no operator can sometimes be tagged
informal
yes
. This tag is often used for social trails, unofficial tent camping sites, and other features found in wilderness areas that are not officially maintained or endorsed by the land management agency, but can be applied to any feature that has not been established on purpose. If
informal
yes
is not appropriate,
operator:type
none
can also be used to tag that a feature is specifically known to have no operator.
If the vast majority of a certain object in an area is operated by a certain organization and only very few by others then it may be sufficient to only tag the exceptions. For example, when nearly all roads in an area are managed by a local authority then it would be sufficient to only tag those that are not with an operator tag.
Examples
Fast food
Subway is one of the biggest franchise system in the US.
name
Subway
brand
Subway
(The name of the chain, as displayed to customers)
branch
Paris Notre-Dame
operator
Some company
(The company operating the restaurant. Usually visible on bills)
Hotel
Some amenities are directly managed by the company having the brand name.
tourism
hotel
name
Le Méridien
(the name of the hotel)
operator
Le Méridien
(the name of the company that manages the hotel, and which maybe manage other hotels too).
brand
Le Méridien
(The name of the chain, as displayed to customers)
branch
Piccadilly
Sometimes, it's more complicated. In this example; the company that manages the hotel is not the same company that owns the building. In other cases; there is another party between the owner and management company that rents or leases the building.
tourism
hotel
name
Holiday Inn
brand
Holiday Inn
branch
Burlington
operator
Westmont Hospitality Group
owner
InnVest REIT
Postal Services
Due to the emerging of private postal service providers, it may be useful for map readers to know which postal services provider operates a certain
amenity
post_box
In Germany there are already some private companies like PIN or Stadtbrief who install their own post boxes. Whomever wants to ship a letter has to choose the post box of their postal service provider.
Public transport
Public transport stations, stops, routes and other amenities (such as ticket-vending machines) can use the
operator
=*
key. This tag is recommended on route relations, and optional on other objects.
Public transport stops can have multiple operators, especially in areas near borders. Use the semi-colon value separator, e.g.
operator
De Lijn;TEC
Shopping malls
Often times, shopping malls are operated by a realty or
property management
group.
shop
mall
name
Ala Moana Center
operator
Brookfield Properties
Other
Other examples are pubs, restaurants and hotel chains, maybe also streets maintained by private companies.
Further details
There are a couple of common subkeys used to add further detail about the operator. These should be used instead of the not prefixed ones if the information given belongs to the operator, but not to the object itself.
Key
Description
Taginfo
operator:abbr
=*
Abbreviated name of the operator
operator:abbr
More details at tag
info
operator
addr:*
=*
Postal address to contact the operator
Address components can be specified separately in various keys, e.g.
operator
addr:street
=*
operator
addr:housenumber
=*
, etc.
operator
addr:country
=*
may be particularly useful to indicate the operator of the object is located in a different country
operator:addr
More details at tag
info
operator:addr:street
More details at tag
info
operator:addr:country
More details at tag
info
operator:phone
=*
Phone number to contact the operator
operator:phone
More details at tag
info
operator:short
=*
Short name of the operator
operator:short
More details at tag
info
operator:type
=*
Classification of the operator, e.g. a private or public entity
operator:type
More details at tag
info
operator:website
=*
Website of the operator
operator:website
More details at tag
info
operator:wikidata
=*
The Wikidata ID of the operator
operator:wikidata
More details at tag
info
operator:wikipedia
=*
The Wikipedia link of the operator
operator:wikipedia
More details at tag
info
See also
operator:website
=*
Bremen Schema
(abandoned) - A schema that proposes to add contact information about a POI to the node via using contact:* instead of adding addr:*
Key:contact#Mail_address
contact:housenumber
=*
contact:street
=*
contact:city
=*
contact:postcode
=*
/ ...
owner
=*
for the name of the entity that owns the feature
ownership
=*
for the type of owner, eg. "public", "private",…
builder
=*
for the name of the entity that build the feature
operator:type
=*
for the type of operator, eg. "public", "private", …
Possible tagging mistakes
operator_name
More details at tag
info
operator_name=*
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
operator
yes
$1%
$1%
$1%
$1%
More details at tag
info
operator=yes
‒ Write the name of the operator instead, or consider
operator:type
=*
or
informal
no
if the operator's name is unknown
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
operator
no
$1%
$1%
$1%
$1%
More details at tag
info
operator=no
‒ Use
informal
yes
or
operator:type
none
instead
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
recycling:operator
More details at tag
info
recycling:operator=*
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
Retrieved from "
Categories
Key descriptions for group "properties"
Key descriptions
Key descriptions with status "approved"
Properties
Tagging Mistakes
Uses semicolon in tag value
Hidden categories:
Pages unavailable in Dutch
Tag and key pages with missing images
Item with no description in language NL
Item with no description in language ZH-HANS
Item with no description in language ZH-HANT
Navigation menu
US