cstb / citygml-energy

CityGML Energy ADE
41 stars 9 forks source link

How to specify U-values at building scale? #119

Closed oliviertournaire closed 6 years ago

oliviertournaire commented 8 years ago

I am wondering how it is possible to define U values at building scale only. Let's say that a building is modeled in LOD 0 (lod0Footprint + measuredHeight) or in LOD 1, it can be interesting for some simulation tools to define a single U value for the walls and / or the ground and / or the roof.

I can use several Construction instances and attach them to the building, but how can I differentiate them (except using a convention that fills the gml:name or gml:description)?

JoachimBenner commented 8 years ago

With the 0.7.0 model, Construction instances can only be attached to _ BoundarySurface, _ Opening or ThermalComponent. Thus, it is not possible to define a list of "Building-Constructions", and as Olivier said it is not possible to differentiate a Construction instance as "Facade-Construction" or "Roof-Construction". If this is a real issue, we must define a specific ADE-property of _ AbstractBuilding.

oliviertournaire commented 8 years ago

I suggest to reopen the issue and discuss about it!

JoachimBenner commented 8 years ago

Yes, I agree with you, but for 0.7.0 we should stay with the actual solution. I am sorry, but I need to finish the work on version 0.7.0 with this week.

oliviertournaire commented 8 years ago

Yes, no problem. I set the milestone to backlog so that we can discuss it later.

gioagu commented 7 years ago

I would like to widen a little bit the discussion and say that, actually, the original idea of having every single CityObject be (optionally!!) linked to a Construction was not that bad, as this actually makes sense in the real (constructed) world! What is more, I believe the construction module would fit very well also outside the Energy ADE (e.g. UtilityNetwork ADE?) with minor additions/changes, so I believe it is time to start thinking how to proficiently "recycle" the module also in other contexts. In the current 0.7 version, there are only a very limited number of classes that have a construction.

So, I would like to (re)open the discussion, here or maybe during the next workshop.

Just like the Occupancy module can be used well beyond energy applications, why not also the construction and materials one?

RomainNouvel commented 7 years ago

Hi, The fact that the object Constructions (and its related module) appears as attribute twice in the Energy ADE (ThermalComponent and BoundarySurface... and maybe ThermalBoundary) doesn't mean that we can't reuse/recycle it in other ADEs. Exactly like the objects Occupants or Household. Or did I misunderstood your comment Giorgio?

JoachimBenner commented 7 years ago

Change Request: Introduction of a new ADE attribute of _AbstractBuilding: buildingMainConstruction: AbstractConstruction[0..1]

JoachimBenner commented 7 years ago

Can we agree on this change for version 0.9.0?

RomainNouvel commented 7 years ago

Ok, how can we define it? Equivalent construction of the building? Construction of most building surface?

gioagu commented 7 years ago

Ok for the concept, regarding the name, my proposal:

...BuildingConstruction

with ... being something like: