Loading...
 
ESA > Join & Share > Forums > LTDP SAFE > SAFE conformance classes creation

LTDP SAFE

Help

Show posts:
Jump to forum:

SAFE conformance classes creation

Current SAFE standard is rigorously linked to long-term preservation imposing strong restrictions on the product formats, e.g. it has to be described with a formal language and therefore product description is archived together with the product.

This makes the SAFE standard unusable for some operational cases, e.g. where data are archived in compressed format: this might be typically higher-level products (e.g. NetCDF, JPEG-2000) but might apply also to L0 data (e.g. compressed downlinks).

The new SAFE standard should define different SAFE conformance classes for long-term preservation and for operational use:

- SAFE-LTDP:
require storage of data in a format that can be described in a formal language and for which a reading algorithm can be developed from this description

- SAFE-Operational:
should relax this requirement and accept dependency on format descriptions by external documents and product access by format-specific libraries


Re: SAFE conformance classes creation

> Current SAFE standard is rigorously linked to long-term preservation imposing strong restrictions on the product formats, e.g. it has to be described with a formal language and therefore product description is archived together with the product.
>
> This makes the SAFE standard unusable for some operational cases, e.g. where data are archived in compressed format: this might be typically higher-level products (e.g. NetCDF, JPEG-2000) but might apply also to L0 data (e.g. compressed downlinks).
>
> The new SAFE standard should define different SAFE conformance classes for long-term preservation and for operational use:
>
> - SAFE-LTDP:
> require storage of data in a format that can be described in a formal language and for which a reading algorithm can be developed from this description
>
> - SAFE-Operational:
> should relax this requirement and accept dependency on format descriptions by external documents and product access by format-specific libraries

The KSAT opinion is that the SAFE format should be kept apart from the operations. We do not foresee that this format is suitable for the KSAT EO operations.



Re: SAFE conformance classes creation

The following comments have been done offline by Diego Lozano (Deimos) after the PDR-C collocation meeting:

In the SAFE volume 1 (PGSI-GSEG-EOPG-FS-05-0001) section 2.1, the EO SAFE product has the list of ADF used in its generation, does it have the reference with the source EO SAFE product of the previous level?

For instance, an EO SAFE Level 1 product is linked to its source EO SAFE level 0 products. Upper levels can be OPERATIONAL class, L0 products should be LTDP class. Can SAFE product of different class be linked? Can SAFE products of OPERATIONAL class link to SAFE ADFs of LTDP class?



Show posts:
Jump to forum: