Not all data sources are supported by web layers, web maps, and web scenes. A layer in a map or scene uses an unsupported data source. The <value> parameter identifies the layer.
Solutions
Do one of the following:
- Replace the unsupported data source with a supported database feature class.
- Do nothing. The unsupported layer will be excluded from the web layer, web map, or web scene.
More information
Unsupported layer types usually fall into one of the following categories:
- Map notes—Map notes are not supported when sharing as a web scene or web layer. Use the Copy Features tool to copy a map notes layer to a new feature class.
- Service layers—Although this warning can occur with any service layer, it most commonly occurs with a basemap layer when you share the contents of a map as a web layer. In this case, do nothing; the basemap layer will be excluded, and all other layers will be shared.
- WCS layers—WCS layers are not supported in web maps.
- TIN layers—TIN layers are not supported as elevation surfaces in web scenes.
- CAD layers—To share CAD layers, the source data must be converted to feature classes. For more information, see CAD data as ArcGIS Pro layers.
- ENC layers—ENC layers are not supported in web maps.
- Revit layers—Revit layers are only supported for sharing as a web scene layer to ArcGIS Online or ArcGIS Enterprise 10.7 or later.
- VPF layers—To share layers with a VPF data source, the source data must be converted to feature classes.
- Voxel layers—Voxel layers are only supported for sharing as a web scene layer to ArcGIS Online, ArcGIS Enterprise 11.0 or later, or ArcGIS Enterprise on Kubernetes 11.1 or later.
- Subtype group layers—Sharing subtype group layers is not supported as the following:
- Web feature layer that copies all data to ArcGIS Enterprise 11.1 or earlier
- Web tile layer to ArcGIS Enterprise 10.8.1 or earlier
- Vector tile layer with an associated web feature layer
- Catalog layers—Sharing catalog layers is only supported as the following:
- Web feature layer that copies all data to ArcGIS Online and ArcGIS Enterprise 11.1 or later
- Map image layer and web feature layer to ArcGIS Enterprise 11.2 or later
- Oriented imagery layers—Oriented imagery layers are only supported for sharing as the following:
- Web feature layer to ArcGIS Online
- Map image layer and web feature layer to ArcGIS Enterprise 11.2 or later
- 3D object feature layers—3D object feature layers are only supported for sharing as a web scene layer to ArcGIS Online and ArcGIS Enterprise 11.1 or later. 3D object feature layers (V1) must be upgraded using the Upgrade Dataset tool.
- Tile packages and vector tile packages—These packages cannot be shared as part of a web layer, web map, or web scene. Replace the package with the source data used to create the package.
- Scene layer packages—All scene layer packages can be shared as part of a web scene to ArcGIS Online. Support for sharing to ArcGIS Enterprise depends on the version.
- Integrated mesh, multipatch, and point scene layer packages are supported for sharing to ArcGIS Enterprise 10.5 or later.
- Point cloud scene layer packages are supported for sharing to ArcGIS Enterprise 10.5.1 or later.
- Building scene layer packages are supported for sharing to ArcGIS Enterprise 10.7 or later.
- SQLite data—Data in an SQLite database must be converted to a file or enterprise geodatabase feature class before sharing.
- Cloud data warehouses—Sharing query layers from cloud data warehouses as a map image layer or web feature layer that copies all data, a tile layer, a vector tile, a web scene layer, or a map service is not supported. You can only publish data from cloud data warehouses as map image layers that reference registered data to ArcGIS Enterprise 10.9.1 or later.
Sharing query layers from the following cloud data warehouses as web feature layers is only supported to the corresponding portal versions:
- Google BigQuery—ArcGIS Enterprise 11.0 or later
- Snowflake—ArcGIS Enterprise 11.1 or later
- Amazon Redshift—ArcGIS Enterprise 11.2 or later
It's not practical to provide a complete list of supported data sources because the list is long and must be qualified depending on the output web layer type and on your portal or server configuration. A general guideline is to convert unsupported data sources to feature classes using tools in the Conversion toolbox.
For more information, see Analyze your GIS resource.