GeoUnpackGot an .lpk but only have Google Earth? GeoUnpack extracts the layer, reprojects it to WGS84 and writes a KML file Google Earth can open.
How the conversion works
KML only supports latitude and longitude on the WGS84 datum, while layer packages are usually in a projected system such as a UTM zone or State Plane. GeoUnpack reads the layer's coordinate system from the geodatabase and reprojects every vertex to WGS84 (EPSG:4326) before writing the KML, which is why the result lands in the right place in Google Earth.
What to expect in Google Earth
- Every attribute is written into the feature's pop-up balloon.
- Colours, line widths and labels from ArcGIS are not carried over; Google Earth applies its default style, which you can change per folder.
- Google Earth Pro on a computer handles tens of thousands of features. Google My Maps is much stricter: about 2,000 features per layer and a 5 MB file limit, so export smaller layers for it.
- KML is verbose. Expect the file to be several times larger than the same data as a Shapefile.
How to use it
- Drop the .lpk or .lpkx file into the box.
- Select the layer you want.
- Choose 'KML (Google Earth)' and click Convert & download, then open the file in Google Earth.
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
Will it line up correctly in Google Earth?
Yes. KML must use WGS84 longitude/latitude, so GeoUnpack reprojects the data automatically from the package's coordinate system.
Does KML keep the attributes?
Yes, attributes are stored as extended data and show in the feature balloon in Google Earth.