<p>The primary objective of FWE ADE is to extend the existing CityGML data model, to store FWE and its nexus related properties for developing a digital twin of the study area. By doing so, not only the status quo can be mapped, analysed and visualised, but future analytical scenarios can also be built, simulated and visualised. For stakeholders, such an integrated data model and visualisation tools can further support them to sketch sustainable urban development policies which is a need of the time.
<p>The primary objective of FWE ADE is to extend the existing CityGML data model, to store FWE and its nexus related properties for developing a digital twin of the study area. By doing so, not only the status quo can be mapped, analysed and visualised, but future analytical scenarios can also be built, simulated and visualised. For stakeholders, such an integrated data model and visualisation tools can further support them to sketch sustainable urban development policies which is a need of the time.
Keeping in mind the challenges of data availability and its granularity, FWE ADE introduces four thematic modules: FWEBuilding, FWELandUse, FWEArea and FWESystem.</p>
Keeping in mind the challenges of data availability and its granularity, FWE ADE introduces four thematic modules: FWEBuilding, FWELandUse, FWEArea and FWESystem.</p>
<p>
<p>
<imgsrc="FWEADE.PNG">
<imgsrc="FWEADE.png">
</p>
</p>
<p>While FWEBuilding and FWE LandUse extends the CityGML core thematic classes of building and landuse with FWE specific attributes, FWEArea and FWESystem are two new classes having multisurface geometry and related FWE attributes introduced in the CityGML core. Newly defined FWEArea object is defined as a city object having multisurface geometry covering the entire study area. It can be neighbourhood boundaries, zonal boundaries, municipality boundaries, or political boundaries which are typically static do not change with time. Based on the underlying FWEBuilding and FWELandUse, FWE and its nexus related properties along with temporal changes of population and LandUse change are summarised and introduced at this spatial level. Additionally, properties which naturally belongs only at FWEArea level or datasets of certain FWE and its nexus properties which are only available at FWEArea level are introduced here. Similar to FWEArea, FWESystem is also defined as a city object having multisurface covering the entire study area. Extending FWEArea up by a spatial level, FWESystem covers entire system boundary of the study area which can be borough, city or even an entire district. These boundaries are also static and typically do not change with time. Since FWE ADE is an integrated data model of different spatial levels, for any given time and use case, data related to properties of population, FWE and its nexus can easily be scaled up or down from a taken spatial level using data inter or extrapolation. FWE ADE as a package is flexible in a way that based on use cases each of its thematic modules can be used as a standalone data model or can be scaled up from the smallest spatial level i.e FWEBuildings to the highest spatial level i.e FWESystem or vice-versa by using aggregation functions in SQL and data inter or extrapolation. A high level UML package diagram can be represented as below. More information including the FWE ADE UML diagram and its XML schema definition (XSD) can be found <ahref="https://transfer.hft-stuttgart.de/gitlab/in-source/fwe-ade">here</a>.</p>
<p>While FWEBuilding and FWE LandUse extends the CityGML core thematic classes of building and landuse with FWE specific attributes, FWEArea and FWESystem are two new classes having multisurface geometry and related FWE attributes introduced in the CityGML core. Newly defined FWEArea object is defined as a city object having multisurface geometry covering the entire study area. It can be neighbourhood boundaries, zonal boundaries, municipality boundaries, or political boundaries which are typically static do not change with time. Based on the underlying FWEBuilding and FWELandUse, FWE and its nexus related properties along with temporal changes of population and LandUse change are summarised and introduced at this spatial level. Additionally, properties which naturally belongs only at FWEArea level or datasets of certain FWE and its nexus properties which are only available at FWEArea level are introduced here. Similar to FWEArea, FWESystem is also defined as a city object having multisurface covering the entire study area. Extending FWEArea up by a spatial level, FWESystem covers entire system boundary of the study area which can be borough, city or even an entire district. These boundaries are also static and typically do not change with time. Since FWE ADE is an integrated data model of different spatial levels, for any given time and use case, data related to properties of population, FWE and its nexus can easily be scaled up or down from a taken spatial level using data inter or extrapolation. FWE ADE as a package is flexible in a way that based on use cases each of its thematic modules can be used as a standalone data model or can be scaled up from the smallest spatial level i.e FWEBuildings to the highest spatial level i.e FWESystem or vice-versa by using aggregation functions in SQL and data inter or extrapolation. A high level UML package diagram can be represented as below. More information including the FWE ADE UML diagram and its XML schema definition (XSD) can be found <ahref="https://transfer.hft-stuttgart.de/gitlab/in-source/fwe-ade">here</a>.</p>
<p>An example implementation workflow using FWE ADE enriched CityGML LandUse dataset with SimStadt biomass workflow using <ahref="https://www.safe.com/">Feature Manipulation Engine (FME)</a> can be represented as below.</p>
<p>An example implementation workflow using FWE ADE enriched CityGML LandUse dataset with SimStadt biomass workflow using <ahref="https://www.safe.com/">Feature Manipulation Engine (FME)</a> can be represented as below.</p>
