Configure your image service before publishing to allow users to view the underlying data, compress the data for rapid visualization, and apply raster functions to render and display analytical results.
You can choose to extend your image service functionality by enabling capabilities, each with its own set of properties that you can configure. Enabling these optional capabilities may create additional services that work from or with your image service.
- In the Catalog pane or a catalog view, browse to the collection of servers in your project.
Right-click the ArcGIS Server connection that you'll publish to, click Publish, and click Image Service .
The Publish menu is only available on ArcGIS Server connections to stand-alone ArcGIS Server sites if the connecting user has privileges to publish services.
- In the Publish Image Service pane, on the Configuration tab, click the Configure Capabilities tab .
- Check each capability to enable for the image service, as necessary. Click Configure Service Properties next to each capability to access its properties. Click the Back button to revert to the Configuration tab main page.
Provides access to your map through REST and SOAP URLs. Always enabled.
Creates a service compliant with the OGC Web Map Service (WMS) specification.
Creates a service compliant with the OGC Web Coverage Service (WCS) specification.
Configure image service properties. Set the permissions that users will have when viewing your image service. Options include the following:
Maximum image size per request
The maximum number of pixel rows and columns that the server allows in a client request.
If the client's request exceeds this value, none of the pixels will be returned.
Default resampling method
Define the resampling method used in the request. The methods include the following:
- Nearest Neighbor (recommended for discrete data)
- Bilinear Interpolation (recommended for continuous data)
- Cubic Convolution (recommended for continuous data)
- Majority (recommended for discrete data)
The allowable compression methods for the image service. The following compression types are available:
You can set a default JPEG quality and LERC tolerance Once added to the stereo view, features are overlaid on top of the stereo model that is being viewed and are clipped to the stereo model. A feature added to the map is visible only if a source has been set.on the Configure Allow List dialog box.
The client can then choose which allowable compression method to use for transmission. You can set the compression method on the Display tab on the Layer Properties dialog box.
This parameter is applicable only to clients that access image services via the SOAP GetImage method; for example, ArcGIS Desktop and applications built with ArcObjects.
For clients accessing services via REST, compression is applied automatically based on the requested format type, regardless of the defined compression methods.
Specify the compression method used as the default from the drop-down list. The default is JPEG.
Edit the quality by typing a value from 0 to 100. A value of 80 tends to retain image quality while providing approximately eight times compression.
Represents the maximum error value that is applicable per pixel (not an average for the image). This value is specified in the units of the mosaic dataset. For example, if the error is 10 centimeters and the mosaic dataset is in meters, type 0.1.
Maximum samples count
This generates sample point locations, pixel values, and corresponding spatial resolutions of the source data for a given geometry. By default, the maximum number of sample locations is 1000.
Cache control max age
When clients send requests to ArcGIS Server to display an image service, the response from the server is typically cached by the browser and reused for a certain period of time. This behavior helps ArcGIS Server achieve the best possible display performance for your image service. However, depending on how your image service and its associated data are used in applications, you may consider adjusting the length of time the browser will use a response in its cache.
ArcGIS Server image service responses include an entity tag (ETag) and a Cache-Control header. The ETag header value is a unique identifier of the response. The Cache-Control header has a max-age value that provides information to the browser regarding the maximum time period for which it can reuse a response from the browser's cache. This is controlled by the Cache control max age property.
When a request is repeated and the maximum age of the cache has not expired, the browser will use the cached response without sending the request to the server. If the maximum age has expired, the browser must send the request to the server and set an IF-NONE-MATCH header with an associated ETag value corresponding to the response in its cache. ArcGIS Server evaluates the request and uses the ETag value to determine if the response has changed. If the response from the server is different from the copy on the browser, the server will send a new response to the browser. If the response is identical to the copy on the browser, the server alerts the browser to continue to use the response in its cache.
As an ArcGIS Server administrator, you can define this property to specify how long a browser is allowed to use a cached response. By mitigating the need for ArcGIS Server to send a full response, you allow your browser caches to be more efficient, help optimize your applications, and save network bandwidth.
The default value for image services is 12 hours (43200 seconds). This means that if a request is repeated within 12 hours, the browser will use the response from its cache. This value works well for most applications.
For image services with frequently changing datasets or symbology, a value such as five minutes (300 seconds) is recommended. In applications with animations or time-aware data, you should consider increasing the value to give your application a smoother animation experience.
Return JPGPNG as JPG
When a user requests the image using the JPGPNG format, if there is transparency, a PNG is returned; otherwise, a JPG is returned. The PNG is often much larger than the JPG and thus can take longer to transmit. If transparency is not necessary and you want to ensure the image service is always transmitted using a smaller image size, check this check box.
Has live data
When new rasters are added to the mosaic dataset of an image service, the image service information—such as source resolution, spatial extent, multidimensional information, and time extent—may become outdated. You can restart the service to reflect data changes. However, if you cannot incur any downtime, choose this option to reflect data changes without restarting the service.
Allow client specified rendering rules
If selected, clients can access and control the server-side rendering and processing. If you do not select this option, clients cannot access or request any server-side rendering.
Select the function chains to publish with the image service.
Select a processing template that will be used as the default to display the data.
The default is None.
Allowed mensuration methods
These allowed methods are derived from the source's mensuration capabilities and listed as part of the dataset's properties. They determine the mensuration tools that can be used with the image service.
- Basic—The Distance, Area, Point Location, and Centroid Location mensuration tools can be used. These tools are available with the other options as well (except None).
- 3D—Measurements made using the tools available with the Basic option can be modified using a DEM.
- Height—The sensor model exists for datasets within the mosaic dataset; therefore, the Height: Using Base To Top mensuration tool can be used.
- Shadow—The sensor model and sun angle information exists for datasets within the mosaic dataset; therefore, the Height: Using Base To Top, Height: Using Base To Top Shadow, and Height: Using Top To Top Shadow mensuration tools can be used.
- None—The user will not be able to use the mensuration tools in ArcGIS with this dataset. This is the default.
Applicable to all inputs.
- Click the Analyze button to verify your settings. Review any messages.
- Click the Publish button to publish your image service to the stand-alone image server.
Configure cached image service properties
You can configure your cached image service before publishing to specify a tiling scheme, the level of detail to cache, and when and where to build the cache.
Antialiasing options set for the application on the Display tab of the Options dialog box located on the Project tab, are applied when you publish a cached image service. The default antialiasing mode is Best.
- In the Publish Image Service pane, on the Configuration tab, click the Configure Capabilities tab .
- Click the Configure Service Properties button next to the Imagery capability.
- Under Layer Drawing, choose how the image service will be drawn:
Dynamically from data
Data is retrieved and drawn each time it is requested. This is the default option.
Using tiles from a new cache
Data is drawn from cached images generated at map scales you define.
Using an existing cache
Data is drawn from tiles previously generated on the server. To associate an existing cache with the image service, the name and server folder of your image service must match the name and server folder of the existing cache.
The Using an existing cache option searches for a disassociated cache with the same name and server folder as your image service. A cache is disassociated from a service if the service was deleted or if the cache was copied to the cache directory. If an eligible cache is found on the server, it is used to draw the image service. The image name, spatial reference, and extent must match the cache for the service to draw correctly.
If you use tiles from a new or existing cache, additional settings may be available in the pane. Continue with the following substeps:
- Click the Tiling Scheme drop-down arrow and choose a tiling scheme for your cache.
Choose a tiling scheme that defines the scale levels, tile dimensions, and tile origin for the cache. These properties define where tile boundaries will exist and are important to match when overlaying caches. Tiling scheme options include the following:
Option Description ArcGIS Online/Bing Maps/Google Maps
The coordinate system of the image service is reprojected on the fly to WGS 1984 Web Mercator (Auxiliary Sphere) to ensure your tile service overlays with these online services. The default tile width and height is 256 by 256 pixels. Scale levels for caching range from 0 to 23. When you initialize a new cache, ArcGIS Pro examines the service in your GIS resource and selects a default tile image format for you. If your GIS resource contains only vector layers, the default is PNG. If at least one raster layer is detected, the default is MIXED.
WGS 1984 Geographic Coordinate System, Version 2
A tiling scheme based on the WGS 1984 Geographic Coordinate System. The coordinate system of the image service is reprojected on the fly to WGS 1984 Geographic Coordinate System. The default tile width and height is 256 by 256 pixels. Scale levels for caching range from 0 to 22. When you initialize a new cache, ArcGIS Pro examines the service and selects a default tile image format for you. If your GIS resource contains only vector layers, the default is PNG. If at least one raster layer is detected, the default is MIXED.
Existing cached map/image service
Use an existing hosted or ArcGIS Server web tile layer or an ArcGIS Server image service as the tiling scheme of your tile service. When you choose this option, the tiling scheme XML file associated with the existing service is downloaded to C:\Users\USERPROFILE\My Documents\ArcGIS\TilingSchemes\Downloaded. ArcGIS Pro will honor the parameters specified in the existing service, with the exception of antialiasing. Antialiasing options set for the application are used.
Tiling scheme file
Import a custom tiling scheme XML file you have created that contains your preferred scales and settings. Use the Generate Map Server Cache Tiling Scheme geoprocessing tool to create a custom tiling scheme XML file. Additional tiling scheme files can also be imported from C:\Program Files\ArcGIS\Pro\Resources\TilingSchemes. The tile image format will default to PNG if the tile image format is not defined in the tiling scheme file. ArcGIS Pro will honor the parameters specified in the tiling scheme file, with the exception of antialiasing. Antialiasing options set for the application are used.
A tiling scheme is suggested based on the spatial reference of your data. The levels of detail defined in this tiling scheme are valid for a global extent, so any image services cached using this tiling scheme can be displayed together. Although the tiling scheme is valid for a global extent, only the extent defined in the map properties is cached.
In ArcGIS Pro 1.1 and 1.2, a previous version of the WGS 1984 Geographic Coordinate System tiling scheme was available. An improved version of this tiling scheme, with higher registration accuracy at higher resolutions (detailed scales), has replaced the old tiling scheme as WGS 1984 Geographic Coordinate System, Version 2.
Cached services that use the old tiling scheme cannot be displayed with cached services that use the new tiling scheme in certain clients due to differences in the tiling schemes. If you need to continue using the old tiling scheme, choose Existing cached map/image service for your Tiling Scheme and browse to a service that uses the old tiling scheme.
- Use the sliders to set the Levels of Detail property. ArcGIS Pro examines the dependencies in your map or service and attempts to suggest a minimum and maximum range of scales for caching. Depending on your map or service, you may want to forego caching some of the extremely large or small scales in your tiling scheme.
- The Maximum source cell size controls the base cell size of the cache. Above the maximum source cell size, the cache tiles will be created by resampling existing cache tiles. Below the maximum source cell size, the cache tiles will be created using the data from the source imagery.
- Under Options, choose when and where to build the cache. The default setting is to build the cache automatically on the stand-alone image server.
Use the reported Estimated cache size under Estimate to help make this choice.
Cache automatically on the server
If the cache is small, it is easiest to build the whole cache automatically. This is the default setting.
Cache manually on the server
If the cache is large, it is wise to build the cache manually in phases, caching the largest scales at selected areas of interest that are most likely to be visited. You can manually build the cache from the ArcGIS Online website or ArcGIS Enterprise website.
- Specify the Cache directory to store the data cache.
- Optionally, check the Allow clients to export cache tiles check box if you want clients to be able to download tiles from the server for offline use.
When this option is on, you can specify a value in the Limit export to box to limit the number of tiles that can be downloaded in a single request.
- Optionally under Estimate, click Calculate to estimate the cache size. On the Estimate Cache Size dialog box, click the drop-down arrow and choose Good or Best for the estimation quality. Click the Start estimating cache button . The number of tiles and storage space are estimated for each cached level of detail and totaled. Click OK.
The default static estimate is based on a general assumption about average tile size and does not consider the specific properties of your map. When you estimate the cache size, sample tiles of your map are built. This means that the tiling scheme, image format, and compression are taken into account (as is LERC compression for elevation layers). If an area of interest is specified as the caching extent, the area of interest is estimated.
The best estimate creates more sample tiles and takes longer to calculate than the good estimate. To cancel the estimation process, click Stop estimating cache . If you adjust the tiling scheme after estimating the cache size—for example, if you change the levels of detail or the image format—the quality estimate on the sharing pane reverts to static. You need to estimate the cache size again.
- Click the Tiling Scheme drop-down arrow and choose a tiling scheme for your cache.
- Click the Back button to revert to the Configuration tab main page.
- Optionally include additional capabilities by checking the check box next to the capability. For more information, see Additional services and capabilities.
Additional services and capabilities
When publishing an image service to a standalone ArcGIS Server, you can enable additional services and capabilities. Enabling some of these will turn on functionality available through the service. Some capabilities require a specific layer or data source to be present in your map; if the required layer or data is not present, the check box will be hidden.
When sharing to a federated server that has a server object extension (SOE) or server object interceptor (SOI), that capability is available. You must select the federated server with the SOE or SOI to see the capability listed. ArcGIS Server Manager should be used to update the order of SOI execution after the web layer has been shared.
Enabling an Open Geospatial Consortium (OGC) layer requires that the layers be shared publicly for the OGC layers to draw correctly.
Enabling Web Coverage Service (WCS) allows you to serve raster datasets according to the OGC WCS specification.
A WCS service returns data in a format that can be used as input for analysis and modeling. This is in contrast with the OGC Web Map Service (WMS), which only returns a picture of the data. The raster datasets made available through WCS services are referred to as coverages. These should not be confused with the vector datasets available in previous versions of ArcGIS, which were also known as coverages.
WCS services are useful if you want to make your raster datasets available online in an open, recognized way across different platforms and clients. Any client built to support the WCS 1.0.0, 1.1.0, 1.1.1, 1.1.2, and 2.0.1 specifications can view and work with your service.
For more information on modifying WCS properties, see Available WCS service properties.
Enabling Web Map Service (WMS) allows you to serve dynamic maps according to the OGC WMS specification.
WMS services are useful if you want to make your maps available online in an open, recognized way across different platforms and clients. Any client built to support the WMS specification can view and work with your service. Four versions of the WMS specification have been published so far: 1.0.0, 1.1.0, 1.1.1, and 1.3.0 (most recent).
To learn about the properties you can set, see Available WMS service properties.