Multiple boundary=administrative without admin_level errors in Poland

[kubahaha]

Hello. Currently every way tagged with boundary=administrative without admin_levelresults in error. item: 9001 class: 9001001 example link: http://osmose.openstreetmap.fr/pl/error/5e626dc4-5d97-37e6-1d15-ef902e1c165b .

Encouraged tagging in Poland is to group ways in relations with proper admin_level (and name, etc). In case one boundary is relevant to multiple admin_levels wiki does not specify what to do, and adding admin_level=3;4;5 is useless as its already declared in relation. I believe this check should be applied only for relations.

[frodrigo]

This check come from JOSM validator https://josm.openstreetmap.de/browser/josm/trunk/resources/data/validator/combinations.mapcss cc @Klumbumbus

[matkoniecz]

It can be solved by removing boundary=administrative tag from ways where it is not needed.

This tagging scheme mixes tagging relations (preferred scheme) and tagging this info on ways.

But what is tagged on ways is redundant, incomplete and not needed.

Still, I think that Osmose/JOSM are wrong here.

They should complain about redundant boundary tag, not about missing admin_level tag.

Note: I proposed mass removal of such redundant boundary tags from ways some time ago and it was rejected. Maybe I should try again.

[matkoniecz]

related:

https://forum.openstreetmap.org/viewtopic.php?id=71873 proposal to mass remove boundary=administrative from ways in Poland.

https://wiki.openstreetmap.org/wiki/Talk:Tag:boundary%3Dadministrative#Explicitly_describe_tags_on_ways_as_optional_and_relation_tagging_as_recommended.3F "Explicitly describe tags on ways as optional and relation tagging as recommended?" on wiki