Skip To Content

Essential vocabulary

In this topic

analysis

A systematic examination of a problem that provides new information. ArcGIS Runtime SDKs support many types of analysis, from simple geometry-based analysis to advanced spatial analysis. You can also string analysis operations together to build models for analysis. For details on analysis and model building, see geoprocessing.

API

Application programming interface. A specification that allows developers to create applications.

basemap

A map layer that helps orient the user of the map. Typically it shows roads and buildings, is non-editable, and is a tiled layer. For a description of basemaps and other layer types, see Layer types.

cache

For details, see tile cache.

Client ID

In ArcGIS Runtime SDKs, an identifier you associate with the app you build (one Client ID per app). You get a Client ID by signing into developers.arcgis.com. For details, see License your app.

connected

In ArcGIS Runtime SDKs, the state of having a network connection to one or more of the following: ArcGIS for Server, Portal for ArcGIS, or ArcGIS Online.

coordinate

A value that denotes the location of a vertex. Coordinates may represent 2D (x,y) or 3D (x,y,z) space. The meaning of the x,y,z-coordinates is determined by a coordinate system. The vertices and coordinate system together allow your app to translate a real-world object from its location on the Earth to its location on your map. For details, see Geometry contents in the Geometry operations topic.

coordinate system

A reference framework consisting of a set of points, lines, and/or surfaces, and a set of rules, used to define the positions of points in space in two or three dimensions. For details, see Geometry contents in the Geometry operations topic. Also known as map projections.

deployment manifest file

A file that can be included in your Visual Studio project that allows you to choose optional capabilities that your app uses. The corresponding files are copied to a folder to include with your app's deployment. The manifest helps you avoid including more capabilities than your app requires, thereby helping you keep your app's footprint as small as possible. See Create an ArcGIS Runtime deployment for information on using the deployment manifest.

deployment pack

In ArcGIS Runtime SDKs, a set of deployments for an app that contains Standard license level capabilities and does not require users to sign in with their ArcGIS Online or Portal for ArcGIS organizational account. Each pack comes with at least one product license string. Available licenses (license strings) are:

  • Standard
  • 3D Analyst
  • Network Analyst
  • Spatial Analyst

For details, see the topics License your app and Deploy your app.

device

In ArcGIS Runtime SDKs, nearly any kind of computer, including desktops, mobile phones and devices, laptops, smartwatches, and large mainframes.

development machine

In ArcGIS Runtime SDKs 10.2 and earlier, the computer or computers you develop applications on. In these SDK versions, your development machine must be licensed. In later versions, you need only a developer account to start developing, which you can get from the sign up page on developers.arcgis.com.

disconnected

For details, see offline.

feature

A representation of a real-world object on a map, such as a building, a river, or a county. A feature may include attributes and a geometry . For more information, see Features and graphics.

geodatabase feature

A representation of a real-world object persisted in a geodatabase. When displayed, it is displayed in a feature layer. GeodatabaseFeatures can have geometry and attributes. GeodatabaseFeatures are associated with a feature table, with which they share a common schema.

geometry

The combination of location and shape for a real-world object or for a geometric construct such as an area of interest or a buffer area around an object. Geometry is the fundamental element for performing spatial analysis. For information on analysis operations such as clip, buffer, and intersect, see Geometry operations.

GeoPackage

A single SQLite file (.gpkg) that conforms to OGC GeoPackage specification (http://www.opengeospatial.org/standards/geopackage) that defines GeoPackages for direct use of vector geospatial features and/or tile matrix sets.

geometry

The combination of location and shape for a real-world object or for a geometric construct such as an area of interest or a buffer area around an object. Geometry is the fundamental element for performing spatial analysis. For information on analysis operations such as clip, buffer, and intersect, see Geometry operations.

geoprocessing

A GIS operation used to manipulate data. A typical geoprocessing operation takes an input dataset, performs an operation on that dataset, and returns the result of the operation as an output dataset. Common geoprocessing operations include geographic feature overlay, feature selection and analysis, topology processing, raster processing, and data conversion. Geoprocessing allows for definition, management, and analysis of information used to form decisions.

You can use geoprocessing tools to chain together a sequence of operations, feeding the output of one tool into another tool, to automate your work, solve complex problems, or perform batch processing. Sequencing operations like this are referred to as model building.

Your app can consume online geoprocessing services or local (packaged) geoprocessing tools. For details on which local tools are supported in each license level, see Supported geoprocessing tools.

graphic

A representation of a real-world object stored in memory. When displayed, it is displayed in a graphics layer. Graphics exist while the app is running, and therefore are used often for temporary features. Graphics can have geometry and attributes. Graphics are not associated with a feature table. For more information, see Features and graphics.

license code

A string of characters that you add to your project, as described in License your app to unlock certain capabilities on the deployment device.

local service

Services, such as geoprocessing services you create, used by your deployed application that are running on the same machine or device as the application. Because they can consume local services, applications you build with ArcGIS Runtime SDK do not require an ArcGIS Server connection to run or to access geodatabase data. Local services use packages. For details, see packages.

locator package

A geocode locator package (.gcpk) makes it easy to share locators with others. A locator package can contain one locator or a composite locator along with its participating locators packaged into one convenient, portable file. The file size of the locator package is smaller than the locator, as it is compressed and thus makes file transfer easier. Locator packages can be used for easy sharing of locators between colleagues in a workgroup, across departments in an organization, or with any other ArcGIS users via ArcGIS Online. Locator packages can also be used to create an archive of the locators.

map cache

For details, see tile cache.

map package

A single file (an .mpk file) you create in ArcGIS for Desktop that contains a map document (.mxd file) and the data layers it references. You can use it to provide local maps to apps that run offline or to share maps between colleagues in a workgroup, across departments in an organization, or with any other ArcGIS users by using ArcGIS Online.

mobile app

In ArcGIS Runtime SDKs, a software application that operates on a mobile device. A mobile device is typically a mobile phone or tablet, such as an iPhone, iPad, and an Android phone and tablet. Apps for custom-purpose handhelds, such as Windows Mobile devices, and car navigation systems are not included unless otherwise specified.

mobile device

In ArcGIS Runtime SDKs, a mobile phone or tablet, such as an iPhone, iPad, and an Android phone and tablet. Custom-purpose handheld devices, such as Windows Mobile devices, and car navigation systems are not included unless otherwise specified.

offline

In ArcGIS Runtime SDKs, the state of having no network connection to any of the following: ArcGIS for Server, ArcGIS Online, or Portal for ArcGIS.

operational layer

A map layer that users can interact with. Typically, an operational layer is vector-based and is editable by users. However, it can also be tiled data that can be queried against. See Maps and layers for more information.

package

A set of items, such as a map and its referenced data, that ArcGIS for Desktop bundles into a single file on your local machine so that the items can be easily transfered from user to user or provisioned onto a device. Especially useful for disconnected apps.

For a list of packages supported by ArcGIS Runtime SDK local services, see Packages used by ArcGIS Runtime.

renderer

A mechanism that defines how data appears when displayed. See Symbols and renderers for more information.

Runtime components

A collection of files containing various parts of ArcGIS Runtime functionality, installed and used on your development machine and deployed with the apps that you create.

The full collection, installed to your development machine when you install ArcGIS Runtime SDK, includes the required Runtime core components and optional components such as those for Local Server and advanced symbology. When you prepare an app for deployment, the Deployment Builder tool helps ensure you deploy only the parts of the collection that are required by the app you build. For descriptions of optional Runtime functionality sets, see Create an ArcGIS Runtime deployment.

Runtime core

Client files (.dll or .so) that must be deployed with all ArcGIS Runtime apps. For Java, Qt, and WPF, you can use the Deployment Builder wizard to choose which Local Server capabilities you want to deploy so they can be bundled with the Runtime core files for you.

SDK

Software development kit. A collection of documentation, sample code, and sample apps to help a developer use an API to build apps.

shapefile

A vector data storage format for storing the location, shape, and attributes of geographic features. A shapefile is stored in a set of related files.

side-by-side development

A capability that lets you develop with different versions of the same SDK on the same machine.

tile

An image, often a graphics file (for example, a .jpg file) and typically stored in a directory known as a cache. The image is part of a set of tiles that, conceptually, are pieces of a bigger map. How the tiles fit into the bigger map, along with other information, is defined in a tiling scheme. Two tile categories are:

  • Tiles in dynamic layers are created on-the-fly and can be stored in a cache on the client machine or on the server machine. Which tiles are created in this scenario depends on where the user pans and zooms, so technically, the tiles may not make up a complete bigger map when put together.
  • Tiles in tile cache layers are created before users view the map, often by a developer or GIS data administrator. These tiles are known as pre-processed tiles.

Also see tile cache.

tile cache

A directory that contains tiles of a map extent at specific levels. The directory can be local to a desktop app or to a client app in a client/server configuration. Also see tile.

tiled layer

A tiled layer is a layer comprised of images that when put together make up a bigger image of a map. Tiles are generated before they're displayed for the user. This differs from a dynamic layer, which generates the images as they are requested by the user, or on-the-fly. Tiled layers are often used for basemaps.

tile package

Tile packages (.tpk files) make is easy to share complete map documents with others. A tile package contains a map and the tile cache of the data contained within it, packaged into one convenient, portable file. Tile packages can be used for easy sharing of cached maps between colleagues in a workgroup, across departments in an organization, or with any other ArcGIS user using ArcGIS Online. Tile packages are ideal in disconnected environments where access to local data is required.

toolkit

A set of user interface components to assist rapid application development. The toolkit components are contained in the toolkit assembly for which the source code is available in a public GitHub repository.

vertex

A point that stands alone or makes up part of a geometry. Vertices that make up a geometry may be connected, one to the next, in a linear order. For more information on vertices and how they're stored in geometries, see Geometry contents in the Geometry operations topic.

viewshed

The locations visible from one or more specified points or lines. Viewshed maps are useful for such applications as finding well-exposed places for communication towers, or hidden places for parking lots. You can create viewsheds using the Standard license level of ArcGIS Runtime SDKs.

USB flash drive

A removable thumb-sized device that provides storage space. USB stands for universal serial bus, an interface compatible with most computers. Also known as thumb drive, flash drive, USB drive, and memory stick. Apps created with ArcGIS Runtime SDK can be deployed to a USB flash drive.