The development of solid EBV observation requirements depends on a consistent approach to developing the EBVs themselves. An early EBV development approach and its revision proved too complex and was hindered by insufficient resources; the current approach is simpler and more focused and will facilitate delivery of updated EBV definitions and plans for EBV data products by mid-2020 for at least one EBV in each EBV Class. This process will be extended and become the basis for developing the EBV observation and product requirements. It is summarized as follows:
1) Each of the six EBV Classes has an associated EBV WG to develop the EBVs for their assigned class.
2) Through discussion with its members and the broader community, EBVs are identified and defined. This includes identifying and defining any Attributes associated with each EBV. (An Attribute is a parameter that fits within the EBV concept and, in general, for which Data Products will be produced.) An October meeting on an EBV-relevant topic will further facilitate this process.
3) The following information should be provided for each EBV/Attribute:
This information can then be used to further develop an EBV Traceability Matrix that contains the observation requirements and is formatted appropriately for CEOS. Additionally, each EBV data product (e.g., Attributes and derived products) will follow standard metadata guidelines