mirror/netcdf-c
2
0
Fork 0
mirror of https://github.com/Unidata/netcdf-c.git synced 2024-12-21 08:39:46 +08:00
Code Issues Packages Projects Releases Wiki Activity
d89a63a1d3
netcdf-c/nczarr_test/ref_power_901_constants.cdl

39 lines
1.3 KiB
Plaintext
Raw Normal View History

Fix JSON quoted string processing in libnczarr re: github issue https://github.com/Unidata/netcdf-c/issues/1982 The problem was that the libnczarr/zsjon.c handling of strings with embedded double quotes was wrong; a one line fix. Also added a test case. Misc. other changes: 1. I Discovered, en passant, that the handling of 64 bit constants had an error that was fixed. 2. cleanup of the constant conversion code to recurse on arrays of values.
2021-05-07 06:39:44 +08:00
netcdf ref_power_901_constants {
Addendum: This PR has been extended to include interoperability fixed. We were given a Zarr format dataset stored as a directory+file tree. This dataset uses the XArray conventions and was generated by some non-Unidata Zarr implementation. In attempting to process it with NCZarr, several interoperability problems were discovered and fixed. This gives us more confidence that NCZarr -- using pure zarr -- can interoperate with other Zarr implementations. Specific changes: * Add test nczarr_test/run_interop.sh * Support attributes with single value not enclosed in JSON array tags. * Add mode inferencing and use it in nczarr_test/run_purezarr.sh * Reduce size of tst_err_enddef.nc because it is more than 3 GB.
2021-04-03 08:39:50 +08:00
dimensions:
lat = 361 ;
lon = 576 ;
variables:
float FRLAKE(lat, lon) ;
FRLAKE:fmissing_value = 999999986991104. ;
FRLAKE:long_name = "fraction_of_lake" ;
FRLAKE:standard_name = "fraction_of_lake" ;
FRLAKE:units = "1" ;
FRLAKE:valid_range = -999999986991104., 999999986991104. ;
FRLAKE:vmax = 999999986991104. ;
FRLAKE:vmin = -999999986991104. ;
Upgrade the nczarr code to match Zarr V2 Re: https://github.com/zarr-developers/zarr-python/pull/716 The Zarr version 2 spec has been extended to include the ability to choose the dimension separator in chunk name keys. The legal separators has been extended from {'.'} to {'.' '/'}. So now it is possible to use a key like "0/1/2/0" for chunk names. This PR implements this for NCZarr. The V2 spec now says that this separator can be set on a per-variable basis. For now, I have chosen to allow this be set only globally by adding a key named "ZARR.DIMENSION_SEPARATOR=<char>" in the .daprc/.dodsrc/ncrc file. Currently, the only legal separator characters are '.' (the default) and '/'. On writing, this key will only be written if its value is different than the default. This change caused problems because supporting a separator of '/' is difficult to parse when keys/paths use '/' as the path separator. A test case was added for this. Additionally, make nczarr be enabled default by default. This required some additional changes so that if zip and/or AWS S3 sdk are unavailable, then they are disabled for NCZarr. In addition the following unrelated changes were made. 1. Tested that pure-zarr mode could read an nczarr formatted store. 1. The .rc file handling now merges all known .rc files (.ncrc,.daprc, and .dodsrc) in that order and using those in HOME first, then in current directory. For duplicate entries, the later ones override the earlier ones. This change is to remove some of the conflicts inherent in the current .rc file load process. A set of test cases was also added. 1. Re-order tests in configure.ac and CMakeLists.txt so that if libcurl is not found then the other options that depend upon it properly are disabled. 1. I decided that xarray support should be enabled by default for pure zarr. In order to allow disabling, I added a new mode flag "noxarray". 1. Certain test in nczarr_test depend on use of .dodsrc. In order for these to work when testing in parallel, some inter-test dependencies needed to be added. 1. Improved authorization testing to use changes in thredds.ucar.edu
2021-04-25 09:48:15 +08:00
float FRLAND(lat, lon) ;
FRLAND:fmissing_value = 999999986991104. ;
FRLAND:long_name = "fraction_of_land" ;
FRLAND:standard_name = "fraction_of_land" ;
FRLAND:units = "1" ;
FRLAND:valid_range = -999999986991104., 999999986991104. ;
FRLAND:vmax = 999999986991104. ;
FRLAND:vmin = -999999986991104. ;
Addendum: This PR has been extended to include interoperability fixed. We were given a Zarr format dataset stored as a directory+file tree. This dataset uses the XArray conventions and was generated by some non-Unidata Zarr implementation. In attempting to process it with NCZarr, several interoperability problems were discovered and fixed. This gives us more confidence that NCZarr -- using pure zarr -- can interoperate with other Zarr implementations. Specific changes: * Add test nczarr_test/run_interop.sh * Support attributes with single value not enclosed in JSON array tags. * Add mode inferencing and use it in nczarr_test/run_purezarr.sh * Reduce size of tst_err_enddef.nc because it is more than 3 GB.
2021-04-03 08:39:50 +08:00
float FRLANDICE(lat, lon) ;
FRLANDICE:fmissing_value = 999999986991104. ;
FRLANDICE:long_name = "fraction_of_land_ice" ;
FRLANDICE:standard_name = "fraction_of_land_ice" ;
FRLANDICE:units = "1" ;
FRLANDICE:valid_range = -999999986991104., 999999986991104. ;
FRLANDICE:vmax = 999999986991104. ;
FRLANDICE:vmin = -999999986991104. ;
Upgrade the nczarr code to match Zarr V2 Re: https://github.com/zarr-developers/zarr-python/pull/716 The Zarr version 2 spec has been extended to include the ability to choose the dimension separator in chunk name keys. The legal separators has been extended from {'.'} to {'.' '/'}. So now it is possible to use a key like "0/1/2/0" for chunk names. This PR implements this for NCZarr. The V2 spec now says that this separator can be set on a per-variable basis. For now, I have chosen to allow this be set only globally by adding a key named "ZARR.DIMENSION_SEPARATOR=<char>" in the .daprc/.dodsrc/ncrc file. Currently, the only legal separator characters are '.' (the default) and '/'. On writing, this key will only be written if its value is different than the default. This change caused problems because supporting a separator of '/' is difficult to parse when keys/paths use '/' as the path separator. A test case was added for this. Additionally, make nczarr be enabled default by default. This required some additional changes so that if zip and/or AWS S3 sdk are unavailable, then they are disabled for NCZarr. In addition the following unrelated changes were made. 1. Tested that pure-zarr mode could read an nczarr formatted store. 1. The .rc file handling now merges all known .rc files (.ncrc,.daprc, and .dodsrc) in that order and using those in HOME first, then in current directory. For duplicate entries, the later ones override the earlier ones. This change is to remove some of the conflicts inherent in the current .rc file load process. A set of test cases was also added. 1. Re-order tests in configure.ac and CMakeLists.txt so that if libcurl is not found then the other options that depend upon it properly are disabled. 1. I decided that xarray support should be enabled by default for pure zarr. In order to allow disabling, I added a new mode flag "noxarray". 1. Certain test in nczarr_test depend on use of .dodsrc. In order for these to work when testing in parallel, some inter-test dependencies needed to be added. 1. Improved authorization testing to use changes in thredds.ucar.edu
2021-04-25 09:48:15 +08:00
float FROCEAN(lat, lon) ;
FROCEAN:fmissing_value = 999999986991104. ;
FROCEAN:long_name = "fraction_of_ocean" ;
FROCEAN:standard_name = "fraction_of_ocean" ;
FROCEAN:units = "1" ;
FROCEAN:valid_range = -999999986991104., 999999986991104. ;
FROCEAN:vmax = 999999986991104. ;
FROCEAN:vmin = -999999986991104. ;
Addendum: This PR has been extended to include interoperability fixed. We were given a Zarr format dataset stored as a directory+file tree. This dataset uses the XArray conventions and was generated by some non-Unidata Zarr implementation. In attempting to process it with NCZarr, several interoperability problems were discovered and fixed. This gives us more confidence that NCZarr -- using pure zarr -- can interoperate with other Zarr implementations. Specific changes: * Add test nczarr_test/run_interop.sh * Support attributes with single value not enclosed in JSON array tags. * Add mode inferencing and use it in nczarr_test/run_purezarr.sh * Reduce size of tst_err_enddef.nc because it is more than 3 GB.
2021-04-03 08:39:50 +08:00
}
Reference in New Issue Copy Permalink