Data Used

The design of sDRIPS emphasizes minimal user-side data requirements while leveraging cloud-hosted datasets to ensure scalability and global applicability.

To execute sDRIPS for a given region of interest (ROI), users must provide only two essential inputs:

  1. A boundary polygon file (e.g., Shapefile or GeoJSON) that defines the spatial extent of the analysis.
  2. The operational mode in which sDRIPS should run.

Beyond these minimal requirements, sDRIPS automatically integrates multiple satellite remote sensing and model-based datasets via Google Earth Engine (GEE), including:

  • Satellite imagery (e.g., Landsat, Sentinel)
  • Precipitation estimates (NASA IMERG)
  • Meteorological inputs (NOAA GFS)

Where available, in situ measurements (e.g., local weather station or sensor data) can supplement or replace global datasets. This adaptive design allows sDRIPS to operate seamlessly across varying levels of data availability, from global-scale applications to local field-level analysis.

  • Table 1 (adapted from Khan and Hossain, (2025)) summarizes the minimal data and credentials required to run sDRIPS.
  • Table 2 (adapted from Khan et al., (2026)) outlines the global datasets integrated into sDRIPS for estimation and analysis.

Table 1. Minimal data and credentials required to run sDRIPS

Sr. No. Requirement Purpose
1 Google Earth Engine (GEE) Account Access to cloud computing power and hosted satellite datasets
2 Precipitation Processing System (PPS) Account Download NASA IMERG precipitation data
3 Boundary Polygon (Shapefile / GeoJSON) Defines the spatial extent of the analysis
4 Crop Type and Planting Date Provides crop-specific information needed for accurate ET estimation
5 Sensor or Weather Station Data (optional) Improves estimation of net water requirement; required only if in-situ data are to be used

Table 2. Global datasets integrated into sDRIPS

Optional supply comparison

Canal discharge data are not required for the core net water requirement workflow. They are used when users want to compare estimated net water requirement with available canal water supply.

Dataset Dataset ID on GEE Band Name / Derived Products Description Spatial Resolution Temporal Resolution
Global Forecasting System (GFS) NOAA/GFS0P25 temperature_2m_above_ground Air temperature 25 km 6 h
u_component_of_wind_10m_above_ground Wind speed (u component)
v_component_of_wind_10m_above_ground Wind speed (v component)
specific_humidity_2m_above_ground Specific humidity
--- --- Pressure, estimated using the hypsometric equation
GEE and NOAA total_precipitation_surface 168 h precipitation
Landsat 8 and Landsat 9 satellite series LANDSAT/LC08/C02/T1_TOA
LANDSAT/LC09/C02/T1_TOA
B2 Blue 30 m 16 d individual, 8 d combined
B4 Red
B5 NIR
B6 Shortwave IR
B10 Low gain thermal
B11 High gain thermal
Sentinel 1 satellite COPERNICUS/S1_GRD VV Single co-polarization, vertical transmit/vertical receive 10 m 10 d
Shuttle Radar Terrain Mapping (SRTM) USGS/SRTMGL1_003 --- Digital elevation map 30 m ---
Global Land Cover Classification (GLCC) COPERNICUS/Landcover/100m/Proba-V-C3/Global discrete_classification Land use land cover 100 m ---
IMERG GPM --- --- Precipitation 10 km Around 4 h
SMAP satellite NASA/SMAP/SPL3SMP_E/005 soil_moisture_am Soil moisture 9 km Daily
ISRIC SoilGrids --- --- Field capacity 250 m ---
Canal discharge data --- --- Discharge, used to compare net water requirement with water supply --- ---

Source: adapted from Table 2 in Khan and Hossain (2026).