<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kml on ikml.com</title>
    <link>https://ikml.com/tags/kml/</link>
    <description>Recent content in Kml on ikml.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ikml.com/tags/kml/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>iKML 0.1 Shows What Is Inside a KML, KMZ or GeoJSON File Before You Import It</title>
      <link>https://ikml.com/ikml-0.1-shows-what-is-inside-a-kml-kmz-or-geojson-file-before-you-import-it/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ikml.com/ikml-0.1-shows-what-is-inside-a-kml-kmz-or-geojson-file-before-you-import-it/</guid>
      <description>&lt;p&gt;Somebody sends you a map file. A KMZ from a drone pilot, a KML export from Google My Maps, a GeoJSON layer from a city&amp;rsquo;s open data portal. You open it in QGIS, or upload it to a web map, and something is off: a few points are missing, a polygon doesn&amp;rsquo;t draw, the icons are grey squares, half the attribute columns are gone. Nothing told you why.&lt;/p&gt;&#xA;&lt;p&gt;iKML 0.1 tells you first. It opens KML, KMZ and GeoJSON files, shows what&amp;rsquo;s inside them, flags what&amp;rsquo;s broken, explains exactly what a conversion to another format will lose, and writes a cleaned copy with a list of every change.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Swapped Latitude and Longitude Sends Points to the Wrong Side of the World</title>
      <link>https://ikml.com/swapped-latitude-and-longitude-sends-points-to-the-wrong-side-of-the-world/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ikml.com/swapped-latitude-and-longitude-sends-points-to-the-wrong-side-of-the-world/</guid>
      <description>&lt;p&gt;KML writes every position as longitude first, then latitude: &lt;code&gt;34.78,32.08&lt;/code&gt; is a point in Tel Aviv. Most people say coordinates the other way round, &amp;ldquo;latitude, longitude&amp;rdquo;, because that&amp;rsquo;s how maps and phones show them. So when somebody types a few points into a KML file by hand, or a script builds one from a spreadsheet with the columns in the wrong order, the numbers go in backwards.&lt;/p&gt;&#xA;&lt;p&gt;The file is still valid. Every number is in range. It opens without an error. And every point lands somewhere else entirely: &lt;code&gt;32.08,34.78&lt;/code&gt; read as longitude 32.08, latitude 34.78 is in the sea just off the west coast of Cyprus. Swap the numbers for Zurich and you get a point in the Horn of Africa.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What KML, KMZ and GeoJSON Are and Why Map Files Lose Data on Import</title>
      <link>https://ikml.com/what-kml-kmz-and-geojson-are-and-why-map-files-lose-data-on-import/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ikml.com/what-kml-kmz-and-geojson-are-and-why-map-files-lose-data-on-import/</guid>
      <description>&lt;p&gt;Most map data that moves between people moves in one of three formats. They look interchangeable, and every tool converts between them. They aren&amp;rsquo;t interchangeable, which is why so much goes missing on the way.&lt;/p&gt;&#xA;&lt;h2 id=&#34;kml-built-for-an-earth-viewer&#34;&gt;KML: Built for an Earth Viewer&lt;/h2&gt;&#xA;&lt;p&gt;KML, the Keyhole Markup Language, was made for the program that became Google Earth. Keyhole, the company, was bought by Google in 2004. Google later handed the format to the Open Geospatial Consortium, and KML 2.2 became an OGC standard in 2008.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
