You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tagging dependencies support is a key feature in OSM quality assurance.
Wiki and DataItems state some tags require to combine with another(s) one(s) on the osm feature we intend to tag to be valid.
Examples : https://wiki.openstreetmap.org/wiki/Key:voltage:primary requires https://wiki.openstreetmap.org/wiki/Key:transformer
Although those tags are specific and technical ones, tagging dependencies covers many tagging scheme in OSM.
It is currently not possible to implement such checks in iD validation to encourage users to change their tagging with a message.
It leads to pretty big inconsistencies and confusion, when some tags are used in context they're not supposed to.
Would you mind supporting this in iD logic please?
Best regards
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Description
Dear maintainers,
Following openstreetmap/id-tagging-schema#447 and openstreetmap/id-tagging-schema#415 a new validation features would be useful to add to iD.
Tagging dependencies support is a key feature in OSM quality assurance.
Wiki and DataItems state some tags require to combine with another(s) one(s) on the osm feature we intend to tag to be valid.
Examples : https://wiki.openstreetmap.org/wiki/Key:voltage:primary requires https://wiki.openstreetmap.org/wiki/Key:transformer
Although those tags are specific and technical ones, tagging dependencies covers many tagging scheme in OSM.
Expected result: Features like https://www.openstreetmap.org/way/1002130808 should raise a warning since no transformer=* is used in combination with voltage:primary=*.
It is currently not possible to implement such checks in iD validation to encourage users to change their tagging with a message.
It leads to pretty big inconsistencies and confusion, when some tags are used in context they're not supposed to.
Would you mind supporting this in iD logic please?
Best regards
Screenshots
No response
The text was updated successfully, but these errors were encountered: