Map files get passed around constantly. Drone mission files, survey boundaries, council data layers, exports from Google My Maps. Open one in QGIS, ArcGIS, a web map or a spreadsheet and things quietly go wrong. Points land in the ocean. A polygon won’t draw. Icons are missing. Folders and attributes vanish in the conversion, and nobody tells you.
iKML tells you. It opens KML, KMZ, GeoJSON, GPX and CSV files, reports what’s inside, flags problems, says what a conversion would lose, and writes a cleaned copy with a log of every change. It runs in the browser with nothing uploaded, or as a small command-line program.
The Pitch in Four Numbers
- 22 of 22 broken test files flagged with exactly the issue codes they were built to trigger.
- 0 bytes of your file sent anywhere by the in-browser inspector.
- 1 engine. The same Go code runs the command-line program and the browser, using only the standard library.
- 5 formats read and written: KML, KMZ, GeoJSON, GPX and CSV.
How It Works
The engine is written in Go. On Linux, macOS and Windows it runs as the ikml program. Compiled to WebAssembly, the same code powers the inspector on the website. In the browser your file is read from disk into the page’s memory. There’s no server processing it, and the preview doesn’t even load map tiles.
Run ikml check and you get a list of what’s in the file and what’s wrong with it: swapped latitude and longitude, polygon rings that aren’t closed, icons missing from a KMZ archive, links to pictures sitting on somebody else’s computer. Ask for a conversion and you get a report of what’s lost, what’s kept in another form and what changed.
ikml clean fixes the safe things: it closes rings, removes repeated points, corrects coordinate spacing and repairs broken style references. It only swaps latitude and longitude when you ask, and it never touches the original file.
What It Reads
KML 2.2, plus the older 2.0 and 2.1 namespaces, and KMZ. GeoJSON to RFC 7946, plus older files with a crs member. GPX 1.0 and 1.1. CSV with latitude and longitude columns. It understands Google’s gx:Track with per-point times, gx:MultiTrack and gx:altitudeMode. Other vendor extensions, like DJI’s wpml in drone missions, are listed and kept in KML output. NetworkLinks are listed and deliberately not fetched, since fetching would break the promise that nothing leaves your machine.
Testing used hand-written files that mimic exports from Google Earth, My Maps, DJI, ArcGIS and QGIS, plus random round trips and fuzzing.
Who It’s For
- Drone pilots handling DJI mission KMZs.
- GIS users in QGIS or ArcGIS who receive files from other people.
- Anyone exporting from Google My Maps or juggling GPS tracks.
- People with private site plans who don’t want to upload them to an online converter.
Limits
No Shapefile or GML. No reprojection. No editing beyond the safe automatic fixes. External NetworkLink content isn’t fetched. Vendor extensions beyond Google’s are inspected and kept in KML, not interpreted in depth. And it’s not affiliated with Google: KML is an open standard of the Open Geospatial Consortium.
The Four-Question Screening
Every project featured here gets the same four questions, the way you’d screen a startup idea.
1. Where is the money in it?
iKML is free and has no paid tier. The money is in the people who move map data for a living: surveyors, drone service companies, utilities, councils and the GIS consultancies that serve them. The paid paths are a desktop or team edition with batch checking across folders, Shapefile and GML support, reprojection, and checks built into the pipelines where map files get imported every day. Drone operators alone produce a steady stream of mission files that have to arrive intact.
2. What real problem does it solve?
Silent data loss. Converters are good at converting and bad at saying what they threw away. When a boundary loses a vertex or a set of attributes disappears on import, nobody notices until a decision has been made on the wrong data.
3. The technology in plain words
Think of a customs inspector for map files. Before the file comes in, the inspector opens it, lists everything inside, points out anything damaged or missing, and tells you what would get left behind if you repacked it into a different suitcase. Then, if you like, it repacks it neatly and hands you a list of what it changed.
4. Moat and differentiation
Plenty of tools convert map files. Few explain what they lose, and fewer run entirely in the browser with nothing uploaded. iKML’s edge is the conversion report and the privacy: one engine that runs the same in a browser tab and on the command line, with the file never leaving your machine. The moat that can grow is the library of real-world quirks from each exporter, which is slow, unglamorous work that a big GIS suite rarely does well.
Why It Matters
Maps drive real decisions about land, infrastructure and flight paths. When the file is wrong, the decision is wrong. A quick, private look inside before importing is the kind of small check that saves a lot of rework.
Follow the Project
Try the in-browser inspector, get the program from the download page, read why map files lose data on import, or see the code in the iKML repository on GitHub. iKML is listed with the other open-source projects on SoftDevStudio.com, and more featured projects are in the Projects section.