<?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: OSGeo Tiling Spec</title>
	<atom:link href="http://blog.webmapper.com.au/2006/10/28/osgeo-tiling-spec/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.webmapper.com.au/2006/10/28/osgeo-tiling-spec/</link>
	<description>Not another GIS blog</description>
	<lastBuildDate>Wed, 02 Jun 2010 04:13:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: I take your S3 and raise you an EC2 &#171; Into The Pudding</title>
		<link>http://blog.webmapper.com.au/2006/10/28/osgeo-tiling-spec/comment-page-1/#comment-2403</link>
		<dc:creator>I take your S3 and raise you an EC2 &#171; Into The Pudding</dc:creator>
		<pubDate>Mon, 30 Oct 2006 03:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://chris.narx.net/2006/10/28/osgeo-tiling-spec/#comment-2403</guid>
		<description>[...] Just read Chris&#8217;s post about using Amazon&#8217;s S3 as a home for caches. The Amazon service I&#8217;ve actually been contemplating for tiling purposes is actually their Elastic Compute Cloud (EC2) . But before we get in to it, a bit on S3 and tiles. I&#8217;d actually still like the distributed peer to peer tile cache, as I talked about in my post on geodata distribution. But it makes a lot of sense to bootstrap existing services on the way to get there. S3 could certainaly help out as a &#8216;node of last resort&#8217; - it&#8217;s nice to know that the tiles will definitely be available somewhere, if the cache isn&#8217;t yet popular enough to be distributed to someone else&#8217;s p2p cache on your more local network. I agree that bittorrent and coral aren&#8217;t up to snuff, but I do believe that distributing mapping tiles will work as p2p technology evolves. But first we have to get our act together with tiling in the geospatial community, so we can go with something concrete to the p2p guys. Which is why I&#8217;m excited about the work being done to figure this out. [...]</description>
		<content:encoded><![CDATA[<p>[...] Just read Chris&#8217;s post about using Amazon&#8217;s S3 as a home for caches. The Amazon service I&#8217;ve actually been contemplating for tiling purposes is actually their Elastic Compute Cloud (EC2) . But before we get in to it, a bit on S3 and tiles. I&#8217;d actually still like the distributed peer to peer tile cache, as I talked about in my post on geodata distribution. But it makes a lot of sense to bootstrap existing services on the way to get there. S3 could certainaly help out as a &#8216;node of last resort&#8217; &#8211; it&#8217;s nice to know that the tiles will definitely be available somewhere, if the cache isn&#8217;t yet popular enough to be distributed to someone else&#8217;s p2p cache on your more local network. I agree that bittorrent and coral aren&#8217;t up to snuff, but I do believe that distributing mapping tiles will work as p2p technology evolves. But first we have to get our act together with tiling in the geospatial community, so we can go with something concrete to the p2p guys. Which is why I&#8217;m excited about the work being done to figure this out. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Tweedie</title>
		<link>http://blog.webmapper.com.au/2006/10/28/osgeo-tiling-spec/comment-page-1/#comment-2376</link>
		<dc:creator>Chris Tweedie</dc:creator>
		<pubDate>Sun, 29 Oct 2006 02:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://chris.narx.net/2006/10/28/osgeo-tiling-spec/#comment-2376</guid>
		<description>Yeah you&#039;re right.

There certainly isnt anything commercially available that can compete with those prices. 

The only thing i failed to factor into the calculations is obviously the 2 way cost of someone actually uploading 1.4tb of data. In the scheme of things though, the total is still going to be very small.</description>
		<content:encoded><![CDATA[<p>Yeah you&#8217;re right.</p>
<p>There certainly isnt anything commercially available that can compete with those prices. </p>
<p>The only thing i failed to factor into the calculations is obviously the 2 way cost of someone actually uploading 1.4tb of data. In the scheme of things though, the total is still going to be very small.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GeoMullah</title>
		<link>http://blog.webmapper.com.au/2006/10/28/osgeo-tiling-spec/comment-page-1/#comment-2363</link>
		<dc:creator>GeoMullah</dc:creator>
		<pubDate>Sat, 28 Oct 2006 11:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://chris.narx.net/2006/10/28/osgeo-tiling-spec/#comment-2363</guid>
		<description>Why doesn&#039;t NASA or USGS pay to cache the tiles with S3?  The cost would definitely be a drop in their bucket.</description>
		<content:encoded><![CDATA[<p>Why doesn&#8217;t NASA or USGS pay to cache the tiles with S3?  The cost would definitely be a drop in their bucket.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
