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, then none of the pixels will be returned.

Applicable to all inputs.

Default resampling method

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)

Applicable to all inputs.

Allowed compression methods

The allowable compression methods for the image service. There are three possible compression types available:

• NONE
• JPEG
• LERC
• LZ77

A default JPEG Quality and LERC Tolerance can be set in the Configure Allow List dialog box.

The client can then choose which allowable compression method to use for transmission. This can be set in the Display tab in the Layer Properties dialog box.

This parameter is applicable only to clients that access image services via the SOAP GetImage method, for example, ArcGIS for 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.

Return JPGPNG as JPG

When the 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 be sure the image service is always transmitted using a smaller image size, check this box.

Applicable to all inputs.

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 down time, select this option to reflect data changes without restarting the service.

This property is only exposed in ArcGIS Server Manager and the ArcGIS REST API.

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 1,000.

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 a entity tag (ETag) and 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 this 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 completely 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 5 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.

This property is only exposed in ArcGIS Server Manager and the ArcGIS REST API.

Choose the cluster hosting the service

By default, every ArcGIS Server site has one cluster. If you have multiple server machines, you can configure them to operate in a cluster. Each cluster can be configured to run a dedicated set of services. The Choose the cluster hosting the service parameter allows you to select the cluster in which your image service will operate.

Directory

You can choose the output directory where you want the server to create temporary files. If you don't specify the output directory, the ArcGIS server will only return images as MIME data. By specifying an output directory, the returned images will also be accessible via a URL address.

Maximum number of rasters per mosaic

The maximum number of rasters that can be mosaicked per request. This will prevent the server from needing to open and perform processing on large numbers of rasters for a single request.

If the client's request requires more than this number of rasters to be accessed, then only this number of rasters will be accessed. None of the pixels for the additional rasters will be returned potentially resulting in gaps in the resulting image. It is recommended that overviews be built so that the client will not end up with gaps in the display.

Applicable to a mosaic dataset only.

Allowed mosaic methods

The allowable mosaic methods for the image service. The possible mosaic methods include the following:

• Closest To Center
• North-West
• Lock Raster
• By Attribute
• Closest To Nadir
• Closest To Viewpoint
• Seamline
• None

Applicable to a mosaic dataset only.

Maximum number of records returned per request

The limit on the number of records transmitted per transaction. If the user’s request exceeds this value, then the image returned uses the maximum allowed rasters.

Applicable to the mosaic dataset only.

Raster metadata level

The metadata that will be transmitted to the client:

• Basic—Metadata of the raster
• Full—Metadata of the raster and the raster functions that are applied to the raster
• None—No metadata

Applicable to the mosaic dataset only.

Allowed fields

This is a list of fields in the attribute table that are transmitted to the client. Uncheck the fields that you don't want a client to view or be able to use in a query.

Applicable to the mosaic dataset only.

Reference image

The reference raster dataset, mosaic dataset, or raster layer used to georeference the source raster dataset. For additional information, see Compute Tie Points in the ArcGIS REST API.

Maximum number of items downloadable per request

The maximum number of rasters that the user can download at one time.

Applicable to a mosaic dataset only.

Maximum download size per request

This is the total number of megabytes (MB) that can be downloaded at one time.

Applicable to a mosaic dataset only.

Allow downloading metadata files

Allows clients to download metadata files associated with the images.

This property is only exposed in ArcGIS Server Manager and the ArcGIS REST API.

Manage downloaded directories

Allows you to map the physical directories where the images are located to a virtual directory where the image URLs will be mapped.

When allowing download, it is critical that the service uses a directory that points to the source rasters of the mosaic dataset. This prevents a huge performance bottleneck that would otherwise occur as the service copies files from the mosaic dataset source directory to the server output directory.

The virtual directory provides web applications' access to files created by the ArcGIS server via a URL address. The virtual directory should point to the same disk location as the output directory. You must create the virtual directory in your web server and link it to the physical directory on disk. Refer to your web server documentation on how to create virtual directories.

Applicable to a mosaic dataset only.

Manage dynamic image workspaces

Directory location, accessible from the server and the mosaic dataset, where the raster data will be uploaded and stored. This must be set; otherwise, the editing operations cannot be used by the service.

Applicable to a mosaic dataset only.

Manage service workspaces

A folder that contains raster data that can be added to the image service mosaic dataset. Rasters can be added from many sources, including a file, folder, raster catalog, table, or web service.

Editor Info

Choose to add a realm to the user name when applying edits so they can be tracked. When you access a secured image service, ArcGIS for Server remembers the user's name and their edits. ArcGIS for Server will also append any realm that has been configured on the image service.

Applicable to the mosaic dataset only (with editor tracking enabled on the mosaic dataset).

Operations allowed on items added by other users

• Update—Allows clients to update the properties of the raster dataset they added to the image service.
• Delete—Allows clients to remove a raster item from an image service.

Applicable to a mosaic dataset only (with editor tracking enabled on the mosaic dataset).

Allowed types for add

Choose one or more raster types from which clients can pick when adding raster data to an image service.

Applicable to a mosaic dataset only.

Manage custom types

If you need clients to add data not defined by the basic raster types, you can select one or more raster-type files (.art).

Raster-type files can be created and edited in the Add Rasters To Mosaic Dataset tool by opening the raster type's properties and saving the file.

Applicable to a mosaic dataset only.

Allow client specified rendering rules

If checked, then clients can access and control the server-side rendering and processing. If unchecked, then the client cannot access and request any server-side rendering.

Applicable to all inputs.

Convert Colormap to RGB

If your raster dataset has a colormap, you can choose to publish it as an RGB image, thereby applying the colormap to the image. This will impact the pixel values since the values will be changed from a single value and associated colormap to a three-band pixel value. To retain the colormap and allow a user to query the pixel based on its colormap, you should not select this option.

This applies to raster datasets with a colormap, or when using a raster dataset layer or mosaic dataset using the Colormap function.

Applicable to all inputs.

Manage raster function templates

You can provide one or more function chains that can be used to process the data in the image service. When applied, these functions are applied on the server and the result is transmitted to the user or application.

These function chains are created in the Raster Function Template Editor and saved as .rft.xml files, created in ArcMap, that can be applied to the image service.

These are provided to allow web applications to perform various on-the-fly processing on the data in the image service.

You can choose a default function chain that is applied whenever the image service is used. This is especially useful when using an image service with data that looks better when it is stretched. ArcMap will apply a stretch, but web applications typically cannot; therefore, you can be sure it will always look the way you want if you define the stretch using a function chain.

Learn more about server-side processing

Applicable to all inputs.

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 tool can be used. These tools will be available with all the other options, except None.
• 3D—The 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.

Applicable to all inputs.

Elevation source

If there is a preferred and available elevation source that should be used when mensurating, you can point to it here. This will allow the user to make measurements in 3D.

Valid elevation sources include raster datasets, image service SOAP URLs, and image service layers. If the elevation image service requires authentication, then you should use an image service layer.

Applicable to all inputs.