Latest Contributions by RyanKoschatzky

Kevin, We have a had a quarterly freeze in place for over a decade. This allows our Pavement folks a chance to update the Agile system. It does not always happened. I believe they just finished the update with 1st Qtr 2020 data but aren't not going to do sync with 2nd Qtr 2020 data. If we had to run RDCG it would be after the editors freeze and before we sync with Agile. In the method you are proposing, how you do handle locks (route or event) that an editor might have overnight on a route that they are changing data and RDCG would be changing? I could see running RDCG in a throw away version, analysis routes touched and lock those route affect in another version that you would run RDCG overnight in to prevent but there is always a chance that things don't line up perfectly.  I wouldn't think you would have to run RDCG more then a few times a year. In our system we would install data reviewer checks and provide more training to the offending editor/s to prevent bad data being posted. It is far better to delete the version and lose work then post and have to fix the error later if it is even possible with all the different downstream impacts.  ... View more

Kevin, NCDOT has run that tool only a handful of times in lower arcmap versions. What I have found is that while I am running the tool to fix one set of known issues it touched other centerline records I had not known about since the tool runs statewide. That's not to say it those change where wrong but just additional issues that I was not aware of and making the cleanup a more difficult process.The last time I tried, I stopped and looked for a different workaround for the route fixes needed because those additional changes. The 10.5 tool version and the condition of some routes lead to event data being shifted and clean up work that needed be done. For us at the end of the day, there was more cons then pros to running the tool. You should be able to run the tool in a version to see what the impact will beforehand. We would run this tool at a scheduled quarterly freeze where we go to state zero in the database to get around the issues your talking about.  One of the things Nathan has talked about for Pro is the tool can be run on a selection set and not statewide. That will one day give us more flexibility and be able to run more often. ... View more

Interesting concept, thanks for the video.  ... View more

I know that the route and centerline records where in alignment. I didn't check the centerline sequence record at the time. In another version, the centerline sequence record appears good. There was a centerline split applied to the active section.  ... View more

I thought that also however we have only used euclidean distance so I wouldn't think we would have the other two types.  ... View more

That is a lollipop route. It is saying all the route vertexes have the same measure. I think if you separate the loop, add a calibrate point at the first duplicate measure, recalculate downstream then re-snap might fix the issue.  ... View more

What you have drawn is a alpha or fish route and not a loop or lollipop. Alpha routes are not supported but planned to be in pro. I would recommend making a small gap on the north/south section just before it crosses over itself. I would recommend posting over at Roads and Highways User Group (RHUG) as other folks comment on how they deal with alpha routes and other routing scenarios. ... View more

You can run the detect Detect Non-monotonic Routes toolbox tool to find issues. Depending on how your setup, Shape.STGeometryType() = 'MultiLineString' Can return your gaps, lollipop and loops. If you use the route tab in your layer properties on the route layer you can visual see issues, see Nathan's post. HTH ... View more

Sam, Our process is different, however those run times do not see that out of line to me and to a certain extent that seems fast. For example on one of our spatially derived products for a full coverage event on all public roads for one event with 397,692 records was 8 hour and  41 minutes.   ... View more

Ron, Depending on how your shop is setup, you could get just event route lock for just those routes the points you know your going to update is on. That should prevent the lrs routes from being modified underneath you and just those event records from being updated. All other routes in the system, all other events within Transit Stop not on those routes and any another events in the R&H can be modified even if on the same route.  In case you didn't know, R&H has two types of locks, route locks and event locks. I couldn't find anything with a quick google search to explain the differences, so here is my stab at it. A route lock prevents all other users from modifying the route and all events on that route. An event lock prevents lrs editors from editing that route and only event editors from editing events on that route in that event table. This is the least intrusive of the lock types.  Hope this helps ... View more

Ron, I would also post your question at Roads and Highways User Group (RHUG) , there might be someone else who has a different workflow to help. ... View more