Public comment requested: CoverageJSON Community Standard

Status: 
Please note:  This Request is scheduled to close on 10 September 2022
Open Date: 
Thursday, 2022-08-11
Closing Date: 
Saturday, 2022-09-10

 

The Open Geospatial Consortium (OGC) is seeking public comment on the candidate CoverageJSON Community Standard. CoverageJSON is a format for publishing multi-dimensional data to the Web. 

The primary design goals for CoverageJSON are simplicity, machine and human readability, and efficiency in the storage and use of complex data. While other use cases are possible, the primary CoverageJSON use case is enabling the development of interactive visualizations to display and manipulate spatio-temporal data within a web browser.

CoverageJSON is based on the popular JavaScript Object Notation (JSON), and provides an effective, efficient format that’s friendly to web and application developers, and therefore consistent with the current OGC API developments. CoverageJSON supports the efficient transfer from big data stores of usable quantities of data to lightweight clients, such as browsers and mobile applications. This enables straightforward local manipulation of the data by users such as science researchers. 

The simplest and most common use-case is to embed all the data values of all variables in a Coverage object within the CoverageJSON document to create a self-contained, standalone, document that supports the use of very simple clients.

Another simple use case is to put data values for each variable (parameter) in separate array objects in separate CoverageJSON documents which are linked from a parent CoverageJSON object. This is useful for a multi-variable dataset, such as one with temperature, humidity, wind speed, etc., to be recorded in separate files. This allows the client to load only the variables of interest.

A sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially, like a tiled map server implementation.

This OGC Community Standard was an outcome of a European Union project, “Maximizing the Exploitation of Linked Open Data in Enterprise and Science” (MELODIES), run from 2013 to 2016, and released under a Creative Commons 4.0 License by the University of Reading. There are several widely-used open source implementations and libraries available.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.