Latest Contributions by RyanKoschatzky

Interesting, you should post this at https://community.esri.com/groups/roads-and-highways-user-group-rhug ,  those users may find this useful for them.  ... View more

Ana, I am not sure as we don't currently use the functionality but I would recommend posting at https://community.esri.com/groups/roads-and-highways-user-group-rhug as there is a few states/users that do use redlining and can probably help answer your question.  ... View more

Andrew Vitale wrote: To add to this a little, the ROUTEID field in the Lrs_Edit_Log will show the original Route ID. To access the NewRouteId, you can right click the text "Blob" in the EDITDATA field and look through the XML. Great tip. Thanks ... View more

This might be a byproduct of the 2 LRMs. WV and you which both have 2 LRMs are both reporting some discrepancies with the log. Hopefully Nathan or Esri can provide some enlightenment on that front.  What I have seen is that if you have R&H turned on (yes some workflows are instructed to have it turned off) that all route edits using the toolbar and cartographic realignments are captured. A reassign does not capture the route it will be come in the reassign record for the route but there should be a record for a created route with the new route id. A visual or centerline sequence table query can help figure that out. I would like to see something similar or another method for capturing event changes. I want to break out event behavior changes vs business owner changes. For NC if we have different user names for LRS editors, LRS event editors and other event editors so removing the time filter some counts be derived.  ... View more

I think you did. I am still getting used to how geonet breaks out different replies.  ... View more

With a copy/paste it could be a case of dirty geometry causing the issue. We try to instruct our editors to create the geometry themselves to cut down on any potential problems.  ... View more

How did you create the centerline, drawing new geometry or copy/paste from a cad file or other data source? ... View more

Nicole, Are those total numbers or just 2018 or 2019?  ... View more

"I'm a little late to the discussion but wanted to get in here." Charles, welcome aboard and there is no way to be late as we all start at different times. Interesting find with multiply LRMs. ... View more

Nathan Easley, branch versioning for R&H is only supported at Pro and it is mandatory is that correct?  ... View more

Thanks Andrew, Kyle, Marshall and Michael for responding.  Have any of you broken down the edit types per route class or system vs nonsystem? I have not yet for our data but that is planned. When looking at the activity type record numbers, did any of the values surprise you for the way your departments are set up? I was expecting most of our values to increase based on what the mid year results showed but not by the numbers I saw.  ... View more

Thanks Jonathan. I have added Annie's slidedeck to the meeting pdf RH_User_Group_January_2020.pdf  ... View more

With a new year, I thought I would report on NCDOT's 2019 stats. TransactionDate > '1/1/2019' AND TransactionDate < '1/1/2020' AND ActivityType = X Edit log Code/R&H Route action name/number of records 1 Create Route 7476 3 Reverse Route 127 4 Retire Route 4563 5 Extend Route 1992 6 Reassign Route 1058 7 Realign Route 795 12 Cartographic Realignment 32154 Please share your stats. ... View more

Nathan, North Carolina has come up with a few use cases.              1. Lollipop route – Reverse and Reassign operations In this example a preexisting lollipop route needed to be Reassigned.  To achieve the desired end result measures were first reversed, then the route was reassigned.  The result is that the lollipop is now the beginning of a much larger route.  The route measure anomalies are turned off in these images, but there is a point anomaly in the lollipop where the route intersects itself. 2. Fish route – Practical example In this example a route representing an Interstate ramp is a fish route. There are many other similar ramps in neighboring interchanges. These are all currently employing the “micro gap” workaround for fish routes. 3. Fish route – Reassign operation In this example a route representing a ramp is coded as such, but the desired case is to use this geometry to represent the route that current traverses a grade separated interchange. Employing the micro gap workaround would allow this Reassign to happen, but current software bugs related to gap routes make this Reassign an impractical change at this time due to event data integrity concerns. 4. Lollipop route – create via Realign operation In this example a route will be Realigned so that it becomes a lollipop route. All other lollipop routes in the ALRS came to be via a Create operation or via the original data load. ... View more