<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Raster geodatabase performance in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/raster-geodatabase-performance/m-p/766865#M704</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everybody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking for success stories about using an enterprise geodatabase (postgres) to store raster data. I mean not just for read-only access but also to write rasters out of geoprocessing tools (python, modelBulder, etc) directly to the enterprise gdb. I'm aware this is not a common approach, but I'm trying find all possible alternatives.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any performance tips or tuning options that would allow the gdb to store and query the rasters with a performance somehow similar to what would be exprerienced using file gdbs to store the data?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Feb 2018 21:27:02 GMT</pubDate>
    <dc:creator>Sergio_Galindo</dc:creator>
    <dc:date>2018-02-19T21:27:02Z</dc:date>
    <item>
      <title>Raster geodatabase performance</title>
      <link>https://community.esri.com/t5/geodatabase-questions/raster-geodatabase-performance/m-p/766865#M704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everybody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking for success stories about using an enterprise geodatabase (postgres) to store raster data. I mean not just for read-only access but also to write rasters out of geoprocessing tools (python, modelBulder, etc) directly to the enterprise gdb. I'm aware this is not a common approach, but I'm trying find all possible alternatives.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any performance tips or tuning options that would allow the gdb to store and query the rasters with a performance somehow similar to what would be exprerienced using file gdbs to store the data?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Feb 2018 21:27:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/raster-geodatabase-performance/m-p/766865#M704</guid>
      <dc:creator>Sergio_Galindo</dc:creator>
      <dc:date>2018-02-19T21:27:02Z</dc:date>
    </item>
  </channel>
</rss>

