Add Fire Discovery datasets on Thomas Fire

[j08lue]

• Identify the point of contact and ensure someone is providing them updates:

• Data provider has read guidelines on data preparation

• Identify data location:

  1. s3://veda-data-store-staging/EIS/COG/Fire-Hydro/thomas_fire_barc_201712.cog.tiff
  2. s3://veda-data-store-staging/EIS/COG/Fire-Hydro/thomas_fire_frpmax_201712.cog.tiff

• Number of items: 2

• Verify that files are valid COGs (e.g. with rio cogeo validate)

  • ✅ https://staging-raster.delta-backend.com/cog/validate?url=s3://veda-data-store-staging/EIS/COG/Fire-Hydro/thomas_fire_barc_201712.cog.tiff
  • ✅ https://staging-raster.delta-backend.com/cog/validate?url=s3://veda-data-store-staging/EIS/COG/Fire-Hydro/thomas_fire_frpmax_201712.cog.tiff

• Gather STAC collection metadata

  • id:
  • title:
  • description:
  • license:
  • temporal interval:
  • whether it is periodic on the dashboard (periodic = regular time series of layers without gaps):
  • the dashboard time density:

{
  "collection": "barc-thomasfire",
  "title": "barc-thomasfire",
  "description": "Burn Area Reflectance Classification (BARC) from the Burned Area Emergency Response (BAER) program for Thomas fire, 2017",
  "license": "CC0-1.0",
  "is_periodic": false,
  "time_density": null,
  "spatial_extent": {
    "xmin": -119.73,
    "ymin": 34.19,
    "xmax": -118.88,
    "ymax": 34.73
  },
  "temporal_extent": {
    "startdate": "2017-12-01T00:00:00Z",
    "enddate": "2017-12-01T00:00:00Z"
  },
  "sample_files": [
    "s3://veda-data-store-staging/EIS/COG/Fire-Hydro/thomas_fire_barc.cog.tiff"
  ],
  "discovery_items": [
    {
      "discovery": "s3",
      "cogify": false,
      "upload": false,
      "dry_run": false,
      "prefix": "EIS/COG/Fire-Hydro/",
      "bucket": "veda-data-store-staging",
      "filename_regex": "(.*)common_part_of_filenames(.*).tif$",
      "datetime_range": "year/month/day"
    }
  ]
}

{
  "collection": "frp-max-thomasfire",
  "title": "frp-max-thomasfire",
  "description": "Maximum Fire Radiative Power per 12hr fire line segment for Thomas fire",
  "license": "CC0-1.0",
  "is_periodic": false,
  "time_density": null,
  "spatial_extent": {
    "xmin": -119.73,
    "ymin": 34.19,
    "xmax": -118.88,
    "ymax": 34.73
  },
  "temporal_extent": {
    "startdate": "2017-12-01T00:00:00Z",
    "enddate": "2017-12-01T00:00:00Z"
  },
  "sample_files": [
    "s3://veda-data-store-staging/EIS/COG/Fire-Hydro/thomas_fire_frpmax.cog.tiff"
  ],
  "discovery_items": [
    {
      "discovery": "s3",
      "cogify": false,
      "upload": false,
      "dry_run": false,
      "prefix": "EIS/COG/Fire-Hydro/",
      "bucket": "veda-data-store-staging",
      "filename_regex": "(.*)common_part_of_filenames(.*).tif$",
      "datetime_range": "year/month/day"
    }
  ]
}

• Review and follow https://github.com/NASA-IMPACT/cloud-optimized-data-pipelines/blob/main/OPERATING.md
• Open PR for publishing those datasets to the Staging API:
• Notify QA / move ticket to QA state
• Once approved, merge and close.

Resources on metadata

If not already familiar with these conventions for generating STAC collection and item metadata:
- Collections: NASA-IMPACT/veda-backend#29 and STAC version 1.0 specification for collections
- Items: NASA-IMPACT/veda-backend#28 and STAC version 1.0 specification for items
- NOTE: The delta-backend instructions are specific to datasets for the climate dashboard, however not all datasets are going to be a part of the visual layers for the dashboard so you can ignore the instructions that are specific to "dashboard" extension, "item_assets" in the collection and "cog_default" asset type in the item.

[slesaad]

These have been published to dev stac catalog and sent for review.
Once reviewed, they will be published to staging.

[slesaad]

The datasets are in staging, so closing this!