Skip to content

Releases: xcube-dev/xcube-viewer

0.12.0-dev.0

11 Jul 09:53
Compare
Choose a tag to compare
0.12.0-dev.0 Pre-release
Pre-release

Changes in version 0.12.0 (in development)

Enhancements

  • xcube Viewer can now be used with any OIDC 1.0 compliant auth service.

Enhancements

  • A new refresh icon in the main bar now allows updating
    server-side resources and refresh the page.
    For this to work, the configuration setting
    branding.allowRefresh must be true.

  • The viewer app can now display also 2D datasets published by
    xcube server (starting with xcube version 0.11.3).

0.11.1

18 May 08:35
Compare
Choose a tag to compare

Changes in version 0.11.1

Enhancements

  • The viewer app can now be called with query parameters that
    preselect the dataset and variable to be displayed.
    The query parameters are dataset and variable. (#207)

    For example, when using the demo configuration, we can preselect
    dataset with ID remote and the variable named kd489:

    http://localhost:3000/?dataset=remote&variable=kd489
    
  • The performance of time-series fetching has been significantly improved
    by exploiting the actual chunk sizes of the time dimension of a variable.
    For this to work, the setting "Number of data points in a time series update"
    has been replaced by "Minimal number of data points in a time series update".
    The effective number of data points is now always an integer multiple of the
    actual variable's time chunk size.

  • The style of the title and icons of the app's header bar can now be
    customized by two new branding properties and that can provide
    any CCS attributes (using camel-case attribute names). (#227)

    For example

    {   
      "branding": {
        "headerTitleStyle": {
          "fontFamily": "courier",
          "color": "yellow"
        },
        "headerIconStyle": {
          "color": "black"
        },
        ...
      },
      ...
    }
  • In the info panel, the dataset's spatial reference system is shown. (#225)

  • It is now possible to display dataset boundaries in the map.
    A new setting "Show dataset boundaries" is available to switch this
    feature on and off. (#226)

Fixes

  • Fixed a bug that caused the app to crash when zooming into the
    time-series chart. (#163)

  • Text selection has now been disabled for the time-series charts.
    Zooming in no longer selects the axes' labels.

Full Changelog: v0.11.0...v0.11.1

0.11.0

20 Apr 14:43
583fe92
Compare
Choose a tag to compare

Changes in version 0.11.0

Enhancements

  • Thanks to using xcube Server 0.11.x, xcube Viewer 0.11.x can now display datasets with non-geographic spatial coordinate reference systems, for example UTM or LAEA Europe (EPSG:3035).
  • The map projection can now be changed in the settings dialog. Possible value are "Geographic" and "Web Mercator".
  • Now the opacity of tile layers can be changed from the color bar dropdown component in the map.

Other Changes

  • xcube Viewer 0.11.x requires xcube Server 0.11.x.
  • The default map projection changed from Geographic (EPSG:4326) to Spherical Mercator (EPSG:3857). Accordingly, image tiles are requested in Spherical Mercator projection (using the same tile grid as OSM)

Fixes

  • Fixed a problem that occurred with datasets referring to the same place group. In this case, only the first dataset received the features on place group reload. Now all datasets referring to that place group are updated on feature reload. (#208)
  • Fixed a problem that prevented setting the map projection using the branding.mapProjection configuration key.

0.11.0-dev.1

14 Apr 07:17
75cb346
Compare
Choose a tag to compare
0.11.0-dev.1 Pre-release
Pre-release

Changes in version 0.11.0 (in development)

Enhancements

  • Thanks to using xcube Server 0.11.x, xcube Viewer 0.11.x can now display
    datasets with non-geographic spatial coordinate reference systems,
    for example UTM or LAEA Europe (EPSG:3035).

  • The map projection can now be changed in the settings dialog.
    Possible value are "Geographic" and "Web Mercator".

  • Now the opacity of tile layers can be changed from the color bar
    dropdown component in the map.

Other Changes

  • xcube Viewer 0.11.x requires xcube Server 0.11.x.

  • The default map projection changed from Geographic (EPSG:4326) to Spherical
    Mercator (EPSG:3857). Accordingly, image tiles are requested in Spherical
    Mercator projection (using the same tile grid as OSM)

Fixes

  • Fixed a problem that occurred with datasets referring to the
    same place group. In this case, only the first dataset received
    the features on place group reload. Now all datasets
    referring to that place group are updated on feature reload.
    (#208)

  • Fixed a problem that prevented setting the map projection
    using the branding.mapProjection configuration key.

0.11.0-dev.0

29 Mar 07:27
Compare
Choose a tag to compare
0.11.0-dev.0 Pre-release
Pre-release

Changes in version 0.11.0 (in development)

Enhancements

  • Thanks to using xcube Server 0.11.x, xcube Viewer 0.11.x can now display
    datasets with non-geographic spatial coordinate reference systems,
    for example UTM or LAEA Europe (EPSG:3035).

Other Changes

  • xcube Viewer 0.11.x requires xcube Server 0.11.x.

  • The default map projection changed from Geographic (EPSG:4326) to Spherical
    Mercator (EPSG:3857). Accordingly, image tiles are requested in Spherical
    Mercator projection (using the same tile grid as OSM)

0.10.1

23 Feb 14:59
Compare
Choose a tag to compare

Changes in version 0.10.1

Enhancements

  • The map projection can now be configured using the
    branding.mapProjection key. Possible values are the default
    "EPSG:4326" (Geographic) and
    "EPSG:3857" (Spherical Mercator).

Fixes

  • Feature geometries loaded from xcube Places API are now rendered again
    in the map.

  • Addressed warning saying Using target="_blank" without rel="noreferrer" is a security risk

0.10.0

10 Feb 16:37
Compare
Choose a tag to compare

Changes in version 0.10.0

Note: version number jumped from 0.4.x to 0.10 to be in line with xcube 0.10.

Enhancements

  • The logo in the application's main bar is now a link.
    The target URL can be configured using the
    branding.organisationUrl key. (#176)

  • Users can now manually enter a variable's min/max values that are
    applied to the selected color bar. The editor that pops up
    when clicking the value range scale in the variable legend overlay.
    (#140)

  • The viewer's map now uses EPSG:4326 projection as default so datasets
    that use this grid too will have image layers showing square pixels.

  • Reduced layer flickering when a new time step is selected.
    Layer transitions are now performed more smoothly. (#119)

  • We can now turn off image smoothing just for the variable layer.
    The background map is no longer concerned by this setting and
    therefore preserves its quality. (#181)

  • Simplified use of xcube-viewer as a container. (#167)

    The ultimate goal of this activity was to get rid of build-time
    configuration and replace it by runtime configuration.
    This introduced some breaking changes as follows.
    We no longer use .env files for build-time configuration.
    Instead, a runtime configuration is initially loaded:

    1. If query parameter configPath is given, it is loaded from
      {origin}/{configPath}/config.json.
    2. Otherwise, it is loaded from {origin}/config/config.json.
    3. If the configuration could not be fetched, the default configuration
      src/resources/config.json is used instead.

    The first option is useful for development. For example, if the app is
    loaded from URL {origin}?configPath=config/myapp, its configuration is
    loaded from {origin}/config/myapp/config.json where configuration
    resources are placed in public/config/myapp/. For this purpose
    public/config/ is in .gitignore.

    The JSON schema for the configuration is given in
    src/resources/config.schema.json.

Fixes

  • Fixed issue with datasets originating from nested, filesystem-based
    data stores such as the "s3" and "file" data stores. See also
    related xcube-dev/xcube#579.
    (#190)

  • Fixed numerous base maps (#197)

    • Where possible, switched from HTTP to HTTPS.
    • Removed all Stamen maps - for not supporting HTTPS
    • Removed all Mapbox maps - no longer freely accessible
    • Removed selected OpenStreetMap maps:
      • OSM Black & White - no longer maintained and provided
      • OSM Landscape - no longer freely accessible
  • Fixed eslint warnings of type "'ACTION' is already defined" during build.

Issues addressed

Full Changelog: v0.4.5...v0.10.0

0.5.0-dev.2

19 Jan 15:41
486f348
Compare
Choose a tag to compare
0.5.0-dev.2 Pre-release
Pre-release

Changes in version 0.5.0 (in development)

Enhancements

  • The logo in the application's main bar is now a link.
    The target URL can be configured using the
    branding.organisationUrl key. (#176)

  • Users can now manually enter a variable's min/max values that are
    applied to the selected color bar. The editor that pops up
    when clicking the value range scale in the variable legend overlay.
    (#140)

  • The viewer's map now uses EPSG:4326 projection as default so datasets
    that use this grid too will have image layers showing square pixels.

  • Reduced layer flickering when a new time step is selected.
    Layer transitions are now performed more smoothly. (#119)

  • We can now turn off image smoothing just for the variable layer.
    The background map is no longer concerned by this setting and
    therefore preserves its quality. (#181)

  • Simplified use of xcube-viewer as a container. (#167)

    The ultimate goal of this activity was to get rid of build-time
    configuration and replace it by runtime configuration.
    This introduced some breaking changes as follows.
    We no longer use .env files for build-time configuration.
    Instead, a runtime configuration is initially loaded:

    1. If query parameter configPath is given, it is loaded from
      {origin}/{configPath}/config.json.
    2. Otherwise, it is loaded from {origin}/config/config.json.
    3. If the configuration could not be fetched, the default configuration
      src/resources/config.json is used instead.

    The first option is useful for development. For example, if the app is
    loaded from URL {origin}?configPath=config/myapp, its configuration is
    loaded from {origin}/config/myapp/config.json where configuration
    resources are placed in public/config/myapp/. For this purpose
    public/config/ is in .gitignore.

    The JSON schema for the configuration is given in
    src/resources/config.schema.json.

Fixes

  • Fixed issue with datasets originating from nested, filesystem-based
    data stores such as the "s3" and "file" data stores. See also
    related xcube-dev/xcube#579.
    (#190)

  • Fixed eslint warnings of type "'ACTION' is already defined" during build.

0.5.0-dev.1

18 Jan 17:03
Compare
Choose a tag to compare
0.5.0-dev.1 Pre-release
Pre-release

Changes in version 0.5.0 (in development)

  • Users can now manually enter a variable's min/max values that are
    applied to the selected color bar. The editor that pops up
    when clicking the value range scale in the variable legend overlay.
    (#140)

  • The viewer's map now uses EPSG:4326 projection as default so datasets
    that use this grid too will have image layers showing square pixels.

  • Reduced layer flickering when a new time step is selected.
    Layer transitions are now performed more smoothly. (#119)

  • We can now turn off image smoothing just for the variable layer.
    The background map is no longer concerned by this setting and
    therefore preserves its quality. (#181)

  • Simplified use of xcube-viewer as a container. (#167)

    The ultimate goal of this activity was to get rid of build-time
    configuration and replace it by runtime configuration.
    This introduced some breaking changes as follows.
    We no longer use .env files for build-time configuration.
    Instead, a runtime configuration is initially loaded:

    1. If query parameter configPath is given, it is loaded from
      {origin}/{configPath}/config.json.
    2. Otherwise, it is loaded from {origin}/config/config.json.
    3. If the configuration could not be fetched, the default configuration
      src/resources/config.json is used instead.

    The first option is useful for development. For example, if the app is
    loaded from URL {origin}?configPath=config/myapp, its configuration is
    loaded from {origin}/config/myapp/config.json where configuration
    resources are placed in public/config/myapp/. For this purpose
    public/config/ is in .gitignore.

    The JSON schema for the configuration is given in
    src/resources/config.schema.json.

  • Fixed eslint warnings of type "'ACTION' is already defined" during build.

0.4.5

13 Apr 11:41
Compare
Choose a tag to compare

Changes in version 0.4.5

  • After logging out, the browser now correctly redirects to the
    viewer's origin. (#142)

  • Default colour for dataset-related place groups now red while
    initial user places colour is yellow. (#153)

  • RGB layer no longer hides places. (#152)

  • Users can now download time-series data as a Zip archive
    containing a GeoJSON file for each time-series graph. (#20)

    Note, this new feature must be enabled in .env:

    REACT_APP_ALLOW_DOWNLOADS=1
    
  • The opacity of polygon fill colours has been made part the
    app's branding.

  • Language setting is now correctly preserved and will be
    used on page reload. (#158)