<?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: PostGIS 1.1.1 Has Been Released</title>
	<atom:link href="http://spatiallyadjusted.com/2006/01/23/postgis-111-has-been-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://spatiallyadjusted.com/2006/01/23/postgis-111-has-been-released/</link>
	<description>Geospatial Technology, Web Mapping and Spatial Services</description>
	<lastBuildDate>Fri, 10 Feb 2012 19:09:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: dylan</title>
		<link>http://spatiallyadjusted.com/2006/01/23/postgis-111-has-been-released/#comment-1037</link>
		<dc:creator><![CDATA[dylan]]></dc:creator>
		<pubDate>Wed, 01 Feb 2006 07:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://zhun.pair.com/spatiall/blog/?p=527#comment-1037</guid>
		<description><![CDATA[I would have to agree with the above comment- what business does a database really have storing a giant blob of raster data when it can be more efficiently stored in a file. Then again I am not operating in a &quot;corporate GIS&quot; environment, whatever that may really be. I have to say though, that this post was one more reminder of downloading postgis 1.1.1. Thanks!]]></description>
		<content:encoded><![CDATA[<p>I would have to agree with the above comment- what business does a database really have storing a giant blob of raster data when it can be more efficiently stored in a file. Then again I am not operating in a &#8220;corporate GIS&#8221; environment, whatever that may really be. I have to say though, that this post was one more reminder of downloading postgis 1.1.1. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Ramsey</title>
		<link>http://spatiallyadjusted.com/2006/01/23/postgis-111-has-been-released/#comment-1036</link>
		<dc:creator><![CDATA[Paul Ramsey]]></dc:creator>
		<pubDate>Tue, 24 Jan 2006 06:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://zhun.pair.com/spatiall/blog/?p=527#comment-1036</guid>
		<description><![CDATA[&quot;Still waiting...&quot; ? You could be waiting a long time if you don&#039;t talk about the issues on the users list.  For the record, neither &quot;locking&quot; or &quot;multi-versioning&quot; have been mentioned on the list, with the possible exception of long transaction locking support for Geoserver WFS, for which there is an implementation.  The issue that receives contant traction on the list (to my chagrin) is raster support.  I would personally do topology before doing any of the above.]]></description>
		<content:encoded><![CDATA[<p>&#8220;Still waiting&#8230;&#8221; ? You could be waiting a long time if you don&#8217;t talk about the issues on the users list.  For the record, neither &#8220;locking&#8221; or &#8220;multi-versioning&#8221; have been mentioned on the list, with the possible exception of long transaction locking support for Geoserver WFS, for which there is an implementation.  The issue that receives contant traction on the list (to my chagrin) is raster support.  I would personally do topology before doing any of the above.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

