Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem when using UGRID aggregated in THREDDS #121

Open
marceloandrioni opened this issue Sep 13, 2019 · 4 comments
Open

Problem when using UGRID aggregated in THREDDS #121

marceloandrioni opened this issue Sep 13, 2019 · 4 comments

Comments

@marceloandrioni
Copy link

marceloandrioni commented Sep 13, 2019

Hello, following @Unidata/thredds#526 (comment) by @drf5n I managed to aggregate unstructured grid results in TDS 4.6.14 as a FMRC (feature model run collection). The solution was basically to add a record dimension to aggregate everything along.
TDS shows the new aggregated dataset just fine using the OPENDAP protocol. All other protocols (NCSS, WMS, WCS) fail, but I think that is expected since only TDS 5 will have true UGRID support.

Back to the main issue, when trying to open the opendap link using ncWMS2/EDAL (version 1.4.1, not the one inside TDS) it fails with the message:
uk.ac.rdg.resc.edal.exceptions.DataReadingException: Coordinate variables listed in mesh_topology:node_coordinates must share the same single dimension to be UGRID compliant

Checking the code my extremely limited java knowledge tells me that the problem is because now latitude and longitude have one extra dimension (record) besides the main one (node).

Here some examples of the files I am testing with.

Thank you very much.

@ghost
Copy link

ghost commented Oct 23, 2019

Please check your files. Maybe they follow the UGRID convention, but they are not CF-compliant:

------------------
Checking variable: element
------------------
ERROR: (3.3): Invalid standard_name: face_node_connectivity
ERROR: (3.1): Invalid units: nondimensional

------------------
Checking variable: latitude
------------------
ERROR: (4.3): Invalid value for positive attribute

------------------
Checking variable: longitude
------------------
ERROR: (4.3): Invalid value for positive attribute

------------------
Checking variable: mesh_topology
------------------
ERROR: (3.3): Invalid standard_name: mesh_topology
INFO: attribute cf_role is being used in a non-standard way
INFO: (3.1): No units attribute set.  Please consider adding a units attribute for completeness.
ERROR: (9.5): Invalid value for cf_role attribute

@marceloandrioni
Copy link
Author

marceloandrioni commented Oct 23, 2019

Hi @JaviRG , thank you for your reply. Those error messages came from EDAL/ncWMS log?

@ghost
Copy link

ghost commented Oct 30, 2019

No, I just checked your files using https://pumatest.nerc.ac.uk/cgi-bin/cf-checker.pl

@marceloandrioni
Copy link
Author

Hi @JaviRG, thanks for pointing me out to cf-checker. I never tried before but it seems a great tool. I will try to fix the errors listed by it to see if then the file can be read/displayed using EDAL.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant