Talk:Tag:type=health

Wrong key

type=* should be used only for types of relations. maro21 14:02, 3 November 2024 (UTC)

This is a relation-only tag, but this relation type can be used on nodes (e.g. health_facility:type=office for tagging the staff with health_person:type=*), areas (e.g. health_facility:type=health_centre for tagging the offices inside with health_facility:type=office, when their locations are not known) or other relations of type=health. This is a relation type for health care related objects, intended as container relation and for tagging permanent information, which have no fixed location or where it is not known. The problem of health care is that the offered service type/specialties and service level depends on the received training of the staff of the facilities at the end. As I was the first one (there is also Proposal:Node (not intended for logical object linking), which I was pointed to, after inventing Relation:multifeature), who used relation for fixing things, that should be better fixed in the OSM data types/API. As this type of use for relations is new many mappers misused this as a normal tag, but it was never intended for normal use outside of relations. Maybe this page should be moved to the relation namespace now. Fabi2 (talk) 17:34, 3 November 2024 (UTC)

What I meant is that we use type only for defining relations, not as an attribute on other features. maro21 22:53, 3 November 2024 (UTC)

This tag is for the use with relations only, but these type=health-relations can define other health care related features and used on these features. Relation:multifeature is a more common useable successor of the same idea, after I had the same problem with layers specialties. At the time the page was created the "Relation:"-namespace did not exist, so the page should be moved now. --Fabi2 (talk) 00:27, 4 November 2024 (UTC)