Farm Sensor Pest Detection Logs

This dataset provides granular logs of pest detection events from IoT sensors deployed on small and medium farms, including sensor metadata, pest types, intervention actions, and outcomes. It enables comprehensive analysis of pest management practices, sensor effectiveness, and response efficiency, supporting data-driven decision-making for sustainable agriculture.

  • last updated 20 Jan 2026
  • by GoMask
The brief that made it

Monitor and optimize pest management interventions across multiple farms

Sample rows

preview · 8 of 80 rows · all 17 columns
log_idstringintervention_typestringpest_countintegerintervention_requiredbooleanintervention_effectivenessstringfarm_idstringsensor_idstringsensor_typestringsensor_location_latitudefloatsensor_location_longitudefloatsensor_location_descriptionstringdetection_timestampdatetimepest_typestringdetection_confidencefloatintervention_timestampdatetimesensor_statusstringnotesstring
LOG-00001-Apesticide8truesuccessfulFARM-001SENS-01-001camera37.2412-120.8323Greenhouse 22024-05-03T07:23:01aphid0.892024-05-03T08:02:15activeImmediate action taken, no issues.
LOG-00002-Anone4falseblankFARM-002SENS-02-003pheromone_trap38.0059-121.1022South field, near irrigation2024-05-04T16:45:47moth0.74blankactiveLow count, watch for trend.
LOG-00003-Anone2falseblankFARM-001SENS-01-002acoustic37.2427-120.8351North field perimeter2024-05-05T13:18:34beetle0.92blankactiveNo action required.
LOG-00004-Abiological_control15truepartialFARM-003SENS-03-001camera36.9987-119.7723East orchard row 52024-05-06T09:30:45aphid0.832024-05-06T11:20:52activeLadybugs released.
LOG-00005-Anone1falseblankFARM-004SENS-04-004pheromone_trap39.1132-120.5648Greenhouse 1 south corner2024-05-07T14:07:11moth0.66blankactiveblank
LOG-00006-Amanual_removal3truesuccessfulFARM-005SENS-05-006acoustic37.9811-121.2845West plot, near equipment shed2024-05-08T20:19:08beetle0.952024-05-08T21:00:34activeStaff removed insects by hand.
LOG-00007-Apesticide12truepartialFARM-003SENS-03-002other36.9979-119.7718Orchard north boundary2024-05-09T07:55:19moth0.822024-05-09T09:03:21activeFollow-up spraying scheduled.
LOG-00008-Abiological_control7truesuccessfulFARM-002SENS-02-004camera38.0072-121.1007Greenhouse 3, entry2024-05-10T12:22:55aphid0.862024-05-10T13:10:44activeParasitic wasps used.

What the 80 rows show

from the 80-row sample

None (intervention type) stands out: mean pest_count is 4.2, against 10.1 for the rest.

  • 51%intervention_required = true
  • 7median pest_count
  • 4sensor types
  • 5pest types
  • 17farms
  • 0.82median detection_confidence
Mean pest_count by intervention_type80 rows
0102012.0pesticide15 rows9.7biologic…11 rows8.5manual_r…15 rows4.2none39 rows
pest_count80 rows, in bands of 2
08163161314119741201020pest_count →

Median 7, from 1 to 19.

intervention_effectiveness41 rows with a value · 39 left blank
  1. successful26
  2. partial13
  3. failed1
  4. unknown1
17 columns by typefrom the column list below
  • string 10
  • integer 1
  • float 3
  • datetime 2
  • boolean 1

Columns

17 columns in four groups
blueprint · 17 columns
columntypedescriptionexample
Text 10 columns
log_idstringUnique identifier for each pest detection log entryuniqueLOG-00001-A
farm_idstringUnique identifier for the farm where the sensor is deployedFARM-001
sensor_idstringUnique identifier for the IoT sensor deviceSENS-01-001
sensor_typestringType or model of the IoT sensor (e.g., camera, pheromone trap, acoustic)camera · pheromone_trap · acoustic · othercamera
sensor_location_descriptionstringTextual description of the sensor's placement (e.g., greenhouse 2, north field)optionalGreenhouse 2
pest_typestringType or species of pest detected (e.g., aphid, moth, beetle)5 typesaphid
intervention_typestringType of intervention performed (e.g., pesticide, biological control, manual removal)5 values · optionalpesticide
intervention_effectivenessstringAssessment of intervention effectiveness (e.g., successful, partial, failed, unknown)successful · partial · failed · unknown · optionalsuccessful
sensor_statusstringOperational status of the sensor at the time of detection (e.g., active, offline, maintenance)active · offline · maintenanceactive
notesstringAdditional notes or comments from farm staff or systemoptionalNo action required.
Numbers 4 columns
sensor_location_latitudefloatLatitude coordinate of the sensor's location-90 to 9037.2412
sensor_location_longitudefloatLongitude coordinate of the sensor's location-180 to 180-120.8323
pest_countintegerNumber of pests detected in this event1 or more8
detection_confidencefloatConfidence score (0-1) of the detection event as reported by the sensor or algorithm0 to 1 · optional0.89
Dates and times 2 columns
detection_timestampdatetimeDate and time when the pest was detected by the sensor2024-05-03T07:23:01
intervention_timestampdatetimeDate and time when the intervention was performedoptional2024-05-03T08:02:15
True or false 1 column
intervention_requiredbooleanIndicates if an intervention (e.g., pesticide application) was required based on this detectiontrue

Use it for

  • intervention r…51%41 of 80 rowsmean pest count by in…12.0pest…9.7biol…8.5manu…4.2none

    An agriculture dashboard

    The intervention_required rate, pest_count by intervention_type and a breakdown of intervention_effectiveness. Excel, Power BI or Tableau.

  • Why do the 39 none rows have a mean pest_count of 4.2?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable logs with farm_id, sensor_id and sensor_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 17 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

10,000 rows of yours: $12.99One-time. No subscription. All prices

This dataset80 rows17 columns
Yours10,000 rows17 columnssensor_location_latitude: UK only

blueprint · farm-sensor-pest-detection-logs

Behind this dataset

Same schema. As many rows as you need.

These 80 rows came out of a blueprint — 17 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 row represents a unique sensor event.
  • Include pest type, detection time, and sensor ID.
  • Track intervention status and action timestamp.
  • Sensors are distributed across distinct farm zones.
  • Sensor readings must be within manufacturer calibration limits.
  • Pest detection events must be verified by manual inspection log.
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
farm-sensor-pest-detection-logs

What should your data show?

Preview 20 rows free
No signup. No card.