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 happy to provide advice on this, for example to support implementation in TDS, which would be great (we already have some libraries that might help here, although they are not complete).

 

In retrospect, I should have announced our progress on this list, although it wasn’t specifically CF-related. Apologies for that. The work was done partly within a joint OGC/W3C working group [3], and some members of the CF/NetCDF community were part of this.

 

My plan is to set up a working group for CovJSON, perhaps under the auspices of the OGC’s incubator programme, with a view to ultimately producing a standard. When this happens, I’ll be sure to invite members of this list to participate, as it would be great to have a wider group of people providing input.

 

David (and indeed anyone) – please feel free to make any comments on CovJSON. You can do this via email to me, or by raising an issue on the appropriate GitHub repositories [4].

 

CovJSON at the moment probably can’t cover the whole gamut of what is possible with CF. Things like cell methods, climatological time and a few other things are not supported. The focus was not on implementing CF in its entirety, but producing a (reasonably) simple JSON format to support the development of interactive websites. Some of the finer points of CF are less important for this kind of application. This could be a good topic of discussion in the incubator group.

 

There is a presentation [5] and overview slides [6], which might be a good way to get an overview of this project.

 

Hope this helps,
Jon

 

[1] http://www.melodiesproject.eu

[2] https://covjson.org

[3] https://www.w3.org/2015/spatial/wiki/Main_Page

[4] https://github.com/covjson

[5] https://ecmwf.adobeconnect.com/p6224btxzng/

[6] https://www.ecmwf.int/sites/default/files/elibrary/2017/17149-building-rich-and-interactive-web-applications-coveragejson.pdf

 

Jon Blower | CTO, Institute for Environmental Analytics

 

Follow the IEA on Twitter @env_analytics  and on LinkedIn The Institute for Environmental Analytics (IEA)

 

Philip Lyle Building, University of Reading, Whiteknights Campus, Reading RG6 6BX

T: +44 (0)118 378 5213 M: +44 (0)7919 112687 

E: j.blo...@the-iea.org W: www.the-iea.org

 

From: CF-metadata <cf-metadata-boun...@cgd.ucar.edu> on behalf of David Johnson <d.john...@metocean.co.nz>
Date: Wednesday, 26 July 2017 02:01
To: Sean Arms <sa...@ucar.edu>
Cc: "cf-metadata@cgd.ucar.edu" <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 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 all the needs we were trying to address with CF-JSON. And more besides.

 

Hopefully we will see widespread uptake and community acceptance. Getting into TDS would certainly be a step in the right direction.

 

This is good and exactly what these kinds of lists are for. And one less project to worry about. We will focus on our _javascript_ NetCDF reader instead:

Unless of course somewhere is aware of another project dealing with that!

 

Cheers, Dave

 

On Wed, Jul 26, 2017 at 12:21 PM, Sean Arms <sa...@ucar.edu> wrote:

Hello Dave,

 

I've been considering adding support for CoverageJSON to the TDS:

 

 

 

The spec specifically mentions CF-netCDF here:

 

 

Cheers,

 

Sean

 

On Tue, Jul 25, 2017 at 1:20 PM David Johnson <d.john...@metocean.co.nz> wrote:

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:

 

The intention of this is to develop a standard around online exchange of climate and weather data. Based firmly on CF conventions for NetCDF. This was in response to the lack of any obvious standards for JSON. The transfer of weather data via RESTful services is now widespread and JSON is a common format for this. The geospatial community have geojson so we figured we need something similar. We are using this internally, but would be happy to see wider adoption. 

 

Pleased to have any feedback and/or knowledge of other existing efforts in this space.

 

Best regards,

Dave

 

-- 

 

mage removed by sender. MetOcean Solutions Ltd

Dr David Johnson
Technical Director 
t: +64 7 825 0540 ext.102 
m: +64 21 057 1058
www.metocean.co.nz

_______________________________________________
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata



 

--

 

mage removed by sender. MetOcean Solutions Ltd

Dr David Johnson
Technical Director 
t: +64 7 825 0540 ext.102 
m: +64 21 057 1058
www.metocean.co.nz

 

_______________________________________________
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata

Reply via email to