<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A Handful of Google Hacks&#8230;</title>
	<atom:link href="http://blog.ouseful.info/2012/01/03/a-handful-of-google-hacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ouseful.info/2012/01/03/a-handful-of-google-hacks/</link>
	<description>Trying to find useful things to do with emerging technologies in open education</description>
	<lastBuildDate>Mon, 20 May 2013 07:57:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: CFHE12 Analysis: Summary of Twitter activity JISC CETIS MASHe</title>
		<link>http://blog.ouseful.info/2012/01/03/a-handful-of-google-hacks/#comment-28904</link>
		<dc:creator><![CDATA[CFHE12 Analysis: Summary of Twitter activity JISC CETIS MASHe]]></dc:creator>
		<pubDate>Mon, 26 Nov 2012 11:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ouseful.info/?p=6719#comment-28904</guid>
		<description><![CDATA[[...] by extracting location recorded in twitter account profile and generating geo-coordinates using recipe here. Locations were extracted for 404 accounts. Co-ordinates were uploaded to GeoCommons and analysed [...]]]></description>
		<content:encoded><![CDATA[<p>[...] by extracting location recorded in twitter account profile and generating geo-coordinates using recipe here. Locations were extracted for 404 accounts. Co-ordinates were uploaded to GeoCommons and analysed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Automagic Creation of a Map of #opened12 Attendees</title>
		<link>http://blog.ouseful.info/2012/01/03/a-handful-of-google-hacks/#comment-27835</link>
		<dc:creator><![CDATA[Automagic Creation of a Map of #opened12 Attendees]]></dc:creator>
		<pubDate>Sun, 30 Sep 2012 20:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ouseful.info/?p=6719#comment-27835</guid>
		<description><![CDATA[[...] in the form of Tony Hirst (who I knew would know the answer) and Alec Couros. Tony pointed me to a post he had written earlier this year that highlighted the Google doc function =ImportData. By using that function and concatenating the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] in the form of Tony Hirst (who I knew would know the answer) and Alec Couros. Tony pointed me to a post he had written earlier this year that highlighted the Google doc function =ImportData. By using that function and concatenating the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Hirst</title>
		<link>http://blog.ouseful.info/2012/01/03/a-handful-of-google-hacks/#comment-19662</link>
		<dc:creator><![CDATA[Tony Hirst]]></dc:creator>
		<pubDate>Wed, 08 Feb 2012 23:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ouseful.info/?p=6719#comment-19662</guid>
		<description><![CDATA[@tom I seem to remember seeing something in a slightly different context about the new long form Twitter IDs causing problems.. I seem to remember there was some way of getting IDs back as strings rather than numerics for cases where long numbers couldn&#039;t be handled...? This maybe? https://groups.google.com/forum/?fromgroups#!topic/twitter-api-announce/ccJeIN3T4_A]]></description>
		<content:encoded><![CDATA[<p>@tom I seem to remember seeing something in a slightly different context about the new long form Twitter IDs causing problems.. I seem to remember there was some way of getting IDs back as strings rather than numerics for cases where long numbers couldn&#8217;t be handled&#8230;? This maybe? <a href="https://groups.google.com/forum/?fromgroups#!topic/twitter-api-announce/ccJeIN3T4_A" rel="nofollow">https://groups.google.com/forum/?fromgroups#!topic/twitter-api-announce/ccJeIN3T4_A</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Szekeres (@tomszekeres)</title>
		<link>http://blog.ouseful.info/2012/01/03/a-handful-of-google-hacks/#comment-19644</link>
		<dc:creator><![CDATA[Tom Szekeres (@tomszekeres)]]></dc:creator>
		<pubDate>Wed, 08 Feb 2012 16:55:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ouseful.info/?p=6719#comment-19644</guid>
		<description><![CDATA[Bizarrely, when I&#039;ve used Twitter Search, Google Refine seems to round up both id and str_id e.g. &quot;166937349609364481&quot; becomes 166937359609364480, whether quoted or unquoted - does this happen for you? Seems to be related to the length of the string (when it&#039;s over 16 characters long).]]></description>
		<content:encoded><![CDATA[<p>Bizarrely, when I&#8217;ve used Twitter Search, Google Refine seems to round up both id and str_id e.g. &#8220;166937349609364481&#8243; becomes 166937359609364480, whether quoted or unquoted &#8211; does this happen for you? Seems to be related to the length of the string (when it&#8217;s over 16 characters long).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OER Visualisation Project: Maps, Maps, Maps, Maps [day 20] &#8211; MASHe</title>
		<link>http://blog.ouseful.info/2012/01/03/a-handful-of-google-hacks/#comment-18868</link>
		<dc:creator><![CDATA[OER Visualisation Project: Maps, Maps, Maps, Maps [day 20] &#8211; MASHe]]></dc:creator>
		<pubDate>Tue, 10 Jan 2012 17:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ouseful.info/?p=6719#comment-18868</guid>
		<description><![CDATA[[...] geo data for the 57 unresolved Phase 1 &amp; 2 projects was a 3 stage process:Use the Google Maps hack recently rediscovered by Tony Hirst to get co-ordinates from a search. You can see the remnants of this here in cell U56 (Google [...]]]></description>
		<content:encoded><![CDATA[<p>[...] geo data for the 57 unresolved Phase 1 &amp; 2 projects was a 3 stage process:Use the Google Maps hack recently rediscovered by Tony Hirst to get co-ordinates from a search. You can see the remnants of this here in cell U56 (Google [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
