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 ONLY time to merge some of this.
CF-JSON looks a little bit like a misnomer, or a maybe a different focus
that what I'd expect. What I"ve getting at is that CF is a metadata spec
(and maybe a data model) -- while it is quite tied to netcdf, it ISN'T
netcdf per se.
So if you what to express that kind of information in JSON, I think the
thing to do is specify how to map netcdf to JSON, and then simply apply the
same CF metadata standards.
Which is what NCO has done.
One couldn't of course, express the CF data model in JSON directly, without
specifically mapping to netcdf, though I think that would look very
similar, but not be as generally applicable.
At a quick glance, NCO's JSON and the CF-JSON spec are similar -- after
all, they are tryn gto do teh same thing -- but there are a lot of niggling
details to settle on, and I can only imagine independent efforts came up
with different solutions.
So I hope that the two groups (and the covjson folks) can get together and
converge to one thing!
-CHB
On Wed, Jul 26, 2017 at 9:13 AM, Jon Blower <j.d.blower at reading.ac.uk>
wrote:
> 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 _at_env_analytics
> <https://twitter.com/env_analytics> and on LinkedIn The Institute for
> Environmental Analytics (IEA)
> <https://www.linkedin.com/company/the-institute-for-environmental-analytics?trk=biz-companies-cymhttps://www.linkedin.com/company/the-institute-for-environmental-analytics?trk=biz-companies-cym>
>
>
>
> Philip Lyle Building, University of Reading, Whiteknights Campus, Reading
> RG6 6BX
>
> *T: *+44 (0)118 378 5213 <+44%20118%20378%205213> *M: *+44 (0)7919 112687
> <+44%207919%20112687>
>
> *E: *j.blower at the-iea.org *W: *www.the-iea.org
>
>
>
> *From: *CF-metadata <cf-metadata-bounces at cgd.ucar.edu> on behalf of David
> Johnson <d.johnson at metocean.co.nz>
> *Date: *Wednesday, 26 July 2017 02:01
> *To: *Sean Arms <sarms at ucar.edu>
> *Cc: *"cf-metadata at cgd.ucar.edu" <cf-metadata at 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:
>
> www.github.com/metocean/netcdfjs
>
> 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 <sarms at ucar.edu> wrote:
>
> 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 25, 2017 at 1:20 PM David Johnson <d.johnson at 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:
>
> 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. 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
>
>
>
> --
>
>
>
> [image: mage removed by sender. MetOcean Solutions Ltd]
> <http://www.metocean.co.nz/>
>
> *Dr David Johnson*
> Technical Director
> t: +64 7 825 0540 ext.1 <http://+6467585035/>02
> m: +64 2 <http://+64276853473/>1 057 1058
> www.metocean.co.nz
>
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
>
>
>
>
> --
>
>
>
> [image: mage removed by sender. MetOcean Solutions Ltd]
> <http://www.metocean.co.nz/>
>
> *Dr David Johnson*
> Technical Director
> t: +64 7 825 0540 ext.1 <http://+6467585035/>02
> m: +64 2 <http://+64276853473/>1 057 1058
> www.metocean.co.nz
>
>
>
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
>
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20170726/a405a9df/attachment.html>
Received on Wed Jul 26 2017 - 18:12:52 BST
