The Sentinel-1 mission provides data from a dual-polarization C-band Synthetic Aperture Radar (SAR) instrument at 5.405GHz (C band). This collection includes the S1 Ground Range Detected (GRD) scenes, processed using the Sentinel-1 Toolbox to generate a calibrated, ortho-corrected product. The collection is updated daily. New assets are ingested within two days after they become available. This collection contains all of the GRD scenes. Each scene has one of 3 resolutions (10, 25 or 40 meters), 4 band combinations (corresponding to scene polarization) and 3 instrument modes. Use of the collection in a mosaic context will likely require filtering down to a homogeneous set of bands and parameters. See this article for details of collection use and preprocessing. Each scene contains either 1 or 2 out of 4 possible polarization bands, depending on the instrument's polarization settings. The possible combinations are single band VV, single band HH, dual band VV+VH, and dual band HH+HV: VV: single co-polarization, vertical transmit/vertical receive HH: single co-polarization, horizontal transmit/horizontal receive VV + VH: dual-band cross-polarization, vertical transmit/horizontal receive HH + HV: dual-band cross-polarization, horizontal transmit/vertical receive Each scene also includes an additional 'angle' band that contains the approximate incidence angle from ellipsoid in degrees at every point. This band is generated by interpolating the 'incidenceAngle' property of the 'geolocationGridPoint' gridded field provided with each asset. Each scene was pre-processed with Sentinel-1 Toolbox using the following steps: Thermal noise removal Radiometric calibration Terrain correction using SRTM 30 or ASTER DEM for areas greater than 60 degrees latitude, where SRTM is not available. The final terrain-corrected values are converted to decibels via log scaling (10*log10(x)). For more information about these pre-processing steps, please refer to the Sentinel-1 Pre-processing article. For further advice on working with Sentinel-1 imagery, see Guido Lemoine's tutorial on SAR basics and Mort Canty's tutorial on SAR change detection. This collection is computed on-the-fly. If you want to use the underlying collection with raw power values (which is updated faster), see COPERNICUS/S1_GRD_FLOAT.

Link to the Google Earth Engine (GEE) code: https://code.earthengine.google.com/cc3ea6593574e321acd7b68c975a9608

You can analyze and visualize the following spatial layers by accessing the GEE link:

Daytime summer land surface temperature (raster data, 30 m horizontal resolution, from Landsat-8 remote sensing data, years 2017-2022)

The surface thermal hot-spot pattern (raster data,30 m horizontal resolution) was obtained by using a statistical-spatial method based on the Getis-Ord Gi* approach through the ArcGIS tool.

Here attached the .txt file from the GEE code.

E-mail

Giulia Guerri, CNR-IBE, giulia.guerri@ibe.cnr.it

Marco Morabito, CNR-IBE, marco.morabito@cnr.it

Alfonso Crisci, CNR-IBE, alfonso.crisci@ibe.cnr.it

Google Earth Engine used to compute the NDVI statistics added to Globe-LFMC. The input of the program is a point shapefile (“samplePlotsShapefile”, extensions .cpg, .dbf, .prj, .shp, .shx) representing the location of each Globe-LFMC site. This shapefile is available as additional data in figshare (see Code Availability). To run this GEE code the shapefile needs to be uploaded into the GEE Assets and, then, imported into the Code Editor with the name “plots” (without quotation marks).Google Earth Engine codeChange Notice - GEE_script_for_GlobeLFMC_ndvi_stats_v2.jsThe following acknowledgements have been added at the beginning of the code: “Portions of the following code are modifications based on work created and shared by Google in Earth Engine Data Catalog and Earth Engine Guides under the Apache 2.0 License. https://www.apache.org/licenses/LICENSE-2.0”Change Notice - samplePlotsShapefile_v2The shapefile describing the database sites has been corrected and updated with the correct coordinates.

After 2022-01-25, Sentinel-2 scenes with PROCESSING_BASELINE '04.00' or above have their DN (value) range shifted by 1000. The HARMONIZED collection shifts data in newer scenes to be in the same range as in older scenes. Sentinel-2 is a wide-swath, high-resolution, multi-spectral imaging mission supporting Copernicus Land Monitoring studies, including the …

A Google Earth Engine implementation of the Floodwater Depth Estimation Tool (FwDET) This is a Google Earth Engine implementation of the Floodwater Depth Estimation Tool (FwDET) developed by the Surface Dynamics and Modeling Lab at the University of Alabama that calculates flood depth using a flood extent layer and a digital elevation model. This research is made possible by the CyberSeed Program at the University of Alabama. Project name: WaterServ: A Cyberinfrastructure for Analysis, Visualization and Sharing of Hydrological Data. Please see the associated publications: 1. Peter, B.G., Cohen, S., Lucey, R., Munasinghe, D., Raney, A. and Brakenridge, G.R., 2020. Google Earth Engine Implementation of the Floodwater Depth Estimation Tool (FwDET-GEE) for rapid and large scale flood analysis. IEEE Geoscience and Remote Sensing Letters, 19, pp.1-5. https://ieeexplore.ieee.org/abstract/document/9242297 2. Cohen, S., Peter, B.G., Haag, A., Munasinghe, D., Moragoda, N., Narayanan, A. and May, S., 2022. Sensitivity of remote sensing floodwater depth calculation to boundary filtering and digital elevation model selections. Remote Sensing, 14(21), p.5313. https://github.com/csdms-contrib/fwdet 3. Cohen, S., A. Raney, D. Munasinghe, J.D. Loftis J, A. Molthan, J. Bell, L. Rogers, J. Galantowicz, G.R. Brakenridge7, A.J. Kettner, Y. Huang, Y. Tsang, (2019). The Floodwater Depth Estimation Tool (FwDET v2.0) for Improved Remote Sensing Analysis of Coastal Flooding. Natural Hazards and Earth System Sciences, 19, 2053–2065. https://doi.org/10.5194/nhess-19-2053-2019 4. Cohen, S., G. R. Brakenridge, A. Kettner, B. Bates, J. Nelson, R. McDonald, Y. Huang, D. Munasinghe, and J. Zhang (2018), Estimating Floodwater Depths from Flood Inundation Maps and Topography, Journal of the American Water Resources Association, 54 (4), 847–858. https://doi.org/10.1111/1752-1688.12609 Sample products and data availability: https://sdml.ua.edu/models/fwdet/ https://sdml.ua.edu/michigan-flood-may-2020/ https://cartoscience.users.earthengine.app/view/fwdet-gee-mi https://alabama.app.box.com/s/31p8pdh6ngwqnbcgzlhyk2gkbsd2elq0 GEE implementation output: fwdet_gee_brazos.tif ArcMap implementation output (see Cohen et al. 2019): fwdet_v2_brazos.tif iRIC validation layer (see Nelson et al. 2010): iric_brazos_hydraulic_model_validation.tif Brazos River inundation polygon access in GEE: var brazos = ee.FeatureCollection('users/cartoscience/FwDET-GEE-Public/Brazos_River_Inundation_2016') Nelson, J.M., Shimizu, Y., Takebayashi, H. and McDonald, R.R., 2010. The international river interface cooperative: public domain software for river modeling. In 2nd Joint Federal Interagency Conference, Las Vegas, June (Vol. 27). Google Earth Engine Code /* ---------------------------------------------------------------------------------------------------------------------- # FwDET-GEE calculates floodwater depth from a floodwater extent layer and a DEM Authors: Brad G. Peter, Sagy Cohen, Ronan Lucey, Dinuke Munasinghe, Austin Raney Emails: bpeter@ua.edu, sagy.cohen@ua.edu, ronan.m.lucey@nasa.gov, dsmunasinghe@crimson.ua.edu, aaraney@crimson.ua.edu Organizations: BP, SC, DM, AR - University of Alabama; RL - University of Alabama in Huntsville Last Modified: 10/08/2020 To cite this code use: Peter, Brad; Cohen, Sagy; Lucey, Ronan; Munasinghe, Dinuke; Raney, Austin, 2020, "A Google Earth Engine implementation of the Floodwater Depth Estimation Tool (FwDET-GEE)", https://doi.org/10.7910/DVN/JQ4BCN, Harvard Dataverse, V2 ------------------------------------------------------------------------------------------------------------------------- This is a Google Earth Engine implementation of the Floodwater Depth Estimation Tool (FwDETv2.0) [1] developed by the Surface Dynamics and Modeling Lab at the University of Alabama that calculates flood depth using a flood extent layer and a digital elevation model. This research is made possible by the CyberSeed Program at the University of Alabama. Project name: WaterServ: A Cyberinfrastructure for Analysis, Visualization and Sharing of Hydrological Data. GitHub Repository (ArcMap and QGIS implementations): https://github.com/csdms-contrib/fwdet ------------------------------------------------------------------------------------------------------------------------- How to run this code with your flood extent GEE asset: User of this script will need to update path to flood extent (line 32 or 33) and select from the processing options. Available DEM options (1) are USGS/NED (U.S.) and USGS/SRTMGL1_003 (global). Other options include (2) running the elevation outlier filtering algorithm, (3) adding water body data to the inundation extent, (4) add a water body data layer uploaded by the user rather than using the JRC global surface water data, (5) masking out regular water body data, (6) masking out 0 m depths, (7) choosing whether or not to export, (8) exporting additional data layers, and (9) setting an export file name....

CANUE staff developed annual estimates of maximum mean warm-season land surface temperature (LST) recorded by LandSat 8 at 30m resolution. To reduce the effect of missing data/cloud cover/shadows, the highest mean warm-season value reported over three years was retained - for example, the data for 2021 represent the maximum of the mean land surface temperature at a pixel location between April 1st and September 30th in 2019, 2020 and 2021. Land surface temperature was calculated in Google Earth Engine, using a public algorithm (see supplementary documentation). In general, annual mean LST may not reflect ambient air temperatures experienced by individuals at any given time, but does identify areas that are hotter during the day and therefore more likely to radiate excess heat at night - both factors that contribute to heat islands within urban areas.

The layers included in the code were from the study conducted by the research group of CNR-IBE (Institute of BioEconomy of the National Research Council of Italy) and ISPRA (Italian National Institute for Environmental Protection and Research), published by the Sustainability journal (https://doi.org/10.3390/su14148412).

Link to the Google Earth Engine (GEE) code (link: https://code.earthengine.google.com/715aa44e13b3640b5f6370165edd3002)

You can analyze and visualize the following spatial layers by accessing the GEE link:

Daytime summer land surface temperature (raster data, horizontal resolution 30 m, from Landsat-8 remote sensing data, years 2015-2019)

Surface thermal hot-spot (raster data, horizontal resolution 30 m) was obtained by using a statistical-spatial method based on the Getis-Ord Gi* approach through the ArcGIS Pro tool.

Surface albedo (raster data, horizontal resolution 10 m, Sentinel-2A remote sensing data, year 2017)

Impervious area (raster data, horizontal resolution 10 m, ISPRA data, year 2017)

Tree cover (raster data, horizontal resolution 10 m, ISPRA data, year 2018)

Grassland area (raster data, horizontal resolution 10 m, ISPRA data, year 2017)

Water bodies (raster data, horizontal resolution 2 m, Geoscopio Platform of Tuscany, year 2016)

Sky View Factor (raster data, horizontal resolution 1 m, lidar data from the OpenData platform of Florence, year 2016)

Buildings' units of Florence (shapefile from the OpenData platform of Florence) include data on the residential real estate value from the Real Estate Market Observatory (OMI) of the National Revenue Agency of Italy (source: https://www1.agenziaentrate.gov.it/servizi/Consultazione/ricerca.htm, accessed on 14 July 2022). Data on the characterization of the buffer area (50 m) surrounding the buildings are included in this shapefile [the names of table attributes are reported in the square brackets]: averaged values of the daytime summer land surface temperature [LST_media], thermal hot-spot pattern [Thermal_cl], mean values of sky view factor [SVF_medio], surface albedo [alb_medio], and average percentage areas of imperviousness [ImperArea%], tree cover [TreeArea%], grassland [GrassArea%] and water bodies [WaterArea%].

Here attached the .txt file of the GEE code.

E-mail

Giulia Guerri, CNR-IBE, giulia.guerri@ibe.cnr.it

Marco Morabito, CNR-IBE, marco.morabito@cnr.it

Alfonso Crisci, CNR-IBE, alfonso.crisci@ibe.cnr.it

PLEASE NOTE:

_ GEEBAM is an interim product and there is no ground truthing or assessment of accuracy. Fire Extent and Severity Mapping (FESM) data should be used for accurate information on fire severity and loss of biomass in relation to bushfires._

The intention of this dataset was to provide a rapid assessment of fire impact.

In collaboration with the University of NSW, the NSW Department of Planning Infrastructure and Environment (DPIE) Remote Sensing and Landscape Science team has developed a rapid mapping approach to find out where wildfires in NSW have affected vegetation. We call it the Google Earth Engine Burnt Area Map (GEEBAM) and it relies on Sentinel 2 satellite imagery. The product output is a TIFF image with a resolution of 15m. Burnt Area Classes:

1. Little change observed between pre and post fire

2. Canopy unburnt - A green canopy within the fire ground that may act as refugia for native fauna, may be affected by fire

3. Canopy partially affected - A mix of burnt and unburnt canopy vegetation

4. Canopy fully affected -The canopy and understorey are most likely burnt

Using GEEBAM at a local scale requires visual interpretation with reference to satellite imagery. This will ensure the best results for each fire or vegetation class.

Important Note: GEEBAM is an interim product and there is no ground truthing or assessment of accuracy. It is updated fortnightly.

Please see Google Earth Engine Burnt Area Factsheet

Top of Atmosphere (TOA) reflectance data in bands from the USGS Landsat 5 and Landsat 8 satellites were accessed via Google Earth Engine. CANUE staff used Google Earth Engine functions to create cloud free annual composites, and mask water features, then export the resulting band data. NDVI indices were calculated as (band 4 - Band 3)/(Band 4 Band 3) for Landsat 5 data, and as (band 5 - band 4)/(band 5 Band 4) for Landsat 8 data. These composites are created from all the scenes in each annual period beginning from the first day of the year and continuing to the last day of the year. No data were available for 2012, due to decommissioning of Landsat 5 in 2011 prior to the start of Landsat 8 in 2013. No cross-calibration between the sensors was performed, please be aware there may be small bias differences between NDVI values calculated using Landsat 5 and Landsat 8. Final NDVI metrics were linked to all 6-digit DMTI Spatial single link postal code locations in Canada, and for surrounding areas within 100m, 250m, 500m, and 1km.

This data is long-term lake dynamic (surface elevation, area, and volume) derived from topographic datasets and Landsat imagery in Google Earth Engine.

This example is about how to use Google Earth Engine API on Jupyter Notebooks. We show the example of how to get Landsat Net Primary Production (NPP) CONUS DataSet from Google Earth Engine Data Catalog.

Google Earth Engine combines a multi-petabyte catalog of satellite imagery and geospatial datasets with planetary-scale analysis capabilities. Scientists, researchers, and developers use Earth Engine to detect changes, map trends, and quantify differences on the Earth's surface. Earth Engine is now available for commercial use, and remains free for academic and research use.

Climate reanalysis and climate projection datasets offer the potential for researchers, students and instructors to access physically informed, global scale, temporally and spatially continuous climate data from the latter half of the 20th century to present, and explore different potential future climates. While these data are of significant use to research and teaching within biological, environmental and social sciences, potential users often face barriers to processing and accessing the data that cannot be overcome without specialist knowledge, facilities or assistance. Consequently, climate reanalysis and projection data are currently substantially under-utilised within research and education communities. To address this issue, we present two simple “point-and-click” graphical user interfaces: the Google Earth Engine Climate Tool (GEEClimT), providing access to climate reanalysis data products; and Google Earth Engine CMIP6 Explorer (GEECE), allowing processing and extraction of CMIP6 projection data, including the ability to create custom model ensembles. Together GEEClimT and GEECE provide easy access to over 387 terabytes of data that can be output in commonly used spreadsheet (CSV) or raster (GeoTIFF) formats to aid subsequent offline analysis. Data included in the two tools include: 20 atmospheric, terrestrial and oceanic reanalysis data products; a new dataset of annual resolution climate variables (comparable to WorldClim) calculated from ERA5-Land data for 1950-2022; and CMIP6 climate projection output for 34 model simulations for historical, SSP2-4.5 and SSP5-8.5 scenarios. New data products can also be easily added to the tools as they become available within the Google Earth Engine Data Catalog. Five case studies that use data from both tools are also provided. These show that GEEClimT and GEECE are easily expandable tools that remove multiple barriers to entry that will open use of climate reanalysis and projection data to a new and wider range of users.

بعد ‎2022-01-25، تمّ تغيير نطاق DN (القيمة) في مَشاهد Sentinel-2 التي تحتوي على القيمة ‎04.00 أو أعلى في PROCESSING_BASELINE بمقدار 1000. تعمل مجموعة HARMONIZED على نقل البيانات في المشاهد الأحدث لتصبح في النطاق نفسه المُستخدَم في المشاهد الأقدم. ‫Sentinel-2 هي مهمة تصوير متعددة الأطوال الموجية وذات نطاق واسع وعالية الدقة، وهي تدعم دراسات "كوبرنيكوس لرصد الأرض"، بما في ذلك رصد الغطاء النباتي والتربة والمياه، بالإضافة إلى رصد الممرات المائية الداخلية والمناطق الساحلية. تحتوي بيانات Sentinel-2 على 13 نطاقًا طيفيًا من النوع UINT16 تمثّل انعاكس سطح الأرض مقسومًا على 10,000. يُرجى الاطّلاع على دليل مستخدم Sentinel-2 للتعرّف على التفاصيل. ‫QA60 هو نطاق قناع بتات كان يحتوي على مضلّعات قناع السحب الممسوحة ضوئيًا حتى شباط (فبراير) 2022، عندما توقّف إنتاج هذه المضلّعات. اعتبارًا من شباط (فبراير) 2024، يتم إنشاء نطاقات QA60 المتوافقة مع الإصدارات القديمة من نطاقات تصنيف السحابة MSK_CLASSI. لمزيد من التفاصيل، اطّلِع على الشرح الكامل لكيفية احتساب أقنعة السحب. قد يحتوي كل منتج من منتجات Sentinel-2 (أرشيف بتنسيق ZIP) على عدة حبيبات. تصبح كل حبيبة مادة عرض منفصلة في Earth Engine. تتّبع أرقام تعريف مواد العرض ذات الدقة العالية لمادة عرض Sentinel-2 التنسيق التالي: COPERNICUS/S2/20151128T002653_20151128T102149_T56MNN. في هذه الحالة، يمثّل الجزء الرقمي الأول تاريخ الاستشعار ووقته، ويمثّل الجزء الرقمي الثاني تاريخ إنشاء المنتج ووقته، وتمثل السلسلة النهائية المكونة من 6 أحرف معرّفًا فريدًا للحبيبة ويشير إلى مرجع شبكة UTM (راجِع MGRS). يمكن العثور على بيانات المستوى 2 التي أنشأها "وكالة الفضاء الأوروبية" في المجموعة COPERNICUS/S2_SR. للحصول على مجموعات بيانات للمساعدة في رصد السحب و/أو ظلال السحب، يُرجى الاطّلاع على COPERNICUS/S2_CLOUD_PROBABILITY وGOOGLE/CLOUD_SCORE_PLUS/V1/S2_HARMONIZED. لمزيد من التفاصيل حول الدقة الشعاعية لآلة Sentinel-2، اطّلِع على هذه الصفحة.

Top of Atmosphere (TOA) reflectance data in bands from the USGS Landsat 5 and Landsat 8 satellites were accessed via Google Earth Engine. CANUE staff used Google Earth Engine functions to create cloud free mean growing season composites, and mask water features, then export the resulting band data. Growing season is defined as May 1st through August 31st. NDVI indices were then calculated as (band 4 - Band 3)/(Band 4 Band 3) for Landsat 5 data, and as (band 5 - band 4)/(band 5 Band 4) for Landsat 8 data. No data were available for 2012, due to decommissioning of Landsat 5 in 2011 prior to the start of Landsat 8 in 2013. No cross-calibration between the sensors was performed, please be aware there may be small bias differences between NDVI values calculated using Landsat 5 and Landsat 8. Final NDVI metrics were linked to all 6-digit DMTI Spatial single link postal code locations in Canada, and for surrounding areas within 100m, 250m, 500m, and 1km.

The API is powered by Google Earth Engine, and currently only supports pan-sharpened Landsat 8 imagery.

Classified maps exported from Google Earth Engine for 2019 and 2020. Change in coal mining areas between 2019 and 2020

An accurate global impervious surface map at a resolution of 30-m for 2015 by combining Landsat-8 OLI optical images, Sentinel-1 SAR images and VIIRS NTL images based on the Google Earth Engine (GEE) platform.

Sentinel2GlobalLULC is a deep learning-ready dataset of RGB images from the Sentinel-2 satellites designed for global land use and land cover (LULC) mapping. Sentinel2GlobalLULC v2.1 contains 194,877 images in GeoTiff and JPEG format corresponding to 29 broad LULC classes. Each image has 224 x 224 pixels at 10 m spatial resolution and was produced by assigning the 25th percentile of all available observations in the Sentinel-2 collection between June 2015 and October 2020 in order to remove atmospheric effects (i.e., clouds, aerosols, shadows, snow, etc.). A spatial purity value was assigned to each image based on the consensus across 15 different global LULC products available in Google Earth Engine (GEE).

Our dataset is structured into 3 main zip-compressed folders, an Excel file with a dictionary for class names and descriptive statistics per LULC class, and a python script to convert RGB GeoTiff images into JPEG format. The first folder called "Sentinel2LULC_GeoTiff.zip" contains 29 zip-compressed subfolders where each one corresponds to a specific LULC class with hundreds to thousands of GeoTiff Sentinel-2 RGB images. The second folder called "Sentinel2LULC_JPEG.zip" contains 29 zip-compressed subfolders with a JPEG formatted version of the same images provided in the first main folder. The third folder called "Sentinel2LULC_CSV.zip" includes 29 zip-compressed CSV files with as many rows as provided images and with 12 columns containing the following metadata (this same metadata is provided in the image filenames):

• Land Cover Class ID: is the identification number of each LULC class
• Land Cover Class Short Name: is the short name of each LULC class
• Image ID: is the identification number of each image within its corresponding LULC class
• Pixel purity Value: is the spatial purity of each pixel for its corresponding LULC class calculated as the spatial consensus across up to 15 land-cover products
• GHM Value: is the spatial average of the Global Human Modification index (gHM) for each image
• Latitude: is the latitude of the center point of each image
• Longitude: is the longitude of the center point of each image
• Country Code: is the Alpha-2 country code of each image as described in the ISO 3166 international standard. To understand the country codes, we recommend the user to visit the following website where they present the Alpha-2 code for each country as described in the ISO 3166 international standard:https: //www.iban.com/country-codes
• Administrative Department Level1: is the administrative level 1 name to which each image belongs
• Administrative Department Level2: is the administrative level 2 name to which each image belongs
• Locality: is the name of the locality to which each image belongs
• Number of S2 images : is the number of found instances in the corresponding Sentinel-2 image collection between June 2015 and October 2020, when compositing and exporting its corresponding image tile

For seven LULC classes, we could not export from GEE all images that fulfilled a spatial purity of 100% since there were millions of them. In this case, we exported a stratified random sample of 14,000 images and provided an additional CSV file with the images actually contained in our dataset. That is, for these seven LULC classes, we provide these 2 CSV files:

• A CSV file that contains all exported images for this class
• A CSV file that contains all images available for this class at spatial purity of 100%, both the ones exported and the ones not exported, in case the user wants to export them. These CSV filenames end with "including_non_downloaded_images".

To clearly state the geographical coverage of images available in this dataset, we included in the version v2.1, a compressed folder called "Geographic_Representativeness.zip". This zip-compressed folder contains a csv file for each LULC class that provides the complete list of countries represented in that class. Each csv file has two columns, the first one gives the country code and the second one gives the number of images provided in that country for that LULC class. In addition to these 29 csv files, we provided another csv file that maps each ISO Alpha-2 country code to its original full country name.

© Sentinel2GlobalLULC Dataset by Yassir Benhammou, Domingo Alcaraz-Segura, Emilio Guirado, Rohaifa Khaldi, Boujemâa Achchab, Francisco Herrera & Siham Tabik is marked with Attribution 4.0 International (CC-BY 4.0)