General Indicator Modeling for Decision Support based on 3D city and - - PowerPoint PPT Presentation

▶
general indicator modeling for decision support
SMART_READER_LITE
LIVE PREVIEW

General Indicator Modeling for Decision Support based on 3D city and - - PowerPoint PPT Presentation

Jun 04, 2023 502 likes •782 views

Lehrstuhl fr Geoinformatik Technische Universitt Mnchen General Indicator Modeling for Decision Support based on 3D city and landscape models using Model Driven Engineering Mostafa Elfouly, Thomas H. Kolbe Chair of Geoinformatics

slide-1
SLIDE 1

Technische Universität München Lehrstuhl für Geoinformatik

General Indicator Modeling for Decision Support based on 3D city and landscape models using Model Driven Engineering

Mostafa Elfouly, Thomas H. Kolbe Chair of Geoinformatics Technische Universität München mostafa.elfouly@tum.de 6th of June 2015

Source: shuttersock.com

slide-2
SLIDE 2

Technische Universität München Lehrstuhl für Geoinformatik

Landscape / City

(and its parts)

Measuring Landscape / City Performance

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 2

Energy Indicators Ecological Indicators Financial Indicators Social Indicators Mobility Indicators

► Evaluation is typically based on indicators,

the most relevant are called Key Performance Indicators (KPIs)

Source: shuttersock.com

slide-3
SLIDE 3

Technische Universität München Lehrstuhl für Geoinformatik

Indicators Geobase data

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 3

Energy Indicators Mobility Indicators Ecological Indicators Social Indicators Financial Indicators

CityGML Data ALKIS Data ATKIS Data INSPIRE Data BIM Data

slide-4
SLIDE 4

Technische Universität München Lehrstuhl für Geoinformatik

Observations

  • 1. Geobase data are available for entire countries and can

be used for computing indicator values

  • (however, typically additional domain specific data are required)
  • 2. All these geospatial information are based on

standardised semantic data models / ontologies

  • 3. So far, indicators are typically not formally modelled

using a standardised framework

  • 4. Furthermore, no systematic model exists yet for linking

indicators and geobase data

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 4

slide-5
SLIDE 5

Technische Universität München Lehrstuhl für Geoinformatik

Model Driven Engineering (MDE)

► … is a software engineering paradigm which began to

evolve in the 1980s

► MDE puts the “model” in the form of formal specifications

in the centre of software analysis and design

  • Application relevant structures are represented by formal data

models (e.g. using Unified Modeling Language, UML)

  • Program code is automatically derived from models

► MDE also addresses the linking of different models

  • This is called Model Weaving
  • Different models are linked by a weaving model which takes care
  • f data transformation across the models

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 5

slide-6
SLIDE 6

Technische Universität München Lehrstuhl für Geoinformatik

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 6

General Feature Model ISO 19109 CityGML Application Schema M1: Model M2: Metamodel X Y Z

This is the general schema which all geospatial data models follow (e.g. ALKIS, INSPIRE, CityGML) This is the data model of the 3D city model (here: CityGML) It defines the structures of all possible 3D city models 3D city model data, e.g. the objects

  • f the 3D city model of Berlin

M0: Instance

Geospatial Information Modelling

slide-7
SLIDE 7

Technische Universität München Lehrstuhl für Geoinformatik

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 7

General Feature Model ISO 19109 CityGML Application Schema

General Indicator Model

Energy Related KPIs Application Schema Climate Related KPIs Application Schema KPI A Building Y KPI B Building Z M1: Model M2: Metamodel X Y Z M0: Instance

Indicator Modelling

Domain specific indicators follow a General Ind. Model These are the indicator models from different application domains Concrete indicators for concrete city / landscape objects

slide-8
SLIDE 8

Technische Universität München Lehrstuhl für Geoinformatik

Requirements for Indicator Models

► Different types of indicators need to be distinguished

(i.e. numerical, textual, categorical indicators)

► Complex indicators can be composed & computed from

  • attribute values from associated city / landscape model objects
  • constants
  • mathematical expressions (unary / binary arithmetic operations)
  • n other indicators

► Indicator value aggregation (e.g. summation, average,

maximum, etc.) of other indicators

► Augment indicator values with meta information like

accuracy, lineage / source etc.

  • allowing for automatic sensitivity analysis

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 8

slide-9
SLIDE 9

Technische Universität München Lehrstuhl für Geoinformatik

ArithmeticOperation TextIndicator BinaryArithmeticOperation +

  • peration :BinaryOperation

ClassifierIndicator Indicator + name :CharacterString + value :IndicatorValueType NumericAggregationOperation +

  • peration :AggregationOperation

NumericAttribute + referenceToObjectAttribute :URI + source :CharacterString NumericConstant + source :CharacterString NumericIndicator + accuracy :Real [0..1] + unit :UnitOfMeasure + value :Real UnaryArithmeticOperation +

  • peration :UnaryOperation

«enumeration» «enumeration» «enumeration»

  • perand1
  • perand2
  • perand

1..*

  • perand

General Indicator Model (GIM) in UML

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 9

slide-10
SLIDE 10

Technische Universität München Lehrstuhl für Geoinformatik

Domain Specific Indicator Modelling

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 10 HeatDemand

+ value

Numeric Indicator

General Indicator Model Domain Indicators

Energy Planner Where do I get the data from?

Domain of the stakeholder/application specialist

slide-11
SLIDE 11

Technische Universität München Lehrstuhl für Geoinformatik

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 11

  • volume

Building District HeatDemand

+ value

Numeric Indicator DistrictHeat EnergyDemand

+ compute()

BuildingHeat EnergyDemand OCL Rule 2

General Indicator Model Domain Indicators Object Related Domain Indicators Reference Objects

«Aggregation» num Energy Planner Where do I get the data from?

Domain of the stakeholder/application specialist

* *

Domain Specific Indicator Modelling

Many of the reference

  • bjects in the context
  • f urban or landscape

indicators are spatial

  • bjects
slide-12
SLIDE 12

Technische Universität München Lehrstuhl für Geoinformatik

Linking Geospatial and Indicator Models

Building CityObject Group Building Connector District Connector

  • volume

Building District HeatDemand

+ value

Numeric Indicator CityObject DistrictHeat EnergyDemand

+ compute()

BuildingHeat EnergyDemand Solid OCL Rule 2

General Indicator Model Domain Indicators Object Related Domain Indicators Reference Objects

«Aggregation» num geometry

Geospatial Application Model (e.g. CityGML)

Energy Planner Where do I get the data from? City Modeler What can we do with

  • ur data?

Weaving Model Domain of the geodata provider Domain of the stakeholder/application specialist

* * *

OCL Rule 1 06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 12

slide-13
SLIDE 13

Technische Universität München Lehrstuhl für Geoinformatik

Rules in Object Constraint Language (OCL) - 1

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 13 Numeric Indicator

+ value

General Indicator Model Domain Indicators Object Related Domain Indicators Reference Objects

HeatDemand DistrictHeat EnergyDemand BuildingHeat EnergyDemand

+ compute()

District Building

+ volume Type ageClass

context BuildingHeatEnergyDemand inv: self.value = refBuilding.volume * 0.97 * *

refBuildingHeat refBuilding

context DistrictHeatEnergyDemand inv: self.value = Sum(refDistrict.refBuilding.refBuil dingHeatEnergyDemand.value)

refDistrict

slide-14
SLIDE 14

Technische Universität München Lehrstuhl für Geoinformatik

Rules in Object Constraint Language (OCL) - 2

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 14

Reference Objects

DistrictHeat EnergyDemand BuildingHeat EnergyDemand

+ compute()

District Building

+ volume

Weaving Classes

District Connector Building Connector

context BuildingConnector inv: refBuilding.volume = refCityGMLBuilding.volume * *

refBuilding

Object Related Domain Indicators

CityObject Building CityObject Group

Geospatial Application Model

Solid

*

refCityGMLBuilding

slide-15
SLIDE 15

Technische Universität München Lehrstuhl für Geoinformatik

Conclusions

► General Indicator Model: new framework for model based

representation and automated computation of indicators

  • Indicators for different domains are specified in a standardised and

interoperable way using UML class diagrams and OCL rules

  • Indicator models are linked to geobase data models using

model weaving

► The framework facilitates

  • systematic analysis of (also very complex) indicators and their

relationships to digital landscape and city models

  • representing and explaining key performance indicators for evaluation
  • f landscape (aspects) represented by 3D models
  • automatic derivation of programs to compute indicator values

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 15

slide-16
SLIDE 16

Technische Universität München Lehrstuhl für Geoinformatik

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 16

slide-17
SLIDE 17

Technische Universität München Lehrstuhl für Geoinformatik

Why KPIs

► A good indicator alerts you to a problem before it gets too

bad and helps you recognize what needs to be done to fix the problem (Sustainable Measures).

► In order to support automated decision-making, the

evaluation of different geodesign methods became a necessity.

► Evaluation and assessment of these models is to be

considered from the basic usages during the geodesign process by using indicators for determining, monitoring, and detecting the impact of a specified change on a given model (Steinitz 2012).

06.06.2015 17 General Indicator Modeling for Decision Support based on 3D City & Landscape Models

slide-18
SLIDE 18

Technische Universität München Lehrstuhl für Geoinformatik

KPIs Scope

► The KPI module can be applied to different domains (HED,

Transportation, Climate, etc…). It‘s not solely applied to

  • ne domain.

► This in turn drove us to the conclusion, General Indicator

Model (GIM) should be at the meta-level bringing down the ideas/concepts of meta-level (M2) down to application- schema-level (M1).

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 18

slide-19
SLIDE 19

Technische Universität München Lehrstuhl für Geoinformatik

► Questions:

1.

To which degree can Indicators be related to objects from X?

2.

To which degree can Indicators be expressed in terms of objects from X?

3.

To which degree can Indicators be computed from objects from X?

4.

Can all the required data from Y be taken from or derived from X?

5.

Do the indicators refer to the same or similar concepts that are represented in X? (e.g. X:Building Y:BuildingHeatEnergyDemand)

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 19

CityGML Application Schema 'X' Indicator Model for Domain 'Y'

?

slide-20
SLIDE 20

Technische Universität München Lehrstuhl für Geoinformatik

6.

Are the indicators and their relations of Y similarly structured than the represented concepts in X? (e.g. X:District X:Buildings Y:DistrictHeatEnergyDemand = Sum( B buildingHeatEnergyDemand))

7.

What is missing in X with respect to the required information in Y? 8. Can X be augmented by the missing information and if yes; how? (e.g. ADEs, but also: Weaving Classes) 9. Which of the available geospatial application schemas is the most suitable regarding 1-8? How to measure this?!

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 20

slide-21
SLIDE 21

Technische Universität München Lehrstuhl für Geoinformatik

Indicator Data Model linkage for different application domains

Heat Demand Building DistricHeatEnergy Demand Population NumericIndicator BuildingHeatEnergy Demand DistrictPopulation BuildingPopulation District

Object Related Domain Indicators Object Related Domain Indicators General Indicator Model Indicator Model for Domain A Indicator Model for Domain B Reference Objects Domain Indicators Domain Indicators

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 21

slide-22
SLIDE 22

Technische Universität München Lehrstuhl für Geoinformatik

Model Weaving Concept

► Reference Objects in different domains (Energy-Related

Indicator, Climate-Related Indicator, etc…) can be connected to the different geospatial application models (e.g. CityGML, INSPIRE, etc…) using the model weaving concept.

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 22

slide-23
SLIDE 23

Technische Universität München Lehrstuhl für Geoinformatik

Weaving Classes between different geospatial application models

Reference Object Classes Weaving Classes 1 Weaving Classes 2 Weaving Classes 3 CityGML INSPIRE BIM / IFC Object Related Indicators Domain A Object Related Indicators Domain B General Indicator Model

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 23

slide-24
SLIDE 24

Technische Universität München Lehrstuhl für Geoinformatik

The Structuring Information Framework using OCL for Heat Energy Demand Estimation

GIM_KnowledgeFramework::WeavingClass
  • ComponentSurfaceNumber :double
  • EnergyEffectiveAirExchange :double
  • GlassSurfaceOverallEnergyTransmittance :real
  • HeatPeriod :double
  • ReductionFactor :double
  • RedutionNightWeekend :double
  • SpecificHeatOutput :double
  • UValueOfComponent :double
  • WindowsSolarIrradiationReductionFactor :real
refObj context WeavingClass inv HED_Mapping: refObj.ReductionNightWeekend = self.ReductionNightWeekend refObj.EnergyEffectiveAirExchange = self.EnergyEffectiveAirExchange refObj.HeatPeriod = self.HeatPeriod refObj.ReductionFactor = self.ReductionFactor refObj.SpecificHeatOutput = self.SpecificHeatOutput refObj.UValueOfComponent = self.UValueOfComponent refObj.refBoundarySurface.refWindow.GlassSurfaceOverallEnergyTransmittance = self.GlassSurfaceOverallEnergyTransmittance refObj.refBoundarySurface.refWindow.WindowsSolarIrradiationReductionFactor = self.WindowsSolarIrradiationReductionFactor refObj.BuildingVolume = refCityGML.measuredHeight * refCityGML.boundedBy.GroundSurface.Area refObj.refBoundarySurface.refWindow.TotalWindowSurface = refCityGML.boundedBy.WallSurface.opening.Window.Area refObj.EnergyReferenceArea = 0.75 * refCityGML.storeysAboveGround * refCityGML.boundedBy.GroundSurface.Area HED::Building
  • BuildingVolume :real
  • ComponentSurfaceNumber :real
  • EnergyEffectiveAirExchange :double
  • EnergyReferenceArea :real
  • HeatPeriod :real
  • ReductionFactor :real
  • ReductionNightWeekend :double
  • SpecificHeatOutput :real
  • UValueOfComponent :real
«FeatureType» AbstractBuilding + class :Code [0..1] + function :Code [0..*] + measuredHeight :Length [0..1] + roofType :Code [0..1] + storeyHeightsAboveGround :MeasureOrNilReasonList [0..1] + storeyHeightsBelowGround :MeasureOrNilReasonList [0..1] + storeysAboveGround :Integer [0..1] + storeysBelowGround :Integer [0..1] + usage :Code [0..*] + yearOfConstruction :Date [0..1] + yearOfDemolition :Date [0..1] «FeatureType» BuildingInstallation + class :Code [0..1] + function :Code [0..*] + usage :Code [0..*] «FeatureType» IntBuildingInstallation + class :Code [0..1] + function :Code [0..*] + usage :Code [0..*] «FeatureType» BuildingFurniture + class :Code [0..1] + function :Code [0..*] + usage :Code [0..*] «FeatureType» Room + class :Code [0..1] + function :Code [0..*] + usage :Code [0..*] «Feature... BuildingPart «Featur... Building «FeatureTy... AbstractOpening «FeatureTy... Window «FeatureTy... Door «FeatureType» Core::Address «FeatureType» AbstractBoundarySurface «FeatureTy... RoofSurface «FeatureTy... WallSurface «FeatureTy... GroundSurface «FeatureTy... ClosureSurface «FeatureTy... CeilingSurface «FeatureType» InteriorWallSurface «FeatureTy... FloorSurface «FeatureType» OuterFloorSurface «FeatureType» OuterCeilingSurface «type» Geometry root::GM_Object {root} GM_Primitive «type» Geometric primitive::GM_Solid GM_MultiPrimitive «type» Geometric aggregates::GM_MultiCurve GM_MultiPrimitive «type» Geometric aggregates::GM_MultiSurface «Type» Core::ImplicitGeometry «FeatureType» Core::AbstractSite VersionableAbstractFeature «FeatureType» Core::AbstractCityObject * +lod0RoofEdge «Property» 0..1 * +lod1TerrainIntersection «Property» 0..1 * +lod3MultiSurface «Property» 0..1 * +lod1MultiSurface «Property» 0..1 * +lod4MultiSurface «Property» 0..1 * +lod3MultiSurface «Property» 0..1 * +lod4MultiSurface «Property» 0..1 * +lod2MultiSurface «Property» 0..1 * +lod2MultiSurface «Property» 0..1 * +lod0FootPrint «Property» 0..1 * +lod3MultiSurface «Property» 0..1 * +lod4TerrainIntersection «Property» 0..1 * +lod4MultiCurve «Property» 0..1 * +lod2MultiCurve «Property» 0..1 * +lod3TerrainIntersection «Property» 0..1 * +lod2TerrainIntersection «Property» 0..1 * +lod4MultiSurface «Property» 0..1 * +lod4ImplicitRepresentation «Property» 0..1 * +lod4MultiSurface «Property» 0..1 * +lod3Solid «Property» 0..1 * +lod3ImplicitRepresentation «Property» 0..1 * +lod2ImplicitRepresentation «Property» 0..1 * +lod4ImplicitRepresentation «Property» 0..1 * +lod3ImplicitRepresentation «Property» 0..1 * +lod4ImplicitRepresentation «Property» 0..1 * +lod4ImplicitRepresentation «Property» 0..1 +relativeGMLGeometry «Property» 0..1 * +boundedBy «Property» * * * +lod3MultiCurve «Property» * +address «Property» * * +address «Property» * +boundedBy «Property» * 0..1 +opening «Property» * 0..2 +interiorFurniture «Property» * 0..1 +boundedBy «Property» * * +boundedBy «Property» * * +consistsOfBuildingPart «Property» * * +outerBuildingInstallation «Property» * * +interiorBuildingInstallation «Property» * * +interiorRoom «Property» * * +roomInstallation «Property» * 0..1 * +lod2Geometry «Property» 0..1 * +lod2Solid «Property» 0..1 * +lod1Solid «Property» 0..1 * +lod4Solid «Property» 0..1 * +lod4Solid «Property» 0..1 * +lod4Geometry «Property» 0..1 * +lod4Geometry «Property» 0..1 * +lod3Geometry «Property» 0..1 * +lod4Geometry «Property» 0..1 context BuildingHeatEnergyDemand inv HeatDemand: self.value= self.HeatLoss - self.HeatGain GIM_KnowledgeFramework:: District GIM_KnowledgeFramework:: BuildingHeatEnergyDemand
  • FreeHeat :Real
  • HeatGain :Real
  • HeatLoss :Real
«Indicator» GIM_KnowledgeFramework:: NumericIndicator + name :CharacterString + unit :Real + value :Real refBuilding buildingHeat context BuildingHeatEnergyDemand inv HeatLoss: self.HeatLoss= ( refBuilding.ReductionNightWeekend * ( (0.34 * refBuilding.EnergyEffectiveAirExchange * refBuilding.BuildingVolume * Building.Theta) + ( Sum( refBuilding.WindowsSolarIrradiationReductionFactor * refBuilding.ComponentSurfaceNumber * refBuilding.UValue ) . Building.Theta) ) ) context BuildingHeatEnergyDemand inv HeatGain: self.HeatGain= ( 1 - ( 0.3 * self.FreeHeat / self.HeatLoss ) ) context BuildingHeatEnergyDemand inv FreeHeat: self.FreeHeat= ( 0.024 * refBuilding.SpecificHeatOutput * refBuilding.HeatingPeriod * refBuilding.EnergyReferenceArea ) * ( ( refBuilding.GlassSurfaceOverallEnergyTransmittance * refBuilding.WindowsSolarIrradiationReductionFactor [0.36 OR 0.48] ) * ( Sum( refBuilding.TotalWindowSurface * 240 ) ) ) GIM_KnowledgeFramework:: DistrictHeatEnergyDemand
  • value :Real
context DistrictHeatEnergyDemand inv: value = Sum(refDistrict.refBuilding.buildingHeat.value) refDistrict refBuilding BoundarySurface Window
  • GlassSurfaceOverallEnergyTransmittance :Real
  • TotalWindowSurface :Real
  • WindowsSolarIrradiationReductionFactor :Real
refBoundarySurface refWindow «Indicator» HeatDemand «NumericIndicator» HeatEnergyDemand * * * * 0..2 *

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 24

slide-25
SLIDE 25

Technische Universität München Lehrstuhl für Geoinformatik

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 25

Object-Related Domain Indicators Domain Indicators General Indicator Model

«FeatureType» «FeatureType» «FeatureType» «FeatureType» «FeatureType» «Feature... «Featur... «FeatureTy... «FeatureTy... «FeatureTy... «FeatureType» «FeatureType» «FeatureTy... «FeatureTy... «FeatureTy... «FeatureTy... «FeatureTy... «FeatureType» «FeatureTy... «FeatureType» «FeatureType» «type» «type» «type» «type» «Type» «FeatureType» «FeatureType» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» context BuildingHeatEnergyDemand inv HeatDemand: self.value= self.HeatLoss - self.HeatGain GIM_KnowledgeFramework:: BuildingHeatEnergyDemand

  • FreeHeat :Real
  • HeatGain :Real
  • HeatLoss :Real

«Indicator» GIM_KnowledgeFramework:: NumericIndicator + name :CharacterString + unit :Real + value :Real buildingHeat context BuildingHeatEnergyDemand inv HeatLoss: self.HeatLoss= ( refBuilding.ReductionNightWeekend * ( (0.34 * refBuilding.EnergyEffectiveAirExchange * refBuilding.BuildingVolume * Building.Theta) + ( Sum( refBuilding.WindowsSolarIrradiationReductionFactor * refBuilding.ComponentSurfaceNumber * refBuilding.UValue ) . Building.Theta) ) ) context BuildingHeatEnergyDemand inv HeatGain: self.HeatGain= ( 1 - ( 0.3 * self.FreeHeat / self.HeatLoss ) ) context BuildingHeatEnergyDemand inv FreeHeat: self.FreeHeat= ( 0.024 * refBuilding.SpecificHeatOutput * refBuilding.HeatingPeriod * refBuilding.EnergyReferenceArea ) * ( ( refBuilding.GlassSurfaceOverallEnergyTransmittance * refBuilding.WindowsSolarIrradiationReductionFactor [0.36 OR 0.48] ) * ( Sum( refBuilding.TotalWindowSurface * 240 ) ) ) GIM_KnowledgeFramework:: DistrictHeatEnergyDemand

  • value :Real

context DistrictHeatEnergyDemand inv: value = Sum(refDistrict.refBuilding.buildingHeat.value) refDistrict «Indicator» HeatDemand *

slide-26
SLIDE 26

Technische Universität München Lehrstuhl für Geoinformatik

06.06.2015 General Indicator Modeling for Decision Support based on 3D City & Landscape Models 26

GIM_KnowledgeFramework::WeavingClass

  • ComponentSurfaceNumber :double
  • EnergyEffectiveAirExchange :double
  • GlassSurfaceOverallEnergyTransmittance :real
  • HeatPeriod :double
  • ReductionFactor :double
  • RedutionNightWeekend :double
  • SpecificHeatOutput :double
  • UValueOfComponent :double
  • WindowsSolarIrradiationReductionFactor :real

refObj context WeavingClass inv HED_Mapping: refObj.ReductionNightWeekend = self.ReductionNightWeekend refObj.EnergyEffectiveAirExchange = self.EnergyEffectiveAirExchange refObj.HeatPeriod = self.HeatPeriod refObj.ReductionFactor = self.ReductionFactor refObj.SpecificHeatOutput = self.SpecificHeatOutput refObj.UValueOfComponent = self.UValueOfComponent refObj.refBoundarySurface.refWindow.GlassSurfaceOverallEnergyTransmittance = self.GlassSurfaceOverallEnergyTransmittance refObj.refBoundarySurface.refWindow.WindowsSolarIrradiationReductionFactor = self.WindowsSolarIrradiationReductionFactor refObj.BuildingVolume = refCityGML.measuredHeight * refCityGML.boundedBy.GroundSurface.Area refObj.refBoundarySurface.refWindow.TotalWindowSurface = refCityGML.boundedBy.WallSurface.opening.Window.Area refObj.EnergyReferenceArea = 0.75 * refCityGML.storeysAboveGround * refCityGML.boundedBy.GroundSurface.Area HED::Building

  • BuildingVolume :real
  • ComponentSurfaceNumber :real
  • EnergyEffectiveAirExchange :double
  • EnergyReferenceArea :real
  • HeatPeriod :real
  • ReductionFactor :real
  • ReductionNightWeekend :double
  • SpecificHeatOutput :real
  • UValueOfComponent :real

«FeatureType» «FeatureType» «FeatureType» «FeatureType» «FeatureType» «Feature... «Featur... «FeatureTy... «FeatureTy... «FeatureTy... «FeatureType» «FeatureType» «FeatureTy... «FeatureTy... «FeatureTy... «FeatureTy... «FeatureTy... «FeatureType» «FeatureTy... «FeatureType» «FeatureType» «type» «type» «type» «type» «Type» «FeatureType» «FeatureType» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» «Property» GIM_KnowledgeFramework:: District «Indicator» refBuilding refBuilding BoundarySurface Window

  • GlassSurfaceOverallEnergyTransmittance :Real
  • TotalWindowSurface :Real
  • WindowsSolarIrradiationReductionFactor :Real

refBoundarySurface refWindow «Indicator» «NumericIndicator» * * * * 0..2

Weaving Model Reference Objects