Proposal:Golf=out of bounds
Golf=out_of_bounds | |
---|---|
Proposal status: | Proposals without post-vote cleanup |
Proposed by: | HuggeK |
Tagging: | golf=out_of_bounds |
Applies to: | ![]() |
Definition: | Area designated as being outside the boundaries of a golf hole. Out-of-bounds areas are usually indicated by white posts. |
Statistics: |
|
Rendered as: | White dashed line. |
Draft started: | 2024-07-09 |
RFC start: | 2025-01-26 |
Vote start: | 2025-02-09 00:00:00 (UTC) |
Vote end: | 2025-02-22 23:59:59 (UTC) |
Proposal
I propose we properly document the use of golf=out_of_bounds on the wiki. I propose we suggest using it on ways as that is what is marked in the real world with white markings/sticks.
Rationale
Golf app consumers/map makers could use this data to generate detailed course maps. For the users it would be a benfit to know where the out of bounds line is and to avoid it.Wikipedia.
When the orignal golf course proposal was drawn up an discussed ten years ago there was alot of talk of out_of_bounds but it never made its way onto the wiki. Proposal talk:Golf course - OpenStreetMap Wiki.
A line of white poles. These poles could bee white facing you when you are standing on the intended hole to be out of bounds but on the other side they can be other colors such as black. This indicates that the poles are intended for the hole which they are facing/is painted white against. This implies that a way golf=out_of_bounds is intended for a specific hole.
Tagging
Draw a line with the nodes on the poles which shows where an area is out of bounds.
To associate an out of bounds line to a hole, create a ref= tag as in other golf features.
Examples
A line between white out of bounds poles.
Rendering
White dashed line.
Features/Pages affected
External discussions
https://community.openstreetmap.org/t/rfc-feature-proposal-golf-out-of-bounds/124835https://lists.openstreetmap.org/pipermail/tagging/2025-January/068083.html
Comments
Please comment on the discussion page.
Voting
- Log in to the wiki if you are not already logged in.
- Scroll back down and click "Edit source" next to the title "Voting". Copy and paste the appropriate code from this table on its own line at the bottom of the text area:
To get this output | you type | Description |
---|---|---|
{{vote|yes}} --~~~~
|
Feel free to also explain why you support the proposal! | |
{{vote|no}} reason --~~~~
|
Replace reason with your reason(s) for voting no. | |
{{vote|abstain}} comments --~~~~
|
If you don't want to vote yes or no but do have something to say. Replace comments with your comments. |
~~~~
automatically inserts your name and the current date.For more types of votes you can cast, see Template:Vote. See also how vote outcome is processed.
I have comments but abstain from voting on this proposal. I abstain, because not play'ing golf yet --chris66 (talk) 18:33, 9 February 2025 (UTC)
I approve this proposal. seems ok, I don‘t particularly like the specific „golf“ key, but it is established so following this use seems consistent. —Dieterdreist (talk) 08:14, 10 February 2025 (UTC)
I approve this proposal. --Mueschel (talk) 10:12, 10 February 2025 (UTC)
I have comments but abstain from voting on this proposal. I don't play golf but I think this is unnecesary. --Meme (talk) 07:23, 14 February 2025 (UTC)
I oppose this proposal. It seems this is a duplication of barrier=bollard for specific use in golf context, why not establish a subtag or
for out of bounds? barrier=bollard & barrier:colour=white seem to describe this well and is already supported by 3D renderers. At the very least, following this scheme if the consensus is a golf specific tag is needed, it should use the term bollard as we describe what is on the ground, not the rules of golf. A particular golf data consumer can setup a rule that if a
of barrier=bollard is present within leisure=golf_course it can be translated as out of bounds for a particular golf=hole with the same ref=*. --GA Kevin (talk) 15:49, 21 February 2025 (UTC)