KML to GeoJSON Converter

Field guide: KML to GeoJSON Converter

This is the most-traveled bridge in casual GIS: data gets born in Google My Maps or Earth (because anyone can draw there) and needs to die in a web app (because that's where products live) — and the web app speaks GeoJSON. This converter does the crossing properly: Placemark names and ExtendedData become GeoJSON properties, coordinates pass through with KML's altitude term dropped, and Multi-geometries flatten predictably.

Conversion runs entirely client-side — significant when the KML is a client's parcel boundaries or your company's territory map. The preview shows what converted before you download, the attribute table confirms the properties survived, and if the destination is 'just show people a map', skip the developer entirely: the HTML export is a finished interactive Leaflet map with your KML data inlined.

Field tips

• Export from Google My Maps via the layer menu → 'Export to KML/KMZ' — choose KML, not KMZ, to paste here directly (or unzip the KMZ).
• Check the attribute table after loading: description-blob HTML from My Maps sometimes deserves cleanup before it becomes a GeoJSON property.
• GeoJSON wants [lng, lat] and that's exactly what KML's lon,lat coordinate order provides — no manual swapping needed; the converter handles it.

Records are stored only in this browser (localStorage) — export regularly. This tool aids field documentation; it does not replace your agency's official inspection procedures or engineering judgment.