Redefine the "volume" attribute in _AbstractBuilding and ThermalZone
Created by: gioagu
Some thought ideas for the next version 0.7
This is a sort of extension of the floorArea idea (issue #47 (closed)), but with regards to volume. Some ideas were collected also in Issue #55 (closed) Currently, we only have two attributes: grossVolume, and netVolume (which is only in ThermalZone). In reality, we may define several types of volume, such as: netVolume, grossVolume, heatedVolume, cooledVolume, ventilatedVolume, etc.
We might even go further, especially when we derive volume from heterogeneous models, such as lod1Volume, lod2Volume, lod3Volume.
Finally, we may think that you can cross these two lists and have something like: lod2NetVolume, lod2GrossVolume, lod2VentilatedVolume, etc. (looks weird, but it's for understanding)
So, my idea is to reshape the volume attribute in a similar way to the floorArea. The attribute could be like:
volume: Volume_new [0..n]
<> Volume_new having volume: Volume volumeType: VolumeType
<> VolumeType lod2NetVolume, lod2GrossVolume, lod2VentilatedVolume, (or something else, it is an example).
In anycase, I would keep the codelist (and no enumeration) so that we can play around at the beginning. What is more, there are here for sure some issues with the names (Volume), but somebody may help to avoid homonimous objects - here I am not the expert. What is more, there could be some hints from other standards about naming...
What do you think?