The libraries of ArcObjects available to ArcGIS Engine developers are shared with ArcGIS Desktop and ArcGIS Server
The libraries are listed in the table below in dependency order. Use the links to navigate to a more detailed overview of each library.
Knowing the library dependency order is important, since it affects the way in which developers interact with the libraries as they develop software. Understanding the dependencies also helps when deploying your developments.
|
Shared libraries
|
Deployment notes
|
|
The System library is the lowest level library in the ArcGIS architecture. The library contains components that expose services used by the other libraries composing ArcGIS.
|
|
|
The SystemUI library mainly defined types used by user interface components in the ArcGIS system. Interfaces such as ICommand and ITool are defined in this library. Implementation of these types is normally done in one or more libraries, higher in the architecture.
|
|
|
The Geometry library contains the core geometry objects, such as Point, Polygon, Polyline, etc. along with Geometry types and definitions. The Geometry library also defines and implements the spatial reference objects for both projected and geographic coordinate systems.
|
|
|
The Display library contains the components that support drawing symbology to an output device. Screen displays, symbols, colors and feedback objects, along with their supporting objects are all defined in the library.
|
|
|
The Server library contains the objects used to obtain a connection to the ArcGIS Server. The connection is managed via the objects in this library, but objects from other libraries can be created by using functions on the server object.
|
|
|
The Output library contains the objects required generate output, most commonly from Maps or PageLayouts, to both printers and plotters or exporting to files.
|
|
|
The GeoDatabase library contains types for all the definitions relating to data access. Features, tables, networks, TINs are all defined in the GeoDatabase library. The implementation of many of the types is contained in the respective DataSource library.
|
The usage of some objects in this library requires the Geodatabase Update extension for ArcGIS Engine Runtime.
|
|
The GISClient library contains objects for working with remote GIS Services. These services can be provided by either ArcIMS or the ArcGIS Server.
|
|
|
The
|
|
|
The DataSourcesFile library contains the workspace factories and workspaces for vector data formats supported by the GeoDatabase API.
|
|
|
The DataSourcesGDB library contains the workspace factories and workspaces for vector and raster data formats supported by the GeoDatabase that are stored within an RDBMS.
|
|
|
The DataSourcesOleDB library provides workspaces for working with OleDB based data sources.
|
|
|
The DataSourcesRaster library contains the workspace factories and workspaces for file based raster data formats.
|
|
|
The DataSourcesNetCDF library contains objects used for accessing netCDF files and for creating rasters, features, or tables from netCDF variables in ArcGIS.
|
|
|
The GeoDatabaseDistributed library contains the objects required to perform, checkout / checkin to support distributed GeoDatabase.
|
|
|
The GeoDatabaseExtensions library contains objects to aid in the creation, management, and use of terrain datasets and cadastral fabrics.
|
|
|
The Carto library contains the objects for displaying data. The PageLayout and Map objects are in this library along map layers, renders for all the supported data types. This library also contains the MxdServer and MapServer objects used by servers to display map data in a client server environment.
|
|
|
The DefenseSolutions library contains objects that display and edit military war fighting symbology per the MIL-STD-2552B Change 1 and APP-6A symbology specifications. These objects implement the non-user-interface functionality of the Military Overlay Editor (MOLE) software application and Military Analyst extension. It composes a collection of custom renderers and tools that conform to MIL-STD-2552B Change 1 and APP-6A. It also contains objects used for converting coordinates, creating geodetically correct geometric objects, creating and displaying MA Layers in ArcGIS, and controlling the GeoSym Renderer.
|
Requires the Military Overlay Editor (MOLE) software application or the ArcGIS Military extension.
|
|
The NetworkAnalysis library supports the creation and analysis of utility networks.
|
|
|
The Location library contains objects related to working with location data. This can either be route events or geocoding locations.
|
|
|
The GeoAnalyst library contains core spatial analysis operations that are used by both the Spatial and 3D extensions.
|
Requires a 3D or Spatial extension for ArcGIS Engine Runtime.
|
|
The Animation library contains objects to work with animations in Map, Scene and Globe. In ArcGIS 9.2, with ArcGIS Desktop, the animation functionality is available in the ArcMap, ArcScene, and ArcGlobe applications. However, when working with ArcGIS Engine, animation functionality is not available for the Map control. It is only available for the Scene and Globe controls, which are supported with the 3D Analyst extension.
|
|
|
The Maplex library contains the objects for labeling features using the Maplex Extension. Other Maplex objects can be found in the Carto library.
|
Requires a Maplex extension for ArcGIS Engine Runtime.
|
|
The Geoprocessing library implements the Geoprocessing framework in addition to the base set of Geoprocessing tools. The tools available depend on the licenses available to you. See the individual tools for specific license information.
|
Some geoprocessing tools and functionality require an extension license. See the documentation for each tool for specifics.
|
|
The NetworkAnalyst library provides objects for working with network datasets. These objects allow you to perform network analysis in your applications.
|
Requires a Network Analyst extension for ArcGIS Engine Runtime.
|
|
The Schematic library implements the non user-interface functionality of the Schematics extension. Its core objects are used to manage schematic data and processes. The Schematics extension supports the analysis, display, and manipulation of schematic data.
|
Requires a Schematic extension for ArcGIS Engine Runtime.
|
|
The SpatialAnalyst library contains objects for performing spatial analyst on raster and vector data.
|
Requires a Spatial extension for ArcGIS Engine Runtime.
|
|
The 3DAnalyst library contains objects for performing 3D analysis of data, along with the support for displaying 3D data.
|
Requires a 3D extension for ArcGIS Engine Runtime.
|
|
The GlobeCore library contains objects for performing analysis of globe data, along with the support for displaying globe data. A control is available in this library for developers to use.
|
Requires a 3D extension for ArcGIS Engine Runtime.
|
|
The Controls library contains controls for application development including commands and tools for use with the controls.
|
Applications that utilize the GlobeControl or SceneControl require a 3D extension for ArcGIS Engine Runtime.
|
|
The TrackingAnalyst library implements the non-user interface functionality of the Tracking extension to ArcGIS Engine. The Tracking extension supports the display, analysis, and manipulation of temporal data within ArcGIS.
|
Requires a Tracking extension for ArcGIS Engine Runtime.
|
|
The SystemUtility library provides some helper objects for cross-platform C++ developers.
NOTE: This library does not apply to Visual C++ developers.
|
|