Key:contact:*



From OpenStreetMap Wiki

(Redirected from Key:contact)


Jump to navigation  Jump to search  

Key:contact:* - Other languages

  •  Afrikaans 
  •  asturianu 
  •  azərbaycanca 
  •  Bahasa Indonesia 
  •  Bahasa Melayu 
  •  bosanski 
  •  brezhoneg 
  •  català 
  •  čeština 
  •  dansk 
  •  Deutsch 
  •  eesti 
  •  English 
  •  español 
  •  Esperanto 
  •  euskara 
  •  français 
  •  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 
  •  українська 
  •  հայերեն 
  •  עברית 
  •  العربية 
  •  فارسی 
  •  ਪੰਜਾਬੀ 
  •  پنجابی 
  •  پښتو 
  •  سرائیکی 
  •  नेपाली 
  •  मराठी 
  •  বাংলা 
  •  தமிழ் 
  •  മലയാളം 
  •  සිංහල 
  •  ไทย 
  •  မြန်မာဘာသာ 
  •  한국어 
  •  ქართული 
  •  ⵜⴰⵎⴰⵣⵉⵖⵜ 
  •  中文(简体) 
  •  中文(繁體) 
  •  日本語 
  •  粵語 
  • Public-images-osm logo.svg Prefix contact:*
    Contact info.jpg
    Description
    The contact:* keys describe contact information. Edit this description in the wiki page. Edit this description in the data item.
    Group: annotations
    Used on these elements

    may be used on nodesmay be used on waysmay be used on areas (and multipolygon relations)may be used on relations

    See also
    Status: in use
    taginfo: contact:*

    information sign

    This page describes a key prefix rather than a simple key.

    The prefix for several contact:*=* keys to describe contact information.

    Values

    You should only add contact information to POIs and not to any private address!

    Email-addresses which are only available on a website after solving a captcha, or which are in other ways obfuscated to protect against SPAM-bots should not be tagged in OSM. The same applies to fax and phone numbers.

    a question mark

    This article or section contains questionable, contentiousorcontroversial information. See the talk page for more information.

    Some details below are incompatible with phone numbers outside of Germany or when written in languages other than German.

    What is used here: phone and fax number format ( DIN 5008): +<country_code> <national_destination_code> <subscriber_number>-<direct_inward_dialing>

    Contact

    Key Value Element Comment Taginfo Photo

    Contact details

    contact:phone +44 11223 456-789 node way area relation Telephone number ( DIN 5008 format: +<country_code> <national_destination_code> <subscriber_number>-<direct_inward_dialling>). See also the more popular phone=*.) Black telephone icon from DejaVu Sans.svg
    contact:website http://example.com node way area relation Website-url (see also the more popular website=* and website:*=*) Vista-www.png
    contact:email mail@example.com node way area relation E-mail address (see also the more popular email=*) Contactenos.jpg
    contact:fax +44 11223 456-789 node way area relation A dedicated telephone number connecting to a telefacsimile (fax) machine. See also the more popular fax=*). Emoji u1f4e0.svg
    contact:mobile +44 11223 456-789 node way area relation A telephone number connecting to a mobile phone. The more general tag contact:phone=* should be preferred. Roadsign - Cellphone.svg
    contact:tty +44 11223 456-789 node way area relation A dedicated telephone number connecting to a teletypewriter (tty). Emoji u1f4e0.svg
    Key Value Element Comment Taginfo Photo

    Social media, messengers, web services

    contact:facebook full facebook URL or FacebookUserName node way area relation Facebook profile - preferably the full URL (because there are many different kinds of pages in facebook), though simply the public username is also used. (see also facebook=*) Facebook f logo (2019).svg
    contact:instagram full instagram URL or InstagramUserName node way area relation Instagram account name (also used on Threads) or full Instagram URL Instagram logo 2016.svg Threads (app) logo.svg
    contact:vk VK.com node way area relation VK link to social network service VK Compact Logo (2021-present).svg
    contact:twitter OpenStreetMap node way area relation Twitter account name or full URL (see also twitter=*) Twitter-logo.svg
    contact:youtube Youtube account/channel URL node way area relation YouTube URL of account or channel officially used by the POI. Sometimes only the YouTube username is indicated. YouTube Logo 2017.svg
    contact:ok ok URL node way area relation ok link to social network service. Ok new logo.png
    contact:webcam webcam URL node For denoting a webcam's location, use a node with the tag surveillance:type=camera. See also Webcams for more information Camera-example.jpg
    contact:telegram https://t.me/Example or Telegram number node way area relation Telegram account name or full URL or Telegram number officially used by the POI. Telegram logo.svg
    contact:whatsapp WhatsApp number node way area relation WhatsApp number officially used by the POI. WhatsApp.svg
    contact:linkedin Username node way area relation LinkedIn account name or full URL LinkedIn Logo.svg
    contact:pinterest Pinterest URL node way area relation Pinterest URL officially used by the POI. Pinterest Logo.svg
    contact:viber +44 11223 456-789 node way area relation Viber account name (phone number) or full URL Viber logo.svg
    contact:foursquare https://foursquare.com/v/Example node way area relation Foursquare account name (hash) or full URL Foursquare logo 2018.png
    contact:skype SkypeName node way area relation Skype login name Skype logo (2019–present).svg
    contact:xing Username node way area relation XING account name or full URL Xing logo.svg
    contact:tiktok Username node way area relation TikTok account name or full URL Tiktok logo text.svg
    contact:vhf VHF Channel or Frequency node way area relation Of interest for maritime and airport services Torre de controle Rio de Janeiro (Galeao).jpg
    contact:flickr Flickr URL node way area relation Flickr URL. Similar to all others, this is where the POI can be officially contacted, or where they broadcast information. This should not point to a self-taken photo depicting the POI. Flickr wordmark.svg
    contact:mastodon @username@server.example node way area relation Mastodon social network handle or full URL Mastodon Logotype (Full Reversed).svg
    contact:matrix @username:server.example node way area relation Matrix social network handle Matrix logo icon 169963.png
    contact:mobilizon @username@example.com or https://example.com node way area relation Mobilizon social network handle or full URL Mobilizon EN.png
    contact:sip sip@example.com node way area relation SIP address
    contact:diaspora username@server.example node way area relation Diaspora social network handle or full URL Diaspora logotype.svg
    contact:gnusocial username@server.example node way area relation GNU Social social network handle or full URL GNU-social-logo.svg
    contact:xiaohongshu Xiaohongshu URL node way area relation Xiaohongshu social network handle or full URL Xiaohongshu logo&slogan.png
    contact:user_defined user defined node way area relation All commonly used namespace keys according to Taginfo
    Key Value Element Comment Taginfo Photo

    Mail address

    contact:street street name node way area relation For use when the contact address is not the same as the address of the physical location.

    For denoting the street name where a POI is located, see also addr:street=*

    contact:housenumber housenumber node way area relation For use when the contact address is not the same as the address of the physical location. (Status: "draft" Text-x-generic.svg)

    For denoting the housenumber where a POI is located, see also addr:housenumber=*

    contact:postcode postcode node way area relation For use when the contact address is not the same as the address of the physical location.

    For denoting the postcode number where a POI is located, see also addr:postcode=*

    contact:city city name node way area relation For use when the contact address is not the same as the address of the physical location.

    For denoting the city name where a POI is located, see also addr:city=*

    contact:country country node way area relation For use when the contact address is not the same as the address of the physical location.

    For denoting the country where a POI is located, see also addr:country=*

    contact:pobox Post Box Number node way area relation Companies and organizations sometimes have a post office box (P.O. Box) to receive mail instead of to their physical address. The value should contain the box number as well as a post office identifier, such as a post code. Note this may be different from addr:postcode=*. USPS Post office boxes 1

    This table is a wiki template with a default description in English. Editable here.

    Overpass Turbo query (2022-02-04) showing the use of contact: keys on POI addresses in France: nearly 18000 locations listed.

    Addressing scheme in France

    Note that in France (especially), contact:housenumber keys are mostly used on POIs to add their addresses without consideration of whether the physical address is different from the postal address but instead of addr: keys reserved for mapping addresses as unique features.

    This usage is relatively widespread, see TagInfo contact:housenumber page, it has not yet (2023-10-09) been approved by the community.

    A draft about this usage called "Schéma de Charlieu" can be found on the OSM wiki.

    Qwant Maps promotes the display of the values of these POIs labels when they exist.

    Organic Maps displays contact: addresses on POI's pop-ups when it exists.

    Existing tagging schemes

    For the most common keys, the shorter version outside the 'contact' scheme is used more frequently: phone=*, fax=*, email=* and website=*, with other contact tags used rarely outside the namespace scheme. Both schemes have been in use for a long time and still exist in parallel. Many applications are able to use both of them.

    At the same time a proposal to deprecate contact:phone=* was not successful - Discussions/tagging/contact:phone or phone. Idea of deprecating either tags without contact: prefix or ones with contact prefix is repeatedly suggested, often triggering huge discussion and ending with conclusion that there is no consensus. Please, read past discussion before starting a new one[1][2][3][4].

    Popularity of phone=* and contact:phone=* indicating ongoing and uninterrupted preference of simple tagging scheme over contact: prefix, see also [5] which is most probably induced by editor presets.

    There were also attempts to deprecate, mechanically retag or promote either version of many other contact tags[6]

    See also

    External Links

    References

    1. https://lists.openstreetmap.org/pipermail/tagging/2019-December/thread.html#49474 - December 2019 thread
  • https://lists.openstreetmap.org/pipermail/tagging/2019-August/thread.html#47668 August 2019 Thread
  • https://lists.openstreetmap.org/pipermail/tagging/2020-May/thread.html#52379 - May 2020 thread, over 50 messages
  • https://lists.openstreetmap.org/pipermail/tagging/2022-January/thread.html#63734 January 2022 thread
  • Contact:website / website / url
  • Proposed features/Social media contact prefix
  • Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=Key:contact:*&oldid=2732138"

    Categories: 
    Key descriptions for group "annotations"
    Key descriptions
    Key descriptions with status "in use"
    Key prefixes
    Annotations
    Namespaces
    Questioned content
    External reference tag
    Hidden categories: 
    Pages unavailable in Dutch
    Mismatched description in default namespace
    Mismatched description
    Item with no description in language UK
    Item with no description in language FI
    Item with no description in language NL
    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


    Personal tools  



    English
    Create account
    Log in
     

    Namespaces  



    Page
    Discussion