Skip to content

GitLab

C
citygml-energy
Closed
Opened by Moritz Robert Lauster@mlauster
Report abuse New issue

Restrict Construction / ConstructionOrientation to relevant ADE features

Created by: JoachimBenner

In ADE version 0.6.0, we defined the new classes Construction and ConstructionOrientation, and simultaneously introduced the extension attribute construction of _CityObject. This allows that every CityGML feature of the base standard as well as of the Energy ADE can refer to layered material information.

This is problematic due to two different reasons:

  • It is not the task of the Energy ADE to define general extensions of the base standard, especially in cases where a corresponding change request for CityGML 3.0 already exists.
  • Concerning the specific features of the EnergyADE, there are many of them where the construction relation does not make sense (e.g. ThermalZone, UsageZone, ..) or where the specification of material information is even forbidden (ThermalBoundary).

I therefore propose to delete the general construction relation from _CityObject to Construction / ConstructionOrientation, and to introduce specific relations for those classes of the base standard and the extension where the concept is really needed: _BoundarySurface and ThermalComponent.

For simplifying the schema, I furthermore propose to introduce a new, abstract super class AbstractConstruction of Construction and ConstructionOrientation, which can be used as relation target.

Linked issues