I was wondering how to tag the visitor hours of e.g. a hospital (section), an elderly group home, … Can I simply reuse ‘opening_hours’ for this?
on hospital opening_hours is unclear
it does not refer to when hospital is open (probably)
but it may refer to when people can come in for registration or maybe when it has standard main operating hours for things which are not time critical or it may refer to visiting hours
https://wiki.openstreetmap.org/wiki/Key%3Aopening_hours%3Avisitors
With microscopic levels of use.
2 Likes
I wouldn’t tag such information at all. The homepage of the facility would provide a much more accurate and up to date information about this.
2 Likes
The opening_hours:*= format isn’t good, and *:visitors= isn’t even a part of the facility. As users, it could use some access:conditional= (I won’t squeeze too many info into commented opening_hours= ) , or can be justified to get its own attribute if important and unique enough.
can you explain what you mean why it is reason against using opening_hours:visitors ?
1 Like
Purely as a low-effort attempt at a humorous argument, if you accept user groups in opening_hours:*= , this could be interpreted as when the beaches or pools are open to lifeguards Key:opening_hours:lifeguard - OpenStreetMap Wiki (should be changed to lifeguard:conditional= )
I don’t see a reason to complicate the opening_hours:*= format with something that has only 2 dozens use. Mixing up different aspects is never good a idea. If standardization and support are desired, commented opening_hours= already work best.
I see no reason at all to interpret all opening_hours:* as being about visitor groups.
Is there one?
opening_hours:*= is used for different parts. An application should be able to distinguish opening times for different parts, and those for different users. Allowing both loses the extensibility of allowing arbitrary new parts to be interpreted acceptably.
Besides, access restrictions for different users could already be done in access:conditional= . No need to start varying another format.
why you think so? Your own example of opening_hours:lifeguard is not such case
1 Like
I highly doubt that’s even possible to tag visiting hours for inpatient healthcare, from a logistical standpoint. At the hospitals I’ve worked in (about a dozen in 3 different states now), visiting hours weren’t a one-size-fits-everyone thing, but instead dictated by the patient’s medical and social needs and desires, with even the theoretical visitor curfew being negotiable. Hospices are similarly flexible about it from my experience.
This really feels like one of those “if you need to know, you’ll be provided with this information directly” situations.
6 Likes
Also, they are often suspended/limited (when given department is overloaded, during high incidence of flu etc.) but in practice various limits highly depend on situation.
Some hospital parts will enforce them stricter (say, maternity or where immunocompromised patients are) compared to section where less fragile people are present (section focusing on injured legs).
2 Likes
Sooooo… opening_hours:url=*
Naaa… General contact information (phone, URL, mail, webpage, …) should be sufficient.
1 Like
Visiting hours at hospitals, in my experience, vary by ward and the severity of patients on those wards and the timing of other activities, such as doctors rounds.
Hospitals have completely different opening hours, clinic hours for outpatients run much longer than visiting hours.
1 Like
As I said, I disagree with using it. And it simply gives a 3rd possibility, on the feature’s status or service. Mixing everything into opening_hours:*= doesn’t help makes it organized.
I think it would be nice to be able to specify opening hours for specific groups of people, just like for it is possible for different parts/services within an establishment (such as opening_hours:kitchen for restaurants). A hospital could have opening_hours:patients (if not 24/7) and opening_hours:visitors, a bathhouse could have opening_hours:men and opening_hours:women, a swimming pool could have opening_hours:lessons, opening_hours:families, opening_hours:60+…
This quickly goes out of hand, eg a children’s pool could be closed while children are still allowed in other pools. Unclear with opening_hours:children= alone.
Even if the suffix format is accepted to be every aspect, this needs distinguishing with service_times:*= . A feature can be always open for everyone, only having special provisions for different users at different times. Or it can further be argued as still the same opening_hours= , only different service_times:*= for different users.