citygml-energy issueshttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues2019-10-24T15:48:09+02:00https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/156Explicit specification of convective heat transfer coefficients2019-10-24T15:48:09+02:00Joachim BennerExplicit specification of convective heat transfer coefficientsMost building energy simulation systems automatically calculate the inside and outside convective heat transfer coefficients. In some cases, especially for modelling benchmark tests list BESTEST, it should however be possible to explicit...Most building energy simulation systems automatically calculate the inside and outside convective heat transfer coefficients. In some cases, especially for modelling benchmark tests list BESTEST, it should however be possible to explicitly specify these parameters. It is therefore proposed to extend the class **Construction** by two parameters **insideConvectionCoefficient** and **outsideConvectionCoefficient** (type Measure).
![Construction](/uploads/cb1d1af8e23a3560aa3a695587f3b89d/Construction.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 Bennerhttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues/154Specification of soil temperatures2022-12-07T15:17:21+01:00Joachim BennerSpecification of soil temperaturesThe energy exchange between a building and the surrounding soil definitely affects the energetic behavior of the building. An important parameter to model this effect is the time-varying soil temperature. Thus, it should be possible to s...The energy exchange between a building and the surrounding soil definitely affects the energetic behavior of the building. An important parameter to model this effect is the time-varying soil temperature. Thus, it should be possible to specify a time series of soil temperatures in the Energy ADE.
One way to realize this is to consider soil temparatures as additional weather data parameters by extending the Enumeration **WeatherDataTypeValue** with a new item **soilTemperature**.
![SoilTemperature](/uploads/b1a21a93e7a84034974987d23e92671e/SoilTemperature.png)Joachim BennerJoachim Bennerhttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues/152Redundant relation "parameter" for WeatherStation2019-10-28T08:30:44+01:00Giorgio AgugiaroRedundant relation "parameter" for WeatherStationA _CityObject is extended to have 0..* WeatherData objects through "weatherData" relation.
A WeatherStation is derived from _CityObject, and can have additionally 0..* Weatherdata through "parameter" relation.
This ("parameter") is IMO...A _CityObject is extended to have 0..* WeatherData objects through "weatherData" relation.
A WeatherStation is derived from _CityObject, and can have additionally 0..* Weatherdata through "parameter" relation.
This ("parameter") is IMO redundant and should hence be removed.Joachim BennerJoachim Bennerhttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues/151Typo in relation "emitts"2019-05-14T10:33:02+02:00Giorgio AgugiaroTypo in relation "emitts"If you look at the UML diagram, you will notice that relation between EnergyFlow and EmitterSystem is written eimiTTs (with double T).
This is clearly a small typo to be corrected.If you look at the UML diagram, you will notice that relation between EnergyFlow and EmitterSystem is written eimiTTs (with double T).
This is clearly a small typo to be corrected.Joachim BennerJoachim Bennerhttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues/130Simulation results2018-12-06T10:43:38+01:00Moritz Robert LausterSimulation results*Created by: JoachimBenner*
I think the EnergyADE should be able to represent also the **output data of simulation systems**. At the moment, it is possible to include simulated energy demands into an EnergyADE file, but not, e.g., the s...*Created by: JoachimBenner*
I think the EnergyADE should be able to represent also the **output data of simulation systems**. At the moment, it is possible to include simulated energy demands into an EnergyADE file, but not, e.g., the simulated actual temperature of a Thermal Zone.
Because the ADE supports different types of simulations and mutiple simulation systems, it is quite difficult to model arbitrary simulation results. Therefore, I propose to start with a very simple and generic data type **_SimulationData_:** A **text attribute** describing the simulated quantity (e.g. actual temperature) and a **Time Series** with time dependent, scalar data. This data structure can be referenced by every city object (ADE attribute of _CityObject). In future versions of the standard, it might be extended for other types of simulation data, or for supporting references to data bases.https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/141Sensors, Timeseries and measurements requirements2018-12-06T10:43:38+01:00Moritz Robert LausterSensors, Timeseries and measurements requirements*Created by: pascal-schetelat*
This issue is meant to discuss all energy-ade partners needs and use case concerning time series, measurement, sensor and other related concepts.*Created by: pascal-schetelat*
This issue is meant to discuss all energy-ade partners needs and use case concerning time series, measurement, sensor and other related concepts.https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/103Choose a license2018-12-06T10:43:38+01:00Moritz Robert LausterChoose a license*Created by: mlauster*
We currently do not have a license for CityGML ADE Energy.
That means, we are quite restrictive, to cite github:
"You're under no obligation to choose a license. It's your right not to include one with your code...*Created by: mlauster*
We currently do not have a license for CityGML ADE Energy.
That means, we are quite restrictive, to cite github:
"You're under no obligation to choose a license. It's your right not to include one with your code or project, but please be aware of the implications. Generally speaking, the absence of a license means that the default copyright laws apply. This means that you retain all rights to your source code and that nobody else may reproduce, distribute, or create derivative works from your work. This might not be what you intend."
https://help.github.com/articles/open-source-licensing/
To open the discussion, what about MIT license?
http://choosealicense.com/
http://choosealicense.com/licenses/mit/
backloghttps://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.
backlog