Tag:route=golf

From OpenStreetMap Wiki
Jump to navigation Jump to search
route = golf
Description
A golf course.
Group: routes
Used on these elements
should not be used on nodesshould not be used on waysshould not be used on areasshould not be used on relations (except multipolygon relations)
Requires
Status: deprecated

exclamation mark icon

This feature has been labeled as deprecated. The recommended replacement is: Relation:golf (type=golf) with golf:course:name=*.
The reason is documented in Deprecated features. You are still free to continue to use or interpret this tag as you see fit since OpenStreetMap does not have “banned features”.
Under no circumstances should you (semi-)automatically change “deprecated” tags to something else in the database on a large scale without conforming to the automated edits code of conduct. Any such change will be reverted.

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 relation 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 way

Examples:

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 golf=out_of_bounds.

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 route=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