|Сompany, corporation, person or any other entity who is directly in charge of the current operation of a map object|
|Used on these elements|
|Documented values: 25|
|Tools for this tag|
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.
How to use
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.
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.
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 and communication networks had been built by public administrations and are now operated by private companies. In some places, the national government retains ownership of the infrastructure, as in power grids and railways. Power grids and their related assets and facilities may be operated and maintained by a private entity while ownership remain under the national government (e.g. in the Philippines). Railways may still be owned and maintained by the national government (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.
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, language, or personal preference. 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. The Name Suggestion Index can help standardize an operator's tags.
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.
Subway is one of the biggest franchise system in the US.
- 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)
Some amenities are directly managed by the company having the brand name.
- 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)
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.
- name=Holiday Inn
- brand=Holiday Inn
- operator=Westmont Hospitality Group
- owner=InnVest REIT
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 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.
Other examples are pubs, restaurants and hotel chains, maybe also streets maintained by private companies.
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.
|operator:abbr=*||Abbreviated name of the operator|
|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:phone=*||Phone number to contact the operator|
|operator:short=*||Short name of the operator|
|operator:type=*||Classification of the operator, e.g. a private or public entity|
|operator:website=*||Website of the operator|
|operator:wikidata=*||The Wikidata ID of the operator|
|operator:wikipedia=*||The Wikipedia link of the operator|
- 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=* / ...