{"id":8597,"date":"2019-04-29T05:35:03","date_gmt":"2019-04-29T03:35:03","guid":{"rendered":"http:\/\/www.sigterritoires.fr\/?p=8597"},"modified":"2019-04-29T09:35:16","modified_gmt":"2019-04-29T07:35:16","slug":"arcgis-10-3-apply-a-license-to-your-geodatabase-ludicrous","status":"publish","type":"post","link":"https:\/\/www.sigterritoires.fr\/index.php\/en\/arcgis-10-3-apply-a-license-to-your-geodatabase-ludicrous\/","title":{"rendered":"ArcGis 10.3: apply a license to your geodatabase? ludicrous !"},"content":{"rendered":"\n

With version 10.3, ESRI has announced a new possibility for the\ngeodatabase file: you can make them non-copy and you can give them a deadline\naccess date. Firstly, let\u2019s discuss all you have to do, then a nice example of\nhow to make yourself absurd by living in isolation. <\/p>\n\n\n\n

Firstly, let\u2019s consider the ESRI terms in the descriptive page of this new feature<\/a> : <\/p>\n\n\n\n\n\n\n\n

\u00a0\u00bb You<\/em> can<\/em> share<\/em> the<\/em> geodatabase<\/em> data file<\/em>\nwith<\/em> others<\/em> users<\/em> and<\/em> apply<\/em> a<\/em> license\nthat<\/em> determines<\/em> the<\/em> data<\/em>\nuse<\/em> authorized<\/em> duration<\/em> and<\/em> whether it is<\/em>\npossible<\/em> or<\/em> not<\/em> to export<\/em> feature classes.<\/em> <\/p>\n\n\n\n

For<\/em> example<\/em> ,<\/em> if<\/em> you<\/em> are<\/em>\nteacher<\/em> and<\/em> you<\/em> want<\/em> to<\/em> communicate<\/em> data<\/em> to<\/em> your<\/em> students<\/em>\nduring a<\/em> semester,<\/em> you<\/em> can<\/em> make<\/em> available<\/em>\na<\/em> geodatabase<\/em> file<\/em> that<\/em> contains<\/em> data<\/em>\nlicensed<\/em> to<\/em> expire at the end of the<\/em> semester.<\/em> Otherwise<\/em>\n,<\/em> if<\/em> you<\/em> hire<\/em> a<\/em> service provider<\/em> to\nanalyze a set of<\/em> data,<\/em> but<\/em> you<\/em> do<\/em> not want<\/em>\nthe provider being able to<\/em> export<\/em> the<\/em> data<\/em> ,<\/em>\nyou<\/em> can<\/em> make<\/em> available<\/em> a<\/em> geodatabase<\/em> file licensed<\/em>\nthat<\/em> does<\/em> not<\/em> allow<\/em> to export<\/em> the data<\/em>\n.<\/em> \u00a0\u00bb <\/p>\n\n\n\n

Therefore, the tool answers to real needs. This article is not a\ndiscussion between the data which is free or not. Let\u2019s agree that there are instances\nwhen, indeed , we can limit access to certain data . <\/p>\n\n\n\n

In this case, we are ArcGis users with special needs. We are lucky to, finally,\nhave tools enabling us to provide some data not likely to be copied or that\ntheir access is limited in time. <\/p>\n\n\n\n

How does it work<\/strong> ?<\/strong> <\/p>\n\n\n\n

In the toolbox Geodatabase<\/em> file<\/em> , you have two tools to\nassign a license to a file geodatabase : <\/p>\n\n\n\n

the first is used to generate a license definition file (file with the extension licdef.): the tool uses as input a geodatabase\nfile with the data included and generates a geodatabase file locked and a definition licence file containing the information of the locked geodatabase. At this stage , the locked geodatabase file is no longer accessible by either ArcMap or ArcCatalog. <\/li>
the second is used to generate a license\nfile (file with the extension sdlic.): the tool takes as input the locked geodatabase file as well as the . licdef file and configure authorization\/non authorization options to copy as well as the consultation deadline , that is registered in the license file . sdlic <\/li><\/ul>\n\n\n\n
At this stage , the secured file geodatabase is still not accessible\nwith ArcMap or ArcCatalog. To do this, you must open the License<\/em> Administrator<\/em>\nand add the file . sdlic in the list of data licenses . <\/p>\n\n\n\n
From there, you can access your geodatabase file , subject to registered\nlimitations in the license: copy right , deadline . <\/p>\n\n\n\n
An<\/strong> example<\/strong> \n\nLet\u2019s take an example with a geodatabase\ncontaining Natura 2000 areas and Znieff :\n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
The first<\/strong> step<\/strong> is to create the license definition\nfile with the Generate<\/em><\/strong> a<\/em><\/strong> geodatabase<\/em><\/strong> licensed<\/em><\/strong>\nfile<\/em><\/strong> tool. \n\nThe created geodatabase , Natura2000_Protected, cannot\nbe used in ArcMap and ArcCatalog. If you try to load a layer you get the following\nerror message : \n\n\n\n<\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
The second step<\/strong> is to create a license file with the Generate<\/em><\/strong>a<\/em><\/strong>geodatabase<\/em><\/strong>license<\/em><\/strong>file<\/em><\/strong> tool: <\/p>\n\n\n\n
$\"\"$ <\/figure>\n\n\n\n
You have two configuration settings : <\/p>\n\n\n\n
- Expiration date. <\/li><\/ul>\n\n\n\n
  The file Natura2000_Protected.sdlic<\/em> is created . <\/p>\n\n\n\n
  The fact that the file exists does not unlock access to the geodatabase.\nIf you try to load a layer , you will always get the error messages . <\/p>\n\n\n\n
  The third step is to add the geodatabase license in your installation data licenses. <\/p>\n\n\n\n
  Small detail , you have to close Arcmap and ArcCatalog to achieve this\noperation . \n\nOpen the Administrator<\/em><\/strong>ArcGis<\/em><\/strong>\n:   \n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  Select Data<\/em><\/strong> licenses<\/em><\/strong> then click Add<\/em><\/strong>\na<\/em><\/strong> license<\/em><\/strong> . <\/p>\n\n\n\n
  Check the file Natura2000_Protected.sdlic<\/em><\/strong> and click\nOK.<\/em><\/strong> <\/p>\n\n\n\n
  Close the window of the ArcGIS Administrator. \n\nNow you can access the protected file\ngeodatabase : \n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  Now, you can send the protected geodatabase and the file . sdlic to your\ninterlocutor . You can go to sleep peacefully, your data will not be copied or\nused beyond the date you have set. <\/p>\n\n\n\n
  How<\/strong> does<\/strong> it not work?<\/strong> <\/p>\n\n\n\n
  As for the quiet sleep, it will come to an end ! <\/p>\n\n\n\n
  Of course , every time there are safety, there are small smart to look\nfor flaws. Let’s forget them ! What we will now do is outside the hackage or\nbypass doubtful a function , in short , we will only do normal and trivial. <\/p>\n\n\n\n
  I am QGis user , I get a file geodatabase (protected or not). \n\nFirst step, I load the layer in QGis\n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  We click on the Add<\/em><\/strong> a vector layer<\/em><\/strong> , in Source\ntype<\/em><\/strong> we choose Directory<\/em><\/strong> , in Type<\/em><\/strong> we\nselect OpenFileGDB<\/em><\/strong> and in Data<\/em><\/strong> set<\/em><\/strong>, our\nprotected file geodatabase shows. \n\nClick on the Open<\/em> button :   \n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWe\nsee that the ZoneNature2000 layer has 0 entities . while\nGDB_SecureCopy_ZonesNatura2000 has 25885. We select obviously this latest and\n… \n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  The data is loaded without any problem. \n\nWe could say that, maybe, just the geometries\nare loaded and that the attribute table , at least , has been encrypted or\nprotected. Click Open<\/em><\/strong>Attribute<\/em><\/strong>Table<\/em><\/strong>\nand …   \n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  And everything is in clear as water . \n\nWell, we can them without any interference, but\nwe have protected the data. We try to save this layer as a shapefile<\/a>, right\nclick on the layer -> Save<\/em><\/strong>as<\/em><\/strong>:   \n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWe\nclick OK, and …   \n\n\n\n<\/p>\n\n\n\n
  $\"\"$ <\/figure>\n\n\n\n
  That’s our copy of the data ready and complete . <\/p>\n\n\n\n
  Conclusion<\/strong> <\/p>\n\n\n\n
  We forgot to say that once the\nexpiry date is past it continues to work the same … <\/p>\n\n\n\n
  We have, just, used QGis in the most classic way, legally and orthodoxly\n. No tampering or tricking! <\/p>\n\n\n\n
  Finally, we spent a quarter of an hour protecting our data while, only,\n30 seconds to load them and create a copy . By the way , the data is, mostly,\nprotected from ourselves when using ArcGis. <\/p>\n\n\n\n
  If the mood of this article is rather ironic, it is that we mean it, if\nthe lack of security is a concern , fake protections are a thousand times worse\n. How is an agreement suitable if it states that you cannot copy data if the\ndata is protected? What is the use of adding that it will destroy the data at\nthe end of the delivery if it will not be accessible after the deadline date? <\/p>\n\n\n\n
  And then, one should ask if those\nwho develop and disseminate these tools are aware that there is a real\nworld beyond ArcGis … <\/p>\n","protected":false},"excerpt":{"rendered":"
  With version 10.3, ESRI has announced a new possibility for the geodatabase file: you can make them non-copy and you can give them a deadline access date. Firstly, let\u2019s discuss all you have to do, then…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1260],"tags":[],"class_list":["post-8597","post","type-post","status-publish","format-standard","hentry","category-non-classe-en"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-2eF","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/8597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=8597"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/8597\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=8597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=8597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=8597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}