In ArcGIS Pro, you can author and share web elevation layers that are stored as items in your active portal. Each elevation source in your scene's ground surface will be published as a separate web elevation layer. The privilege to publish server-based layers is required to share a web elevation layer that is cached on the server.
The elevation surface properties Vertical exaggeration, Surface color, and Shade surface relative to the scene's light position are not maintained through the sharing process.
Share a web elevation layer
- In the Contents pane, right-click the elevation source in your scene's ground surface you want to share and click Share as Web Layer .
The Share as Web Layer pane appears.
- Provide a name for the web layer.
- Complete the Summary and Tags fields.
- If you are sharing to ArcGIS Enterprise and want to reference registered data sources, select Reference registered data. To copy the elevation source to the federated server, select Copy all data.
- Use the Folder drop-down menu to specify where the web layer will be stored in your portal content. Optionally click the browse button to create a folder or choose an existing one. You can also type the name of the desired folder in the text box.
- If you are sharing to ArcGIS Enterprise, 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.
- 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.
- Optionally click the Content tab to view the new web layer that will be created and all its components.
- 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
- Once validated, click Publish to share your web layer using the default configuration.
Note:If you selected a server other than the hosting server, the option to configure the elevation layer to Cache locally will not be available. To cache locally, select 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.
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 LERC compression is used. When selecting 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 Basemap and elevation layers.
- Click the Configuration tab.
- 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.
When sharing from a local 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 local 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 256 by 256 pixels. Scale levels for caching range from 0 (zero) through 23. When you initialize a new cache, ArcGIS Pro examines the layers in your GIS resource and selects a default tile image format. 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 0 (zero) through 22. When you initialize a new cache, ArcGIS Pro examines the layers in your map and selects a default tile image format. 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 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. 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've 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. The tile image format defaults 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.
- If you are sharing to ArcGIS Enterprise and selected Reference registered data, choose Cache automatically on the server or Cache manually on the server. If you selected Copy all data, you can also choose Cache locally.
- If caching locally, specify a Temp cache location by either typing a valid location in the text box or clicking and browsing to the desired location. This location is where the tile package will be created, uploaded, and published.
When sharing to ArcGIS Online, the web elevation layer will always be cached locally.
- Optionally change the LERC Compression value.
The web elevation layer will be cached using LERC (Limited Error Raster Compression). 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.