citygml-energy issueshttps://git.rwth-aachen.de/energyade/citygml-energy/-/issues2015-05-07T14:11:52+02:00https://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/27Tag version to v0.5.02015-03-12T20:27:58+01:00Moritz Robert LausterTag version to v0.5.0*Created by: oliviertournaire*
When everyone will agree, tag version to v0.5.0.
The version in the UML model will also have to be upgraded.
*Created by: oliviertournaire*
When everyone will agree, tag version to v0.5.0.
The version in the UML model will also have to be upgraded.
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/2Update README.md2015-03-12T13:53:17+01:00Moritz Robert LausterUpdate README.md*Created by: oliviertournaire*
The current README.md file is incomplete
- Add authors
- Add description
*Created by: oliviertournaire*
The current README.md file is incomplete
- Add authors
- Add description
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/18Fix association from ScheduleLoD2 to DailySchedule2015-03-03T00:52:02+01:00Moritz Robert LausterFix association from ScheduleLoD2 to DailySchedule*Created by: oliviertournaire*
See image below
![attendeeviewerimage000](https://cloud.githubusercontent.com/assets/1990302/6437941/b23538ec-c0c4-11e4-88c7-c3c608ec9afc.png)
*Created by: oliviertournaire*
See image below
![attendeeviewerimage000](https://cloud.githubusercontent.com/assets/1990302/6437941/b23538ec-c0c4-11e4-88c7-c3c608ec9afc.png)
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/14Cardinalities missing for Construction and ConstructionOrientation2015-03-03T00:51:28+01:00Moritz Robert LausterCardinalities missing for Construction and ConstructionOrientation*Created by: oliviertournaire*
*Created by: oliviertournaire*
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/5Glazing featureType bad inheritance2015-03-03T00:51:28+01:00Moritz Robert LausterGlazing featureType bad inheritance*Created by: oliviertournaire*
From Romain Nouvel:
"The featureType Glazing (which may have several glazes and gas gapes) is actually not a "Material" but a 'LayerComponent'. Then, it should not inherit from 'AbstractMaterial' but from ...*Created by: oliviertournaire*
From Romain Nouvel:
"The featureType Glazing (which may have several glazes and gas gapes) is actually not a "Material" but a 'LayerComponent'. Then, it should not inherit from 'AbstractMaterial' but from 'LayerComponent'. Following that, the 'OpaqueMaterial' object should be renamed as 'SolidMaterial' (with the same parameters, at less for the first release)."
v0.4.3https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/17HouseholdType Codelist is not used2015-03-03T00:51:27+01:00Moritz Robert LausterHouseholdType Codelist is not used*Created by: oliviertournaire*
What to do:
- Remove the Codelist
- Use it in `featureType Household`
*Created by: oliviertournaire*
What to do:
- Remove the Codelist
- Use it in `featureType Household`
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/19Glazing should derive from AbstractMaterial and not LayerComponent2015-03-02T22:50:21+01:00Moritz Robert LausterGlazing should derive from AbstractMaterial and not LayerComponent*Created by: oliviertournaire*
*Created by: oliviertournaire*
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/10Usage of temporal data types2015-03-02T22:48:47+01:00Moritz Robert LausterUsage of temporal data types*Created by: oliviertournaire*
[Thanks to Joachim Benner for reporting this issue]
The UML model uses a lot of types for time instances (TM_ClockTime, TimePositionType) and time periods (TimePeriod, TimeIntervalLengthType). Some of them...*Created by: oliviertournaire*
[Thanks to Joachim Benner for reporting this issue]
The UML model uses a lot of types for time instances (TM_ClockTime, TimePositionType) and time periods (TimePeriod, TimeIntervalLengthType). Some of them may not be recognized by ShapeChange. We thus have to ensure that in the generated XSD schema, attributes using these types are correctly defined. The while model has to be checked.
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/9Missing attributes type2015-03-02T22:48:26+01:00Moritz Robert LausterMissing attributes type*Created by: oliviertournaire*
[Thanks to Joachim Benner for reporting this issue]
Some attributes have no type. This is due to a bad specification in the UML model. Can be fixed by correcting types in the UML model and / or by setting ...*Created by: oliviertournaire*
[Thanks to Joachim Benner for reporting this issue]
Some attributes have no type. This is due to a bad specification in the UML model. Can be fixed by correcting types in the UML model and / or by setting proper conversion rules in ShapeChange configuration files.
Here is a list (might not be exhaustive) of the types that have to be changed:
- MeasureType --> Measure
- LengthType --> Length
- AreaType --> Area
- VolumeType --> Volume
- boolean --> Boolean
- Int --> Integer
- ScaleType --> Scale
- UomIdentifier --> Measure
- AngleType --> Angle
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/16Use correct CityGML class names2015-03-02T22:46:03+01:00Moritz Robert LausterUse correct CityGML class names*Created by: oliviertournaire*
Some classes do not have a correct name. For instance `AbstractBuilding` should be `_AbstractBuilding`.
The easiest way is to change names of classes used in the model to their correct version.
*Created by: oliviertournaire*
Some classes do not have a correct name. For instance `AbstractBuilding` should be `_AbstractBuilding`.
The easiest way is to change names of classes used in the model to their correct version.
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/8The codeSpace attribute in code lists is 1.02015-03-02T22:44:22+01:00Moritz Robert LausterThe codeSpace attribute in code lists is 1.0*Created by: 900k*
The codelists still refere to codeSpace 1.0. Please ensure that the current version is injected in the codelists.
*Created by: 900k*
The codelists still refere to codeSpace 1.0. Please ensure that the current version is injected in the codelists.
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/11ADEElement _BoundarySurface2015-03-02T22:28:19+01:00Moritz Robert LausterADEElement _BoundarySurface*Created by: oliviertournaire*
In the current model, an abstract class `_BoudarySurface` with the stereotype `ADEElement` exists. It derives from `Building:AbstractBoundarySurface`.
Some clarification are required:
1. If we want to cre...*Created by: oliviertournaire*
In the current model, an abstract class `_BoudarySurface` with the stereotype `ADEElement` exists. It derives from `Building:AbstractBoundarySurface`.
Some clarification are required:
1. If we want to create a class (i.e. a type) in the ADE which derives from `Building:AbstractBoundarySurface`, it should be done in another way (see image below)
2. The name of the derived class, if it has the stereotype `ADEElement` must have the **same name as its base class** (i.e. `AbstractBoundarySurface`)
![ade1](https://cloud.githubusercontent.com/assets/1990302/6414473/01d57a3a-be98-11e4-9823-8c4382c6d9b0.png)
0.5.0https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/12ADEElement _Opening2015-03-02T22:27:59+01:00Moritz Robert LausterADEElement _Opening*Created by: oliviertournaire*
In the current model, an abstract class `_Opening` with the stereotype `ADEElement` exists. It derives from `Building:AbstractOpening`.
Some clarification are required:
1. If we want to create a class (i....*Created by: oliviertournaire*
In the current model, an abstract class `_Opening` with the stereotype `ADEElement` exists. It derives from `Building:AbstractOpening`.
Some clarification are required:
1. If we want to create a class (i.e. a type) in the ADE which derives from `Building:AbstractOpening`, it should be done in another way (see image below)
2. The name of the derived class, if it has the stereotype `ADEElement` must have the **same name as its base class** (i.e. `AbstractOpening`)
![ade1](https://cloud.githubusercontent.com/assets/1990302/6414473/01d57a3a-be98-11e4-9823-8c4382c6d9b0.png)
0.5.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/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/1Add a license file2015-02-18T23:20:08+01:00Moritz Robert LausterAdd a license file*Created by: oliviertournaire*
Is it necessary? CityGML does not provide any license file
*Created by: oliviertournaire*
Is it necessary? CityGML does not provide any license file
v0.4.3https://git.rwth-aachen.de/energyade/citygml-energy/-/issues/7Check cardinalities2015-02-05T13:40:34+01:00Moritz Robert LausterCheck cardinalities*Created by: oliviertournaire*
It seems that cardinalities on relationships are not well handled when converting from UML to XSD. They thus need to be checked carefully.
*Created by: oliviertournaire*
It seems that cardinalities on relationships are not well handled when converting from UML to XSD. They thus need to be checked carefully.
v0.4.3