Skip To Content

Share a web elevation layer

You can share elevation layers from ArcGIS Pro to your active portal as web elevation layers. Web elevation layers can supplement the default Terrain3D elevation layer used in Scene Viewer with higher-resolution elevation data for your area of interest. Like other web layers, web elevation layers can also be added from your portal to ArcGIS Pro.

Any raster dataset that can be added as an elevation surface to ArcGIS Pro can be shared as a web elevation layer. Common surfaces include raster datasets stored in geodatabases and raster datasets stored in file formats such as TIFF, DTED, DEM, FLT, HGT, Esri Grid, or CRF with LERC compression. However, elevation surfaces based on TIN datasets and existing image services cannot be shared as web elevation layers.

Web elevation layers do not maintain any elevation surface properties that are set on the Appearance tab in ArcGIS Pro (for example, vertical exaggeration or surface color).

Note:

When you share a web elevation layer to an ArcGIS Enterprise portal, you can cache the layer on the server (the default) or locally. To cache the layer on the server, you need the privilege to publish server-based layers. To cache the layer locally, you need the privilege to publish hosted tile layers. See User types, roles, and privileges in the ArcGIS Enterprise help for more information.

When you share a web elevation layer to an ArcGIS Online portal, the layer is cached locally. You need the privilege to publish hosted tile layers. See User types, roles, and privileges in the ArcGIS Online help for more information.

Share a web elevation layer using the default configuration

  1. In the Contents pane, right-click the elevation source in your scene's ground surface that you want to share and click Share as Web Layer New 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. If you are sharing to ArcGIS Enterprise and want to reference registered data sources, choose Reference registered data. To copy the elevation source to the federated server, choose Copy all data.
  5. Use the Folder menu to specify where the web layer will be stored in your portal content. The web layer is stored in the root of your content by default. 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.
  6. If you are sharing to ArcGIS Enterprise, use the Server and Folder menu to specify the federated server where the service will be published and the folder on the server where it will be stored. If the folder does not already exist, type the name of the desired folder in the text box. The service is stored in the root folder by default.
  7. Note:
    If you chose a server other than the hosting server, the option to configure the elevation layer to Cache locally will not be available. To cache locally, choose the hosting server. If you specify a server folder when caching locally, your selection will be overridden and the service will be published to the hosted folder.
  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.
  11. Once validated, click Publish to share your web layer using the default configuration.

Configure a web elevation layer

You can configure your web elevation layer to use a specific tiling scheme, and determine where it is cached and what Limited Error Raster Compression (LERC) is used. When you select the tiling scheme, keep in mind that web scenes require all cached layers, including your basemap and elevation layers, to use the same tiling scheme. If you plan to use this web elevation layer with an existing basemap or elevation layer, use the same tiling scheme for all. For more information on web scene tiling scheme requirements, see Tiling scheme requirements in the basemap and elevation layers topic .

  1. Click the Configuration tab.
  2. Choose a Tiling Scheme that defines the desired 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:

    Same as basemap

    This is the default tiling scheme. Because web scenes require all cached services to use the same tiling scheme, the default is to use the tiling scheme of your scene's basemap. This ensures that the elevation layer will be able to be used in your current scene.

    Auto-suggest

    When sharing from a scene that does not have a basemap, this is the default tiling scheme.

    A tiling scheme is suggested based on the coordinate system of your scene. The levels of detail defined in this tiling scheme are valid for a global extent, so datasets in the same coordinate system that are cached using this tiling scheme can be displayed together in the future. Although the tiling scheme is valid for a global extent, only the extent defined in the map properties will be cached.

    This option is only available when sharing from a scene.

    ArcGIS Online/Bing Maps/Google Maps

    When sharing from a global scene that does not have a basemap, 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 256x256 pixels. Scale levels for caching range from 0 (zero) through 23.

    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 the WGS 1984 Geographic Coordinate System. The default tile width and height is 256x256 pixels. Scale levels for caching range from 0 (zero) through 22.

    CGCS2000 Geographic Coordinate System

    A tiling scheme based on China Geodetic Coordinate System 2000. The default tile width and height is 256x256 pixels. Scale levels range from 0 (zero) through 22. This option is only available from a global scene set to China Geodetic Coordinate System 2000.

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

    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 be imported from C:\Program Files\ArcGIS\Pro\Resources\TilingSchemes.

  3. If you are sharing to ArcGIS Enterprise and chose Reference registered data, choose Cache automatically on the server or Cache manually on the server. If you chose Copy all data, you can also choose Cache locally.
    1. If you are caching locally, specify a Temp cache location by typing a valid location in the text box. Alternatively, click the Browse button Browse and browse to the desired location. This location is where the tile package will be created, uploaded, and published.

      If you are sharing to ArcGIS Online, the web elevation layer will always be cached locally.

  4. Optionally change the LERC Compression value.

    The web elevation layer will be cached using LERC. Specify a tolerance value that represents the maximum allowable error per pixel in the units of the data. For example, if the dataset is in meters and you want to ensure accuracy within 10 centimeters, enter 0.1.

Considerations when sharing to older portals

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

Related topics