<?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 Show if a tool will not work with a geopackage or other format in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/show-if-a-tool-will-not-work-with-a-geopackage-or/idi-p/1709963</link>
    <description>&lt;P&gt;Currently, there are file-types and data formats that are not fully supported within the ArcGIS ecosystem. The ability for a tool to report which files or data formats are fully supported vs. those that are not, would offer the following benefits:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;reduce user confusion and troubleshooting&lt;/LI&gt;&lt;LI&gt;reduce number of Esri support cases&lt;/LI&gt;&lt;LI&gt;allow a development roadmap to be:&lt;UL&gt;&lt;LI&gt;maintained&lt;/LI&gt;&lt;LI&gt;scored and based on end-user tool usage statistics&lt;/LI&gt;&lt;LI&gt;scored and voted on by end-users&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Granted, this is a lot of development work upfront to build all the testing required. across all the toolboxes. After that initial work, the testing suite would be minimal to maintain AND offer Esri developers an additional pathway for regression testing and preventing tool breakages in future versions. My personal interest is the geopackage, but this idea is applicable to any of the newly developing formats that are being utilized throughout the industry.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;This is an idea on request of&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.esri.com/t5/user/viewprofilepage/user-id/604859" target="_blank"&gt;@SSWoodward&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; to split [the] idea "full support of gpkg" into more clearly defined sub-ideas.&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/full-functionality-for-gpkg-in-arcgis-pro/idi-p/1491535" target="_blank"&gt;https://community.esri.com/t5/arcgis-pro-ideas/full-functionality-for-gpkg-in-arcgis-pro/idi-p/14915...&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;see also,&amp;nbsp;&lt;STRONG&gt;add fields to gpkg&lt;/STRONG&gt;:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/make-it-possible-to-add-fields-to-gpkg-and-use/idi-p/1709814" target="_blank"&gt;make it possible to add fields to gpkg and use too... - Esri Community&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Jun 2026 17:53:46 GMT</pubDate>
    <dc:creator>JordanCarmona</dc:creator>
    <dc:date>2026-06-25T17:53:46Z</dc:date>
    <item>
      <title>Show if a tool will not work with a geopackage or other format</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/show-if-a-tool-will-not-work-with-a-geopackage-or/idi-p/1709963</link>
      <description>&lt;P&gt;Currently, there are file-types and data formats that are not fully supported within the ArcGIS ecosystem. The ability for a tool to report which files or data formats are fully supported vs. those that are not, would offer the following benefits:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;reduce user confusion and troubleshooting&lt;/LI&gt;&lt;LI&gt;reduce number of Esri support cases&lt;/LI&gt;&lt;LI&gt;allow a development roadmap to be:&lt;UL&gt;&lt;LI&gt;maintained&lt;/LI&gt;&lt;LI&gt;scored and based on end-user tool usage statistics&lt;/LI&gt;&lt;LI&gt;scored and voted on by end-users&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Granted, this is a lot of development work upfront to build all the testing required. across all the toolboxes. After that initial work, the testing suite would be minimal to maintain AND offer Esri developers an additional pathway for regression testing and preventing tool breakages in future versions. My personal interest is the geopackage, but this idea is applicable to any of the newly developing formats that are being utilized throughout the industry.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;This is an idea on request of&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.esri.com/t5/user/viewprofilepage/user-id/604859" target="_blank"&gt;@SSWoodward&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; to split [the] idea "full support of gpkg" into more clearly defined sub-ideas.&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/full-functionality-for-gpkg-in-arcgis-pro/idi-p/1491535" target="_blank"&gt;https://community.esri.com/t5/arcgis-pro-ideas/full-functionality-for-gpkg-in-arcgis-pro/idi-p/14915...&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;see also,&amp;nbsp;&lt;STRONG&gt;add fields to gpkg&lt;/STRONG&gt;:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/make-it-possible-to-add-fields-to-gpkg-and-use/idi-p/1709814" target="_blank"&gt;make it possible to add fields to gpkg and use too... - Esri Community&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jun 2026 17:53:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/show-if-a-tool-will-not-work-with-a-geopackage-or/idi-p/1709963</guid>
      <dc:creator>JordanCarmona</dc:creator>
      <dc:date>2026-06-25T17:53:46Z</dc:date>
    </item>
  </channel>
</rss>

