Contact:website / website / url
Comparison of "contact:website / website / url" tagging and showing some pros and cons.
Notes and advantages
All two (three) taggings have equal rights. For additional information see following table for illustration.
Using non contact*:* scheme
|
Using contact*:* scheme
|
---|---|
email=* / fax=* / phone=* / website=* / ( url=*) / ( mobile=*) / ( facebook=*) / ( vk=*) | contact:*=* ( contact:email=* / contact:fax=* / contact:phone=* / contact:website=* / contact:mobile=* / contact:facebook=* / contact:vk=*) |
There is an advantage of usage the scheme without contact:*=* . When you don't use any editor presets, it is faster to use, because it's not necessary to type in so many letters for each key name parameter. For older values (e.g. website, phone) there is a higher amount of database distribution, this is reasonable because this was the initial tagging scheme, see #Taginfo & Tag History.
|
There is an advantage of contact:*=* contact=*, because mostly you will get consistent overview of tag arrangement, which will be a kind of a Namespace group block for contact=*. This is similar to other Namespaces, which are in a wide use for the OpenStreetMap database, e.g. Namespace group block of address information, see addr=*. When using this contact:*=* scheme and having these Namespace group blocks available it might be less error prone to get consistent data sets for existing poi objects in long run. This may also speed up different processing steps, e.g. while adding tags, while removing tags and, or while other maintenance work (like changing/updating key/values). For newer contact values (e.g. facebook, vk, mobile) there is a higher amount of database distribution, see #Taginfo and OSM Tag History.
|
addr:city=New Town |
addr:city=New Town |
Find examples via: https://overpass-turbo.eu/s/BLM (click "Run" button top left to show results) |
Find examples via: https://overpass-turbo.eu/s/BLL (click "Run" button top left to show results) |
Please decide by yourself, which tagging scheme you prefer. Interpreter software should know all of them.
Taginfo and OSM Tag history
To illustrate how often each tag is used, here are the Taginfo statistics and OSM Tag History graphs for these different tags:
Taginfo without contact | Taginfo contact scheme | OSM Tag History graph | |
---|---|---|---|
website=* | contact:website=* | website=* vs contact:website=* vs url=* | url=* |
Taghistory.raifer.tech live Chart Taginfo chronology |
phone=* | contact:phone=* | phone=* vs contact:phone=* |
Taghistory.raifer.tech live Chart |
email=* | contact:email=* | email=* vs contact:email=* |
Taghistory.raifer.tech live Chart |
fax=* | contact:fax=* | fax=* vs contact:fax=* |
Taghistory.raifer.tech live Chart |
mobile=* | contact:mobile=* | mobile=* vs contact:mobile=* |
Taghistory.raifer.tech live Chart |
facebook=* | contact:facebook=* | facebook=* vs contact:facebook=* |
Taghistory.raifer.tech live Chart Taginfo chronology |
vk=* | contact:vk=* | vk=* vs contact:vk=* |
Taghistory.raifer.tech live Chart |
instagram=* | contact:instagram=* | instagram=* vs contact:instagram=* |
Taghistory.raifer.tech live Chart Taginfo chronology |
See also
- Gym / Fitness centre - Comparison & overview the distribution of gym and fitness tags.
- Discussions/tagging/contact:phone or phone - 11-2019 Rejected attempt to merge phone=* and contact:phone=* to only phone=*.