citygml-energy issueshttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues2019-10-24T16:47:42+02:00https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/170New Time Series type MonthlyTimeSeries2019-10-24T16:47:42+02:00Joachim BennerNew Time Series type MonthlyTimeSeriesIn the building simulation area, there are quite often monthly averages, and time series consisting of 12 monthly averages for a certain year. In principle, such a time series could be modelled as *IrregularTimeSeries*, but the processin...In the building simulation area, there are quite often monthly averages, and time series consisting of 12 monthly averages for a certain year. In principle, such a time series could be modelled as *IrregularTimeSeries*, but the processing would be much easier if only 12 monthly values and the corresponding year need to be specified.
It is therefore proposed to add a new class **MonthlyTimeSeries**, derived from *IrregularTimeSeries*, for specifying one value for each month of a specific year.![MonthlyTimeSeries](/uploads/74292351c03115ba65ca1103ed318c79/MonthlyTimeSeries.png)https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/162Add attributes for File-based TimeSeries2019-10-24T16:53:35+02:00Giorgio AgugiaroAdd attributes for File-based TimeSeriesI was thinking that it might be useful to add one or two fields to the file-based TimeSeries classes, i.e.
is_compressed:Boolean=FALSE
compression_type:CompressionTypeValue[0..1]
CompressionTypeValue could be either an enumeration or a...I was thinking that it might be useful to add one or two fields to the file-based TimeSeries classes, i.e.
is_compressed:Boolean=FALSE
compression_type:CompressionTypeValue[0..1]
CompressionTypeValue could be either an enumeration or a codelist.
The attributes could be added to both classes, or an abstract class _TimeSeriesFile could be created between them and AbstractTimeSeries. In the latter case, other shared existing attributes (uom, file, etc...) could be moved to _TimeSeriesFile.https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/161Redundant attribute stationName in WeatherStation?2019-10-24T17:09:18+02:00Giorgio AgugiaroRedundant attribute stationName in WeatherStation?I may be wrong, but a WeatherStation is derived from a _CityObject, which itself inherits a number of attributes (e.g. id, description AND name).
I think therefore that this attribute could be dropped. Is there a specific reason for not ...I may be wrong, but a WeatherStation is derived from a _CityObject, which itself inherits a number of attributes (e.g. id, description AND name).
I think therefore that this attribute could be dropped. Is there a specific reason for not using the standard gml:name one?https://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 Benner