Id: Support leisure=pitch on ways

[jomo]

For example, soccer fields without a clear outline can be mapped as ways (a single line from one goal to the other), according to the wiki.

iD doesn't currently support this and warns that "Leisure should be a closed area".

[Adamant36]

For example, single basketball hoops or soccer fields without a clear outline can be mapped as nodes or ways, according to the wiki.

Maybe it can be mapped as nodes according to the wiki, but the wiki also does say a pitch is "an area designed for practicing a particular sport." I'd be interested to know where the line is between mapping a pitch as a node versus just tagging a single basketball hoop as a point with sport=basketball or something. Especially in your example where there is no clear basketball playing area. There doesn't seem to be a tag that I could find for mapping single sports related objects like that. At least not for basketball.

[jomo]

The wiki pages for both leisure and leisure=pitch state that these tags are used on nodes, ways, and areas (but not relations). The photo of the basketball hoop above is taken from the examples section, where it is mapped as a node with leisure=pitch + sport=basketball

[Adamant36]

Yeah, I mean, we already established that. Just repeating what we already know doesn't really answer my question. I thought you might have your own opinion about it outside of what the wiki says.

[jomo]

I's not about mapping the soccer goals and basketball hoops in particular, but more about mapping the actual pitch which doesn't have a clear boundary, which can't be mapped as an area. I do like the way the wiki suggest doing this.

Perhaps iD could show a note that an area should be used, if possible.

[Adamant36]

Perhaps iD could show a note that an area should be used, if possible.

That's my only issue. I'm inclined to think that given the option, people will default to mapping all pitches as nodes just because it takes less time and not confine it specifically to ones with unclear boundaries. If there's a warning or note though, that would help. Although, I've also seen it go the other way where people will map arbitrary boundaries for unclear pitches because the option to map them as nodes isn't available. Which isn't so good either.

[Adamant36]

Btw, I just placed a node in iD Editor and put "pitch" in the search and it worked. So, this might not be a problem for nodes after all. Looks like it just doesn't work for ways. I didn't any warning about it either. You might want to double check it and update the title of the issue. Maybe it was an issue in the last version or something.

[quincylvania]

@jomo Sorry, but iD can't really support any kind of landuse features as lines.

Since OpenStreetMap doesn't have different data types for lines and areas, the tags themselves imply whether a way should be an area. Right now leisure=pitch implies area. If we allow that tag on lines, then _all_ pitches would be treated as lines until someone added area=yes.

Also, I think the existing tagging system for pitches suits all cases. If the direction of play is ambiguous, you can use a point. If the direction is evident, it's okay to estimate the play bounds even if they're not marked.