Click on author name to view affiliation information
A new smartphone vegetable irrigation scheduling application (VegApp) was compared with current irrigation scheduling recommendations and soil moisture sensor (SMS)–based irrigation for growing tomato (Solanum lycopersicum) in southern Georgia during Spring 2016 and 2017. Plants were grown using plastic mulch and drip irrigation following standard production. The VegApp-scheduled irrigation based on crop evapotranspiration (ETc) values calculated daily from meteorological data retrieved from nearby weather stations, whereas ETc rates for current water balance (WB)–based recommendations were calculated from historic averages for the region. Water usage, soil moisture tension, fruit yield and quality, and foliar macronutrient content were measured. In 2016, plants grown using SMS-based irrigation applied the least water followed by the VegApp- and WB-grown plants. In 2017, WB-treated plants received the least water, followed by VegApp- and SMS-grown plants. Total marketable yields were similar among treatments and years. Irrigation water use efficiency (IWUE) varied between year and irrigation regime, with SMS-grown plants having a significantly greater IWUE than the other treatments in 2016. Plants irrigated using the VegApp had a greater IWUE than SMS-irrigated plants in 2017. Differences in IWUE were largely the result of variable irrigation volumes and not changes in yield. Fruit total soluble solids (TSS) were unaffected by treatment in either study year. Fruit pH was affected by irrigation treatment in 2017. Foliar nitrogen concentrations were affected by irrigation regime in 2017, with VegApp-grown plants having significantly greater concentrations of foliar N than other irrigation treatments. The results of this study suggest that the VegApp could be a reliable tool that can be used by growers to produce yields comparable to currently accepted irrigation scheduling practices and reduce water use in some seasons.
Georgia produces more than 3800 acres of tomato valued at more than $56 million annually (Wolfe and Stubbs, 2016). Tomato in Georgia are grown almost exclusively using plastic mulch with drip irrigation. In southwest Georgia, where considerable production occurs, groundwater resources are relatively abundant and growers often over irrigate. However, over irrigating tomato not only wastes water but also can reduce yields (Locascio, 2005).
Current recommendations for drip-irrigated tomato in Georgia and Florida are based on variations of the WB method (Harrison, 2009). The WB method estimates daily crop water use based on historic evapotranspiration (ETo) values for a region adjusted with a crop coefficient (Kc) (Allen et al., 1998). Current recommendations use a range of Kcs based on five stages of tomato growth (Dukes et al., 2015). An advantage of using the WB method is that it allows growers to anticipate crop water requirements at certain times during the growing season and plan irrigation accordingly. Irrigating solely based on predicted ETc values can be inaccurate because of changes in annual weather patterns and differences in production practices for which Kc were developed (Amayreh and Al-Abed, 2005).
In lieu of using the WB method, some growers may use a form of soil moisture–based irrigation. Personal observations by the authors suggest that the most common soil moisture–based method used is the “feel method,” where irrigation is started when the soil “feels” dry (Maynard and Hochmuth, 2007). Other methods of soil moisture–based irrigation may use tensiometers, granular matrix, or resistance-based sensors to determine thresholds for irrigation management (Cardenas-Lailhacar et al., 2010; Munoz-Carpena et al., 2005). Soil moisture sensor-based irrigation has been shown to be more efficient than a time-based system (Zotarelli et al., 2009a, 2009b, 2011). However, proper placement of sensors to accurately reflect conditions experienced by the plant can be challenging (Dabach et al., 2015). Furthermore, placement of sensors within an irrigation zone can be problematic for growers with heterogeneous soils or variable topography within a field. Irrigation thresholds may also be affected by factors such as soil type and depth of drip tubing (Coolong, 2016).
Recently, smartphone applications have been developed that scheduled irrigation using real-time weather data to calculate ETo [Smartirrigation App (University of Florida, 2012)]. These tools use meteorological parameters to determine irrigation schedules based on ETc calculated, using a Kc and ETo in the following relationship: ETc = ETo × Kc. The suite of applications can schedule irrigation for avocado (Persea americana), citrus (Citrus sp.), strawberry (Fragaria ×ananassa), cotton (Gossypium hirsutum), and several vegetables. The cotton smartphone irrigation–scheduling application resulted reductions in irrigation water use of 40% to 75% with concomitant 10% to 25% increases in yield in Georgia when compared with the WB method recommended for cotton (Vellidis et al., 2015).
The VegApp currently can be used to schedule irrigation for four vegetables, cabbage (Brassica oleracea), squash (Cucurbita pepo), tomato, and watermelon (Citrullus lanatus). Weather data are retrieved from the Florida Automated Weather Network or the University of Georgia Weather Network and are used to calculate ETo from air temperature, solar radiation, wind speed, and relative humidity measurements using the Penman–Monteith equation (Migliaccio et al., 2016). Each new field registered in the VegApp by a user is automatically associated with the closest weather station; however, the user has the option to select any of the other available weather stations. The VegApp uses ETo from the prior 5 d to calculate an average ETo. Then ETc is estimated using Kc curves developed by the University of Florida based on a days-after-transplanting (DAT) model of crop maturity (Dukes et al., 2015; Stanley and Clark, 2009). The Kc curve for tomato was developed for drip-irrigated crop grown with plastic mulch (Dukes et al., 2015; Stanley and Clark, 2009). The VegApp can provide an irrigation schedule for the subsequent week or longer. The irrigation schedule is provided to the user as an irrigation run time per day. Additional model variables used by the VegApp to schedule irrigation include crop, row spacing, irrigation rate, irrigation system efficiency, and planting date. The VegApp uses an ETo replacement model. It does not account for precipitation or soil types. It was designed for use with vegetables grown in a drip-irrigation and raised-bed plastic mulch production system (Migliaccio et al., 2016). Because the performance of the VegApp had not been evaluated in southern Georgia, the objective of this study was to determine the utility of the VegApp for tomato growers in Georgia. Water usage, tomato yield, and fruit quality were evaluated using the VegApp and accepted irrigation scheduling methods.
This study was conducted at the University of Georgia Tifton Vegetable Park in Tifton, GA (lat. 31°5′N, long. 83°5′W), in 2016 and 2017. The soil is a Tifton loamy sand series (0% to 2% slope). ‘Red Bounty’ (HM Clause, Davis, CA) tomato transplants were grown by a local greenhouse producer (LTF Greenhouses, Tifton, GA) in 128-cell trays (Speedling, Ruskin, FL).
Soils were fumigated with chloropicrin (194 lb/acre) and 1,3-dichloropropene (129 lb/acre) (Pic-Chlor 60; TriEst Ag Group, Tifton, GA) when plastic was laid. Irrigation was supplied with a single line of drip-irrigation tubing [12 inches emitter spacing, 0.50 gal/min per 100 ft at 10 psi (Chapin DLX; Jain USA, Haines City, FL)]. Drip tubing was placed in the center of the row at a depth of 1–2 inches. Fumigation, plastic laying, and preplant fertilizer were applied using a raised-bed plastic mulch layer with attached fumigation system and fertilizer hopper (SuperBedder; Kennco Manufacturing, Ruskin, FL). Beds were 6 inches tall by 32 inches wide spaced on 6-ft row centers covered with a 1.1-mil-thick totally impermeable film plastic mulch (Vaporsafe RM, TIF, 60 inches; Raven Industries, Sioux Falls, SD). Preplant fertilization consisted of 50 lb/acre nitrogen (N) [5.0N–4.3P–14.5K (Rainbow Plant Food; Agrium, Tifton, GA)] placed in the row immediately before laying plastic mulch. An herbicide mixture containing the active ingredients, 0.12 lb/acre flumioxazin (Chateau; Valent USA, Walnut Creek, CA), 0.7 lb/acre S-metolachlor (Dual Magnum; Syngenta, Greensboro, NC), 0.38 lb/acre ethalfluralin (Curbit 3 EC; Loveland Products, Loveland, CO), and 0.84 lb/acre glyphosate (RoundUp WeatherMax; Monsanto, St. Louis, MO) was applied between rows with a shielded sprayer ≈2 weeks before transplanting. Seedlings were transplanted on 28 Mar. 2016 and 4 Apr. 2017. Within-row spacing was 22 inches. A severe wind storm on 5–6 Apr. 2017 damaged many seedlings and all plants were replaced on 12 Apr. 2017. Stakes were placed between every plant and plants were strung three times for support. Treatments were arranged in a randomized complete block design with five replications of WB and VegApp plots and four replications of SMS-managed plots in 2016 and four replications of each treatment in 2017. Each treatment plot contained ≈30 and 20 plants each in 2016 and 2017, respectively. Plants were watered equally for ≈3 and 4 weeks after transplanting in 2016 and 2017, respectively, at which time irrigation treatments were implemented. About 10 d after planting, weekly applications of liquid fertilizer were begun at a rate of 15 lb/acre N [7N–0P–5.8K (Big Bend Agri-Services, Cairo, GA)]. A season total of 170 and 155 lb/acre N were applied in 2016 and 2017, respectively. Fungicides and insecticides were applied weekly according to commercial recommendations for watermelon grown in Georgia (Horton, 2016).
The VegApp calculated ETc from weather data collected by the University of Georgia Weather Network weather station in Tifton. Data were used to calculate ETo from air temperature, solar radiation, wind speed, and relative humidity measurements using the Penman–Monteith equation (Migliaccio et al., 2016). Then ETo was adjusted using a Kc based on a DAT model of crop maturity (Dukes et al., 2015). Additional model variables entered into the VegApp include row spacing, irrigation rate (gallons per 100 ft/h), irrigation system efficiency, and planting date. The VegApp then calculated an average ETo from data collected over the previous 5 d and estimated ETc based on the following equation: ETc = ETo × Kc. The VegApp then estimated irrigation run times using the previously entered row spacing, flow rate, and system efficiency. This irrigation estimate was then used for the next 7 d, after which time irrigation needs were recalculated. Total run times were split into two daily irrigation events (14 per week). The VegApp does not integrate rainfall into the irrigation schedule and it does not account for soil type (Migliaccio et al., 2016).
Irrigation schedules for WB-managed plots were calculated based on estimated crop water demand using historic rates of ETo adjusted with a Kc for tomato. The Kc used in this study were for plasticulture-grown tomato and were as follows: 0–21 DAT = 0.4, 21–42 DAT = 0.75, 42–91 DAT = 1.0, 91–105 DAT = 1.0, and 105–119 DAT = 0.85 (Dukes et al., 2015). Historic ETo for each month was estimated from a 10-year monthly average of measured ETo rates for several geographical regions of Florida (Dukes et al., 2015). Because of its proximity to the research site, historic ETo rates attributed to northwest Florida were used. Total ETc was then divided by irrigation system efficiency, which was estimated to be 95% for VegApp and WB treatments, to determine total irrigation volume. Drip-irrigation flow rate and row spacing were then used to calculate the time required to apply the desired volume of water. Required irrigation run times were divided into two equal daily irrigation events. Irrigating tomatoes twice daily would reflect good grower practices for the region. Rainfall amounts were not included in irrigation calculations in WB- or VegApp-based treatments. Irrigation water use efficiency was determined by the following formula: IWUE = marketable yield/Irrigation applied during study period.
The SMS-based irrigation regime was automated using paired-switching tensiometers (model RA 6 inches; Irrometer, Riverside, CA) (Coolong, 2016; Coolong et al., 2011). Plots receiving SMS-based irrigation were controlled independently and each plot had a pair of tensiometers. In brief, one tensiometer functioned to turn on irrigation at the set point reflecting a higher (drier) soil moisture tension whereas the other turned it off at the set point indicating the lower (wetter) soil moisture tension. Tensiometers were placed ≈6 inches from a drip emitter and a tomato plant at a depth of 6 inches from the bed surface. Irrigation treatments had set points of on/off: −18/−10 kPa, which were estimated to reflect 75% of plant available water and field capacity, respectively, for the soil at the research site. Water applied in all treatments was recorded weekly using mechanical flow meters (DLJSJ50 Water Meter; Daniel L Jerman Co., Hackensack, NJ).
Soil moisture probes (Watermark, Irrometer) were used in combination with a smart sensor array (SSA). The SSA consists of smart sensor nodes and gateway sensor nodes, which consist of a circuit board, a radio frequency transmitter, as well as soil moisture and temperature sensors (Vellidis et al., 2008). Environmental data from the array were recorded every 5 min and transmitted to a server hourly (Vellidis et al., 2013). Probes were placed at 6-, 10-, and 14-inch depths in each plot to monitor soil moisture levels. Sensors were placed into holes and then sealed with mud slurry made from soil removed from the hole. Sensors were placed ≈6 inches from drip irrigation emitters in each plot.
Midday leaf water potential (ψL) measurements were conducted on 4 and 15 June 2016 and 15, 19, and 26 June 2017. Measurements of ψL were conducted within 1.5 h of solar noon in both years of the study. Plant ψL was measured using a pressure chamber (model 615; PMS Instrument Co., Albany, OR) using two fully expanded leaflets exposed to full sunlight from plants near the center of each plot. Plant material was analyzed within 1 min of sampling.
Tomato foliar macronutrient content was determined by taking one newest fully expanded leaf from 15 to 10 representative plants from the center of each plot in 2016 and 2017, respectively. Each sample was oven-dried at 122 °F or a minimum of 10 d. Samples were analyzed by a commercial laboratory (Waters Agricultural Laboratory, Camilla, GA) for nutrient content.
Tomatoes were harvested at a red-ripe stage, six times in 2016, beginning on 14 June and ending 11 July. In 2017, tomatoes were harvested five times beginning on 21 June and ending 21 July. All fruit were counted and graded based on U.S. Department of Agriculture grade standards for fresh market tomatoes (USDA, 1991). Tomato internal quality parameters were measured on five randomly selected, extra-large, fully ripened fruit from each treatment replication. Fruit TSS and pH were determined by slicing tomatoes longitudinally into 10-mm-wide slices that weighed ≈55 g. Two slices were taken from the center each of the five fruit and combined in a 20-fl oz blender (Blend N Go Blender; Oster, Boca Raton, FL) and processed into a liquid pulp. About 5.0 µL of the pulp sample was then tested using a refractometer (Brix Stick; Cole Parmer, Vernon, IL) for TSS levels. A 45-mL subsample of the liquid pulp was placed into a 50-mL centrifuge tube and spun at 1880 gn for 5-min at 28 °C (Allegra 25R; Beckmann-Coulter, Atlanta, GA) and repeated. Then 15 mL of the supernatant was filtered through 50-grade cheesecloth (VeraTec Cheesecloth; Fiberweb, Old Hickory, TN). Internal pH was measured using 600 µL of the filtered supernatant, which was diluted with 39.4 mL of deionized water and transferred into a titrator (DL15; Mettler Toledo, Leicester, UK).
Data were subjected to the general linear model (GLM) procedure and mean separation using Tukey’s honest significant difference test (P < 0.05) when appropriate with SAS statistical software (version 9.3; SAS Institute, Cary, NC).
The ETc during the study was greater in 2016 than 2017. This was because of the longer study period in 2016 (84 d) compared with 2017 (68 d) and a higher ETc in late May and June 2016 compared with 2017 (Table 1). Average daily high air temperatures in June 2016 and 2017 were 90.2 and 85.8 °F, respectively. Total rainfall levels were greater in the 2017 growing season compared with 2016. The difference was most notable in June when 5.11 inches were received in 2017 compared with 3.94 inches in 2016. Most rain in June 2016 came from a single event early in the month.
During the 2016 growing season the WB method of irrigation applied 483,880 gal/acre of water, which averaged 5760 gal/acre per day (Table 2). The VegApp and SMS-managed irrigation systems applied 353,440 and 206,850 gal/acre for the season, respectively. In 2016, the VegApp and SMS irrigation systems applied a daily average of 4210 and 2640 gal/acre, respectively. The SMS irrigation method applied the least amount of water in 2016, which is similar to results obtained in other studies using tensiometers for irrigation scheduling (Smajstrla and Locascio, 1990). The VegApp applied less water than estimated ETc (Tables 1 and 2). Irrigation volumes in 2017 were lower than 2016 levels for WB and VegApp methods. The WB irrigation method used 180,050 gal/acre irrigation water, whereas the VegApp and SMS irrigation treatments used 202,550 and 250,060 gal/acre water, respectively. The VegApp- and WB-based methods applied less water on a daily basis in 2017 than 2016. The VegApp primarily applied less water in 2017 because of lower ETc compared with 2016. However, WB-daily irrigation volumes would be expected to be consistent from year to year as historic averages for ETo are used. There are two likely reasons for this. The 2017 study period season was ≈16 d shorter than the 2016 study period, and the Kc for tomato at the end of the study period was 1.0 compared with 0.4 and 0.75 near the beginning of the study. Therefore, the 2016 irrigation applications would be weighted toward more days with the highest possible irrigation volumes, resulting in more average daily water applied. In addition, there were several significant rain events in June and July 2017, which resulted in scheduled irrigations in the VegApp and WB being discontinued for a total of 10 d. This was carried out to reflect grower practices where saturated soils would not be irrigated because of the potential for soil-borne diseases. The VegApp-irrigated plots used relatively more water compared with WB-managed plants in 2017. This suggests that the VegApp may over irrigate in cooler and wetter years or under irrigate in hotter and drier seasons. Irrigation in the SMS-based treatments was allowed to remain on after the rain events in June and July to account for tensiometers detecting increased soil moisture levels and not starting irrigation during rain events. Currently, the contribution of rainfall not been incorporated into the VegApp because of limited information regarding the impact of rain on soil moisture levels under raised beds covered with plastic mulches and the potential for spatial variability in precipitation (Migliaccio et al., 2016). The increased relative water applied with SMS-based irrigation suggests that despite saturated soils surrounding plots, rainfall may not have affected soil moisture levels within the planted beds. Soil water tension readings indicate that soil moisture levels were unaffected significantly by rainfall (Table 3).
When averaged over the two study years, the VegApp used 16% less water than the WB method. The SMS-managed plots used 31% less water than the WB method. The VegApp also used less water in both seasons than estimated ETc. Some of this difference may be because of how the VegApp calculates irrigation. It uses data from the prior 5 d to estimate irrigation for the upcoming week, which could allow for differences if weather conditions rapidly change. However, another reason for this to occur in both seasons could be that the Kc used by the VegApp may differ than those used to estimate ETc (Dukes et al., 2015). The VegApp- and SMS-based irrigation may reduce water applications compared with methods relying on historic ETo to manage irrigation. Other studies have also demonstrated the efficiencies of a microclimate and SMS-based irrigation compared with historical ET-based methods (DePascale et al., 2011).
There was a significant treatment by year by depth by time interaction for soil moisture levels (F = 4.4, P ≤ 0.001) (Table 3). In Apr. 2016, plant canopies were small and soil moisture levels remained high at all depths (Table 3). Soil moisture levels remained the highest in WB-treated plots in 2016, with the exception of the VegApp-treated plots at a depth of 6 inches during the July measurement period. Soil tension values overall were low in 2016. On-farm trials in southwest Georgia with tomato have shown that growers typically maintain soil moisture levels between 0.5 and 5.0 cbar (data not shown) at soil depths of 6–12 inches. The SMS-treated plots had significantly higher soil-water tension values at 6-inch depths in June and July 2016 compared with the VegApp-treated plots but there were no differences between the two treatments at 10- or 14-inch depths for the same time period. This may be because of the relatively shallow placement of the porous tip of the tensiometers (6–8 inches deep), which could result in increasing demand for water at shallower depths compared with the VegApp (Marouelli and Silva, 2007; Marouelli et al., 2004).
Significant differences in moisture levels among treatments in 2017 were primarily observed in May (Table 3). The VegApp-treated plots used more irrigation water in May than WB-treated plots because of higher ETc values. However, despite using more water, the VegApp-treatments experienced higher moisture tension values than the WB-treated plots at 6- and 10-inch depths (Table 3). This may be due to Kc varying when used under a different set of climate conditions from which they were developed, particularly early in crop growth (Jagtop and Jones, 1989). In June and July 2017, there were no differences in soil moisture tension between irrigation treatments at any depth, although soil water tension values were generally higher in June and July 2017 compared with the same period in 2016. Analysis of main effects indicated that despite lower ETc values in 2017, soil moisture tension significantly increased compared with 2016 (data not shown). In general, average soil moisture tension values were low for most treatments and time periods during the 2017 study. It is possible that ETc estimated in the cooler and wetter 2017 growing season may have underestimated water use by the crop in resulting in higher moisture tension values in the VegApp-managed plots. Subtle differences in drip tape or sensor placement between years may also have contributed to the increase in soil moisture tension in 2017. Midday ψL readings taken in June were low (<5 bar) and were not different among treatments or years suggesting that the differences observed in soil moisture tension between years or treatments did not affect plant moisture status (data not shown).
There was a significant year by treatment interaction for yield of large fruit (F = 4.6, P ≤ 0.05) (Table 4). There were no treatment-by-year interactions for total, extra-large, and medium fruit yields. In 2016 and 2017, plants grown using the VegApp had the highest numerical yield, although this was not significantly different from the other treatments. Total marketable yields ranged from 43,520 (SMS treatment) to 52,220 lb/acre (VegApp treatment) in 2016. In 2017, total marketable yields ranged from 45,200 (WB treatment) to 51,780 lb/acre (VegApp treatment). Extra-large fruit yields increased in 2017 compared with 2016 (F = 21.7, P ≤ 0.01), whereas large fruit yields concomitantly decreased. Medium fruit yields were unaffected by treatment and were a minor portion of the total fruit harvested. The average fruit weight was unaffected by treatment or year and ranged from 237 to 264 g/fruit. The percentage of cull fruit was unaffected by treatment but was significantly affected by year (F = 224.1, P ≤ 0.01) (data not shown). Cull fruit ranged from 7.0% to 11.6% in the VegApp- and SMS-based treatments, respectively, in 2016. In 2017, cull fruit ranged from 28.7% to 30.6% in the SMS- and VegApp-based treatments. Cull rates were primarily due to blossom end rot, misshapen fruit, and minor damage from green stink bug (Chinavia hilaris) and two spotted spider mites (Tetranychus urticae). Overall cull rates were similar to those found in nearby commercial tomato fields for the two seasons (T. Coolong, personal observation). Total marketable yields were comparable with those expected from a commercial tomato field in Georgia (Kelley and Boyhan, 2017).
There was a significant year-by treatment interaction for IWUE (F = 22.6, P ≤ 0.01) (Table 4). In 2016, plants grown using the SMS-based irrigation method had a significantly higher IWUE compared with those grown using the VegApp and WB-methods (Table 4). The SMS-based treatment applied 41% and 57% less water than the VegApp- and WB-based treatments, respectively, in 2016. In 2017, the VegApp had a significantly greater IWUE than the SMS-irrigated plants. The IWUE of WB-grown plants was not significantly different from other irrigation treatments in 2017. The increased IWUE in 2017 for VegApp- and WB-grown plants was because of the decrease in irrigation volume used (Table 2). During this study, the SMS-grown plants had the most consistent IWUE, with 0.21 and 0.20 lb/gal in 2016 and 2017, respectively. These values were similar to those reported for fresh market tomato in north Florida (Zotarelli et al., 2009b). The IWUE of the other irrigation treatments were more variable. This variability was the result of fluctuations in water applied and not differences in yield (Table 2). Prior studies with tomato suggested that maximum yields were consistently produced under relatively broad irrigation ranges of 50% to 100% ETc (Locascio et al., 1989; Olson and Rhoads, 1992). Furthermore, numerous reports using deficit irrigation have been shown to regularly reduce irrigation below 100% ETc use while not affecting yield of plasticulture-grown fresh market tomato (Favati et al., 2009; Ozbahce and Tari, 2010; Patane and Cosentino, 2010). Our data indicate that the VegApp applied less than 100% ETc in both study years, while maintaining commercially acceptable yields.
Fruit pH was affected by treatment (F = 7.9, P ≤ 0.01) and year (F = 439.5, P ≤ 0.01) but fruit TSS was not (Table 5). Fruit TSS values ranged from 3.91% to 4.03% in the SMS- and VegApp-treated plots, respectively. Fruit pH values were significantly higher in WB- and SMS-based plots compared with those grown using the VegApp. Fruit pH levels increased from 3.41 in 2016 to 4.04 in 2017. Tomato fruit pH levels have previously been reported to be affected by irrigation management (Mitchell et al., 1991; Tuzel et al., 1994), although some studies have reported no impact of irrigation on fruit pH (Hanson et al., 2006). Regardless of treatment, pH values were lower than those deemed to be preferred (≤4.30) according to the reference scale of analytical parameters for tomato pulp (Patane and Cosentino, 2010).
There were significant year-by treatment interactions for foliar N (F = 3.6, P ≤ 0.05). There were no treatment-by-year interactions for magnesium (Mg), phosphorus (P), potassium, calcium (Ca), or sulfur (S) (Table 6). Foliar N concentrations were unaffected by irrigation regime in 2016 but plants irrigated with the VegApp had significantly higher N levels than the WB and SMS-irrigated plants in 2017. In 2017, VegApp-irrigated plants had foliar N concentrations of 5.56% compared with 5.04% and 4.61% in the WB- and SMS-treated plants, respectively. Foliar P concentrations were unaffected by treatment and concentrations ranged from 0.36% to 0.45% in VegApp-grown plants in 2016 and WB-grown plants in 2017, respectively. Potassium, a key nutrient for tomato fruit development ranged from a low of 3.35% in VegApp-grown plants in 2017% to 4.05% in WB-treated plants in 2016. Foliar Ca concentrations displayed similar trends in 2016 and 2017. Plants grown using the VegApp had the highest numerical levels of foliar Ca followed by WB- and SMS-grown plants; however, differences were not significant in either year. Foliar Mg concentrations were affected by treatment (F = 16.3, P ≤ 0.05) and year (F = 81.2 P ≤ 0.01). Foliar Mg concentrations were significantly greater in the VegApp-treated plants (0.48%) compared with the other irrigation regimes (0.43%) in 2016. In 2017, the VegApp-grown plants had significantly greater Mg concentrations than SMS-treated plants. Foliar S concentrations were unaffected by irrigation regime in either study year but were significantly greater in 2017 (F = 22.9, P ≤ 0.05) (1.06%) compared with 2016 (0.80%). All macronutrient concentrations were within or greater than expected ranges for field-grown tomato (Bryson et al., 2014). Only N and Mg concentrations in the foliage were affected by irrigation regime and both were greater in VegApp-treated plants. The N fertilizer used in this study was nitrate based. Using the VegApp for scheduling irrigation may potentially reduce leaching through more judicious water use during fruit set (when plants were sampled) or potentially improve the ability of a crop to remove nutrients from the soil profile (Dukes et al., 2010).
Numerous studies have shown that applying real-time ETo values obtained by using nearby weather stations can be more efficient than using historic ETo values to determine irrigation scheduling. Performance of the VegApp compared with both WB- and SMS-based irrigation methods in the present study was variable. In 2016, the VegApp applied 27% less water than the recommended WB method, whereas in 2017 it applied 12.5% more. The VegApp could be improved by incorporating rainfall as a factor and using a growing-degree-day–based method to calculate Kc vs. the current DAT-based model. Despite some limitations, the findings from this study suggest that the VegApp is easier to use than manually calculating irrigation needs from historic averages and can produce commercially acceptable yields of tomatoes in southern Georgia.
Contributor Notes
Corresponding author. E-mail: tcoolong@uga.edu.
