Server-Side vs Client-Side Objects in Google Earth Engine
Pulakesh Pradhan
PhD Scholar, MPhil, UGC-SRF (Focus Area: Climate and Agriculture || Rural Geography)
Google Earth Engine (GEE) is a cloud-based platform that provides a massive catalogue of satellite imagery and geospatial datasets, along with powerful tools to analyze and visualize them. Within GEE, objects can be categorized into two primary types: server-side objects and client-side objects.
Server-Side Objects
Server-side objects are created and processed entirely on GEE’s cloud infrastructure. They reside in GEE’s servers and are computationally expensive to manipulate. Once a server-side object is created, it remains on the server until you explicitly delete it.
EECU (Earth Engine Compute Units) measures the computational resources required to execute a task or script in Google Earth Engine Server.
Examples:
ee.ImageCollection('LANDSAT/LC08/C01/T1_SR')
ee.Geometry.Rectangle(-122.35, 37.77, -122.15, 37.97)
ee.FeatureCollection('USDA/ERS/Global_Trade')
ee.Algorithms.Landsat.thermalAnomaly
Client-Side Objects
领英推荐
Client-side objects are created and manipulated within your browser. They are less computationally expensive than server-side objects but have limited capabilities. Client-side objects are often used to visualize data or interact with the user interface. Client-side objects in GEE are created and manipulated within your browser. They are not directly prefixed with ee..
Common Client-Side Objects:
Examples:
In summary, server-side objects are the backbone of GEE, handling data processing and analysis. Client-side objects provide the user interface and visualization capabilities. By understanding the differences between these two types of objects, you can effectively leverage GEE’s capabilities to analyze and visualize geospatial data.
?? More insights & projects: pulakeshpradhan.github.io