SOLARNET Metadata Recommendations for Solar Observations
docs |
|
|---|---|
build status |
|
Project Information |
Stein Vidar Hagfors Haugan @steinhh, Terje Fredvik @tfredvik
Until the advent of the SOLARNET recommendations, metadata descriptions of Solar observations have been standardized for space-based observations, but the standards have been mostly within a single space mission at a time, at times with significant differences between different mission standards. In the context of ground-based Solar observations, data has typically not been made freely available to the general research community, resulting in an even greater lack of standards for metadata descriptions. This situation makes it difficult to construct multi-instrument archives/virtual observatories with anything more than the most basic metadata available for searching, as well as making it difficult to write generic software for instrument-agnostic data analysis. This document describes the metadata recommendations developed under the SOLARNET EU project, which aims foster more collaboration and data sharing between both ground-based and space-based Solar observatories. The recommendations will be followed by data pipelines developed under the SOLARNET project and others (Solar Orbiter SPICE, SST CHROMIS/CRISP (SSTRED), AISAS/Lomnicky Stit COMP-S/SCD, SAMNET, Gregor HiFI/GFPI, ROB USET, Alma pipeline for Solar data (SOAP), INAF IBIS-A (IBIS data Archive), PADRE/MeDDEA). These recommendations are meant to function as a common reference to which even existing diverse data sets may be related, for ingestion into solar virtual observatories and for analysis by generic software.
The original development of this work received funding from the European Union’s Horizon 2020 and FP7 programmes under grant agreements No 824135 and 31295. Version 2.0 of this document was the final version produced under these grants.
Documentation
The latest rendered documentation can be found on readthedocs.
Acknowledging or Citing The SOLARNET Metadata Recommendations
If you use the SOLARNET Metadata Recommendations in your scientific work, we would appreciate your citing it in your publications. The continued growth and development of the SOLARNET Metadata Recommendations is dependent on the community being aware of them.
Building the Documentation Locally
After cloning the repository, you can build the documentation locally by running the following commands:
cd docs
make clean
make html # Generates HTML in _build/html
make latex && cd _build/latex && make && cd ../.. # Generates PDF in _build/latex
Metadata
Release files for solarnet-metadata 3.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| solarnet_metadata-3.3.0.tar.gz | 407.9 kB | Without provenance | Details for solarnet_metadata-3.3.0.tar.gz |
Release files / solarnet_metadata-3.3.0.tar.gz
| Download URL | solarnet_metadata-3.3.0.tar.gz |
|---|---|
| Size | 407.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
818833861973ac813c5185b7ba90d5b66e736a950eaab9991482dcb2079c8e05
|
|
BLAKE2b-256 checksum How to use checksums |
e6cc92eb05de1d182a7ec799ba8ad014f4f418d72d2fd7e246160cca2a146a38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for solarnet-metadata 3.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.