Help:Best Practices: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
This page is intended to describe best practices while adding a new dataset entry to the Catalog. | This page is intended to describe best practices while adding a new dataset entry to the Catalog. In case you think some information is missing, please indicate it on '''[https://github.com/orgs/ruisdael-observatory/projects/1/ GitHub Ruisdael Data Catalog project]'''. | ||
= Guidelines for all submissions = | = Guidelines for all submissions = |
Revision as of 14:00, 3 April 2025
This page is intended to describe best practices while adding a new dataset entry to the Catalog. In case you think some information is missing, please indicate it on GitHub Ruisdael Data Catalog project.
Guidelines for all submissions
Naming
The first required field for the submission of a new dataset is the name. This name is used to identify the new dataset within the Catalog environment. For naming the dataset, please use the following convention:
Institute Sensor/Campaign/Product/Model at Location
Examples:
- TU Delft optical disdrometer Parsivel² PAR001 at Cabauw
- KNMI DALES model outputs over Cabauw
- TU Delft CMTRACE Level 2 Wind field at Cabauw
Recommendations for the different submission types
Geographic coordinates
For datasets produced by stationary instruments (in-situ, remote sensing) and for single-column model outputs, the latitude and longitude coordinates should be entered with a precision of at least 4 digits.
For non-stationary in-situ and remote sensing observations, use the description field to indicate the measurement domain. For example, the coordinates from the starting and ending points could be indicated.
Description of in-situ datasets
Description of campaigns and products datasets
Description of model output submission
======================================================
First ideas
/This page is under construction. Please come back later..
General Guidelines
- Latitude and longitude coordinates for in-situ and remote sensing datasets should be entered with a precision of at least 4 digits.
- Refrain from using Notes. Put important information directly in the description
- Naming convection for the title: Institute - Sensor - Location
Checklist for in-situ data
- dataset description should contain sensor type/brand
- dataset description should contain .. (if applicable)
Checklist for remote-sensing data
Checklist for model data
- The description should explicitly mention the variables that are provided (e.g., temperature, wind speed, etc..)
Campaign data
How to enter campaign data?