<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Google Earth on ikml.com</title>
    <link>https://ikml.com/tags/google-earth/</link>
    <description>Recent content in Google Earth 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/google-earth/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KMZ Files That Point to Pictures on Someone Else&#39;s Computer</title>
      <link>https://ikml.com/kmz-files-that-point-to-pictures-on-someone-elses-computer/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ikml.com/kmz-files-that-point-to-pictures-on-someone-elses-computer/</guid>
      <description>&lt;p&gt;A KMZ is supposed to carry its pictures with it. That&amp;rsquo;s the reason it exists: the KML document goes into a zip archive together with the icons, the photos in the descriptions and the images of any overlays, and the whole thing works anywhere.&lt;/p&gt;&#xA;&lt;p&gt;It only works if the document refers to the copies inside the archive. When someone builds a placemark in Google Earth with an icon from their desktop, or pastes a photo into a description, the reference can end up as a path on their own computer. They see everything, because the files are right there. Everyone else sees a broken image.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
