Skip to main content

Scenarios for generating and updating intersections

Available with the Linear Referencing license.

Use the Generate Intersections tool generate new intersections and update existing intersections. The following sections describe scenarios for generating and updating intersections.

Intersections and conflict prevention

When conflict prevention is enabled, the following conditions affecting intersecting routes apply:

  • If conflict prevention is not enabled and the routes are not locked during intersection calculation, resolve any intersection conflicts with the default version. Reconcile any route changes from the default version into the named version and recalculate intersections.

  • If conflict prevention is enabled, all routes that intersect with routes for which intersections are being calculated are also locked.

In the following example, Route D is selected before running the Generate Intersections tool. Because Routes AA, BB, CC, and DD intersect Route D, the tool must acquire locks for all of these routes.

The following diagram shows no locks are present for intersecting routes:

No locks are present for intersecting routes.

Before generating intersections, the tool locks routes D, AA, BB, CC, and DD.

The following diagram shows locks are acquired on intersecting routes:

Locks are acquired on intersecting routes.

The tool fails in cases where locks are not available for intersecting routes.

In the following diagram, Route D is selected for generating intersections. Because Routes AA, BB, CC, and DD intersect Route D, the tool must acquire locks for these routes. The tool cannot lock Route CC because user A owns its lock or user B owns its lock in another version. As a result, the tool cannot generate intersections.

No intersections are generated as all locks are not available.

When conflict prevention is enabled, the following conditions are applicable to acquiring locks:

  • If the tool runs on the default version, it releases the acquired locks after a successful run.

  • If the tool runs on a named version, it does not release the acquired locks after a successful run.

  • If the tool returns an error or stops during a run, it releases the acquired locks.

Scenarios for generating intersections

The following sections describe the intersection generation scenarios.

Single intersections

In the following example, a single intersection is generated where three routes intersect.

The following diagram shows an intersection that is generated where routes intersect:

Route intersections

The following table provides details on the intersection:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A and B and C A,B,C Network1 1/1/2000 <Null> 5

An intersection generated or updated from the above scenario has the following characteristics:

  • The tool generates a single intersection where the three routes—A, B, and C—meet.

  • The intersection name is determined by the sorting order of the route IDs.

  • The route IDs are comma-separated and alphabetically sorted.

  • The tool provides a feature ID only for non-route-on-route intersections.

  • The tool determines the dates from the common date range for all routes that constitute the intersection.

  • The measure is from the first route in the route ID list at the intersection location.

Time-sliced intersections

In the following diagram, an intersection is time sliced:

Time sliced intersections

Route A exists from 2010 to <Null>, Route B exists from 2000 to 2012, and Route C exists from 2020 to <Null>. The tool determines intersections from the common date range for all routes that constitute the intersection.

The following table provides details on the intersections:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A and B A,B Network1 2010 2012 5
2 A and C A,C Network1 2020 <Null> 5

An intersection time slice from the scenario above has the following characteristics:

  • From 2010 to 2012, only Route A and Route B exist, so the tool creates intersection ID 1 for the two routes.

  • Route B no longer exists after 2012, and Route C begins in 2020. The tool creates intersection ID 2 for Route A and Route C from 2020 to <Null>, their common date range.

Multiple intersections

The following diagram details multiple intersections:

The features intersect at more than one location

The following table provides details on the intersections:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A and B A,B Network1 2000 <Null> 2
2 A and B (2) A,B Network1 2000 <Null> 8

When features intersect at more than one location, the intersection names have the suffixes (2), (3), and so on.

Using z-values

The following example compares intersection feature attributes when z-values are used and when they are not used.

The following diagram details multiple intersecting routes:

Multiple intersecting routes

The following table shows the z-values at the point of intersection:

Route Z-value
A 10
B 34
C 34

The results in the following two tables differ depending on whether the intersection feature class uses z-values.

The following table provides details on the intersection when z-values are not used:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A and B and C A,B,C Network1 1/1/2000 <Null> 5

The following table provides details on the intersection when z-values are used:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 B and C B,C Network1 1/1/2000 <Null> 24

The tool uses z-values to generate intersections. It includes Route B and Route C because their z-values (34 and 34) are within the z-tolerance (0.001 m in this example). Route A, with a z-value of 10, is outside the z-tolerance.

An intersection ID is unique to every x, y, z location when z-values are considered or to every x, y location when z-values are not considered. When multiple time slices create intersections at one location, those intersections have the same intersection ID.

Route and polygon intersections

The following diagram details route and polygon intersections:

Route and polygon intersections use Feature ID.

The following table provides details on the intersections, route, and polygon:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A and Poly1 A Polygon1 Poly1 2000 <Null> 2
2 A and Poly1 (2) A Polygon1 Poly1 2000 <Null> 8

A route and polygon intersection from the scenario above has the following characteristics:

  • The tool provides a feature ID for route and polygon intersections.

  • The same route and polygon intersection name combination appears more than once, so the intersection names have the suffixes (2), (3), and so on.

Scenarios for updating intersections

When the tool updates intersections, the following situations can occur:

  • New intersections—The tool can create new intersections after edits such as creating, realigning, extending, or reassigning a route; cartographic realignment; or editing non-LRS features such as railroads or political boundaries.

  • Existing intersections are retired—The tool retires an intersection by populating its To Date field with the route edit date after a route is realigned, retired, or reassigned, or after other edits.

  • Existing intersections are moved—The tool moves intersections after cartographic realignment or edits to non-LRS features. It updates the intersection location and point geometry while maintaining the intersection ID. The tool does not retire these intersections. If a feature intersects a route at multiple locations and the intersection locations change, the tool moves the original intersection closest to the new location.

  • Existing intersections are deleted—The tool deletes intersections after cartographic realignment or edits to non-LRS features when routes no longer intersect the features in any time range.

The following table details scenarios that can occur when updating intersections:

Edit activity Route and route intersections Route and non-LRS layer intersections
Route edits Retires existing intersections or creates intersections Retires existing intersections or creates intersections
Cartographic realignment: Intersects after realignment Moves existing intersections or creates intersections Moves existing intersections or creates intersections
Cartographic realignment: Does not intersect after realignment Deletes existing intersections Deletes existing intersections
Non-LRS feature edit: Intersects after edit N/A Moves existing intersections
Non-LRS feature edit: Does not intersect after edit N/A Deletes existing intersections

The following sections present examples of intersection updates.

Intersection updates when an intersecting feature is added

The following example details intersection updates after a new intersecting feature is added.

The following diagram shows an intersection that exists between Route A and Route B:

Intersection of Route A and Route B

The following table provides details on the intersection:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A,B A,B Network1 1/1/2000 1/1/2010 5

When Route C is created or appended and intersects Route A and Route B at the original intersection location, the tool creates a new intersection with the same intersection ID for Route A, Route B, and Route C.

The following diagram shows the addition of Route C:

Intersection of Route A, Route B, and Route C

The following table provides details on the intersections:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A,B A,B Network1 1/1/2000 1/1/2010 5
1 A,B,C A,B,C Network1 1/1/2010 <Null> 5

Intersection updates when a route retires

The following example details updates that occur after an intersecting route retires.

The following diagram shows an intersection that exists between Route A and Route B:

Intersection of Route A and Route B

The following table provides details on the intersection:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A,B A,B Network1 1/1/2000 <Null> 5

When part of Route B that contains the intersection location is retired, the tool retires the intersection with the end date of Route B.

The following diagram shows the retired route B and intersection:

Intersection of Route A and Route B is retired due to retirement of Route B

The following table provides details on the retired intersection:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A,B A,B Network1 1/1/2000 12/31/2020 5

Intersection updates after cartographic realignment

The following example details updates that occur after part of Route B is cartographically realigned.

The tool updates the intersection location and measure along Route A. When Route B is cartographically realigned and no longer intersects Route A, the tool deletes the intersection.

The following diagram shows an intersection that exists between Route A and Route B:

Intersection of Route A and Route B

The following table provides details on the intersection:

Intersection ID Intersection name Route ID Feature class name Feature ID From Date To Date Measure
1 A,B A,B Network1 1/1/2000 <Null> 5

The following diagram shows Route B that is cartographically realigned:

Route B is cartographically realigned

The following table provides details on the intersection:

Intersection ID Intersection name Route ID FC name Feature ID From Date To Date Measure
1 A,B A,B Network1 1/1/2000 <Null> 3