Bob Simons asked me to reply with the following, as he is not on the mail-list:
I like/vote for NCO's .json format
http://nco.sourceforge.net/nco.html#json
A simple set of rules converts any .nc file into one of these .json files.
These .json files are human readable and machine readable.
I particularly like the lvl=2 "pedantic" format, because it includes 100% of
the information in the original .nc file, thus allowing for the possibility of
a round trip (.nc -> .json -> .nc) with no loss of information.
-Roy
> On Sep 11, 2018, at 8:49 AM, Dennis Heimbigner <dmh@xxxxxxxx> wrote:
>
> Has the community ever achieved consensus on a standard translation
> of netcdf-4 to Json? It seems to me that Unidata might usefully serve
> as a repository for such a standard if it exists.
> =Dennis Heimbigner
> Unidata
>
> _______________________________________________
> 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:
> http://www.unidata.ucar.edu/mailing_lists/
