Relation:golf
 type = golf
|
 |
| Description |
|---|
| A type of relation used for golf specific mapping. |
| Used on these elements |
    |
| Requires |
|
| Useful combination |
|
For courses:
For tee marker relations:
|
| Status: proposed |
| Tools for this tag |
A relation for multiple golf related elements as members. Often that is a course consisting of golf=hole in sequence. This can be especially useful to distinguishing multiple courses at the same facility/club.
Can also be used to better tie golf=tee together and into a relation to better represent per tee marker data. This data can be used to route from a previous green as a course guide and to discern what tees belong to a specific course by putting the course relation as a member to the tee marker relation.
How to map
Courses:
Courses are mapped in relations 
of type type=golf. The relation should contain golf:course:name=* tag to be considered a course.
This course relation can then mapped with the following tags:
golf:par=*golf:course=*fee=*operator=*start_date=*architect=*golf:loop=*
Other Key:golf elements can also be added as members to relate them to a specific course.
Tee Markers:
Put all of the golf=tee as members to a relation of type=golf. If a golf=tee areas consists of multiple tee colors/numbers, just include it into multiple relations.
You can then attach per tee information to this tee marker relation as:
tee=*golf:course_rating:male=*golf:course_rating:female=*golf:slope_rating:male=*golf:slope_rating:female=*distance=*golf:par=*- if the course is different between any chosen tees.
The relation should contain a tee=* tag to be considered a Tee marker relation.
You should also put this relation as a member to the course relation to tie these tees to a specific course.
In regards to using a different unit than meters for distance=* tag, which is standard in OSM, specify it with units as stated in Map features/Units#Explicit specifications. For example
distance=40 yd
Sub-namespaced per-hole values per tee color/number:
On golf=hole ways: One can map hole specific dist:<tee>=*, par:<tee>=* and handicap:<tee>=*, where <tee> is the tee=* value of a tee marker relation on the same course. This information can usually be found on signage close to the tee area.
This is a compromise we do becuase it is hole specific, the sub-key is also not a wildcard persay - becuse :<tee> is any valid tee color/number already defined in the tee marker relations in the tee=*. Note that golf:par=* is for the entire course and should not be used on individual holes.
Distances:
If no unit is given explicitly, the value is assumed to be in meters. If another unit is given, it should be separated from the number by a space. Common distances in golf is for exampledistance=375 yd. Any decimal should be specified using a dot (.) as the decimal separator. Abbreviations for other units are described on the units page.
Role
Elements will be added with an empty role in order of the holes, the order of the holes can also be verified by the consumer of the data of the ref=* on the golf=hole way 
Examples:
Courses:
- Björketorpsbanan, Emmaboda Golfklubb - One course.
- Nya Banan, Kalmar Golfklubb & Gamla Banan, Kalmar Golfklubb- Two courses on one golf course facility,
Tee markers:
Why
If one tags multiple golf:course=*, golf:course:name=* and golf:par=* etc on one leisure=golf_course it is imposible for data consumers to assign what golf=hole with the ref=* goes to what course. Even if a facility only have one course, it is hard for a data consumer and a computational expensive spatial query "what course does this hole lie inside of?" is needed instead of having the data directly tied to a golf=hole.
Using type=golf also have the benefit in that you do not need to duplicate data on alla golf=hole - making updates easier and you could also include other features as members, for example golf=out_of_bounds for the course relation.
An added argument for using a relation for tee markers is that we can represent that one golf=tee area can contain multiple tee=*, making it easier to present that one area contain multiple tee markers and that one course have different attributes depending on what tee color/number you chose to play the course from.
Alternative tagging
One could also put all the course-specific tags on golf=hole, but then you lose the ability to describe the course itself with additional tags. With type=golf you have a relation object to put tags on to describe the course itself.
Courses which consists of different "loops" for each day
See golf:loop=*
See also
- Proposal page for updated golf tagging schema: Proposal:Relation:golf
leisure=golf_course- The facility containing the golf course.- Tag:leisure=golf_course#Courses in a facility
- Previous development on a now deprecated tag Talk:Tag:route=golf#Initial creation of this tag