You can share your map or selected map layers as a web layer. You can also share stand-alone tables. There are seven web layer types that can be shared from ArcGIS Pro: feature, tile, vector tile, map image, imagery, scene, and elevation. Feature, tile, vector tile, map image, and imagery layers share 2D data, while scene and elevation layers share 3D data. Tables share attribute data and are listed with the other layer types below.
When you share a web layer, a service is published and exposed through the web layer. Depending on the layer type and how it is configured, an ArcGIS Server service or a hosted service is published.
To share any content from ArcGIS Pro, you must have an account that is part of an ArcGIS organization that has the privileges to create, update, and delete content. The sharing of web layers requires additional privileges that vary depending on the layer type and how it's configured. If an ArcGIS Server service will be published, the privilege to publish a server-based layer is required. If a hosted service will be published, the privilege to publish the corresponding hosted layer is required.
When an ArcGIS Server service will be published, you can specify the federated server where the service will be published. To publish an ArcGIS Server service, access to the admin API must be possible through either the federated server's administration URL or services URL.
Before sharing a web layer, analyze your GIS resource to identify potential performance delays and errors. For more information, see Analyze your GIS resource.
During the sharing process, the web layer data is consolidated and prepared in a staging folder on a local drive. You can use the default staging folder or choose a different folder in the Share and download options.
You can continue to work with ArcGIS Pro while your sharing job is processing. You can even close ArcGIS Pro. You can monitor the status of your sharing jobs in the Job Status pane.
You can use ArcPy to automate sharing web layers. To learn more, see Introduction to arcpy.sharing.
A number of factors should be considered when determining the layer type to share, including how the layer will be used and whether your source data is accessible to the server.
Supports feature querying, visualization, and editing. Feature layers are appropriate for visualizing vector data on top of your basemaps. When sharing a feature layer that copies all data to ArcGIS Enterprise, the service will always be published to your hosting server. When sharing a feature layer that references registered data to ArcGIS Enterprise, it's shared as a dependent layer to a map image layer.
A feature layer exposes a feature service.
Supports fast map visualization using a collection of predrawn map images or tiles. These tiles are created and stored on the server after you upload your data. Web tile layers are appropriate for basemaps. When sharing a tile layer to ArcGIS Enterprise, the service will always be published to your hosting server.
A tile layer exposes a hosted, cached map service.
Supports fast map visualization using a collection of predrawn vector tiles. Although these tiles do not support raster data, they can adapt to the resolution of their display device and be restyled for multiple uses. When sharing a vector tile layer to ArcGIS Enterprise, the service will always be published to your hosting server.
A vector tile layer exposes a vector tile service.
Supports map visualization and feature querying. Map image layers can be drawn dynamically by the server or from tiles. Map image layers can only be shared to ArcGIS Enterprise. Map image layers can reference datasets in workspaces that have been registered with your federated server. When sharing a map image layer, the service can be published to any server that has been federated with the portal to which you have access. Additional layers and capabilities can be enabled; for more information, see Additional layers and capabilities.
A map image layer exposes a dynamic or cached map service.
Supports querying and visualization of point, 3D object, building, and point cloud data. When sharing a scene layer to ArcGIS Enterprise, the scene service will always be published to your hosting server.
3D object, building, and point scene layers can have an associated feature service that allows you to edit the scene layer.
A scene layer exposes a cached scene service.
Supports visualization, metadata, mensuration, and image processing to display data as a basemap or the results of analysis. Imagery layers can be shared to any server federated with ArcGIS Enterprise.
An imagery layer exposes a dynamic or cached image service.
Supports visualization, metadata, mensuration, and image processing of elevation data sources in the ground surface of a scene. The elevation layer is used in web scenes to display 3D content on a custom elevation surface. When sharing an elevation layer to ArcGIS Enterprise that is cached locally, the service will always be published to your hosting server. When cached on the server, the service can be published to any server federated with ArcGIS Enterprise.
An elevation layer exposes a cached image service that uses a LERC compression tiling scheme.
Supports viewing, filtering, and editing of table attributes.
A stand-alone table exposes a feature service.
Depending on your active portal, different layer types are available to share. Some layer types require packages to be created and uploaded depending on the active portal and the type of data being shared.
Layer types by active portal
|Active portal||Feature layer||Tile layer||Vector tile layer||Map image layer||Scene layer—3D Object||Scene layer—Points||Scene layer—Point cloud||Scene layer—Building||Imagery layer||Elevation layer||Stand-alone table|
|ArcGIS Enterprise 10.7 |
ArcGIS Enterprise 10.5 through 10.6.1
Portal for ArcGIS 10.4 and 10.4.1
Portal for ArcGIS 10.3.1
Portal for ArcGIS 10.3 or earlier
Select the layer type
When selecting the layer type, consider the following:
- If the layer will be used for editing workflows, select feature layer.
- If the data changes regularly and will not be used for editing workflows, select map image layer.
- If the data changes semiregularly, select map image layer and configure it to display using tiles from a cache.
- If the data is static vector data and will only be used for visualization, select vector tile layer.
- If the data is static raster data and will only be used for visualization, select tile layer.
- If you will be changing the visualization of your raster dataset dynamically on the client, share an imagery layer.
- If you need open source formats, select map image layer and include an associated WMS layer.
Reference registered data sources
If your active portal is an ArcGIS Enterprise portal, you can choose to share a web layer that references registered data or copies all data. Sharing to Portal for ArcGIS 10.4 and later also has these data options. If you want your web layer to reference data from data sources that are registered with your federated server, choose a layer type under Reference registered data. For more information on data registration, see Register your data with ArcGIS Server.
If you do not want the web layer to have access to the registered data source, choose a layer type under Copy all data. These layer types either use data copied to the server or drawn from caches on the hosting server. Web feature layers, web tile layers cached on the server, and map image layers will copy all layers in the map to the server, including registered data. Web tile layers and vector tile layers cached locally will upload a tile package to your portal.
A map image layer must be included to reference registered data. Map image layers are automatically included when you choose a layer type under Reference registered data.
- When sharing a map image layer that references registered data, the data source of each layer must be registered with the selected federated server. Layers with unregistered data sources will be copied as a file geodatabase onto the server.
If you choose to share a map image layer that copies all data instead, all data will be copied as a file geodatabase onto the server, including data from registered data sources.
- When sharing a feature layer that references registered data, all layers must have the same enterprise database as their data source. The database must be registered with the selected federated server. Edits made to your web feature layer and to your source data will be reflected in the source data and the web layer.
If you choose to share a feature layer that copies all data instead, all layers will be copied into your hosting server's managed database.
The following applies when sharing to Portal for ArcGIS 10.4.1 and earlier:
When the publisher's machine and the server are working with different geodatabases as the registered data source, referencing the registered data is not supported. If the publisher's machine and the server are working with different folders as the registered data source, referencing the registered data is supported.
Data sources can be registered with the portal's federated server before sharing; this can be done in the Manage registered data stores pane. For more information, see Manage registered data stores. Data sources can also be registered in the sharing pane by resolving analyzer warnings 24011 and 24012 or by resolving analyzer errors 00231 and 00232.
Decide on the data type
Consider the following when determining whether to share a web layer that references registered data or copies all data:
- If you want edits to your web layer or enterprise data to be dynamically displayed in the web layer and the source data, choose a layer type under Reference registered data.
- If your data source is registered with the federated server but you don't want the layer to reference your source data, choose a layer type under Copy all data. Your data will be copied to the server.
- If your active portal is ArcGIS Enterprise 10.5 or Portal for ArcGIS 10.4.1 or earlier and you will be using Collector or other sync-based workflows, share a web layer that copies all data. Feature layers that reference registered data sources do not support sync or export.
Preserve layer and table IDs
By default, the layer and table IDs of a service are not preserved when its web layer is overwritten. If you changed the ordering of the layers or added or removed layers, you must update any client applications, such as web maps, consuming the service to use the updated IDs. To avoid updating client applications, it is recommended that you author the map to preserve the layer and table IDs before sharing a map image layer or web feature layer.
To preserve layer and table IDs, follow these steps:
- Right-click the map in the Contents pane and click Properties .
- On the Map Properties dialog box, on the General tab, check Allow assignment of unique numeric IDs for sharing web layers and click OK.
Sequential IDs are assigned to each layer and table in the map.
- Optionally, assign custom IDs to layers and tables in the map.
- Right-click a layer or table in the Contents pane and click Properties .
- On the Layer Properties dialog box, on the General tab, type a custom integer ID in the Layer ID text box.
This ID can be any arbitrary integer. The IDs you specify do not need to be sequential.
- Repeat the previous two steps for each layer or table as necessary.
- Share the map as a map image layer or web feature layer. The IDs are preserved after publishing, eliminating the need to update client applications if the web layer is overwritten in the future.
You can share an entire map, a selection of layers, a group layer, or a single layer as a web layer from ArcGIS Pro. Both the web layer and the sublayers of the service exposed by the web layer can store metadata. The type of web layer selected will determine if only the web layer or both the web layer and the sublayers store metadata.
All web layers store the metadata of what was shared (entire map, group layer, and so forth) with the web layer item. A selection of layers does not have a single source for metadata, so only the summary and tags specified in the sharing pane will be stored with the web layer. Web layers that are cached locally will contain only the metadata content displayed by the Item Description style; all others will store the full metadata of the shared item. To add full metadata to web layers that are locally cached, import the metadata. For more information, see Copy or import metadata to an item.
|What is shared||Metadata source|
Selection of layers
Not applicable. Only the summary and tags specified in the sharing pane are stored with the web layer.
Group layer's metadata.
Map image and feature layers also store metadata with the sublayers of the service. Each sublayer exposes the full metadata of its corresponding ArcGIS Pro layer or table as it was authored in ArcGIS Pro. Layers and tables can be authored in the following two ways:
- Show metadata from data source (read-only)—References the dataset's metadata.
- Layer has its own metadata or Table has its own metadata—Uses metadata stored in the project that describes the layer or table.
When sharing to ArcGIS Enterprise, the selected data option also applies to the layer's metadata. This means if you authored a layer with Show metadata from data source (read-only) selected and you selected a layer under Reference registered data when sharing, changes to the dataset's metadata will automatically display in the sublayer's metadata.
As an example, an organization that manages information about trees maintained by the city is planning to use web maps to collect information from the public about trees that need attention. Volunteers regularly check and verify the crowdsourced information before delivering it to the city's tree maintenance department. They have two maps in ArcGIS Pro; one will be shared as a map image layer to be used as a basemap. The other map contains a tree layer that will be shared as a web feature layer to be used as an editable operational layer in the web map.
The basemap map's metadata contains general information about the tree maintenance program. The map contains multiple layers, including building footprints, streets, and the city boundaries. Each of these layers shows metadata from its data source. By sharing the entire map as a map image layer that references registered data, the web layer item will display the map's metadata (the general information about the tree maintenance program), and the sublayers will display the metadata from their original data sources. Any updates made to the data sources' metadata will automatically be reflected in the sublayers.
The tree layer has its own metadata. The data source's metadata was copied to the layer and modified to include information about how often the web layer will be updated and checked for accuracy. By sharing only the tree layer, both the web layer item and the sublayer of the service will contain the layer's metadata, including the modifications made to it. Any updates made to the layer's metadata will not be reflected in the web layer or sublayer until the web feature layer is overwritten.
For more information about authoring metadata, see View and edit metadata.