Disponible con licencia de 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.
Nota:
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:
| Field | Data Type | Length | IsNullable | Description |
|---|---|---|---|---|
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:
| Field | Data Type | Length | IsNullable | Description |
|---|---|---|---|---|
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:
| Field | Data Type | Length | IsNullable | Description |
|---|---|---|---|---|
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:
| Field | Data Type | Length | IsNullable | Description |
|---|---|---|---|---|
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).
Los eventos se pueden registrar como eventos de línea o punto en la geodatabase LRS de una red LRS existente mediante la herramienta Crear evento LRS.
Learn more about creating and modifying LRS events
Los eventos externos de una fuente de datos externa se pueden registrar como eventos de línea o de punto para una red LRS existente con la herramienta Configurar evento externo con LRS.
Nota:
Si la clase de entidad de eventos se modela por adelantado, su referencia espacial, la tolerancia x, y, z y m y la resolución deben coincidir con la red asociada.
También se recomienda indexar los elementos del proyecto para mejorar el rendimiento de la tabla de eventos al registrar eventos.
Más información sobre la tolerancia y la resolución en ArcGIS Pipeline Referencing
Events in the geodatabase
Además de la ubicación de la fuente de datos, los eventos internos y externos también difieren con respecto a cómo se administran después del registro.
Los eventos de la geodatabase LRS se almacenan como clases de entidad y la forma de las entidades de evento se administran en función de la ruta, la medición y las fechas inicial y final. Esto proporciona un mayor rendimiento en ArcGIS para la representación cartográfica y la consulta espacial de los datos de eventos.
Al registrar un evento en la geodatabase LRS, puede modelar la clase de entidad en la geodatabase con el LRS por adelantado y crear la nueva clase de entidad en la geodatabase con el LRS. También puede copiar el esquema de otra tabla o clase de entidad a la nueva clase de entidad creada en la geodatabase LRS.
Learn more about creating and modifying LRS events
Después del registro de evento, el evento se administra automáticamente. Cuando se realizan ediciones en una ruta, los cambios se realizan directamente en la clase de entidad de evento mediante la configuración del comportamiento de medición de eventos. Cuando la capa de eventos se actualiza en el mapa, que se desencadena automáticamente por una actividad de edición, puede ver las actualizaciones de inmediato.
Después de realizar y guardar los cambios utilizando las herramientas de la barra de herramientas Location Referencing, ejecute la herramienta Aplicar comportamientos de eventos para actualizar las ubicaciones de los eventos.
External events
Las conexiones a tablas de eventos externas no se modelan en la geodatabase. Cuando una tabla de eventos o clase de entidad fuera de la geodatabase LRS se registra como una tabla de eventos externa, se asume que es una conexión de solo lectura y que los cambios no se escriben directamente en la tabla de eventos externa. Puede haber reglas empresariales asociadas a la actualización de medidas en eventos de un sistema externo, por lo que los eventos de sistemas externos no se modifican directamente.
Se mantiene un registro de todas las ediciones realizadas que tienen un impacto en las mediciones de los eventos. Puede utilizar los servicios web para enviar estas actualizaciones a la clase de entidad o tabla externa para aplicar medidas.