Publish a web elevation layer from a cache dataset

With ArcGIS Pro, you can publish web elevation layers that reference elevation cache datasets (.tiles) in folders or cloud stores to ArcGIS Enterprise 11.0 or later. Sharing web layers from cache datasets uses minimal resources and is an efficient way to publish large data. When a web elevation layer is published, the ready-to-serve cache is referenced rather than built and stored on the server.

The privilege to publish server-based layers is required for this workflow.

If you want to share a web elevation layer from a scene instead, see Share a web elevation layer.

Prepare an elevation cache dataset

Before publishing a web elevation layer, you must create a cache dataset containing elevation content and register its folder or cloud store with your portal's federated server.

Follow these steps to prepare an elevation cache dataset:

  1. Use the Extract Package geoprocessing tool with the desired tile package (.tpkx) to create a cache dataset (.tiles) in a file share or cloud store.

    Ensure you specify a tile package created from a raster dataset that represents elevation data and uses a LERC compression tiling scheme. For more information, see Share a tile package.

  2. Register the folder or cloud store with a server that is federated with your portal. For more information, see Manage registered data stores.

Publish a web elevation layer

Follow this workflow to publish a web elevation layer from a cache dataset:

  1. In the Catalog pane, right-click an elevation cache dataset (.tiles) in a folder or cloud store and click Share As Web Layer Publish Web Layer.

    The Share As Web Layer pane appears.

  2. Accept the default name or provide a new name for the web layer.

    The default name is the name of your cache dataset.

  3. Optionally, complete the Summary and Tags fields.

    You can enter a maximum of 128 tags.

  4. Under Layer Type, click Elevation.
  5. Under Location, use the Portal Folder drop-down menu to choose a folder in your portal content in which to store the web layer. Optionally, create a folder.

    By default, the web layer is stored at the root level of your portal content.


    Click the Browse button Browse to browse to a folder in your portal content. You can also type a folder name in the text box.

  6. Use the Server and Folder drop-down menus to specify the federated server where the service is published and the folder where it is stored. Optionally, create a folder.

    By default, the service is stored in the root folder of the server.


    You can click the Data Stores button Data Stores to open the Manage Registered Data Stores pane. Use this pane to register folders and cloud stores with federated servers.

  7. Under Share with, specify how the web layer will be shared:
    • Everyone—Share your content with the public. Anyone can access and see it.
    • My Organization—Share your content with all authenticated users in your organization. This option is available when you are signed in with an organizational account.
    • Groups—Share your content with groups to which you belong and their members.

    Leave all options unchecked to set the sharing level to the owner of the item.

  8. Optionally, click the Content tab to view the folder and new web layer.
  9. Under Finish Sharing, click Analyze Identify potential performance bottlenecks and errors to review for potential problems.

    Errors and warnings are listed on the Messages tab. Right-click a message to open its help topic or take corrective action in the software. Errors Error must be resolved before you can share your GIS resource. Resolving warnings Warning is recommended but not required.

    Learn more about analyzing GIS resources

  10. After you resolve errors, and optionally, resolve warnings, click Publish Publish to share the web layer.
  11. Optionally, click Jobs Open Job Status Pane to monitor the job status.
  12. When the web layer is successfully published, click the Manage the web layer link at the bottom of the pane to access the web layer in your portal.