Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore user-selected dataset options in xcube-viewer #426

Open
b-yogesh opened this issue Sep 12, 2024 · 1 comment
Open

Restore user-selected dataset options in xcube-viewer #426

b-yogesh opened this issue Sep 12, 2024 · 1 comment

Comments

@b-yogesh
Copy link
Contributor

b-yogesh commented Sep 12, 2024

Is your feature request related to a problem? Please describe.

The time is reset every time we select a dataset, and this is a problem for the Maps split view and also when we select a dataset with some timestamp and then select another dataset and return to the original one. To improve the user experience, we should restore the selected time for each dataset that has the time dimension.

Left: Status quo
Right: Required solution
image_2024_09_13T09_08_26_879Z

This will have twofold advantages:

  • First, it improves the UX and allows the user to come back to the dataset with selected timestamp previously.
  • Second, it will also help in the Map Split view where currently, when the user hovers over the map, the requests that are sent to the server use the data that is present on current dataset selected, which if doesn't have a time dimension and other one does, the server will throw the 400 exception. When this issue is solved, we can use the data that was selected for each dataset to send the requests instead of sending the same parameters for both the datasets.

Some screenshots showing

  1. Time Selected for a dataset
    ksnip_20240912-145503

  2. Selecting another dataset
    ksnip_20240912-145526

  3. Selecting the original dataset but the time is reset
    ksnip_20240912-145543

  4. In split view, the time dimension is not passed because the current dataset does not one resulting in error for the dataset that has a time dimension.

ksnip_20240912-164117

The solution you'd like

  • Store the state of the user selections per dataset
  • Restore the state of the dataset when user selects that dataset
  • Make this state available that can be used when sending requests to the server
@KerstinS
Copy link

The behaviour as it is now is useful for the case that a user wants to compare same dates from different datasets going back and forth in the data sets. When time in one data set is changed, the other data set should jump to that time as well. Thus there are different ways how to work with the time when changing data sets. The one use case wants to see always the same date in all data sets, the other wants to keep the date that was selected before when the data set was selected.

Aside from this, it would be nice to be able to compare two times from one data set in the split window (different topic....)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants