Iraq climate and weather data
+ Follow new data22 datasets about climate and weather in Iraq.
The International Best Track Archive for Climate Stewardship (IBTrACS) project is the most complete global collection of tropical cyclones available. It merges recent and historical tropical cyclone data from multiple agencies to create a unified, publicly available, best-track dataset that improves inter-agency comparisons. Fields available: SID: A unique storm identifier (SID) assigned by IBTrACS algorithm. ISO_TIME: Time of the observation in ISO format (YYYY-MM-DD hh:mm:ss) BASIN: Basin of the current storm position SUBBASIN: Sub-basin of the current storm position NATURE: Type of storm (a combination of the various types from the available sources) NUMBER: Number of the storm for the year (restarts at 1 for each year LAT: Mean position - latitude (a combination of the available positions) LON: Mean position - longitude (a combination of the available positions) WMO_WIND: Maximum sustained wind speed assigned by the responsible WMO agency WMO_PRES: Minimum central pressure assigned by the responsible WMO agency.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
This map illustrates satellite-detected fires and smoke plumes at oil wells south of Mosul, and also east of Baiji, Iraq. The Mosul fires began with an initial fire at one or two wells on 8 May 2016, lasting less than one day, and intermittently burned in June. The current fire complex began on 3 July with daily fire detections occurring until about 12 July, when the fires greatly increased in number and continued to burn until gradual reductions in detected fires occurred starting in November 2016. The fires east of Baiji have been active since early January 2016. The frequency of smoke plumes (in days) is symbolized in shades of red and yellow, and was calculated using daily MODIS satellite images collected between 18 July 2016 and 13 March 2017. Note that as the plume dissipates then areas of thinner smoke are not detected in this process. The inset on the top right corner shows the infrared data from a Landsat image collected on 25 February 2017, indicating the Mosul fires in white. The inset on the top left corner, from 5 March 2017, shows the same area in real color. Additionally, precipitation data from NASA's IMERG algorithm was included to evaluate instances of rainfall intersecting the smoke plume. This is a preliminary analysis and has not yet been validated in the field. Please send ground feedback to UNITAR - UNOSAT.
The actual EvapoTranspiration and Interception (ETIa) is the sum of the soil evaporation (E), canopy transpiration (T), and evaporation from rainfall intercepted by leaves (I). The value of each pixel represents the ETIa in a given month. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: -9999 Unit: mm Scale Factor : 0.1 Map code : L3-AETI-M Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. This implies that other temporal aggregations (monthly, seasonal, annual), and layers that depend on those, are updated as well. Practically this means that a final annual aggregation of the most recent full calendar year can only be produced after the end of February. Likewise, the final monthly aggregation of the most recent calendar months can only be produced 2 full months later. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. License: CC-BY-4.0 **Contact points:** Metadata Contact: [WaPOR](mailto:wapor@fao.org) Resource Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** See ETIa by dekad for further information. The annual total is obtained by taking the ETIa in mm/day, multiplying by the number of days in a dekad, and summing the dekads of each year. **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
The actual EvapoTranspiration and Interception (ETIa) is the sum of the soil evaporation (E), canopy transpiration (T), and evaporation from rainfall intercepted by leaves (I). The value of each pixel represents the average daily ETIa in a given dekad. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: -9999 Unit: mm Scale Factor : 0.1 Map code : L3-AETI-D Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. This implies that other temporal aggregations (monthly, seasonal, annual), and layers that depend on those, are updated as well. Practically this means that a final annual aggregation of the most recent full calendar year can only be produced after the end of February. Likewise, the final monthly aggregation of the most recent calendar months can only be produced 2 full months later. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. License: CC-BY-4.0 **Contact points:** Metadata Contact: [WaPOR](mailto:wapor@fao.org) Resource Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** The calculation of the ETIa is based on the ETLook model described in Bastiaanssen et al. (2012). See the methodology of the three components (E, T and I) for further information. **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
The Evaporation (E) data component is the actual evaporation of the soil surface. The value of each pixel represents the total annual evaporation for that specific year. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: -9999 Unit: mm Scale Factor : 0.1 Map code : L3-E-A Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. This implies that other temporal aggregations (monthly, seasonal, annual), and layers that depend on those, are updated as well. Practically this means that a final annual aggregation of the most recent full calendar year can only be produced after the end of February. Likewise, the final monthly aggregation of the most recent calendar months can only be produced 2 full months later. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. License: CC-BY-4.0 **Contact points:** Resource Contact: [WaPOR](mailto:wapor@fao.org) Metadata Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** See evaporation (E) by dekad for further information. The annual total is obtained by taking the E in mm/day, multiplying by the number of days in a dekad, and summing the dekads of each year. **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
The Evaporation (E) data component (dekadal, in mm/day) is the actual evaporation of the soil surface. The value of each pixel represents the average daily actual evaporation for that specific dekad. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: 255 Unit: mm Scale Factor : 0.1 Map code : L3-E-D Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. Licence: CC-BY-4.0 **Contact points:** Metadata Contact: [WaPOR](mailto:wapor@fao.org) Resource Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** The calculation of the evaporation is based on the ETLook model described in Bastiaanssen et al. (2012). It uses the Penman-Monteith equation, adapted to remote sensing input data. The Penman-Monteith equation predicts the rate of total evaporation and transpiration using commonly measured meteorological data (solar radiation, air temperature, vapour content and wind speed). It has become the FAO standard for calculating the actual and reference evapotranspiration (see FAO Irrigation and Drainage paper 56, Allen et al. 1998). The following data is used for calculating evaporation: • Daily: incoming solar radiation and weather data (temperature, humidity, wind speed and precipitation); • Dekadal: NDVI, surface albedo and soil moisture stress; • Seasonal: Land Cover; • Static: Digital Elevation Model. Data component developed through collaboration with the FRAME Consortium. More information can be found at: http://www.fao.org/in-action/remote-sensing-for-water-productivity/en/ **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
The Transpiration (T) data component is the actual transpiration of the vegetation canopy. The value of each pixel represents the total annual transpiration for that specific year. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: -9999 Unit: mm Scale Factor : 0.1 Map code : L3-T-A Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. This implies that other temporal aggregations (monthly, seasonal, annual), and layers that depend on those, are updated as well. Practically this means that a final annual aggregation of the most recent full calendar year can only be produced after the end of February. Likewise, the final monthly aggregation of the most recent calendar months can only be produced 2 full months later. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. License: CC-BY-4.0 **Contact points:** Metadata Contact: [WaPOR](mailto:wapor@fao.org) Metadata Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** See transpiration (T) by dekad for further information. The annual total is obtained by taking the T in mm/day, multiplying by the number of days in a dekad, and summing the dekads of each year. **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
The transpiration (T) data component (dekadal, in mm/day) is the actual transpiration of the vegetation canopy. The value of each pixel represents the average daily actual transpiration for that specific dekad. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: 255 Unit: mm Scale Factor : 0.1 Map code : L3-T-D Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. Licence: CC-BY-4.0 **Contact points:** Metadata Contact: [WaPOR](mailto:wapor@fao.org) Resource Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** The calculation of the transpiration is based on the ETLook model described in Bastiaanssen et al. (2012). It uses the Penman-Monteith equation, adapted to remote sensing input data. The Penman-Monteith equation predicts the rate of total evaporation and transpiration using commonly measured meteorological data (solar radiation, air temperature, vapour content and wind speed). It has become the FAO standard for calculating the actual and reference evapotranspiration (see FAO Irrigation and Drainage paper 56, Allen et al. 1998). The following data is used for calculating transpiration: • Daily: incoming solar radiation and weather data (temperature, humidity, wind speed and precipitation); • Dekadal: NDVI, surface albedo and soil moisture stress; • Seasonal: Land Cover; • Static: Digital Elevation Model. Data component developed through collaboration with the FRAME Consortium. More information can be found at: http://www.fao.org/in-action/remote-sensing-for-water-productivity/en/ **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
Interception is the process where rainfall is captured by the leaves. Part of this captured rainfall will evaporate again. The Interception (I) data component represents the evaporation of intercepted rainfall from the vegetation canopy. The value of each pixel represents the total annual interception for that specific year. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: -9999 Unit: mm Scale Factor : 0.1 Map code : L3-I-A Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. This implies that other temporal aggregations (monthly, seasonal, annual), and layers that depend on those, are updated as well. Practically this means that a final annual aggregation of the most recent full calendar year can only be produced after the end of February. Likewise, the final monthly aggregation of the most recent calendar months can only be produced 2 full months later. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. License: CC-BY-4.0 **Contact points:** Resource Contact: [WaPOR](mailto:wapor@fao.org) Metadata Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** See interception (I) by dekad for further information. The annual total is obtained by taking the I in mm/day, multiplying by the number of days in a dekad, and summing the dekads of each year. **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
The Interception (I) data component (dekadal, in mm/day) represents the evaporation of intercepted rainfall from the vegetation canopy. Interception is the process where rainfall is captured by the leaves. Part of this captured rainfall will evaporate again. The value of each pixel represents the average daily evaporated interception for that specific dekad. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: 255 Unit: mm Scale Factor : 0.1 Map code : L3-I-D Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. Licence: CC-BY-4.0 **Contact points:** Metadata Contact: [WaPOR](mailto:wapor@fao.org) Resource Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** Evaporation of intercepted rainfall requires energy that is not available for transpiration or evaporation. Interception is a function of the vegetation cover and precipitation. Interception is relatively high with a small amount of precipitation, with the fraction intercepted decreasing quickly as precipitation increases. The maximum interception is determined by the LAI. The following data is used for calculating interception: • Daily: incoming solar radiation and weather data (temperature, humidity and precipitation); • Dekadal: NDVI. Data component developed through collaboration with the FRAME Consortium. More information can be found at: http://www.fao.org/in-action/remote-sensing-for-water-productivity/en/ **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage
The actual EvapoTranspiration and Interception (ETIa) is the sum of the soil evaporation (E), canopy transpiration (T), and evaporation from rainfall intercepted by leaves (I). The value of each pixel represents the ETIa in a given year. **Data publication:** 2023-01-01 **Supplemental Information:** No data value: -9999 Unit: mm Scale Factor : 0.1 Map code : L3-AETI-A Conversion factor: the pixel value in the downloaded data must be multiplied by 0.1 New dekadal data layers are released approximately 5 days after the end of a dekad. A higher quality version of the same data layer is uploaded after 6 dekads have passed. This final version of the dekadal dataset has a higher quality because gap filling and interpolation processes, where needed, have been based on more data observations. This implies that other temporal aggregations (monthly, seasonal, annual), and layers that depend on those, are updated as well. Practically this means that a final annual aggregation of the most recent full calendar year can only be produced after the end of February. Likewise, the final monthly aggregation of the most recent calendar months can only be produced 2 full months later. **Citation:** FAO 2018. WaPOR Database Methodology: Level 3. Remote Sensing for Water Productivity Technical Report: Methodology Series. Rome, FAO. 72 pages. License: CC-BY-4.0 **Contact points:** Resource Contact: [WaPOR](mailto:wapor@fao.org) Metadata Contact: [WaPOR](mailto:wapor@fao.org) **Data lineage:** See ETIa by dekad for further information. The annual total is obtained by taking the ETIa in mm/day, multiplying by the number of days in a dekad, and summing the dekads of each year. **Resource constraints:** Creative Commons Attribution 4.0 International (CC-BY-4.0) **Online resources:** Download the data from Google Cloud Storage