<?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 Virtual Attribute Summary Tables (VASTs) in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idi-p/936196</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Related enhancement request:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;It would be a great benefit to ESRI if&amp;nbsp;ArcGIS Pro&amp;nbsp;could readily do the following: Allow users to apply live queries to data stores containing detail records and view &lt;STRONG&gt;aggregated&lt;/STRONG&gt; results through the lens of whatever polygon geography is in the view, OR create a view on the data that can be associated and viewed through any polygon layer readily without requiring the data to be stored with the geography (unless you choose to persist it that way).&lt;/P&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;LI style="margin-left: 0in;"&gt;SQL&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;Cloud data stores&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;JSON&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;Text&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;Excel&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This would break away from the tight coupling of feature and static attributes and deliver a Tableau-like ease of use.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SCENARIO:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;A seasoned GIS analyst enters into a boardroom with project containing a set of tables/charts etc.&lt;/P&gt;&lt;P&gt;An executive asks a question about a distribution of target customer sales that, if the analyst had anticipated it, they maybe could have created some semi-prototypical daisy-chained workflow to generate a summary data table to be joined back into their target layer in a form that would support answering that question and visualizing it on a map… BUT by the time that workflow is executed and the results generated, three similar questions have been asked with the only change being the level of detail.&amp;nbsp; With the limited time available to everyone, the executives are left wanting and the analyst is frustrated by the speed at which they can generate answers and perspectives on the data.&lt;/P&gt;&lt;P&gt;Due to the meeting, the software is seen as complex, and even though the analyst understand the power of the GIS tools, the platform is is seen as abstract, complicated and time consuming, and everyone (including the analyst) is thinking “can’t we explore these questions much more quickly and easily in Tableau, or PowerBI?” – The question being asked is a &lt;EM&gt;FAIL&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wouldn’t it be nice for the analyst to go into the meeting with:&lt;/P&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;LI style="margin-left: 0in;"&gt;3 layers of geography and&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;one connection to a data source containing the up-to-the-minute list of target customer sales records…&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;and, expediently… without persisting another byte of attribute data, view the aggregated results through each of those 3 layers on-the-fly… &amp;nbsp;&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;then spontaneously add a 4&lt;SUP&gt;th&lt;/SUP&gt; and 5&lt;SUP&gt;th&lt;/SUP&gt; to satisfy another executive’s curiosity for viewing through their team’s field-operations geography&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;then look at a live virtual attribute summary table (a.k.a. VIEW)… and graph it&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;THEN, optionally, persist that view of the data as a layer in that consumable form to be more broadly used in a formal web-map/app?&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;EVEN BETTER?&amp;nbsp; Allow connecting multiple virtual attribute summary tables (VASTs) to each layer with multiple Tables to segment Topics/Themes (Customer Sales, Demographics, Competitors, etc).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This type of scenario is very typical (not at all atypical) of a commercial business environment’s.&amp;nbsp; The need for analytic speed is a core demand trait for modern businesses.&amp;nbsp; Let me know if you have any further clarifications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Speaking ArcGIS Pro: [this is a baseline functionality... &lt;/STRONG&gt;it's akin to creating a SQL view&lt;STRONG&gt;]&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If I already have a &lt;STRONG&gt;Zip Codes Layer&lt;/STRONG&gt; in my ArcGIS Pro project, and I then add data with a zip code field:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Let user click to choose to create a &lt;EM&gt;&lt;STRONG&gt;VAST Relationship&lt;/STRONG&gt;&lt;/EM&gt; between my layer and a data source.&lt;/LI&gt;&lt;LI&gt;Let user point to&amp;nbsp;that&amp;nbsp;data source (e.g. a SQL Table, csv, delimited txt, excel file (sheet), etc.)&lt;/LI&gt;&lt;LI&gt;By default, try to auto pick the ID field(s) to join on. In this example, ArcGIS would simply look for columns named "*zip*" or "*post*" and allow user to verify/correct the auto selected column(s) for the target layer and the "joining" data.&lt;/LI&gt;&lt;LI&gt;Let user choose all or some of the columns from the data source to include in the zip code level (in this example) aggregation of the data as well as the column summary methods to apply&amp;nbsp;&lt;STRONG&gt;(first, last, mode, top x, sum, min, max, average, median, count &lt;/STRONG&gt;&lt;EM&gt;(the idea is to mimic &lt;STRONG&gt;SQL group by&lt;/STRONG&gt; options, and maybe expand those with a few more exotic aggregation options)&lt;/EM&gt;&lt;STRONG&gt;).&amp;nbsp; &lt;/STRONG&gt;With some of these options a &lt;STRONG&gt;sort sub-option&lt;/STRONG&gt; may need to be/could be presented to the user.&lt;/LI&gt;&lt;LI&gt;Let the user apply the equivalent of a SQL where clause.&lt;/LI&gt;&lt;LI&gt;The&amp;nbsp;functionality would permit&amp;nbsp;the user to summarize the data records (customers, stores, households, students, zip code tabular data)&amp;nbsp;up to&amp;nbsp;the entity level of the layer (in this case zip codes)... &lt;STRONG&gt;BUT WITHOUT REQUIRING CREATION OF A PERSISTED DATA SET UP FRONT &lt;/STRONG&gt;(it's a VIRTUAL attribute table associated with the layer)&lt;/LI&gt;&lt;LI&gt;Once created the user can have a regular, persisted attribute table AND&amp;nbsp;the newly created VAST.&lt;/LI&gt;&lt;LI&gt;Give the user the choice at any time to persist the VAST (append to attribute table columns, replace/update attribute table columns, replace/update attribute table).&lt;/LI&gt;&lt;LI&gt;Give the user the option to bring in a States layer, and &lt;STRONG&gt;re-use &amp;amp; modify&lt;/STRONG&gt; the VAST definition, changing the ID field from zip to State.&lt;/LI&gt;&lt;LI&gt;Optimize it for speed.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This &lt;STRONG&gt;SCENARIO&lt;/STRONG&gt; I describe earlier is meant to convey&amp;nbsp;&lt;SPAN style="font-size: 11.0pt;"&gt;how this capability will be beneficial for many organizations.&amp;nbsp; In particular, it will be useful in many variants of the story I've laid out.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;I'm quite&amp;nbsp;confident that this would be seen as a cool evolution of ESRI's GIS platform.&amp;nbsp; The ease of use of this functionality of "&lt;STRONG&gt;quickly&lt;/STRONG&gt; &lt;STRONG&gt;viewing&lt;/STRONG&gt; a data table through the lens of geography" would permit GIS to better compete against the non-GIS tools (Tableau, Excel, PowerBI, etc.).&amp;nbsp; Help that analyst demonstrate the power of where.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Mar 2020 18:33:28 GMT</pubDate>
    <dc:creator>AngeloTaylor2</dc:creator>
    <dc:date>2020-03-06T18:33:28Z</dc:date>
    <item>
      <title>Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idi-p/936196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Related enhancement request:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;It would be a great benefit to ESRI if&amp;nbsp;ArcGIS Pro&amp;nbsp;could readily do the following: Allow users to apply live queries to data stores containing detail records and view &lt;STRONG&gt;aggregated&lt;/STRONG&gt; results through the lens of whatever polygon geography is in the view, OR create a view on the data that can be associated and viewed through any polygon layer readily without requiring the data to be stored with the geography (unless you choose to persist it that way).&lt;/P&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;LI style="margin-left: 0in;"&gt;SQL&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;Cloud data stores&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;JSON&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;Text&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;Excel&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This would break away from the tight coupling of feature and static attributes and deliver a Tableau-like ease of use.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SCENARIO:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;A seasoned GIS analyst enters into a boardroom with project containing a set of tables/charts etc.&lt;/P&gt;&lt;P&gt;An executive asks a question about a distribution of target customer sales that, if the analyst had anticipated it, they maybe could have created some semi-prototypical daisy-chained workflow to generate a summary data table to be joined back into their target layer in a form that would support answering that question and visualizing it on a map… BUT by the time that workflow is executed and the results generated, three similar questions have been asked with the only change being the level of detail.&amp;nbsp; With the limited time available to everyone, the executives are left wanting and the analyst is frustrated by the speed at which they can generate answers and perspectives on the data.&lt;/P&gt;&lt;P&gt;Due to the meeting, the software is seen as complex, and even though the analyst understand the power of the GIS tools, the platform is is seen as abstract, complicated and time consuming, and everyone (including the analyst) is thinking “can’t we explore these questions much more quickly and easily in Tableau, or PowerBI?” – The question being asked is a &lt;EM&gt;FAIL&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wouldn’t it be nice for the analyst to go into the meeting with:&lt;/P&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;LI style="margin-left: 0in;"&gt;3 layers of geography and&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;one connection to a data source containing the up-to-the-minute list of target customer sales records…&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;and, expediently… without persisting another byte of attribute data, view the aggregated results through each of those 3 layers on-the-fly… &amp;nbsp;&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;then spontaneously add a 4&lt;SUP&gt;th&lt;/SUP&gt; and 5&lt;SUP&gt;th&lt;/SUP&gt; to satisfy another executive’s curiosity for viewing through their team’s field-operations geography&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;then look at a live virtual attribute summary table (a.k.a. VIEW)… and graph it&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;THEN, optionally, persist that view of the data as a layer in that consumable form to be more broadly used in a formal web-map/app?&lt;/LI&gt;&lt;LI style="margin-left: 0in;"&gt;EVEN BETTER?&amp;nbsp; Allow connecting multiple virtual attribute summary tables (VASTs) to each layer with multiple Tables to segment Topics/Themes (Customer Sales, Demographics, Competitors, etc).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This type of scenario is very typical (not at all atypical) of a commercial business environment’s.&amp;nbsp; The need for analytic speed is a core demand trait for modern businesses.&amp;nbsp; Let me know if you have any further clarifications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Speaking ArcGIS Pro: [this is a baseline functionality... &lt;/STRONG&gt;it's akin to creating a SQL view&lt;STRONG&gt;]&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If I already have a &lt;STRONG&gt;Zip Codes Layer&lt;/STRONG&gt; in my ArcGIS Pro project, and I then add data with a zip code field:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Let user click to choose to create a &lt;EM&gt;&lt;STRONG&gt;VAST Relationship&lt;/STRONG&gt;&lt;/EM&gt; between my layer and a data source.&lt;/LI&gt;&lt;LI&gt;Let user point to&amp;nbsp;that&amp;nbsp;data source (e.g. a SQL Table, csv, delimited txt, excel file (sheet), etc.)&lt;/LI&gt;&lt;LI&gt;By default, try to auto pick the ID field(s) to join on. In this example, ArcGIS would simply look for columns named "*zip*" or "*post*" and allow user to verify/correct the auto selected column(s) for the target layer and the "joining" data.&lt;/LI&gt;&lt;LI&gt;Let user choose all or some of the columns from the data source to include in the zip code level (in this example) aggregation of the data as well as the column summary methods to apply&amp;nbsp;&lt;STRONG&gt;(first, last, mode, top x, sum, min, max, average, median, count &lt;/STRONG&gt;&lt;EM&gt;(the idea is to mimic &lt;STRONG&gt;SQL group by&lt;/STRONG&gt; options, and maybe expand those with a few more exotic aggregation options)&lt;/EM&gt;&lt;STRONG&gt;).&amp;nbsp; &lt;/STRONG&gt;With some of these options a &lt;STRONG&gt;sort sub-option&lt;/STRONG&gt; may need to be/could be presented to the user.&lt;/LI&gt;&lt;LI&gt;Let the user apply the equivalent of a SQL where clause.&lt;/LI&gt;&lt;LI&gt;The&amp;nbsp;functionality would permit&amp;nbsp;the user to summarize the data records (customers, stores, households, students, zip code tabular data)&amp;nbsp;up to&amp;nbsp;the entity level of the layer (in this case zip codes)... &lt;STRONG&gt;BUT WITHOUT REQUIRING CREATION OF A PERSISTED DATA SET UP FRONT &lt;/STRONG&gt;(it's a VIRTUAL attribute table associated with the layer)&lt;/LI&gt;&lt;LI&gt;Once created the user can have a regular, persisted attribute table AND&amp;nbsp;the newly created VAST.&lt;/LI&gt;&lt;LI&gt;Give the user the choice at any time to persist the VAST (append to attribute table columns, replace/update attribute table columns, replace/update attribute table).&lt;/LI&gt;&lt;LI&gt;Give the user the option to bring in a States layer, and &lt;STRONG&gt;re-use &amp;amp; modify&lt;/STRONG&gt; the VAST definition, changing the ID field from zip to State.&lt;/LI&gt;&lt;LI&gt;Optimize it for speed.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This &lt;STRONG&gt;SCENARIO&lt;/STRONG&gt; I describe earlier is meant to convey&amp;nbsp;&lt;SPAN style="font-size: 11.0pt;"&gt;how this capability will be beneficial for many organizations.&amp;nbsp; In particular, it will be useful in many variants of the story I've laid out.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;I'm quite&amp;nbsp;confident that this would be seen as a cool evolution of ESRI's GIS platform.&amp;nbsp; The ease of use of this functionality of "&lt;STRONG&gt;quickly&lt;/STRONG&gt; &lt;STRONG&gt;viewing&lt;/STRONG&gt; a data table through the lens of geography" would permit GIS to better compete against the non-GIS tools (Tableau, Excel, PowerBI, etc.).&amp;nbsp; Help that analyst demonstrate the power of where.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Mar 2020 18:33:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idi-p/936196</guid>
      <dc:creator>AngeloTaylor2</dc:creator>
      <dc:date>2020-03-06T18:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1023304#M15070</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/364294"&gt;@AngeloTaylor2&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;did you happen to check out the following blogs? We do have capabilities in Pro similar to what you are asking for. I admit creating such layer is not an easy user experience - we are working on making the authoring such layers better.&lt;/P&gt;&lt;P&gt;Having said that I'd appreciate if you could check out this capability, and let me know what you find missing.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/dynamic-spatiotemporal-exploratory-analysis-with-aggregated-results-using-time-series-data-in-arcgis/" target="_blank"&gt;https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/dynamic-spatiotemporal-exploratory-analysis-with-aggregated-results-using-time-series-data-in-arcgis/&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/transform-aggregated-time-series-results-into-polygons-in-arcgis/" target="_blank"&gt;https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/transform-aggregated-time-series-results-into-polygons-in-arcgis/&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/dynamic-aggregate-points-within-polygon-features-for-exploratory-analysis/" target="_blank"&gt;https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/dynamic-aggregate-points-within-polygon-features-for-exploratory-analysis/&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Tanu&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2021 07:08:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1023304#M15070</guid>
      <dc:creator>TanuHoque</dc:creator>
      <dc:date>2021-02-04T07:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1390389#M28825</link>
      <description>&lt;P&gt;I just want to create a live "group by" summary statistics view, that updates as I save edits to the underlying attribute table.&amp;nbsp; e.g. sum voters by district as you are assigning voter blocks to one district or another.&amp;nbsp; (see Redistricting for ArcMap).&amp;nbsp; I believe in QGIS this is called a "virtual layer".&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 15:06:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1390389#M28825</guid>
      <dc:creator>KevinMayall</dc:creator>
      <dc:date>2024-03-04T15:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1390962#M28844</link>
      <description>&lt;P&gt;From&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/virtual-attributes-ad-hoc/idi-p/1276471/highlight/true" target="_self"&gt;Virtual Attributes (ad hoc)&lt;/A&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;I think Esri needs to keep in mind that the data analysis industry is a very fast-paced business. We can’t afford the time or messiness that comes with classic ArcGIS Pro workarounds [such as models and GP tools that produce static copies of data].&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;We need dynamic/real-time queries that can be built using the UI &lt;STRONG&gt;on the fly&amp;nbsp;in a meeting&lt;/STRONG&gt;. Kind of like pivot tables in Excel.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 14:39:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1390962#M28844</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-03-05T14:39:42Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1390975#M28845</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/8180"&gt;@KevinMayall&lt;/a&gt;&amp;nbsp;As a temporary workaround, could you create a database view or query layer?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2024 04:00:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1390975#M28845</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-03-08T04:00:58Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391031#M28846</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/351335"&gt;@Bud&lt;/a&gt;&amp;nbsp;Well, it's just a feature class in a file gdb.&amp;nbsp; I guess I could install SQL Express and move data to a SQL db, and make a query layer.&amp;nbsp; Or I have the geoprocessing history open and run the Summary Statistics tool again and again, but it closes the table window every time.&amp;nbsp; The idea still stands.&amp;nbsp; &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 11:50:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391031#M28846</guid>
      <dc:creator>KevinMayall</dc:creator>
      <dc:date>2024-03-05T11:50:26Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391101#M28848</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/8180"&gt;@KevinMayall&lt;/a&gt;&amp;nbsp;File geodatabases support database views. The main downside is FGDB SQL is limited and buggy. But you might be able to get something to work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;FGDB SQL does support GROUP BY:&amp;nbsp;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-file-gdb/sql-reporting-and-anlysis-file-geodatabases.htm" target="_self"&gt;SQL for reporting and analysis on file geodatabases&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Yes, I agree the idea is still valid. But it won’t be implemented any time soon. So a database view might be a suitable workaround as a last resort.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 14:38:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391101#M28848</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-03-05T14:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391309#M28852</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/351335"&gt;@Bud&lt;/a&gt;&amp;nbsp; Thanks!&amp;nbsp; I was able to use the Create Database View tool to create a view in the FGDB, and it does allow GROUP BY.&amp;nbsp; That's not bad.&amp;nbsp; So a simple summary count or sum by category works.&amp;nbsp; I tried some arithmetic but it had problems with '/'.&lt;/P&gt;&lt;P&gt;For workflow, you can have it open in a pane while editing the source table, and then hit the refresh button in the lower left corner to refresh the view.&amp;nbsp; You don't even have to save the table edits before refreshing the view.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 17:54:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391309#M28852</guid>
      <dc:creator>KevinMayall</dc:creator>
      <dc:date>2024-03-05T17:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391318#M28853</link>
      <description>&lt;P&gt;That's interesting that you don't need to save the table edits before refreshing the view. I wouldn't have expected that.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/fgdb-views-since-the-division-operator-isn-t/idi-p/1238086" target="_self"&gt;FGDB views: Since the division operator '/' isn't supported, create a DIVIDE() function instead&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 18:05:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391318#M28853</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-03-05T18:05:40Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391326#M28854</link>
      <description>&lt;P&gt;You might be able to do some pivoting too using SQL:&amp;nbsp;&lt;A href="https://dba.stackexchange.com/questions/299113/zero-null-case-trick" target="_self"&gt;Zero/NULL Case Trick&lt;/A&gt;&lt;/P&gt;&lt;P&gt;On a side note, here's an ArcGIS Pro idea for dynamic pivot tables:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/pivot-table-chart-style-in-arcgis-pro/idc-p/1390953" target="_self"&gt;Pivot Table Chart Style in ArcGIS Pro&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jun 2024 20:08:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1391326#M28854</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-06-14T20:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Attribute Summary Tables (VASTs) - Status changed to: Already Offered</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1608649#M34588</link>
      <description>&lt;P&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/define-parameters-in-a-query-layer.htm" target="_blank"&gt;https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/define-parameters-in-a-query-layer.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Apr 2025 18:46:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/virtual-attribute-summary-tables-vasts/idc-p/1608649#M34588</guid>
      <dc:creator>TanuHoque</dc:creator>
      <dc:date>2025-04-23T18:46:05Z</dc:date>
    </item>
  </channel>
</rss>

