citygml-energy issueshttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues2015-11-10T22:48:51+01:00https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/35Labels by creating issues2015-11-10T22:48:51+01:00Moritz Robert LausterLabels by creating issues*Created by: bahujean*
-- label bug --
Be able to insert directly a label by creating an issue would be very useful.
*Created by: bahujean*
-- label bug --
Be able to insert directly a label by creating an issue would be very useful.
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/42new Class RefurbishmentMeasures2016-06-29T22:47:25+02:00Moritz Robert Lausternew Class RefurbishmentMeasures*Created by: RomainNouvel*
In the Energy ADE version 0.5, information concerning possible refurbishment measures are integrated inside the _AbstractBuilding Class as two attributes: yearOfRefurbishment[Year] and refurbishmentClass[Chara...*Created by: RomainNouvel*
In the Energy ADE version 0.5, information concerning possible refurbishment measures are integrated inside the _AbstractBuilding Class as two attributes: yearOfRefurbishment[Year] and refurbishmentClass[CharacterString].
The present structure does not allow to have partial RefurbishmentMeasures (e.g. only for a wall, a window or a energy system), nor several RefurbishmentMeasures for one building. Moreover, yearOfRefurbishment might be too precise, and refurbishmentClass as CharacterString is not usable in software/libraries
PROPOSITIONS:
- Create a FeatureType RefurbishmentMeasures containing the attributes DateOfRefurbishment[Date] and LevelOfRefurbishment[CodeList], which could be associate with a Cardinality [1 , 0..*] to _AbstractBuilding, _BoundarySurface, _Opening and EnergyConversionSystem for instance (any CityObject?).
- The attribute LevelOfRefurbishment could be a hierarchical multi-lingual CodeList (use Re3gistry developed by jrc), referring for instance to the Refurbishment variants "Standard" and "Advanced" defined in the European Projekt Tabula, or to any other local refurbishment variant, provided that it is defined somewehere (in a library or a document, whose reference should be indicated with the LevelOfRefurbishment)
v0.7.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/38Optical Properties2016-01-14T13:55:11+01:00Moritz Robert LausterOptical Properties*Created by: RomainNouvel*
Optical properties (reflectance, transmittance, emittance, absorptance etc...) are presently spread off in different objects of the Material Module (Construction and Glazing), with different level of details (...*Created by: RomainNouvel*
Optical properties (reflectance, transmittance, emittance, absorptance etc...) are presently spread off in different objects of the Material Module (Construction and Glazing), with different level of details (distinction hemispherical/normalIncidence in Glazing).
For more readibility and flexibility, it would be interesting to pick out all optical properties and gather them in a single object "OpticalProperties", possibly assigned to Construction or LayerComponent.
In this case, the specification of a "GlazingObject", hybrid object between a layer and material, would not be required anymore. Instead, we could only distinguish Materials between Gas and SolidMaterial. The transparence characteristic would come only from the OpticalProperties...
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/31Lighting in Building2016-01-14T13:55:43+01:00Moritz Robert LausterLighting in Building*Created by: RomainNouvel*
Up to now, the building model do not integrate specific attributes for lighting.
- Luminance Threshold (Lux) could be included in UsageZone for instance...
- LightingFacilities/Systems could be specificied suc...*Created by: RomainNouvel*
Up to now, the building model do not integrate specific attributes for lighting.
- Luminance Threshold (Lux) could be included in UsageZone for instance...
- LightingFacilities/Systems could be specificied such as DHWFacilities...
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/33Rename the "Occupancy" featureType2015-11-27T11:41:18+01:00Moritz Robert LausterRename the "Occupancy" featureType*Created by: bahujean*
-- Label Building Occupant --
**Rename the "Occupancy" featureType "Occupants"** in order to avoid misunderstanding regarding the multiplicity indices with BuildingUnit or UsageZone.
*Created by: bahujean*
-- Label Building Occupant --
**Rename the "Occupancy" featureType "Occupants"** in order to avoid misunderstanding regarding the multiplicity indices with BuildingUnit or UsageZone.
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/32Internal Gains management2015-11-27T11:41:03+01:00Moritz Robert LausterInternal Gains management*Created by: bahujean*
**-- Label Building occupants --**
**1-** Up to now, internal gains are attributes in the featureTypes:
- as "internGains" within the "occupancy" featureType
- as "heatLosses" within the "electricalAppliances" f...*Created by: bahujean*
**-- Label Building occupants --**
**1-** Up to now, internal gains are attributes in the featureTypes:
- as "internGains" within the "occupancy" featureType
- as "heatLosses" within the "electricalAppliances" featureType
They design the same effect and are at the same level. That's why it could be relevant to **rename both attributes "heatDissipation"**.
**2-** It could be also relevant to **insert an "internalGains" attribute within the "UsageZone" featureType**. User could then choose if he wants to directly use a simplified attribute or provide more detailed calculation for internal Gains.
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/34Hierarchy and changes within the "OwnershipType" codeList2015-11-27T11:41:35+01:00Moritz Robert LausterHierarchy and changes within the "OwnershipType" codeList*Created by: bahujean*
- Label codeList -
1- **Rename "Governement" within the "OwnershipType" codeList into "Public"**
2- **Is it possible to insert hierarchical relations within a codeList?**
It could indeed then be possible to in...*Created by: bahujean*
- Label codeList -
1- **Rename "Governement" within the "OwnershipType" codeList into "Public"**
2- **Is it possible to insert hierarchical relations within a codeList?**
It could indeed then be possible to insert more detailed code List and insert hierarchy between them, such as in the inspire codeLists:
(http://inspire.ec.europa.eu/codelist/CurrentUseValue/)
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/53Identify BuildingUnit also with address(parts)?2015-11-27T11:43:50+01:00Moritz Robert LausterIdentify BuildingUnit also with address(parts)?*Created by: gioagu*
Hi,
I am thinking whether and how a BuildingUnit (e.g. a flat) could be futher identified with the useful parts of the address after the house number.
Example: "Hauptstraße 10/A/15"
Generally, I'd use only Haupts...*Created by: gioagu*
Hi,
I am thinking whether and how a BuildingUnit (e.g. a flat) could be futher identified with the useful parts of the address after the house number.
Example: "Hauptstraße 10/A/15"
Generally, I'd use only Hauptstraße 10/A as address, as the remaining parts refers only to the door number. (In Austria it can be even more complex, but let's keep it simple).
Maybe we could add an attribute to BuildingUnit which contains this remaining part, while the normal address is associated with the whole building (as usual)?
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/52More solar-related attributes for SurfaceComponent?2016-01-14T13:52:50+01:00Moritz Robert LausterMore solar-related attributes for SurfaceComponent?*Created by: gioagu*
Hi!
As of now, there is only a boolean isSunExposed attribute to the SurfaceComponent class.
I think it would be useful to be able to store (for example):
direct_solar_irradiance: _Timeseries
diffuse_solar_irradi...*Created by: gioagu*
Hi!
As of now, there is only a boolean isSunExposed attribute to the SurfaceComponent class.
I think it would be useful to be able to store (for example):
direct_solar_irradiance: _Timeseries
diffuse_solar_irradiance: _Timeseries
global_solar_irradiance: _Timeseries
insolation_time:_Timeseries (e.g. sun hours per day, per month, per year, etc.)
shadowing_ratio: _Timeseries (for example due to adjacent buildings)
This could for example speed up simulations where these parameters are computed only once and then simply reused whenever necessary.
What do you think?
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/40new sample file2015-05-07T14:11:52+02:00Moritz Robert Lausternew sample file*Created by: PRemmen*
I created a first CityGML file for our internal workflow. What we basically do is to create archetype building with help of statistical data. The input is very generall (in this case: Type of Building: Residantial,...*Created by: PRemmen*
I created a first CityGML file for our internal workflow. What we basically do is to create archetype building with help of statistical data. The input is very generall (in this case: Type of Building: Residantial, year of construction: 1988, number of storys: 1, height of storys: 3 and net floor area: 200) According to this data typical wall construction for this type of building are selected. I saved the whole data set using following ADE Energy Classes:
- _AbstractBuilding
- ThermalZone
- ThermalBoundarySurface
- Construction including Glazing and OpaqueMaterial
Don't know if that sample file helps, but since I had to create it anyway I will provide it to you. Any comments are welcome
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/23Expand BuildingType Codelist2016-07-01T10:21:30+02:00Moritz Robert LausterExpand BuildingType Codelist*Created by: oliviertournaire*
[Reported by Piergiorgio Cipriano]
In general, an alignment with INSPIRE codelists is suggested.
BuildingType: at the moment the codelist (BuildingType.xml) is only containing 3 possible values:
- Singl...*Created by: oliviertournaire*
[Reported by Piergiorgio Cipriano]
In general, an alignment with INSPIRE codelists is suggested.
BuildingType: at the moment the codelist (BuildingType.xml) is only containing 3 possible values:
- SingleFamilyHouse
- MultiFamilyHouse
- ApartmentBlock
We suggest to expand the codelist with the following:
- SFH (Single Family House)
- MFH (Multi Family House)
- TH (Terraced House)
- AB (Apartment Block)
- HLB (Historical large building)
- HSB (Historical small building)
The latter are crucial to estimate energy needs in historical centres (e.g. Ferrara, in Sunshine project).
v0.7.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/39g-value and conductivity for Windows2016-01-14T13:54:56+01:00Moritz Robert Lausterg-value and conductivity for Windows*Created by: PRemmen*
A widley used property for the calculation of transmitted solar gains through a window is the g-value. Right now it seems that it is missing in the schema, correct me if I'm wrong.
The g-value is comparable to the...*Created by: PRemmen*
A widley used property for the calculation of transmitted solar gains through a window is the g-value. Right now it seems that it is missing in the schema, correct me if I'm wrong.
The g-value is comparable to the uValue, since it is typically calculated for the whole window and not single panes.
Considering that, I would suggest to implement the gValue in _Opening, but I'm not a expert in UML Design.
Also it seems that thermal properties like conductivity, density etc. can't be set for glazing, again: correct me if I'm wrong :)
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/37Add a ThermalWindow type for LoD{0,1,2}2016-01-14T13:55:19+01:00Moritz Robert LausterAdd a ThermalWindow type for LoD{0,1,2}*Created by: oliviertournaire*
In CityGML standard, the class _Opening can only be used starting from LoD3. The Energy ADE extends this class with some attributes. As energy simulation requires to have building windows, it is necessary ...*Created by: oliviertournaire*
In CityGML standard, the class _Opening can only be used starting from LoD3. The Energy ADE extends this class with some attributes. As energy simulation requires to have building windows, it is necessary to create a new type. How to do this should now be discussed.
v0.6.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/36Update README.md2016-01-14T13:55:34+01:00Moritz Robert LausterUpdate README.md*Created by: oliviertournaire*
Update REAME.md:
- Add a section "How to contribute?"
- Add some links to the main SIG3D webpage
- Add links to workshops meetings
- Add an "Announcement" section
*Created by: oliviertournaire*
Update REAME.md:
- Add a section "How to contribute?"
- Add some links to the main SIG3D webpage
- Add links to workshops meetings
- Add an "Announcement" section
https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/13Why an ADEElement _CityObject is defined2015-03-02T22:21:09+01:00Moritz Robert LausterWhy an ADEElement _CityObject is defined*Created by: oliviertournaire*
I was wondering why we have defined a `_CityObject ADEElement` in the UML model. Why do not we use directly the `core:AbstractCityObject`? Can you explain?
Note that is issue is related to issues #11 and ...*Created by: oliviertournaire*
I was wondering why we have defined a `_CityObject ADEElement` in the UML model. Why do not we use directly the `core:AbstractCityObject`? Can you explain?
Note that is issue is related to issues #11 and #12
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/22TimeValuesProperties incorrect uom attribute type2015-03-03T00:14:53+01:00Moritz Robert LausterTimeValuesProperties incorrect uom attribute type*Created by: oliviertournaire*
Attribute should be `MeasureType` instead of `Measure`
*Created by: oliviertournaire*
Attribute should be `MeasureType` instead of `Measure`
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/24Vacant in HouseholdType Codelist2015-11-27T11:46:14+01:00Moritz Robert LausterVacant in HouseholdType Codelist*Created by: oliviertournaire*
[Reported by Piergiorgio Cipriano]
The term “Vacant” is already included in the ResidenceType codelist.
We propose to remove "Vacant" from this list.
Household is "A unit for the population census, every ...*Created by: oliviertournaire*
[Reported by Piergiorgio Cipriano]
The term “Vacant” is already included in the ResidenceType codelist.
We propose to remove "Vacant" from this list.
Household is "A unit for the population census, every individual or group of individuals residing in the same dwelling"; therefore this codelist should not contain values referring to the status of the dwelling.
v0.6.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/21Repair Materials ADE2015-03-02T22:23:57+01:00Moritz Robert LausterRepair Materials ADE*Created by: 900k*
Hi Olivier,
could you please change back some modifications of the Materials ADE which Romain introduced lately? Currently, the "Glazing" is a subclass of "LayerComponent", but it should be a subclass of "AbstractMat...*Created by: 900k*
Hi Olivier,
could you please change back some modifications of the Materials ADE which Romain introduced lately? Currently, the "Glazing" is a subclass of "LayerComponent", but it should be a subclass of "AbstractMaterial". Additionally, please change the class name of "SolidMaterial" back to "OpaqueMaterial".
Thank you very much!
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/20Fix relation between _BoundarySurface and _SolarEnergySystem2015-03-03T12:50:51+01:00Moritz Robert LausterFix relation between _BoundarySurface and _SolarEnergySystem*Created by: oliviertournaire*
`_SolarEnergySystem` should be linked to `Building:_BoundarySurface`
![attendeeviewerimage001](https://cloud.githubusercontent.com/assets/1990302/6438308/2bf2fbbc-c0c8-11e4-95b3-6c1c2e8d1878.png)
*Created by: oliviertournaire*
`_SolarEnergySystem` should be linked to `Building:_BoundarySurface`
![attendeeviewerimage001](https://cloud.githubusercontent.com/assets/1990302/6438308/2bf2fbbc-c0c8-11e4-95b3-6c1c2e8d1878.png)
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/30Missing association between ThermalZone and UsageZone2015-11-24T11:49:38+01:00Moritz Robert LausterMissing association between ThermalZone and UsageZone*Created by: 900k*
There was once an association from ThermalZone to UsageZone [0..\* -> 0..*]. The role name was "relatesTo". It must have gone lost during the separation of the modules.
*Created by: 900k*
There was once an association from ThermalZone to UsageZone [0..\* -> 0..*]. The role name was "relatesTo". It must have gone lost during the separation of the modules.
v0.6.0