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 TypeLengthIsNullableDescription

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.

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 length from the beginning of an event, other LRS events, intersections, or another point feature class.

To enable storing referent locations with an event, the following fields are required:

FieldData TypeLengthIsNullableDescription

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. 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. 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. 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 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, the following fields should be added to the event:

FieldData TypeLengthIsNullableDescription

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

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 TypeLengthIsNullableDescription

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 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 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 事件工具将事件注册为现有 LRS 网络的 LRS 地理数据库中的线或点事件。

Learn more about creating and modifying LRS events

可以使用使用 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 工具栏上的工具执行并保存编辑后,请运行应用事件行为工具来更新事件位置。

External events

系统将不在地理数据库中对外部事件表的连接进行建模。 当 LRS 地理数据库之外的事件表或要素类注册为外部事件表时,系统会将其假定为只读连接,并且不会将更改直接写入外部事件表。 可能存在与更新外部系统中事件的测量值相关联的业务规则,因此不会直接修改外部系统中的事件。

系统将保留对事件测量值有影响的所有已执行编辑的日志。 您可以使用 Web 服务将这些更新发送到外部表或要素类以应用测量值。

Learn more about registering an external event