Event creation using feature creation

Available with Location Referencing license.

You can digitize an event in a feature service using the feature template for that layer in the Create Features tool Create Features. The route ID and measures are automatically populated to associate the event with the route on which the feature is created. The Attributes pane appears where you can review existing event attributes and provide additional event attributes.

Tip:

Click the Create Features button Create Features on the Edit tab, in the Features group, to open the Create Features pane and expand the feature template for the feature service layer.

Learn more about creating features using feature templates

If a message regarding acquiring locks or reconciling appears, conflict prevention is enabled.

When you create a point event, the route ID, measure, and date fields are populated based on the underlying route. When digitizing a line event feature, the first vertex is used to populate the From Measure, From Date, To Date, and From Route fields, and the last vertex is used to populate the To Measure and To Route fields. For spanning line event features, the from and to measures must be on routes that have the same line ID.

Learn more about creating polyline features, including event features

Location Errors

If the feature is added outside of tolerance and the route ID or measures are not detected, a location error occurs.

Any of the following statuses indicate a problem that must be resolved.

Location ErrorDescription

Can't Find Extent

The route location's shape was not found because the from measure and the to measure are outside the route measures.

Can't Find Location

The route location's shape doesn't exist on the route (the route has no m-values or the route location's measures don't exist on the route).

Can’t Find Parent Event

The parent event was not found. This is applicable to reference offset events.

Different From-Route And To-Route Line IDs

The from route and the to route have different line IDs. This is applicable to line networks.

Invalid Line ID

The route's line ID is invalid. This is applicable to line networks.

Invalid Location Route ID

The route location's route ID is invalid (NULL, empty, or invalid value).

Invalid Measure

At least one of the route location's measure values is invalid.

Invalid Route ID

The route location's route ID is invalid (NULL, empty, or invalid value).

Multiple Location

More than one point location was found. Measures may not be unique along the routes.

Null Extent

The from measure is equal to the to measure.

Partial Match for From and To Measure

The entire route location's shape was not found. The from measure and the to measure are outside the route measure range.

Partial Match for From Measure

The entire route location's shape was not found. The from measure is outside the route measure range.

Partial Match for To Measure

The entire route location's shape was not found. The to measure is outside the route measure range.

Reversed Line Order

The from route does not have a lower line older than the to route. This is applicable to line networks.

Route Not Found

The route does not exist.

Route Shape Empty

The route does not have a shape or the shape is empty.

Scenarios for adding a line event using feature creation

In the scenarios below, a line event is added using the feature template in the Create Features pane.

Adding a line event

The following image shows the route attributes:

Before adding a line event to a nonspanning route

The following table details the route attributes. The route (Route1) has measures from 0 to 20.

Route IDFrom DateTo Date

Route1

1/1/2000

<Null>

The following image shows the creation of a line event. The first and last vertices intersect Route1, which results in a new line event.

Drawing the vertices for a line event

The following table details the line event:

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation ErrorSpeed Limit

Event1

Route1

1/1/2000

<Null>

10

20

No Error

55

The following image shows the route and the associated event after the edit:

After adding a line event to a nonspanning route resulting in No Error

Adding a line event resulting in a location error

The following image shows the route attributes. The route (Route1) has measures from 0 to 20.

Before adding a line event to a nonspanning route

The following table details the route attributes:

Route IDFrom DateTo Date

Route1

1/1/2000

<Null>

The following image shows the creation of a line event. Only the first vertex intersects Route1. The route ID and from measure are populated, but the to measure is <Null> because the last vertex does not intersect the route.

Drawing the vertices for a nonspanning line event

The following table details the line event:

EventRoute IDFrom DateTo DateFrom MeasureTo MeasureLocation ErrorSpeed Limit

Event1

Route1

1/1/2000

<Null>

0

<Null>

Invalid Location Measure

55

Scenarios for adding a spanning event using feature creation

The scenarios below detail the results of adding a spanning line event using the feature template in the Create Features pane.

Adding a spanning line event

The following image shows the routes:

Before adding a spanning line event to routes on a line in a line network

The following table details attributes for the routes (Route1, Route2, and Route3):

Route IDFrom DateTo Date

Route1

1/1/2000

<Null>

Route2

1/1/2000

<Null>

Route3

1/1/2000

<Null>

The following image shows the creation of a spanning event feature. The first vertex intersects Route1 at 5, which is resolved to the From Measure on Route1, and the second vertex intersects Route3 at 35, which is resolved to the To Measure on Route3.

Drawing the vertices for a spanning line event

The following table details the spanning event after the edit:

EventFrom Route IDTo Route IDFrom DateTo DateFrom MeasureTo MeasureLocation ErrorSpeed Limit

Event1

Route1

Route3

1/1/2000

<Null>

5

35

No Error

55

The following image shows the routes and the spanning event after the edit:

After adding a spanning line event to routes on a line in a line network resulting in no error

Adding a spanning event resulting in a location error

The following image shows the routes before a line event is associated with it. In this case, Route1 and Route2 are on LineA, and RouteA is on LineB. Spanning events must be on the same line in a line network.

Before adding a spanning line event to routes on a line in a line network

The following table details the route attributes. Route1 and Route2 are on LineA, and RouteA is on LineB.

Route IDFrom DateTo Date

Route1

1/1/2000

<Null>

Route2

1/1/2000

<Null>

Route3

1/1/2000

<Null>

The following image shows the creation of a spanning event feature. The first vertex intersects Route1 at 5, which is resolved to the From Measure on Route1, and the second vertex intersects RouteA at 35, which is not resolved to the To Measure on RouteA because RouteA is on LineB.

During spanning event creation resulting in a location error because Route1 and Route3 are on a different line

The following table provides an example of the Different From-Route and To-Route Line IDs value for the Location Error field. Events spanning routes must share the same line ID.

EventFrom Route IDTo Route IDFrom DateTo DateFrom MeasureTo MeasureLocation ErrorSpeed Limit

Event1

Route1

RouteA

1/1/2000

<Null>

5

35

Different From-Route and To-Route Line IDs

55

The following image shows Event1 after the error:

After editing a line event on a spanning route resulting in an error