GeoUnpackZip your .gdb folder, drop it below and export any feature class to KML, reprojected to WGS84 for Google Earth.
From geodatabase to Google Earth
Feature classes in a file geodatabase are usually stored in a projected coordinate system. KML needs WGS84 latitude and longitude, so GeoUnpack reprojects each feature class during export. Zip the .gdb folder, drop it in, tick a feature class, choose KML and open the downloaded file in Google Earth.
Practical tips
- Export one feature class per KML file; it keeps Google Earth's Places panel readable.
- Attributes appear in each feature's balloon. Coded-value domains show as codes, not descriptions.
- For Google My Maps, stay under about 2,000 features and 5 MB per file.
- Need a
.kmz? It is simply a zipped KML: zip the file and rename the extension to.kmz. - If a feature class has no coordinate system defined, reprojection is not possible; export it as Shapefile and assign the system in a GIS first.
How to use it
- Compress the .gdb folder to a .zip.
- Drop the .zip into the box.
- Select layers, choose 'KML' and click Convert & download.
Supported formats
| Input | What it is |
|---|---|
.lpk / .lpkx | ArcGIS layer package (ArcMap / ArcGIS Pro) |
.mpk / .mpkx | ArcGIS map package (ArcMap / ArcGIS Pro) |
.gdb (zipped) | File geodatabase folder, compressed to .zip |
Output: Shapefile, GeoPackage, GeoJSON, KML, CSV. Vector layers and tables only; raster and tile packages are not supported yet.
FAQ
Can I make a KMZ?
Export to KML, then compress the .kml file to a .zip and rename it to .kmz. Google Earth opens both.