Datasets:
File size: 9,973 Bytes
ff01f6e | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 | ---
pretty_name: "OPheno: Curated Weed Emergence & Phenology Dataset"
license: cc-by-4.0
language:
- en
tags:
- agriculture
- weed-science
- phenology
- plant-science
- tabular
- time-series
- growth-stages
- emergence
annotations_creators:
- expert-generated
source_datasets:
- original
configs:
- config_name: default
data_files:
- split: train
path: train.csv
---
# OPheno: Curated Weed Emergence & Phenology Dataset

## Overview
The **OPheno Curated Weed Emergence & Phenology Dataset** provides harmonized, high-quality weed emergence and phenology observations collected from research studies, field trials, and scientific publications.
It contains standardized temporal observations of weeds growing within various crop systems, enabling:
- modelling of weed emergence timing
- development of weed phenology models
- cross‑site and cross‑species comparison
- machine learning applications
- agronomic research and decision-support development
This curated dataset is continuously expanded as new [submissions](https://huggingface.co/spaces/OPheno/OPheno-Submission-Portal) are reviewed and validated.
---
## Load the Dataset
[If you want to download the.csv file directly click here](https://huggingface.co/datasets/OPheno/Weed-phenology/blob/main/train.csv)
<details>
<summary><strong>With Python</strong></summary>
```python
from datasets import load_dataset
dataset = load_dataset("OPheno/Weed-phenology")
df = dataset["train"].to_pandas()
```
</details>
<details>
<summary><strong>With R</strong></summary>
```r
library(reticulate)
datasets <- import("datasets")
dataset <- datasets$load_dataset("OPheno/Weed-phenology")
df <- py_to_r(dataset$train$to_pandas())
```
</details>
[For more information about setting up your environment click here](https://huggingface.co/docs/datasets/installation)
## Data Dictionary
| Column | Type | Description |
|---|---|---|
| `trialNumber` | string | Unique identifier for each experimental trial. |
| `countryCode` | string | ISO 3166-1 alpha-2 country code of the observation site. |
| `crop` | string | Crop species identified using EPPO code. |
| `cropEstablishmentMethod` | string | Method of crop establishment (e.g., direct seeding, transplanting). |
| `tillageSystem` | string | Tillage practice used at the site (e.g., no-till, conventional tillage). |
| `typeOfTrial` | string | Type of experimental setup (e.g., field, greenhouse, lab). |
| `seedingDate` | string (ISO 8601) | Date the crop was seeded (`YYYY-MM-DD`). |
| `targetCode` | string | Target weed species identified using EPPO code. |
| `date` | string (ISO 8601) | Date of the observation (`YYYY-MM-DD`). |
| `assessment` | string | Type of observation or assessment performed (e.g., cumulative emergence, weed growth stage). |
| `measurementUnit` | string | Unit associated with the observation (e.g., `%`, `BBCH`). |
| `value` | float32 | Numerical value recorded for the observation. |
| `latitude` | float32 | Latitude of the site in decimal degrees (WGS84). |
| `longitude` | float32 | Longitude of the site in decimal degrees (WGS84). |
| `photoPeriod` | float32 | Photoperiod (day length in hours) at the observation date. |
| `dayOfYear` | int32 | Day of year for the observation (1–366). |
| `daysAfterStart` | int32 | Days since the start of the trial or seeding date. |
| `cumulativeEmergencePercentage` | float32 | Cumulative emergence expressed as a percentage over time. |
| `contributor` | string | Name(s) of the dataset contributor. |
| `organization` | string | Affiliated institution(s) responsible for the data. |
| `doi` | string | Digital Object Identifier linking to the original publication or dataset. |
| `publicationStatus` | string | Publication status of the data (e.g., published, unpublished, in review). |
## Data Creation
The curated dataset is built from researcher contributions and from published studies.
To harmonize diverse submissions while keeping the process open and flexible, OPheno applies a lightweight curation workflow:
1. **Ingest raw submissions** from the OPheno Submission Portal and literature sources.
2. **Standardize names, formats, and units** where appropriate (e.g., ISO‑formatted dates, consistent column naming).
3. **Map observations to the curated schema**, including:
- countryCode, latitude, longitude
- crop, cropEstablishmentMethod, tillageSystem, seedingDate
- targetCode, date, assessment, measurementUnit, value
- photoPeriod, dayOfYear, daysAfterStart
- optional cumulativeEmergencePercentage when derivable
4. **Perform basic validation**, such as:
- checking that dates parse correctly
- verifying coordinate plausibility
- catching obvious type inconsistencies
5. **Enrich the dataset** with environmental context variables where possible, such as photoPeriod, dayOfYear, and daysAfterStart.
If a submission is not yet ready for curation (e.g., incomplete metadata), it remains accessible in the submission portal for transparency and future revision.
Although the curated dataset undergoes quality checks, users should still apply any domain‑specific validation required for their analysis.
## Contributions, Data Scope and Requirements
We welcome contributions to OPheno! If you have relevant weed emergence or phenology data to share, please go to our [submission portal](https://huggingface.co/spaces/OPheno/opheno-submission-portal). Contributions help enhance the dataset's scope and utility for the entire community.
To ensure the utility of OPheno for modeling baseline weed dynamics, the current version focuses on specific data types.
**Inclusion Criteria (Examples):**
* Assessments from untreated control plots.
* Data under standard regional agronomic practices.
* Pre-treatment measurements or data before confounding events occur.
**Exclusion Criteria (Current Curated Version):**
* Weed-control treatments that directly modify weed development or emergence patterns.
Please note that these criteria apply **only to the current curated release**.
We still welcome submissions containing such data because:
1. they remain scientifically valuable,
2. they help us understand the broader landscape of available phenology and emergence datasets,
3. they may be incorporated in future expanded versions of OPheno.
In short, **even if your data fall outside the scope of the curated dataset, we encourage you to submit them**, as they contribute to community knowledge and help guide future development of the project.
**Metadata is Crucial:** Please provide detailed metadata regarding management practices and environmental conditions, especially any treatments applied (include this information in the [submission portal](https://huggingface.co/spaces/OPheno/opheno-submission-portal).
**Future Scope:** We aim to potentially expand OPheno in the future to include data explicitly studying factors like weed control effects. If you have such data, please provide it in the submission portal.
## Allowed Values and Units
**PERC_PLANTEMERGED_PLOT**
Represents cumulative emergence already provided as a percentage.
For each date:
`emergence(t) = average_value(t)`
→ Shows the percentage of plants that have emerged by each date, as directly measured.
**NUM_PLANT_M2**
Represents relative emergence based on the final plant density.
For each date:
`emergence(t) = (average_value(t) / final_average_value) × 100`
→ Shows how much of the final density has emerged by each date.
**NUM_PLANTEMERGED_M2**
Represents cumulative emergence over time (new plants per date).
For each date:
`emergence(t) = (sum of average_values up to date t / sum of all average_values) × 100`
→ Shows cumulative emergence progress as a percentage.
<details>
<summary><strong>Calculation logic</strong></summary>
### Time-series definition
- Each calculation is performed **per time series**
- All dates belonging to the same time series are processed together.
### Data validation
Before any calculation:
- All observations of a given `assessment_type` **must use the same unit**.
- If mixed units are detected, an **exception is raised**.
### Date aggregation
- If multiple observations exist for the same date (e.g. replicates or subsamples):
- Values are **averaged first**.
After averaging: Only **one value per date** is retained.
</details>
## Citation Information
@misc{opheno_dataset_2026
title = {OPheno: An Open-Source Weed Phenology Database},
author = {Espejel Padilla, Jorge Alberto; Akhter Muhammad Javaid; Kromminga, Heiko Hopke and Hoffman, Holger},
year = {2026},
publisher = {Hugging Face},
journal = {Hugging Face Hub},
howpublished = {\url{[https://huggingface.co/OPheno](https://huggingface.co/OPheno)}}
}
## License
The data is distributed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. You are free to share and adapt the data for any purpose, provided you give appropriate credit, provide a link to the license, and indicate if changes were made. See the LICENSE file for full details
## Maintainer
OPheno is maintained by
[Heiko Hopke Kromminga ](https://de.linkedin.com/in/heiko-kromminga?trk=people-guest_people_search-card),
[Muhammad Javaid Akhter ](https://de.linkedin.com/in/muhammad-javaid-akhter-40a18975),
[Jorge Alberto Espejel Padilla](https://de.linkedin.com/in/jorge-alberto-espejel-padilla-b00840216), and
[Holger Hoffmann](https://de.linkedin.com/in/holger-hoffmann-1988834a).
Please use the Hugging Face Hub's Community tab for questions or open an issue on the repository [if using GitHub mirror etc.]
## Acknowledgments
The maintainers acknowledge the use of large language models for assistance in drafting documentation sections, generating code examples, and refining text presented in this repository. All final content was reviewed, validated, and finalized by the maintainers |