When licensing a file geodatabase, currently only the vector data is protected and licensed. Any file gdb rasters are bypassed. 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.
It appears that the issue just lies with the rasters.
Our data products contain a combination of vector and raster.
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.
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.
