An image service supports accessing data as static tiled images and dynamically generated images. This section provides an overview of these formats and the functionality they provide.
Static image tiles
An image service supports accessing data as static tiles. Static tiles are cached (pre-generated) tiles that also include additional data such as the source pixel values. They are stored as LERC2D, JPEGPLUS, or JPGPNG tiles. You typically use a hosted tiled imagery layer (item) to access the tiles of an image service.
Below is an example of displaying the tiles of an image service in a map using a hosted tiled imagery layer (item).
The service URL format to access the tiles is:
https://{host}/{organizationId}/arcgis/rest/services/{serviceName}/ImageServer/tile/{level}/{row}/{column}https://{host}/{webadaptor}/rest/services/hosted/{serviceName}/ImageServer/tile/{level}/{row}/{column}Dynamic images
An image service supports accessing data as dynamically generated images. Dynamic images are generated for every request to the service returning a new image along with metadata, such as the image's URL, extent, width, and height. You can change the functions and parameters per request. This allows you to create multiple image products on demand from a single source. The default format of the returned image is jpgpng, but other formats such as png, jpg, bmp, tif, and lerc are supported. You typically access a hosted imagery layer (item) to use dynamically generated images from an image service.
Below is an example of accessing dynamically generated images from an image service using a hosted imagery layer (item).
The service URL format to access images dynamically is:
https://{host}/{organizationId}/arcgis/rest/services/{serviceName}/ImageServer/exportImage?{parameters}https://{host}/{webadaptor}/rest/services/hosted/{serviceName}/ImageServer/exportImage?{parameters}Service data comparison
The table summarizes the main distinctions between dynamic and tiled imagery layers in ArcGIS:
| Feature | Dynamic Imagery Layer | Tiled Imagery Layer |
|---|---|---|
| Display performance | Slower | Optimized |
| Perferred use case | Dynamic visualization & Analysis | Visualization & Analysis |
| Visualization Control | Extensive control over visualization post-creation | Visualization choices made prior to creation |
| Flexibility | Can modify properties like display order and visibility | Pre-rendered tiles with limited post-creation customization |
| Additional Functionality | Advanced options for controlling input images | Optimized for fast rendering but limited customization |
| Sharing | Private | Public & Private |
Services
Feature service
Add, update, delete, and query feature data.
Vector tile service
Store and access vector tile data.
Map tile service
Store and access map tile data.
Image service
Store and access imagery and raster data.
API support
Use data management tools or Client APIs to create, manage, and access data services. The table below outlines the level of support for each API.
- 1. Use portal class and direct REST API requests
- 2. Access via ArcGIS REST JS
- 3. Requires manually setting styles for renderers