<?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: Google, Microsoft, and the USGS</title>
	<atom:link href="http://jimthompson.org/wp/2005/04/08/google-microsoft-and-the-usgs/feed/" rel="self" type="application/rss+xml" />
	<link>http://jimthompson.org/wp/2005/04/08/google-microsoft-and-the-usgs/</link>
	<description>A clean, well-lighted blog.</description>
	<lastBuildDate>Sat, 16 May 2009 13:22:18 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jim</title>
		<link>http://jimthompson.org/wp/2005/04/08/google-microsoft-and-the-usgs/comment-page-1/#comment-32</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Sun, 05 Jun 2005 18:31:23 +0000</pubDate>
		<guid isPermaLink="false">/?p=73#comment-32</guid>
		<description>Thanks for the notes, Tim.

I was aware that there was a second set of imagery in addition to the USGS Urban Areas imagery, but I didn&#039;t know what it was called.

And yeah, you&#039;re right that Google/Keyhole probably isn&#039;t doing their own orthorectification. Why would they, if the USGS is already doing it? But it never occurred to me that the difference might be simply due to the map projection.</description>
		<content:encoded><![CDATA[<p>Thanks for the notes, Tim.</p>
<p>I was aware that there was a second set of imagery in addition to the USGS Urban Areas imagery, but I didn&#8217;t know what it was called.</p>
<p>And yeah, you&#8217;re right that Google/Keyhole probably isn&#8217;t doing their own orthorectification. Why would they, if the USGS is already doing it? But it never occurred to me that the difference might be simply due to the map projection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Peterson</title>
		<link>http://jimthompson.org/wp/2005/04/08/google-microsoft-and-the-usgs/comment-page-1/#comment-31</link>
		<dc:creator>Tim Peterson</dc:creator>
		<pubDate>Sat, 04 Jun 2005 01:30:52 +0000</pubDate>
		<guid isPermaLink="false">/?p=73#comment-31</guid>
		<description>A few notes:

TerraServer does indeed serve only USGS images, but there are two datasets available (as I&#039;m sure you know). The first is the NAPP (National Aerial Photography Program) 1 meter per pixel grayscale imagery, which covers nearly all of the US. (Some of these images were actually taken in infrared, but they&#039;ve been made grayscale for TerraServer.) The second is the USGS Urban Areas 1 foot resolution color imagery, which covers 30+ major cities. Some sites (such as GlobeXplorer) fall back on the NAPP imagery when they don&#039;t have anything better to display. However, Google (and hence Keyhole) apparently accepts only color imagery, so they instead default to the lower resolution Landsat for the unimaged reaches of the country. Keyhole does make use of the Urban Areas imagery, which you&#039;re seeing in most of the images above.

I rather doubt that Keyhole does their own orthorectification, and even if they did it wouldn&#039;t come out as squished as you see on Google compared with TerraServer&#039;s rendition. The difference between the two is actually the map projection being used. TerraServer uses the UTM (Universal Transverse Mercator) projection, which slices the globe up into zones 6 degrees of longitude wide and then flattens them such that the resulting image pixels closely approximate square meters on the ground. This makes it easy to compare distances and directions on the image, but it also creates gaps between UTM zones. As a compromise between accuracy, user-friendliness, and easy programmability, Google Maps uses a simple lat-long projection, where pixels on the X and Y axes correspond directly to fractions of degrees of longitude and latitude, respectively. Due to the Earth&#039;s curvature, however, this results in a horizontal stretching of the image in areas far from the equator. This is why the Google &quot;Satellite&quot; image is compressed vertically relative to TerraServer even though they both use the same source image. (The Maps view actually has a constant scale factor built in, which returns the map to approximately correct proportions for viewing the US. This scaling wasn&#039;t applied to the Satellite imagery, though, perhaps because Keyhole already had everything in normal lat-long projection.)

As you noted, the USGS Urban Areas imagery has 0.3m (1ft) resolution, which on TerraServer is scaled to 0.25m resolution (to match the powers-of-two zoom levels). Google&#039;s maximum zoom level has a resolution of 1.2m/pixel vertically, and a horizontal resolution that ranges from 0.8m to 1m as you move from north to south in the US (due to the projection). So, Google&#039;s zoom levels are approximately equivalent to TerraServer&#039;s, all the way down to 1m.

--Tim</description>
		<content:encoded><![CDATA[<p>A few notes:</p>
<p>TerraServer does indeed serve only USGS images, but there are two datasets available (as I&#8217;m sure you know). The first is the NAPP (National Aerial Photography Program) 1 meter per pixel grayscale imagery, which covers nearly all of the US. (Some of these images were actually taken in infrared, but they&#8217;ve been made grayscale for TerraServer.) The second is the USGS Urban Areas 1 foot resolution color imagery, which covers 30+ major cities. Some sites (such as GlobeXplorer) fall back on the NAPP imagery when they don&#8217;t have anything better to display. However, Google (and hence Keyhole) apparently accepts only color imagery, so they instead default to the lower resolution Landsat for the unimaged reaches of the country. Keyhole does make use of the Urban Areas imagery, which you&#8217;re seeing in most of the images above.</p>
<p>I rather doubt that Keyhole does their own orthorectification, and even if they did it wouldn&#8217;t come out as squished as you see on Google compared with TerraServer&#8217;s rendition. The difference between the two is actually the map projection being used. TerraServer uses the UTM (Universal Transverse Mercator) projection, which slices the globe up into zones 6 degrees of longitude wide and then flattens them such that the resulting image pixels closely approximate square meters on the ground. This makes it easy to compare distances and directions on the image, but it also creates gaps between UTM zones. As a compromise between accuracy, user-friendliness, and easy programmability, Google Maps uses a simple lat-long projection, where pixels on the X and Y axes correspond directly to fractions of degrees of longitude and latitude, respectively. Due to the Earth&#8217;s curvature, however, this results in a horizontal stretching of the image in areas far from the equator. This is why the Google &#8220;Satellite&#8221; image is compressed vertically relative to TerraServer even though they both use the same source image. (The Maps view actually has a constant scale factor built in, which returns the map to approximately correct proportions for viewing the US. This scaling wasn&#8217;t applied to the Satellite imagery, though, perhaps because Keyhole already had everything in normal lat-long projection.)</p>
<p>As you noted, the USGS Urban Areas imagery has 0.3m (1ft) resolution, which on TerraServer is scaled to 0.25m resolution (to match the powers-of-two zoom levels). Google&#8217;s maximum zoom level has a resolution of 1.2m/pixel vertically, and a horizontal resolution that ranges from 0.8m to 1m as you move from north to south in the US (due to the projection). So, Google&#8217;s zoom levels are approximately equivalent to TerraServer&#8217;s, all the way down to 1m.</p>
<p>&#8211;Tim</p>
]]></content:encoded>
	</item>
</channel>
</rss>
