[CF-metadata] Provide input on draft of STAC "Datacube" Extension
rmay at ucar.edu
Sun Jan 20 15:40:13 MST 2019
Can you enumerate some of the advances that STAC brings over the existing
THREDDS catalog spec?
>From what I can tell, a lot of the concepts are similar, and the existing
spec is already supported by tools beyond THREDDS, like Hyrax and ERDDAP. I
think JSON is great and all, but I'm curious what adding a new standard
brings us rather than extending an existing, already-supported standard?
On Fri, Jan 18, 2019 at 7:23 AM Ryan Abernathey <ryan.abernathey at gmail.com>
> Dear CF Conventions People,
> Some of you may be aware of the Spatio-Temporal Asset Catalog (STAC)
> STAC is basically a .json specification which aims to standardize the way
> geospatial assets are exposed online and queried. It originated from the
> geospatial imaging community, and is described in this blog post by Chris
> There is currently some discussion on the STAC repo about how STAC could
> be useful for netCDF-type data.
> This is a technology space that is currently occupied by THREDDS and
> OpenDAP. But something like STAC could be very useful for our community,
> especially as more netCDF-style data moves into the cloud.
> In particular, there is a proposed extension to STAC to describe "data
> cubes," which is roughly what geospatial imaging people call netCDF-type
> gridded datasets:
> I wanted to email this mailing list to see if someone from the CF
> community could weigh in on this proposed standard. More generally, if the
> CF / netCDF community wanted to engage with the STAC people more broadly, I
> think there is quite a bit of potential.
> Ryan Abernathey
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
Ryan May, Ph.D.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CF-metadata