Events data model

Location Referencing ライセンスで利用可能です。

Events are managed in ArcGIS Pipeline Referencing in feature classes called event feature classes, which are registered in the same geodatabase as the LRS.

Pipeline Referencing manages the shape of the feature based on the route, measure, and to and from dates. The required source event data differs depending on the event type being registered. The required fields for each event type are listed in the following sections.

注意:

Event feature classes can be modeled in advance or created when registering the event in the LRS. If modeled in advance, ensure that the spatial reference and x,y-, z-, and m-tolerance and resolution of the event feature class match that of the network in which it's registered.

Learn more about tolerance and resolution settings for the LRS

Minimum event fields

The minimum event fields are as follows:

FieldData typeLengthIs nullableDescription

Event ID

String

Between 32 and 255

No

The unique ID for each event record.

Route ID

String or GUID

Same type and length as the Route ID field in the Centerline Sequence table

No

The unique ID for each route in the network.

Route Name (if configured)

String

255

No

The unique name for the route.

To Route ID (required for event feature classes that store events that span routes)

String or GUID

Same type and length as the Route ID field in the Centerline Sequence Table

No

The unique ID for the to route in the network.

From Date

Date

8

Yes

The date that the event becomes active on the route.

To Date

Date

8

Yes

The date that the event is retired on the route.

Measure (point events only)

Any Numeric

No

The measure on the route where the event is located.

From Measure (line events only)

Any Numeric

No

The measure on the route where the beginning of the event is located.

To Measure (line events only)

Any Numeric

No

The measure on the route where the end of the event is located.

Location Error

String

100

Yes

The location error for the event.

Event referent fields

When registering events, you can store the event location based on its offset from another location. The offsets can be based on x- and y-coordinates, a station, the distance from the beginning of an event, other LRS events, intersections, or another point feature class.

You can use the Enable Referent Fields tool to enable storing referent locations with an event. The following fields are required:

FieldData typeLengthIs nullableDescription

Referent Method (point events only)

Short Integer

5

Yes

The method for referencing the offset feature. This can be x,y coordinates, stationing, length, LRS Network, event, intersection, or other point feature classes.

Referent Location (point events only)

String

Between 50 and 255

Yes

The location of the offsetting feature. This can be an x,y coordinate, feature or event ID, or intersection ID.

Referent Offset (point events only)

String

Between 50 and 255

Yes

The offset measure. This is saved in the unit of measure configured when registering an event and configuring the offset fields.

From Referent Method (line events only)

Short Integer

5

Yes

The method for referencing the offset feature. This can be x,y coordinates, stationing, length, LRS Network, event, intersection, or other point feature classes.

From Referent Location (line events only)

String

Between 50 and 255

Yes

The location of the offsetting feature. This can be an x,y coordinate, feature or event ID, or intersection ID.

From Referent Offset (line events only)

String

Between 50 and 255

Yes

The offset measure. This is saved in the unit of measure configured when configuring offset fields.

To Referent Method (line events only)

Short Integer

5

Yes

The method for referencing the offset feature. This can be x,y coordinates, stationing, length, LRS Network, event, intersection, or other point feature classes.

To Referent Location (line events only)

String

Between 50 and 255

Yes

The location of the offsetting feature. This can be an x,y coordinate, feature or event ID, or intersection ID.

To Referent Offset (line events only)

String

Between 50 and 255

Yes

The offset measure. This is saved in the unit of measure configured when configuring offset fields.

Derived network event fields

When an event is registered with a line network, you can also store the derived network route and measure information. This allows the route ID and measure from both a line and a derived network to be stored on the same event feature class.

To enable storage of a derived network route and measure fields on an event, add the following fields to the event:

FieldData typeLengthIs nullableDescription

Derived Route ID

Text or GUID

Same type and length as the Route ID field in the centerline sequence table

No

The unique ID of the route in the derived network.

Derived Route Name

Text

Same length as the LineName field in Line Network

Yes

The name of the route in the derived network.

Derived Measure (point event only)

Double

Yes

The measure on the route in the derived network where the event is located.

Derived From Measure (line event only)

Double

Yes

The measure on the route in the derived network where the event begins.

Derived To Measure (line event only)

Double

Yes

The measure on the route in the derived network where the event ends.

Learn more about using derived networks in Pipeline Referencing

Stationing event fields

Pipeline Referencing supports the registration of point events with stationing measures in the LRS geodatabase using the Enable Stationing Fields tool. Registering a stationing event allows you to locate stations with ahead and back station values at any measure along a route in the LRS Network.

When combined with referents and offsets, you can use a stationing event as an additional method for creating and editing the location of other events in the LRS.

When registering an event that uses stationing, all of the fields from a route and measure point event are required in the source event data. The following fields are required for an event that uses stationing:

FieldData typeLengthIs nullableDescription

Station

String

Any

Yes

The stationing value for the station.

Back Station

String

Any

Yes

The back stationing value for the station. This value is populated when an equation point is present at the station location.

Station Value Direction

String

Any

Yes

The field used to designate if stationing values increase in the opposite direction of the increase in measure on routes.

Event types

Pipeline Referencing has two types of events: those stored in the same geodatabase as the LRS and those stored in external databases. Events in the geodatabase are stored as feature classes, while external events are stored as tables in an RDBMS database or geodatabase (other than the geodatabase in which the LRS resides).

イベントは、[LRS イベントの作成 (Create LRS Event)] ツールを使用して、既存の LRS ネットワークのラインまたはポイント イベントとして LRS ジオデータベースに登録できます。

Learn more about creating and modifying LRS events

外部データ ソースの外部イベントは、[LRS を使用する外部イベントの構成 (Configure External Event With LRS)] ツールを使用して、既存の LRS ネットワークのラインまたはポイント イベントとして登録できます。

注意:

イベント フィーチャクラスが事前にモデル化されている場合、その空間参照、X,Y,Z,M 許容値および座標精度は、関連付けられているネットワークと一致する必要があります。

また、イベントを登録するときのイベント テーブルのパフォーマンスを向上させるために、プロジェクト アイテムのインデックスを作成することもお勧めします。

ArcGIS Pipeline Referencing での許容値と座標精度の詳細

Events in the geodatabase

内部イベントと外部イベントは、データ ソースの場所のほかに登録後の管理方法に関しても異なります。

LRS ジオデータベースのイベントはフィーチャクラスとして格納され、イベント フィーチャの形状は、ルート、メジャー、開始日および終了日に基づいて管理されます。 これにより、ArcGIS でのイベント データのマッピングと空間検索のパフォーマンスが向上しています。

LRS ジオデータベースにイベントを登録するとき、LRS を使用してジオデータベース内でフィーチャクラスを事前にモデル化して、LRS を使用してジオデータベース内に新しいフィーチャクラスを作成することができます。 また、別のテーブルまたはフィーチャクラスのスキーマを、LRS ジオデータベース内に作成した新しいフィーチャクラスにコピーすることもできます。

Learn more about creating and modifying LRS events

イベントの登録後、イベントは自動的に管理されます。 ルートを編集すると、イベント メジャーの振舞い構成を使用して、イベント フィーチャクラスが直接変更されます。 マップ内でイベント レイヤーが更新されると、編集アクティビティが自動的に実行され、更新内容を即座に確認できます。

Location Referencing ツールバーのツールを使用して編集を実行および保存した後は、[イベントの振舞いを適用 (Apply Event Behaviors)] ツールを実行してイベントのロケーションを更新します。

External events

外部イベント テーブルへの接続は、ジオデータベース内にモデル化されません。 LRS ジオデータベースの外部のイベント テーブルまたはフィーチャクラスを外部イベント テーブルとして登録するときは、読み取り専用の接続であると想定され、変更内容は外部イベント テーブルに直接書き込まれません。 外部システムのイベントでメジャーの更新にビジネス ルールが関連付けられている可能性があるため、外部システムのイベントは直接変更されません。

イベント メジャーに影響がある、実行されたすべての編集のログは維持されます。 Web サービスを使用して、これらの更新を外部テーブルまたはフィーチャクラスに送信し、メジャーを適用することができます。

Learn more about registering an external event