Proposal:Net
| The Feature Page for this approved proposal is located at Key:pitch:net |
| net | |
|---|---|
| Proposal status: | Approved (active) |
| Proposed by: | Push-f |
| Tagging: | pitch:net=* |
| Applies to: | node, area ( /  )
|
| Definition: | Indicates whether a net is available at a sports pitch. |
| Draft started: | 2022-05-27 |
| RFC start: | 2022-05-28 |
| Vote start: | 2022-06-18 |
| Vote end: | 2022-07-02 |
Proposal
Several sports require a net to be played (e.g. volleyball, beach volleyball, tennis, table tennis, etc.). Some pitches (public pitches in particular) however do not have a net, potentially because it has been damaged or stolen at some point in time. The presence of a net at a sports pitch is currently tagged in one of two ways:
- the pitch is tagged with net=yes, or
- the net is mapped as a separate way (with barrier=net) on top of the pitch area
For nets essential to the sport, let us encourage the former (tagging the pitch with net=yes), as opposed to mapping the net with a separate barrier=net.
To establish a dedicated namespace for other pitch features that may be introduced in the future, we deprecate net=* in favor of pitch:net=*.
Rationale
There are three distinct advantages to tagging the availability of the net directly on the pitch node/area:
- the unavailability of a net can be explicitly tagged with pitch:net=no, which in combination with access=yes indicates that this is a public pitch where you have to bring your own net
- it makes querying pitches based on net availability easier (e.g. show me nearby pitches with/without a net)
- a boolean tag is easier to survey (e.g. a StreetComplete question "Is there a net available at this pitch?" could be introduced)
Existing pitch-specific tags tend to be namespaced under the sport name e.g.
- for leisure=pitch + sport=shooting there is shooting=*
- for leisure=pitch + sport=baseball there is baseball=*
Since the net key however applies to several sports it makes sense to keep it in a namespace that can be applied to pitches of varying sports.
While we could simply use the main namespace that is bound to result in namespace conflicts in the future once we formalize further pitch-specific but cross-sport tags like playability=*.
We therefore introduce the pitch: key namespace to facilitate the introduction of further pitch-specific tags without risking namespace collisions.
Tagging
pitch:net is intended to be added to pitches that are tagged with leisure=pitch and sport=*, where the sport requires a net (e.g. volleyball, beachvolleyball, tennis, table_tennis or badminton).
- pitch:net=yes means there is a net available at the sports pitch
- pitch:net=no means there is no net available at the sports pitch
pitch:net is particularly of interest for public pitches (access=yes). For pitches only accessible to customers or club members (access=customers / access=private) nets are generally provided, meaning pitch:net=yes could generally be assumed / inferred.
Examples
- a public pitch where you have to bring your own net would be tagged with leisure=pitch, access=yes, net=no
- overpass for net=*, e.g. 414161206
414161206, 495553375 495553375 - overpass for barrier=net (not all are for sports pitches and sometimes it's also used for non-essential nets on sports pitches)
Features/Pages affected
- pitch:net=*
- net=*
- sport=volleyball
- sport=beachvolleyball
- sport=tennis
- sport=table_tennis
- sport=badminton
- sport=pickleball
- other sports with a net?
External discussions
Comments
Please comment on the discussion page.
Voting
Voting on this proposal has been closed.
It was approved with 17 votes for, 1 vote against and 0 abstentions.
I approve this proposal. As proposing contributor. --Push-f (talk) 08:06, 18 June 2022 (UTC)- I approve this proposal.—Dieterdreist (talk) 09:31, 18 June 2022 (UTC)
- I approve this proposal. --Tordanik 13:17, 18 June 2022 (UTC)
- I approve this proposal. The proposed prefixed key helps a lot with possible future additions of other equipment installed on pitches for various sports. --Mueschel (talk) 13:58, 18 June 2022 (UTC)
- I approve this proposal. --PeterPan99 (talk) 08:04, 19 June 2022 (UTC)
- I approve this proposal. Very niche, I love it. Feel free to come over the the MapComplete repository on github to add this tag to the sport-pitches layers. Pietervdvn (talk) 10:52, 19 June 2022 (UTC)
- I approve this proposal. Might want to include basketball in this proposal. Although not technically required (and I've seen a lot of basketball courts without nets), it's more fun when nets are present. --Dr Centerline (talk) 19:18, 19 June 2022 (UTC)
- I think hoop nets are different enough from nets that divide a pitch to deserve their own tag. tag:sport=basketball currently suggests hoops:nets. I don't see any advantage to extending pitch:net=* to also apply to hoop nets since the resulting tagging would only be less clear/descriptive than hoops:nets. Instead I think it would make sense to formalize all the basketball-specific tags in a separate proposal. --Push-f (talk) 20:07, 19 June 2022 (UTC)
- I approve this proposal. A problem is the mapper sees no net and maps for no net when the net is in fact available but stored locally. This needs to be made clear in the instructions - "pitch:net=yes" means "available but not necessarily installed as it maybe stored locally and ready for use". With that caveat my vote is yes, without it I would vote no. --Warin61 (talk) 04:06, 21 June 2022 (UTC)
- I approve this proposal. --Shaun das Schaf (talk) 08:39, 24 June 2022 (UTC)
- I approve this proposal. --EneaSuper (talk) 12:02, 26 June 2022 (UTC)
- I approve this proposal. --Reino Baptista (talk) 17:40, 26 June 2022 (UTC)
- I approve this proposal. So we will have to replace all net=yes/no by pitch:net=yes/no? --Binnette (talk) 12:43, 27 June 2022 (UTC)
- I approve this proposal.
Although there maybe some better way to tag those things, I can't found it, soI agree with this tag. And I think such tag as "@Push-f:" said will be better. --快乐的老鼠宝宝 (talk) 15:52, 27 June 2022 (UTC) - I approve this proposal. --Władysław Komorek (talk) 07:31, 28 June 2022 (UTC)
- I approve this proposal. Even if the proposal relates to a niche area, it brings more order and systematics into the database. I fully support this. However, I would strongly avoid a "mass edit", because 1) there are only very few objects with the old tagging and 2) in many cases they may have been tagged in this way a long time ago, so an individual check is necessary to see if the data is still correct. This should rather be done by an editor like StreetComplete. If you like, you (or someone else) could propose a StreetComplete quest afterwards that asks for this tagging for suitable sports areas. -- Supaplex030 (talk) 08:29, 28 June 2022 (UTC)
I oppose this proposal. I see nothing wrong with the net=no tag. Namespace is not needed here. maro21 21:56, 28 June 2022 (UTC)
- As Mueschel explained on the talk page there is a large variety of pitch equipment (e.g. nets, goals, loops, gates, (chess) pieces), in the future we might also want to tag the presence of players benches or a scoreboard. Having a common namespace for all of this pitch tagging is just way more organized and let's us avoid creating more homonymous keys. --Push-f (talk) 08:54, 29 June 2022 (UTC)
- I approve this proposal. Public table tennis here have a steel sheet with holes. Will this be a pitch:net=yes ? Regardless, like it. Great potential for plenty StreetComplete contributions. --Hungerburg (talk) 22:09, 28 June 2022 (UTC)
- Yes this would be pitch:net=yes. The material of the net can be specified with a separate tag. sport=table_tennis currently suggests net:material=metal, so with the additional pitch: namespace this would become pitch:net:material=metal. --Push-f (talk) 08:54, 29 June 2022 (UTC)