ArcGIS Developer Foundation key terms

The HTTP interface exposed by ArcGIS services, where operations are invoked as URL endpoints returning JSON, and resources are addressed by paths. Clients use it to query, edit, and manage services without a vendor SDK.

A REST service that exposes vector features with geometry, attributes, and editing capability. It supports query, add, update, and delete operations, and is the primary data layer behind hosted feature layers and field editing apps.

A REST service that returns rendered map images or vector tiles rather than editable features. It is typically read-only and used for basemaps and cartographic display, though it can also expose limited query capability.

A structured container for spatial data that stores features, tables, relationships, domains, and topology rules. It exists in file, personal, and enterprise forms, and enterprise geodatabases add versioning and multi-user editing.

A collection of features of a single geometry type stored together, such as points, lines, or polygons. Each feature has a shared attribute schema and a unique object identifier, and it is the basic vector storage unit.

A layer in a map or app that references a feature source and applies symbology, labeling, and popups to it. Feature layers can be client-side or service-backed, and they carry the editing and query behavior configured for display.

A system-maintained integer field that uniquely identifies each row in a feature class or table. It is required for editing and relationship tracking, and it is not guaranteed to stay stable across data reloads unless explicitly preserved.

A field holding a globally unique identifier, typically a GUID, that stays stable across copies, replicas, and synchronization. It is used for offline editing and distributed data workflows where object IDs may collide or change.

The spatial component of a feature, expressed as coordinates plus a spatial reference. Common types include point, multipoint, polyline, polygon, and envelope, and geometry objects are serialized to JSON for transport over REST.

A coordinate system definition, including datum and projection parameters, that determines how coordinates map to locations on the earth. Services and clients must agree on it, and servers can reproject on request via an output parameter.

A projected coordinate system widely used for web maps because it preserves shape locally and tiles efficiently. It distorts area strongly toward the poles, so it is unsuitable for area measurement and global thematic mapping.

A layer that displays pre-rendered image tiles organized by zoom level, row, and column. Tiles are cached for fast display but carry no attributes, so they cannot be queried like features and must be regenerated when data changes.

A compact binary encoding of geometry and attributes split into tiles, rendered client-side by the map. Vector tiles allow dynamic restyling and smaller payloads than raster tiles, but styling happens on the device.

The reference layer providing geographic context beneath operational data, such as imagery, streets, or terrain. Basemaps are usually cached tile services and can be selected from a basemap style or supplied as custom layers.

The REST inputs that filter and shape a request, such as where, outFields, returnGeometry, and f. Correct use of these controls response size, projection, and format, which matters for performance and payload limits.

A SQL expression passed to a query that filters features by attribute, for example a status field equal to a value. It supports comparison and logical operators, and date and string literals must follow the service's SQL dialect.

A filter applied to a layer so only matching features are drawn and queried. It is set in the layer configuration rather than per request, making it useful for restricting a shared layer to a subset without copying data.

Fetching large result sets in chunks using parameters such as resultOffset and resultRecordCount, or by splitting on object ID ranges. It avoids service result limits and keeps client memory and response times manageable.

The process of proving identity to access protected services, commonly through OAuth 2.0 tokens, API keys, or enterprise identity providers. Tokens expire and must be refreshed, and scopes determine which resources the caller may reach.

A long-lived credential string that identifies an application and grants access to specific services or quotas. Keys are simpler than OAuth but must be restricted by referrer or IP and never embedded where they can be extracted.

An authorization framework in which a user grants an application scoped access without sharing a password. ArcGIS uses it for named-user sign-in, and the app receives access and refresh tokens for API calls.

A time-limited credential string issued after successful authentication and sent with requests to authorize them. Access tokens expire quickly, so applications must refresh them, and tokens should be transmitted only over HTTPS.

A developer-focused offering providing location services, basemaps, geocoding, and routing through APIs with usage-based keys. It does not require a full organizational account, making it suitable for embedding location features in custom apps.

Converting text addresses into coordinates and, in reverse, coordinates into addresses. Services expose endpoints for single and batch operations, and results include match scores and candidate addresses for quality control.

Resolving a coordinate pair to the nearest address or place description. It is used for map clicks and data enrichment, and accuracy depends on the reference data and search distance supplied in the request.

Computing optimal paths between stops using a network dataset, with options for travel mode, barriers, and time windows. Services return directions, distances, and estimated times, and can solve multi-stop or fleet problems.

A routable data structure built from line features with connectivity, impedance attributes, and turn rules. It powers routing, service areas, and closest facility analysis, and must be rebuilt when the underlying streets change.

The region reachable from a facility within a given travel time or distance along a network. It is used for coverage analysis such as emergency response or retail catchment, and output can be polygons or lines.

A client-side library for spatial operations such as buffer, intersect, union, and projection without a server round trip. Running these locally reduces latency and service usage, but requires geometry to be loaded in memory.

A query that filters features by their relationship to another geometry, such as intersects, contains, or within a distance. It is expressed through geometry and spatialRel parameters and is often combined with attribute filters.

A specific URL path on a service that represents a resource or operation, such as a layer's query operation. Endpoints return JSON by default, and the f parameter selects HTML, JSON, or other response formats.

A lightweight text format of objects, arrays, and primitives used for nearly all ArcGIS REST requests and responses. Feature data is commonly encoded as Esri JSON or GeoJSON, and clients must parse it into native objects.

An open JSON specification for geographic features with type, geometry, and properties members. ArcGIS services can return it via a format parameter, and it is the standard interchange format for web mapping libraries.

A geodatabase construct defining an association between two tables, with cardinality and optional messaging. It supports one-to-many and many-to-many links, and related records can be returned in queries via relationship parameters.

An enterprise geodatabase capability that lets multiple editors work on isolated versions and reconcile changes later. It prevents edit conflicts in multi-user workflows, and versions can be posted to the default version when complete.

A copy of data created for offline use or distributed editing, tracked so changes can be synchronized back. Replicas rely on global IDs and versioning, and synchronization can be one-way or two-way depending on configuration.

The process of exchanging edits between a replica and its source, upload-first then download, using tracked changes. It enables field workflows without continuous connectivity, and conflicts must be resolved by defined rules.

An attack where untrusted input is concatenated into a query and alters its logic. In ArcGIS clients, user-supplied values should be escaped or parameterized before entering where clauses to prevent data exposure.