<?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: Better Know a GeoCommons Feature – GeoJoin</title>
	<atom:link href="http://blog.geoiq.com/2010/02/09/better-know-a-geocommons-feature-%e2%80%93-geojoin/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.geoiq.com/2010/02/09/better-know-a-geocommons-feature-%e2%80%93-geojoin/</link>
	<description>News and updates from GeoIQ</description>
	<lastBuildDate>Wed, 23 May 2012 08:01:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Better Know a GeoCommons Feature – GeoJoin (Fortius One) &#171; Kelso&#8217;s Corner</title>
		<link>http://blog.geoiq.com/2010/02/09/better-know-a-geocommons-feature-%e2%80%93-geojoin/#comment-1196</link>
		<dc:creator>Better Know a GeoCommons Feature – GeoJoin (Fortius One) &#171; Kelso&#8217;s Corner</dc:creator>
		<pubDate>Tue, 23 Feb 2010 11:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/?p=1251#comment-1196</guid>
		<description>[...] Republished from Fortius One. February 9th, 2010 by Kevin Burke [...]</description>
		<content:encoded><![CDATA[<p>[...] Republished from Fortius One. February 9th, 2010 by Kevin Burke [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pslarkin</title>
		<link>http://blog.geoiq.com/2010/02/09/better-know-a-geocommons-feature-%e2%80%93-geojoin/#comment-1195</link>
		<dc:creator>pslarkin</dc:creator>
		<pubDate>Wed, 10 Feb 2010 21:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/?p=1251#comment-1195</guid>
		<description>This is awesome.</description>
		<content:encoded><![CDATA[<p>This is awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kate Chapman</title>
		<link>http://blog.geoiq.com/2010/02/09/better-know-a-geocommons-feature-%e2%80%93-geojoin/#comment-1194</link>
		<dc:creator>Kate Chapman</dc:creator>
		<pubDate>Wed, 10 Feb 2010 18:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/?p=1251#comment-1194</guid>
		<description>nicheVC,

If technically inclined you could actually do that with the GeoCommons API.  http://github.com/geocommons/api/

Thanks for the idea!</description>
		<content:encoded><![CDATA[<p>nicheVC,</p>
<p>If technically inclined you could actually do that with the GeoCommons API.  <a href="http://github.com/geocommons/api/" rel="nofollow">http://github.com/geocommons/api/</a></p>
<p>Thanks for the idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nicheVC</title>
		<link>http://blog.geoiq.com/2010/02/09/better-know-a-geocommons-feature-%e2%80%93-geojoin/#comment-1193</link>
		<dc:creator>nicheVC</dc:creator>
		<pubDate>Wed, 10 Feb 2010 00:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fortiusone.com/?p=1251#comment-1193</guid>
		<description>What about an automated feature (TripIt-like) that allows a user to email a csv file or data set in the text of email that might analyze and produce a visual effect in a proprietary account or openly within GeoCommons?</description>
		<content:encoded><![CDATA[<p>What about an automated feature (TripIt-like) that allows a user to email a csv file or data set in the text of email that might analyze and produce a visual effect in a proprietary account or openly within GeoCommons?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

