Support for single string attributes in read

[graziano-giuliani]

Partial modification to allow netCDF Fortran library able to read single string attributes from a netCDF4 CF-1.9 compliant using string type for attributes. It overloads the nf90_get_att_text function returning a single string attribute (note the nlen == 1 in the patch) as if it is a character attributes. What is not implemented are multidimensional strings, and the capability to write string attributes, because of the lack of string type in Fortran standard. This patch would allow reading netCDF files like the one created from the Copernicus cds-beta site for ECMWF ERA5 model. See reference to this in issue #181 "string attributes are not supported yet?"

[CLAassistant]

All committers have signed the CLA.

[WardF]

Thank you!

[edwardhartnett]

Can you add a test or two as well?

[WardF]

@graziano-giuliani Is there any chance you could help us by adding a test for this as well?

[WardF]

I'll see if I can add a test for this.

[gmao-cda]

@WardF May I ask if there is a test for this new implementation? If not, can I contribute one? I have encountered the same issue and I directly called netcdf-c lib from Fortran to overpass it (https://github.com/cd10kfsu/F90GIO/issues/12#issue-3333074239), and I have an existing file for testing. It would be great that netcdf-fortran can do it directly as implemented in this PR.

File list:

• example.cdl: CDL to create the test data
• example.nc: test data generated by using ncgen -o example.nc example.cdl

The CDL example.cdl is

netcdf example {

  dimensions:
      Location = UNLIMITED ; // (0 currently)

  // global attributes:
      string :author = "fake_author" ;
      :agency = "fake_agency" ;

  group: MetaData {
    variables:
        float latitude(Location) ;
            string latitude:units = "degrees_north" ;
  }

  group: yobs {
    variables:
        float sst(Location) ;
            string sst:units = "C" ;
  }

  group: Hx {
    variables:
        float sst(Location) ;
            sst:units = "C" ;
  }
}

Essentially it creates NC_STRING and NC_CHAR attributes for global, and variables under different groups , so that the new build from this PR can be tested to see if these attributes are correctly read in.

I can try to build the NetCDF-Fortran lib from this PR, and write a code using this lib to check if updated nf90_get_att_text can read the attributes correctly.

[WardF]

Hello @gmao-cda; contributing a test would be greatly appreciated, as it would help us keep our CI up to date. I have had this on the back burner as something to do for a while, clearly, but if you were able to contribute that I should be able to get things up and running and merged ASAP. Thank you!

[gmao-cda]

Hi @WardF, I have added a test in the PR #469. PR #469 shall be merged after PR #453 Please let me know if I need further revise it. Thanks!

[veenstrajelmer]

@WardF I noticed the related issue #181 that is still open. Should it be closed or does this PR not completely fix that issue?

Internally we are also running into this same issue with netcdf network files written with xarray (and engine="h5netcdf"), resulting in string-type attributes. I would love to see if we can update the netcdf-fortran library in our software, but for that it would be required that there is another release including this fix. Is that by any chance already planned?

[gmao-cda]

(cc @WardF here)

@veenstrajelmer For the 1d string, it has been solved using the source codes from the latest branch main

Check this test to see how to read string: https://github.com/Unidata/netcdf-fortran/blob/main/nf03_test4/f90tst_att.F90

The corresponding test data is here: https://github.com/Unidata/netcdf-fortran/blob/main/nf03_test4/ref_att.nc Its cdl is: https://github.com/Unidata/netcdf-fortran/blob/main/nf03_test4/ref_att.cdl

Let me know if it works for you. If you cannot change the netcdf-fortran version, I will provide you an alternative solution.

[veenstrajelmer]

Great, thanks for the reply. And are there any plans to release somewhere soon? I don't think I can push a non-released version into our pipelines, that won't be accepted.