适用于 Location Referencing 许可。
Web maps can be authored using ArcGIS Pro. You can choose to add the data layers you intend to use, zoom to the extent, select a basemap, include a description of the map, and save it as your own item in Portal for ArcGIS for use in the Event Editor web application. Web maps can be authored and made editable by sharing with branch versioning enabled.
Share as web layers with linear referencing capability
You can share your web layers with the linear referencing capability.
- Sign in to ArcGIS Pro with your portal credentials.
It must be a portal with a federated ArcGIS Server site.
- Create a map in an ArcGIS Pro project, and add the appropriate routes, event layers, calibration points, centerline and optionally, a redline layer.
- To share a web feature layer, do one of the following:
- 将地图中的所有可用图层共享为 Web 图层。在共享选项卡的共享为组中，单击 Web 图层菜单下拉箭头，然后单击发布 Web 图层 。
- 将地图中的选定图层共享为 Web 图层。在内容窗格中选择这些图层。右键单击任何图层，指向共享，然后单击共享为 Web 图层 。
随即显示共享为 web 图层窗格。
- 提供 web 图层的名称。
- For Layer Type, click Feature.
- 如果活动门户为 ArcGIS Enterprise 且您想要引用注册企业级数据库中的数据集，请选中引用注册数据。启用引用注册数据后，将包含一张地图图像图层。
Do not choose the Copy all data option.
- Specify how the web layer will be shared:
The following image is an example.
- 所有人 - 该选项将您的内容变为公开状态。任何人均可访问并进行查看。
- 我的组织 - 此选项允许您与组织中所有经过身份验证的用户共享您的内容。
- 群组 - 您可以与您所在的群组以及群组中的成员共享您的内容。
The Share with options will vary when sharing to ArcGIS Enterprise using the Reference registered data option.
- Click the Configuration tab.
- Check the Linear Referencing check box under Capabilities.
- Click Analyze to check for any errors or issues. You must resolve all errors.
- Once validated, click Publish to share your web layer using the default configuration.
Your web layer is now published with linear referencing capability.
Share as web layers with linear referencing and version management
Version management provides management capabilities for editing feature services such as:
- 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||Capabilities needed while publishing||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
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
Sharing web layers with linear referencing capability and version management requires some data preparation steps. Use the following steps to prepare your data prior to publishing:
- Do all data loading using ArcGIS Pro prior to changing your geodatabase connection type (step 3) and registration (step 4).
- Depending on whether your data is not versioned or traditionally versioned, you must do the following:
- If your data is not using any versioning, proceed to step 3.
- If your data is already 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.
- 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.
You can also change your geodatabase connection type to branch versioning using the Update Geodatabase Connection Properties To Branch geoprocessing tool.
The branch versioning option is only available for 10.6 or later enterprise geodatabases.
- All data layers within the database must have:
- Global IDs, except locks, event behavior, and metadata tables.
If Global IDs are not present, right-click a feature class or table in the Catalog pane and click Manage > Add Global IDs.
- Enabled editor tracking with UTC time, except for the locks, event behavior, and metadata tables. To enable editor tracking, do the following:
- Right-click a feature class or table in the Catalog pane, and click Properties.
- Click the Editor Tracking tab.
- Check the Enable editor tracking check box.
- In the Record dates in section, make sure UTC is chosen.
Check other requirements before registering data as branch versioned.
- Global IDs, except locks, event behavior, and metadata tables.
- Register the data layer in your database as branch versioned, except locks, event behavior, and metadata tables. Right-click a feature class or table in the Catalog pane and click Manage > Register As Versioned to register it as branch versioned.
Once registered as branch versioned, data can no longer be edited when accessed directly from the database connection. Branch versioned data can only be edited through feature services.
You'll still be able to view the data when connected to the default version and make schema changes directly from the database connection.
Also note that to access the registered branch versioned dataset, the minimum client version is ArcGIS Pro 2.1. This also means that the dataset will no longer be available for use in ArcMap.
- Enable time on your data layers.
Publishing your data
Once your version has been created and the data edited, you can publish the data.
- Publish the data to your organization's portal as a web layer using steps 1 through 9 in the previous section of Share as web layers with linear referencing capability.
When creating a map in ArcGIS Pro, start with a new map and ensure all data in the map's layers is from a branch geodatabase.
- On the Configuration tab, check both Linear Referencing and Version Management under Capabilities.
- Click Analyze to check for any errors or issues. You must resolve all errors before you can complete the publishing process.
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.5 and earlier instances are not 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.
- 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 for ArcGIS credentials can now create child versions of your feature service and start editing.