Tag:route=golf
| Description |
|---|
| A golf course. |
| Group: routes |
| Used on these elements |
| Requires |
|
| Useful combination |
|
| Status: proposed |
| Tools for this tag |
A route of 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.
How to map
Courses are mapped in relations
of type type=route and
Other Key:golf elements can also be added to relate it to a specific course, for example golf=tee´s and paths to take in between holes.
Roles
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:
- Björketorpsbanan, Emmaboda Golfklubb - One course.
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 route=golf also have the benefit in that you do not need to duplicate data on alla golf=hole - making updates eaiser and you could also include other features as members, such as golf=tee and golf=out_of_bounds.
Alternative tagging
One could also put all the course-specific tags on golf=hole, but then use lose the ability to describe the course itself with additional tags just becuase with using route=golf you have a relation object to put tags on.
Courses which consists of different "loops" for each day
See golf:loop=*
See also
leisure=golf_course- The facility containing the golf course.- Tag:leisure=golf_course#Courses in a facility
- Why this tag was created, discussed on the talk pages of multiple golf keys and tags: Talk:Tag:route=golf#Initial creation of this tag
