1.7.0

Changes in 1.7.0

Full Changelog: v1.6.0...v1.7.0

Enhancements

• Bundled xcube-viewer 1.3.0.

• xcube server can now deal with "user-defined" variables. Endpoints
  that accept a {varName} path parameter in their URL path can now be
  called with assignment expressions of the form <var_name>=<var_expr>
  where <var_name> is the name user defined variable and <var_expr>
  is an arbitrary band-math expression,
  see xcube-dev/xcube-viewer#371.

• xcube server now allows for configuring new dataset properties
  GroupTitle and Tags . This feature has been added in order to support
  grouping and filtering of datasets in UIs,
  see xcube-dev/xcube-viewer#385.

• Added server endpoint GET /statistics/{varName} with query parameters
  lon, lat, time which is used to extract single point data.
  This feature has been added in order to support
  xcube-dev/xcube-viewer#404.

• The xcube server STAC API now publishes all fields available via the
  /datasets endpoint. This includes colormap information for each asset such as
  colorBarName, colorBarNorm, colorBarMin, colorBarMax, tileLevelMin, tileLevelMax.
  (#935, #940)

• xcube server now allows for configuring custom color maps via the configuration file.
  It supports continuous, stepwise and categorical colormaps, which may be
  configured as shown in the section CustomColorMaps of the xcube serve documentation
  (#1055)

Fixes

• Migrated the .github/workflows/xcube_build_docker.yaml and the corresponding
  Dockerfile from setup.py to pyproject.toml. Additionally, updated the relevant
  documentation in doc/source to reflect this change from setup.py to
  pyproject.toml. (related to #992)
• Normalisation with xcube.core.normalize.normalize_dataset fails when chunk encoding
  must be updated (#1033)
• The open_data method of xcube's default xcube.core.store.DataStore implementations
  now supports a keyword argument data_type, which determines the
  data type of the return value. Note that opener_id includes the data_type
  at its first position and will override the data_type argument.
  To preserve backward compatibility, the keyword argument data_type
  has not yet been literally specified as open_data() method argument,
  but may be passed as part of **open_params. (#1030)
• The xcube.core.store.DataDescriptor class now supports specifying time ranges
  using both datetime.date and datetime.datetime objects. Previously,
  only datetime.date objects were supported.
• The xcube server STAC API has been adjusted so that the data store
  parameters and data ID, which are needed to open the data referred to by a STAC item,
  are now included with the item's analytic asset.
  Furthermore, a second assert called analytic_multires will be published
  referring to the multi-resolution data format levels (#1020).
• Improved the way color mapping works in xcube server to support simplified
  color bar management in xcube viewer,
  see xcube-dev/xcube-viewer#390. (#1043)
• The xcube server's dataset configuration extraction methodology has been updated.
  When the data resource ID is provided in the Path field, xcube will attempt to
  access the dataset using the given ID. If wildcard patterns are used, the server
  will crawl through the data store to find matching data IDs. This process may
  result in a long setup time if the data store contains numerous data IDs.
  A UserWarning will be issued for the "stac" data store.
• Corrected extent object of a STAC collection issued by xcube server, following the
  collection STAC specifications
  (#1053)
• When opening a GeoTIFF file using a file system data store, the default return value
  is changed from MultiLevelDataset to xr.Dataset, if no data_type is assigned
  in the open_params of the store.open_data() method. (#1054)
  xcube server has been adapted to always open MultiLevelDatasets from
  a specified data store, if that data type is supported.

Other changes

• Renamed internal color mapping types from "node", "bound", "key"
  into "continuous", "stepwise", "categorical".