...
Adrian Harper, Innovyze Ltd (adrian.harper@innovyze.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
Jesper Grooss, DHI (jgr@dhigroup.com)
~s.vanecek@dhi.cz, DHI (s.vanecek@dhi.cz)
Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)
Apologies
-
E-mail from the dissimination committee (Johan/Michiel)
up-to-date list of OATC members
Stef will send an e-mail to all current members on the list, and ask whether they:
- still want to be on it
- access the wiki pages
Specification document replaced by OGC format version?
...
Johan of correct, but there are a few things to make clear:
- the OpenMI 1.4. component is able to run in Pipistrelle, and interact with 2.0 components
- however, it does not become OpenMI 2.0 compliant itself (it is just wrapped)
- all the 1.4 component's data operations are not visible and therefore can not be used (however, this can be replaced by the 2.0 adapted outputs
Planning of the OpenMI 2.0 components
Supplier | component | release date | remarks |
---|---|---|---|
DHI | Mike-11 | available in last release | no compliancy info available yet, not thorougly tested in real compositions |
DHI | MIKE-Urban | " | " |
DHI | MIKE-She | " | " |
DHI | MIKE-21 | 3th quarter 2012 |
|
DHI | FEFLOW | " |
|
DHI | WEST | " | waste water treatment |
DHI | DIMS | " | time series database |
Deltares | Sobek213-RR | april (2012) |
|
Deltares | Sobek213-CF | " |
|
Deltares | Sobek213-RTC | " |
|
Deltares | DeltaShell-Flow1D | " | channel flow and real time control |
Deltares | DeltaShell-RR | date to be announed announced |
|
Innovyze | InfoWorks-CS version 13.0 | early autumn 2012 |
|
Innovyze | InfoWorks-RS version 13.0 | " |
|
Status OGC
See note above ("Specification document replaced by OGC format version").
Status OpenMI 2.0
No the issue is how to specify and implement the mandatory conformance tests.
- Just state for every interface that its methods are implemented correctly?
- Just say that the component should be loaded in Pipistrelle?
After some discussion we decided that we will use the same approach as done for netcdf: assume that there is a testing tool implemented, en specify the things to be tested (see the first download on http://www.opengeospatial.org/standards/netcdf)
Java SDK / GUI
Alterra has limited funding available for the development of OpenMI. Plans to be made yet on what effort goes to models, applications, SDK, GUI, etcetera.
A way to work with java components in the GUI would be:
- let the component write its 'exchange item xml'
- create the composition in the Pipistrelle GUI
- write a composition XML
- run that composition in a lean and mean Java runtime environment (console application?)
1.4 Video on OpenDA website?
Yep, do so.
Status OGC
See note above ("Specification document replaced by OGC format version"Johan has asked Standa for the status on the OpenMI 2.0 implementation. Standa will forward the question to Adrian, and Adrian will answer it.
There also is a need for an overview of OpenMI 2.0 compliant components. DHI has a few, but no formal xml etc. yet. Stef will ask the OAEC to find someone to put more effort in gathering compliant components. As a first step Stef will ask the OAEC for a specific email (compliance@openmi.org).
There is a EU proposal (CEnTIEM 3) that will put more attention to OpenMI and existing component.
Jan once implemented a tool that generates 1.4. compliancy info XML after loading the component. We should try to find the source of that tool (Jesper will have a look).
Next meetings
Thursday Feb 2nd, 13:30 CET - 14:30 CET