NASA-IMPACT / NASA-IMPACT/veda-data

[WIP] Define best practices for defining collections when produced for specific stories

Open
#58 12 comments 0 reactions 1 assignee View on GitHub

@abarciauskas-bgse is already working on this.

Since Mar 28, 2022.

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

Description

The question has arisen for datasets we are curating specifically to tell the EJ story of Hurricanes Ida and Maria: how do we want to organize collections that are produced for specific events (e.g. Hurricanes). The consensus so far is that we want to publish to generalizable collections as much as possible rather than collections scoped to a specific event.

What this means is that for the EJ story we will be creating and using the following collections:

  • reformatted planetscope data - reformatted to COG, segmented by zip code for Hurricanes Ida and Maria but could be extended to other spatial and temporal locations in the future
  • blue tarp detections from this planetscope collection, starting with Hurricanes Ida and Maria but these detections could be created for other localities in the future
  • HLS data - no special collection for these events (however for the configuration of stories, we should be able to specify temporal and spatial extents of this data)
  • nightlights data - we already have https://staging-stac.delta-backend.xyz/collections/nightlights-hd-monthly/items, however the Ida and Maria nightlights data are for specific dates before during and after the hurricanes. Does it make sense to put it in the same collection?

Interested in any additional thoughts or considerations from the team @anayeaye @slesaad @xhagrg @leothomas @danielfdsilva

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.