-
Notifications
You must be signed in to change notification settings - Fork 38
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
Configure CMIP6 datasets & discovery #153
Comments
@freitagb Just confirming, should CMIP6 be in the VEDA Dashboard and should it be its own thematic area? |
FYI the CMIP6 data is not fully loaded yet:
|
Thanks @j08lue |
We rolled the CMIP-6 ingestion over to the current sprint, but AFAIK are expecting to close it within that time. I'll double-check and confirm here. |
@aboydnw I am planning to do some investigation of the sample CMIP6 data ingested into the dev catalog this sprint. I think we can reasonably finish evaluating whether or not the changes cause degraded stac-api/raster-api performance (CMIP6 was breaking for us in pgstac <v0.5) and if the metadata as defined are suitable for veda-config this sprint but I am not sure about the current state of the ingest pipelines for running the ingest for staging--that step could roll over. |
Sounds good, thanks for the update. We don't have a real rush on this, just trying to plan out the next couple of sprints. Thanks! |
This is the ticket in progress NASA-IMPACT/veda-data#67. Let us discuss this during sprint planning on Monday - I'll remember to look in the "in progress" column. |
Closing in favor of opening another ticket to explore options for visualization |
Description
Based on content in the CMIP6 staging dashboard: https://cmip6.surge.sh/
2 datasets with multiple indicators (layers)
1 discovery
1 About page
Note, dates for these datasets are in the future
Also note, for the TAS Crossing Year layer, the date seems to be the dependent variable,, so it drives the map view. As opposed to the user selecting a date to view another metric.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: