Proposal talk:Pitch markings

Proposal Feb 2022

Background Information

History of Pitches

1: As of Feb 2022 from TagInfo there are 1.9 Million Pitches: TagInfo Number of Pitches Of these 1.7 million have assosiated sport tags TagInfo Pitch with sport tag

2: Soccer Pitches are not a standard size

3: Pitches can have multiple uses and markings.

4: Pitches can be different depending on the season

5: Soccer Pitches are rendered on https://www.openstreetmap.fr/ see Institut National du Sport, de l'Expertise et de la Performance outside the center of Paris

6: Pitches are not data dence as compared to houses and the city centres, this is because they are fairly large. A large proportion of lines are straight and only need two nodes

7: Pitch Lines can have different names depending on the sport and location on the pitch

8: Markings on a pitch can help identify the sites function for example Wimbledon and Tennis, Murryfield and Rugby, Real Madrid CF and Soccer. We akreadt identify different landuses such as commercial, industrial , farmyard. Pitches may have an associated sport=* tag but there is no standardised way to show it and icons are a messy solution

Previous Proposal

Ideas for future improvements

In response to the RFC, these are some open issues I've encountered while implementing pitch marking rendering:

• overlapping lines present in sport=multi pitches
• marking colors.

However, this is not a suggestion to add these right away. I think this is a solid proposal as is and it would probably be best to get it accepted first – no need to get bogged down with too much additional topics at the moment. Future extensions are always possible, after all. --Tordanik 19:27, 26 July 2018 (UTC)

More values

I'd suggest four values for this, rather than a simple yes/no:

• pitch_markings=permanent: for permanent markings such as might be found on an artificial-turf field.
• pitch_markings=temporary: for markings that are refreshed on an as-needed basis. Markings might not be present on the off-season.
• pitch_markings=yes: for when the permanence of markings isn't known.
• pitch_markings=no: for fields without markings, such as a soccer field consisting of just a pair of goals.

--Carnildo (talk) 04:54, 27 July 2018 (UTC)

Tracks

Tracks may also have markings as you can see on the title photo for leisure=track:

-> Perhaps better use a tag name like "sport_markings" and allow to use it also for tracks? sport=* is a required tag too. --Hufkratzer (talk) 11:33, 27 July 2018 (UTC)

Absence of pitch markings

With the recent changes to the proposal, how should I map the fact that a pitch does not have markings at all? --Tordanik 15:55, 13 September 2018 (UTC)

would be intuitive to add lines=no, but apparently the lines=* key is already used in different context, although marked as deprecated there is still some thousand uses. --Dieterdreist (talk) 21:27, 10 March 2021 (UTC)

Updated Proposal

This proposal has been updated due to new information including newer versions of tags and standardisation of pitch tags