Work around for appending routes (Retire by route ID) in case of a partially changed centerline

[MirekGroen]

Hi Community,

We are working on a project to create a LRS, where we are dependend on external data. That means that centerlines as input for our LRS are managed outside our database. We receive messages in case of a Create, Update and Delete event in this external database, and therefore need to update our LRS based on these event messages. We are running into a problem when trying to update a route when a centerline is geometrically partially updated.

Here is an example:

1. We have a route that exists of 3 centerlines (16, 17  and 18)

2. We received an update event on centerline 16 and appended this new centerline to the centerline feature class in the LRS

3. As preparation to append the new route, we create a new polyline outside the LRS (blue selected line) and use this as Source Route when running the Append Routes tool

4. We run the Append Routes tool with the following settings:

Since the route id is already present in the LRS, we want to Retire the existing route by its route ID, and we want the tool to use existing centerlines.

However, because there are now two partially overlapping centerlines, the new route cannot be appended to the LRS and gives the following error message:

Partially matched centerlines found. A list of offending OIDs is available below.

Has anyone a workaround for this problem? We cannot use the Realign tool in ArcGIS Pro, and are dependent on the tools available in the arcpy locref toolbox.

I hope anyone out there can come with some ideas on a work around!

Thanks,

Mirek

[AyanPalit]

@MirekGroen There may be different workarounds but here's something to try:

• Use 'Delete Routes' check delete associated centerlines
• Append Routes without considering existing centerlines

[MirekGroen]

Hi @AyanPalit,

Thanks for your response.

• Delete Routes would not work for us, since we want to keep history.
• Append Routes without considering existing centerlines works, but in this case we loose connection with the existing external managed centerlines. We are dependent on external data for centerline input.

We changed our datamodel, so that the external centerlines are not part of our LRS.

[AyanPalit]

@MirekGroen  Based on the limited information, my understanding is that the LRS must maintain the relationship with the centerline maintained in an external database.

My recommendation would be to look at this use case more holistically as LRS centerlines will change based on ArcGIS edits, Roads & Highways data maintenance. This seems to be a driver to develop a integration between GIS and the external database. The integration needs to track centerline changes in both systems (edits happening in both) and keep them in sync, following the Roads & Highways data maintenance polices.

[MirekGroen · Accepted solution]

Hi @AyanPalit, in our case we are not allowed to edit centerlines in ArcGIS and update external databases. The centerlines are owned by third parties and we are using them as a base for a LRS. In case of updates in the external database, we are receiving change messages to be able to update our LRS. The solution for now is that we add changed centerlines to a separate feature class, related to the routes feature class with a GlobalID. And then we Append Routes not using the 'considering existing centerlines'