For bowling alleys, no guidance is given though I did start a talk topic about this a while back (with no responses).
I think it would be useful for us to agree on a consistent approach here.
Should lanes=* only be used in conjunction with highway=*? If so:
Why? Surely data consumers aren’t expecting lanes=* as a stand-alone tag, so it’s straightforward enough to understand the context based on the primary tag. Why should usage be exclusive to highways? We don’t restrict surface=* just to highways for example.
How should “lanes” for other features be mapped? Does it make sense to keep creating new keys for each feature (e.g. swimming_lanes=*, bowling_lanes=* etc.)?
Perhaps using some namespace tagging? E.g., swimming_pool:lanes=*, bowling_alleys:lanes=* (or even highway:lanes=*).
Or in other words, 7.4% of leisure tracks have a lanes tag.
IMHO these numbers would justify adjusting the current lanes description to mention there is also significant use in combination with running tracks.
Bwilliant idea, let me see how Shift P works on this .
Wonder how a sports minded renderer would show a 6 lane running track when mapped as area. Seen a french version which had all the different pitches right.
Edit: And the results are in, working from inside out, ever larger perfect replicas of the previous copied ring. 100% parallel. Tagged as divider=solid_line
I and another user modified the page a couple years ago to acknowledge non-highway usage, for consistency with other pages that had mentioned these possibilities as far back as 2011, but this page is still confusing overall because it’s focused on roadway lanes. The definition still says “lanes … on a highway” and excludes non-motorized lanes. It may be obvious to some of us that this language only excludes cycle lanes on highways, but it also technically excludes all the lanes of a velodrome track (thus lanes=0).
The capacity of a bowling alley, like that of any indoor venue, would normally be understood as the number of people who are allowed to fit inside the venue at the same time. The number of lanes corresponds to the number of games that can be played at the same time.
Automatically removed quote of whole previous post.
Quote from Minh Nguyen: “The capacity of a bowling alley, like that of any indoor venue, would normally be understood as the number of people who are allowed to fit inside the venue at the same time. The number of lanes corresponds to the number of games that can be played at the same time.”
I disagree with the argument because that would be true if a two lane road can only be used by two cars at the same time. But it may indeed be confusing what capacity means.
In fact, when someone refers to “an eight-lane bowling alley”, they mean the floor is divided into eight linear tracks with eight pin decks and up to eight simultaneously rolling bowling balls. They don’t mean that the bowlers have to play in solitude without any spectators.
I intentionally wrote “number of lanes” rather than “the lanes=* tag” because I don’t have an opinion on whether the three leisure=bowling_alleys tagged with lanes=* are correctly or incorrectly tagged. But there should be a key for this information, just as there’s an (ungrammatically named) screen=* key for the number of screens in a cinema.
I’m amused that anyone is concerned about a building=entertainmentleisure=bowling_alleysport=10pin getting misinterpreted as a road just because it has a lanes=* tag on it. That simply isn’t how renderers or routers work. Granted, bowling:lanes=* would account for the possibility of a new “extreme bowling” sport in which you use an active two-lane roadway as a single bowling lane, tailoring your hook to dodge oncoming traffic. (I would settle for a gutter ball.)
Alas, even bowling:lanes=* was deemed too risky in this case. There are a dozen bowling alleys with “lanes” in the description, most of them the work of SEO specialists. But it isn’t very nice to take already structured data and turn it into unstructured data just because the key isn’t widely used yet…
A fundamental issue for lanes= on them is using areas instead of lines. This makes the directionality meaningless, and has to be derived implicitly.
The bad thing about leisure=track + area=yes is it doesn’t show the section of 100m start lines explicitly, which you haven’t drawn here either. So I personally believe leisure=track lines should still be drawn inside the area with a tail to the 100m start lines. The area should have been eg area:leisure=track similar to area:highway= for compliance of typology for lanes= and possibly other linear attributes.
It may not seem significant for running. But in horse-racing, there are much more variations on the course. Plus, some may want to add the slopes and corner or curve details. incline:across= could be used for bikes and =raceway (which already has area:highway=raceway mentioned) superelevation. There is also type=circuit to define the racing routes.
On a side note, number of lanes would be applicable to shooting, archery, and golf driving range too. Anything else?
OT\ On the globe there’s only 25 instances of the area:leisure and to my surprise it did render on Carto standard so wonder what their problem is with some other area:* variations. /OT
Since what I mapped is a inner/outer ring of a type=MP, no area=yes to be found. Either is cool, more ways in OSM than ways to Rome.
BTW, I just tried out the shift P technique to discover how accurate it would be… very, the more nodes in the bends the smoother the pic becomes. After, the edit went to the bin. Those who want to go overboard in mapping these details incl 100 meter start/finish can have a go.
Mapped a few driving ranges, but I’ve never seen them in real live each mat being numbered nor lanes being painted on the grass. In days of shanking the balls, i’d manage to hit all ‘lanes’ in one stroke ;o). Would use capacity=* tag on this function for the number of spots from which to ‘drive’, and some have multiple levels at that.