You are not logged in.

#1 2021-03-08 05:50:48

arkriger
Member
Registered: 2021-03-07
Posts: 7

building:part when relation type=building role=outline exists

Hi.

Forgive my noobish-ness. I’m attempting to define roof shape more accurately using Kendzi3D View and am experiencing challenges when `building:part` is surrounded with a relation `type=building` `role=outline` (a building)  [to the `building:part`]. I don’t have height but am using `building:level` as a proxy. As per OpenStreetMap the outline must be tagged at the maximum level and each `building:part` at its respective level.

When extracting and generating LOD1 3D Buildings the result is as expected if the outline is excluded.
It matches [3dbuildings.com](https://3dbuildings.com/data/#18.16/-33 … 0205/76/58)

In Kendzi the result is the outline at maximum extrusion height. I can not even select the object.

Should `role=outline` not be automatically excluded in the 3D render when `building:part` exists? Have I tagged these incorrectly? What stupidity have I performed and how do I correct it?

(sorry; I do not know how to add an image which would explain the challenge more clearly)

Adrian.

edit (08/03/2021): Ok. some searching reveals this is an actual challenge that members get around through mapping for a renderer and setting the `building:levels=0` when an outline exists [here](https://forum.openstreetmap.org/viewtopic.php?id=57195). Is there a permanent solution that fulfills OpenStreetMap guidelines and makes viewing in kendzi3D possible?

edit (18/08/2021): I've edited the `Subject` since this was never a rendering challenge: but rather tagging 'relations' correctly.

Last edited by arkriger (2021-08-18 15:53:21)

Offline

#2 2021-03-15 21:10:07

pyram
Member
Registered: 2012-06-16
Posts: 1,336

Re: building:part when relation type=building role=outline exists

arkriger wrote:

As per OpenStreetMap the outline must be tagged at the maximum level...

That's not an error, but you needn't, if there are "building:part"s.

Please show an example, that doesn't work ( e.g. like a link like https://www.openstreetmap.org/relation/12295766 or https://www.openstreetmap.org/way/905545982 ). By the way, this building is duplicate and should only be a relation *or* a way.
Probably this is the real problem.

arkriger wrote:

`building:levels=0`

That is a bad workaround and idea.

Offline

#3 2021-03-17 19:49:33

arkriger
Member
Registered: 2021-03-07
Posts: 7

Re: building:part when relation type=building role=outline exists

Thank you for helping me communicate effectively.
You are right: https://www.openstreetmap.org/way/904201083 was not part of the relation. It displays correctly in Kendzi 3D View now.

I am a bit confused by your duplicate statement. Should the outline not be a way; part of a relation `type=building`? How else would the building outline be defined? How would the `building:part` know which outline to belong too?

Last edited by arkriger (2021-03-17 21:08:37)

Offline

#4 2021-04-04 21:54:19

maro21
Member
From: Wrocław
Registered: 2018-03-06
Posts: 815

Re: building:part when relation type=building role=outline exists

This way https://www.openstreetmap.org/way/905545982 shouldn't have any tags. The building tags for 2D are already in the multipolygon relation.

Offline

#5 2021-04-14 12:54:00

arkriger
Member
Registered: 2021-03-07
Posts: 7

Re: building:part when relation type=building role=outline exists

I've deleted all tags from the `role=outer`.
This appears to solve the overpass-turbo challenge (here) where [the tags of] `role=outer` were coming with the query. With the tags removed the result (here) looks correct.

Your kung-fu is legend. Thank you.

Do you mind responding to OpenStreetMap help (here) please? I want to accept your answer; so that the question can be resolved.

Offline

#6 2021-08-11 12:04:44

arkriger
Member
Registered: 2021-03-07
Posts: 7

Re: building:part when relation type=building role=outline exists

I am incapable of defining these relations correctly. I don't know how.

The [relation](https://www.openstreetmap.org/relation/13076003) and the [query](https://overpass-turbo.eu/).

Where/how must the relation `role=outline` be defined so that the `building:part` is returned when `role=outline` exists?
Your help is appreciated.

edit: (31/08/2021)
`building:part multipolygon` relations were not accounted for - when a `building:part` has a courtyard.

adding: `relation["building:part"]["type"="multipolygon"](area.a);` to the [query](https://overpass-turbo.eu/) (line 10) fixes it.

Last edited by arkriger (2021-08-31 16:19:18)

Offline

Board footer

Powered by FluxBB