Smart Irrigation System Event Logs

This dataset provides granular event logs from smart irrigation systems deployed in SME agricultural settings, capturing operational activity, faults, water usage, and sustainability interventions. It enables agri-tech startups and farm managers to monitor device performance, optimize water consumption, and track climate resilience actions, supporting data-driven precision agriculture and sustainability reporting.

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

Monitoring device uptime and operational efficiency across multiple farms

Sample rows

preview · 8 of 94 rows · all 17 columns
event_idstringevent_typestringwater_usage_litersfloatsustainability_flagbooleanoperator_idstringdevice_idstringfarm_idstringevent_timestampdatetimeevent_subtypestringstatusstringduration_secondsintegerfault_codestringfault_descriptionstringlocation_latitudefloatlocation_longitudefloatnotesstringoptimization_actionstring
EVT001-2024-06-01T08:01:45operational120.7falseOP100DEV-A1001FARM-CA-0012024-06-01T08:01:45startactive1800blankblank36.7783-119.4179Morning cycle started successfully.blank
EVT002-2024-06-01T08:33:02fault15.2trueOP102DEV-A1002FARM-CA-0012024-06-01T08:33:02leak_detectederror635F102Pipe leak detected on sector 2.36.7784-119.4182Leak detected; irrigation halted.blank
EVT003-2024-06-01T09:05:27operational110.3falseOP101DEV-A1003FARM-CA-0022024-06-01T09:05:27stopinactive1750blankblank36.7791-119.4195Irrigation cycle completed.blank
EVT004-2024-06-01T09:17:09optimization98.5trueOP103DEV-A1004FARM-CA-0022024-06-01T09:17:09schedule_adjustedmaintenance1480blankblank36.7793-119.4199Schedule optimized for water conservation.Adjusted watering schedule for drought conditions.
EVT005-2024-06-01T10:02:53operational134.9falseOP104DEV-A1005FARM-CA-0032024-06-01T10:02:53startactive2100blankblank36.7801-119.4205Cycle started as scheduled.blank
EVT006-2024-06-01T10:30:18fault25.6falseOP105DEV-A1006FARM-CA-0032024-06-01T10:30:18low_pressureerror500F201Low water pressure detected in main line.36.7803-119.4208Pressure dropped below threshold.blank
EVT007-2024-06-01T11:12:41operational129.6falseOP106DEV-A1007FARM-CA-0042024-06-01T11:12:41startactive1860blankblank36.7806-119.4211Cycle started, soil moisture adequate.blank
EVT008-2024-06-01T11:44:03optimization97.2trueOP107DEV-A1008FARM-CA-0042024-06-01T11:44:03flow_rate_adjustedmaintenance1600blankblank36.7809-119.4214Adjustment made for sustainability.Reduced flow rate for eco mode.

What the 94 rows show

from the 94-row sample

Fault (event type) stands out: mean water_usage_liters is 13.1, against 121.3 for the rest.

  • 23%sustainability_flag = true
  • 116.5median water_usage_liters
  • 4statuses
  • 11farms
  • 16event subtypes
  • 18devices
Mean water_usage_liters by event_type82 rows
0100200125.9operational54 rows13.1fault16 rows100.8optimization12 rows
water_usage_liters82 rows, in bands of 25
015301510830270010125225water_usage_liters →

Median 116.5, from 0.0 to 214.5.

operator_id94 rows · top 10 of 22 values
  1. op-107
  2. op-226
  3. OP1005
  4. OP1025
  5. OP1015
  6. OP1035
  7. OP1045
  8. OP1055
  9. OP1065
  10. op-135
17 columns by typefrom the column list below
  • string 11
  • integer 1
  • float 3
  • datetime 1
  • boolean 1

Columns

17 columns in four groups
blueprint · 17 columns
columntypedescriptionexample
Text 11 columns
event_idstringUnique identifier for each event log entryuniqueevt-20001
device_idstringUnique identifier for the smart irrigation deviceDEV-A1001
farm_idstringUnique identifier for the farm where the device is located11 farmsFARM-CA-001
event_typestringType of event (e.g., operational, fault, optimization)operational · fault · optimizationoperational
event_subtypestringSpecific subtype of the event (e.g., start, stop, leak_detected, schedule_adjusted)optionalstart
statusstringStatus of the device at the time of event (e.g., active, inactive, error, maintenance)active · inactive · error · maintenanceactive
fault_codestringCode representing the specific fault (if applicable)optionalF102
fault_descriptionstringDetailed description of the fault (if applicable)optionalLeak detected, sector 3.
optimization_actionstringDescription of any optimization or intervention performed (if applicable)optionalAdjusted watering schedul…
operator_idstringIdentifier for the operator or system triggering the eventoptionalOP100
notesstringAdditional notes or comments about the eventoptionalEco mode activated.
Numbers 4 columns
water_usage_litersfloatAmount of water used during the event, in liters0 or more · optional120.7
duration_secondsintegerDuration of the event in seconds0 or more · optional1800
location_latitudefloatLatitude coordinate of the device-90 to 90 · optional36.7783
location_longitudefloatLongitude coordinate of the device-180 to 180 · optional-119.4179
Dates and times 1 column
event_timestampdatetimeDate and time when the event occurred2024-06-01T08:01:45
True or false 1 column
sustainability_flagbooleanIndicates if the event is related to a sustainability interventionoptionalfalse

Use it for

  • sustainability…23%22 of 94 rowsmean water usage lite…125.9operat…13.1fault100.8optimi…

    An agriculture dashboard

    The sustainability_flag rate, water_usage_liters by event_type and a breakdown of operator_id. Excel, Power BI or Tableau.

  • Why do the 16 fault rows have a mean water_usage_liters of 13.1?

    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 events with device_id, farm_id and event_timestamp 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

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset94 rows17 columns
Yours1,000 rows17 columnslocation_latitude: UK only

blueprint · smart-irrigation-system-event-logs

Behind this dataset

Same schema. As many rows as you need.

These 94 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 event generated by an irrigation device
  • Events include type (activation, fault, optimization), timestamp, device ID, and water volume impacted
  • Fault events must indicate severity and whether remote intervention resolved the issue
  • Optimization events must record the sustainability metric improved (e.g., water saved, energy reduced)
  • Only devices registered to SME farms are included
Rows
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
smart-irrigation-system-event-logs

More in Agriculture

Browse all
Also in AgricultureIoT Precision Irrigation Sensor DataAgri-Market Price Fluctuation RecordsAgri Cold Storage IoT MetricsAll 1,967 datasets

What should your data show?

Preview 20 rows free
No signup. No card.