Reassigning portions of lollipop route to multiple non-lollipop routes

[GraemeBrowning_Aurizon]

I am using Roads and Highways with ArcGIS Pro 3.0.0 and a File Geodatabase.

Reassign routes documents a number of Complex route reassignment scenarios.  However, I think I am encountering another, and am struggling to work out how to deal with it.

I have a lollipop route (TESTX) based on two centerlines like this:

Is it possible to start at the beginning of the route and reassign portions of it to new routes like this?

• 0-200m becomes route TEST1
• 200-400m becomes route TEST2
• 400-600m becomes route TEST3
• 600m to its end becomes TEST4

I suspect it's easiest by doing TEST4 first:

This creates a route TEST4 which can be seen in the attribute table, but from the map it is not the last 92m that I expected, and the new TESTX has been recalibrated so that its 692m length becomes 600m (which I did not want):

The above is just one of many ways I've tried unsuccessfully to get my desired result. 

Is there a way, that I have not tried, which will enable it to be done?

[JordanM_Support]

Hi @GraemeBrowning_Aurizon ,

Based on the last screenshot, are you seeing the TEST4 route being created at the start of the TESTX route, even though you are reassigning the end of the TESTX route? And does the route appear to be calibrated properly?

When I try to replicate your workflow, I receive the following result for the test4 route, which shows NaN for Measure values using the Identify Routes tool or Attributes Pane.

 
Test4 route created from reassign route workflow

The remainder of the original route looks like the following screenshot, and does have valid calibration points:

Original Lollipop Route after reassignment

Additionally, what is the WKID of the spatial reference you used to create this LRS Network? I have been testing using GDA2020 GCS (WKID 7844).

[GraemeBrowning_Aurizon · Accepted solution]

The need to resolve this issue has gone out of scope for the project that I am working on, and I am happy to leave it unresolved for now.  However, I just ran a similar test and got a different result/issue when I tried to Reassign from 600 to the end into TEST4:

The above is just an FYI but if you wish to pursue it the other relevant details to my environment are:

• My test is run in a File Geodatabase and not an Enterprise Geodatabase
• My test uses GCS_GDA_1994 (4283)
• The Centerlines in my test were densified by 50m

The reason this has gone out of scope is that my client plans always to create the KM routes (200m in the test represents long/short KM routes from the real data) one at a time, at the outset, rather then creating routes that span multiple kilometres and then chop them into KM routes.  Using the "one KM (in test approx. 200m) route at a time" workflow I had no trouble creating the desired result below: