Downloading and Importing Data from Google Earth to ArcGIS Pro
In the world of Geographic Information Systems (GIS), Google Earth Pro remains a favorite for quick digitizing and 3D visualization. However, to perform advanced spatial modeling, you must move that data into ArcGIS Pro. In 2026, this process has evolved from simple file conversion to direct cloud integration via Google Earth Engine.
1. The Classic Method: KML and KMZ Conversion
The most common way to transfer points, lines, and polygons is by using Keyhole Markup Language (KML). This is the "universal language" of Google Earth.
- Step A (Google Earth): Right-click your folder or feature in the 'Places' panel and select Save Place As.... Choose
.kmz(compressed) or.kml(text-based). - Step B (ArcGIS Pro): Open the Geoprocessing Pane and search for the KML To Layer tool.
- Step C: Input your file and specify an output location. ArcGIS Pro will convert the KML into a File Geodatabase (FGDB) feature class, preserving the original symbology and pop-up information.
2. Advanced Integration: Google Earth Engine (GEE) to ArcGIS Pro
For 2026 workflows involving massive satellite datasets (Sentinel, Landsat), downloading raw files is often inefficient. Using the Google Earth Engine Python API directly inside ArcGIS Pro is now the preferred professional method.
- Authentication: Use the ArcGIS Pro Python Command Prompt to install the
earthengine-apiandgeemaplibraries. - Scripting: Use an ArcGIS Notebook to authenticate your Google Cloud project. You can filter imagery in the cloud and pull only the resulting "clipped" raster into your Pro map.
- Benefit: This avoids the "heavy download" of gigabytes of imagery, bringing only the processed results into your local project.
3. Comparison: Google Earth Data Types in ArcGIS Pro
| Data Source | File Format | Recommended ArcGIS Pro Tool |
|---|---|---|
| Google Earth Pro Features | KML / KMZ | KML To Layer |
| Google My Maps | KML / KMZ | KML To Layer |
| Earth Engine Rasters | GeoTIFF (via Cloud) | Copy Raster / Python API |
| Google Maps (Points/Search) | JSON / CSV | JSON To Features / XY Table To Point |
4. Important Legal and Technical Constraints
While importing vector data is straightforward, capturing Google's Satellite Imagery for use as a local raster tile is strictly prohibited by Google's Terms of Service. For professional mapping, you should instead use the Esri Imagery Basemap, which offers comparable resolution and is fully licensed for GIS use.
- Coordinate Systems: Remember that KML data is always natively in WGS 84 (EPSG:4326). Always use the Project tool in ArcGIS Pro after importing to match your local project's coordinate system (e.g., State Plane or UTM).
- Z-Values: If your Google Earth data contains elevation, ensure the "Include Ground Overlay" or 3D settings are checked during conversion to maintain vertical accuracy.
Conclusion
Moving data from Google Earth to ArcGIS Pro is a bridge between accessibility and analytical power. In 2026, the workflow has shifted from manual "Save As" clicks to powerful cloud-to-desktop integrations. By mastering both the KML To Layer tool for vector data and the Earth Engine API for raster analysis, you can leverage the best of both worlds in your GIS projects. This integration ensures your maps are not only visually recognizable but also mathematically rigorous.
Keywords
import Google Earth to ArcGIS Pro, KML to Layer ArcGIS Pro tutorial, download Google Maps data for GIS, Google Earth Engine ArcGIS Pro integration 2026, convert KMZ to feature class, ArcGIS Pro 3.x KML import, GIS satellite data download guide, ArcGIS Pro geoprocessing KML.
