Gather complex golf courses around the world

[HuggeK]

For example clubs with "loops" and courses with complex geometries.

[101Steeps]

Hilton Park Golf Club in Milngavie, Scotland, has 2 18-hole courses (Hilton Course and Allander Course) sharing the same estate. It has already been mapped for greens and hole lines. If useful, I can complete the mapping with fairways, bunkers, etc? - https://osm.org/go/evXpbsph?layers=VNDG&way=87148149

Gleneagles in Scotland has also been extensively mapped with only some additions needed. Gleneagles has 4 courses: PGA, PGA Juniors, Kings Course and Queens Course. - https://osm.org/go/e6IiTk6J--?layers=VNDG&way=269353306

Auchterarder Golf Club is next to Gleneagles and has the same level of mapping: https://osm.org/go/e6Ii01L7A-?layers=VNDG&way=269353312

[HuggeK]

TODO: include the complex courses gathered here in the CI test fixture, so every pull request is automatically verified against them.

Since #51 (see #50), every PR build runs the full pipeline on a small committed fixture (tests/fixtures/golf-fixture.osm.pbf, currently the Emmaboda GK + Nybro golfklubb areas) and produces a browser-testable demo bundle. Adding a complicated course from this issue is just:

1. Add its bbox as another entry in tests/fixtures/extract-config.json.
2. Re-cut the fixture with the osmium extract/osmium merge commands from Add per-PR demo bundle CI workflow (#50) #51's description (works against any Geofabrik extract covering the course).
3. Commit the updated .pbf — from then on every PR's schema/style changes are exercised against that course too, and reviewers can pan to it in the demo bundle viewer.

Good candidates are exactly what this issue collects: multi-course facilities using route=golf relations, courses with unusual tagging, boundary-hugging features, etc. Keeping the fixture small (a few MB) matters for repo size, so prefer tight bboxes per course.

🤖 Generated with Claude Code