Hi all,
Luke and I just discussed the workflow for calculating Derived Parameters that require input from multiple Data Products – as is the case for calculating the L2 DOCONCS from DOSTA and CTD inputs (see section 2.2.2 of [DOCONCS DataProduct spec] [2]).
While the combinatorial functionality required at the Coverage Model level is already in place, there are some gaps in the resource, association, and preload layers of the system required to orchestrate this type of DataProduct. Here are the gaps that would need to be filled to realize an AggregateDataProduct (working name):
- Resource stuff:
- New resource – AggregateDataProduct: extends DataProduct
- Adds fields:
- complex_coverage_type or