... | ... | @@ -13,6 +13,11 @@ This is the paramount requirement that ***must*** be fulfilled for a successful |
|
|
* Temporal coverage: When does the observation start and end?
|
|
|
* Spectral coverage: Which wavelengths are covered by the observation?
|
|
|
|
|
|
In general, benefits of well structured header data are:
|
|
|
* Interoperability: Third party tools that follow the same standards are compatible with your data
|
|
|
* Attractiveness: Data that is easier to use and understand is more attractive for others to use and will thus higher scientific impact.
|
|
|
|
|
|
|
|
|
## Explicit Recommendations
|
|
|
|
|
|
Any file structure that satisfies the requirement above is formally fit to be integrated into the archive. In practice, it makes sense to further specify these requirements both as a way to enhance interoperability and as a way to provide a proven structure to which new instrument concepts can follow.
|
... | ... | @@ -21,12 +26,7 @@ When dealing with potential files to integrate into the archive, we distinguish |
|
|
* old files from existing archives and possibly discontinued instruments
|
|
|
* files from new instruments that are still under development.
|
|
|
|
|
|
Our current policy is that we will try to reshape headers of existing instruments if necessary and if the required effort is in proportion to the expected scientific value of the archive. For new data we strongly encourage developers to adhere to the recommendations we define below.
|
|
|
|
|
|
In general, benefits of well structured header data are:
|
|
|
* Interoperability: Third party tools that follow the same standards are compatible with your data
|
|
|
* Attractiveness: Data that is easier to use and understand is more attractive for others to use and will thus higher scientific impact.
|
|
|
|
|
|
Our current policy is that we will only try to reshape headers of existing instruments if necessary and if the required effort is in proportion to the expected scientific value of the archive. For new data we strongly encourage developers to adhere to the recommendations we define below.
|
|
|
|
|
|
### Header Structure
|
|
|
|
... | ... | |