Share as web layers

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.

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:
   • マップ内の使用可能なすべてのレイヤーを Web レイヤーとして共有します。[共有] タブの [共有] グループで、[Web レイヤー] ドロップダウン矢印をクリックした後、[Web レイヤーの公開] をクリックします。
   • マップで選択したレイヤーを Web レイヤーとして共有します。[コンテンツ] ウィンドウでレイヤーを選択します。選択したレイヤーを右クリックして、[共有] をポイントし、[Web レイヤーとして共有] をクリックします。

   [Web レイヤーとして共有] ウィンドウが表示されます。

4. Web レイヤーの名前を指定します。
5. For Layer Type, click Feature.
6. アクティブなポータルが ArcGIS Enterprise であり、登録済みのエンタープライズ データベースのデータセットを参照する場合は、[登録済みデータを参照] をオンにします。[登録済みデータを参照] を有効にすると、マップ イメージ レイヤーが含まれます。

   メモ:

   Do not choose the Copy all data option.

7. [概要] フィールドと [タグ] フィールドに値を入力します。
8. Specify how the web layer will be shared:
   • [すべての人に公開] - このオプションを選択すると、コンテンツがパブリックになります。誰もがコンテンツにアクセスして表示することができます。
   • [組織] - このオプションを選択すると、コンテンツを組織内のすべての認証済みユーザーと共有できます。
   • [グループ] - このオプションを選択すると、所属するグループおよびグループのメンバーとコンテンツを共有できます。

   メモ:

   The Share with options will vary when sharing to ArcGIS Enterprise using the Reference registered data option.

   The following image is an example.

   

9. Click the Configuration tab.
10. Check the Linear Referencing check box under Capabilities.
11. Click Analyze to check for any errors or issues. You must resolve all errors.
12. 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	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, the version management capability should be turned on while publishing data.

Data preparation

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:

1. Do all data loading using ArcGIS Pro prior to changing your 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 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.

   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.

   

   ヒント:

   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.

   Learn more about registering data as branch versioned

4. All data layers in the database must have the following:
   • Global IDs, except for 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.

   • Enabled editor tracking with UTC time, except for 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, make sure UTC is chosen.

   メモ:

   Check other requirements before registering data as branch versioned.

5. Register the data layer in your database as branch versioned, except for the locks table. Right-click a feature class or table in the Catalog pane and click Manage > Register As Versioned to register it as branch versioned.

   メモ:

   If a new, unversioned feature class is added to the feature dataset after data from the feature dataset has been published as a service, re-register the feature dataset as versioned and restart the service.

   注意:

   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 is not available for use in ArcMap.

6. Enable time on your data layers.

   Learn more about setting the time view for LRS data and setting the time view for LRS data in a group.

   メモ:

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

Publishing your data

Once your version has been created and the data edited, you can publish the data.

1. 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.

2. On the Configuration tab, check both Linear Referencing and Version Management under Capabilities.

   

3. 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.
4. 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.