ArcGIS Developer Foundation flashcards
ArcGIS Developer Foundation · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- ArcGIS REST API
- The HTTP/JSON interface underlying all ArcGIS services; each service exposes resources and operations such as query, applyEdits, and export that SDKs and apps call directly.
- API key authentication
- A long-lived credential sent as a token parameter for service access; it carries no user identity and can be restricted by referrer, IP range, and service scope.
- OAuth 2.0 authorization code flow
- Browser-based login where the app redirects to the portal authorize endpoint, receives a code, and exchanges it for an access token tied to a user's identity.
- Portal item
- The fundamental unit of content in ArcGIS Online or Enterprise, identified by a 32-character item ID and typed as Web Map, Feature Service, Layer, or similar.
- WebMap and WebScene
- Portal items that store a 2D map or 3D scene definition, including layers, basemap, and bookmarks, loadable by item ID in any ArcGIS SDK.
- FeatureLayer
- A client-side layer bound to a feature service layer that supports querying, rendering, popups, and editing of vector features with attributes and geometry.
- MapImageLayer
- A layer that displays server-rendered map images from a map service, with sublayers that can be toggled, filtered, and queried individually.
- TileLayer
- A cached raster tile layer served from a tile cache; fast to render but not queryable for attributes and only refreshed by rebuilding the cache.
- GraphicsLayer
- A client-side layer holding temporary graphics created in code, used for sketches, highlights, and analysis results that are not persisted to a service.
- MapView and SceneView
- View objects that render a Map in 2D or a WebScene in 3D; they own extent, camera, popups, hit testing, and the UI widget container.
- PopupTemplate
- Configuration object defining popup content via field infos, expressions, or functions, attached to a layer to control what appears when a feature is clicked.
- resultOffset and resultRecordCount
- Query parameters that page through large result sets; pair them with orderByFields on a unique field to keep pages stable across requests.
- exceededTransferLimit
- A boolean in a query response indicating more records exist than were returned, signaling that paging or a narrower filter is required.
- outStatistics parameter
- A JSON array defining server-side statistics such as count, sum, avg, min, max, and stddev on specified fields, optionally grouped by category fields.
- applyEdits operation
- A REST editing endpoint accepting adds, updates, and deletes arrays; returns per-feature results with success flags and assigned object IDs.
- rollbackOnFailure
- An applyEdits parameter that makes the whole edit transaction atomic: if any feature fails, all changes in that request are reverted.
- spatialRel values
- Spatial relationship filters for queries, including esriSpatialRelIntersects, esriSpatialRelContains, esriSpatialRelWithin, and esriSpatialRelEnvelopeIntersects.
- outSR parameter
- Specifies the spatial reference of returned geometry; omitting it returns data in the service's native coordinate system, which may mismatch other layers.
- WKID
- Well-Known ID, an integer identifier for a coordinate reference system such as 4326 for WGS 84 or 3857 for Web Mercator.
- Geodesic vs planar geometry
- Geodesic operations compute on the ellipsoid and suit large distances or high latitudes; planar operations assume a projected plane and suit local, small-extent analysis.
- Geocoding service
- A REST service with findAddressCandidates for forward geocoding, reverseGeocode for coordinates to addresses, and suggest for autocomplete; each call consumes credits.
- Routing service
- A service exposing solve for routes, closestFacility, serviceArea, and originDestinationCostMatrix, with travel modes and impedances controlling cost calculations.
- Geoprocessing service jobs
- Asynchronous tasks submitted to a GPServer; clients poll the job status until esriJobSucceeded or esriJobFailed, then fetch results by parameter name.
- ArcGIS Maps SDK for JavaScript
- The browser SDK (4.x) using ES modules with Map, View, layers, and widgets; it renders 2D and 3D content and calls ArcGIS services under the hood.
- ArcGIS Maps SDK for Python
- The arcgis Python package wrapping the REST API; a GIS object authenticates, items are retrieved by ID, and layers expose query and edit methods.
- ArcGIS Enterprise versus Online
- Both expose the same REST surface, but Enterprise runs on your own portal host under /arcgis/rest/services and can federate servers with portal identity.
- Branch versioning
- Feature service versioning for long transactions; clients pass gdbVersion in query and applyEdits requests to read and edit a named version.
- Sync capability
- A feature service setting enabling offline replicas and incremental edit synchronization; requires global IDs and is essential for offline field workflows.
- Editor tracking fields
- Automatically maintained attributes recording creator, editor, and timestamps for each feature, supporting audit trails and incremental data synchronization.
- CORS and proxy configuration
- Cross-origin rules govern browser calls to services; self-hosted deployments behind a proxy require configuring the SDK's proxy URL so requests route correctly.
- HTTP 429 and backoff
- The status returned when rate limits or quotas are exceeded; clients should retry with exponential backoff and chunk batch requests to stay within limits.
- Basemap styles service
- A service delivering basemaps by style name such as arcgis/streets or arcgis/imagery, requiring an API key or token and mapped to SDK basemap enums.