Re: update on coverages work [SEC=UNCLASSIFIED]

For 2.: would it help if we (me, GA and the netCDF-LD informal WG) made an example netCDF file with a speculative implementation of QB4ST defining the variables of that file in the headers? Or is that just way too much for a "simple example coverage" (perhaps too much implementation detail)?


What about using QB4ST to describe a theoretical chunk of spatial data like you would expect to see in a netCDF file, format non-specific?


Nick


________________________________
From: Bill Roberts <bill@swirrl.com>
Sent: 18 May 2017 01:14
To: public-sdw-wg@w3.org
Subject: update on coverages work

Hi all

Here's an update on the three Notes we've been working on.  The aim is to have them all finalised by end of May, for review and final editorial tweaks during June.

1. EO-QB

Editor's draft: http://w3c.github.io/sdw/eo-qb/

Dmitry and Sam following up a few remaining issues as listed in https://github.com/w3c/sdw/pull/742  (that PR has been merged)

2. QB4ST

Editor's draft: http://w3c.github.io/sdw/qb4st/

Main outstanding issue is for me to add an example of how the ontology would be applied to a simple example coverage.

3. CovJSON

Editor's draft: http://w3c.github.io/sdw/coverage-json/

Outstanding issues:
- Jon to talk to Scott Simmons about options for future standardisation work on the CoverageJSON format
- Jon to add some more illustrations
- Bill to sort out the references, with advice from Jon where needed
- Jon to tidy section 3.6 (relationship between CoverageJSON and RDF) then seek feedback from SDW group
- Bill to create cross-references to the BP doc
- Jon to address https://www.w3.org/2015/spatial/track/issues/101

Best regards

Bill



Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks.
-------------------------------------------------------------------------------------------------------------------------