Assessing Hourly and Daily Reference Evapotranspiration from NASA POWER Data: Implications for Irrigation Water Requirement

Imagine you are trying to figure out how much water a thirsty garden needs to survive. In the world of farming and water management, scientists use a special number called "Reference Evapotranspiration" (or ET₀ for short) to guess this. Think of ET₀ as the garden's "thirst meter." It measures how much water the air is trying to steal from the soil and plants through a process called evaporation (water turning into vapor) and transpiration (plants sweating). To calculate this thirst, scientists use a famous recipe called the FAO-56 Penman-Monteith method. This recipe mixes ingredients like sunshine, wind speed, temperature, and how dry the air is.

Here is the tricky part: the recipe isn't a simple straight line; it's a bit like a rollercoaster. If you have a little bit of sun, the thirst goes up a bit. But if you have a huge burst of sun for just one hour, the thirst doesn't just go up a little; it spikes wildly because of how the ingredients mix together. Usually, farmers and planners use "daily" weather reports—averages of the whole day—to feed into this recipe. It's like saying, "The sun was bright today," without realizing that the sun was blindingly bright for just two hours and barely there for the rest. The big question is: Does smoothing out the day into one average number give us the right answer for how much water to pour, or does it trick us?

---

The Great Time-Travel Experiment

Two researchers, Pankaj Agrawal and Pratik Gite, decided to play detective with weather data from NASA's POWER database. They wanted to see what happens when you calculate the garden's thirst using two different time-travel methods.

Method A (The Hourly Detective): They took the weather data hour-by-hour, calculated the thirst for every single hour, and then added them all up at the end of the day. This is like tasting the soup every 15 minutes to see exactly when it gets too salty.

Method B (The Daily Summarizer): They took the average weather for the whole day (average sun, average wind, average heat) and ran that single number through the thirst recipe once. This is like tasting the soup only once at dinner and assuming the flavor was the same all day.

They did this for a whole year in a semi-arid (dry) part of India, a place where getting irrigation right is a life-or-death matter for crops.

The Big Reveal: The Daily Method Overestimates

The results were clear and consistent. The "Daily Summarizer" (Method B) was always, every single day, telling the farmers that the garden was thirstier than it actually was.

On average, the daily method overestimated the water need by 1.2055 mm per day. That might sound small, but over a whole year, it added up to a massive 439.99 mm of extra water that wasn't actually needed. The researchers found that the daily method was wrong about 8.4% of the time compared to the more precise hourly method.

Why did this happen? It comes down to those "rollercoaster" peaks. The garden's thirst spikes wildly during the hottest, sunniest hours of the day (usually between 11:00 AM and 3:00 PM). When you use the hourly method, you catch these spikes and add them up correctly. But when you use the daily average, you smooth out those spikes. You take the super-hot noon and mix it with the cool night, creating a "meh" average temperature. Because the thirst recipe is non-linear, this "meh" average actually calculates more total thirst than the real, spiky reality. It's like trying to calculate the speed of a car that stopped at a red light and then zoomed at 100 mph by saying it drove at a steady 50 mph the whole time; you'd think it covered more ground than it actually did.

When Does the Mistake Get Worse?

The researchers discovered that this mistake isn't the same all year round. It's like a chameleon that gets brighter in certain conditions.

• Winter: When the weather is calm and the sun isn't too fierce, the two methods agree pretty well. The daily average is close enough to the hourly truth.
• Summer: This is where the trouble starts. During the high-energy summer months, when the sun is blazing and the air is dry, the daily method goes haywire. It overestimated the water needed by a huge 165.6 mm just during the summer season alone.
• The Culprits: The researchers found that the mistake gets worst when the air is dry (low humidity) and the sun is strong. They found a very strong link between the error and how dry the air was (a correlation of -0.8337). The drier and hotter it gets, the more the daily average lies about the garden's true thirst.

Why Should You Care?

Imagine you are the person in charge of the water valves for a massive farm. If you trust the "Daily Summarizer," you will turn the water on too much, especially in the summer. You might think the crops are screaming for water when they are actually just fine. This leads to wasting precious water and potentially drowning the roots of your plants.

The paper suggests that for planning irrigation, especially in hot, dry places, we shouldn't just rely on the easy "daily average" numbers. We need to respect the hourly spikes. While daily data is okay for long-term, rough guesses, it fails when we need to be precise about peak water needs.

The Bottom Line

Agrawal and Gite didn't just find a small glitch; they found a systematic bias. They proved that even if you use the exact same weather data source (NASA POWER), simply changing the time you look at it (hourly vs. daily) changes the answer. The daily method smooths out the peaks, but in doing so, it creates a false sense of high demand.

So, the next time you hear about how much water a field needs, remember the rollercoaster. If you only look at the average height of the track, you might miss the terrifying drop that actually defines the ride. For farmers in dry climates, knowing the difference between the average and the peak could mean the difference between a harvest and a drought.