Skip To Content

Web imagery layer

From ArcGIS Pro, you can author and share web imagery layers to ArcGIS Enterprise. These web layers will expose the selected raster dataset. The default configuration will allow users to view the dataset and its associated metadata. The privilege to publish server-based layers is required to share a web imagery layer.

Tip:

Web imagery layers are shared from the Catalog pane, not the Contents pane.

Share a web imagery layer

  1. To share a web imagery layer, right-click a raster dataset in the Catalog pane and click Share as Web Layer Share as web layer.

    The Share As Web Layer pane appears.

  2. Provide a name for the web layer.
  3. Complete the Summary and Tags fields.
  4. Choose Reference registered data or Copy all data. Choosing Copy all data will create a copy of the dataset on the server.
  5. Accept the default Layer Type option, Imagery.
  6. Use the Folder drop-down menu to specify where the web layer will be stored in your portal content. Optionally click the browse button Browse to create a folder or choose an existing one. You can also type the name of the desired folder in the text box.
  7. Use the Server and Folder drop-down menu to specify the federated server where the service will be published and the folder on the server where the service will be stored. If the folder does not already exist, type the name of the desired folder in the text box.
  8. Specify how the web layer will be shared:
    • My Organization—This option allows your content to be shared with all authenticated users in the organization.
    • Everyone—This option makes your content public. Anyone can access and see it.
    • Groups—You can share your content with groups you belong to and their members.
  9. Optionally click the Content tab to view the new web layer that will be created and all its components.
  10. Click Analyze to check for any errors or issues. You must resolve all errors. If any issues are discovered, they appear on the Messages tab. Right-click each message to get more information, read the help for the error or warning, and access suggested fixes. Learn more about analyzing GIS resources
  11. Once validated, click Publish to share your web layer using the default configuration.
  12. Once the web layer has been successfully published, click the Manage the web layer link to manage the web imagery layer.

Configure a web imagery layer

By default, querying pixel values is not enabled for web imagery layers. You can configure your web imagery layer prior to 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.

  1. Click the Configuration tab. If your active portal is ArcGIS Enterprise, click Configure Web Layer Properties Configure Web Layer Properties to access the configurable properties.
  2. Set the permissions that users will have when viewing your web imagery layer. 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

    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)

    Allowed compression

    The allowable compression methods for the image service. The following compression types are available:

    • NONE
    • JPEG
    • LERC
    • LZ77

    You can set a default JPEG quality and LERC tolerance in 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.

    Default compressions

    The compression method used as the default.

    JPEG quality

    Edit the quality by typing a value from zero to 100. A value of 80 tends to retain image quality while providing approximately eight times compression.

    LERC tolerance

    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 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 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.

    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 twelve 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, select 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 down time, 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.

    Processing templates

    Select the function chains to publish with the web imagery layer.

    Default template

    The processing template that will be used as the default to display the data.

    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.

    Applicable to all inputs.

  3. Once the web imagery layer has been successfully published, click the Manage the web layer link that appears in the Sharing pane. Sign in to your organization to view the item if it was not shared publicly.

Configure a cached web imagery layer

You can configure your cached web imagery layer prior to publishing to specify a tiling scheme, the level of detail to cache, and when and where to build the cache.

Note:

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 web tile layer. The default antialiasing mode is Best.

  1. Click the Configuration tab. If your active portal is ArcGIS Enterprise, click Configure Web Layer Properties Configure Web Layer Properties to access the configurable properties.
  2. 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:
    ArcGIS Online/Bing Maps/Google Maps

    This is the default tiling scheme. The coordinate system of the web layer is reprojected on the fly to WGS 1984 Web Mercator (Auxiliary Sphere) to ensure your web tile layer overlays with these online services. The default tile width and height is 256 by 256 pixels. Scale levels for caching range from zero to 23. When you initialize a new cache, ArcGIS Pro examines the layers 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 web layer 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 zero to 22. When you initialize a new cache, ArcGIS Pro examines the layers in your map 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 web tile layer. 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.

    Web tile layers that are published when a web map is shared will automatically use the tiling scheme associated with the web map's basemap.

    Legacy:

    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 web layers that use the old tiling scheme cannot be displayed with cached web imagery layers 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.

  3. Use the sliders to set the Levels of Detail property. ArcGIS Pro examines the dependencies in your map or layer and attempts to suggest a minimum and maximum range of scales for caching. Depending on your map or layer, you may want to forego caching some of the extremely large or small scales in your tiling scheme.
  4. Choose when and where to build the cache. The default setting is to build the cache automatically on the server. Use the reported Estimated cache size to help you 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.

  5. 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.

Considerations when sharing to older portals

Web imagery layers cannot be shared to Portal for ArcGIS 10.3.1 or earlier.

Related topics