NASA-IMPACT / NASA-IMPACT/veda-data

TWS Anomaly Trend data not plotting in E&A

Open
#396 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Jupyter Notebook
Stars
9
Forks
1
Avg merge
1d 9m
Merged PRs (30d)
1

Description

Issue:
TWS anomaly trend data is not plotting in E&A nor in the data-catalog. Currently this is not actually setup to plot within the data-catalog, but I tested locally.

STAC catalogue
E&A

Additional notes:
I tried to investigate what the issue could be but I fell short in finding the problem. It is calling the proper STAC collection name lis-tws-trend but it's not rendering any data.

The datetime seems fine but I'm not sure if there was any changes in the UI which may impact it. Technically it's a single file but there is a range of datetimes. I'm unsure if this would impact the rendering. Please let me know if you can identify what the issue is, this needs to be included within a Water Insight data story.

"end_datetime": "2021-12-31T23:59:59+00:00",
"start_datetime": "2001-01-01T00:00:00+00:00"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the STAC collection response for lis-tws-trend with how the linked E&A dashboard and data-catalog request and render it. Pay particular attention to the single file's start_datetime and end_datetime range; done means the anomaly trend data plots in E&A and the data-catalog.

Written by the indexing model from the issue text.

Assessment

Domain
data-visualization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.