2017 GR Minutes of the Workshop: Difference between revisions

Jump to navigation Jump to search
← Older edit
update
Fixed typpo
 
(5 intermediate revisions by the same user not shown)
Line 2: Line 2:
{| class="wikitable"
{| class="wikitable"
|-
|-
! WHAT !! WHO !! WHEN
! WHAT !! WHEN !! WHO
|-
|-
| Make new branch the default branch, but make the releases clearly visible on the frontpage || ASAP || CSTB
| Make new branch the default branch, but make the releases clearly visible on the frontpage || ASAP || CSTB
Line 12: Line 12:
| Feedback on availability for the next workshop : Options  November 7, 8, 14, 15 or Decembre 4, 5, 6, 7, 8 || ASAP || All partners  
| Feedback on availability for the next workshop : Options  November 7, 8, 14, 15 or Decembre 4, 5, 6, 7, 8 || ASAP || All partners  
|-
|-
| Codelist : Agree on high-level values|| Before next workshop ||  All partners
| Codelist : Agree on high-level values. Plan an online meeting|| Before next workshop ||  Luca, Usman, Lydia CSTB, Emilien CSTB, Romain, Mariam, Joachim
|-
|-
|  Dedicated WG/online meeting on simulation results and measurements + create milestone on Github || Before next workshop ||  Kanish, Joachim, Pascal, Romain
|  Dedicated WG/online meeting on simulation results and measurements + create milestone on Github || Before next workshop ||  Kanishk, Joachim, Pascal, Romain
|-
|-
| Testing automation : create stand alone sample files with explicit names to be used in the guidelines|| Before next workshop ||  All WG
| Guidelines and testing automation : create stand alone sample files with explicit names to be as example|| Before next workshop ||  All WG
|-
|-
|}
|}
Line 51: Line 51:
<b>[mailto:romain.nouvel@hft-stuttgart.de Romain Nouvel]</b> (HFT Stuttgart)<br/>
<b>[mailto:romain.nouvel@hft-stuttgart.de Romain Nouvel]</b> (HFT Stuttgart)<br/>
<i>Presentation:</i> [[media:20170523_Introduction_EnergyADE_Grenoble.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:20170523_Introduction_EnergyADE_Grenoble.pdf| PDF file]] of the slides<br/>
* Mentimeter quiz on:
===== Mentimeter quiz on: =====
** [https://www.mentimeter.com/s/c9233944c727b849b270bfa51bc71283/10b7d24bf1c7 CityGML Energy ADE for you... ]
* [https://www.mentimeter.com/s/c9233944c727b849b270bfa51bc71283/10b7d24bf1c7 CityGML Energy ADE for you... ]
** [https://www.mentimeter.com/s/c9233944c727b849b270bfa51bc71283/369d61b8e1c6 Priorities for the next semester?] : Make ADE test cases!
* [https://www.mentimeter.com/s/c9233944c727b849b270bfa51bc71283/369d61b8e1c6 Priorities for the next semester?] : Make ADE test cases!
* Activity  
===== Activity : =====
** Activity (measured on GitHub activity) is not constant; attendance to workshops is diminishing -> Would be nice to integrate work on energy ADE into projects, to have time and budget (work on ADE is not only standardization, but also interoperability)
* Activity (measured on GitHub activity) is not constant; attendance to workshops is diminishing -> Would be nice to integrate work on energy ADE into projects, to have time and budget (work on ADE is not only standardization, but also interoperability)
** Many companies/countries are interested, but not necessarily active… -> Build interest through common publications for example
* Many companies/countries are interested, but not necessarily active… -> Build interest through common publications for example
* Organisation
===== Organisation : =====
** Wiki page: http://en.wiki.energy.sig3d.org  
* Wiki page: http://en.wiki.energy.sig3d.org  
** 4 working groups with each 2 coordinators:
* 4 working groups with each 2 coordinators:
** Building physics: Romain & Mostafa
* Building physics: Romain & Mostafa
** Occupancy: Piergiorio & Giorgio
* Occupancy: Piergiorio & Giorgio
** Energy use and systems: Moritz & Silvia
* Energy use and systems: Moritz & Silvia
** Time-dependant data: Alexandru & Kanish
* Time-dependant data: Alexandru & Kanishk
** Technical committee in charge of XML schema: Joachim & Elisa
* Technical committee in charge of XML schema: Joachim & Elisa
Problem: there are often collisions between several issues  
Problem: there are often collisions between several issues  
* Process:  
===== Process: =====
** General:
* General:
*** Issue created on Github
** Issue created on Github
*** Discussion ongoing, including a feedback from technical committee which has the global overview
** Discussion ongoing, including a feedback from technical committee which has the global overview
*** When discussion has found a consensus, add a “validated by WG” tag
** When discussion has found a consensus, add a “validated by WG” tag
*** TC: Go to modelisation
** TC: Go to modelisation
*** WG: actualize guidelines in the corresponding Github branch, including examples (doc/guidelines/Guidelines_EnergyADE.md, linked to figures in /fig)
** WG: actualize guidelines in the corresponding Github branch, including examples (doc/guidelines/Guidelines_EnergyADE.md, linked to figures in /fig)
*** If need be: feedback from WG, changes by TC
** If need be: feedback from WG, changes by TC
** Github branches:
* Github branches:
*** Master branch = current validated version (today 0.8)
** Master branch = current validated version (today 0.8)
*** When new branch (0.9) is stabilized (including guidelines), merge it to master branch
** When new branch (0.9) is stabilized (including guidelines), merge it to master branch
*** NB: make new branch the default branch, but make the releases clearly visible on the frontpage
** NB: make new branch the default branch, but make the releases clearly visible on the frontpage
* Deadlines:
===== Deadlines:=====
** mid-June: Github issues
* mid-June: Github issues
** July: draft modelisation (Joachim)
* July: draft modelisation (Joachim)
** end-July: edit guidelines by WG (in parallel to modelisation) -> edits can be suggested directly into issues, so update is easy and quick a validation by all
* end-July: edit guidelines by WG (in parallel to modelisation) -> edits can be suggested directly into issues, so update is easy and quick a validation by all
** Mid-August: release of .xsd and guidelines
* Mid-August: release of .xsd and guidelines
* Timeline for v1.0? Before v1.0 there needs to be testing on real case tools… we need to accelerate on this in upcoming semester
===== Timeline for v1.0 : =====
** Proposals for modeling changes:
Before v1.0 there needs to be testing on real case tools… we need to accelerate on this in upcoming semester
*** Energy and system
* Proposals for modeling changes:
*** Q/ how to integrate simulation data? With Dynamizer module?
** Energy and system
*** Q/ management of codelists -> WG
** Q/ how to integrate simulation data? With Dynamizer module?
* Apache license 2.0:
** Q/ management of codelists -> WG
** Objective: protect our development, before it becomes an OGC standard
===== Apache license 2.0: =====
** Implications: anyone can use it, but need to integrate a specific text in header of documents (text quotes license and participant organisations with email contact)
* Objective: protect our development, before it becomes an OGC standard
** In order to go forward:  
* Implications: anyone can use it, but need to integrate a specific text in header of documents (text quotes license and participant organisations with email contact)
*** Mustafa needs an explicit email agreement from each participant partner
* In order to go forward:  
*** We need to agree on which organizations should be quoted in license (some participate to workshops but are not active, and some are active but do not participate to workshop) -> criteria proposal: regularly active on Github, reactive to emails (to be discussed further)
** Mustafa needs an explicit email agreement from each participant partner
* Next meeting: Karlsruhe
** We need to agree on which organizations should be quoted in license (some participate to workshops but are not active, and some are active but do not participate to workshop) -> criteria proposal: regularly active on Github, reactive to emails (to be discussed further)
** Options: 7, 8, 14, 15 November; 4, 5, 6, 7, 8 December
===== Next meeting: Karlsruhe =====
** Provide feedback to Romain on availability
* Options: 7, 8, 14, 15 November; 4, 5, 6, 7, 8 December
* Provide feedback to Romain on availability




Line 102: Line 103:
|
|


==== CityGML: standard and practical examples in Germany ====
==== Codelist concrete implementation ====
<b>[mailto:Volker.Coors@hft-stuttgart.de Volker Coors]</b> (HFT Stuttgart)<br/>
<b>[mailto:luca.giovannini@dedagroup.it Luca Giovannini]</b> (Dedagroup Public Sector & Utilities)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara02_VolkerCoors_CityGML-Germany.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:WG_Occupancy_-_Codelists.pdf| PDF file]] of the slides<br/>
* Introduction to CityGML
 
* 3D City models in Germany
Working document on [https://docs.google.com/spreadsheets/d/1QosN8dEW757ht1OqTdTOicw2Yy57syTqrXZA3tcAVUY/edit#gid=928437924 Google doc]
* SimStadt
===== To do : =====
* Future work: Simulations as a Service for citizens
* Link to be added in GitHub readme
* Add a column “source” or “reference”
* Verify English translations
* Discuss unclear points
* Designate one person per language
===== Discussion: =====
* BuildingTypeValue:
** Source: physical architecture typology comes frome TABULA project (now EPISCOPE)
** Issues: Make all labels identical: “XX building”
* Agree on high-level values -> plan an online meeting (Usman, Lydia CSTB, Emilien CSTB, Romain, Mariam, Joachim)
* Create expanded version (subvalues) for more clarity, precision? -> discussion on subvalues for next version
* CurrentUseValue:
** Source: Geomark city project
* See: CityGML codelist (Joachim to provide URL link)
* EnergySourceValue:
** Work on definitions needed -> all
* OccupantTypeValue:
** Work on definitions needed -> all
* OfficialAreaReferenceValue:
** Issue: not one national way to measure net surface -> should use possibility to define surface type
 
|-
|-
|
|


==== CityGML: standard and practical examples in Austria and Italy ====
==== Store Energy Simulation results / inputs ====
<b>[mailto:Giorgio.Agugiaro@ait.ac.at Giorgio Agugiaro]</b> (Austrian Insitute of Technology)<br/>
<b>[mailto:joachim.benner@kit.edu Joachim Benner ]</b> (KIT)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara03_GiorgioAgugiaro_CityGML-Austria-Italy.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:KIT-Proposals-EnergyADE.pdf| PDF file]] of the slides<br/>
Modelling cities in CityGML: Experiences from two case studies.
===== Issues : =====
* Italy (project EnerCity in Trento): LoD2 model generated from footprints and Lidar data by means of BuildingReconstruction Software by VirtualCitySystems (after automatic process, 40% of buildings must be corrected manually). Estimated effort to extend the 3D modelling to the whole city of Trento: 2-3 persons over 1 year<br/>
* Automatic generation of a diagram legend -> optional character string “thematicDescription” in TimeSeriesProperties (a dataType does not have a gml_name!)
** Creation of the 3D city model
**        WeatherData -> need to be aggregated in a WeatherStation
** Enrichment of the 3D city model
** Q/ generalization to noise etc.? -> this is domain specific (inside Energy ADE)
** Estimation of buildings' energy performance
** Q/ what if sensor inside building? -> not weather…
* Austria (project Ci-Nergy in Vienna): estimated effort to complete data integration for the whole city: 5 persons over 1 year
** Q/ context can sometimes have a big impact on measurements -> add a human-readable description for all additional info
** 3D City model
** Q/ will there be a Sensor module in CityGML 3.0? -> No…
** Data sources
* EnergySimulationResults: metadata, link to raw data, …
** Data integration issues 
** Q/ what conceptual difference between simulated and measured data? -> none, but it is difficult to work on too generic feature types -> Pb: some simulation outputs are inputs for other simulations -> this is simulation metadata (input data, simulation model used, date…)
|-
** Add a code snipet, or contact person?
|
** Value: can be Measure or TimeSeries -> include only aggregated values in CityGML? -> Pb: co-simulation needs the extensive simulation results
* -> Need to look into the Sensor ML (with metadata, sensor can be real or virtual) + Observations ML (supports external references), which are parts of Sensor Observation Service -> dedicated WG/online meeting on simulation results and measurements (Kanishk, Joachim, Pascal, Romain) + create a milestone on Github linked to all related issues, with definition of both “measurements” and “results”


==== CityGML and urban energy simulations ====
<b>[mailto:romain.nouvel@hft-stuttgart.de Romain Nouvel]</b> (HFT Stuttgart)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara04_RomainNouvel_Urban-Energy-Simulations.pdf| PDF file]] of the slides<br/>
* Urban energy simulation – for who? for what?
* Example of energy analyses at city scale
* What is required to run these analyses?
* SimStadt Building Typology library
|-
|-
|
|


==== CityGML Energy ADE: objectives and state of development  ====
<b>[mailto:romain.nouvel@hft-stuttgart.de Romain Nouvel]</b> (HFT Stuttgart)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara05_RomainNouvel_CityGML-Energy-ADE.pdf| PDF file]] of the slides<br/>
* Main objectives of the Energy ADE
* Activities of the Energy ADE Working Group
* Energy ADE Team: Size and Visibility, Organization, Dissemination, Development
* CityGML Energy ADE Guidelines
* Links with other OGC standards
* Past workshops
|-
|


==== Energy-related data at building level: examples and issues ====
==== PostgreSQL-based extension 3DCityDB for energy ADE 0.8.0  ====
<b>[mailto:piergiorgio.cipriano@dedagroup.it Piergiorgio Cipriano]</b> (Sinergis - Dedagroup Public Services)<br/>
<b>[mailto:Giorgio.Agugiaro@ait.ac.at Giorgio Agugiaro]</b> (AIT)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara06_PiergiorgioCipriano_Energy-Data-Issues.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:20170523_Agugiaro_Energy_ADE_Workshop_7_3DCityDB.pdf| PDF file]] of the slides<br/>
* Standards for interoperability
* Growing demand for an ADE-aware DB solution
* 3 projects and data issues
* Design criteria
* Practical questions and some conclusions
* Implementation steps
|-
|


==== Energy ADE: Building Physics module  ====
<b>[mailto:romain.nouvel@hft-stuttgart.de Romain Nouvel]</b> (HFT Stuttgart)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara07_RomainNouvel_ADE-BuildingPhysics.pdf| PDF file]] of the slides<br/>
* Working Group Organization
* Activities over the last 6 months
* Open issues 
|-
|-
|
|


==== Energy ADE: Occupancy module ====
==== Temporal data and Dynamizer Module ====
<b>[mailto:piergiorgio.cipriano@dedagroup.it Piergiorgio Cipriano]</b> (Sinergis - Dedagroup Public Services)<br/>
<b>[mailto:kanishk.chaturvedi@tum.de Kanishk Chaturvedi]</b> (TUM)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara08_PiergiorgioCipriano_ADE-Occupancy.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:Dynamizer_Kanishk_Chaturvedi.pdf| PDF file]] of the slides<br/>
* Working group organization
* “Mini Sensor Observation Service” (mini SOS): lightweight service
* Activities over the last 12 months
** work with arbitrary tabular data source (including ADE Dynamizer)
* General feedbacks on ADE v0.7 and future
** provide multiple interfaces
* Occupancy example
* -> explicit link to Sensor
* Data sources
** “getSensorObservation”
* Open issue
* Code lists management (INSPIRE Registry)
|-
|


==== Energy ADE: Systems module ====
<b>[mailto:MLauster@eonerc.rwth-aachen.de Moritz Lauster]</b> (E.ON Energy Research Center)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara09_MoritzLauster_ADE+SystemsModule.pdf| PDF file]] of the slides<br/>
* Working Group Organization
* Activities over the last 6 months
* General feedbacks on ADE
* Open issues 
|-
|-
|
|


==== CityGML Dynamizer ====
==== Testing automation (Pascal – CSTB)  ====
<b>[mailto:mostafa.elfouly@tum.de Mostafa Elfouly]</b> on behalf of '''Kanishk Chaturvedi''' and '''Prof. Thomas H. Kolbe''' (Techcnical University Munich)<br/>
<b>[mailto:pascal.schetelat@cstb.fr Pascal Schetelat]</b> (CSTB)<br/>
<i>Presentation:</i> [[media:20161124_Ferrara10_CityGML_Dynamizer.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:2017_05_22_ADE_testing_automation.pdf| PDF file]] of the slides<br/>
* Introduction to Dynamizer
Motivation: ensure coherence in the GitHub repository (UML file, guidelines, sample files, 3DCityDB SQL schema)
* New Feature Type
* Testing what can be automated :
* How to work with dynamic values?
* Test sample files against latest energy.xsd schema implemented on the GitHub repository
* Handling Timeseries using OGC TimeseriesML 1.0
* For all WG: create sample files with explicit names so they can be both tested and integrated into the guidelines
|-
* Schematron compliance
|
** Works in principle, but little practical impact because very simple
** More useful would be geometric checking… but this would need a geometric module
* Generation of 3DCityDB SQL schema? -> Not yet
*       3D Validation : can City Dr be used ?
* Class generation for different languages? -> Interests in Java and Python


==== European Union Location Framework - Energy pilot project ====
<b>[mailto:francesco.pignatelli@jrc.ec.europa.eu Francesco Pignatelli]</b> and <b>[mailto:giacomo.martirano@ext.jrc.ec.europa.eu Giacomo Martirano]</b> (European Commission - DG JRC)<br/>
<i>Presentation:</i> [[media:20161125_Ferrara11_PignatelliMartirano_EULF.pdf| PDF file]] of the slides<br/>
* Geospatial technologies fuel the data economy
* The role of INSPIRE
* ISA, EULF, ISA2, ELISE
* Overview of EULF Pilots (Transport and Marine)
* The EULF Energy Pilot 
|-
|-
|
|


==== Domain Extendable 3D City Models ====
==== Feedback on Energy ADE application in simulation tools (Joachim – KIT and Jérôme – Kaemco) ====
<b>[mailto:zhihang.yao@tum.de Zhihang Yao]</b> (Techcnical University Munich)<br/>
<b>[mailto:joachim.benner@kit.edu Joachim – KIT and Jérôme – Kaemco ]</b> (KIT / Kaemco)<br/>
<i>Presentation:</i> [[media:20161125_Ferrara12_ZhihangYao_3D-CityDB-ADE.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:KIT-EnergySimulation-Workflow.pdf| PDF file]] of the slides<br/>
* Extending CityGML
*   GUI for manual enrichment of CityGML files 
* Data management of 3D City Model
*   Use of CityGML LoD2: compromise between availability and functionality
* General idea for extending 3D CityDB
* Example
* Ongoing and future work 
|-
|


==== CityGML and Solar Potential Analysis for Buildings in Singapore ====
<b>[mailto:xule@nus.edu.sg Xu Le]</b> (Solar Energy Research Institute - National University of Singapore)<br/>
<i>Presentation:</i> [[media:20161125_Ferrara13_XuLe_Solar-Potential-Singapore.pdf| PDF file]] of the slides<br/>
In 2014, a LOD2 model of whole Singapur has been generated. SERIS has used it to simulate the solar potential with a 1 sqm meshing.
* Introduction of SERIS
* Capabilities from SES cluster
* Motivation and Background
* Methodology
* Case studies
** Rooftop PV potential
** Solar Insolation for Buildings with full 3D implementation
**Automatically Modelling LoD from 2 to 3
|-
|-
|
|


==== Consclusions and next steps ====
<b>[mailto:romain.nouvel@hft-stuttgart.de Romain Nouvel]</b> (HFT Stuttgart)<br/>
<i>Presentation:</i> [[media:20161125_Ferrara14_RomainNouvel_Conclusions.pdf| PDF file]] of the slides<br/>
* Towards Energy ADE 0.8
* Energy ADE Team – Integrate new contributors
* Next workshop?
* Dissemination
|
|
Retrieved from "http://en.wiki.energy.sig3d.org/index.php?title=2017_GR_Minutes_of_the_Workshop"