Help:Best Practices: Difference between revisions
No edit summary |
|||
| Line 4: | Line 4: | ||
== Naming == | == 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/Campaing/Product/Model at Location. | 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/Campaing/Product/Model at Location. | |||
Examples: | Examples: | ||
Revision as of 12:11, 3 April 2025
This page is intended to describe best practices while adding a new dataset entry to the Catalog.
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/Campaing/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, it could be indicated the coordinates from the starting and ending points.