User talk:HuggeK

Dist key under golf=hole

I think deleting dist and dist:* from golf=hole shouldn't have been done without a broader discussion. Can you add them back for now and let's talk about it further on Slack (OSM US) in the #golf channel?

B-jazz (talk) 21:09, 13 July 2026 (UTC)

We can discuss more, I just think having the distance on the hole itself to not actually describing something that exist or is usefull - the distance is depending on what tee markers you chose... On signage. SO having the distance on the hole does not tell you anything? And also: looking at the Key:distance Keyt it should not be used on ways: a way already have a length I would guess is why it is discouraged to use that.

We(some guys in the fairwaymapper discord) are in the process of proposing new better golf tagging schema to cover the tee markers too and a course relation to actually represent courses as OSM enitities(help and shime in on it welcome!), will post the proposal and examples in the couple of days on a talk page (leaning towards the Tag:golf=tee and Key:tee pages, and cross post it to slack(you lose some momentum for new users who wants to jump into the discussion if they need to be allowed into the slack channel manually by an admin) HuggeK (talk) 05:34, 14 July 2026 (UTC)

It's a fair discussion to have. I'm willing to open to a discussion about removing it. I'm just opposed to removing the tag description by fiat.

As for the momentum loss, Slack history is (semi-)permanent. Any new user joining will be able to see the full history of the conversation from before they joined. So that shouldn't be a concern. The OSM US Slack server has a very large audience so we would be able to get a better discussion going than a focused discord server like the FWM one.

A quick note before the main discussion: I think the `golf=hole` way is the best place to put distances (like you said, ones that are official from the course on a plaque or score card). So things like `distance:red=145` is the right way. And in order for that to happen, you have to allow the `distance` parent tag and maybe add some commentary to the wiki about how it is discouraged and to put more detail in the child subkeys. That's my gut feel of the issue.

B-jazz (talk) 16:49, 14 July 2026 (UTC)

Ok, I´m not proposing to continue the discussion on the FM discord server, I´m proposing to propose to pitch it(see, golf lingo) on the relevant tags talk page to record it for the future, just becuase it is about a tag on the wiki and it will not be lost to the scrolling of a chat channels in the same way. It is not preferable to express multiple values into one tag. So using a :suffix on the key which can be any value under the sun is hard for a consumer to actually consume. Better to actually use key=value flat on an osm object. You query the features when to process it byt the key - and if you do not know beforehand what tees exist you need to take all data which is ineficient/hard. The golf=hole is not the right place for it, it does describe something which is dependent on what tees you chose. So how it was written as before does not add any value. HuggeK (talk) 19:00, 14 July 2026 (UTC)