<?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 When creating a licensed file gdb, protect and license all data, not just vector in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/when-creating-a-licensed-file-gdb-protect-and/idi-p/1671963</link>
    <description>&lt;P&gt;When licensing a file geodatabase, currently only the vector data is protected and licensed. Any file gdb rasters are bypassed.&amp;nbsp;Having tested file gdb tables, the protection and licensing seems to be applied along with the vector data. This is for both a stand-alone table and also a related table.&lt;BR /&gt;It appears that the issue just lies with the rasters.&lt;/P&gt;&lt;P&gt;Our data products contain a combination of vector and raster.&lt;BR /&gt;There are scenarios where delivering our data using file geodatabases is the preferred method and as a result, we would like to utilise the functionality of protecting the data by creating a licensed file gdb.&lt;BR /&gt;This would allow us to deliver data which only works with a license, but we can also set an expiry date for that license to coincide with the end of a contractual term. This is ideal for adding further protection of our IP.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Dec 2025 15:16:50 GMT</pubDate>
    <dc:creator>Getech_Admin</dc:creator>
    <dc:date>2025-12-10T15:16:50Z</dc:date>
    <item>
      <title>When creating a licensed file gdb, protect and license all data, not just vector</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/when-creating-a-licensed-file-gdb-protect-and/idi-p/1671963</link>
      <description>&lt;P&gt;When licensing a file geodatabase, currently only the vector data is protected and licensed. Any file gdb rasters are bypassed.&amp;nbsp;Having tested file gdb tables, the protection and licensing seems to be applied along with the vector data. This is for both a stand-alone table and also a related table.&lt;BR /&gt;It appears that the issue just lies with the rasters.&lt;/P&gt;&lt;P&gt;Our data products contain a combination of vector and raster.&lt;BR /&gt;There are scenarios where delivering our data using file geodatabases is the preferred method and as a result, we would like to utilise the functionality of protecting the data by creating a licensed file gdb.&lt;BR /&gt;This would allow us to deliver data which only works with a license, but we can also set an expiry date for that license to coincide with the end of a contractual term. This is ideal for adding further protection of our IP.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 15:16:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/when-creating-a-licensed-file-gdb-protect-and/idi-p/1671963</guid>
      <dc:creator>Getech_Admin</dc:creator>
      <dc:date>2025-12-10T15:16:50Z</dc:date>
    </item>
  </channel>
</rss>

