GeoJSON to KML Converter
The canonical step between a web-mapping dataset and a stakeholder who wants to inspect it in Google Earth.
Common issues converting GeoJSON to KML
- GeoJSON must be in WGS 84; a deprecated 'crs' member pointing to a projected CRS will land your data in the wrong place on the globe. Reproject to EPSG:4326 first.
- The 'name' feature property (if present) becomes the KML <Placemark> label. Rename to 'name' before conversion if your label is in a different property.
- KML styling isn't derivable from GeoJSON properties. The output uses the Google Earth default style; add <Style> elements afterwards if you need custom colors or icons.
- Google My Maps enforces a 5 MB KML limit. For larger outputs, split by feature subset or simplify geometry before converting.
Frequently asked questions
Will all my GeoJSON properties be visible in Google Earth?
Yes. Every property becomes a row in the Placemark's <ExtendedData> table, which Google Earth renders in the default info popup when a user clicks the feature.
How are GeometryCollection features handled?
They're expanded into a <MultiGeometry> container in the output. This preserves all sub-geometries but flattens any nested collection structure.
Can I open the output in Google My Maps?
Yes. Google My Maps imports KML up to 5 MB on the free tier. Strip unused properties or simplify geometry if you hit the limit.
Are feature ids preserved?
Yes. A GeoJSON feature's 'id' becomes the 'id' attribute on the output <Placemark>, so tools keyed on stable identifiers keep working.