-
Notifications
You must be signed in to change notification settings - Fork 5
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
Ab/add zarr timeseries #538
Conversation
✅ Deploy Preview for veda-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
mapboxId: 'cldu1cb8f00ds01p6gi583w1m', | ||
thumbnailUrl: `https://api.mapbox.com/styles/v1/covid-nasa/cldac5c2c003k01oebmavw4q3/static/-9.14,38.7,10.5,0/480x320?access_token=${process.env.MAPBOX_TOKEN}` | ||
mapboxId: 'ckb01h6f10bn81iqg98ne0i2y', | ||
thumbnailUrl: `https://api.mapbox.com/styles/v1/covid-nasa/ckb01h6f10bn81iqg98ne0i2y/static/-9.14,38.7,10.5,0/480x320?access_token=${process.env.MAPBOX_TOKEN}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if this change is necessary to have things working locally but apparently I needed it to get things working. Should it be updated?
@@ -0,0 +1,44 @@ | |||
--- | |||
id: oco2-geos-l3-daily |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just for demonstration purposes, not sure this dataset or its configuration will end up in the dashboard and if so it would go in veda-config anyways
cf91e6a
to
5540904
Compare
5540904
to
f8b15c1
Compare
@abarciauskas-bgse Made some small changes and rebased on top of Changes:
|
Will fix #166 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be good to go once the data makes it to the production environment.
I will update this PR to resolve conflicts soon, but more immediately need to address the titiler deployment returning an internal server error (with no logs at this time) |
@abarciauskas-bgse Is there any update on this? Are we planning to include this in the current format? |
@danielfdsilva this should be good to merge. I have updated the branch with latest changes and tested locally. Waiting on the netlify preview at the moment. |
@danielfdsilva it looks like there are some lint and ts-check errors unrelated to this PR - can you help me resolve them? Any advice on how to avoid this in the future would be appreciated. |
e0410aa
to
f71364a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abarciauskas-bgse Made a couple of changes to simplifying the layer data handling and fix the typing issues. I'd say it is good to go.
Thank you @danielfdsilva @j08lue @anayeaye I would like to setup some automated alerts in case the xarray titiler goes down but then I think we should go ahead and add the zarr dataset to the dashboard (see https:/NASA-IMPACT/veda-ui/blob/ab/add-zarr-timeseries/mock/datasets/oco2-geos-l3-daily.data.mdx) to demonstrate the capability, what do you think? |
This PR adds a component for Zarr timeseries layers which is similar too (but much simpler than) the raster timeseries component.
Right now, the only Zarr datasets available via STAC are in the dev version of the catalog, which is why I temporarily point the STAC API URL to the dev stack. This change (to the STAC API URL) should not be merged. We should first determine if that zarr dataset in dev will be promoted to staging and / or a resolution to this ADR on including external datasets: https:/NASA-IMPACT/veda-architecture/pull/258