ArcGIS Desktop includes several optional extensions that can be used for raster analysis, 3D visualization, advanced map printing, etc. Each extension is listed below along with a brief description of its capabilities.
Spatial Analyst |
Surface creation, raster analysis, and grid algebra. |
3D Analyst |
Three dimensional visualization and analysis. |
Geostatistical Analyst |
Advanced kriging and statistical analysis for surface estimation. |
Streetmap USA |
Nationwide street mapping and geocoding. |
MrSID Encoder* |
Encode and mosaic images up to 500 mega-pixels in size. |
ArcPress
|
Advanced map printing.
|
TIFF/LZW Compression* |
Provides the right to use TIFF/LZW compression technology patented by UNISYS. |
*These extensions cannot be managed from the Extension dialog.
ArcGIS Workstation contains additional extensions. Workstation extensions cannot be managed using the Extensions dialog.
You may choose to install these extensions during the installation process by selecting the Complete or Custom options. For more information on the installation process, see the Install.htm located in the documentation folder in your install location (ex. c:\arcgis\arcexe81\documentation) or on the ArcGIS Desktop or ArcInfo Workstation CD.
At any time, you may evaluate extensions that you have not purchased. The evaluation is free of charge for a fixed period of time. (Streetmap USA, MrSID Encoder and TIFF/LZW Compression are not available for evaluation.)
To see which licenses these extensions use, please refer to the section: Licenses available for Windows NT and 2000.
In order to use an extension, it has to be enabled in the Extensions dialog in the application you want to use.
You can access the Extensions dialog by choosing Extensions from the Tools menu in ArcMap and ArcCatalog. You'll also find the Extensions command in the Tools menu of ArcScene (the application that comes with the 3D Analyst extension).
In each application (ArcMap, ArcCatalog, and ArcScene), the Extensions dialog lists the extensions that are currently installed and can be used by that application. Extensions that cannot be used in a particular application will not be listed in the Extensions dialog for that application.
By default, the first time you open the Extension dialog all extension boxes are unchecked. When you make changes to the extension dialog, the settings are automatically saved with your user profile. Each new user can create personalized extension settings.
When you enable an extension in the Extension dialog, an appropriate extension license is automatically obtained from the License Manager. The extension’s functionality becomes available for use in the application.
Unchecking an extension returns the extension license to the License Manager making it available for another user. The extension’s functionality is no longer available for use within the application.
If a license cannot be obtained when you enable an extension in the Extensions dialog, the message "License Not Available" will appear next to the extension name. The extension's functionality cannot be used until a valid license is available. You may try to obtain a license by unchecking and rechecking the extension, or by shutting down and restarting the application.
We recommend that you have only one ArcMap session open when you make changes to the ArcMap Extension dialog.
The Extension dialog changes will immediately be applied to the ArcMap session in which they were made. The Extension dialog changes will NOT be applied to other open ArcMap sessions.
The state of the Extension dialog is saved from the LAST ArcMap session open (not necessarily the ArcMap Extension dialog with the most recent changes.)
Ensure that your changes are saved by making sure your modified ArcMap session is the last ArcMap session you close.
ArcCatalog demonstrates the same behavior. If you have two ArcCatalog sessions open, the state of the Extension dialog will be saved from the LAST ArcCatalog session open.
Some extensions provide support for additional data types. You can open a map document containing layers that reference these extension-specific data types, even if that extension is not currently installed or enabled. However, depending on the extension, you may not be able to draw these layers or use them in other operations until you install and enable the extension that they were created with.
ArcToolbox does not support an Extension dialog control. Some TIN commands can be accessed via the ArcToolbox. They are Contour, CreateTIN, Visibility, and Volume. You need an available TIN license to execute these commands. The ArcToolbox extension license behavior is the same as Workstation ArcInfo. There are a few reasons for allowing the ArcToolbox to behave this way:
The TIN Wizards can be used to generate AML code that will be processed later, when TIN licenses may be available
The TIN Wizards can be used to generate batch jobs that will be processed on a Geoprocessing Server that will have an available license.
The ArcToolbox supports a “Run Geoprocessing AML” that could run any Arc: command that uses an extension license.
The ArcToolbox is an interface to Arc: and inherits the Workstation extension license model from it.
Application developers can query the state of all extensions to determine if the extension is available or not. They can attempt to change the state using IExtensionConifg::put_State which may fail if an attempt is made to enable an extension when a license is not available.
Failures of this kind will not result in a user interface flag (error messages, dialog boxes, alerts) of any kind. The failure is signaled via the HRESULT returned from IExtensionConfig::put_State. (Note, that put_State(state = esriESDisabled) can fail when objects that require a license are in use by that extension.)
If an attempt is made to use an object in the absence of a license, methods will fail by returning a failure HRESULT. Various choke points will be introduced in the object models of the extensions to insure that the extension is enabled before executing the functionality.
Third party developer extensions may be listed in the Extensions dialog by implementing the IExtension and IExtensionConfig interfaces and registering the component in the appropriate category for the desired application: CATID_MxExtensions, CATID_GxExtensions, or CATID_SxExtensions. The IExtensionConfig interface is designed to be independent of our licensing approach so third party developers can incorporate a custom licensing solution.