<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
>

<channel>
	<title>nearby.org.uk blog &#187; geohash</title>
	<atom:link href="http://www.nearby.org.uk/blog/tag/geohash/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nearby.org.uk/blog</link>
	<description>GIS, maps, mapping, geo, UK, Geograph, PHP, Perl and more</description>
	<lastBuildDate>Fri, 01 Jul 2011 18:59:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>Geohash converter; API limit upped</title>
		<link>http://www.nearby.org.uk/blog/2008/02/28/geohash-converter-api-limit-upped/</link>
		<comments>http://www.nearby.org.uk/blog/2008/02/28/geohash-converter-api-limit-upped/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 23:01:37 +0000</pubDate>
		<dc:creator>Barry</dc:creator>
				<category><![CDATA[API]]></category>
		<category><![CDATA[Coordinate Converter]]></category>
		<category><![CDATA[Experimental]]></category>
		<category><![CDATA[geo]]></category>
		<category><![CDATA[geohash]]></category>
		<category><![CDATA[Nearby]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[Web Services]]></category>

		<guid isPermaLink="false">http://www.nearby.org.uk/blog/2008/02/28/geohash-converter-api-limit-upped/</guid>
		<description><![CDATA[Recently geohash.org was released; the premise: short easy links that encode a location. The website offers instant conversion, but as the algorithm is Public Domain, Lordelph was quick to implement a php class, and I could quickly add the conversion to my existing conversion API. Convert a postcode to geohash anyone? Updating the documentation noticed [...]]]></description>
			<content:encoded><![CDATA[<p>Recently <a href="http://geohash.org/">geohash.org</a> was released; the premise: short easy links that encode a location. The website offers instant conversion, but as the <a href="http://en.wikipedia.org/wiki/Geohash">algorithm</a> is Public Domain, <a href="http://blog.dixo.net/">Lordelph</a> was quick to implement a <a href="http://blog.dixo.net/2008/02/28/geohash-php-class/">php class</a>, and I could quickly <strong>add the conversion to my existing <a href="http://www.nearby.org.uk/api/convert-help.php">conversion API</a>. </strong>Convert a postcode to geohash anyone?</p>
<p>Updating the <a href="http://www.nearby.org.uk/api/convert-help.php">documentation</a> noticed the API was last updated in 2005 &#8211; gulp, how time flies! Anyway as a celebration have upped the throttling on the API, <strong>now three times the previous limit.</strong> Running on much improved hardware than when it was launched so maybe the limit can be tweaked even more, will run some analysis of its impact &#8211; it already seems the API is a minor part of the overall load on the server &#8211; particularly against the Google Earth layers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.nearby.org.uk/blog/2008/02/28/geohash-converter-api-limit-upped/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

