citygml-energy issueshttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues2019-10-24T15:36:35+02:00https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/169ThermalZone should have isVentilated2019-10-24T15:36:35+02:00Peter RemmenThermalZone should have isVentilatedThe ThermalZone class should have an object, that describes if the thermal zone is ventialted through mechanical ventilation (similar to isHeated, isCooled).
Interesting enough: the UseageZone class already has an attribute "ventilatio...The ThermalZone class should have an object, that describes if the thermal zone is ventialted through mechanical ventilation (similar to isHeated, isCooled).
Interesting enough: the UseageZone class already has an attribute "ventilationSchedule".https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/159Multi-zone models2019-10-24T15:25:33+02:00Joachim BennerMulti-zone modelsFor thermal models containing more than one thermal zone, it is essential to know the topological structure of the zones. This especially means that internal thermal boundaries and their relations to the correnponding thermal zones need ...For thermal models containing more than one thermal zone, it is essential to know the topological structure of the zones. This especially means that internal thermal boundaries and their relations to the correnponding thermal zones need to be identified.
Energy ADE 1.0 represent an internal thermal boundary by **one object ThermalBoundary** (with thermalBoundaryType **interiorWall**, **intermediaryFloor**, ...), being related with **two objects ThermalZone**. This sounds good, but in fact is incorrect. In reality, thermal boundaries are **oriented surfaces** bounding the volume of the different thermal zones. The normal convention is that the **orientation** of a thermal boundary- in the Energy ADE either represented by the attributes **azimuth** / **inclination** or by an explicit surface (attribute **surfaceGeometry** ) - points out of the zone volume. In consequence, an **internal thermal boundary cannont be correctly represented by only one ThermalBoundary object**.
In the process of transforming an Energy ADE 1.0 model into a specifc simulation model like EnergyPlus IFD-file, it might principally be possible to correct this unavoidably error and switch the surface orientation for one of the two adjacent zones, but this is very difficult to implement. Therefore, a new concept is proposed to specify the topological structure in multi-zone models:
**Each ThermalBoundary object belongs to exactly one ThermalZone object. In consequence, internal thermal boundaries (and if necessary also internal thermal openings) are represented by two ThermalBoundary / ThermalOpening objects, refering each other by a relation isAdjacentTo of cardinality 0..1**.
![TwoThermalZones](/uploads/8a2e10ff479f292a55f08721ae619382/TwoThermalZones.png)
![MultiZoneModel](/uploads/741ae56a7d2e0a5067dca04cd1e53458/MultiZoneModel.png)Joachim BennerJoachim Bennerhttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues/155Modelling of partly touching buildings2019-10-24T15:02:36+02:00Joachim BennerModelling of partly touching buildingsEspecially in densly populated city centers, it often occurs that neighboring buildings partly or fully touch each other. In this case, the building's energetic behavior significantly differs from a free-standing building. Unfortunately,...Especially in densly populated city centers, it often occurs that neighboring buildings partly or fully touch each other. In this case, the building's energetic behavior significantly differs from a free-standing building. Unfortunately, CityGML completely lacks a concept for "shared walls/roofs", and existing CityGML building models therefore do not represent closed building structures correcty. A single CityGML Building object is always bounded by *exterior* BoundarySurfaces (WallSurface, RoofSurface, GroundSurface).
In the Energy ADE, a ThermalBoundary object can be specified as "sharedWall". In reality, often only a part of a wall or roof surface is shared with a neighboring building, and the remaining part is facing the outside air. Thus, for transforming CityGML BoundarySurface into Energy ADE ThermalBoundary objects, a separation of the BoundarySurface geometry is needed, which is a time consuming and error-prone process. In most cases, it is much faster and much more robust only to calculate the **size of the shared area**. It is therefore proposed to add a numeric attribute to ThermalBoundary to either specify the absolute **sharedAreaSize** (type Area), or the ratio of shared area to total BoundarySurface area (**sharedAreaRatio**, type Scale).
![ThermalBoundary](/uploads/d4dd82a831a7ada79985f04c29193aac/ThermalBoundary.png)Joachim BennerJoachim Benner