<?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 Maps API shows off vastly improved geocoding</title>
	<atom:link href="http://www.digitalearthblog.com/200805/google-maps-api-shows-off-vastly-improved-geocoding/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalearthblog.com/200805/google-maps-api-shows-off-vastly-improved-geocoding/</link>
	<description>Keeping up with the various digital globe products from companies such as Google, Microsoft and more</description>
	<lastBuildDate>Mon, 10 Dec 2012 15:31:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: mickey</title>
		<link>http://www.digitalearthblog.com/200805/google-maps-api-shows-off-vastly-improved-geocoding/#comment-659</link>
		<dc:creator>mickey</dc:creator>
		<pubDate>Thu, 08 May 2008 00:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalearthblog.com/?p=275#comment-659</guid>
		<description><![CDATA[Pamela,

Thanks for the info.  That explains it.

However, what is the purpose in using different datasets?  Wouldn&#039;t you be better off using one and then tweaking to be as accurate as possible?]]></description>
		<content:encoded><![CDATA[<p>Pamela,</p>
<p>Thanks for the info.  That explains it.</p>
<p>However, what is the purpose in using different datasets?  Wouldn&#8217;t you be better off using one and then tweaking to be as accurate as possible?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pamela Fox</title>
		<link>http://www.digitalearthblog.com/200805/google-maps-api-shows-off-vastly-improved-geocoding/#comment-658</link>
		<dc:creator>Pamela Fox</dc:creator>
		<pubDate>Wed, 07 May 2008 23:32:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalearthblog.com/?p=275#comment-658</guid>
		<description><![CDATA[Google Maps is licensed to use Navteq data. Google Maps API is licensed to use Teleatlas data. The rooftop data comes from the Teleatlas database. Therefore.. :)]]></description>
		<content:encoded><![CDATA[<p>Google Maps is licensed to use Navteq data. Google Maps API is licensed to use Teleatlas data. The rooftop data comes from the Teleatlas database. Therefore.. <img src='http://www.digitalearthblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: que</title>
		<link>http://www.digitalearthblog.com/200805/google-maps-api-shows-off-vastly-improved-geocoding/#comment-646</link>
		<dc:creator>que</dc:creator>
		<pubDate>Thu, 01 May 2008 22:58:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalearthblog.com/?p=275#comment-646</guid>
		<description><![CDATA[Nope, didn&#039;t work well for me. My address was off by several houses even though I&#039;ve manually pinpointed my house thru the maps &#039;edit&#039; option. Using the regular Maps site still locates it correctly though.]]></description>
		<content:encoded><![CDATA[<p>Nope, didn&#8217;t work well for me. My address was off by several houses even though I&#8217;ve manually pinpointed my house thru the maps &#8216;edit&#8217; option. Using the regular Maps site still locates it correctly though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mickey</title>
		<link>http://www.digitalearthblog.com/200805/google-maps-api-shows-off-vastly-improved-geocoding/#comment-645</link>
		<dc:creator>mickey</dc:creator>
		<pubDate>Thu, 01 May 2008 17:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalearthblog.com/?p=275#comment-645</guid>
		<description><![CDATA[Very good point.  They&#039;ve probably got a ton of markers that have been tweaked, so they don&#039;t want to erase those with the new geocoding.

I&#039;ll be curious to see what they eventually do with it.]]></description>
		<content:encoded><![CDATA[<p>Very good point.  They&#8217;ve probably got a ton of markers that have been tweaked, so they don&#8217;t want to erase those with the new geocoding.</p>
<p>I&#8217;ll be curious to see what they eventually do with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Taylor</title>
		<link>http://www.digitalearthblog.com/200805/google-maps-api-shows-off-vastly-improved-geocoding/#comment-644</link>
		<dc:creator>Frank Taylor</dc:creator>
		<pubDate>Thu, 01 May 2008 17:01:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalearthblog.com/?p=275#comment-644</guid>
		<description><![CDATA[The Google Maps database also has input from many users who have used the &quot;Edit -&gt; Move Marker&quot; feature.  I imagine they will have to integrate the new database with this user database.  Also, I suspect they want to &quot;try it out&quot; to see what the reaction is before they put it on the main Maps database.]]></description>
		<content:encoded><![CDATA[<p>The Google Maps database also has input from many users who have used the &#8220;Edit -&gt; Move Marker&#8221; feature.  I imagine they will have to integrate the new database with this user database.  Also, I suspect they want to &#8220;try it out&#8221; to see what the reaction is before they put it on the main Maps database.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
