Proposal talk:Leisure=racetrack

[was:Duplicates] Why a different value?

Please see documented and already in use tag Tag:highway=raceway --Althio (talk) 12:37, 17 October 2016 (UTC)

As you can see I mentioned highway=raceway many times and the aim of the proposal is not to replace it, indeed it is "part of the schema". As an easy example: an highway=raceway is inside a leisure=racetrack area like a leisure=pitch is inside a leisure=sports_centre area --sorcrosc 18:10, 17 October 2016 (UTC)

My apologies! I was on mobile phone and missed a few sections or really did not read carefully. --Althio (talk) 07:51, 18 October 2016 (UTC)

What confuses me then: why do you use a different word for value? Isn't it more simple to propose a highway=raceway is inside a leisure=raceway (instead of racetrack)? --Althio (talk) 07:51, 18 October 2016 (UTC)

According to en.wikipedia seems to me "racetrack" is a common term to describe this features and "raceway" more suitable for the way itself, anyway proposals for the term to use are welcome --sorcrosc 23:52, 18 October 2016 (UTC)

sports_centre

As you mean the whole area including shops etc., this is simply a leisure=sports_centre. Even if "there is no mention on possible usage for places where motorized sports take place", motor sport is generally considered a sport. That makes a motor sport facility a sports centre. When you find the sport=* tag unsuitable to distinguish sports centres, you'll have to get rid of the leisure=sports_centre tag altogether and invent a new leisure=* tag for every single sport where sports centres exist. --Fkv (talk) 07:06, 7 November 2016 (UTC)

Of course all facilities where sport take place are sport centers but it is really useful to have a tag leisure=sports_centre with so wide meaning? Keep leisure=stadium, it is clear what we can expect from it but leisure=sports_centre is pretty useless if it can be either a tennis center or a motocross site. Really we have to get rid of it --sorcrosc 19:07, 07 November 2016 (UTC)

I consider it not a bug, but a feature, that undocumented or multiple values can be used for the sport=* key. Imagine a racetrack that is used for ice stock in winter. However, either sport=motor or sport=motocross or sport=equestrian should be fine for most racetracks. --Fkv (talk) 07:06, 7 November 2016 (UTC)

For most but not all (drag_racing, folkrace). However I agree that undocumented or multiple values have to be used for the sport=* key --sorcrosc 19:07, 07 November 2016 (UTC)

If Riding is correct sport=equestrian is rather not fine for racetracks in the sense of this proposal (whole facilities especially for races). Did you mean sport=horse_racing instead? --Hufkratzer (talk) 15:15, 8 November 2016 (UTC)

I was not aware that this tag exists. I am not a horse expert, and the horse-related racetrack websites I incidentally found all had "equestrian" in their descriptions. Anyway, that does not really matter in our choice between leisure=racetrack/sports_centre. --Fkv (talk) 17:15, 8 November 2016 (UTC)

Added sport=equestrian in the non-applicable sports reference list. As for sport=horse_racing I have non experience with this kind of races. I guess it's better to keep it out unless someone has good reasons to include it. --sorcrosc 21:03, 08 November 2016 (UTC)

Why not more detailed tagging?

I recently mapped a racetrack and I found it a bit confusing as how to map the enclosing area. The centerline track itself, and the start/goal posisions seemed to be the only documented tagging. Relevant data such as racetrack area, run-off areas, service areas, kerbs (different from regular barrier=kerb), pit lane, and the various types of barriers seemed to completely lack raceway related/specific tagging. I ended up tagging a little bit for the renderer (sorry about that) and a little bit as an example for precisely this discussion. As an example there was a circular enclosure for drifting which I tagged as: "access=no, area=yes, highway=service, raceway=track, sport=drifting". I would love for there to be a complete set of official tags for all these details so we can avoid tagging for renderer (using highway=service) in order to show a track as it deserves to be shown. Therefor i suggest something like sports_centre=racetrack + sport for the enclosing area. highway=raceway + raceway=* for the different parts of the track. For barriers I'm missing something like "raceway_kerb" and "tire_wall". Gravel traps are also hard to map since things like shingle and sand are of wrong, but there is no better alternatives if you want it rendered. My examples are: https://www.openstreetmap.org/#map=16/59.3669/11.2660 and https://www.openstreetmap.org/#map=18/43.43083/-5.83280. I'm not usually involved in these discussions so sry if I'm a bit disorganized and not-well-read :). --Wulfmorn (talk) 11:18, 1 July 2018 (UTC)

Proceeding to vote

Are you planning to start a vote? See Proposal_process#Voting for help how to do that. 09:22, 12 January 2021 (UTC)

Although I don't find the usual way of mapping with leisure=sports_centre satisfactory, I don't think there is a future for this tag. I will put it in status abandoned. --sorcrosc (talk) 19:50, 12 January 2021 (UTC)