-
Notifications
You must be signed in to change notification settings - Fork 30
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
Comments
Please check your files. Maybe they follow the UGRID convention, but they are not CF-compliant:
|
Hi @JaviRG , thank you for your reply. Those error messages came from EDAL/ncWMS log? |
No, I just checked your files using https://pumatest.nerc.ac.uk/cgi-bin/cf-checker.pl |
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. |
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.
The text was updated successfully, but these errors were encountered: