AnsweredAssumed Answered

PackageLayer_management() - Access Use and Constraints

Question asked by johnmdye on Oct 13, 2014
Latest reply on Oct 13, 2014 by jskinner-esristaff

When you create a layer package manually through the ArcMap Table of Contents, there is a textbox labeled 'Access Use and Constraints'.


I have a few questions on this (I guess that's what it is)


First, what is the actual intent of this property?

Is it for me to enter things like classifications (ie. Public, Confidential, Proprietary, Secret, Top Secret, etc.)?

If so, what's the point as there doesn't seem to be a way to interrogate it or even set it through arcpy?

Additionally, that property also does not seem to become a property on the Layerfile or Featureclass packaged into the LPK when they are extracted, so I mean really...I don't know what to do with it.


Secondly, why is it unique to LPKs or more correctly Packages?

I mean, an LPK is just essentially a zipped Geodatabase replica (or shapefile...and shame on you if that's the case) and Layerfile. Admittedly, it's a little more than that because if you change the extension to .zip, you can't extract it so there's a little more going on under the hood there, but conceptually that's what we're dealing with.

What's more, when you extract an LPK, you get the dataset and a layerfile referencing the dataset in your assembly cache and the layerfile is what gets added to your MXD but since Layerfiles nor Feature Classes have no Access Use and Constraints property there's no place for that property to be assigned. So...poof? It goes into the abyss? I'm just really confused over the whole thing.


Summary is another property which Layerfiles and Feature Classes do not have, but I'm able to rationalize that property a bit more because Layer Packages can contain multiple datasets and layers. Therefore, a summary is useful in that it can provide information about the could the description as well...darn it, confused again...