I have identified a route that was accidentally retired (along with all of its events) that I want to unretire in RCE. I know that I can bring up the RCE attribute tables for this route (and its events) by adjusting the view date to one day before everything was retired. For the events, it appears that I can just remove the retire date in their respective RCE attribute tables to unretire them, but the system will not let me do this for the route itself. Does anyone have suggestions for how I can also remove the retire date in the RCE attribute for the actual route?
Assuming you are using ArcGIS Desktop 10.5.1 or later there is a COTS-based workflow to bring your routes back from retirement. This workflow assumes you want/need to preserve all timeslices for the route in question and that you may have custom/intermediate calibration points. The process is simpler if you are reloading a route using geometric length or do not have intermediate calibration.
Be sure your events’ temporal dates match the routes as you wish. You may also wish to test this workflow in a version or file GDB export to be sure it yields the results you desire.
Roads and Highways team
@Amit, does a generate events need to be run afterwards?
@Joseph, does the route that needs to be unretired have any coroutes?
We are in the process of doing a load routes to fix incorrectly loaded routes from 2016 (v10.3) those routes had coroutes. At that time we had issues with coroutes so to fix that issue we are planning on loading all routes that overlap and any routes that overlap those routes in what we term "spider web effect". We discovered in a previous system that while routes are separate, they are connected and with out chasing down all the strands you usually ran in problems with those downstream routes some time later.
@Joseph, after running the centerline duplication step, I would recommend checking the centerline fc for lasted edited records you touched to see if it is localized to your route. Running that process this morning, centerline duplication ran on the whole state and updated more records then intended.
Can you guys explain why running remove centerline duplication as part of load routes and not running remove centerline duplication as part of load route but running remove centerline duplication tool separate gives you different results?
Is there a workflow to run remove centerline duplication only on the routes loaded and not the entire centerline FC or State in our case?
There shouldn't be a difference in results when running the tool in these two contexts as the same Remove Duplicate Centerline Geometry operation is being executed in each case. Unfortunately in ArcMap there isn't a way to choose the centerline features/area/selection set to run the tool against. In ArcGIS Pro, we've made this tool a geoprocessing tool which allows for selection sets and a greater level of control over which features the tool runs against.
Esri Roads and Highways team