Generate Event Table

An event table is essentially an attribute table where each record represents an event. In addition to mandatory fields like route ID and measure values, it may contain other attributes to describe events.

SuperMap iDesktopX provides basic operations for event tables, such as generating event tables, overlaying event tables, and merging event tables.

Feature Description

Generating an event table is the process of creating an attribute table containing point or line events. Event tables can be manually populated or automatically generated using existing point/line datasets combined with route datasets.

  • Manual method: Create an attribute table by adding route ID fields, measure fields, and other property fields, then input corresponding attributes. While straightforward, this method can be resource-intensive.
  • Automated method: Generate event tables using spatial data (point/line events) and reference route data. The measure values and associated routes are automatically derived from the route data.

For detailed explanations of point and line event tables, see About Event Tables.

Feature Entry

  • On the Transport Analysis Tab -> Dynamic Segmentation group, click the Dynamic Segmentation button, then select Generate Event Table from the dropdown menu.
  • Toolbox -> Transport Analysis -> Dynamic Segmentation tools: Generate Event Table; or drag this tool to the Model Builder window and double-click its icon.

Parameter Description

  • Event Data: Configure parameters for event data. Select point/line event datasets and their corresponding datasources.
  • Route Data: Set parameters for route data. Specify the datasource, dataset, and route ID field for the route data.

    Route ID Field: Defines the field storing route IDs to associate with corresponding route data.

  • Result Data: Configure result parameters. Select the output datasource, event table name, route ID field, measure field, and other parameters.

    Route ID Field: Name of the route ID field in the generated event table. This field establishes relationships between event tables and route data through matching IDs.

    Measure Field: Specifies the measure field in the result event table. For line events, set both From-Measure (start point) and To-Measure (end point) fields.

    Search Radius: Define the radius and unit. Points/lines outside this buffer range (based on Euclidean distance to the route) will not generate event records. The system converts this value to match the unit of the reference route data during processing.

    Create Distance Field: (Point events only) Toggles whether to add a field storing the Euclidean distance from points to routes. Enabled by default.

    Find Nearest Route Only: (Point events only) When enabled, only the closest route within the search radius generates an event record. Disabled by default.

    Reserve Custom Fields of Event Dataset: Determines whether to retain non-system fields from the original event data in the result table. Enabled by default.

  • Click Execute to run the operation after configuring parameters.

Notes

  • Parameter settings differ between line and point event tables. Line events require both start and end measure fields, while point events need only one measure field.
  • Appropriate search radius values are critical. Excessively large radii may yield impractical analysis results. Always use reasonable values based on actual scenarios.

Related Topics