You are not logged in.

Announcement

*** NOTICE: By 30th of September 2022 the forum.openstreetmap.org will be retired, please request a category for your community in the new ones as soon as possible using this process, which will allow you to propose your community moderators. We expect the migration of data will be finished by that date, you can follow its progress here.***

#1 2022-09-08 15:25:20

Cactusbone
Member
Registered: 2013-06-11
Posts: 110

OSM grandstands rendering

One user contacted us about grandstands rendering, because some mappers were using building:part=steps instead (for example https://demo.f4map.com/#lat=51.4139616& … 3&zoom=19)

So right now what we have is (at least in F4 map):

- building=grandstand rendered as a block
- leisure=bleachers, without specific render
- building:part=steps, which accept step:height (defaulted to 0.16m) and step_count (defaulted to height divided by step:height), both from Stairs_modelling


I think using leisure=bleachers along with height and a new tag 'row_count' (better name needed) should be quite easy, but the height for a building=grandstand indicate where the roof is, so some other tags are required, like 'row_count'+'row_height' or 'seated_height'

any ideas / suggestions / feedback ?

Offline

#2 2022-09-09 07:52:22

googlenaut
Member
Registered: 2017-06-24
Posts: 92

Re: OSM grandstands rendering

what I've found is:

building=yes
height=0.001
leisure=stadium
name=Stadion Zagłębia Lubin
sports=soccer

missing:

wikipedia:pl=Stadion Miejski w Lubinie
wikipedia:de=Zagłębie-Lubin-Stadion
wikipedia:en=Stadion Miejski (Lubin)
wikipedia:fr=Stade du Zagłębie Lubin
starting_date=14 March 2009
capacity=16068
owner=Zagłębia Lubin

but I'm fine with the rendering. steps hidden in building:part. no need for uncovered or elevated bleachers here. https://www.openstreetmap.org/#map=17/51.41378/16.19872

Last edited by googlenaut (2022-09-09 08:40:25)

Offline

#3 2022-09-09 10:10:00

Cactusbone
Member
Registered: 2013-06-11
Posts: 110

Re: OSM grandstands rendering

Indicating steps to get "bleachers like" rendering is "tagging for the renderer". these are not actual steps here hmm

Last edited by Cactusbone (2022-09-09 13:16:13)

Offline

#4 2022-09-09 16:42:14

googlenaut
Member
Registered: 2017-06-24
Posts: 92

Re: OSM grandstands rendering

agree. this is 3D-modelling without 3D-primitives. but bleachers won't help here. in 2D-OSM its simply grandstand.

Offline

#5 2022-09-09 23:04:45

Tordanik
Moderator
From: Germany
Registered: 2008-06-17
Posts: 2,834
Website

Re: OSM grandstands rendering

I agree that treating these as steps would be mapping for the renderer, and I also agree in wanting a solution that allows 3D renderers to properly support this feature.

It's a bit tricky to find a good solution with the existing, popular tags. hmm A building=grandstand has the problem of being larger than the actual seating area – both in terms of height (as you mentioned) but possibly also in terms of area.

If I had the opportunity to design this tagging from scratch, I would probably end up with a tag that refers specifically to the seating on both bleachers and grandstands. This tag would then be used to map just the section of a grandstand that is actually used for seating. Maybe amenity=stadium_seating, which is currently undocumented but has a few hundred uses, might fit the bill depending on how exactly it is/would be used.


OSM in 3D: OSM2World

Online

#6 2022-09-11 19:59:49

googlenaut
Member
Registered: 2017-06-24
Posts: 92

Re: OSM grandstands rendering

what about area=yes, amenity=stepped_seating?

area example: https://www.openstreetmap.org/way/4431170

Offline

#7 2022-09-14 10:52:52

Cactusbone
Member
Registered: 2013-06-11
Posts: 110

Re: OSM grandstands rendering

amenity=stadium_seating looks interesting, for example the denver stadium have both amenity=stadium_seating AND building:part=steps so we can compare big_smile

https://www.openstreetmap.org/#map=17/3 … -105.01997

https://demo.f4map.com/#lat=39.7435407& … 00&zoom=19

It seems the building:part=steps are made to overlap and have a lot of extra tags for the rendering (ie roof orientation)
https://www.openstreetmap.org/way/633086670

the amenity=stadium_seating does not seem to match the steps,
https://www.openstreetmap.org/way/324373552

So for rendering seating, I believe the direction would be required, and the steps height, as well as height  (and min_height when needed)

another more simple example
https://www.openstreetmap.org/way/638574802


what about area=yes, amenity=stepped_seating?

area is not really needed here, I do not see a case where stepped_seating can be a line
However, since stadium_seating already exists, let's start by using this one smile

Last edited by Cactusbone (2022-09-14 10:55:23)

Offline

Board footer

Powered by FluxBB