Key:male

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Key:male
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština dansk Deutsch eesti English español Esperanto estremeñu euskara français Frysk Gaeilge Gàidhlig galego Hausa hrvatski Igbo interlingua Interlingue isiXhosa isiZulu íslenska italiano Kiswahili Kreyòl ayisyen kréyòl gwadloupéyen kurdî latviešu Lëtzebuergesch lietuvių magyar Malagasy Malti Nederlands Nedersaksies norsk norsk nynorsk occitan Oromoo oʻzbekcha/ўзбекча Plattdüütsch polski português română shqip slovenčina slovenščina Soomaaliga suomi svenska Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް
Public-images-osm logo.svg male
Male-Symbol-Silhouette.png
Description
Access for persons of the male sex or gender only Edit
Group: Restrictions
Used on these elements
may be used on nodesshould not be used on waysmay be used on areasshould not be used on relations
Useful combination
See also
Wikidata
Status: in use

Description

Denotes that access is restricted to persons of the male sex or gender. This is an access tag following the same rules as those described in access=*, though the presence of this tag with a yes value necessarily implies a no for all other gender-based access tags.

Usage

Use this tag in combination with other tags, most frequently in combination with amenity=toilets.

amenity=toilets
male=yes

It's probably best to express this type of access as male=yes and let the implications take care of other sexes/genders since the number is not guaranteed to be exactly two across all cultures. It's also faster to tag in this way.

Implications

A value other than no is interpreted as yes, and implies no for all other unspecified gender-based access tags, but this can be overridden by adding more access role tags. In case of conflict, resolve in favour of more access.

Possible tagging mistakes

If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
  • man=yes ‒ But this could be a misstaged man_made, too
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
  • man=no ‒ But this could be a misstaged man_made, too
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
  • man=only ‒ But this could be a misstaged man_made, too
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!