Events data model

Disponible avec la licence 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.

Remarque :

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

Les événements peuvent être inscrits sous forme d’événements linéaires ou ponctuels dans la géodatabase LRS pour un réseau LRS existant à l’aide de l’outil Créer un événement LRS.

Learn more about creating and modifying LRS events

Les événements externes d’une source de données externe peuvent être inscrits sous forme d’événements linéaires ou ponctuels pour un réseau LRS existant à l’aide de l’outil Configurer un événement externe avec LRS.

Remarque :

Si une classe d’entités d’événements est modélisée en avance, sa référence spatiale, ses valeurs de tolérance x, y, z et m et sa résolution doivent correspondre à son réseau associé.

Nous vous recommandons également d’indexer les éléments de projet afin d’améliorer les performances des tables d’événements lors de l’inscription d’événements.

En savoir plus sur la tolérance et la résolution dans ArcGIS Pipeline Referencing

Events in the geodatabase

Outre du point de vue de la localisation de la source des données, les événements internes et externes peuvent également différer dans la façon dont ils sont gérés après leur inscription.

Les événements dans la géodatabase LRS sont stockés en tant que classes d’entités et la forme des entités est gérée en fonction de l’itinéraire, de la mesure et des dates de début et de fin. Cela améliore les performances de cartographie et de requête spatiale des données d’événements dans ArcGIS.

Lors de l’inscription d’un événement dans la géodatabase LRS, vous pouvez modéliser la classe d’entités en avance dans la géodatabase avec le LRS de sorte que la nouvelle classe d’entités soit créée dans la géodatabase avec le LRS. Vous pouvez également copier le schéma d’une autre table ou classe d’entités dans la nouvelle classe d’entités créée dans la géodatabase LRS.

Learn more about creating and modifying LRS events

Après son inscription, l’événement est automatiquement géré. Lorsqu’un itinéraire est mis à jour, les modifications sont apportées directement à la classe d’entités d’événements à l’aide de la configuration du comportement de mesure d’événement. Lorsque la couche d’événements est actualisée sur la carte, qui est déclenchée automatiquement par une mise à jour, vous y voyez immédiatement les mises à jour.

Une fois les modifications apportées et enregistrées à l’aide des outils de la barre Location Referencing, exécutez l’outil Appliquer les comportements d’événement pour mettre à jour les localisations d’événement.

External events

Les connexions aux tables d’événements externe ne sont pas modélisées dans la géodatabase. Lorsqu’une table d’événements ou une classe d’entités en dehors de la géodatabase LRS est inscrite en tant que table d’événements externe, il est supposé qu’il s’agit d’une connexion en lecture seule et que les modifications apportées ne sont pas directement écrites dans la table d’événements externe. Des règles de gestion peuvent être associées à la mise à jour des mesures d’événements dans un système externe, afin que ces événements ne soient pas modifiés directement.

Un journal de toutes les mises à jour effectuées et ayant des conséquences sur les mesures d’événement est tenu. Vous pouvez utiliser des services web pour envoyer ces mises à jour à la classe d’entités ou la table externe pour appliquer les mesures.

Learn more about registering an external event