... | ... | @@ -4,7 +4,7 @@ |
|
|
|
|
|
The main data we are interested in in relation to the Archive is the ***science ready level1 FITS data***. This is what we use as a source to describe observations, accordingly our descriptions can only be as precise as the headers of the files. The question we ask to determine whether a specific header format is sufficient for our purposes is:
|
|
|
|
|
|
> Does the header contain all information to completely describe the underlying observation solely from it's constituent FITS files?
|
|
|
> Does the header contain sufficient information to completely describe the underlying observation solely from it's constituent FITS files?
|
|
|
|
|
|
This is the paramount requirement that ***must*** be fulfilled for a successful integration into our archive. Further specifications can make the data more interoperable and easier to deal with, but if this requirement is not fulfilled, it is a total showstopper. In this context *completely* is meant to indicate the full set of fields of an [observation description](standards_and_references/Mandatory-Fields-for-Observation-Descriptions). They include, but are not limited to:
|
|
|
|
... | ... | |