Disc Golf Tagging in OpenStreetMap

The scheme, in short

One course = one OSM object. Interior features use a dedicated namespace. This mirrors how golf is tagged (leisure=golf_course + golf=*) — the same model, applied to disc golf.

Don't: leisure=pitch or leisure=track for the course; sport=disc_golf on tees, baskets or holes (the course node already states the sport); golf=* keys; name=* on individual holes; an invented leisure=park boundary drawn just to carry the course tags.

Multi-layout courses

Same holes, different tee positions or hole counts (short 9 vs. full 18, seasonal layouts): use one type=disc_golf_layout relation per configuration. Hole number comes from the relation member's position — the first role=hole way is hole 1 — never from ref on the way itself, since the same way can be a different hole number in a different layout. The course node is a mandatory role=course member.

DiscGolfPark Běchovice (Prague) has three type=disc_golf_layout relations sharing one course node — the reference implementation. See it on the live map or its course page.

The scheme has also been adopted independently: Thornbury Park Disc Golf (Pennsylvania, US) uses the same relation structure without any involvement from us.

The numbers

Totals (taginfo, 2026-07-02): 2,674 objects tagged leisure=disc_golf_course (1,648 nodes / 849 ways / 177 relations); 3,773 objects tagged sport=disc_golf. About 18.5% of courses lack the sport tag entirely — a gap that's growing since the iD editor stopped auto-adding it in July 2025 (see the renderer matrix below). Beyond the course feature itself, roughly 31,106 disc_golf=tee/basket/hole micro-features are mapped (10,181 tees / 10,474 baskets / 10,451 holes).

Where sport=disc_golf actually points

A full Overpass dump of every sport=disc_golf object shows only 57.8% of it is the course feature itself. This is why a renderer keying on the sport tag alone shows noise — see the renderer matrix below.

Geographic distribution

leisure=disc_golf_course by country (Overpass, 2026-07-02) — a curated selection of major markets, not exhaustive:

The top 5 countries hold roughly 79% of all mapped courses.

Mistagging patterns found

Renderer & editor support

Verified examples

Well-tagged courses

• Tantolunden DiscGolfPark (Sweden) — Textbook tagging — leisure and sport tags, fee/access, opening hours, website, and 7/8/7 tees, baskets and holes mapped. Map · Course page · OSM
• Ummeljoen Frisbeegolfrata (Finland) — The richest metadata in the dataset — full address, operator, start date, website, and complete 9/9/9 infrastructure. Map · Course page · OSM
• Valtu discgolfipark (Estonia) — Complete from its very first upload — every core tag present at version 1, with 20 tees, 16 baskets and 18 holes. Map · Course page · OSM
• DiscGolfPark Chodov (Czechia) — Area mapping done right — full tagging on a way, with 9/9/9 tees, baskets and holes, proving the scheme works on areas too. Map · Course page · OSM

Common mistakes, in the wild

• "Håll 1", Sweden — Tagged leisure=disc_golf_course, but the name is a hole label — this is really a basket or hole, not a separate course. OSM
• Fairway "3", Plzeň-Homolka, Czechia — A fairway drawn as leisure=pitch + sport=disc_golf and named just "3" — renders as a spurious extra course in sport-tag-only apps. OSM
• Praha-Čakovice info board, Czechia — Full course tags placed on a tourism=information board node instead of a dedicated course point — one course, mapped across three separate objects. OSM
• DiscGolfPark Běchovice park boundary, Czechia — An invented leisure=park boundary (farmland until 2015) carrying the course's sport tag and name — not a verifiable park, and the reason some apps show this course via the park instead of the course node. OSM

Sources & method

Statistics on this page come from three sources, each cross-checked: the taginfo API for totals, full Overpass API dumps for carrier and geographic breakdowns, and individual OSM API lookups to verify every example cited by hand. All figures are a point-in-time snapshot from 2026-07-02.

• OSM wiki: Disc golf
• Tag:leisure=disc_golf_course
• Proposal:Disc_golf_course_2025 (current draft)
• Proposal:Disc_golf_course (2011, never voted)
• Proposal:Disc_golf (2009, sport=disc_golf, archived)
• RFC discussion thread

Disc golf tagging FAQ

Which tags does a disc golf course need?

leisure=disc_golf_course plus sport=disc_golf and a name, on one node placed at the course entrance or first tee. That alone is enough to appear on every OSM-based disc golf map.

Should a course be a node or an area?

A node is preferred — it doubles as the point a router navigates to. An area is fine where the boundary is verifiable on the ground, but never tag both a node and an area for the same course.

Why doesn't my course show up in OsmAnd?

OsmAnd currently renders disc golf only via the sport=disc_golf tag, not leisure=disc_golf_course alone. Add sport=disc_golf to the course node — see the tagging statistics on this page for how common this gap is.

How do I map a course with multiple layouts (tee/basket variants)?

Use one type=disc_golf_layout relation per playable configuration, with the hole ways in playing order and the course node as a role=course member. See the multi-layout section on this page.