How to Add a New Layer in Bignbit - podaac/bignbit GitHub Wiki

Note: This procedure is currently notional and a work in progress. The intent is that with greater automation and more deployed layers, the details will be solidified and less of the process will be on a case-by-case basis.

Procedure

  1. [If required] Implement any code changes required to support the given layer. For example, there are outstanding tickets right now to handle additional projections, modify HyBIG to properly palettize embedded colormaps, and (currently untracked) combine data from multiple variables into a single browse image.
  2. When development is complete and unit tests have passed, a new alpha release can be created and deployed on the SIT venue. At this point, end-to-end tests with multiple collection types should be performed using the procedure. Create a DatasetConfig for this new layer and deploy it in the relevant bucket.
  3. Assuming there are no regressions and end-to-end tests produced the expected results, the new bignbit version is now ready to be deployed on UAT. At this point, the operators should run some data from the collection that is intended to be supported, and ensure that this data is reaching the UAT deployment of GIBS. If all is well, the new layer should be visible in UAT Worldview. If the product is colormapped, ensure that GIBS has a colormap in the format that they expect, as well as any layer metadata such as name, description, etc.
  4. Notify the relevant science team that is a stakeholder in this layer that the data is now ready to view in UAT Worldview. Science validation is required to ensure that none of the details about displaying the product which were not documented in the ICD are caught before reaching operations.
  5. Once science validation and GIBS approval have been met, the operations team is ready to deploy the new layer (and the new bignbit release) to the ops venue. In most cases, some data will be pre-processed on ops to back-populate dates for the new layer before making it available in Worldview.
  6. Once deployment and pre-processing is complete, the new layer should be available in the production version of Worldview!