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
At a really quick glance, it looks like CovJSON has a different mission
that "CF-json" or "netcdf-json". But they do sure overlap, so I hope we can
not have TOO many overlapping yet different JSON specs out there.
None of these are very mature or widely adopted -- so now it a good time
(indeed the
Hi Antonio,
Yes, we will have remote participation available.
Cheers,
Ethan
On Wed, Jul 26, 2017 at 1:28 PM, Antonio S. Cofiño wrote:
> Hi Ethan,
>
> There is any chance to enable remote virtual participation into this
> workshop?
>
> Thank you and regards
>
> Antonio
>
>
> --
> Antonio S. Co
Hi Ethan,
There is any chance to enable remote virtual participation into this
workshop?
Thank you and regards
Antonio
--
Antonio S. Cofiño
Associate Professor and Researcher
Grupo de Meteorología de Santander
Dep. of Applied Mathematics and Computer Sciences
Universidad de Cantabria (Spain
Hi all,
As many of you know, we are holding an "Advancing netCDF-CF" workshop [1]
on 6-8 September 2017 at UCAR in Boulder, CO USA. This workshop will focus
on efforts to advance the Climate and Forecast (CF) metadata conventions
for netCDF (netCDF-CF). The meeting is being hosted by the EarthCube
Hi all,
Just to introduce myself – I managed the project [1] that yielded CovJSON [2]. It was developed mostly by my colleague Maik Riechert, with occasional input from me. We managed to get it
to a reasonable state of maturity, but it would be great to see wider uptake – I’m very hap
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