On Tue, Aug 1, 2017 at 1:26 PM, David Johnson
wrote:
> We have released version 0.2 of our CF-JSON spec (http://cf-json.org/
> specification) to merge with the NCO format. So CF-JSON is now consistent
> with NCO JSON output. CF-JSON does not currently *require* all of the NCO
> JSON elements, but
Just to round this out for now:
We have released version 0.2 of our CF-JSON spec (
http://cf-json.org/specification) to merge with the NCO format. So CF-JSON
is now consistent with NCO JSON output. CF-JSON does not currently
*require* all of the NCO JSON elements, but NCO JSON is valid CF-JSON.
T
On Thu, Jul 27, 2017 at 12:47 AM, Jon Blower
wrote:
> P.S. I’ve created an issue on the CovJSON GitHub site for discussion on
> the distinction between CovJSON, CF-JSON and NCO-JSON. I thought this might
> be a more appropriate forum for the discussion than this mailing list.
>
>
>
> https://gith
July 2017 07:59
To: David Johnson , Christopher Barker
Cc: "cf-metadata@cgd.ucar.edu"
Subject: Re: [CF-metadata] JSON representation based on CF
Hi David,
Just a quick one as I’m conscious that this list isn’t really for JSON discussions – the reasons that CovJSON flattens
2017 05:33
To: Christopher Barker
Cc: Jon Blower , Sean Arms , "cf-metadata@cgd.ucar.edu"
Subject: Re: [CF-metadata] JSON representation based on CF
Hi All,
The CF-JSON structure was generally based on CDL (as produced by ncdump) which stores the data in a separa
My bad:
"As of version 4.6.3, NCO defaults to demarcate inner dimensions of
variable data with (nested) square brackets rather than printing data as an
unrolled single dimensional array."
So we will seriously consider the change of data location, "dimensions" to
"shape", and then CF-JSON=NCO v4.6.
Hi All,
The CF-JSON structure was generally based on CDL (as produced by ncdump)
which stores the data in a separate section. The key requirement is the
same as for CDL.
But I do see the logic of just including it in the variable section itself.
I haven't had a chance to properly review NCO JSON
Just looked a tiny bit more at CF_JSON, and see an issue right away:
"The data object contains the actual data for each variable as its
key:value members. Each data key MUST be the same as it variable ID key."
{
...
"variables": {
"tmp2m": {
"dimensions": ["time","lati
5213 <+44%20118%20378%205213> *M: *+44 (0)7919 112687
> <+44%207919%20112687>
>
> *E: *j.blo...@the-iea.org *W: *www.the-iea.org
>
>
>
> *From: *CF-metadata on behalf of David
> Johnson
> *Date: *Wednesday, 26 July 2017 02:01
> *To: *Sean Arms
> *Cc:
Cc: "cf-metadata@cgd.ucar.edu"
Subject: Re: [CF-metadata] JSON representation based on CF
Hi Sean,
Thanks very much for that reference. CovJSON looks really good, and fairly mature. Pity we weren't aware of this and didn't check this out a
Hi Folks,
My colleague recently brought this list to my attention and I was very happy to
see mention of CovJSON ☺
At NASA JPL’s PO.DAAC I have also been working with CovJSON manifestations of
our data offerings. Specifically, I’ve been working with a bunch of others on
the pycovjson [0] toolkit
The NCO implementation of JSON is fully documented here:
http://nco.sf.net/nco.html#json
All discussions on choices made for the implementation
are at the link Chris posted.
Sample input and output files are here:
http://dust.ess.uci.edu/tmp/in*
We welcome any discussion/feedback to improve/e
Hi Sean,
Thanks very much for that reference. CovJSON looks really good, and fairly
mature. Pity we weren't aware of this and didn't check this out a couple of
months ago!.
I think this would probably provide a full one-to-one mapping to CF-NetCDF,
which I think some will want. And seems to cover
Hello Dave,
I've been considering adding support for CoverageJSON to the TDS:
https://www.w3.org/TR/covjson-overview/
(Github page https://github.com/covjson/specification)
The spec specifically mentions CF-netCDF here:
https://www.w3.org/TR/covjson-overview/#netcdf
Cheers,
Sean
On Tue, Jul
There have been a few similar efforts.
One is the work in NCO -- not about CF per-se but about a way to translate
the netcdf data model to json -- once you've done that, the CF rules are
pretty much the same.
There was also an effort by Pedro Nunes at NESDIS/STAR:
http://www.space-research.org/b
Hello All,
Apologies if this is wrong place to post this. But I would like to draw
your attention to an open source initiative we have started:
cf-json.org.
The intention of this is to develop a standard around online exchange of
climate and weather data. Based firmly on CF conventions for NetCDF
16 matches
Mail list logo
