Do not warn about "Nodes at the same position" if tag(s) with different values

[Emvee]

In the Netherlands, GSM antenna's are imported from a database into OpenStreetMap. Multiple antenna can be in the same tower leading to one node per antenna that share the same position:

  <node id='599529331' ... lat='51.8753285' lon='4.4998153'> 
    <tag k='height' v='35' /> 
    <tag k='man_made' v='tower' />
    <tag k='technology' v='UMTS' />
    <tag k='tower:type' v='communication' />
  </node>

  <node id='599529332' ... lat='51.8753285' lon='4.4998153'>
    <tag k='height' v='36' />
    <tag k='man_made' v='tower' />
    <tag k='technology' v='GSM 1800' />
    <tag k='tower:type' v='communication' />
  </node>

In this case the warning is not valid because the height and technology are different, but more general I think that if two nodes have tag(s) with the same key but with different values this warning should not be given or at least reported as information/other.

[stoecker]

You can ignore individual false warnings. What you suggest is nearly impossble to implement. How do you want to distiguish e.g. a double restaurant entry where one has wrong name from the example you give above?

I think the way the GSM antennas are imported is broken by design. One node should be used with something like "technology:umts=yes", "technology:gsm1800=yes", ...

[Emvee]

Thanks for the feedback and I do understand your objections and agree with what you are proposing, i.e. something like "technology:umts=yes", "technology:gsm1800=yes", ...

[skinkie]

@stoecker

False warnings are there to be solved. Again there are no strict specifications to distinguish nodes. Since in OSM the 3D component is not (yet) fixed, the height does give you a third dimension. In that perspective, tagging two sequences of housenumbers in an appartment would also give false positives.

Regarding to your 'broken by design'. That is not true. The hole concept of appending things in one node is fubar, since it would not be a k/v-store anymore + there is not even a specification for that! The tower relationship (the proposed relationship mentioned on the wiki) is fully using nodes on a fixed location and a tower relationhip to merge them to one site.