Growing degree days (GDD) are the quiet workhorse of agricultural planning. They turn a messy stream of daily temperatures into a single running total that predicts, with surprising accuracy, when a crop will emerge, flower, and mature, and when the insects that feed on it will hatch. If you grow, advise, insure, or study anything that grows, GDD by zip code is often more useful than the raw temperatures themselves.
What a growing degree day actually measures
The idea is simple. Most plants and insects do almost nothing below a base temperature, often 50°F for corn and many pests, and their development speeds up as it gets warmer. A growing degree day is the amount of warmth accumulated above that base in a single day. The common formula takes the day’s high and low, averages them, and subtracts the base: GDD = ((high + low) / 2) − base, with any negative result counted as zero. Add up the daily values from a start date and you get accumulated GDD, the number that actually drives predictions.
A concrete example makes it click. On a day with a high of 78°F and a low of 54°F, the average is 66°F. Against a base of 50°F that day contributes 16 GDD. String together a warm week and you might accumulate 100+ GDD; a cool, cloudy stretch might add almost nothing. Corn typically needs roughly 2,700 GDD from planting to maturity, so a grower can watch the accumulation and forecast harvest weeks ahead.
Why zip code resolution matters
GDD is intensely local. Two zip codes an hour apart can differ by hundreds of accumulated degree days over a season because of elevation, proximity to water, and urban heat. Fresno’s 93720 in California’s Central Valley banks GDD fast and grows a long season; Buffalo’s 14201, moderated by Lake Erie and a northern latitude, accumulates far more slowly and starts later. A statewide or even county-wide average washes out exactly the differences a grower or pest scout cares about. Matching GDD to the zip code where the field, orchard, or insured property actually sits is what makes the number actionable.
Who uses GDD, and for what
Growers use accumulated GDD to time planting, nitrogen application, and harvest. Extension services and pest managers use it to predict insect emergence, codling moth in apples and corn borer in the Midwest hatch at well-known GDD thresholds, so a scout knows when to check traps instead of guessing. Crop insurers and ag lenders use historical GDD to model yield risk by location. Researchers use long GDD series to study how growing seasons are shifting. In every case the common need is the same: a clean, location-specific history rather than a single year pulled from one weather station.
Getting GDD data without building it yourself
You can compute GDD from raw NOAA daily highs and lows, and for one location that is a reasonable afternoon project, our guide to getting NOAA data into Excel walks through the download and cleanup. The work compounds quickly across many zip codes and many years: you need consistent daily highs and lows, a decision on how to handle missing days, and a base temperature suited to your crop. Because GDD is derived directly from daily temperature, the fastest path is usually to start from a clean daily temperature history and apply the formula. Our 10 years of daily temperature data by zip code gives you the daily highs and lows for every US zip code in one Excel file, ready to drop the GDD formula onto. If you need GDD pre-calculated for a specific base temperature or region, that is a common custom request, email contact@weatherdatabyzipcode.com with your crop and base and we will scope it.
A note on base temperatures
The base you choose changes everything, so match it to the organism. Corn and soybeans use 50°F. Many cool-season crops and some pests use 40°F or 41°F. Wine grapes are often tracked with the Growing Degree Day model from a 50°F base between April and October. Some models also cap the daily high (for example at 86°F for corn) because development plateaus in extreme heat. Decide the base and cap first, then accumulate, running the same field against two different bases produces two very different numbers, and mixing them is the most common GDD mistake we see.
Related guides: historical temperature data by zip code, precipitation data by zip code, and historical snowfall data by zip code.
Get free data: our four overall-average datasets (temperature, rainfall, snowfall, and humidity — every US zip code) are free to download here.