<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.esri.com/Dev/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Should I load my raster data into a geodatabase?</title><link>http://blogs.esri.com/Dev/blogs/geodatabase/archive/2008/08/14/Should-I-load-my-raster-data-into-a-geodatabase_3F00_.aspx</link><description>I noticed there were a lot of raster related questions at the user conference this year. People mainly wanted to know the advantages of loading raster data into a geodatabase, and generally how to manage their raster data. So I talked to Simon Woo on</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Debug Build: 61120.2)</generator><item><title>Geoprocessing</title><link>http://blogs.esri.com/Dev/blogs/geodatabase/archive/2008/08/14/Should-I-load-my-raster-data-into-a-geodatabase_3F00_.aspx#2480</link><pubDate>Fri, 15 Aug 2008 04:19:11 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:2480</guid><dc:creator>majgis</dc:creator><description>&lt;p&gt;I heard at the user conference that geoprocessing operations can be tediously slow on geodatabase rasters. &amp;nbsp;It would be helpful if you included details on geoprocessing in this comparison.&lt;/p&gt;
</description></item><item><title>re: Should I load my raster data into a geodatabase?</title><link>http://blogs.esri.com/Dev/blogs/geodatabase/archive/2008/08/14/Should-I-load-my-raster-data-into-a-geodatabase_3F00_.aspx#2483</link><pubDate>Sat, 16 Aug 2008 16:54:48 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:2483</guid><dc:creator>iKeepSmile</dc:creator><description>&lt;p&gt;my company has 1TB/year raster data. It's very hard to decide whether to store it in a ArcSDE database or file format. I want to know is there any problem to manager these huge amount of data in a sde database, if the raster data size exceed 10TB.&lt;/p&gt;
</description></item><item><title>re: majgis's question</title><link>http://blogs.esri.com/Dev/blogs/geodatabase/archive/2008/08/14/Should-I-load-my-raster-data-into-a-geodatabase_3F00_.aspx#2487</link><pubDate>Tue, 19 Aug 2008 17:19:34 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:2487</guid><dc:creator>simo3919</dc:creator><description>&lt;p&gt;&amp;quot;I heard at the user conference that geoprocessing operations can be tediously slow on geodatabase rasters. &amp;nbsp;It would be helpful if you included details on geoprocessing in this comparison.&amp;quot;&lt;/p&gt;
&lt;p&gt;----------------------------------------------&lt;/p&gt;
&lt;p&gt;In general, geoprocessing in a geodatabase should be relatively similar processing times as in a file based system. &amp;nbsp;There are a few exceptions to this.&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;1) Mosaicking tends to be much faster in a geodatabase (as seen in a previous blog post).&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;2) Applying compression will increase the time it take to write a compressed raster to a geodatabase.&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;3) Any Spatial Analyst or 3D Analyst tool will take longer, since it is outputing everything to GRID and then converting to a geodatabase format.&lt;/p&gt;
&lt;p&gt;Simon W.&lt;/p&gt;
&lt;p&gt;ESRI - Team Raster&lt;/p&gt;
</description></item><item><title>re: iKeepSmile's question</title><link>http://blogs.esri.com/Dev/blogs/geodatabase/archive/2008/08/14/Should-I-load-my-raster-data-into-a-geodatabase_3F00_.aspx#2488</link><pubDate>Tue, 19 Aug 2008 17:23:40 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:2488</guid><dc:creator>simo3919</dc:creator><description>&lt;p&gt;I want to know is there any problem to manage these huge amounts of data in an sde database, if the raster data size exceed 10TB.&lt;/p&gt;
&lt;p&gt;--------------------------------------------&lt;/p&gt;
&lt;p&gt;This is a very common question, and it is very complicated to answer since it is on a case to case interpretation on whether your project is suited for the geodatabase. &amp;nbsp;We will come up with a more comprehesive decison tree and post it in an upcoming blog.&lt;/p&gt;
&lt;p&gt;In terms of the amount of raster data, in house we have compiled ArcSDE databases with at least one terabyte of raster data. Some of our business partners have compiled ArcSDE databases of over 17,000 images totaling over 22 terabytes. So it is definitely possible to manage these large amounts of data.&lt;/p&gt;
&lt;p&gt;Simon Woo&lt;/p&gt;
&lt;p&gt;ESRI - Team Raster&lt;/p&gt;
</description></item><item><title>Compare Image Server</title><link>http://blogs.esri.com/Dev/blogs/geodatabase/archive/2008/08/14/Should-I-load-my-raster-data-into-a-geodatabase_3F00_.aspx#2520</link><pubDate>Sun, 24 Aug 2008 11:34:39 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:2520</guid><dc:creator>mody</dc:creator><description>&lt;p&gt;We (and some of our users) will be very happy if you can compare to Image Server and not to just images on disk.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Mody Buchbinder&lt;/p&gt;
&lt;p&gt;Systematics, Israel&lt;/p&gt;
</description></item><item><title>re: Should I load my raster data into a geodatabase?</title><link>http://blogs.esri.com/Dev/blogs/geodatabase/archive/2008/08/14/Should-I-load-my-raster-data-into-a-geodatabase_3F00_.aspx#2541</link><pubDate>Tue, 26 Aug 2008 21:15:56 GMT</pubDate><guid isPermaLink="false">b60b3f0a-e2bd-4be5-8a18-822c697649ab:2541</guid><dc:creator>JonMurphy</dc:creator><description>&lt;p&gt;Mody, &lt;/p&gt;
&lt;p&gt;We've been getting feedback on the blog and elsewhere about image server. I'll be getting a post together and putting it up on the blog shortly which should help with your image server questions.&lt;/p&gt;
&lt;p&gt;Jonathan Murphy&lt;/p&gt;
</description></item></channel></rss>