<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How I geotag my photos</title>
	<atom:link href="http://rishida.net/blog/?feed=rss2&#038;p=79" rel="self" type="application/rss+xml" />
	<link>http://rishida.net/blog/?p=79</link>
	<description>News of changes to my main site, and W3C related posts.</description>
	<lastBuildDate>Thu, 05 Aug 2010 18:29:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lyberty</title>
		<link>http://rishida.net/blog/?p=79&#038;cpage=1#comment-6518</link>
		<dc:creator>Lyberty</dc:creator>
		<pubDate>Tue, 06 Mar 2007 04:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://people.w3.org/rishida/blog/?p=79#comment-6518</guid>
		<description>Hello Ishida - Thanks for the detailed reply! Good to know the details. And thanks again for tools and ongoing blogs. Best regards, - Lyberty</description>
		<content:encoded><![CDATA[<p>Hello Ishida &#8211; Thanks for the detailed reply! Good to know the details. And thanks again for tools and ongoing blogs. Best regards, &#8211; Lyberty</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: site admin</title>
		<link>http://rishida.net/blog/?p=79&#038;cpage=1#comment-6347</link>
		<dc:creator>site admin</dc:creator>
		<pubDate>Sun, 25 Feb 2007 10:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://people.w3.org/rishida/blog/?p=79#comment-6347</guid>
		<description>Hi Lyberty.
1. I&#039;m using version 4.0.2693 (beta) of Google Earth.  This handles overlapping markers better than the last non-beta version I used, by spreading them out for selection, but otherwise everything here should work the same in the non-beta. 

2. I rewrote the paragraph about the example to provide clearer information for those who want to investigate the photo. Thanks.

3. This approach does embed latitude and longitude in the exif data. I extract the information using a Python script I hacked up.  I suppose I should write another blog entry to make that code available...

The labels are exif:GPSLongitude and exif:GPSLatitude.  (There&#039;s also a GPSAltitude, but I haven&#039;t made use of that yet, even though my GPS device gives me that data.)  I too have applications that don&#039;t show that info, and I guess Exifer is one such.

For work on photos I use Adobe PhotoShop CS2, where you can see the information under File Info &gt; Advanced &gt; EXIF Properties.  Unfortunately, CS2 doesn&#039;t allow you to edit the data, and it is displayed with some rounding, so what you see is not as accurate as the actual exif data in the image.</description>
		<content:encoded><![CDATA[<p>Hi Lyberty.<br />
1. I&#8217;m using version 4.0.2693 (beta) of Google Earth.  This handles overlapping markers better than the last non-beta version I used, by spreading them out for selection, but otherwise everything here should work the same in the non-beta. </p>
<p>2. I rewrote the paragraph about the example to provide clearer information for those who want to investigate the photo. Thanks.</p>
<p>3. This approach does embed latitude and longitude in the exif data. I extract the information using a Python script I hacked up.  I suppose I should write another blog entry to make that code available&#8230;</p>
<p>The labels are exif:GPSLongitude and exif:GPSLatitude.  (There&#8217;s also a GPSAltitude, but I haven&#8217;t made use of that yet, even though my GPS device gives me that data.)  I too have applications that don&#8217;t show that info, and I guess Exifer is one such.</p>
<p>For work on photos I use Adobe PhotoShop CS2, where you can see the information under File Info > Advanced > EXIF Properties.  Unfortunately, CS2 doesn&#8217;t allow you to edit the data, and it is displayed with some rounding, so what you see is not as accurate as the actual exif data in the image.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lyberty</title>
		<link>http://rishida.net/blog/?p=79&#038;cpage=1#comment-6346</link>
		<dc:creator>Lyberty</dc:creator>
		<pubDate>Sun, 25 Feb 2007 01:05:11 +0000</pubDate>
		<guid isPermaLink="false">http://people.w3.org/rishida/blog/?p=79#comment-6346</guid>
		<description>Thank you for the details. Very interesting!
What version of Google Earth are you using?
--
You wrote:&quot;Using the geodata. Once I have the geodata in the photo’s metadata, I can use it in a number of ways. I can extract it to label a photo. In this example (click on ’show detail’), you can cut and paste the coordinates into Google Earth or Google Maps to find out where the photo was taken.&quot;
I don&#039;t think that that is supposed to be an example of a photo with metadata embedded... so you might want to clarify by saying &quot;I can extract it so I can provide the data with copies of the original photo (that don&#039;t have the embedded metadata), or to provide the data online so that people don&#039;t have to extract it themselves. In this example ...&quot;
--
You wrote &quot;I also add latitude and longitude to the exif data using Picassa and Google Earth.&quot; Do you know how these aps add the exif data to the image file? Because when I save the largest version of the file used in your example, and open it in Exifer, it doesn&#039;t seem to have the geodata -- just resolution, camera model, etc... Maybe Exifer doesn&#039;t use the latest EXIF version or something, but I suspect that the tool you used to enter the EXIF is using local data. Ideally, we should get to the point where the data is embedded in the image, and the image sharing service can extract that data and display it to users automatically... right?</description>
		<content:encoded><![CDATA[<p>Thank you for the details. Very interesting!<br />
What version of Google Earth are you using?<br />
&#8211;<br />
You wrote:&#8221;Using the geodata. Once I have the geodata in the photo’s metadata, I can use it in a number of ways. I can extract it to label a photo. In this example (click on ’show detail’), you can cut and paste the coordinates into Google Earth or Google Maps to find out where the photo was taken.&#8221;<br />
I don&#8217;t think that that is supposed to be an example of a photo with metadata embedded&#8230; so you might want to clarify by saying &#8220;I can extract it so I can provide the data with copies of the original photo (that don&#8217;t have the embedded metadata), or to provide the data online so that people don&#8217;t have to extract it themselves. In this example &#8230;&#8221;<br />
&#8211;<br />
You wrote &#8220;I also add latitude and longitude to the exif data using Picassa and Google Earth.&#8221; Do you know how these aps add the exif data to the image file? Because when I save the largest version of the file used in your example, and open it in Exifer, it doesn&#8217;t seem to have the geodata &#8212; just resolution, camera model, etc&#8230; Maybe Exifer doesn&#8217;t use the latest EXIF version or something, but I suspect that the tool you used to enter the EXIF is using local data. Ideally, we should get to the point where the data is embedded in the image, and the image sharing service can extract that data and display it to users automatically&#8230; right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
