Road Closures - two roads one detour

Jennifer_Parmeley

We have a road closure for a major construction project and the road name changes in the closed section. (image below)

While taking a closer look at this closure and our Waze feed today I noticed that the Locust St closure was missing from Waze. Originally this was entered as one line segment that started at the north end of the red line along Walnut and went south, past where the name changes to Locust.  I have updated this to be separate line segments, one for Walnut and one for Locust. Both now show in Waze (not perfect but better). BUT I cannot put in two closure Global ID values in the detour table. Or I guess I should say I cannot do this out of the box, now that I think about it maybe I can add this with some Arcade. 

My question. How have others handled this? 
The Walnut/Locust corridor is one of the major routes through our town and it would be nice to have the Walnut AND Locust closure popups show the detour information.

I'm using duplicate detour ID fields to accommodate the one way streets - which is why the popup shows two detours

 

 

joyoung_kerrvilletx

We have run into the same issue with Waze requiring different closures where the road name changes. The problem that we have is we are using the Road Closure solution 2.0 and the relationship type between the closures and detours is one-to-many. We have a separate hosted feature service that a Python script does ETL from the road closure layer to another one formatted for Waze. I tried leaving the closure combined in the Esri layer and splitting it in the Waze layer but the next sync wipes that out.

Currently if a closure has to be split due to a name change, I will draw the detour in twice the same way for both closures. In theory if you created a new relationship based off of the Closure ID instead of the GlobalID then you could get one popup for the detour. However, if I remember correctly some functionality in ArcGIS Online/Enterprise does not like relationships that are not based on GlobalIDs and it is easier for related data to get accidentally orphaned. There are also many-to-many relationships but Esri's support of them has not been great in my experience, especially in ArcGIS Online/Enterprise.

Personally, it would be easier if Waze was smart enough to recognize the two road names in the road name field and process the closure accordingly. You would think in the age of "AI" that would be possible.