2017 GR Minutes of the Workshop: Difference between revisions

Jump to navigation Jump to search
Updated with more slides
Fixed typpo
 
(2 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 14: Line 14:
| Codelist : Agree on high-level values. Plan an online meeting|| Before next workshop ||  Luca, Usman, Lydia CSTB, Emilien CSTB, Romain, Mariam, Joachim
| 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 63: Line 63:
* 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  
Line 147: Line 147:
** Add a code snipet, or contact person?
** 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
** 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 (Kanish, Joachim, Pascal, Romain) + create a milestone on Github linked to all related issues, with definition of both “measurements” and “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”


|-
|-
Line 156: Line 156:
<b>[mailto:Giorgio.Agugiaro@ait.ac.at Giorgio Agugiaro]</b> (AIT)<br/>
<b>[mailto:Giorgio.Agugiaro@ait.ac.at Giorgio Agugiaro]</b> (AIT)<br/>
<i>Presentation:</i> [[media:20170523_Agugiaro_Energy_ADE_Workshop_7_3DCityDB.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/>
* Growing demand for an ADE-aware DB solution
* Design criteria
* Implementation steps


|-
|-
Line 163: Line 166:
<b>[mailto:kanishk.chaturvedi@tum.de Kanishk Chaturvedi]</b> (TUM)<br/>
<b>[mailto:kanishk.chaturvedi@tum.de Kanishk Chaturvedi]</b> (TUM)<br/>
<i>Presentation:</i> [[media:Dynamizer_Kanishk_Chaturvedi.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:Dynamizer_Kanishk_Chaturvedi.pdf| PDF file]] of the slides<br/>
* “Mini Sensor Observation Service” (mini SOS): lightweight service
** work with arbitrary tabular data source (including ADE Dynamizer)
** provide multiple interfaces
* -> explicit link to Sensor
** “getSensorObservation”


|-
|-
Line 170: Line 178:
<b>[mailto:pascal.schetelat@cstb.fr Pascal Schetelat]</b> (CSTB)<br/>
<b>[mailto:pascal.schetelat@cstb.fr Pascal Schetelat]</b> (CSTB)<br/>
<i>Presentation:</i> [[media:2017_05_22_ADE_testing_automation.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:2017_05_22_ADE_testing_automation.pdf| PDF file]] of the slides<br/>
Motivation: ensure coherence in the GitHub repository (UML file, guidelines, sample files, 3DCityDB SQL schema)
* Testing what can be automated :
* Test sample files against latest energy.xsd schema implemented on the GitHub repository
* 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


|-
|-
Line 175: Line 193:


==== Feedback on Energy ADE application in simulation tools (Joachim – KIT and Jérôme – Kaemco) ====
==== Feedback on Energy ADE application in simulation tools (Joachim – KIT and Jérôme – Kaemco) ====
<b>[mailto:joachim.benner@kit.edu Joachim Benner ]</b> (KIT)<br/>
<b>[mailto:joachim.benner@kit.edu Joachim – KIT and Jérôme – Kaemco ]</b> (KIT / Kaemco)<br/>
<i>Presentation:</i> [[media:KIT-EnergySimulation-Workflow.pdf| PDF file]] of the slides<br/>
<i>Presentation:</i> [[media:KIT-EnergySimulation-Workflow.pdf| PDF file]] of the slides<br/>
*    GUI for manual enrichment of CityGML files 
*    Use of CityGML LoD2: compromise between availability and functionality


|-
|-