Using both phone and contact:phone on the same object. Is that an error?

OSM Phone Number Validation has added a test for the use of phone and contact:phone [1] on an object at the same time.

In this post @dieterdreist wondered if that is actually an error which caused me to wonder as wel.

So, what do you folks think about that.

My initial thought: It might be not a real error but is is undesirable, there is a risk that the keys go out of sync.


  1. All results I have seen are for the same number ↩︎

3 Likes

Think Osmose flags this combo if the numbers are not the same. I could imagine a business has a regular number and a number for customers to call… the contact:phone, so I’d expect them to be different.

Who calls that “regular” number?

3 Likes

If both numbers are identical it’s an error and one of the tags can be removed

5 Likes

Using both phone and contact:phone on the same object. Is that an error?

no, it is a double-tagging (see also people adding healthcare=pharmacy to amenity=pharmacy

note: there were repeated attempts to deprecate either phone or contact:phone - attempts in either direction were rejected

If both numbers are identical it’s an error

no, it is not

1 Like

OSM Phone Number Validation has added a test for the use of phone and contact:phone on an object at the same time.

(I am the author of the tool)

The test is rather for duplicate numbers in general, whether in the same tag or different tags (across phone, contact:phone, mobile and contact:mobile). My “suggested fix” is to remove the number in the less common tag.

no, it is a double-tagging

Perhaps there is a subtle difference between double tagging and duplicate tagging.

It is the same thing, as far as I know.

Difference is what is implied about situation.

Do you mean the difference between “Contact the feature at this number that belongs to it” (phone=*) versus “Contact this number about the feature” (contact:phone=*)? For some mappers that seems to be essentially the difference between addr:housenumber/street=* and contact:housenumber/pobox/street=*, but not for social media keys as far as I can tell.

I meant difference between “duplicate tagging” (suggesting that one of tags should be removed) and “double tagging” which does not make such implication or makes it less strongly.