citygml-energy issueshttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues2016-01-14T13:50:58+01:00https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/66Add RegularTimeSeriesFile and IrregularTimeSeriesFile Class which inherits fr...2016-01-14T13:50:58+01:00Moritz Robert LausterAdd RegularTimeSeriesFile and IrregularTimeSeriesFile Class which inherits from TimeSeries*Created by: RomainNouvel*
RegularTimeSeriesFile
-> Attributes:
- uom: UnitOfMeasure [1]
- File. type: uri [1]
- timeIntervale: TM_IntervalLength [1]
- numberOfHeaderLines [0..1](default value: 0)
- fieldSeparator [1](default value: [...*Created by: RomainNouvel*
RegularTimeSeriesFile
-> Attributes:
- uom: UnitOfMeasure [1]
- File. type: uri [1]
- timeIntervale: TM_IntervalLength [1]
- numberOfHeaderLines [0..1](default value: 0)
- fieldSeparator [1](default value: [space])
- recordSeparator [1](default value: [new line])
- regionalCode [codeList](default value: en)
- valueFieldNumber[0..1] : field number from which the value dataset must be extracted (default value: 1)
IrregularTimeSeriesFile
-> Attributes:
- uom: UnitOfMeasure [1]
- File. type: uri [1]
- numberOfHeaderLines [0..1](default value: 0)
- fieldSeparator [1](default value: [space])
- recordSeparator [1](default value: [new line])
- regionalCode [codeList](default value: en)
- valueFieldNumber[0..1] : field number from which the value dataset must be extracted (default value: 1)
- timeFieldNumber[0..1] : field number from which the time dataset must be extracted (default value: 1)
v0.6.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/65add Mandatory Units of Measure2019-10-08T08:32:29+02:00Moritz Robert Lausteradd Mandatory Units of Measure*Created by: RomainNouvel*
List of units of measure should be mandatory (for instance: m2 and not m² nor sqm).
Check if we can use standard list of units / uri. How do we deal with it in GML
*Created by: RomainNouvel*
List of units of measure should be mandatory (for instance: m2 and not m² nor sqm).
Check if we can use standard list of units / uri. How do we deal with it in GML
backloghttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues/64Add optional geometrical attributes to ThermalZone, UsageZone, ThermalBoundary2016-01-14T13:51:17+01:00Moritz Robert LausterAdd optional geometrical attributes to ThermalZone, UsageZone, ThermalBoundary*Created by: RomainNouvel*
Introduction of optional geometrical attributes to:
- ThermalZone: volumeGeometry, type: gml:Solid, [0..1]
- UsageZone: volumeGeometry, type: gml:Solid, [0..1]
- ThermalBoundary: surfaceGeometry, type: gml:Mul...*Created by: RomainNouvel*
Introduction of optional geometrical attributes to:
- ThermalZone: volumeGeometry, type: gml:Solid, [0..1]
- UsageZone: volumeGeometry, type: gml:Solid, [0..1]
- ThermalBoundary: surfaceGeometry, type: gml:Multi-Surface, [0..1]
Agreed in Workshop Munich by Thomas, Georgio, Alexandru, Silvia, Jerome, KH
v0.6.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/63Space-separated values in regular time series2016-01-14T13:51:32+01:00Moritz Robert LausterSpace-separated values in regular time series*Created by: RomainNouvel*
Make possible to store time series under the form of space separated values inside the same tag.
Proposition of Jerome, agreed by Joachim and Thomas.
*Created by: RomainNouvel*
Make possible to store time series under the form of space separated values inside the same tag.
Proposition of Jerome, agreed by Joachim and Thomas.
v0.6.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/55ThermalZone Volume2016-01-14T13:52:29+01:00Moritz Robert LausterThermalZone Volume*Created by: RomainNouvel*
In the ADE Energy v0.5, the ThermalZone does not include a parameter volume.
In the case that a Building includes several ThermalZone (or if the ThermalZone does not correspond exactly to the 3D building geom...*Created by: RomainNouvel*
In the ADE Energy v0.5, the ThermalZone does not include a parameter volume.
In the case that a Building includes several ThermalZone (or if the ThermalZone does not correspond exactly to the 3D building geometry), information about the Abstract building volume and the ThermalZone floor area are not sufficient to calculate the space heating of the ThermalZone.
Therefore, a parameter volume is required for the ThermalZone.
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/62Test issue2015-11-30T11:32:26+01:00Moritz Robert LausterTest issue*Created by: oliviertournaire*
**Describe issue**
*Created by: oliviertournaire*
**Describe issue**
v0.6.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/59Window missing in ThermalBoundarySurfaceTypeType2015-10-29T16:04:51+01:00Moritz Robert LausterWindow missing in ThermalBoundarySurfaceTypeType*Created by: PRemmen*
A window can also be a ThermalBoundarySurface but is not part of the Enumeration "ThermalBoundarySurfaceTypeType" am I missing something ?
*Created by: PRemmen*
A window can also be a ThermalBoundarySurface but is not part of the Enumeration "ThermalBoundarySurfaceTypeType" am I missing something ?
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/54footprintArea2015-11-11T14:41:19+01:00Moritz Robert LausterfootprintArea*Created by: RomainNouvel*
the footprint area of a building is sometimes required for the calculation of performance, environmental and planning ratio.
-> a parameter footprintArea may be added in the _AbstractBuilding class
*Created by: RomainNouvel*
the footprint area of a building is sometimes required for the calculation of performance, environmental and planning ratio.
-> a parameter footprintArea may be added in the _AbstractBuilding class
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/60ThermalBoundarySurface Types2016-01-14T13:51:55+01:00Moritz Robert LausterThermalBoundarySurface Types*Created by: RomainNouvel*
The first goal of ThermalBoundarySurfaceType was to identify specific Thermal boundary surface typologies which are likely to have similar Constructions in a building (and possibly relate them with a construct...*Created by: RomainNouvel*
The first goal of ThermalBoundarySurfaceType was to identify specific Thermal boundary surface typologies which are likely to have similar Constructions in a building (and possibly relate them with a construction library). Indeed, the unique use of BoundarySurfaceType for this purpose is not enough (is floor surface directly in contact to the ground, or the ceiling of the basement floor?). Moreover, for Buildings LOD4, 2 BoundarySurfaces of different rooms (FloorSurface or Room 1 and CeilingSurface of Room2) may corresponds to a unique ThermalBoundarySurface (IntermediaryFloor).
Presently in the Energy ADE v0.5, the ThermalBoundarySurfaceType Codelist is uncomplete and not fully clear.
For the Building LOD4, we should introduced:
- **InteriorWall**. Definition: Vertical partition separating two ThermalZones of a same building.
- **IntermediaryFloor**. Definition: Horizontal partition separating two ThermalZones of a same building.
Further proposed specifications of existing ThermalBoundarySurfaceType:
- **SharedWall**. Definition: Vertical partition separating two different buildings.
- **OuterWall** (or Outwall). Definition: Vertical thermal boundary surface with one side facing outdoor.
- **BasementFloor**. Definition: Lower horizontal thermal boundary surface of the ThermalZone, built direct on the ground.
- **BasementCeiling** (instead of cellarCeiling). Definition: Horizontal partition separating the basement floor and the ground floor.
- **AtticFloor** (instead of TopCeiling which can also be a FlatRoof). Definition: Horizontal partition separating the attic and the highest full storey.
Concerning the roof, flat roofs and pitched roofs obviously don't have the same constructions (as well as copular). However, should we distinguish them in the ThermalBoundarySurfaceType? or should we only right Roof, and the constructions could be deduced from the roof type for instance?
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/57Contruction and material names2016-01-14T13:52:09+01:00Moritz Robert LausterContruction and material names*Created by: RomainNouvel*
Presently, for the identification and management of the Construction objects, no name / description exist.
- it would be useful to add an attribute name[CharacterString].
for instance: "28cm brick wall".
Co...*Created by: RomainNouvel*
Presently, for the identification and management of the Construction objects, no name / description exist.
- it would be useful to add an attribute name[CharacterString].
for instance: "28cm brick wall".
Concerning the Material, What contains precisely the attribute referenceURI? Can we get the material name through it? or it is just an reference id?
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/56Building Key Performance Indicators (KPI)2018-12-06T10:43:38+01:00Moritz Robert LausterBuilding Key Performance Indicators (KPI)*Created by: RomainNouvel*
Key Performance Indicators may be important for energy analyses at urban scale, helping for example to understand building consumptions, plan an energy refurbishment strategy, or compare different energy plann...*Created by: RomainNouvel*
Key Performance Indicators may be important for energy analyses at urban scale, helping for example to understand building consumptions, plan an energy refurbishment strategy, or compare different energy planning variants.
They are generally intermediary/final outputs, deduced from other geometry and physical parameters of the 3d city model.
Some useful KPI:
- surfaceAreaToVolumeRatio (index of compacity)
- meanUValue (global envelope insulation level)
- specificPrimaryEnergyDemand (global efficiency of the building)
This issue is a general question: do we want to include some KPIs in our ADE Energy? If yes, they would be parameters of _AbstractBuilding.
backloghttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues/48Schedule LoD1/ daily usage ending and starting time2015-11-27T11:43:16+01:00Moritz Robert LausterSchedule LoD1/ daily usage ending and starting time*Created by: Maryamzk*
Usage time defined by starting time and ending time cannot be adapted to all cases. For example, for cases that starting time and ending time of different days a week varies, like a restaurant with off-day on Thur...*Created by: Maryamzk*
Usage time defined by starting time and ending time cannot be adapted to all cases. For example, for cases that starting time and ending time of different days a week varies, like a restaurant with off-day on Thursdays. Maybe changing starting time and ending time to usage hour per week is more accurate, as it is defined in ISO 13790, as well. Moreover, switched-off time is also required, since for considering intermittency effects on heating demand according to ISO 13790, the longest and shortest switched-off time during calculation time (month for Monthly balance) is required.
Therefore, we can modify the schedule in LoD1 as:
• Changing starting time and ending time to longest and shortest switched off time in month
• Adding usage hour per week
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/51Relation between _AbstractBuilding and ThermalZone2015-10-23T08:56:34+02:00Moritz Robert LausterRelation between _AbstractBuilding and ThermalZone*Created by: Maryamzk*
Hi again,
Another recommendation:
The relation between _AbstractBuilding and ThermalZone is recommended to be composition hierarchy, since energy need of thermal zone is strongly dependent on the entire building...*Created by: Maryamzk*
Hi again,
Another recommendation:
The relation between _AbstractBuilding and ThermalZone is recommended to be composition hierarchy, since energy need of thermal zone is strongly dependent on the entire building (effects of unconditioned spaces for example). This is the same for relation between ThermalBoundarySurface and ThermalZone, where, no thermal zone can exist without thermal boundary surface.
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/50Structure of adjacentTo:2016-01-14T13:53:06+01:00Moritz Robert LausterStructure of adjacentTo:*Created by: Maryamzk*
Hi everybody,
I have a doubt about structure of "adjacentTo" association, which I think is needed to be discussed here.
The recent structure of adjacent association is not able to identify the thermal characteri...*Created by: Maryamzk*
Hi everybody,
I have a doubt about structure of "adjacentTo" association, which I think is needed to be discussed here.
The recent structure of adjacent association is not able to identify the thermal characteristics of the adjacent surface but the whole adjacent zone. Therefore, if some thermal parameter of the adjacent surface should be specified, the defined adjacent association should be modified. Below you can find some examples about the parameter of adjacent zone in ISO 13790 and DIN 15899 which are required for heating demand of the thermal zone. I have explained where re-structuring of the adjacent association might be required, but the energy-expert persons can approve it.
In ISO 13790:
- Time-averaged heat flux from all solar sources in the unconditioned adjacent zone. This heat flux in unconditioned is calculated like heat flux in thermal zone for all surfaces (see equations bellow), therefore the adjacent surface should not necessarily be identified. In other words, according to the current definition of ThermalZone class and adjacentTo association, when solar sources of thermal zone are identified, the solar sources for unconditioned adjacent zone are also identified. The only missing point is to recognize an adjacent zone is conditioned or not, right?
Solar heat gain:
![image](https://cloud.githubusercontent.com/assets/12936292/10601511/9994580e-7712-11e5-9aef-77d65cf02dfa.png)
![image](https://cloud.githubusercontent.com/assets/12936292/10601520/ac4e70ce-7712-11e5-9fef-489504c031f7.png)
the time-average heat flow rate from solar heat source l in the adjacent unconditioned space,
,in W
,and
![image](https://cloud.githubusercontent.com/assets/12936292/10601542/b881aee2-7712-11e5-85c8-29de124f2c1f.png)
In DIN 15899:
-Solar radiation passing through the sunspace into the adjacent building. For calculating this we need to know the area of the adjacent surface (see the equations bellow), we need re-structuring in adjacent (DIN 18599-section 6.4)
heat flow into the unheated or uncooled sunspace:
![image](https://cloud.githubusercontent.com/assets/12936292/10601827/9a60a894-7714-11e5-8c5b-d070e137b594.png)
![image](https://cloud.githubusercontent.com/assets/12936292/10601831/a0373dbe-7714-11e5-88eb-8d9e7cd406de.png)
is the total solar radiation passing through the sunspace into the adjacent building zone, calculated using equation (below) for all transparent elements of the partition separating the building zone considered and the unheated sunspace;
![image](https://cloud.githubusercontent.com/assets/12936292/10601834/a5cd9584-7714-11e5-8169-23112a1d843d.png)
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/43averageCeilingHeight2016-01-14T13:54:39+01:00Moritz Robert LausteraverageCeilingHeight*Created by: RomainNouvel*
The attribute "averageStoreyHeight" of _AbstractBuilding in the Energy ADE version 0.5 is partly redundant with the attribute storeysHeightAboveGround[0..*] of CityGML, and seems not very useful.
PROPOSITION:
...*Created by: RomainNouvel*
The attribute "averageStoreyHeight" of _AbstractBuilding in the Energy ADE version 0.5 is partly redundant with the attribute storeysHeightAboveGround[0..*] of CityGML, and seems not very useful.
PROPOSITION:
It could be renamed in "averageCeilingHeight" which is a parameter used in many Heating Demand calculation norms for instance (the difference between both is the thickness of the ceiling)
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/49EnergySupply, Energy carrier, Energy source2016-01-14T13:53:20+01:00Moritz Robert LausterEnergySupply, Energy carrier, Energy source*Created by: RomainNouvel*
1- In our EnergyADE version 0.5, the feature "EnergySource" can be a Primary our Secondary Energy Source, renewable or not. It is therefore not systematically an energy carrier ("energy form which has been tra...*Created by: RomainNouvel*
1- In our EnergyADE version 0.5, the feature "EnergySource" can be a Primary our Secondary Energy Source, renewable or not. It is therefore not systematically an energy carrier ("energy form which has been transformed from primary energy sources, such as electricity"), like in the case of Solar Energy.
Beside, some energy carrier (hot water, chilled air etc.) related to EnergySupply does not have related CO2 emission factor, primary energy factor etc...
We should therefore rethink our EnergySupply, EnergySource and EnergyCarrier structures, contents and wordings...
2- Other issue: how do we model the (PV) electrical production feeding the grid? Should we only add an EndUseType "GridFeedIn"?
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/47Building Floor Areas2016-01-14T13:53:32+01:00Moritz Robert LausterBuilding Floor Areas*Created by: RomainNouvel*
Many different floor area definitions exist, depending on the application (e.g. heating, living, working), the country. In US, you have for instance the choice between gross floor area, gross internal area, ne...*Created by: RomainNouvel*
Many different floor area definitions exist, depending on the application (e.g. heating, living, working), the country. In US, you have for instance the choice between gross floor area, gross internal area, net internal area, usable floor area... with sizeable difference of results when you're using consumption ratio and criterias refering to them.
In the version 0.5, different Floor areas are used in _AbstractBuilding (referenceHeatedFloorArea) and in ThermalZone (heatedFloorArea, cooledFloorArea). This is quite incomplete and confusing...
PROPOSITION:
- replace referenceHeatedFloorArea by a type FloorArea precising the area and the area definition (CodeList?), which could be associated to _AbstractBuilding, _ThermalZone, _UsageZone etc.
- replace heatedFloorArea and cooledFloorArea of ThermalZone by this new type FloorArea and the parameters isHeated[Boolean] and isCooled[Boolean]
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/46Energy Performance Certification2016-01-14T13:53:42+01:00Moritz Robert LausterEnergy Performance Certification*Created by: RomainNouvel*
Different labels (e.g. LEED, KfW Effizienzhaus) and degrees (e.g. of Platine, KfW 100) of energy performance certification exist in the world.
PROPOSITION:
a hierarchical CodeList should be defined to manage t...*Created by: RomainNouvel*
Different labels (e.g. LEED, KfW Effizienzhaus) and degrees (e.g. of Platine, KfW 100) of energy performance certification exist in the world.
PROPOSITION:
a hierarchical CodeList should be defined to manage the different energy performance certifications
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/44building Physics Description / construction type2016-07-05T23:05:11+02:00Moritz Robert Lausterbuilding Physics Description / construction type*Created by: RomainNouvel*
Some information about the building contruction type could be useful, for instance to assess the materials of a buildings (information about building type and year of construction is sometimes not enough).
A...*Created by: RomainNouvel*
Some information about the building contruction type could be useful, for instance to assess the materials of a buildings (information about building type and year of construction is sometimes not enough).
A attribute called "buildingPhysicsDescription" or "constructionType" (the "constructionStyle" of the version 0.5 doesn't look like a reference name) should be precisely defined and maybe set as a hierarchical CodeList.
(Some information about building construction type: http://www.wikihow.com/Determine-a-Building%27s-Construction-Type)
v0.7.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/45Landmarked / Historical Buildings2016-01-14T13:54:24+01:00Moritz Robert LausterLandmarked / Historical Buildings*Created by: RomainNouvel*
Different status of landmarked/historical buildings exist in Europe with different degrees of protection.
Therefore, a simple landmarked[Boolean] as attribute of _AbstractBuilding should be not enough.
PROPOSI...*Created by: RomainNouvel*
Different status of landmarked/historical buildings exist in Europe with different degrees of protection.
Therefore, a simple landmarked[Boolean] as attribute of _AbstractBuilding should be not enough.
PROPOSITION:
- Use the Hierarchical/multi-lingual CodeList Re3gistry as developed by JRC to manage the different certification labels and degrees.
- Rename this attribute (culturalHeritageStatus?)