Convert GeoJSON to KML
Your file never leaves your device — conversion happens here in your browser.
GeoJSON is built for the browser; KML is built for Google Earth. If you've got a route as GeoJSON — pulled from a web map, exported from a GIS pipeline, or written by hand — and you want to actually fly around it in 3D terrain rather than stare at coordinates, KML is the target that gets you there. This tool takes the LineString geometry and writes it into a KML Placemark with a coordinate sequence Google Earth reads directly. One detail worth knowing if you've done coordinate conversions before: GeoJSON and KML both order coordinates as longitude, latitude, elevation, so this is one of the rare format pairs where nothing needs flipping — most other formats here store latitude first, which is exactly the kind of silent bug that corrupts a route if you're writing your own converter by hand. What doesn't make the trip is anything beyond the geometry itself. KML has no concept of heart rate, cadence, power, or temperature, and no lap structure either, so if your GeoJSON's coordinateProperties block carries sensor data, none of it appears in the output — this conversion is for the shape of your route and where it went, not what your body was doing along the way. Timestamps and elevation do carry over, so playback and altitude profiles still work correctly in Earth's timeline view. As with every conversion on this site, the file never leaves your device: parsing and writing both happen locally in your browser, in a background worker, so even a long route with a dense point count converts without freezing the page.
Questions
Does coordinate order need to be fixed when converting GeoJSON to KML?
No — this is one of the few conversions where it doesn't. GeoJSON and KML both store coordinates as longitude, latitude, elevation, so the values pass straight through without reordering.
Will my heart rate or power data show up in Google Earth?
No. KML has no fields for heart rate, cadence, power, or temperature, so none of that data is written to the output — only position, elevation, and timestamp make the conversion.
Does KML preserve lap boundaries from my GeoJSON?
Neither format has a lap concept, so there's nothing to preserve or lose there — your route becomes a single continuous path in Google Earth either way.
Can I use the resulting KML file for anything besides viewing?
KML is primarily a visualization format for tools like Google Earth and some GIS software. For analysis or further data processing, converting to CSV or GeoJSON instead keeps more of your original data intact.