<?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"
	>
<channel>
	<title>Comments on: GeoX Rails Geocoding Plugin</title>
	<atom:link href="http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/</link>
	<description>It would be a good idea.</description>
	<pubDate>Fri, 25 Jul 2008 23:46:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Norman Clarke</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-1146</link>
		<dc:creator>Norman Clarke</dc:creator>
		<pubDate>Thu, 06 Mar 2008 23:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-1146</guid>
		<description>Perfect! Thanks a lot, I'm glad in did a "-x" when I installed the plugin now. :-)</description>
		<content:encoded><![CDATA[<p>Perfect! Thanks a lot, I&#8217;m glad in did a &#8220;-x&#8221; when I installed the plugin now. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: science</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-1145</link>
		<dc:creator>science</dc:creator>
		<pubDate>Thu, 06 Mar 2008 22:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-1145</guid>
		<description>Norman: That's all set - new code uploaded to SVN.

Here's how you set Google "locale":
&lt;pre&gt;&lt;code&gt;
location = {:address =&gt; '1711 Martin Luther King Junior Wy', :city =&gt; 'Berkeley', :state =&gt; 'CA'}

geocoder = GeoX::Geocoder.new(:geoengine =&gt; GeoX::Google, :locale =&gt; 'oe=utf8')
locations = geocoder.geocode(location)
&lt;/code&gt;&lt;/pre&gt;
When you create your geocoder, you set this value. It will persist for all subsequent geocodings using that *instance* of the Geocoder.</description>
		<content:encoded><![CDATA[<p>Norman: That&#8217;s all set - new code uploaded to SVN.</p>
<p>Here&#8217;s how you set Google &#8220;locale&#8221;:</p>
<pre><code>
location = {:address => '1711 Martin Luther King Junior Wy', :city => 'Berkeley', :state => 'CA'}

geocoder = GeoX::Geocoder.new(:geoengine => GeoX::Google, :locale => 'oe=utf8')
locations = geocoder.geocode(location)
</code></pre>
<p>When you create your geocoder, you set this value. It will persist for all subsequent geocodings using that *instance* of the Geocoder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norman Clarke</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-1144</link>
		<dc:creator>Norman Clarke</dc:creator>
		<pubDate>Thu, 06 Mar 2008 20:44:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-1144</guid>
		<description>Thanks for putting in the time on this useful plugin. It's very handy for me that it provides a list of possible locations, rather than simple pulling off the first match like other plugins like Geokit do.

One small problem I noticed is that you're not including the option to request UTF-8 from the Google geocode service. This messes up quite a few things in an application I'm working on because place names with accent marks get truncated after the first accented character.

To fix this, simply modify google.rb on line 38:

Before:

url &#60;&#60; "output=xml"

After:

url &#60;&#60; "output=xml&#38;oe=utf-8"</description>
		<content:encoded><![CDATA[<p>Thanks for putting in the time on this useful plugin. It&#8217;s very handy for me that it provides a list of possible locations, rather than simple pulling off the first match like other plugins like Geokit do.</p>
<p>One small problem I noticed is that you&#8217;re not including the option to request UTF-8 from the Google geocode service. This messes up quite a few things in an application I&#8217;m working on because place names with accent marks get truncated after the first accented character.</p>
<p>To fix this, simply modify google.rb on line 38:</p>
<p>Before:</p>
<p>url &lt;&lt; &#8220;output=xml&#8221;</p>
<p>After:</p>
<p>url &lt;&lt; &#8220;output=xml&amp;oe=utf-8&#8243;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Belec</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-997</link>
		<dc:creator>Jason Belec</dc:creator>
		<pubDate>Thu, 28 Feb 2008 20:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-997</guid>
		<description>Thanks, that link alone is worth your weight in gold. And thank you for the wrapper idea, should solve some issues I listed out. I will report back after some testing.</description>
		<content:encoded><![CDATA[<p>Thanks, that link alone is worth your weight in gold. And thank you for the wrapper idea, should solve some issues I listed out. I will report back after some testing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: science</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-996</link>
		<dc:creator>science</dc:creator>
		<pubDate>Thu, 28 Feb 2008 19:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-996</guid>
		<description>Jason: There are a number of resources out on the web that you can use to use a phone number to determine a general area. Because so many numbers are portable (i.e. cell phones), it's often impossible to know for sure where a phone is located (so an 510 number indicates the Eastern part of the San Francisco Bay Area, but I know people with a 510 area code on their cell who live full time in New York City).

With that caveat you could pre-process your incoming addresses with something like:

http://www.bennetyee.org/ucsd-pages/area.html

This is just an example - google "area codes region lookup" or variations to find tons more info.

I'd recommend wrapping GeoX in a pre-processing class that handles conversion from phone numbers to geography where possible. Basically a geocoder should get geographic information, and you should pre-process phone numbers to generate required geographic information which you submit to the big geocoder engines for conversion to lat/long. Hope that helps!</description>
		<content:encoded><![CDATA[<p>Jason: There are a number of resources out on the web that you can use to use a phone number to determine a general area. Because so many numbers are portable (i.e. cell phones), it&#8217;s often impossible to know for sure where a phone is located (so an 510 number indicates the Eastern part of the San Francisco Bay Area, but I know people with a 510 area code on their cell who live full time in New York City).</p>
<p>With that caveat you could pre-process your incoming addresses with something like:</p>
<p><a href="http://www.bennetyee.org/ucsd-pages/area.html" rel="nofollow">http://www.bennetyee.org/ucsd-pages/area.html</a></p>
<p>This is just an example - google &#8220;area codes region lookup&#8221; or variations to find tons more info.</p>
<p>I&#8217;d recommend wrapping GeoX in a pre-processing class that handles conversion from phone numbers to geography where possible. Basically a geocoder should get geographic information, and you should pre-process phone numbers to generate required geographic information which you submit to the big geocoder engines for conversion to lat/long. Hope that helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Belec</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-995</link>
		<dc:creator>Jason Belec</dc:creator>
		<pubDate>Thu, 28 Feb 2008 18:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-995</guid>
		<description>I've been looking for a way to improve the geocode returns and wanted to use the phone number to get a more exact location or to enhance a current location return... Any ideas?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been looking for a way to improve the geocode returns and wanted to use the phone number to get a more exact location or to enhance a current location return&#8230; Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: science</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-327</link>
		<dc:creator>science</dc:creator>
		<pubDate>Mon, 22 Oct 2007 06:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-327</guid>
		<description>I've updated GeoX to support failover geocoding. It's as easy as passing an array into the geocode init routine instead of a single engine. See the wiki or README file for details. 

Also, you can now locate your geox_api_keys.rb file in the Rails root/config folder so you can have an SVN:external link to my code base and stay current more easily.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve updated GeoX to support failover geocoding. It&#8217;s as easy as passing an array into the geocode init routine instead of a single engine. See the wiki or README file for details. </p>
<p>Also, you can now locate your geox_api_keys.rb file in the Rails root/config folder so you can have an SVN:external link to my code base and stay current more easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: a work on process &#187; Rails Geo Plugins: GeoX</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-266</link>
		<dc:creator>a work on process &#187; Rails Geo Plugins: GeoX</dc:creator>
		<pubDate>Tue, 16 Oct 2007 14:26:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-266</guid>
		<description>[...] GeoX is the latest kid on the Ruby on Rails geocoding block. The plugin was announced a couple of weeks ago and I&#8217;ve been meaning to explore it ever since, just in case it had any new features and also so that I can add it to my comparison chart. [...]</description>
		<content:encoded><![CDATA[<p>[...] GeoX is the latest kid on the Ruby on Rails geocoding block. The plugin was announced a couple of weeks ago and I&#8217;ve been meaning to explore it ever since, just in case it had any new features and also so that I can add it to my comparison chart. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Selder</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-226</link>
		<dc:creator>Andrew Selder</dc:creator>
		<pubDate>Wed, 10 Oct 2007 20:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-226</guid>
		<description>I love this plug in... great work.

A couple suggestions.

1. Instead of using an API key file in the plug-in directory, copy the file to the config directory. That way you can use an svn:external link to the plugin.

2. Allow for easy switching of api keys based on environment.</description>
		<content:encoded><![CDATA[<p>I love this plug in&#8230; great work.</p>
<p>A couple suggestions.</p>
<p>1. Instead of using an API key file in the plug-in directory, copy the file to the config directory. That way you can use an svn:external link to the plugin.</p>
<p>2. Allow for easy switching of api keys based on environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: science</title>
		<link>http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-63</link>
		<dc:creator>science</dc:creator>
		<pubDate>Tue, 25 Sep 2007 17:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2007/09/25/geox-rails-geocoding-plugin/#comment-63</guid>
		<description>Oh - that's a really good idea. I'll add failover to GeoX! Thanks.</description>
		<content:encoded><![CDATA[<p>Oh - that&#8217;s a really good idea. I&#8217;ll add failover to GeoX! Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
