You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

scrollbar}

See also: OATC Wiki Home

Date: June 8 - 9, 20010
Venue: Unesco-IHE, The Netherlands

Participants:

Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Standa Vanecek, DHI (s.vanecek@dhi.cz)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
Jesper Grooss, DHI (jgr@dhigroup.com)

Apologies:
~jnh@dhigroup.com, DHI (jnh@dhigroup.com)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade@baw.de)
Daniele Andreis,Universita` di Trento,(daniele.andreis@gmail.com)
Jan Gregersen, LicTek

Documents:

Table of contents

1. Comments from review

Make clear how use IElementSet to work with OGC formats

Two alternatives were discussed:

  • Document how each OGC feature is to be used by the current elementset.
  • Make a more general element set, and let the current element set extent from the general one. And open for the possibility for other extensions of the general one, being e.g. the different OGC feature classes.

The discussion turned into which strategy was the best for OpenMI: To document specialized interfaces, or to have general ones and allow them to be extended over time.

How to make the standard extendable

Meeting with EPA on how to make OpenMI and FRAMES work together, and also several reviewers, have revealed the necessity of making the standard extendable instead of "all inclusive". since the "all inclusive" is very difficult to predict.

The base idea is to make very general versions of interfaces, and provide specializations of these. These specializations can be released at a later stage than the standard, and without affecting the standard.

Strategy for releasing 2.0

Releasing standard and then extensions.

Possible candidates for extensions.

  1. LinkableComponent: Parallel computing component
  2. ExchangeItem: FRAMES dictinaries.
  3. ValueDefinition: ontologies, FRAMES dictinaries.
  4. ElementSet: Advanced spatial/GIS functionality.
  5. ValueSet: FRAMES dictinaries.
  6. TimeSet.

ad: ElementSet: Advanced spatial/GIS functionality:

Typical geometrical element types for models are:

  • Point
  • LineString - values defined on each LineString coordinate (node based values on a line)
  • MultiLineString - values defined on each LineString (element based values on a line)
  • 2D/3D mesh based - the IElementSet of today
    • Element values (finite volume type values)
  • Node values (finite element type values)
  • Grid based, element/node/face values
    • Structured grid, (x0, dx, xCount)^dimension + rotation from true north
    • CurveLinear grid (coordinates for all grid points)
  • Polygon/MultiPolygon

Some of these have directly an OGC feature counterpart, while others (the grid) has not. Some of these are covered by the current element set, and some are not, or only in a "generic" geometrical way, i.e. without topology information.

So it would be nice to have a general element set and in time release extensions to the standard that includes new type of "often used"/requested element sets.

Releasing full standard, reflecting all suggested requests, including SDK and GUI.

Current problems:

No model, neither test models nor real world model has really been used and tested using the 2.0 standard. Hence, there are many unknowns and in order to get around all possible issues, quite a lot of work is required.

Limited resources within OATC for testing and development, in order to get as well the standard as the SDK "correct".

Limited resources for GUI development and support.

  • No labels

Disclaimer