citygml-energy issueshttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues2018-12-06T10:43:38+01:00https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/122Industrial FeatureTypes in EnergyConversionSystem2018-12-06T10:43:38+01:00Moritz Robert LausterIndustrial FeatureTypes in EnergyConversionSystem*Created by: kwakuwulf*
_As discussed in Vienna I'm adding some issues from the viewpoint of industrial process modelling:_
Adding _chiller_ and _air compressor_ as feature types in `EnergyConversionSystem`.
*Created by: kwakuwulf*
_As discussed in Vienna I'm adding some issues from the viewpoint of industrial process modelling:_
Adding _chiller_ and _air compressor_ as feature types in `EnergyConversionSystem`.
v0.8.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/119How to specify U-values at building scale?2017-11-27T09:10:03+01:00Moritz Robert LausterHow to specify U-values at building scale?*Created by: oliviertournaire*
I am wondering how it is possible to define U values at building scale only. Let's say that a building is modeled in LOD 0 (lod0Footprint + measuredHeight) or in LOD 1, it can be interesting for some simul...*Created by: oliviertournaire*
I am wondering how it is possible to define U values at building scale only. Let's say that a building is modeled in LOD 0 (lod0Footprint + measuredHeight) or in LOD 1, it can be interesting for some simulation tools to define a single U value for the walls and / or the ground and / or the roof.
I can use several `Construction` instances and attach them to the building, but how can I differentiate them (except using a convention that fills the `gml:name` or `gml:description`)?
v0.8.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/118Mandatory relation between ThermalZone and ThermalBoundary?2017-11-27T09:09:22+01:00Moritz Robert LausterMandatory relation between ThermalZone and ThermalBoundary?*Created by: oliviertournaire*
I am wondering if the _boundedBy_ relation between `ThermalZone` and `ThermalBoundary` is really mandatory. The cardinality is set to `1..*`.
However, if one just want to model a building and attached the...*Created by: oliviertournaire*
I am wondering if the _boundedBy_ relation between `ThermalZone` and `ThermalBoundary` is really mandatory. The cardinality is set to `1..*`.
However, if one just want to model a building and attached the properties `isCooled` or `isHeated`, he has to define a `ThermalZone`. Sounds good. However, as long as you define a `ThermalZone`, you are obliged to also model a `ThermalBoundary`. I do not think this is really necessary.
Your opinions?
v0.8.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/67Modelling the time period of a time series2017-11-27T09:06:19+01:00Moritz Robert LausterModelling the time period of a time series*Created by: JoachimBenner*
Actually, we are using the ISO type _TM_Period_ for beginning and end of both, regular and irregular time series, In the irregular time series, each value has an absolute time position (_TP_Position_), which ...*Created by: JoachimBenner*
Actually, we are using the ISO type _TM_Period_ for beginning and end of both, regular and irregular time series, In the irregular time series, each value has an absolute time position (_TP_Position_), which means that the definition of a TemporalExtent in principle is superflous. The only use case could be to enable the validation, whether a certain value falls into the specified temporal extent. Is this really needed?
I propose to shift the the attribute _temporalExtent \* from *_TimeSeries_ to _RegularTimeSeries_.
In GML, TM_Period is encoded as _gml:TimePeriodType_. This type works very well to define **absulute** time periods, e.g.
1. January 2014 - 14. march 2014
2010 - 2012
January 2010 - march 2012
8.00 h - 12:00 h
What is **not possible** with gml:TimePeriodType is to specify a date interval without an explicit year, e.g.
January - October
1. January - 31. January
I think this is a problem, because e.g. statistical climate data do not refer to a specific year, but to specific days, years and months within a year. Actually, I do not know a good way to express this type of information in GML. Has anyone ideas?
I would like to label this issue, but I do not know how to do this!
v0.8.0