Quantized data can be read by all versions of netCDF-4.
The reason is that the quantization is applied as the data are written.
>From that point on, it's just normal netCDF data. The fact that some of the
bits have been smoothed away can only be seen in the presence of an
attribute we add to the variable to record it.
Keep on NetCDFing!
Ed Hartnett
On Sat, Jun 10, 2023 at 7:44 AM John Caron <jcaron1129@xxxxxxxxx> wrote:
> Apparently its not needed for reading data:
>
> "As part of the netcdf-c library, the quantize algorithms are available
> for netCDF/HDF5 files, and the new ncZarr format, and produce data files
> that are fully backward compatible for all versions of netcdf-c since 4.0,
> and also fully compatible with netcdf-Java."
>
> (see https://github.com/Unidata/netcdf-c/blob/main/docs/quantize.md)
>
> On Fri, Nov 4, 2022 at 11:51 AM Joe Lee via netcdf-java <
> netcdf-java@xxxxxxxxxxxxxxxx> wrote:
>
>> Does the current netCDF-Java also support it?
>>
>> I’m mostly concerned about Data Interoperability.
>>
>>
>>
>> *From: *netcdfgroup <netcdfgroup-bounces@xxxxxxxxxxxxxxxx> on behalf of
>> Thompson, Matt (GSFC-610.1)[SCIENCE SYSTEMS AND APPLICATIONS INC] via
>> netcdfgroup <netcdfgroup@xxxxxxxxxxxxxxxx>
>> *Date: *Friday, November 4, 2022 at 12:40 PM
>> *To: *netcdfgroup@xxxxxxxxxxxxxxxx <netcdfgroup@xxxxxxxxxxxxxxxx>
>> *Subject: *[netcdfgroup] Quantize Support in netCDF-Fortran: Only Bit
>> Groom possible?
>>
>> netCDF List,
>>
>>
>>
>> I am looking to extend the model I work on, GEOS, to support using the
>> new quantize options in netCDF. My question is: am I right in my reading of
>> netCDF-Fortran that only Bit Groom is supported?
>>
>> I can see in netCDF-C that there seem to be three variants:
>>
>>
>>
>> - Bit Groom
>> - Granular Bit Round
>> - Bit Round
>>
>>
>>
>> (see https://github.com/Unidata/netcdf-c/blob/main/docs/quantize.md)
>>
>>
>>
>> but in the netCDF-Fortran docs I only see it mention Bit Groom and my
>> reading of the include files seem to back that up.
>>
>>
>>
>> So I was wondering: Is there a fundamental Fortran reason for not
>> supporting the other two variants? Or perhaps, is it that, of the three
>> variants, Bit Groom is by far the one people should use, so that's what was
>> exposed by the Fortran interface?
>>
>>
>>
>> Thanks,
>>
>> Matt
>>
>>
>>
>> --
>>
>> Matt Thompson, SSAI, Ld Scientific Programmer/Analyst
>>
>> NASA GSFC, Global Modeling and Assimilation Office
>>
>> Code 610.1, 8800 Greenbelt Rd, Greenbelt, MD 20771
>>
>> Phone: 301-614-6712 Fax: 301-614-6246
>>
>> *http://science.gsfc.nasa.gov/sed/bio/matthew.thompson
>> <http://science.gsfc.nasa.gov/sed/bio/matthew.thompson>*
>> _______________________________________________
>> NOTE: All exchanges posted to Unidata maintained email lists are
>> recorded in the Unidata inquiry tracking system and made publicly
>> available through the web. Users who post to any of the lists we
>> maintain are reminded to remove any personal information that they
>> do not want to be made public.
>>
>>
>> netcdf-java mailing list
>> netcdf-java@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> https://www.unidata.ucar.edu/mailing_lists/
>>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> netcdfgroup mailing list
> netcdfgroup@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> https://www.unidata.ucar.edu/mailing_lists/
>
