Unify Indicators provided by different Agencies

eurodatacube / eodash

Software behind the RACE dashboard by ESA and the European Commission (https://race.esa.int), the Green Transition Information Factory - GTIF (https://gtif.esa.int), as well as the Earth Observing Dashboard by NASA, ESA, and JAXA (https://eodashboard.org)

https://race.esa.int

MIT License

94 stars 42 forks source link

Unify Indicators provided by different Agencies #500

Closed silvester-pari closed 4 years ago

silvester-pari commented 4 years ago

into a single view

Currently:

Multiple entries in the table and on map for the same indicator, e.g. North Adriatic – Chl-a maps

Aim:

A single entry in the table and on map per indicator

Example: In the new visualisation, we would have a single entry for NorthAdriatic – Chl maps in the table.

We could distinguish between data coming from different agencies by implementing different tabs (on top of indicator data map).

lubojr commented 4 years ago

Add this behavior for global indicators list, as this could be then grouped as well. Grouping will be done only "per agency" not mixing TSM and Chl-a together. A Data Provider column will be used for grouping. Existing data will be concatenated to remove necessity to modify coordinates slightly.

silvester-pari commented 4 years ago

initial implementation in https://github.com/eurodatacube/eodash/commit/78fea729fa300cdfde0e64d5418e9ca2a5ed6e05 (WIP)

silvester-pari commented 4 years ago

https://github.com/eurodatacube/eodash/commit/038d5bf65e22020b4c843f95c4bcbae850d7f713 added provider logos (for trilateral version)
https://github.com/eurodatacube/eodash/commit/3cced76c90f3cad6f3e7f13c11a6ecc0bdb10cdb fixed highlighting of currently selected POIs on the map

silvester-pari commented 4 years ago

this is now implemented. the following fields of the config are used:

aoiID: needs to be the same to create grouping
description: next to location name, eg. "World, Greenhouse Gases" (if different, first one is taken)
indicatorName: on the overview (global list or in map/POI hover, and as subtitle in the data panel (if different, first one is taken)
eoSensor: tab name (has to be different)

@Schpidi @aapopescu

silvester-pari commented 4 years ago

A different approach is used now: instead of using the eoSensor field by default and the need of a tabIndex, the grouping is done instead in appConfig.js:

featureGrouping: [
      {
        features: [
          'NorthAdriaticTSM_ESA-N3a2',
          'NorthAdriaticTSM_NASA-N3a2',
          'NorthAdriaticTSM_JAXA-N3a2',
        ],
        label: 'dataProvider',
      },
      {
        features: [
          'NorthAdriatic_ESA-N3a2',
          'NorthAdriatic_NASA-N3a2',
          'NorthAdriatic_JAXA-N3a2',
        ],
        label: 'dataProvider',
      },
      {
        features: [
          'W1-N1',
          'W2-N1',
          'W3-N1',
        ],
        label: 'eoSensor',
      },
      {
        features: [
          'W4-N2',
          'W5-N2',
        ],
        label: 'calcMethod',
      },
      {
        features: [
          'US08-E10c',
          'US09-E10c',
        ],
        label: 'eoSensor',
      },
    ],

This approach should be more versatile, as any field in indicatorObject can be referenced as label for the tabs, no matter if a string or an array (in case of an array, the very first value is taken).