You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I remove the type=building
with the outline and 3 building parts..
Delete the type=building relationship
delete the building:part which is a copy of the outline
and rename the other 2 building:part into building=
then it renders okay:
But that's lying.. that's mapping for the renderer but not the reality.
The reality is there's not 3 buildings on top of each other.
it's 1 building with 3 building parts..
Ah building:level on the outline creates the bug..
so building:level can't be defined on the outline or else building:part will have problems with rendering.
I won't close this - as it may be a bug.
but maybe it's not, if it's intentional feel free for the devs to close it with the comment:"building:levels is per design intentional to interfere with the rendering"
as I thought from OSM Wiki if height and min_height are defined then hat overrides building:level
but for 2D backwards compatibility one still adds it..
seems the renderer however doesn't like it so I just remove it.. but again, maybe the devs find it worth to work on this to ensure backwards compatibility - so I leave it up to the devs to close/not close this one
Activity
HikeAndMap commentedon Jan 8, 2025
Please by all means, if I do something wrong - kindly explain to me.. thank you
HikeAndMap commentedon Jan 8, 2025
If I remove the type=building
with the outline and 3 building parts..
Delete the type=building relationship
delete the building:part which is a copy of the outline
and rename the other 2 building:part into building=
then it renders okay:

But that's lying.. that's mapping for the renderer but not the reality.
The reality is there's not 3 buildings on top of each other.
it's 1 building with 3 building parts..
HikeAndMap commentedon Jan 8, 2025
Ah building:level on the outline creates the bug..
so building:level can't be defined on the outline or else building:part will have problems with rendering.
I won't close this - as it may be a bug.
but maybe it's not, if it's intentional feel free for the devs to close it with the comment:"building:levels is per design intentional to interfere with the rendering"
as I thought from OSM Wiki if height and min_height are defined then hat overrides building:level
but for 2D backwards compatibility one still adds it..
seems the renderer however doesn't like it so I just remove it.. but again, maybe the devs find it worth to work on this to ensure backwards compatibility - so I leave it up to the devs to close/not close this one
tordanik commentedon Jan 14, 2025
In general, adding
building:levels
to the outline is correct even if the building's parts are mapped individually. So this might be a genuine bug.As with the other issue, an .osm file would be helpful to reproduce the issue more easily.
HikeAndMap commentedon Jan 15, 2025
Dear Tordanik, thank you for the reply.
With the following zip file (building:levels=1 in the outline) this is what I see:

false.zip
HikeAndMap commentedon Jan 15, 2025
The following has building:levels=1 removed and this is what I get

good.zip