Ghansham,
Sorry for the slow reply. This list is no longer regularly used. Please
look at cf-conventions.org and follow the links to the CF Github site where
you can see and contribute to various discussions about CF. The next
version of CF (1.9
<http://cfconventions.org/cf-conventions/cf-conventions.html>) includes
support for all unsigned types.
Grace and peace,
Jim
<http://ncics.org/> *Jim Biard*
*Research Scholar*
North Carolina State University <http://ncsu.edu/>
North Carolina Institute for Climate Studies (NCICS) <https://ncics.org/>
151 Patton Ave, Asheville, NC 28801
e: jbiard@xxxxxxxxx (or jcbiard@xxxxxxxx)
o: +1 828 271 4900
On Tue, May 12, 2020 at 7:27 AM Ghansham Sangar <ghanshamsangar@xxxxxxxxx>
wrote:
> Dear Sir
>
> Why are we having only unsigned byte data support. Atleast we should have
> unsigned short also because most of the sensor raw count have valid bits
> more than 8.
>
> Regards
> Ghansham
> _______________________________________________
> 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.
>
>
> cf-satellite mailing list
> cf-satellite@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: https://www.unidata.ucar.edu/mailing_lists/
>
