<?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>idea File geodatabase query layers in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idi-p/1237538</link>
    <description>&lt;P&gt;It would be very helpful if we could create query layers on file geodatabase data.&lt;/P&gt;&lt;P&gt;Even though FGDBs don't have a SQL spatial type like ST_GEOMETRY, it would still help to use non-spatial SQL in full blown SQL queries on file geodatabases.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Dec 2023 20:24:01 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2023-12-11T20:24:01Z</dc:date>
    <item>
      <title>File geodatabase query layers</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idi-p/1237538</link>
      <description>&lt;P&gt;It would be very helpful if we could create query layers on file geodatabase data.&lt;/P&gt;&lt;P&gt;Even though FGDBs don't have a SQL spatial type like ST_GEOMETRY, it would still help to use non-spatial SQL in full blown SQL queries on file geodatabases.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Dec 2023 20:24:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idi-p/1237538</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2023-12-11T20:24:01Z</dc:date>
    </item>
    <item>
      <title>Re: Support query layers on file geodatabases</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1237757#M22383</link>
      <description>&lt;P&gt;Hi Bud, this is like your other idea for the equivalent functionality for mobile geodatabases, Create Database View will do the job for you.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Dec 2022 14:26:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1237757#M22383</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2022-12-05T14:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: Support query layers on file geodatabases</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1237836#M22386</link>
      <description>&lt;P&gt;A comment from&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/1371"&gt;@JoshuaBixby&lt;/a&gt;&amp;nbsp;from a related post (&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/mobile-geodatabase-query-layers/idc-p/1237769" target="_self"&gt;Mobile geodatabase query layers&lt;/A&gt;) is relevant here too:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;Although a Query Layer and Database View could give the same result within a map, the implementation is different.&amp;nbsp; I think the difference is enough to warrant keeping this idea.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;My thoughts are: Query layers are useful for temporary or one-off cases where you don’t want to create an object in the database.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Dec 2022 09:07:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1237836#M22386</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-12-06T09:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: File geodatabase query layers</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1271619#M24014</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Related: &lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/aggregation-layer-file-and-mobile-geodatabases/idi-p/1271616" target="_self"&gt;Aggregation Layer — File and mobile geodatabases&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="http://virtual%20attributes%20(ad%20hoc)/" target="_self" rel="nofollow noopener noreferrer"&gt;Virtual Attributes (ad hoc)&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 11 Dec 2023 20:32:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1271619#M24014</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2023-12-11T20:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: File geodatabase query layers</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1325481#M26152</link>
      <description>&lt;P&gt;This would be a game changer. Query layers are an amazing tool in our arsenal, but being limited to only enterprise GDBs severely cuts down on our possible uses, given that a lot of data lives in file geodatabases.&lt;/P&gt;&lt;P&gt;Especially for users without enterprise GDBs, not being able to use query layers is really limiting.&lt;/P&gt;&lt;P&gt;Like JoshuaBixby and Bud say, although the end result is the same, the implementation matters. Layers are great because they ultimately don't really take up any space. Creating a view (which is also very cool) adds yet another item to clutter the GDB, and is a more permanent solution for what could be a throwaway question.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another great thing about query layers (and views) is that they can get around several Arcade limitations, such as &lt;A href="https://community.esri.com/t5/arcgis-online-ideas/have-arcade-expressions-become-real-fields-on/idi-p/1074182" target="_self"&gt;exporting the value returned by the expression as a field&lt;/A&gt;, or symbolizing &lt;A href="https://community.esri.com/t5/arcgis-online-ideas/update-arcade-profiles-to-include-visualization/idi-p/1243517" target="_blank" rel="noopener"&gt;based&lt;/A&gt; on a &lt;A href="https://community.esri.com/t5/developers-ideas/enable-arcade-functions-for-labels-and-symbols/idi-p/1223708" target="_blank" rel="noopener"&gt;related table&lt;/A&gt;. Being able to use a computed columns with a file geodatabase (or mobile) would open up a world of possibilities.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Sep 2023 16:43:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1325481#M26152</guid>
      <dc:creator>AlfredBaldenweck</dc:creator>
      <dc:date>2023-09-05T16:43:40Z</dc:date>
    </item>
    <item>
      <title>Re: File geodatabase query layers</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1490480#M30635</link>
      <description>&lt;P&gt;A use case for fgdb query layers:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490469/highlight/true#M84476" target="_self"&gt;Control schema locking behavior in ArcGIS Pro&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 13:25:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idc-p/1490480#M30635</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-06-12T13:25:31Z</dc:date>
    </item>
  </channel>
</rss>

