Web-based GIS for spatiotemporal crop climate niche mapping Interactive Google Earth Engine Application—Version 2, July 2020 https://cropniche.cartoscience.com https://cartoscience.users.earthengine.app/view/crop-niche Google Earth Engine Code /* ---------------------------------------------------------------------------------------------------------------------- # CropSuit-GEE Authors: Brad G. Peter (bpeter@ua.edu), Joseph P. Messina, and Zihan Lin Organizations: BGP, JPM - University of Alabama; ZL - Michigan State University Last Modified: 06/28/2020 To cite this code use: Peter, B. G.; Messina, J. P.; Lin, Z., 2019, "Web-based GIS for spatiotemporal crop climate niche mapping", https://doi.org/10.7910/DVN/UFC6B5, Harvard Dataverse, V1 ------------------------------------------------------------------------------------------------------------------------- This is a Google Earth Engine crop climate suitability geocommunication and map export tool designed to support agronomic development and deployment of improved crop system technologies. This content is made possible by the support of the American People provided to the Feed the Future Innovation Lab for Sustainable Intensification through the United States Agency for International Development (USAID). The contents are the sole responsibility of the authors and do not necessarily reflect the views of USAID or the United States Government. Program activities are funded by USAID under Cooperative Agreement No. AID-OAA-L-14-00006. ------------------------------------------------------------------------------------------------------------------------- Summarization of input options: There are 14 user options available. The first is a country of interest selection using a 2-digit FIPS code (link available below). This selection is used to produce a rectangular bounding box for export; however, other geometries can be selected with minimal modification to the code. Options 2 and 3 specify the complete temporal range for aggregation (averaged across seasons; single seasons may also be selected). Options 4–7 specify the growing season for calculating total seasonal rainfall and average season temperatures and NDVI (NDVI is for export only and is not used in suitability determination). Options 8–11 specify the climate parameters for the crop of interest (rainfall and temperature max/min). Option 12 enables masking to agriculture, 13 enables exporting of all data layers, and 14 is a text string for naming export files. ------------------------------------------------------------------------------------------------------------------------- ••••••••••••••••••••••••••••••••••••••••••• USER OPTIONS ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• */ // CHIRPS data availability: https://developers.google.com/earth-engine/datasets/catalog/UCSB-CHG_CHIRPS_PENTAD // MOD11A2 data availability: https://developers.google.com/earth-engine/datasets/catalog/MODIS_006_MOD11A2 var country = 'MI' // [1] https://en.wikipedia.org/wiki/List_of_FIPS_country_codes var startRange = 2001 // [2] var endRange = 2017 // [3] var startSeasonMonth = 11 // [4] var startSeasonDay = 1 // [5] var endSeasonMonth = 4 // [6] var endSeasonDay = 30 // [7] var precipMin = 750 // [8] var precipMax = 1200 // [9] var tempMin = 22 // [10] var tempMax = 32 // [11] var maskToAg = 'TRUE' // [12] 'TRUE' (default) or 'FALSE' var exportLayers = 'TRUE' // [13] 'TRUE' (default) or 'FALSE' var exportNameHeader = 'crop_suit_maize' // [14] text string for naming export file // ••••••••••••••••••••••••••••••••• NO USER INPUT BEYOND THIS POINT •••••••••••••••••••••••••••••••••••••••••••••••••••• // Access precipitation and temperature ImageCollections and a global countries FeatureCollection var region = ee.FeatureCollection('USDOS/LSIB_SIMPLE/2017') .filterMetadata('country_co','equals',country) var precip = ee.ImageCollection('UCSB-CHG/CHIRPS/PENTAD').select('precipitation') var temp = ee.ImageCollection('MODIS/006/MOD11A2').select(['LST_Day_1km','LST_Night_1km']) var ndvi = ee.ImageCollection('MODIS/006/MOD13Q1').select(['NDVI']) // Create layers for masking to agriculture and masking out water bodies var waterMask = ee.Image('UMD/hansen/global_forest_change_2015').select('datamask').eq(1) var agModis = ee.ImageCollection('MODIS/006/MCD12Q1').select('LC_Type1').mode() .remap([1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17], [0,0,0,0,0,0,0,0,0,0,0,1,0,1,0,0,0]) var agGC = ee.Image('ESA/GLOBCOVER_L4_200901_200912_V2_3').select('landcover') .remap([11,14,20,30,40,50,60,70,90,100,110,120,130,140,150,160,170,180,190,200,210,220,230], [1,1,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]) var cropland = ee.Image('USGS/GFSAD1000_V1').neq(0) var agMask = agModis.add(agGC).add(cropland).gt(0).eq(1) // Modify user input options for processing with raw data var years = ee.List.sequence(startRange,endRange) var bounds = region.geometry().bounds() var tMinMod = (tempMin+273.15)/0.02 var tMaxMod = (tempMax+273.15)/0.02 //...

Forest cover is rapidly changing at the global scale as a result of land-use change (principally deforestation in many tropical regions and afforestation in many temperate regions) and climate change. However, a detailed map of global forest gain is still lacking at fine spatial and temporal resolutions. In this study, we developed a new automatic framework to map annual forest gain across the globe, based on Landsat time series, the LandTrendr algorithm and the Google Earth Engine (GEE) platform. First, samples of stable forest collected based on the Global Forest Change product (GFC) were used to determine annual Normalized Burn Ratio (NBR) thresholds for forest gain detection. Secondly, with the NBR time-series from 1982 to 2020 and LandTrendr algorithm, we produced dataset of global forest gain year from 1984 to 2020 based on a set of decision rules. Our results reveal that large areas of forest gain occurred in China, Russia, Brazil and North America, and the vast majority of the global forest gain has occurred since 2000. The new dataset was consistent in both spatial extent and years of forest gain with data from field inventories and alternative remote sensing products. Our dataset is valuable for policy-relevant research on the net impact of forest cover change on the global carbon cycle and provides an efficient and transferable approach for monitoring other types of land cover dynamics.

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....

GEE-TED: A tsetse ecological distribution model for Google Earth Engine Please refer to the associated publication: Fox, L., Peter, B.G., Frake, A.N. and Messina, J.P., 2023. A Bayesian maximum entropy model for predicting tsetse ecological distributions. International Journal of Health Geographics, 22(1), p.31. https://link.springer.com/article/10.1186/s12942-023-00349-0 Description GEE-TED is a Google Earth Engine (GEE; Gorelick et al. 2017) adaptation of a tsetse ecological distribution (TED) model developed by DeVisser et al. (2010), which was designed for use in ESRI's ArcGIS. TED uses time-series climate and land-use/land-cover (LULC) data to predict the probability of tsetse presence across space based on species habitat preferences (in this case Glossina Morsitans). Model parameterization includes (1) day and night temperatures (MODIS Land Surface Temperature; MOD11A2), (2) available moisture/humidity using a vegetation index as a proxry (MODIS NDVI; MOD13Q1), (3) LULC (MODIS Land Cover Type 1; MCD12Q1), (4) year selections, and (5) fly movement rate (meters/16-days). TED has also been used as a basis for the development of an agent-based model by Lin et al. (2015) and in a cost-benefit analysis of tsetse control in Tanzania by Yang et al. (2017). Parameterization in Fox et al. (2023): Suitable LULC types and climate thresholds used here are specific to Glossina Morsitans in Kenya and are based on the parameterization selections in DeVisser et al. (2010) and DeVisser and Messina (2009). Suitable temperatures range from 17–40°C during the day and 10–40°C at night and available moisture is characterized as NDVI > 0.39. Suitable LULC comprises predominantly woody vegetation; a complete list of suitable categories is available in DeVisser and Messina (2009). In the Fox et al. (Forthcoming) publication, two versions of MCD12Q1 were used to assess suitable LULC types: Versions 051 and 006. The GeoTIFF supplied in this dataset entry (GEE-TED_Kenya_2016-2017.tif) uses the aforementioned parameters to show the probable tsetse distribution across Kenya for the years 2016-2017. A static graphic of this GEE-TED output is shown below and an interactive version can be viewed at: https://cartoscience.users.earthengine.app/view/gee-ted. Figure associated with Fox et al. (2023) GEE code The code supplied below is generalizable across geographies and species; however, it is highly recommended that parameterization is given considerable attention to produce reliable results. Note that output visualization on-the-fly will take some time and it is recommended that results be exported as an asset within GEE or exported as a GeoTIFF. Note: Since completing the Fox et al. (2023) manuscript, GEE has removed Version 051 per NASA's deprecation of the product. The current release of GEE-TED now uses only MCD12Q1 Version 006; however, alternative LULC data selections can be used with minimal modification to the code. // Input options var tempMin = 10 // Temperature thresholds in degrees Celsius var tempMax = 40 var ndviMin = 0.39 // NDVI thresholds; proxy for available moisture/humidity var ndviMax = 1 var movement = 500 // Fly movement rate in meters/16-days var startYear = 2008 // The first 2 years will be used for model initialization var endYear = 2019 // Computed probability is based on startYear+2 to endYear var country = 'KE' // Country codes - https://en.wikipedia.org/wiki/List_of_FIPS_country_codes var crs = 'EPSG:32737' // See https://epsg.io/ for appropriate country UTM zone var rescale = 250 // Output spatial resolution var labelSuffix = '02052020' // For file export labeling only //[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17] MODIS/006/MCD12Q1 var lulcOptions006 = [1,1,1,1,1,1,1,1,1, 0, 1, 0, 0, 0, 0, 0, 0] // 1 = suitable 0 = unsuitable // No more input required ------------------------------ // var region = ee.FeatureCollection("USDOS/LSIB_SIMPLE/2017") .filterMetadata('country_co', 'equals', country) // Input parameter modifications var tempMinMod = (tempMin+273.15)/0.02 var tempMaxMod = (tempMax+273.15)/0.02 var ndviMinMod = ndviMin*10000 var ndviMaxMod = ndviMax*10000 var ndviResolution = 250 var movementRate = movement+(ndviResolution/2) // Loading image collections var lst = ee.ImageCollection('MODIS/006/MOD11A2').select('LST_Day_1km', 'LST_Night_1km') .filter(ee.Filter.calendarRange(startYear,endYear,'year')) var ndvi = ee.ImageCollection('MODIS/006/MOD13Q1').select('NDVI') .filter(ee.Filter.calendarRange(startYear,endYear,'year')) var lulc006 = ee.ImageCollection('MODIS/006/MCD12Q1').select('LC_Type1') // Lulc mode and boolean reclassification var lulcMask = lulc006.mode().remap([1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17],lulcOptions006) .eq(1).rename('remapped').clip(region) // Merge NDVI and LST image collections var combined = ndvi.combine(lst, true) var combinedList = combined.toList(10000) // Boolean reclassifications (suitable/unsuitable) for day/night temperatures and ndvi var con =...

Geospatial raster data and vector data created in the frame of the study "Mapping Arctic Lake Ice Backscatter Anomalies using Sentinel-1 Time Series on Google Earth Engine" submitted to the journal "Remote Sensing" and Python code to reproduce the results.

In addition to the full repository (Supplement_to_RS_Arctic_Lake_Ice_Backscatter_Anomalies.zip), two reduced alternatives of this repository are available due to large file size of the full repository:

Supplement_to_RS_Arctic_Lake_Ice_Backscatter_Anomalies_without_IW_result_data.zip contains the same data and Python scripts as the full repository, but results based on IW data and tiled EW delta sigma0 images directly exported from Google Earth Engine have been removed. The merged data (from tiled EW delta sigma0 images) and all other results deduced thereof are included.

Supplement_to_RS_Arctic_Lake_Ice_Backscatter_Anomalies_scripts_and_reference_data_only.zip contains only the Python scripts and reference data. The directory structure was retained for better reproducibility.

Please see the associated README-files for details.

Results from time-series analysis of Landsat images in characterizing global forest extent and change. The 'first' and 'last' bands are reference multispectral imagery from the first and last available years for Landsat spectral bands corresponding to red, NIR, SWIR1, and SWIR2. Reference composite imagery represents median observations from a set of quality-assessed growing-season observations for each of these bands. Please see the User Notes for this update, as well as the associated journal article: Hansen, Potapov, Moore, Hancher et al. "High-resolution global maps of 21st-century forest cover change." Science 342.6160 (2013): 850-853.

GEODATA TOPO 250K Series 3 is a vector representation of the major features appearing on 1:250,000 scale NATMAP topographic maps and is supplied in various formats over a defined area. It is primarily designed to provide high quality data for mapping
and GIS professionals.
Data includes powerlines and pipelines and is supplied for commercial GIS and public use in the formats described below.
GEODATA TOPO 250K Series 3 is available as a packaged product in Personal Geodatabase, ArcView Shapefile or MapInfo TAB file formats. Each
package includes data arranged in ten main themes - cartography, elevation, framework, habitation, hydrography, infrastructure, terrain, transport, utility and vegetation. Data is also available as GEODATA TOPO 250K Series 3 for Google Earth in .kml format for use on Google Earth TM Mapping
Service.
All data is based on GDA94 coordinate system, however .kml format data has been converted to WGS84.
Use of GEODATA TOPO 250K Series 3 is subject to a licence, the full terms of which are contained within the package. Interactive Maps, Geoscience Australia`s on-line map download
system, delivering free download of seamless data. MapConnect will allow you to select a specific area (subject to parameters) and themes or select individual tiles for download. Data will be available in GML and Shape file formats.
Customised 250K GEODATA is available where requirements
are not met by the packaged or Interactive Maps options. The price will be determined after assessing your needs - contact the Geoscience Australia Sales Centre. Alternately, we may refer you to a third party supplier.
Packaged product formats - Personal geodatabase (Geocat # 63999), Shapefiles
(Geocat # 64058), TAB files (Geocat # 64059), KML files for use with Google Earth (Geocat # 65137). Product Specifications Themes: Cartography, Elevation, Framework, Habitation, Hydrography, Infrastructure, Terrain, Transport, Utility and Vegetation Coverage: National
(Powerlines not available in South Australia) Currency: Data has a currency of less than five years for any location Coordinates: Geographical Datum: Geocentric Datum of Australia (GDA94) Formats: Personal Geodatabase, ArcView Shapefile and MapInfo TAB Medium: Packaged DVD ROM ($99 per package) or online via Interactive Maps Previous Version: Replaces GEODATA TOPO 250K Series 2

Abstract: We present a detailed geomorphological map (1:5000-scale) of a middle mountainous area in Jena, Germany. To overcome limitations associated with traditional field-based approaches and to extend the possibility of manually digital mapping in a structural way, we propose an approach using geographic information systems (GIS) and high-resolution digital data. The geomorphological map features were extracted by manually interpreting and analyzing the combination of different data sources using light detection and ranging (LiDAR) data. A combination of topographic and geological maps, digital orthophotos (DOPs), Google Earth images, field investigations, and derivatives from digital terrain models (DTMs) revealed that it is possible to generate and present the geomorphologic features involved in classical mapping approaches. We found that LiDAR-DTM and land surface parameters (LSPs) can provide better results when incorporating the visual interpretation of multidirectional hillshade and LSP composite maps. The genesis of landforms can be readily identified, and findings enabled us to systematically delineate landforms and geomorphological process domains. Although our approach provides a cost effective, objective, and reproducible alternative for the classical approach, we suggest that further use of digital data should be undertaken to support analysis and applications.

ERA5-Land is a reanalysis dataset providing a consistent view of the evolution of land variables over several decades at an enhanced resolution compared to ERA5. ERA5-Land has been produced by replaying the land component of the ECMWF ERA5 climate reanalysis. Reanalysis combines model data with observations from across the world into a globally complete and consistent dataset using the laws of physics. Reanalysis produces data that goes several decades back in time, providing an accurate description of the climate of the past. This dataset includes all 50 variables as available on CDS. ERA5-Land data is available from 1950 to three months from real-time. Please consult the ERA5-Land "Known Issues" section. In particular, note that three components of the total evapotranspiration have values swapped as follows: variable "Evaporation from bare soil" (mars parameter code 228101 (evabs)) has the values corresponding to the "Evaporation from vegetation transpiration" (mars parameter 228103 (evavt)), variable "Evaporation from open water surfaces excluding oceans (mars parameter code 228102 (evaow)) has the values corresponding to the "Evaporation from bare soil" (mars parameter code 228101 (evabs)), variable "Evaporation from vegetation transpiration" (mars parameter code 228103 (evavt)) has the values corresponding to the "Evaporation from open water surfaces excluding oceans" (mars parameter code 228102 (evaow)). The asset is a daily aggregate of ECMWF ERA5 Land hourly assets which includes both flow and non-flow bands. Flow bands are formed by collecting the first hour's data of the following day which holds aggregated sum of previous day and while the non-flow bands are created by averaging all hourly data of the day. The flow bands are labeled with the "_sum" identifier, which approach is different from the daily data produced by Copernicus Climate Data Store, where flow bands are averaged too. Daily aggregates have been pre-calculated to facilitate many applications requiring easy and fast access to the data. Precipitation and other flow (accumulated) bands might occasionally have negative values, which doesn't make physical sense. At other times their values might be excessively high. This problem is due to how the GRIB format saves data: it simplifies or "packs" the data into smaller, less precise numbers, which can introduce errors. These errors get worse when the data varies a lot. Because of this, when we look at the data for a whole day to compute daily totals, sometimes the highest amount of rainfall recorded at one time can seem larger than the total rainfall measured for the entire day. To learn more, Please see: "Why are there sometimes small negative precipitation accumulations"

OpenStreetMap (openstreetmap.org) is a global collaborative mapping project, which offers maps and map data released with an open license, encouraging free re-use and re-distribution. The data is created by a large community of volunteers who use a variety of simple on-the-ground surveying techniques, and wiki-syle editing tools to collaborate as they create the maps, in a process which is open to everyone. The project originated in London, and an active community of mappers and developers are based here. Mapping work in London is ongoing (and you can help!) but the coverage is already good enough for many uses.

Browse the map of London on OpenStreetMap.org

Downloads:

The whole of England updated daily:

• england.osm.bz2 ~185M - .osm formatted raw XML data (compressed)
• england.shp.zip ~156M - ESRI shapefiles

For more details of downloads available from OpenStreetMap, including downloading the whole planet, see 'planet.osm' on the wiki.

Data access APIs:

Download small areas of the map by bounding-box. For example this URL requests the data around Trafalgar Square:

http://api.openstreetmap.org/api/0.6/map?bbox=-0.13062,51.5065,-0.12557,51.50969

Data filtered by "tag". For example this URL returns all elements in London tagged shop=supermarket:

http://www.informationfreeway.org/api/0.6/*[shop=supermarket][bbox=-0.48,51.30,0.21,51.70]

The .osm format

The format of the data is a raw XML represention of all the elements making up the map. OpenStreetMap is composed of interconnected "nodes" and "ways" (and sometimes "relations") each with a set of name=value pairs called "tags". These classify and describe properties of the elements, and ultimately influence how they get drawn on the map. To understand more about tags, and different ways of working with this data format refer to the following pages on the OpenStreetMap wiki.

• .osm - About the raw XML data format of OpenStreetMap
• Downloading data - More details of the API and extract download options
• Xapi - The extended api for filtering by tag
• Map Features - A list of tags, and what map features they represent
• Converting map data between formats - catalogue of tools for converting from .osm to other formats

Simple embedded maps

Rather than working with raw map data, you may prefer to embed maps from OpenStreetMap on your website with a simple bit of javascript. You can also present overlays of other data, in a manner very similar to working with google maps. In fact you can even use the google maps API to do this. See OSM on your own website for details and links to various javascript map libraries.

Help build the map!

The OpenStreetMap project aims to attract large numbers of contributors who all chip in a little bit to help build the map. Although the map editing tools take a little while to learn, they are designed to be as simple as possible, so that everyone can get involved. This project offers an exciting means of allowing local London communities to take ownership of their part of the map.

Read about how to Get Involved and see the London page for details of OpenStreetMap community events.

The MOD13Q1 V6.1 product provides a Vegetation Index (VI) value at a per pixel basis. There are two primary vegetation layers. The first is the Normalized Difference Vegetation Index (NDVI) which is referred to as the continuity index to the existing National Oceanic and Atmospheric Administration-Advanced Very High Resolution Radiometer (NOAA-AVHRR) derived NDVI. The second vegetation layer is the Enhanced Vegetation Index (EVI) that minimizes canopy background variations and maintains sensitivity over dense vegetation conditions. The EVI also uses the blue band to remove residual atmosphere contamination caused by smoke and sub-pixel thin cloud clouds. The MODIS NDVI and EVI products are computed from atmospherically corrected bi-directional surface reflectances that have been masked for water, clouds, heavy aerosols, and cloud shadows. Documentation: User's Guide Algorithm Theoretical Basis Document (ATBD) General Documentation

This is a mutli-modal dataset for restaurants from Google Local (Google Maps). Data includes images and reviews posted by users, as well as metadata for each restaurant.

LinkedIn Company Data for Company Analysis, Valuation & Portfolio Strategy LinkedIn company data is one of the most powerful forms of alternative data for understanding company behavior, firmographics, business dynamics, and real-time hiring signals. Canaria’s enriched LinkedIn company data provides detailed company profiles, including hiring activity, job postings, employee trends, headquarters and branch locations, and verified metadata from Google Maps. This LinkedIn corporate data is updated weekly and optimized for use in company analysis, startup scouting, private company valuation, and investment monitoring. It supports BI dashboards, risk models, CRM enrichment, and portfolio strategy.

Use Cases: What Problems This LinkedIn Data Solves Our LinkedIn company insights transform opaque business landscapes into structured, analyzable data. Whether you’re conducting M&A due diligence, tracking high-growth companies, or benchmarking performance, this dataset empowers fast, confident decisions.

Company Analysis • Identify a company’s size, industry classification, and headcount signals using LinkedIn firmographic data • Analyze social presence through LinkedIn follower metrics and employee engagement • Understand geographic expansion through branch locations and hiring distribution • Benchmark companies using LinkedIn profile activity and job posting history • Monitor business changes with real-time LinkedIn updates

Company Valuation & Financial Benchmarking • Feed LinkedIn-based firmographics into comps and financial models • Use hiring velocity from LinkedIn job data as a proxy for business growth • Strengthen private market intelligence with verified non-financial signals • Validate scale, structure, and presence via LinkedIn and Google Maps footprint

Company Risk Analysis • Detect red flags using hiring freezes or drop in profile activity • Spot market shifts through location downsizing or organizational changes • Identify distressed companies with decreased LinkedIn job posting frequency • Compare stated presence vs. active behavior to identify risk anomalies

Business Intelligence (BI) & Strategic Planning • Segment companies by industry, headcount, growth behavior, and hiring activity • Build BI dashboards integrating LinkedIn job trends and firmographic segmentation • Identify geographic hiring hotspots using Maps and LinkedIn signal overlays • Track job creation, title distribution, and skill demand in near real-time • Export filtered LinkedIn corporate data into CRMs, analytics tools, and lead scoring systems

Portfolio Management & Investment Monitoring • Enhance portfolio tracking with LinkedIn hiring data and firmographic enrichment • Spot hiring surges, geographic expansions, or restructuring in real-time • Correlate LinkedIn growth indicators with strategic outcomes • Analyze competitors and targets using historical and real-time LinkedIn data • Generate alerts for high-impact company changes in your portfolio universe

What Makes This LinkedIn Company Data Unique

Includes Real-Time Hiring Signals • Gain visibility into which companies are hiring, at what scale, and for which roles using enriched LinkedIn job data

Verified Location Intelligence • Confirm branch and HQ locations with Google Maps coordinates and public company metadata

Weekly Updates • Stay ahead of the market with fresh, continuously updated LinkedIn company insights

Clean & Analysis-Ready Format • Structured, deduplicated, and taxonomy-mapped data that integrates with CRMs, BI platforms, and investment models

Who Benefits from LinkedIn Company Data • Hedge funds, VCs, and PE firms analyzing startup and private company activity • Portfolio managers and financial analysts tracking operational shifts • Market research firms modeling sector momentum and firmographics • Strategy teams calculating market size using LinkedIn company footprints • BI and analytics teams building company-level dashboards • Compliance and KYC teams enriching company identity records • Corp dev teams scouting LinkedIn acquisition targets and expansion signals

Summary Canaria’s LinkedIn company data delivers high-frequency, high-quality insights into U.S. companies, combining job posting trends, location data, and firmographic intelligence. With real-time updates and structured delivery formats, this alternative dataset enables powerful workflows across company analysis, financial modeling, investment research, market segmentation, and business strategy.

About Canaria Inc. Canaria Inc. is a leader in alternative data, specializing in job market intelligence, LinkedIn company data, and Glassdoor salary analytics. We deliver clean, structured, and enriched datasets at scale using proprietary data scraping pipelines and advanced AI/LLM-based modeling, all backed by human validation. Our AI-powered pipeline is developed by a seasoned team of machine learning experts from Google, Meta, and Amazon, and by alumni of Stanford, Caltech, and Columbia ...

MSZSI: Multi-Scale Zonal Statistics [AgriClimate] Inventory -------------------------------------------------------------------------------------- MSZSI is a data extraction tool for Google Earth Engine that aggregates time-series remote sensing information to multiple administrative levels using the FAO GAUL data layers. The code at the bottom of this page (metadata) can be pasted into the Google Earth Engine JavaScript code editor and ran at https://code.earthengine.google.com/. Input options: [1] Country of interest [2] Start and end year [3] Start and end month [4] Option to mask data to a specific land-use/land-cover type [5] Land-use/land-cover type code from CGLS LULC [6] Image collection for data aggregation [7] Desired band from the image collection [8] Statistics type for the zonal aggregations [9] Statistic to use for annual aggregation [10] Scaling options [11] Export folder and label suffix Output: Two CSVs containing zonal statistics for each of the FAO GAUL administrative level boundaries Output fields: system:index, 0-ADM0_CODE, 0-ADM0_NAME, 0-ADM1_CODE, 0-ADM1_NAME, 0-ADMN_CODE, 0-ADMN_NAME, 1-AREA_PERCENT_LULC, 1-AREA_SQM_LULC, 1-AREA_SQM_ZONE, 2-X_2001, 2-X_2002, 2-X_2003, ..., 2-X_2020, .geo PREPROCESSED DATA DOWNLOAD The datasets available for download contain zonal statistics at 2 administrative levels (FAO GAUL levels 1 and 2). Select countries from Southeast Asia and Sub-Saharan Africa (Cambodia, Indonesia, Lao PDR, Myanmar, Philippines, Thailand, Vietnam, Burundi, Kenya, Malawi, Mozambique, Rwanda, Tanzania, Uganda, Zambia, Zimbabwe) are included in the current version, with plans to extend the dataset to contain global metrics. Each zip file is described below and two example NDVI tables are available for preview. Key: [source, data, units, temporal range, aggregation, masking, zonal statistic, notes] Currently available: MSZSI-V2_V-NDVI-MEAN.tar: [NASA-MODIS, NDVI, index, 2001–2020, annual mean, agriculture, mean, n/a] MSZSI-V2_T-LST-DAY-MEAN.tar: [NASA-MODIS, LST Day, °C, 2001–2020, annual mean, agriculture, mean, n/a] MSZSI-V2_T-LST-NIGHT-MEAN.tar: [NASA-MODIS, LST Night, °C, 2001–2020, annual mean, agriculture, mean, n/a] MSZSI-V2_R-PRECIP-SUM.tar: [UCSB-CHG-CHIRPS, Precipitation, mm, 2001–2020, annual sum, agriculture, mean, n/a] MSZSI-V2_S-BDENS-MEAN.tar: [OpenLandMap, Bulk density, g/cm3, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200] MSZSI-V2_S-ORGC-MEAN.tar: [OpenLandMap, Organic carbon, g/kg, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200] MSZSI-V2_S-PH-MEAN.tar: [OpenLandMap, pH in H2O, pH, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200] MSZSI-V2_S-WATER-MEAN.tar: [OpenLandMap, Soil water, % at 33kPa, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200] MSZSI-V2_S-SAND-MEAN.tar: [OpenLandMap, Sand, %, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200] MSZSI-V2_S-SILT-MEAN.tar: [OpenLandMap, Silt, %, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200] MSZSI-V2_S-CLAY-MEAN.tar: [OpenLandMap, Clay, %, static, n/a, agriculture, mean, at depths 0-10-30-60-100-200] MSZSI-V2_E-ELEV-MEAN.tar: [MERIT, [elevation, slope, flowacc, HAND], [m, degrees, km2, m], static, n/a, agriculture, mean, n/a] Coming soon MSZSI-V2_C-STAX-MEAN.tar: [OpenLandMap, Soil taxonomy, category, static, n/a, agriculture, area sum, n/a] MSZSI-V2_C-LULC-MEAN.tar: [CGLS-LC100-V3, LULC, category, 2015–2019, mode, none, area sum, n/a] Data sources: https://developers.google.com/earth-engine/datasets/catalog/MODIS_006_MOD13Q1 https://developers.google.com/earth-engine/datasets/catalog/MODIS_006_MOD11A2 https://developers.google.com/earth-engine/datasets/catalog/UCSB-CHG_CHIRPS_PENTAD https://developers.google.com/earth-engine/datasets/catalog/OpenLandMap_SOL_SOL_BULKDENS-FINEEARTH_USDA-4A1H_M_v02 https://developers.google.com/earth-engine/datasets/catalog/OpenLandMap_SOL_SOL_ORGANIC-CARBON_USDA-6A1C_M_v02 https://developers.google.com/earth-engine/datasets/catalog/OpenLandMap_SOL_SOL_PH-H2O_USDA-4C1A2A_M_v02 https://developers.google.com/earth-engine/datasets/catalog/OpenLandMap_SOL_SOL_WATERCONTENT-33KPA_USDA-4B1C_M_v01 https://developers.google.com/earth-engine/datasets/catalog/OpenLandMap_SOL_SOL_CLAY-WFRACTION_USDA-3A1A1A_M_v02 https://developers.google.com/earth-engine/datasets/catalog/OpenLandMap_SOL_SOL_SAND-WFRACTION_USDA-3A1A1A_M_v02 https://developers.google.com/earth-engine/datasets/catalog/OpenLandMap_SOL_SOL_GRTGROUP_USDA-SOILTAX_C_v01 https://developers.google.com/earth-engine/datasets/catalog/COPERNICUS_Landcover_100m_Proba-V-C3_Global https://developers.google.com/earth-engine/datasets/catalog/MERIT_Hydro_v1_0_1 https://developers.google.com/earth-engine/datasets/catalog/FAO_GAUL_2015_level0 https://developers.google.com/earth-engine/datasets/catalo... Visit https://dataone.org/datasets/sha256%3A1844d916f64551cf0a8e0fe8d71474912d22e43d77c43c848aa8fac7e7e02f29 for complete metadata about this dataset.

Repository providing free access to marine geophysical data (e.g. bathymetry, seismic data, magnetics, gravity, images) and related land-based data from NSF-funded research conducted throughout the global oceans. Data Portals include GeoPRISMS, MARGINS, Ridge 2000, Antarctic and Southern Ocean Data Synthesis, the Global Multi-Resolution Topography Synthesis, and Seismic Reflection Field Data Portal. Primary data types served are multibeam bathymetric data from the ocean floor, seismic reflection data imaging below the seafloor, and multi-disciplinary ship based data from the Southern Ocean. Other holdings include deep-sea photographic transects, and ultra-high resolution bathymetry, temperature probe data, biological species compilations, MAPR and CTD data. Derived data products and sets include microseismicity catalogs, images, visualization scenes, magnetic and gravity compilations, grids of seismic layer thickness, velocity models, GIS project files, and 3D visualizations. Tools to discover, explore, and visualize data are available. They deliver catalogs, maps, and data through standard programmatic interfaces. GeoMapApp, a standalone data visualization and analysis tool, permits dynamic data exploration from a map interface and the capability to generate and download custom grids and maps and other data. Through GeoMapApp, users can access data hosted at the MGDS, at other data repositories, and import their own data sets. Global Multi-Resolution Topography (GMRT) is a continuously-updated compilation of seafloor bathymetry integrated with global land topography. It can be used to create maps and grids and it can be accessed through several standard programmatic interfaces including GeoMapApp and Google Earth. The GMRT compilation can also be explored in 3D using Virtual Ocean. The MGDS MediaBank contains high quality images, illustrations, animations and video clips that are organized into galleries. Media can be sorted by category, and keyword and map-based search options are provided. Each item in the MediaBank is accompanied by metadata that provides access to a cruise catalog and data repository.

The global Cloud Native GIS Platform market is poised for significant expansion, projected to reach an estimated $12,500 million by 2025, with a robust Compound Annual Growth Rate (CAGR) of 18.5% through 2033. This upward trajectory is propelled by an increasing demand for scalable, flexible, and accessible geospatial data solutions across diverse industries. The inherent advantages of cloud-native architectures – such as enhanced data processing capabilities, real-time analytics, and simplified deployment – are making these platforms indispensable for modern geographic information system (GIS) applications. Key drivers fueling this growth include the burgeoning need for advanced land surveying and mapping, environmental monitoring initiatives, sophisticated traffic management systems, and enhanced public safety applications. The transition from traditional on-premise GIS solutions to cloud-native alternatives is a defining trend, enabling organizations to leverage powerful GIS functionalities without the burden of substantial infrastructure investments. This shift democratizes access to sophisticated geospatial tools, fostering innovation and efficiency in how spatial data is managed, analyzed, and visualized. The market is characterized by a dynamic interplay of technological advancements and evolving user needs. While the server computing type continues to hold a significant share, the rapid emergence and adoption of serverless computing type present a compelling growth opportunity. Serverless architectures offer unparalleled scalability and cost-effectiveness, making them increasingly attractive for handling fluctuating workloads and dynamic data processing requirements. Despite the promising outlook, certain restraints such as data security concerns, integration complexities with legacy systems, and the need for specialized cloud-native GIS expertise may pose challenges. However, the market is actively addressing these through continuous innovation in security protocols, development of comprehensive integration tools, and increased training programs. Major players like ESRI, Mapbox, and Google Maps are at the forefront, investing heavily in R&D to offer cutting-edge cloud-native GIS solutions, further solidifying the market's growth trajectory. The Asia Pacific region, driven by rapid digitalization and smart city initiatives in countries like China and India, is expected to exhibit the fastest growth, closely followed by North America and Europe. This report delves into the dynamic realm of Cloud Native GIS Platforms, a technology revolutionizing how organizations harness location-based data. From sophisticated land surveying to real-time traffic management, these platforms are becoming indispensable. Our analysis spans the Historical Period (2019-2024), the Base Year (2025), and forecasts future trajectory through 2033. The market is witnessing significant growth, estimated to reach hundreds of millions of dollars by the Estimated Year (2025), with projections soaring into the billions of dollars by 2033. This comprehensive report provides in-depth insights into market dynamics, key players, emerging trends, and future opportunities within this critical technology sector.

Auburn Maine's parcel Inquiry map with optional zoning and high-resolution aerial photography. Optional zoning layers. Map provides detailed assessing data for each parcel as well as links to WebPro assessing records and Google Street View. Users can search for parcels using parcel ID, location, or owner name. Advanced search options provide ability to select and buffer parcels with an optional export to csv file.

The RADARSAT-2 ESA archive collection consists of RADARSAT-2 products requested by ESA supported projects over their areas of interest around the world. The dataset regularly grows as ESA collects new products over the years. Following Beam modes are available: Standard, Wide Swath, Fine Resolution, Extended Low Incidence, Extended High Incidence, ScanSAR Narrow and ScanSAR Wide. Standard Beam Mode allows imaging over a wide range of incidence angles with a set of image quality characteristics which provides a balance between fine resolution and wide coverage, and between spatial and radiometric resolutions. Standard Beam Mode operates with any one of eight beams, referred to as S1 to S8, in single and dual polarisation . The nominal incidence angle range covered by the full set of beams is 20 degrees (at the inner edge of S1) to 52 degrees (at the outer edge of S8). Each individual beam covers a nominal ground swath of 100 km within the total standard beam accessibility swath of more than 500 km. Beam Mode Product Nominal Resolution (metres) Nominal Pixel Spacing Range x Azimuth (metres) Resolution Range x Azimuth (metres) Nominal Scene Size Range x Azimuth (kilometres) Range of Angle of Incidence (degrees) Number of Looks Range x Azimuth Polarisations Options Standard SLC 25 8.0 or 11.8 x 5.1 9.0 or 13.5 x 7.7 100 x 100 20 - 52 1 x 1 Single Pol HH or VV or HV or VH - or - Dual HH + HV or VV + VH SGX 8.0 x 8.0 26.8 - 17.3 x 24.7 1 x 4 SGF 12.5 x 12.5 SSG, SPG Wide Swath Beam Mode allows imaging of wider swaths than Standard Beam Mode, but at the expense of slightly coarser spatial resolution. The three Wide Swath beams, W1, W2 and W3, provide coverage of swaths of approximately 170 km, 150 km and 130 km in width respectively, and collectively span a total incidence angle range from 20 degrees to 45 degrees. Polarisation can be single and dual. Beam Mode Product Nominal Resolution (metres) Nominal Pixel Spacing Range x Azimuth (metres) Resolution Range x Azimuth (metres) Nominal Scene Size Range x Azimuth (kilometres) Range of Angle of Incidence (degrees) Number of Looks Range x Azimuth Polarisations Options Wide SLC 30 11.8 x 5.1 13.5 x 7.7 150 x 150 20 - 45 1 x 1 Single: Pol HH or VV or HV or VH - or - Dual: HH + HV or VV + VH SGX 10 x 10 40.0 - 19.2 x 24.7 1 x 4 SGF 12.5 x 12.5 SSG, SPG Fine Resolution Beam Mode is intended for applications which require finer spatial resolution. Products from this beam mode have a nominal ground swath of 50 km. Nine Fine Resolution physical beams, F23 to F21, and F1 to F6 are available to cover the incidence angle range from 30 to 50 degrees. For each of these beams, the swath can optionally be centred with respect to the physical beam or it can be shifted slightly to the near or far range side. Thanks to these additional swath positioning choices, overlaps of more than 50% are provided between adjacent swaths. RADARSAT-2 can operate in single and dual polarisation for this beam mode. Beam Mode Product Nominal resolution (metres) Nominal Pixel Spacing Range x Azimuth (metres) Resolution Range x Azimuth (metres) Nominal Scene Size Range x Azimuth (kilometres) Range of Angle of Incidence (degrees) Number of Looks Range x Azimuth Polarisations Options Fine SLC 8 4.7 x 5.1 5.2 x 7.7 50 x 50 30 - 50 1 x 1 Single: Pol HH or VV or HV or VH - or - Dual: HH + HV or VV + VH SGX 3.13 x 3.13 10.4 - 6.8 x 7.7 1 x 1 SGF 6.25 x 6.25 SSG, SPG In the Extended Low Incidence Beam Mode, a single Extended Low Incidence Beam, EL1, is provided for imaging in the incidence angle range from 10 to 23 degrees with a nominal ground swath coverage of 170 km. Some minor degradation of image quality can be expected due to operation of the antenna beyond its optimum scan angle range. Only single polarisation is available. Beam Mode Product Nominal resolution (metres) Nominal Pixel Spacing Range x Azimuth (metres) Resolution Range x Azimuth (metres) Nominal Scene Size Range x Azimuth (kilometres) Range of Angle of Incidence (degrees) Number of Looks Range x Azimuth Polarisations Options Extended Low SLC 25 8.0 x 5.1 9.0 x 7.7 170 x 170 10 - 23 1 x 1 Single: HH SGX 10.0 x 10.0 52.7 - 23.3 x 24.7 1 x 4 SGF 12.5 x 12.5 SSG, SPG In the Extended High Incidence Beam Mode, six Extended High Incidence Beams, EH1 to EH6, are available for imaging in the 49 to 60 degree incidence angle range. Since these beams operate outside the optimum scan angle range of the SAR antenna, some degradation of image quality, becoming progressively more severe with increasing incidence angle, can be expected when compared with the Standard Beams. Swath widths are restricted to a nominal 80 km for the inner three beams, and 70 km for the outer beams. Only single polarisation available. Beam Mode Product Nominal resolution (metres) Nominal Pixel Spacing Range x Azimuth (metres) Resolution Range x Azimuth (metres) Nominal Scene Size Range x Azimuth (kilometres) Range of Angle of Incidence (degrees) Num...

This Mobile Location Data product provides extensive coverage of North America with precise timestamped GPS coordinates from opted in mobile devices. Data is available both in real time and historically, enabling detailed analysis of movement patterns, foot traffic trends and location based behavior.

The dataset is sourced via partnerships with established app publishers, ensuring accuracy, scale and full privacy compliance. Each record contains latitude, longitude, event timestamp and optional device metadata, making it adaptable for operational monitoring and strategic market research.

Included attributes: Latitude & Longitude coordinates Event timestamp (epoch & date) Mobile Advertising ID (IDFA/GAID) Horizontal accuracy (~85% fill rate) Country code (ISO3) Optional metadata: IP address, carrier, device model Access & Delivery Delivered via API with polygon queries (up to 10,000 tiles)

Formats: JSON, CSV, Parquet Supports API, AWS S3, or Google Cloud Storage delivery Hourly or daily refresh options Historical coverage starting September 2024 Flexible, credit-based query pricing Privacy & Compliance Fully compliant with GDPR and CCPA Clear privacy notices with every data source Robust opt-in/opt-out user controls

Use Cases Retail expansion & site selection Audience segmentation & behavioral analysis Urban mobility planning & infrastructure optimization DOOH / OOH campaign performance measurement Geofencing for targeted marketing campaigns Tourism & event attendance mapping

The National Census of Ferry Operators (NCFO) Terminals dataset was collected through December 31, 2020 and compiled on October 16, 2024 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The Ferry Terminals dataset represents all ferry terminals from operators that provided responses to the 2020 National Census of Ferry Operators. Areas covered by the dataset include the 50 states as well as the territories of Puerto Rico, the United States Virgin Island, and American Samoa. The terminals represent departure and arrival locations for ferry segments in the NCFO. As part of the NCFO questionnaire, respondents were asked terminal name, city, and state. From this information, longitude and latitudes were obtained through open, online searches that include operator websites and map platforms such as Google Maps and Open Street Maps. As a result, termina sometimes do not represent the exact location where ferry vessels dock but may represent other locations such as the operator’s business location or alternative docking locations. However, whenever possible, the terminal locations represent departure and arrival points for that ferry segment. Each terminal contains information about its operation and ownership status, in addition to geographic location and transportation connections, whenever operators provided this information. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529043