<?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 Route Tools</title>
	<atom:link href="http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools/</link>
	<description>A design blog with a particular emphasis on green design, design for society, and environmental technologies, Vestal Design Blog also discusses web design, product design, graphic design, and architecture.</description>
	<lastBuildDate>Fri, 12 Mar 2010 07:25:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: links for 2007-05-02 // daily contributions</title>
		<link>http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools/comment-page-1/#comment-46065</link>
		<dc:creator>links for 2007-05-02 // daily contributions</dc:creator>
		<pubDate>Fri, 04 May 2007 01:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools.html#comment-46065</guid>
		<description>[...] Google Maps Route Tools Â» Vestal Design Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] Google Maps Route Tools &#194;&#187; Vestal Design Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-05-02 &#171; Rob Edwards: Collection of my daily bookmarks: roedward</title>
		<link>http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools/comment-page-1/#comment-45785</link>
		<dc:creator>links for 2007-05-02 &#171; Rob Edwards: Collection of my daily bookmarks: roedward</dc:creator>
		<pubDate>Wed, 02 May 2007 07:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools.html#comment-45785</guid>
		<description>[...] Google Maps Route Tools Â» Vestal Design Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] Google Maps Route Tools &#194;&#187; Vestal Design Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Warren</title>
		<link>http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools/comment-page-1/#comment-38943</link>
		<dc:creator>Jeffrey Warren</dc:creator>
		<pubDate>Wed, 11 Apr 2007 21:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools.html#comment-38943</guid>
		<description>Thanks for the tip, Jess, those are interesting - but we&#039;re faced with thousands of points at a time, and need a ceiling of maybe 10-20k points per day, working from addresses.  Also, we really need an API or some kind of remote request service, like Yahoo&#039;s.  Yahoo limits at 5k per day, and we ran through that pretty fast.  I think we&#039;ll figure it out but for now we&#039;re probably going to stick to being really conservative about how many requests we let through.  I wish there were a reliable address-based service we could just buy, maybe per request, or buy 10k per day or so.

In any case there soon will be, this is a huge market and more and more web services will be using datapoints.  Yahoo or Google could probably make a killing by offering a geocoding library with some nice functions like distance_between_points() and others.  I ended up writing them myself.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip, Jess, those are interesting &#8211; but we&#8217;re faced with thousands of points at a time, and need a ceiling of maybe 10-20k points per day, working from addresses.  Also, we really need an API or some kind of remote request service, like Yahoo&#8217;s.  Yahoo limits at 5k per day, and we ran through that pretty fast.  I think we&#8217;ll figure it out but for now we&#8217;re probably going to stick to being really conservative about how many requests we let through.  I wish there were a reliable address-based service we could just buy, maybe per request, or buy 10k per day or so.</p>
<p>In any case there soon will be, this is a huge market and more and more web services will be using datapoints.  Yahoo or Google could probably make a killing by offering a geocoding library with some nice functions like distance_between_points() and others.  I ended up writing them myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jessica Pfund</title>
		<link>http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools/comment-page-1/#comment-38411</link>
		<dc:creator>Jessica Pfund</dc:creator>
		<pubDate>Tue, 10 Apr 2007 06:44:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/04/google-maps-route-tools.html#comment-38411</guid>
		<description>Here&#039;s &lt;a href=&quot;http://groups.google.com/group/Google-Maps-API/web/resources-non-google-geocoders&quot; rel=&quot;nofollow&quot;&gt;a big list&lt;/a&gt; of geocoders and reverse-geocoders.


Note that &lt;a href=&quot;http://earth.google.com/earth_plus.html&quot; rel=&quot;nofollow&quot;&gt;Google Earth Plus&lt;/a&gt; ($20/year) also lets you geocode up to a 100 points at a time based on address while &lt;a href=&quot;http://earth.google.com/earth_pro.html&quot; rel=&quot;nofollow&quot;&gt;Google Earth Pro&lt;/a&gt; ($400/year) lets you geocode up to 2500 at a time (among a lot of other neat features.)</description>
		<content:encoded><![CDATA[<p>Here&#8217;s <a href="http://groups.google.com/group/Google-Maps-API/web/resources-non-google-geocoders" rel="nofollow">a big list</a> of geocoders and reverse-geocoders.</p>
<p>Note that <a href="http://earth.google.com/earth_plus.html" rel="nofollow">Google Earth Plus</a> ($20/year) also lets you geocode up to a 100 points at a time based on address while <a href="http://earth.google.com/earth_pro.html" rel="nofollow">Google Earth Pro</a> ($400/year) lets you geocode up to 2500 at a time (among a lot of other neat features.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
