Events are fired by user interaction with a widget or a programmatic change to a widget. To do something when the event occurs, register a callback function on the widget with either onClick() (for ui.Map or ui.Button) or onChange() (everything else). You can also specify a callback in the constructor. The parameters to event callbacks vary depending on the widget and event type. For example, a ui.Textbox passes the currently entered string value to its ‘click’ event callback functions. Check the API reference in the Docs tab for the type of parameter passed to the callback functions of each widget.

The following example demonstrates multiple events originating from a single user action of specifying an image to display. When the user selects an image, another select widget is updated with the bands of the image and displays the first band in the map:

Code Editor (JavaScript)

// Load some images.
var dem = ee.Image('NASA/NASADEM_HGT/001');
var veg = ee.Image('NOAA/VIIRS/001/VNP13A1/2022_06_02')
  .select(['EVI', 'EVI2', 'NDVI']);

// Make a drop-down menu of bands.
var bandSelect = ui.Select({
  placeholder: 'Select a band...',
  onChange: function(value) {
    var layer = ui.Map.Layer(imageSelect.getValue().select(value));
    // Use set() instead of add() so the previous layer (if any) is overwritten.
    Map.layers().set(0, layer);

// Make a drop down menu of images.
var imageSelect = ui.Select({
  items: [
    {label: 'NASADEM', value: dem},
    {label: 'VIIRS Veg', value: veg}
  placeholder: 'Select an image...',
  onChange: function(value) {
    // Asynchronously get the list of band names.
    value.bandNames().evaluate(function(bands) {
      // Display the bands of the selected image.
      // Set the first band to the selected band.


Note that when the user selects an image, the list of the image's band names is loaded into the bandSelect widget, the first band is set to the current value, and the onChange function of bandSelect is fired automatically. Also note the use of evaluate() to asynchronously get the value of the ComputedObject returned by bandNames(). Learn more in the Asynchronous Events section.


The unlisten() method provides the ability to remove callback functions registered on a widget. This is useful to prevent triggering events that should only occur once, or under certain circumstances. The return value of onClick() or onChange() is an ID that can be passed to unlisten() in order to make the widget stop calling the function. To unregister all events or events of a specific type, call unlisten() with no arguments or an event type (e.g. 'click' or 'change') argument, respectively. The following example demonstrates unlisten() to facilitate opening and closing of a panel:

Code Editor (JavaScript)

// Create a panel, initially hidden.
var panel = ui.Panel({
  style: {
    width: '400px',
    shown: false
  widgets: [
    ui.Label('Click on the map to collapse the settings panel.')

// Create a button to unhide the panel.
var button = ui.Button({
  label: 'Open settings',
  onClick: function() {
    // Hide the button.'shown', false);
    // Display the panel.'shown', true);

    // Temporarily make a map click hide the panel
    // and show the button.
    var listenerId = Map.onClick(function() {'shown', false);'shown', true);
      // Once the panel is hidden, the map should not
      // try to close it by listening for clicks.

// Add the button to the map and the panel to root.
ui.root.insert(0, panel);

Observe that unlisten() is used to stop Map from listening for click events to close the panel when the panel is already closed.

Asynchronous Events

If you use an Earth Engine result (such the numerical output from a reduction) in a widget, you will need to get the value from the server. (See the this page for details about client vs. server in Earth Engine). To keep from hanging the entire UI while that value is computed, you can use the evaluate() function to get the value asynchronously. The evaluate() function begins a request for a value, and when the value is ready calls a callback function to do something with the result. For example, consider an application to get the mean value of an NDVI time series at a point:

Code Editor (JavaScript)

// Load and display an NDVI image.
var ndvi = ee.ImageCollection('LANDSAT/LC8_L1T_8DAY_NDVI')
    .filterDate('2014-01-01', '2015-01-01');
var vis = {min: 0, max: 1, palette: ['99c199', '006400']};
Map.addLayer(ndvi.median(), vis, 'NDVI');

// Configure the map.
Map.setCenter(-94.84497, 39.01918, 8);'cursor', 'crosshair');

// Create a panel and add it to the map.
var inspector = ui.Panel([ui.Label('Click to get mean NDVI')]);

Map.onClick(function(coords) {
  // Show the loading label.
  inspector.widgets().set(0, ui.Label({
    value: 'Loading...',
    style: {color: 'gray'}

  // Determine the mean NDVI, a long-running server operation.
  var point = ee.Geometry.Point(coords.lon,;
  var meanNdvi = ndvi.reduce('mean');
  var sample = meanNdvi.sample(point, 30);
  var computedValue = sample.first().get('NDVI_mean');

  // Request the value from the server.
  computedValue.evaluate(function(result) {
    // When the server returns the value, show it.
    inspector.widgets().set(0, ui.Label({
      value: 'Mean NDVI: ' + result.toFixed(2),

When the user clicks a point on this map, a reduceRegion() call is triggered on the server. This operation might take a while. To prevent the application from blocking while Earth Engine is computing, this example registers a callback function to the result, specifically computedValue.evaluate(). When the computation is finished, the result is displayed. In the meantime, a message is displayed to indicate that the computation is in progress.