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
Similarly to openEO that defines a list of predefined processes, Weaver can offer Buitin Processes that can be used to define multiple thematic operations.
For now, these operations are fairly limited, since the standardized OGC API - Processes approach of "Bring your own Process" is employed, which defines "How to describe a process", but not "Which processes are required".
More commonly used thematic processes should be integrated to facilitate their adoption and use. Notably, using ad-hoc CWL workflows would be simplified if most of the common/reusable parts of a workflow were predefined, robust and tested across multiple situations.
The tools should support namespaced IDs to facilitate thematic grouping (similar to what other references do).
They should also rely on available tools (dockerized application of existing CLIs) because of how well they are typically optimized, battle-tested and known to the communities.
Tools
These are some examples of potential tools or source of inspiration to implement capabilities:
CDO — The Climate Data Operator (CDO) software is a collection of many operators for standard processing of climate and forecast model data
pyramids-gis (not to be confused with pyramid API framework used by this repo!)
GIS utility package built on top of GDAL/OGR for working with raster data (GeoTIFF, NetCDF), vector data (shapefiles, GeoJSON), and multi-temporal datacubes.
Description
Similarly to openEO that defines a list of predefined processes, Weaver can offer Buitin Processes that can be used to define multiple thematic operations.
For now, these operations are fairly limited, since the standardized OGC API - Processes approach of "Bring your own Process" is employed, which defines "How to describe a process", but not "Which processes are required".
More commonly used thematic processes should be integrated to facilitate their adoption and use. Notably, using ad-hoc CWL workflows would be simplified if most of the common/reusable parts of a workflow were predefined, robust and tested across multiple situations.
The tools should support namespaced IDs to facilitate thematic grouping (similar to what other references do).
They should also rely on available tools (dockerized application of existing CLIs) because of how well they are typically optimized, battle-tested and known to the communities.
Tools
These are some examples of potential tools or source of inspiration to implement capabilities:
nckscombines selected features ofncdump,ncextr, and thenccutandncpastespecifications into one versatile utilityxclim— Climate service processes and indice computationgimi-tools— GeoTIFF (or any other really) to HEIF / GIMI image converter, tiling, etc.rasteriorasterio— GEO-image manipulationss2mosaicsupermorecadogeolibre-rustwhitebox_next_gen(similar to abovewhitebox-tools) andGeoLibrepyramids-gis(not to be confused withpyramidAPI framework used by this repo!)References