<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coordinates on ikml.com</title>
    <link>https://ikml.com/tags/coordinates/</link>
    <description>Recent content in Coordinates 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/coordinates/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
