Help:What is a Dataset: Difference between revisions
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
* in-situ observations | * in-situ observations | ||
* remote-sensing observations | * remote-sensing observations | ||
* | * Derived/Processed Data: for example, highly processed datasets, blended satellite and in-situ data, retrievals and datasets based on other datasets. | ||
* Geospatial Data: for example, datasets that include spatial information about the Earth's surface, sub-surface and atmosphere. GIS layers etc.. | |||
Historical and Paleoclimate Data (Datasets that provide information about past climates using proxy data or historical records.) | |||
In-situ Observation (Datasets collected directly at the location of interest.) | |||
Model Data (Datasets produced by computational models.) | |||
Remote Sensing Observation (Datasets collected from a distance, typically using satellites or ground-based remote sensors.) | |||
Software should not be part of the catalog and should be shared via the Ruisdael github. But I agree with you that we should provide some better guidelines as to what counts as a dataset. I'll put this on the agenda for the first core group meeting in January/February 2025. For now, if you are not sure, just ask me 🙂 | |||
Revision as of 08:39, 10 December 2024
The catalog lists many different types of data.
Types
- model output
- in-situ observations
- remote-sensing observations
- Derived/Processed Data: for example, highly processed datasets, blended satellite and in-situ data, retrievals and datasets based on other datasets.
- Geospatial Data: for example, datasets that include spatial information about the Earth's surface, sub-surface and atmosphere. GIS layers etc..
Historical and Paleoclimate Data (Datasets that provide information about past climates using proxy data or historical records.) In-situ Observation (Datasets collected directly at the location of interest.) Model Data (Datasets produced by computational models.) Remote Sensing Observation (Datasets collected from a distance, typically using satellites or ground-based remote sensors.)
Software should not be part of the catalog and should be shared via the Ruisdael github. But I agree with you that we should provide some better guidelines as to what counts as a dataset. I'll put this on the agenda for the first core group meeting in January/February 2025. For now, if you are not sure, just ask me 🙂
Not a Dataset
- software and data analysis scripts. The latter should be indexed, documented and distributed through the Ruisdael github page.
- datasets that do not have any link to the Ruisdael project.