streetcomplete / StreetComplete

Easy to use OpenStreetMap editor for Android
https://streetcomplete.app
GNU General Public License v3.0
3.87k stars 353 forks source link

Quest suggestion: hairdresser for men/women/all #4833

Closed FloEdelmann closed 1 year ago

FloEdelmann commented 1 year ago

General

Affected tag(s) to be modified/added: female=yes or male=yes (for shop=hairdresser) Question asked: Which customers does this hairdresser serve?

male=no or female=no could be tagged together with female=yes or male=yes, respectively.

Checklist

Checklist for quest suggestions (see guidelines):

Ideas for implementation

Element selection:

nodes with
  shop = hairdresser
  and !female and !male and !unisex

Or, to cover edge cases like this one I discovered:

nodes with
  shop = hairdresser
  and female != yes and male != yes and unisex != yes

In this case, should the respective other existing keys should be deleted, in addition to setting female=yes / male=yes? Or should the unusual only value also be considered valid?

Metadata needed: None.

Proposed UI: Simple text selection: "Women only" / "Men only" / "Both"


Note: this is a follow-up suggestion to #4829. The unisex tag is considered "burnt" and should not be tagged by StreetComplete. For the quest selection, it can still be considered.

Discostu36 commented 1 year ago

I find it an important information for non-binary people to know if a hairdresser is gender neutral or if they have to decide to use a door for men or a door for women. In my opinion, a quest without a third option should not be done.

mnalis commented 1 year ago

If unisex is considered burnt, we should use this quest to clean it up. I.e. match on

nodes with
  shop = hairdresser
  and female != yes and male != yes

and then upon answering the quest remove any existing unisex tag.

Discostu36 commented 1 year ago

Please do not remove tags from OSM without an accepted deprecation proposal.

matkoniecz commented 1 year ago

If unisex is consider burnt, we should use this quest to clean it up.

The problem is that it is burnt without a proper replacement existing for some of tasks it was tried to be used.

Please do not remove tags from OSM without an accepted deprecation proposal.

There are some cases where it is entirely fine without deprecation proposal (though not in this specific case).

mnalis commented 1 year ago

I find it an important information for non-binary people to know if a hairdresser is gender neutral or if they have to decide to use a door for men or a door for women. In my opinion, a quest without a third option should not be done.

While I agree that it is important information for non-binary people, there are few issues with that third option, though:

mnalis commented 1 year ago

Also, at the quest level, I find those problems:

mnalis commented 1 year ago

Please do not remove tags from OSM without an accepted deprecation proposal. There are some cases where it is entirely fine without deprecation proposal (though not in this specific case).

Note that unisex=* wiki does however say:

In case of conflict with other gender-based tags (e.g. female=*), resolve in favour of the more specific tag.

Which seems to suggest that mappers should replace unisex tag if usage is clear male+female (or leave note to later add description=* or something if the unisex meant something different in that specific case).

Discostu36 commented 1 year ago
  • how is causal mapper to know when non-binary people are welcome? Do hairdressers in your area usually put such notices on the door?

On the contrary, if there is no sign about gender on the door, I'd consider it a unisex hairdresser where every person is welcome.

  • how would you actually tag that third option? Current male/female/unisex is not adequate.

In my opinion, it is adequate and the definition is quite clear: Unisex clothing, toilets or hairdressers can be used by anybody, they are gender-neutral. But as can be seen on wiki, there seem to be people with a different opinion on that.

So from my perspective, there are now these options, as long as there is no clear definition on wiki:

  1. Wait for a proposal that solves the conflict with a clear definition of unisex key. Don't do this quest until that is the case.
  2. SC chooses the unisex definition that means "all (non-)genders can use it" and creates the quest like proposed in the original issue

Of course, theoretically, there is a third option, but I hope nobody will argue for that:

  1. For SC there is only male and female
mnalis commented 1 year ago

On the contrary, if there is no sign about gender on the door, I'd consider it a unisex hairdresser where every person is welcome.

That assumption seem culturally dependent to me (and incorrect in Croatia, see below).

There are basically 4 categories in Croatia (ignoring for the moment rampant confusion about sex-vs-gender e.g. female-vs-woman), and them being called the same at least for the last hundred years, so it is likely they haven't caught up with non-binary distinctions:


So, I'd say in Croatia signage is probably mostly about the services available, and not about entrance restrictions / segregation based on sex (or even gender). Similar to e.g. the Kosher restaurant -- you can enter and eat there even if you're not a Jew, but do not expect to be able to order your favorite pork ribs.

In fact (AFAIK) in Croatia if you are registered for selling services to the public (i.e. you are not registered as private club with membership, where you can make up mostly any rules), and you are not covered by certain exceptions (mostly cases where genitalia or breasts or areas very close to it may be exposed - like toilets, saunas, massage parlors, gym communal showers / dressing rooms, doctors etc) you are not legally allowed to refuse service dependent on protected discrimination criteria (e.g. you may not refuse service because someone is black, or woman, or transgender, or of islamic religion, or minority, or living with partner outside of church marriage etc.). You may still discriminate on non-protected differences (e.g. "suit&tie only", "no swimsuits" etc.)

rhhsm commented 1 year ago

It seems we need to look strictly at what is indicated on the shop window and tag accordingly, and not take into account how welcome various genders are in the shop because there could be endless variations. I don't think a surveyor should investigate whether a woman that feels male and wants a male haircut might be welcome at a hairdresser that has "Men's hairdresser" written on the window. I think the question should be "Which sexes are shown on the sign of this hairdresser"? and the answer options should be "Women", "Men" and "No sign". Unfortunately there is no established tag for the third option.

westnordost commented 1 year ago

Yes. male and female on hairdressers is about hairstyles / barber services, that's clear.

Anyway, seems a useful thing to ask. I'd consider whether barber shops (i.e. "for men") should get tagged with just male=yes instead of also with female=no etc. because that's what usually on the sign. The sign will never say "not for women" but "for men".

Discostu36 commented 1 year ago

So the question would be more like "What are the signed customers of this hairdresser"? But this would still leave the question of what to tag if there is none.

"Men" --> male=yes "Women" --> female=yes "Men and women" --> male=yes and female=yes "Not signed" --> unixex=yes? gender:signed=no?

westnordost commented 1 year ago

Hm, I guess both male:signed=no and female:signed=no

Discostu36 commented 1 year ago

Yeah, maybe.

mnalis commented 1 year ago

It seems to me mostly defined then. Only question that remains is:

As unisex=* wiki says:

In case of conflict with other gender-based tags (e.g. female=*), resolve in favour of the more specific tag.

(which the user on the ground definitely knows the best what is the current situation).


Whatever the answer, it seems to be relatively easy quest to make. Are there any takers interested in trying to implement this quest?

Discostu36 commented 1 year ago

should the quest permanently ignore any hairdressers which have unisex=* tag set, or

I think it should ignore items with unisex=yes and ask for items with unisex=no. It should not delete unisex tags.

mnalis commented 1 year ago

As nobody else volunteered, I'll implement this quest.

I'd still like @westnordost opinion on this choice: https://github.com/streetcomplete/StreetComplete/issues/4833#issuecomment-1464557177 (I myself and the wiki find it preferable to make situation unambiguous when we have the chance with mapper on the ground, rather then to simply "sweep the problem under the rug" - but not everybody seems to agree).

westnordost commented 1 year ago

I agree with your statement. What better time to make something unambiguous than when someone is actually on-site. However, no point in fighting against windmills: If iD pushes a different tagging, it makes little sense to push the other way.