open TELEMAC-MASCARET The mathematically superior suite of solvers

netcdf format is not supported as of version 3.3.4 of Blue Kenue (2012), which is also the version currently available from the CHC website, I believe. In 2014 Michel confirmed that this was the state of the play (www.opentelemac.org/index.php/kunena/blu...3-contour-file#11541).

Personally I would find netdcf import/export handy to exchange information on bathymetry and mesh connectivity across different modelling and information systems.

Is there any plan to include this capability in the foreseeable future?

Could any other user possibly be interested in using this feature, in the first place?

Would interested people leave a statement in this post? The reactions could serve as a way to probe the sentiment about this idea... and que sera sera

Hello There,

netcdf is not supported in BlueKenue version 3.6.1-beta+20161207.

For me, netcdf is akin to xml; where anything can be put into it and there is no real structure.

my 2 cents

Kindly,
Alan

Hi,

I'll echo what Alan posted above.
NETcdf is just a bucket and it's up to the user to decide
how and with what it gets filled.
This makes implementing generic support in an application
like Blue Kenue pretty much impossible.

That being said, we did implement rather limited support for importing
some raster data from NETcdf files via GDAL a few years ago.
If the community is interested in supporting this effort I suppose
we could flesh it out and add it to a future release.

Please note that I have yet to see a "standard" way to store
triangular mesh data in NETcdf but my information might be
out of date.
(being retired and all

Cheers... Martin

I appreciate that generic/general support would be undoable. Indeed, anyone chooses his own way of storing his data set according to the NetCDF criteria. However, the attributes and values of these data are stored and retrieved efficiently thanks to the standardization.

This standardization has to do with the semantics, but indeed one can choose its ways to arrange the data -- a standard arrangement is one step further, far from mandatory. I know that the folks at Deltares in the Netherlands are using NetCDF format to import the mesh data and export simulation outputs.

Therefore, the benefit of an implementation of choice for the Blue Kenue files in NetCDF would be that they can be read, written, converted and exchanged between modelling and information systems. Of course, you can write a script for anything you like, but NetCDF would provide the structure to locate the meanings and whereabouts of the data.

Rather than a bucket, I see more NetCDF is more akin to a chest of drawers.

These are my 2 cents.

If the goal is to use NetCDF as a way to exchange information across different modelling and information systems then it may help to start growing a list of systems that
1. currently support NetCDF along with a description of what they put into their NetCDF file(s)... e.g. bathymetry and mesh connectivity
1. currently don't support NetCDF and what would be nice to put into a possible NetCDF file or file(s)

And then see what is common and how that commonality is commonly structured

Maybe the community can let you know about these things? Or maybe you already know? 'fraid I don't know...

Kindly,
Alan

I came across this resource named Ugrid conventions

ugrid-conventions.github.io/ugrid-conventions/

whose aim is clear from this excerpt

This suggests that there is at least one way to implement NetCDF formats in Blue Kenue that can be useful for/used by a wide modelling community.

Hope this helps