Concurrent Routes - Managed via LRS (Routes) or Events?

[KevinKoester_KSDOT]

We are wanting to know from the states that have riding routes (US-24 riding on I-70 for example) how many of the states are managing the route concurrency via separate LRS Routes or via events.

Please advise!

We are currently using ArcMap 10.7.1, but we are working towards ArcGIS Pro (hopefully after June 15, 2022).

[RyanKoschatzky]

NCDOT uses separate routes with shared centerline segments for the sections corouted. For us via events would not work as our coroutes can be across multiply routes and managing topology of event records across multiply routes seems difficult at best. 

In Pro, I have seen options that appears to allow a single event record to traverse multiply routes as one record and that might work to capture coroutes via events. https://pro.arcgis.com/en/pro-app/latest/help/production/location-referencing-pipelines/what-is-even... 

Hope that helps.

[KevinKoester_KSDOT]

Thanks Ryan!

We currently maintain our concurrency via multiple LRS Routes on top of one another and it makes finding overlapping data locations a real challenge because its only an overlap if its on the same RouteID.  Gets a little hairy when there are five or more concurrent route segments in some places where only one route should actually have the data on it (dominant route, usually from RouteConcurrency output, but sometimes not because of dominance rules that have nearly impossible logic to script for!)

Looked like the functionality you referenced was on the pipeline referencing side of things, is that the same for Roads & Highways in Pro?

I seem to recall that ESRI encouraged us to use the event to manage concurrency as its less complex to maintain the route network (and a lot less edits there for sure).

[SamuelColdiron]

OKDOT uses 6 separate events to track Highway Routes. We have an OKDOT Primary Route, FHWA Primary Route, Follow Route 1, Follow Route 2, Follow Route 3, and Follow Route 4. Our LRS Routes do not follow the Highway Route Designations and are broken at County Lines and where it makes sense for our Agency internally.

[KevinKoester_KSDOT]

Sam,

Currently our Routes are county based and we derive the state route measures via python scripting as we have systems of record that require state mileage...

I could envision taking our current concurrent LRS Routes and develop an event based concurrency - that probably doesn't help anything downstream from us though.

[AmitHazra]

Hi Kevin - Off the topic from the original posting but in reference to your process to programmatically derive a Statelog-based LRM, once you transition to the ArcGIS Pro release of Roads and Highways you could conceptually model your Statelog as a "derived network" from a line network where your routes are based on your Countylog. This would automate the process of maintaining two LRMs and would also allow you to support events that span multiple Countylog routes. Here are a few resources for you to look at:

Line Networks

Network Configuration

Deriving Event Measures

-amit@esri

[KevinKoester_KSDOT]

Amit,

We definitely should look at that - we've actually already abandoned the State LRS and only maintain the County LRS in our current ArcMap instance - I'll pass the links along!

[KevinHunt]

Hi Kevin

NYSDOT maintains route concurrency on the routes.   Due to some special cases related to incomplete inventory data on reverse (or non-primary) direction routes, our system generates and maintains a CONC_HIERARCHY field (a database trigger and calculates a value based on other route table attributes) for every route in the ALRS.    This field then becomes the primary field defining the route dominance on the network.    Once all roadways in the network include inventory data, we should be able to remove the CONC_HIERARCHY field and rely on the remaining four route table fields.  

The attached xlsx shows the current Route Dominance settings on our network.