Share as web layers

Available with Location Referencing license.

Web maps can be authored from LRS and Version Management Service (VMS) enabled services published using ArcGIS Pro. You can choose to add these data layers: route network, event, centerline, calibration point, and redline. You can also zoom to the extent, choose a basemap, include a description of the map, and save it for use in the ArcGIS Event Editor web app.

Share as web layers with linear referencing and version management

Version management provides management capabilities for editing feature services such as the following:

• Creating, modifying, deleting, and switching to a feature service version
• Reconciling and posting edits from a child version to the default version
• Undoing, redoing, saving, and discarding individual edits that have been made on a feature service version in an edit session

Quick version management comparison

Purpose of sharing data	Required publishing capabilities	Geodatabase connection type
For multiuser editing scenarios when data is accessed directly from the enterprise geodatabase—also known as traditional versioning	Feature Layer, Linear Referencing	Traditional
For multiuser editing scenarios when data is accessed via feature services with undo and redo ability—also known as branch versioning	Feature Layer, Linear Referencing, Version Management	Branch

To perform editing activities using feature services, turn on the version management capability while publishing data.

Prepare data

Sharing web layers with linear referencing capability and version management requires data preparation. Use the following steps to prepare your data before publishing:

1. Perform all data loading using ArcGIS Pro before changing the geodatabase connection type (step 3) and registration (step 4).
2. Depending on whether your data is not versioned or is traditionally versioned, you must do the following:
   • If your data is not versioned, proceed to step 3.
   • If your data is traditionally versioned, unregister each feature class and table as versioned. In ArcGIS Pro, right-click each feature class or table in the Catalog pane and click Manage > Unregister As Versioned.

   Learn more about the differences between traditional and branch versioning in ArcGIS Pro

3. Your geodatabase connection must be explicitly set to the branch versioning connection type. Right-click the geodatabase in the Catalog pane and click Geodatabase Connection Properties. On the Geodatabase Connection Properties dialog box, choose Branch under Versioning Type.

   

   Tip:

   You can also change your geodatabase connection type to branch versioning using the Update Geodatabase Connection Properties To Branch tool.

   Note:

   The branch versioning option is only available for a 10.6 or later enterprise geodatabase.

   Learn more about registering data as branch versioned

4. All data layers in the database must have the following:
   • Global IDs, except the locks table.

     If Global IDs are not present, right-click a feature class or table in the Catalog pane and click Manage > Add Global IDs.

   • Editor tracking enabled with UTC time, except the locks table. To enable editor tracking, do the following:
     1. Right-click a feature class or table in the Catalog pane and click Properties.
     2. Click the Editor Tracking tab.
     3. Check the Enable editor tracking check box.
     4. In the Record dates in section, ensure that UTC is checked.

   Note:

   Check other requirements before registering data as branch versioned.

5. Enable time on your LRS data layers on a layer-by-layer basis or enable time for all the LRS layers in a map at once.

   Note:

   Once the data is published, you cannot set time filters for layers.

Publish data

Once your version has been created and the data edited, you can publish the data to your organization's portal as a web layer using the following steps:

1. Sign in to ArcGIS Pro with your portal credentials.

   It must be a portal with a federated ArcGIS Server site.

2. Create a map in an ArcGIS Pro project, and add the appropriate routes, event layers, calibration points, centerline, and optionally, a redline layer.
3. To share a web feature layer, do one of the following:
   • Share all usable layers in the map as a web layer. On the Share tab, in the Share As group, click the Web Layer drop-down arrow and click Publish Web Layer .
   • Share selected layers in the map as a web layer. Select the layers in the Contents pane. Right-click any selected layer, point to Sharing, and click Share As Web Layer .

   The Share As Web Layer pane appears.

4. Provide a name for the web layer.
5. Complete the Summary and Tags fields.

   You can enter a maximum of 128 tags.

6. Specify how the web layer is shared:
   • Everyone—Share your content with the public. Anyone can access and see it.
   • My Organization—Share your content with all authenticated users in the organization.
   • Groups—Share your content with groups to which you belong and their members.

   Note:

   The Share with options vary when sharing to ArcGIS Enterprise.

   

7. Click the Configuration tab.
8. On the Configuration tab, in the Capabilities section, check the Linear Referencing and Version Management check boxes.

   

9. Click Analyze to check for any errors or issues. You must resolve all errors before you can complete the publishing process.

   Note:

   Analyzers are used to validate the branch versioned dataset when publishing as a feature service. The following conditions are enforced by these analyzers:

   • ArcGIS Server 10.6 or later instances are supported.
   • If Version Management is enabled under Capabilities, all layers must be of the same registration type.
   • All data must belong to a branch workspace.
   • All data must be published from the default version.
   • The connected geodatabase user must be the owner of the data.
   • Definition queries must not be present.
   • All fields must be visible.
10. Once validated, click Publish to share your web layer.

Your layers are now published as a feature service with linear referencing and version management capability. ArcGIS Pro users with Portal credentials can now create child versions of your feature service and start editing.