Asia agriculture data

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on July 14, 2013. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * xx201304_ML1 Most likely food security outcome for July-September 2013 * xx201304_ML2 Most likely food security outcome for October-December 2013 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on February 11, 2015. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * centralasia201304_ML1 Most likely food security outcome for January-March 2015 * centralasia201304_ML2 Most likely food security outcome for April-June 2015 Where xx is one of the region codes listed above. Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on November 13, 2014. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * CA201304_ML1 Most likely food security outcome for October-December 2014 * CA201304_ML2 Most likely food security outcome for January-March 2015 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on June 14, 2013. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * xx201304_ML1 Most likely food security outcome for April-June 2013 * xx201304_ML2 Most likely food security outcome for July-September 2013 Where xx is one of the region codes listed above. Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on August 01, 2014. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * CA201304_ML1 Most likely food security outcome for July-September 2014 * CA201304_ML2 Most likely food security outcome for October-December 2014 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on January 19, 2014. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * xx201401_ML1 Most likely food security outcome for January-March 2014 * xx201401_ML2 Most likely food security outcome for April-June 2014 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on April 30, 2015. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * centralasia201304_ML1 Most likely food security outcome for April-June 2015 * centralasia201304_ML2 Most likely food security outcome for July-September 2015 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on June 14, 2013. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * xx201304_ML1 Most likely food security outcome for April-June 2013 * xx201304_ML2 Most likely food security outcome for July-September 2013 Where xx is one of the region codes listed above. Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on July 31, 2015. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * centralasia201304_ML1 Most likely food security outcome for July-September 2015 * centralasia201304_ML2 Most likely food security outcome for October-December 2015 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **East Africa**. It was last updated on January 14, 2013. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * xx201304_ML1 Most likely food security outcome for January-March 2013 * xx201304_ML2 Most likely food security outcome for April-June 2013 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

This Archive contains shapefiles for FEWS NET Food Security Outlook for **Central Asia**. It was last updated on April 2014. The classification used is IPC V2.0 Compatible, aimed to address acute food insecurity. The two shapefiles represent the two analytic periods: * xx201404_ML1 Most likely food security outcome for April-June 2014 * xx201404_ML2 Most likely food security outcome for July-September 2014 Within the shapefiles, the food security outlook is contained in a field named as ML1 or ML2 according to the outlook period. The code itself is the IPC phase. Two additional codes are used: * 66 = water * 88 = parks, forests, reserves * 99 = missing data (usually urban centers)

The NASA Making Earth System Data Records for Use in Research Environments (MEaSUREs) Global Food Security-support Analysis Data (GFSAD) data product provides cropland extent data over Australia, New Zealand, China, and Mongolia for nominal year 2015 at 30 meter resolution (GFSAD30AUNZCNMOCE). The monitoring of global cropland extent is critical for policymaking and provides important baseline data that are used in many agricultural cropland studies pertaining to water sustainability and food security. The GFSAD30AUNZCNMOCE data product uses the pixel-based supervised classifier, Random Forest (RF), to retrieve cropland extent from a combination of Landsat 8 Operational Land Imager (OLI) and Landsat 7 Enhanced Thematic Mapper Plus (ETM+) data. Each GFSAD30AUNZCNMOCE GeoTIFF file contains a cropland extent layer that defines areas of cropland, non-cropland, and water bodies over a 10° by 10° area. Known Issues * Note overlapping tiles: The following tile also covers part of another tile in GFSAD30SEACE (Indonesia). Please ignore the Indonesian data in the following tile: GFSAD30AUNZCNMOCE_2015_S20E120_001_2017286154500.tif * Additional known issues, including constraints and limitations, are provided on page 22 of the ATBD.

The NASA Making Earth System Data Records for Use in Research Environments (MEaSUREs) Global Food Security-support Analysis Data (GFSAD) data product provides cropland extent data over Southeast and Northeast Asia for nominal year 2015 at 30 meter resolution (GFSAD30SEACE). The monitoring of global cropland extent is critical for policymaking and provides important baseline data that are used in many agricultural cropland studies pertaining to water sustainability and food security. The GFSAD30SEACE data product uses the pixel-based supervised classifiers, Random Forest (RF), to retrieve cropland extent from a combination of Landsat 8 Operational Land Imager (OLI), Landsat 7 Enhanced Thematic Mapper Plus (ETM+), and elevation derived from the Shuttle Radar Topography Mission (SRTM) Version 3 data products. Each GFSAD30SEACE GeoTIFF file contains a cropland extent layer that defines areas of cropland, non-cropland, and water bodies over a 10° by 10° area. Known Issues * Certain small islands in the Pacific are not classified and therefore data for these areas are not provided. * Additional known issues, including constraints and limitations, are provided on page 19 of the ATBD.