Remote Sensing a Framework for Defining Spatially Explicit Earth Observation Requirements for a Global Agricultural Monitoring Initiative (geoglam)

Global agricultural monitoring utilizes a variety of Earth observations (EO) data spanning different spectral, spatial, and temporal resolutions in order to gather information on crop area, type, condition, calendar, and yield, among other applications. Categorical requirements for space-based monitoring of major agricultural production areas have been articulated based on best practices established by the Group on Earth Observation's (GEO) Global Agricultural Monitoring Community (GEOGLAM) of Practice, in collaboration with the Committee on Earth Observation Satellites (CEOS). We present a method to transform generalized requirements for agricultural monitoring in the context of GEOGLAM into spatially explicit (0.05°) Earth observation (EO) requirements for multiple resolutions of data. This is accomplished through the synthesis of the necessary remote sensing-based datasets concerning where (crop mask, when (growing calendar, and how frequently imagery is required (considering cloud cover impact throughout the agricultural growing season. Beyond this provision of the framework and tools necessary to articulate these requirements, investigated in depth is the requirement for reasonably clear moderate spatial resolution (10–100 m) optical data within 8 days over global within-season croplands of all sizes, a data type prioritized by GEOGLAM and CEOS. Four definitions of " reasonably clear " are investigated: 70%, 80%, 90%, or 95% clear. The revisit frequency required (RFR) for a reasonably clear view varies greatly both geographically and throughout the growing season, as well as with the threshold of acceptable clarity. The global average RFR for a 70% clear view within 8 days is 3.9–4.8 days (depending on the month), 3.0–4.1 days for 80% clear, 1462 2.2–3.3 days for 90% clear, and 1.7–2.6 days for 95% clear. While some areas/times of year require only a single revisit (RFR = 8 days) to meet their reasonably clear requirement, generally the RFR, regardless of clarity threshold, is below to greatly below the 8 day mark, highlighting the need for moderate resolution optical satellite systems or constellations with revisit capabilities more frequent than 8 days. This analysis is providing crucial input for data acquisition planning for agricultural monitoring in the context of GEOGLAM.


Introduction
The coordination of Earth observations (EO) data necessitates first the articulation of spatially explicit EO requirements for monitoring, including where [1], when [2], how frequently [3], over which spectral range, and at what spatial resolution these data are needed.In 2007, there was an attempt by those in the Group on Earth Observations Agricultural Monitoring Community of Practice (GEO Ag CoP) to describe the data necessary for operational agricultural monitoring [4], and a related effort was made to define the requirements specifically for Europe [5].While these efforts provided a sketch of the multiple spatial and temporal scales of required data inputs for a variety of monitoring applications and illustrated the inherent complexity of such an undertaking, they needed refinement and a higher degree of specificity in order to be translatable into data acquisition requests.
In the context of the Group on Earth Observations Global Agricultural Monitoring (GEOGLAM) Initiative-a G20-mandated activity to coordinate satellite-based monitoring of global croplands [6,7]-spatially explicit requirements for agricultural monitoring are a necessary input into data acquisition planning.In 2012, the newly formed Committee on Earth Observations Satellites (CEOS) Ad Hoc Team for GEOGLAM (including members of the GEO Agricultural Community of Practice and CEOS space agency representatives) met to articulate the spatial (Table 1 [8,9], Column B), spectral (Table 1, Column C), and "cloud free" temporal resolution (Table 1, Column D) data requirements for a variety of agricultural monitoring applications or "target products" (Table 1, Columns G-M), based on their combined experiences in research and operational agricultural monitoring [8].
Table 1.The table of requirements for satellite-based Earth observations data, developed by the CEOS Ad Hoc Team for GEOGLAM [8,9].Requirements are broken down by spatial & spectral range (Columns B&C), frequency with which reasonably cloud-free data are required (Column D), geographic extent (Columns E&F), as well as the application or target product for which the data would be used (Columns G-M).Requirements are further refined based on the field size over which acquisitions are required (Column F), or the field sizes for which a certain data type would be useful (Columns G-M)."L" refers to "Large fields" (defined as >15 ha), "M" refers to "Medium fields" (defined as 1.5-15 ha), and "S" refers to "small fields" (<1.5 ha).The symbol "x" or the word "All" indicates that these data are useful for that product's generation for all field sizes.These agricultural monitoring applications include mapping cropped area (crop mask) and crop type area, identifying the crop calendar, monitoring crop condition, forecasting crop yield, retrieving crop biophysical variables (such as leaf area index (LAI), green area index (GAI), and fraction of absorbed photosynthetically active radiation (fAPAR); [10][11][12][13][14]), deriving environmental variables, and identifying agricultural practices and cropping systems (including burning, tillage, transplantation, and cropping intensity) [8].In addition to the framework this provided, the table additionally referenced where the imagery was required (Table 1, Columns E&F)-extent of coverage varies, as does the field sizes for which a given spatial/spectral resolution combination is required [15,16]-as well as when the imagery was required (Table 1, Column D), with most of the requirements being for imagery during the agricultural growing season (AGS), but a few requesting data to be acquired during the non-AGS.Although the requirements detailed herein cover many agricultural areas of the Earth, they have been generated with a particular emphasis on the monitoring of major production areas.

Agricultural Monitoring: Spatial and Temporal Considerations
Due to the rapid rate of change in crop phenology and progress-beneath the weekly time step [5,17]-reasonably cloud-free imagery is generally required with greater frequency for agricultural monitoring than it is for applications that monitor more static phenomena or processes [18].For crop yield and crop condition, for example, clear views are needed roughly weekly or at least biweekly, although even more frequent data are valuable [18][19][20][21][22]. Due to this requirement for frequently sampled data, global cropland monitoring to date has been predominately undertaken with coarse spatial resolution data (defined in the context of GEOGLAM as greater than 100 m) [23,24], with near-daily MODIS-class observations at 250-500 m and with broad spectral coverage providing the primary data source over the past decade [25][26][27][28][29][30][31][32][33][34][35][36][37][38][39].However, analyses relying upon coarse spatial resolution data to monitor cropland dynamics are often confronted with issues of subpixel heterogeneity [16,[40][41][42][43], with many small fields or highly heterogeneous landscapes having variability beneath the spatial resolution of the sensing instrument in use.While moderate spatial resolution (defined in the context of GEOGLAM as 10-100 m) has been used extensively in national scale analyses of land cover, including cropped area and crop type mapping efforts [39,[44][45][46][47][48][49][50][51][52][53][54][55][56][57][58], their limited revisit frequency and/or limitations in on-board storage capacity have meant that these data have been too sparsely collected in time and often also in extent in order to be used for agricultural monitoring at broad scales across the globe [19].
The persistence of cloud cover in certain agricultural regions and during certain portions of the AGS exacerbates the sparseness of usable data [3,5].Meanwhile, as demonstrated by Table 1, particularly Requirements #4-6, the use of moderate spatial resolution data collected at a more frequent rate is a priority growth area for analyses spanning the full extent of croplands for fields of all sizes.With the Landsat archive opening, new moderate resolution missions set to launch, and computational resources growing, global scale analyses are poised to move into the moderate resolution domain [59][60][61][62][63][64], with regional to global datasets at 30 m resolution already demonstrated [65][66][67][68][69].
The requirements established by the CEOS Ad Hoc Team for GEOGLAM (Table 1) build upon the experience of agricultural monitoring experts from around the world (For information on the full membership of those involved in the development of this requirements table and involved in the crop monitoring in the context of the GEOGLAM activity, please refer to the GEOGLAM Community of Practice webpage [9]), who stand in agreement that more frequent moderate spatial resolution imagery are required for operational cropland monitoring (beyond cropped area and crop type) than are presently freely available to and accessible by the public, particularly if more broad scale monitoring is to be undertaken.While Table 1 provides a solid conceptualization of the requirements, we present the datasets and the tools to place each of the individual requirements in its geographical, spatially explicit context with respect to target cropland locations [1], growing season calendar [2], and cloud cover considerations [3].As an example of this process, particularly highlighted here are the requirements to yield reasonably cloud-free views within 8 days over in-season agricultural areas, as articulated by Table 1, Requirement #5.This analysis builds upon previous efforts, in particular taking the cloud cover dataset introduced in Whitcraft et al. (2015) [3] and transforming it to reveal precisely where, when, how frequently, and to what spatial extent data are required, highlighting localities and regions in which cloud cover may present a barrier to optical remote sensing.This paves the way for an analysis of the ways and regions in which we can (or cannot) meet our data requirements for agricultural monitoring (found in the subsequent manuscript by Whitcraft et al. (this issue) [70]).These requirements are an important input into satellite data acquisition planning by CEOS in the context of GEOGLAM.

Datasets & Methods
While the requirements established in Table 1 are explicitly for "cloud-free" data, in reality there are many cases where data that are reasonably cloud-free may be sufficient.The definition of "reasonable" will vary with application and study area, and thus the revisit frequency required for a variety of clarity thresholds are herein considered: 70%, 80%, 90%, and 95% clear, the latter considered virtually cloud-free and clear.

Input Datasets: Where to Image?
The first step in defining EO requirements for global agricultural monitoring is identifying the areas that require monitoring, namely the locations of global croplands [71].To this end, Fritz et al. (2015) [1] have developed a "best-available" cropland mask that indicates the probability that any 0.0083° (~1 km at the Equator) cell contains cropland based on a suite of existing land cover and cropland masks.This harmonizing and synthesizing effort was undertaken in the context of GEOGLAM, and as such has been chosen as the cropland mask for this analysis.Due to the resolution of other input datasets (namely, cloud cover, Section 2.3), and balancing data volume considerations with the need for a resolution sufficiently fine to be scalable to very fine to moderate (<100 m) spatial resolution missions' swath widths (approximately 11 km [Ikonos] to 740 km [AWiFS]), this cropland mask has been degraded to 0.05° (~5.6 km at the Equator).While different cropland probabilities are likely suited for different areas of the globe, a threshold has been set at 20% as it aligns well with understood cropland distributions [33,72].
The requirements are also broken down by the field sizes for which they are prescribed.Generally speaking, larger fields can be adequately imaged using coarser spatial resolution data, while medium fields require moderate spatial resolution data and smaller fields require finer spatial resolution data [73].These relationships are further contingent upon shape, arrangement, fragmentation, and crop type heterogeneity of the fields as well as the imaging bandwidths [15,16], and future articulations of the requirements can be refined by the inclusion of this additional information.However, such datasets do not currently exist at the global level, and in the interim, the broad relationship between field size and necessary spatial resolution is sufficient to allocate fine, moderate, and coarse spatial resolution data acquisitions.A research group at the International Institute for Applied Systems Analysis have deployed an online collaborative tool called "GEO-WIKI" [1,74,75] to gather "crowd-sourced" information on field size.Volunteers from around the world visually interpret high-resolution imagery on GEO-WIKI's Google Earth platform and use visual interpretation to estimate field size.As of 2013, over 50,000 individual fields had been identified, and this point information has been extrapolated to neighboring locations to create a global indicator layer for field size.The requirements table identifies fields as "small," "medium," or "large," corresponding with fields smaller than 1.5 ha, between 1.5 and 15 ha, and larger than 15 ha, respectively.This field size classification system was designed to align with very fine/fine (<5-10 m), moderate (10-100 m), and coarse resolution (100-1100 m) sensor spatial resolutions, respectively, and the ability to have at least the possibility of a few "pure" pixels of each class of sensors' systems fall within each field [5,76].

Input Datasets: When to Image?
Many agricultural monitoring applications including crop yield, crop condition, and crop type mapping rely on data acquired only during the period when crops are actually growing.By contrast, cropland area mapping efforts ("crop mask"), particularly in light of dynamics in year-to-year cropping practices and associated changes in land use, require data throughout the calendar year, although the frequency with which imagery are required is reduced during the non-agricultural growing season as the goal is to detect long-term rather than short-term (i.e., phenological) changes.This seasonal breakdown is provided by the agricultural growing season (AGS) calendars detailed in Whitcraft et al. (2014) [2], with the AGS spanning the period between the median start of season (SOS; green-up onset, emergence of above ground biomass) and the median end of season (EOS; end of senescence, termination of photosynthetic activity) as observed over 2001-2010, and the non-AGS spanning the period between the median EOS and the median SOS.If there are multiple crop cycles within an area during the same year, then the AGS has been defined as beginning with the first SOS and ending with the last EOS.This does not account for (generally brief) periods of inactivity between cropping cycles, and as such may slightly overestimate the periods requiring monitoring.However, to account for year-to-year variations in cropping dynamics, this overestimation may be worthwhile in reducing the risk of missing key periods for monitoring.

Input Datasets: How Frequently to Image for (Reasonably) Clear Views
Whether the requirement (Table 1, Column D) is for a virtually clear view of every pixel within a scene or a partially clear scene is contingent upon the application and the expert opinion of the user, although increasingly scientists are moving toward per pixel analyses as opposed to per scene analyses [66,68,77].To evaluate the multiple thresholds of clarity that may be acceptable, the four definitions of a reasonably clear view will be presented (70%, 80%, 90%, and 95%), all based on daily MODIS Terra surface reflectance (MOD09) quality assessment bits from 2000 to 2012 [78].Any 1-km pixel that contained cloud was flagged as cloudy and then aggregated to 0.05° to show daily percentage cloudy for each day and for each year analyzed.From this, the average percentage cloudy (and its complement, the average percentage clear) for each cell and for each day of the year between 2000 and 2012 was calculated.For the present analysis, this dataset has been further aggregated to show average cloudiness for each calendar month.The full dataset has been documented in Whitcraft et al. (2015) [3].
Cloud cover varies seasonally, geographically, and diurnally, and as such the revisit frequency required (RFR) in order to satisfy a given reasonably clear view requirement (referred to as the "Effective Temporal Resolution" in Table 1) within a certain period varies throughout the year, with location, and also with the acceptable cloud threshold [3,[79][80][81][82][83][84][85][86][87][88][89].As the great majority of moderate resolution EO satellites have morning overpasses, the revisit frequency required herein will be presented assuming a morning (10:30 am local solar time) overpass.
Multi-date image compositing is a common approach to overcoming issues of cloud occultation [19,20,81,[90][91][92].In areas impacted by cloud cover, multiple data acquisitions are necessary in order to piece together a cell or an area with an acceptable final percentage clear (FPC).The revisit frequency required (RFR) to yield a cell with a given FPC (here, 70%, 80%, 90%, or 95% clear) within a certain number of days (d; here, 8 days) is equal to that number of days divided by the number of necessary acquisitions: where P(cloudportion) is the probability that any given portion of a cell is cloudy during a given observation.This probability is the same as the average percentage of a cell that is cloudy, and is based on the assumption that the percentage of any cell that is cloudy is the same as the probability that any given portion of a cell is cloudy.As described in Roy et al. (2006) [93], from which Equation 1 is adapted, this may underestimate the impact of clouds, and as such, it may provide a slightly optimistic outlook for the RFR to meet a reasonable FPC requirement within a certain period (d).

Generation of Requirements Maps
For simplicity of analysis, the year has been divided into its calendar months, and acquisitions are considered necessary during any month for which even one day is actively cropped (based on median SOS and median EOS from Whitcraft et al. (2014) [2]).This may lead to overestimation of the period for which imagery is required, but variability in year-to-year cropping practices and the negative potential impacts of missing the SOS justifies the potentially expanded period of acquisition.
With all of the components of the EO requirements established, it is possible to articulate the spatially explicit revisit frequency requirements for any optical data requirement in Table 1.This is accomplished by assembling these individual layers to provide spatially explicit monthly estimates of revisit frequency required to yield a reasonably clear view within a certain time period, only for the extent of crops that are actively growing (or, in the case of those requirements for imagery during the non-AGS (not discussed herein), for all croplands that are out of season) for that month.For each individual requirement in Table 1, Column D, there is at least a minimum and a preferred "effective temporal resolution" (same as RFR) requirement during the AGS, and in Requirements #4 and #10 a tertiary requirement for imagery outside of the AGS.The focus herein will be on Requirement #5 (10-100m; optical data (visible, reflected-infrared, thermal infrared)), detailing the average RFR to meet each reasonably clear view requirement for its preferred (8-day) effective temporal resolution requirement for all field sizes during each month of the agricultural growing season (Table 1, Column D).While 16-day data has commonly been used [35,91,94], the precision and accuracy of satellite-based estimates, particularly regarding yield and condition, would be improved by having reasonably clear views every 8 days [19,21].

Results
As was shown in Whitcraft et al. (2015) [3], the early-to-mid AGS (between the start of season and shortly after the NDVI maximum) in most areas is more heavily occluded by cloud cover than is the late (or non-) AGS.This is particularly noticeable in India and surrounding areas, where the start of the season (May-June) is followed shortly by the Summer Monsoon (Figure 1).During the months after the Monsoon period for which crops are in season (approximately October-March), the revisit frequency requirement for much of the impacted area (especially India) is around 5-8 days in all scenarios.However, during the monsoon months (June-August), the RFR is almost always less than 1 day, even in the FPC ≥ 70% scenario.Only southern Brazil comes close to having a similar magnitude of seasonal divergence in revisit frequency required (Figure 1).
The revisit frequency required to yield a view at least 70% clear within 8 days varies throughout the calendar year and the AGS, ranging from < 1 day to exactly 8 days, with a mean ranging between 3.9 and 4.8 days, depending on the month (Figure 2a).For November through February, a single revisit (RFR = 8 days) is all that is required to yield a view at least 70% clear for 22%-31% of actively cropped cells globally, although the months with the greatest quantity of actively growing cropland (May-September) are often the most impacted by clouds and therefore require the most frequent revisit (cropland per month is shown in Figure 3a-f).Many of these cells with an RFR of 8 days fall in the areas of South and Southeast Asia, outside of the aforementioned Monsoon season (October to March).For April-June, 3-5 days is the most common revisit frequency required (20%-31% of cells), while in July-October, the required revisit frequency ranges broadly from 2 to 6 days.There are some cells for which a revisit rate of less than 1 day is required, but only during the months of July and August does this account for more than 4% of cells (8% and 9%, respectively).In sum, to be at least 70% clear, 44%-55% of in-season cells require a revisit rate more frequent than every 4 days, while 7%-23% of in-season cells require a revisit rate more frequent than every 2 days.
Not surprisingly, the higher the threshold of acceptable clarity (and the lower the threshold of acceptable cloud occlusion), the more frequent the required revisit becomes.In the FPC ≥ 80% scenario, the mean RFR decreases to 3.0-4.1 days (Figure 2b).There is also a marked decrease in the frequency with which a single revisit (RFR = 8) is all that is required (1%-23% of actively cropped cells), with 56%-79% requiring a revisit rate more frequent than every 4 days, and 15%-32% requiring a revisit rate more frequent than every 2 days.Meanwhile, in the FPC ≥ 90% scenario, the mean RFR decreases further to 2.2-3.3 days (Figure 2c), RFR = 8 days in 0-11% of actively cropped cells (with only December-February, the least pervasively cropped months, surpassing 6%), and 68%-95% require a revisit rate more frequent than every 4 days, while 38%-51% of in-season cells require a revisit rate more frequent than every 2 days.Finally, obtaining a view at least 95% clear after 8 days would require, on average, a revisit frequency of 1.7-2.6 days, with 76% to nearly 99% of actively cropped cells requiring a revisit rate more frequent than every 4 days (Figure 2d).On a global basis, securing a view at least 80% clear requires a revisit rate on average 0.88 days more frequent than does a 70% clear view.Increasing the clarity from 80% to 90% requires a revisit rate on average 0.91 days more frequent, while increasing clarity from 90% to 95% translates to an RFR 0.57 days more frequent.However, there is considerable variability at the continental-to-local level, as well as throughout the year.This month-to-month and geographic variability is illustrated in Figure 3a-f, wherein the mean monthly RFRs are shown for each of the FPCs for each of the continents, plotted over the percentage of total cropland actively in season for that continent.Still, as is clear in the map figures (Figure 1) and is illustrated in Figure 3a-f by the standard deviation overplot, there is a great deal of fine scale variability in cloud cover.The largest within-region variability in RFR occurs in November-January in North America, June-August in Europe, December-February in Asia, June-July in South America, May-July and October-December in Africa, and March-April and September in Australia.Additionally, Africa and Asia, very large land masses that span broad latitudinal gradients, have the highest within-regional variability across all months (1.5-2.6 days and 1.6-2.9days, respectively, depending on the month).This pattern in standard within-region variability is observed in the other FPC scenarios as well (not plotted).

Discussion & Future Research
The RFR varies throughout the year and geographically, as well as with the threshold of acceptable cloud cover.If data that are at least 70% clear are required within a given period (8 days), then 44%-55% of global cells require a revisit frequency less than half the length of that given period (i.e., <4 days for a reasonably clear view within 8 days), although during November-February, 22%-31% of cells could be satisfied by only a single revisit within the given period (i.e., every 8 days).Meanwhile, many areas require revisits more frequently than every 2 days in order to probabilistically meet a requirement for reasonably clear views every 8 days, even with an FPC as low as 70%.In areas with persistent and pervasive cloud occultation, the costs may outweigh the benefits for monitoring with optical data.SAR data algorithms are currently being prototyped and analyzed for operational monitoring applications [57,64,[95][96][97].
For over 40 years, moderate spatial resolution polar-orbiting optical remote sensing instruments have passed over areas of the Earth at least every 16-18 days, with much of the Landsat program's history having 8-9 day overpass frequency, although data have not been systematically acquired at this rate for most areas outside of the United States [54,83,98].In this context, it may seem surprising that the revisit frequency that is required to actually meet an 8-day requirement for reasonably clear data is in some areas less than 4 or even 2 days.However, in the context of global agricultural monitoring activities such as crop condition monitoring and yield forecasting, which have traditionally relied upon daily data, this revelation is not unexpected.In order to yield moderate resolution results at the regional to global scale, it is necessary to rethink the way in which we have historically approached moderate resolution systems' design and/or to consider a multi-mission constellation approach to monitoring [60,77].
There remain several questions that require addressing in the development of satellite-based EO requirements for agricultural monitoring.First, the requirement evaluated (#5) is preferred for the full cropland extent, but data acquired on a sampled basis will still yield important results [73,[99][100][101].The location and extent of the statistical sampling frame will vary over time and with target crop, and thus the requirements over the full extent of actively growing large, medium, and small fields have been analyzed, and can later be refined geographically to represent sample sites.It could be beneficial to design sampling strategy with these cloud constraints in mind.Secondly, an investigation into our current, near-term, and mid-term EO systems revisit capabilities would provide valuable insight into our missions' capacity to meet such requirements.Many of the required revisit frequencies articulated herein are well beyond the capabilities of any single existing moderate resolution program or mission.This demonstrates that with current proven capabilities, a multi-mission, multi-space agency constellation approach is necessary for operational monitoring in the moderate resolution domain.Precisely how these constellations might operate requires further analysis, which can be found in this issue in Whitcraft et al. [70].
In the present analysis, the resultant RFR from Equation ( 1) is often a non-integer.A non-integer revisit is an impossibility with polar-orbiting, sun-synchronous imaging systems, and when translating into data requests it will have to be altered to align with real-world orbital capabilities.However, data coordination at this level is beyond the scope of this present discussion, but merits further research before implementation.
As the threshold of acceptable cloud cover decreases (i.e., the desired clarity increases), the revisits must be 0.5-1.2days more frequent, depending on month, than each antecedent FPC threshold.The threshold of acceptable cloud cover will vary with the monitoring application and spatial resolution of imaging instruments, among other factors.For this reason, research should be conducted to analyze how these variable cloud cover amounts impact the production of each target product, investigating the utility and limitations of data with different cloud cover thresholds.
Finally, for the synthetic aperture radar (SAR) requirements detailed in Table 1, Requirements #6 and #9, the "where" requirement identifies "persistently cloudy" areas.It is necessary to delineate precisely which regions are "persistently cloudy" and therefore require microwave SAR acquisitions, a topic that will also be addressed in the accompanying paper [70].

Conclusions
Neither the problem of food insecurity nor the impact of increased agricultural market volatility is likely to disappear without policy interventions formed from sound scientific evidence.As such, it is crucial to acquire EO data of sufficient quantity, quality, and accessibility to generate informational products about local, regional, and global food production.In this vein, categorical Earth observation data requirements for global agricultural monitoring have been established by the GEO Agricultural Monitoring Community of Practice and the CEOS Ad Hoc Team for GEOGLAM, and are introduced here in Table 1.Further, these descriptive requirements have been made spatially explicit through the inclusion of the growing season calendars from Whitcraft et al. (2014 [2]; when to image), a "best available" cropland mask along with a field size distribution layer (Fritz et al. (2015) [1]; where [fine vs. moderate vs. coarse] data are required), and the cloud cover information detailed in Whitcraft et al. (2015 [3]; how frequently to image given a particular reasonably clear view requirement).We have introduced a method for combining these datasets to reveal the revisit frequency that would be required in order to probabilistically yield a reasonably clear view (defined as at least 70%, 80%, 90%, or 95% clear) within 8 days during each month for actively cropped areas at 0.05°.This is a novel framework for synthesizing multiple layers of information to create spatially explicit, quantitative estimates to which CEOS and space agency data acquisition teams can respond.As such, the spatially explicit requirements articulated herein provide critical inputs into a data acquisition strategy for global agricultural monitoring in the context of GEOGLAM, and highlight the need for a collaborative, multi-mission response to a pressing global issue.

Figure 1 .
Figure 1.The revisit frequency required (RFR) to probabilistically yield a view at least 70% (left) or 95% (right) clear within 8 days over in-season croplands, for the representative months of January, April, July, and October.Areas containing cropland out of season are shown in gray.Resolution is 0.05°.Full map figures for all months can be found in the Supplemental Materials.

Figure 3 .
Figure 3.For each continent (a-f), the mean revisit frequency required (RFR) to yield, every 8 days, an FPC of at least 70%, 80%, 90%, or 95% clear (left axis), on a monthly basis.The error bars (mean ± 1 standard deviation) plotted for the FPC ≥ 80% case illustrate sub-continental variability.Also plotted is the percentage of croplands in that continent that are in season at any point during that month (right axis), as indicated by Fritz et al. (2015) [1] and Whitcraft et al. (2014) [2].