3.1.0.dev1

Changes 3.1.0 (in development)

• Do not request production status for development version

3.1.0.dev0

Changes 3.1.0 (in development)

• Adapted to Cate Web API 3.1.x which changed in an
  incompatible way. Dataset descriptors now have a data_type
  field instead of a type_specifier field in 3.0.x.

3.0.1

Changes 3.0.1

• Implemented a workaround for an issue that prevented user logins once a certain server-side degree of capacity utilisation was reached. (#156)

3.0.0

Changes 3.0.0

• Cate App 3.0 now requires the Web API service of the cate 3.0+
  Python package.

• In order to keep alive the connection to the Web API service,
  Cate App now sends a keepalive signal every 2.5 seconds. (#150)

• For faster opening of datasets, the value of the currently selected
  data store data_store_id is now passed to the open_dataset
  operation.

• Fixed a bug with user preferences not being saved correctly. (#146)

• Optimisations in the DATA SOURCES panel (that have been enabled by
  using xcube in the backend):

  • Initialising the "CCI Open Data Portal" data store
    is now accelerated by a magnitude.
  • Local caching of remote data sources when opening datasets
    is now much faster and more reliable.
  • Added new experimental store "CCI Zarr Store" that offers
    selected CCI datasets that have been converted to Zarr format
    and are read from JASMIN object storage.
  • Ability to add more data stores has been greatly improved.
  • Enhanced the "Open Dataset" dialog by messages that tell
    why a certain constraint is not (yet) available.
  • Fixed icons and labels for some new CCI ECVs.
  • Cate now utilizes dataset capabilities such as the ability
    to create spatial or temporal subsets in the "Open Data Source"
    dialog. In case a dataset has no such capabilities, we compute
    them from the dataset's metadata, if possible.

• We now obtain Cate Hub's status information from a dedicated GitHub
  repository cate-status.

• Adapted to changed cate-hub API. (An API response no longer has
  status and result properties, instead a response is the result,
  and the response status is represented by the HTTP response code.)

• Improved rendering of text in many places by making it user-selectable
  and interpreting it as markdown:

  • Data source abstract in the DATA SOURCES details panel:
  • Operation description in OPERATIONS panel.

• Other:

  • Simplified Dockerfile which now uses a 2-stage build.
  • No longer require .env.production and .env.local files
    because all settings now have reasonable defaults.
  • Removed phrase "please check .cate/webapi.log" from some
    error messages, because users have no longer access to
    log files.
  • Renamed "About" tab in Preferences Dialog into "System".
    There we now also display the versions of Cate's core Python
    package dependencies.

3.0.0-dev.7

Changes 3.0 (in development)

• Cate App 3.0 now requires the Web API service of the cate 3.0+
  Python package.

• In order to keep alive the connection to the Web API service,
  Cate App now sends a keepalive signal every 2.5 seconds. (#150)

• For faster opening of datasets, the value of the currently selected
  data store data_store_id is now passed to the open_dataset
  operation.

• Fixed a bug with user preferences not being saved correctly. (#146)

• Optimisations in the DATA SOURCES panel (that have been enabled by
  using xcube in the backend):

  • Initialising the "CCI Open Data Portal" data store
    is now accelerated by a magnitude.
  • Local caching of remote data sources when opening datasets
    is now much faster and more reliable.
  • Added new experimental store "CCI Zarr Store" that offers
    selected CCI datasets that have been converted to Zarr format
    and are read from JASMIN object storage.
  • Ability to add more data stores has been greatly improved.
  • Enhanced the "Open Dataset" dialog by messages that tell
    why a certain constraint is not (yet) available.
  • Fixed icons and labels for some new CCI ECVs.
  • Cate now utilizes dataset capabilities such as the ability
    to create spatial or temporal subsets in the "Open Data Source"
    dialog. In case a dataset has no such capabilities, we compute
    them from the dataset's metadata, if possible.

• We now obtain Cate Hub's status information from a dedicated GitHub
  repository cate-status.

• Adapted to changed cate-hub API. (An API response no longer has
  status and result properties, instead a response is the result,
  and the response status is represented by the HTTP response code.)

• Improved rendering of text in many places by making it user-selectable
  and interpreting it as markdown:

  • Data source abstract in the DATA SOURCES details panel:
  • Operation description in OPERATIONS panel.

• Other:

  • Simplified Dockerfile which now uses a 2-stage build.
  • No longer require .env.production and .env.local files
    because all settings now have reasonable defaults.
  • Removed phrase "please check .cate/webapi.log" from some
    error messages, because users have no longer access to
    log files.
  • Renamed "About" tab in Preferences Dialog into "System".
    There we now also display the versions of Cate's core Python
    package dependencies.

3.0.0-dev.6

Changes 3.0 (in development)

• Cate App 3.0 now requires the Web API service of the cate 3.0+
  Python package.

• In order to keep alive the connection to the Web API service,
  Cate App now sends a keepalive signal every 2.5 seconds. (#150)

• For faster opening of datasets, the value of the currently selected
  data store data_store_id is now passed to the open_dataset
  operation.

• Fixed a bug with user preferences not being saved correctly. (#146)

• Optimisations in the DATA SOURCES panel (that have been enabled by
  using xcube in the backend):

  • Initialising the "CCI Open Data Portal" data store
    is now accelerated by a magnitude.
  • Local caching of remote data sources when opening datasets
    is now much faster and more reliable.
  • Added new experimental store "CCI Zarr Store" that offers
    selected CCI datasets that have been converted to Zarr format
    and are read from JASMIN object storage.
  • Ability to add more data stores has been greatly improved.
  • Enhanced the "Open Dataset" dialog by messages that tell
    why a certain constraint is not (yet) available.
  • Fixed icons and labels for some new CCI ECVs.
  • Cate now utilizes dataset capabilities such as the ability
    to create spatial or temporal subsets in the "Open Data Source"
    dialog. In case a dataset has no such capabilities, we compute
    them from the dataset's metadata, if possible.

• We now obtain Cate Hub's status information from a dedicated GitHub
  repository cate-status.

• Adapted to changed cate-hub API. (An API response no longer has
  status and result properties, instead a response is the result,
  and the response status is represented by the HTTP response code.)

• Improved rendering of text in many places by making it user-selectable
  and interpreting it as markdown:

  • Data source abstract in the DATA SOURCES details panel:
  • Operation description in OPERATIONS panel.

• Other:

  • Simplified Dockerfile which now uses a 2-stage build.
  • No longer require .env.production and .env.local files
    because all settings now have reasonable defaults.
  • Removed phrase "please check .cate/webapi.log" from some
    error messages, because users have no longer access to
    log files.
  • Renamed "About" tab in Preferences Dialog into "System".
    There we now also display the versions of Cate's core Python
    package dependencies.

3.0.0-dev.5

Changes 3.0 (in development)

• Cate App 3.0 now requires the Web API service of the cate 3.0+
  Python package.

• In order to keep alive the connection to the Web API service,
  Cate App now sends a keepalive signal every 2.5 seconds. (#150)

• For faster opening of datasets, the value of the currently selected
  data store data_store_id is now passed to the open_dataset
  operation.

• Fixed a bug with user preferences not being saved correctly. (#146)

• Optimisations in the DATA SOURCES panel (that have been enabled by
  using xcube in the backend):

  • Initialising the "CCI Open Data Portal" data store
    is now accelerated by a magnitude.
  • Local caching of remote data sources when opening datasets
    is now much faster and more reliable.
  • Added new experimental store "CCI Zarr Store" that offers
    selected CCI datasets that have been converted to Zarr format
    and are read from JASMIN object storage.
  • Ability to add more data stores has been greatly improved.
  • Enhanced the "Open Dataset" dialog by messages that tell
    why a certain constraint is not (yet) available.
  • Fixed icons and labels for some new CCI ECVs.
  • Cate now utilizes dataset capabilities such as the ability
    to create spatial or temporal subsets in the "Open Data Source"
    dialog. In case a dataset has no such capabilities, we compute
    them from the dataset's metadata, if possible.

• We now obtain Cate Hub's status information from a dedicated GitHub
  repository cate-status.

• Adapted to changed cate-hub API. (An API response no longer has
  status and result properties, instead a response is the result,
  and the response status is represented by the HTTP response code.)

• Improved rendering of text in many places by making it user-selectable
  and interpreting it as markdown:

  • Data source abstract in the DATA SOURCES details panel:
  • Operation description in OPERATIONS panel.

• Other:

  • Simplified Dockerfile which now uses a 2-stage build.
  • No longer require .env.production and .env.local files
    because all settings now have reasonable defaults.
  • Removed phrase "please check .cate/webapi.log" from some
    error messages, because users have no longer access to
    log files.
  • Renamed "About" tab in Preferences Dialog into "System".
    There we now also display the versions of Cate's core Python
    package dependencies.

3.0.0-dev.4

Changes 3.0 (in development)

• Cate App 3.0 now requires the Web API service of the cate 3.0+
  Python package.

• In order to keep alive the connection to the Web API service,
  Cate App now sends a keepalive signal every 2.5 seconds. (#150)

• For faster opening of datasets, the value of the currently selected
  data store data_store_id is now passed to the open_dataset
  operation.

• Fixed a bug with user preferences not being saved correctly. (#146)

• Optimisations in the DATA SOURCES panel (that have been enabled by
  using xcube in the backend):

  • Initialising the "CCI Open Data Portal" data store
    is now accelerated by a magnitude.
  • Local caching of remote data sources when opening datasets
    is now much faster and more reliable.
  • Added new experimental store "CCI Zarr Store" that offers
    selected CCI datasets that have been converted to Zarr format
    and are read from JASMIN object storage.
  • Ability to add more data stores has been greatly improved.
  • Enhanced the "Open Dataset" dialog by messages that tell
    why a certain constraint is not (yet) available.
  • Fixed icons and labels for some new CCI ECVs.

• We now obtain Cate Hub's status information from a dedicated GitHub
  repository cate-status.

• Adapted to changed cate-hub API. (An API response no longer has
  status and result properties, instead a response is the result,
  and the response status is represented by the HTTP response code.)

• Improved rendering of text in many places by making it user-selectable
  and interpreting it as markdown:

  • Data source abstract in the DATA SOURCES details panel:
  • Operation description in OPERATIONS panel.

• Other:

  • Simplified Dockerfile which now uses a 2-stage build.
  • No longer require .env.production and .env.local files
    because all settings now have reasonable defaults.
  • Removed phrase "please check .cate/webapi.log" from some
    error messages, because users have no longer access to
    log files.
  • Renamed "About" tab in Preferences Dialog into "System".
    There we now also display the versions of Cate's core Python
    package dependencies.

3.0.0-dev.3

Changes 3.0 (in development)

• Cate App 3.0 now requires the Web API service of the cate 3.0+
  Python package.

• In order to keep alive the connection to the Web API service,
  Cate App now sends a keepalive signal every 2.5 seconds. (#150)

• For faster opening of datasets, the value of the currently selected
  data store data_store_id is now passed to the open_dataset
  operation.

• Fixed a bug with user preferences not being saved correctly. (#146)

• Optimisations in the DATA SOURCES panel (that have been enabled by
  using xcube in the backend):

  • Initialising the "CCI Open Data Portal" data store
    is now accelerated by a magnitude.
  • Local caching of remote data sources when opening datasets
    is now much faster and more reliable.
  • Added new experimental store "CCI Zarr Store" that offers
    selected CCI datasets that have been converted to Zarr format
    and are read from JASMIN object storage.
  • Ability to add more data stores has been greatly improved.
  • Enhanced the "Open Dataset" dialog by messages that tell
    why a certain constraint is not (yet) available.
  • Fixed icons and labels for some new CCI ECVs.

• We now obtain Cate Hub's status information from a dedicated GitHub
  repository cate-status.

• Adapted to changed cate-hub API. (An API response no longer has
  status and result properties, instead a response is the result,
  and the response status is represented by the HTTP response code.)

• Improved rendering of text in many places by making it user-selectable
  and interpreting it as markdown:

  • Data source abstract in the DATA SOURCES details panel:
  • Operation description in OPERATIONS panel.

• Other:

  • Simplified Dockerfile which now uses a 2-stage build.
  • No longer require .env.production and .env.local files
    because all settings now have reasonable defaults.
  • Removed phrase "please check .cate/webapi.log" from some
    error messages, because users have no longer access to
    log files.
  • Renamed "About" tab in Preferences Dialog into "System".
    There we now also display the versions of Cate's core Python
    package dependencies.

3.0.0-dev.2

Changes 3.0 (in development)

• Cate App 3.0 now requires the Web API service of the cate 3.0+
  Python package.

• In order to keep alive the connection to the Web API service,
  Cate App now sends a keepalive signal every 2.5 seconds. (#150)

• For faster opening of datasets, the value of the currently selected
  data store data_store_id is now passed to the open_dataset
  operation.

• Fixed a bug with user preferences not being saved correctly. (#146)

• Optimisations in the DATA SOURCES panel (that have been enabled by
  using xcube in the backend):

  • Initialising the "CCI Open Data Portal" data store
    is now accelerated by a magnitude.
  • Local caching of remote data sources when opening datasets
    is now much faster and more reliable.
  • Added new experimental store "CCI Zarr Store" that offers
    selected CCI datasets that have been converted to Zarr format
    and are read from JASMIN object storage.
  • Ability to add more data stores has been greatly improved.
  • Enhanced the "Open Dataset" dialog by messages that tell
    why a certain constraint is not (yet) available.
  • Fixed icons and labels for some new CCI ECVs.

• We now obtain Cate Hub's status information from a dedicated GitHub
  repository cate-status.

• Adapted to changed cate-hub API. (An API response no longer has
  status and result properties, instead a response is the result,
  and the response status is represented by the HTTP response code.)

• Improved rendering of text in many places by making it user-selectable
  and interpreting it as markdown:

  • Data source abstract in the DATA SOURCES details panel:
  • Operation description in OPERATIONS panel.

• Simplified Dockerfile which now uses a 2-stage build.

• No longer require .env.production and .env.local files
  because all settings now have reasonable defaults.