[Tagging] Admin Boundary admin_centre or label roles

tguen at tutanota.com tguen at tutanota.com
Fri Oct 1 09:52:45 UTC 2021


Yes, duplicated tags are a pain. It doesn't seem right to have all the tags duplicated and kept in sync, especially given my lack of confidence that they *will* be kept in sync. Having them all on only one of two features seems like a hack and sort of tagging for the renderer. Either way, it's breaking the 'one feature, one OSM element' rule.

I've been meaning to post a rant about how admin_level by itself is inadequate. The wiki claims the values describe the type of boundary as a number to avoid regional differences in names, e.g. state/province. In practice, the values only describe relative position in a government hierarchy. The values can't be used to find a particular type of feature. A city is usually an 8, but NYC is a 5 because its authority is above the county level. This is why I think the place tag should be on the boundary with admin_level. Having one on the boundary and the other on the node is awkward, and leads to things like using border_type to essentially duplicate the place tag.

If given enough time to adapt, I think making renderers handle relations is the best solution. If a renderer only wants a node, picking out the label (or city_centre) node shouldn't be too much trouble.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20211001/ff88e87d/attachment.htm>


More information about the Tagging mailing list