Application programming interface. A specification that allows developers to create applications.
ArcGIS Runtime SDK installation directory
<ArcGIS Runtime SDK installation directory> refers to the folder you install the ArcGIS Runtime SDK for Java to. By default on Windows 64 bit for Java, the directory is C:\Program Files (x86)\ArcGIS SDKs\java10.1.1. On Ubuntu, the default installation directory is $HOME/arcgis/runtime_sdk/java10.1.1.
A file that you receive from your Esri representative. Your Esri representative can be an Esri customer support staff member, an Esri Distributor, your Esri account manager, or another representative.The file indicates that you or your company has purchased the product and are a valid user of the product.
See tile cache.
Typically refers to a scenario in which an application is connected to the Internet or to a network that's connected to ArcGIS Server, ArcGIS Online, or Portal for ArcGIS.
A set of deployments for applications built with ArcGIS Runtime SDK for Java. Each pack comes with at least one product license string. Available licenses (license strings) are:
- 3D Analyst
- Network Analyst
- Spatial Analyst
ArcGIS Runtime SDK for Java comes with a deployment tool that allows you to choose the optional functionality sets that your application uses so the tool can copy the corresponding library files (.dll or .jar files) to a folder. The tool helps you avoid including more capabilities than your application requires, thereby helping you keep your application's footprint as small as possible. Also see runtime components.
The computer you plan to develop applications on. It differs from a deployment machine/device, one of the computers you plan to deploy your application to.
Typically refers to a scenario where your users are using an application (the ArcGIS application or an application you built) without a connection to ArcGIS Server, ArcGIS Online, or Portal for ArcGIS. For example, field inspection and data collection tasks in the field often require that field workers be able to work with an application that doesn't require an Internet connection or connection to their organization's servers.
A GIS operation used to manipulate GIS 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.
A string of characters included in the license code snippet that you add to your project to unlock certain functionality sets on the deployment machine/device or the testing machine/device. For information on which functionality sets require which licenses (which license strings), see Functionality set requirements. Also see runtime components and pack.
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 for Java do not require an ArcGIS Server connection to run or to access geodatabase data. Local services use packages. Also see packages.
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 work group, 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.
A software application with capabilities focused on a visual representation of a geographic region(s) or of worldwide data. The application can be a mobile application, can run in a web browser, can run off of a USB flash drive, or can be a desktop client with robust analysis capability, such as ArcMap. Also known as map-based application.
See tile cache.
Map packages (.mpk) make it easy to share complete map documents with others. A map package contains a map document (.mxd) and the data referenced by the layers it contains, packaged into one convenient, portable file. Map packages can be used for easy sharing of maps between colleagues in a work group, across departments in an organization, or with any other ArcGIS users via ArcGIS Online. Map packages have other uses, too, such as the ability to create an archive of a particular map that contains a snapshot of the current state of the data used in the map.
A software application that operates on a mobile device. A mobile device is typically a mobile phone, such as an Android or iPhone, but it can also be a tablet, laptop, or vehicle-mounted device or computer. Also known as app or mobile app.
A set of items, such as a map and its referenced data or a map and its tile cache, that ArcGIS bundles into a single file on your local machine so that the items can be easily transfered from user to user or easily provisioned onto a machine or device. The file is especially useful for disconnected environments, where the application you deploy has only local access—access only to files on the same machine or device the application is installed on.
The bundling process, or packaging process, ensures everything needed to view the set of items is included in the bundle, including referenced items that might've otherwise been left out if you were trying to share the items.
For a list of packages supported by ArcGIS Runtime SDK for Java local services, see Packages used by the ArcGIS Runtime. Also see tile cache and local service.
A mechanism that defines how data appears when displayed.
A collection of functionality (.jar files) installed on your development machine and deployed with your application.
The full collection is installed to your development machine when you install ArcGIS Runtime SDK for Java. When you prepare an application for deployment, the Deployment Builder helps ensure you deploy only the parts of the collection required by the application you built. For descriptions of optional runtime functionality sets, see Deploying the runtime.
Software development kit. A collection of documentation, sample code, and sample applications to help a developer use an API to build applications.
side-by-side development and deployment
A capability that lets you develop with different SDK versions on the same machine and lets you deploy to the same machine multiple applications built with different versions of the SDK.
software authorization number
The EDN authorization number you received with your EDN subscription or from an authorization file supplied by your Esri representative. Your Esri representative can be an Esri customer service staff member, an Esri Distributor, your Esri account manager, or another representative. If you are unsure of who your Esri representative is, you can find out at http://www.Esri.com/about-Esri/locations.html. Also known as authorization code.
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.
A directory that contains tiles of a map extent at specific levels. The directory can be local to a desktop application or to a client application in a client/server configuration. Also see tile.
Tile packages (.tpk) 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 work group, 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.
A set of user interface components to assist rapid application development. The toolkit components are contained in the toolkit jar for which the source code is available. Also see 'toolkit jar', below.
A .jar file that contains the toolkit components which you can use in your applications. The jar is located in the directory <ArcGIS Runtime installation directory>/sdk/jars. To use any toolkit component, add the jar manually to your project or using the Eclipse plugin's 'Add toolkit jar' menu option.
The viewshed identifies the cells in an input raster that can be seen from one or more observation points or lines. Each cell in the output raster receives a value that indicates how many observation points can see the location. If you have only one observation point, each cell that can be seen from the observation point is given a value of 1. All cells that can't be seen from the observation point are given a value of 0.
For details, see Analyze visibility.
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.