IoT Crop Pest Monitoring Data
This dataset provides granular, time-stamped sensor readings and pest incident logs from smart agriculture plots, including detailed environmental metrics and operational responses. It is ideal for developing AI-driven pest management solutions, optimizing farm operations, and conducting predictive analytics for crop protection.
Sample rows
preview · 8 of 124 rows · all 16 columns| reading_idstring | action_takenstring | pest_countinteger | pest_detectedboolean | pest_typestring | plot_idstring | zone_idstring | sensor_idstring | timestampdatetime | incident_severitystring | temperature_celsiusfloat | humidity_percentfloat | soil_moisture_percentfloat | light_intensity_luxfloat | operator_idstring | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| R0001 | none | 0 | false | blank | PLOT_A1 | ZONE_001 | SEN_AA01 | 2024-03-04T08:21:00Z | blank | 15.4 | 72.5 | 33 | 12000 | blank | Routine sensor check, weather normal, no pests detected this morning. |
| R0002 | none | 0 | false | blank | PLOT_B2 | ZONE_002 | SEN_AB02 | 2024-03-04T09:10:00Z | blank | 14.1 | 68.2 | 28.3 | 11800 | blank | Routine morning reading, optimal environmental conditions, no pest activity. |
| R0003 | manual_removal | 17 | true | aphid | PLOT_C3 | ZONE_003 | SEN_AC03 | 2024-03-04T13:44:00Z | medium | 22.7 | 64.1 | 41.6 | 16300 | OP_JOHNSON | Cluster of aphids found near central stem; manual removal scheduled by operator. |
| R0004 | manual_removal | 5 | true | beetle | PLOT_D4 | ZONE_004 | SEN_AD04 | 2024-03-04T16:05:00Z | low | 25.2 | 59 | 32.7 | 14000 | OP_FISCHER | Early detection of beetle presence, minor damage, operator dispatched for removal. |
| R0005 | none | 0 | false | blank | PLOT_C3 | ZONE_005 | SEN_AC05 | 2024-03-04T17:13:00Z | blank | 23.8 | 75.1 | 29.2 | 19500 | blank | Evening sensor reading, no pest event, weather mild, maintenance checked. |
| R0006 | none | 0 | false | blank | PLOT_A1 | ZONE_002 | SEN_AA02 | 2024-03-05T06:20:00Z | blank | 11.8 | 67.4 | 25.1 | 9000 | blank | Routine pre-dawn reading, calibration confirmed, no pest or environmental alerts. |
| R0007 | manual_removal | 9 | true | mite | PLOT_E5 | ZONE_006 | SEN_AE06 | 2024-03-05T09:58:00Z | low | 18.9 | 51.2 | 22 | 15100 | OP_ROMERO | Mite traces on leaf undersides, manual removal scheduled, weather dry. |
| R0008 | none | 0 | false | blank | PLOT_F6 | ZONE_007 | SEN_AF07 | 2024-03-05T13:17:00Z | blank | 21 | 62.3 | 37.6 | 12700 | blank | Midday check, optimal growth conditions, no pest or system anomalies. |
| R0009 | biological_control | 21 | true | caterpillar | PLOT_B2 | ZONE_008 | SEN_AB08 | 2024-03-05T15:55:00Z | medium | 29.8 | 48.7 | 31.4 | 20100 | OP_LEE | Caterpillar outbreak detected, beneficial insects released, monitoring ongoing. |
| R0010 | none | 0 | false | blank | PLOT_G7 | ZONE_009 | SEN_AG09 | 2024-03-05T16:29:00Z | blank | 19.6 | 69.8 | 36.4 | 14500 | blank | Routine sensor reading, no pest events, environmental conditions stable. |
| R0011 | none | 0 | false | blank | PLOT_H8 | ZONE_010 | SEN_AH10 | 2024-03-06T07:45:00Z | blank | 10.3 | 80.1 | 23.2 | 5400 | blank | Early morning check, high humidity, no pest detected, sensor recalibrated. |
| R0012 | pesticide_applied | 92 | true | locust | PLOT_E5 | ZONE_011 | SEN_AE11 | 2024-03-06T11:38:00Z | high | 35.6 | 19.8 | 7.2 | 47000 | OP_CHEN | Large-scale locust outbreak; emergency pesticide application and damage assessment ongoing. |
| R0013 | none | 0 | false | blank | PLOT_C3 | ZONE_012 | SEN_AC12 | 2024-03-06T13:02:00Z | blank | 16.7 | 73 | 30.6 | 10400 | blank | Routine check, no pest found, environmental metrics within normal range. |
| R0014 | manual_removal | 3 | true | aphid | PLOT_F6 | ZONE_013 | SEN_AF13 | 2024-03-06T15:29:00Z | low | 24.4 | 58.9 | 38.2 | 17600 | OP_GARCIA | Small aphid cluster on new growth, manual removal planned, no further action needed. |
| R0015 | none | 0 | false | blank | PLOT_B2 | ZONE_014 | SEN_AB14 | 2024-03-06T17:53:00Z | blank | 22 | 63.2 | 34.1 | 14350 | blank | End-of-day reading, no pest activity, weather mild, sensors checked for calibration. |
| R0016 | none | 0 | false | blank | PLOT_A1 | ZONE_015 | SEN_AA15 | 2024-03-07T08:12:00Z | blank | 16.1 | 61.4 | 35.7 | 11000 | blank | Routine morning monitoring, no pests detected, environmental levels nominal. |
| R0017 | biological_control | 56 | true | beetle | PLOT_G7 | ZONE_016 | SEN_AG16 | 2024-03-07T11:15:00Z | high | 32.8 | 15.9 | 6.3 | 53000 | OP_PATEL | Major beetle infestation detected, biological control introduced, emergency protocols engaged. |
| R0018 | manual_removal | 2 | true | mite | PLOT_D4 | ZONE_017 | SEN_AD17 | 2024-03-07T13:41:00Z | low | 21.6 | 57.8 | 41.2 | 15800 | OP_SMITH | Minor mite traces, manual removal performed, pest pressure low. |
| R0019 | none | 0 | false | blank | PLOT_H8 | ZONE_018 | SEN_AH18 | 2024-03-07T15:32:00Z | blank | 13.9 | 77.5 | 39.8 | 12800 | blank | Regular monitoring, high humidity, no pest detected, sensor maintenance completed. |
| R0020 | biological_control | 14 | true | caterpillar | PLOT_E5 | ZONE_019 | SEN_AE19 | 2024-03-07T17:59:00Z | medium | 27.2 | 44.7 | 19 | 22200 | OP_LEE | Caterpillar group found near irrigation line, beneficial insects deployed, monitoring ongoing. |
What the 124 rows show
from the 124-row samplePesticide_
- 44%pest_
detected = true - 0median pest_
count - 3incident severities
- 26plots
- 20.3median temperature_
celsius - 62.2median humidity_
percent
Median 0, from 0 to 315.
- string 9
- integer 1
- float 4
- datetime 1
- boolean 1
Columns
16 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 9 columns | |||
reading_id | string | Unique identifier for each sensor reading or incident log entryunique | R0001 |
plot_id | string | Unique identifier for the agricultural plot where the sensor is located | PLOT_A1 |
zone_id | string | Identifier for the specific zone within the plot | ZONE_001 |
sensor_id | string | Unique identifier for the IoT sensor device | SEN_AA01 |
pest_type | string | Type of pest detected (e.g., aphid, beetle, caterpillar); empty if no pest detected7 values · optional | aphid |
incident_severity | string | Severity of the pest incident (low, medium, high); empty if no pest detectedlow · medium · high · · optional | medium |
action_taken | string | Action taken in response to pest detection (e.g., none, pesticide_applied, manual_removal, biological_control)5 values · optional | none |
operator_id | string | Identifier for the operator or system that responded to the incident; empty if no action takenoptional | OP_JOHNSON |
notes | string | Additional notes or comments about the reading or incidentoptional | Routine sensor check, wea… |
| Numbers 5 columns | |||
pest_count | integer | Estimated number of pests detected in this reading; zero if none detected0 or more | 0 |
temperature_celsius | float | Ambient temperature at the time of reading, in degrees Celsius-40 to 60 | 15.4 |
humidity_percent | float | Relative humidity at the time of reading, as a percentage0 to 100 | 72.5 |
soil_moisture_percent | float | Soil moisture level at the time of reading, as a percentage0 to 100 | 33 |
light_intensity_lux | float | Light intensity measured at the time of reading, in lux0 or more | 12000 |
| Dates and times 1 column | |||
timestamp | datetime | Date and time when the reading or incident was recorded | 2024-03-04T08:21:00Z |
| True or false 1 column | |||
pest_detected | boolean | Indicates whether a pest was detected in this reading | false |
Use it for
An agriculture dashboard
The pest_
detected rate, pest_ count by action_ taken and a breakdown of pest_ type. Excel, Power BI or Tableau. Why do the 10 pesticide_
applied rows have a mean pest_ count of 116.0? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Readings124R00010noneR000317manual_r…R00045manual_r…
A software demo
Believable readings with plot_
id, zone_ id and sensor_ id to fill a screen in front of a buyer.
This dataset124 rows16 columns
Yours1,000 rows16 columns
blueprint · iot-crop-pest-monitoring-data
Behind this dataset
Same schema. As many rows as you need.
These 124 rows came out of a blueprint — 16 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
Rules it was built with
- Each zone must log at least one pest incident per month.
- Sensor readings include temperature, humidity, and pest count every 12 hours.
- Manual validation required for flagged high-risk incidents.
- Weather anomalies trigger re-sampling of environmental metrics.
- No duplicate timestamps within a zone.
Open the blueprint in Data Factory
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- iot-crop-pest-monitoring-data