You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of #1563 implementation of geo-spatial data type it is now possible to introduce geoJSON data objects in the VCs/VPs and scemas in the Guardian. However much of historic geographic data, specifically satellite imagery, is stored in geoTIFF format. Also see https://www.sentinel-hub.com data and API for such archives. Such data also needs to be natively supported by Guardian.
Requirements
Introduce support for geoTIFF and other raster types of data such that:
Guardian documents (i.e. in schemas) can reference raster data (in geoTIFF and other common formats) which are located on external (3rd party) systems.
Guardian UI can display raster images and their geo-referencing data when they are encountered in documents.
Guardian policy can access and manipulate (use in calculations, etc) data from raster sources.
Definition of done
Introduced support for raster data into Guardian policies and documents
Documentation updated accordingly
At a minimum a single example of using raster data is introduced into Guardian sample policies
Acceptance criteria
Guardian can work out of the box with raster data from one of the following sources:
Guardian supports at a minimum geoTIFF and other common image formats (jpeg, png, etc)
Subsets of data from the raster image can be extracted into a variable (of a suitable type), and then further used in the policy calculations via custom logic block
Auxiliary info
Raster description
Rasters may be stored in any number of formats or containers. They are typically stored in a binary format for the sake of efficiency, but plaintext formats are not uncommon.
Geo-referencing information for raster images is embedded either directly in the header of the container file, or via ancillary files that are distributed with the raster. A world file is a common example of the latter approach, where a separate plaintext file describes the position in geographic space of the center of the upper-left pixel, as well as the x and y resolution of the raster.
External references
Docs page offering good explanation of what raster data is.
Problem description
As of #1563 implementation of geo-spatial data type it is now possible to introduce geoJSON data objects in the VCs/VPs and scemas in the Guardian. However much of historic geographic data, specifically satellite imagery, is stored in geoTIFF format. Also see https://www.sentinel-hub.com data and API for such archives. Such data also needs to be natively supported by Guardian.
Requirements
Introduce support for geoTIFF and other raster types of data such that:
Definition of done
Acceptance criteria
Auxiliary info
Raster description
Rasters may be stored in any number of formats or containers. They are typically stored in a binary format for the sake of efficiency, but plaintext formats are not uncommon.
Geo-referencing information for raster images is embedded either directly in the header of the container file, or via ancillary files that are distributed with the raster. A world file is a common example of the latter approach, where a separate plaintext file describes the position in geographic space of the center of the upper-left pixel, as well as the x and y resolution of the raster.
External references
The text was updated successfully, but these errors were encountered: