Provide a mechanism to integrate Google Earth Engine data

[DevinJacobs_JGI]

Previously, users were able to use the geemap package to log into GEE, access data through a jupyter notebook, and visualize that data in a mapframe in ArcGIS Pro. With the latest version of arcpro (3.5.3) this connection appears to be broken, and GEE data is no longer able to be added to the map frame via the .addLayer command. 

I would like to request some mechanism to connect to data within GEE in a way that allows for adding said data to a map frame for comparisons/overlays with other relevant datasets. 

[dericksteinmann]

Wow this is really cool! Please keep me updated 

[VenkataKondepati]

I’m seeing the same in Pro 3.5.3 — the old geemap.addLayer() path no longer binds into the Pro map. Two practical workarounds that keep you in Pro:

1) Add GEE as a Web Tile Layer (no export)
In Python, get a tile template from GEE:

import ee, geemap
ee.Initialize()
image = ee.Image('COPERNICUS/S2_SR_HARMONIZED').median().visualize(min=0, max=3000, bands=['B4','B3','B2'])
url = geemap.ee_image_tile_url(image)  # e.g., https://earthengine.googleapis.com/map/{mapid}/{z}/{x}/{y}?token={token}
print(url)

In ArcGIS Pro: Insert → Connections → New Web Tile Layer, paste the {z}/{x}/{y} template.
(If auth tokens expire, you’ll need to refresh the URL; for persistent use, wrap this in a tiny script tool that regenerates and updates the layer.)

2) Export, then add to map (robust for analysis/overlay)

Export from GEE to a local COG/GeoTIFF, then add to Pro:

import ee, geemap, arcpy
ee.Initialize()
roi = ee.Geometry.BBox(-106.7, 31.6, -106.2, 32.0)
image = ee.Image('USGS/SRTMGL1_003').clip(roi)
out = r"C:\temp\srtm.tif"
geemap.ee_export_image(image, filename=out, scale=30, region=roi, file_per_band=False)
arcpy.mp.ArcGISProject('CURRENT').activeMap.addDataFromPath(out)

Benefits: stable, full raster tools, no token refresh issues.

Notes that helped me

Use a cloned Pro env and install earthengine-api + geemap there; re-authenticate with earthengine authenticate.

For dynamic layers without exports, the Web Tile Layer route is the closest to the old “visualize in mapframe” experience.

If you need features from GEE, export to GeoJSON/FGDB first, then add.

If Esri restores the direct notebook→map binding for geemap, great; until then, tile template or export flows have been reliable for me.

[HannesZiegler]

Hi @DevinJacobs_JGI , thank you for submitting this idea! Just to clarify- geemap is a third-party Python API package built around the Google Earth Engine (GEE) and is not maintained by Esri. As such, breaks in functionality in geemap are not something esri can directly address. To get help with the recent break for <geemap.Map>.addLayer, I recommend reaching out to the developers via Issues · gee-community/geemap. They’re best positioned to help troubleshoot or suggest workarounds.