Latest Contributions by RyanKoschatzky

‎03-21-2019

Glad it worked out for you. I would have preferred to have arcs in the data as that is how roads are created and we had arcs in our previous system using esri products. I had hoped R&H being for the transportation industry would have gone to the next level to help with ramps and multimodel (ie rail) and included tools for spiral curves but alas those dreams where crushed.

‎03-20-2019

Joseph, Been there, done that. Not fun fixing arcs. Our migrated was cleaned but when fixing and reloading routes we had used curves to redraw the route. I would caution on using non R&H tools on R&H routes. For example if you use the split tool vs the R&H centerline split tool, it will not update R&H. If you don't have any routes associated with the centerline you can use the split tool. This is been our experience in 10.5.1

Re: GIS-T RHUG SIG Meeting · ‎03-20-2019

I agree, hence this post. I do feel sorry for Nathan, we have John from Alabama. You know that boy is country strong. Won't matter if Nathan tries to go Over the Top, jest saying.

GIS-T RHUG SIG Meeting · ‎03-15-2019

For those going to GIS-T next month in Florida, what would you like to get out of the RHUG SIG meeting? What type of format, questions, etc would you like to see?

Re: Dealing with Coincident Routes · ‎03-15-2019

Mark, See NCDOT's model below: We apply events to the dominant route. Most events represent the pavement, so the route id does not matter. We have at least one event is tied to the route id, so the location doesn't matter. In these cases where the route id is not the dominate route, a second event has to be applied to the dominate section. It is the events that might get gapped but not the routes. In general NCDOT prefers not to have gapped routes. We have an inhouse process to merge all the routes and events together. We can review the output products at GIS Data Layers The current drawback for our method is at 10.5.1 (our current version) is if you add a dominant route to the corouted stack or create a new stack, the events do not transfer up the stack to the new dominant route. They have to be added manually and the existing events have to be manually retired in those corouted locations. If you remove the dominant route, the event will either retire or fall down the stack to the next dominant route in that section correctly. Hope that helps and we can discuss more either on or offline if you have more questions, Ryan

Re: Dealing with Coincident Routes · ‎03-14-2019

Mark, Thanks for the clarification on the model 2 source, that said can you share the other options that you provided?

RH_User_Group_March_2019.pdf · ‎03-13-2019

Recorded meeting https://meetny.webex.com/meetny/lsr.php?RCID=195ca2b57ec645dc9cfc13f1978470b9 Chat window: from Jeromy to everyone: @Nicole ITD - Are your SME's entering the data within RCE located in other places other than your HQ building? ex. In other Idaho DOT buildings...districts, areas... from Nicole (ITD) to everyone: Yes, we have people in the HQ building, and in district buildings entering data into RCE. The furtherest right now is in Shoshone (its about the middle of the "fat" part of Idaho. from Nicole (ITD) to everyone: The end goal is to have all the districts entering data into RCE, and also the Local Highway Districts (LHD) entering data through redlining (using R&H, but it's an external app that'll be created as the LHD are not internal to ITD. from Jeromy to everyone: Good stuff...might hit y'all up later regarding performance and dealing with locks among "disconnected" users. And yeh, we are in the process of opening up our Redline semi public facing...good time;] Thanks. from Kevin Hunt to everyone: New York is in the process of loading capital project locations from the past into R&H so we would also be interested in a standardized tool to "backdate" events in R&H. from Nicole (ITD) to everyone: No probs! I'll be at GIS-T if you want to chat then too? from Jeromy to everyone: For sure...I will be there. from Patrick Whiteford to everyone: I would like to touch base at GIS-T on this too. from Nicole (ITD) to everyone: Sounds good Patrick! from Jeromy to everyone: Good with me. Looking forward to it. from Ryan to everyone: I would love to be part of this discussion with you all too! from Jeromy to everyone: I can grab everyones email from Patrick and get times from everyone...and plan a quick discussion from Michael Clement to everyone: Iowa wants temporality to stay, we use it a lot from Nicole (ITD) to everyone: Idaho isn't concerned about going back intime to make edits. from MnDOT to everyone: Minnesota will also be a part of the discussion at GIS-T from Jeromy to everyone: @MnDOT - Alright the more the merrier! from Nicole (ITD) to everyone: There's a lot of good places around there that we can meet and chat. from Steve H. - Maricopa County to everyone: We would like to have a route/referent geocoder. We would also like to have it as an AGS service. from Claire Inbody to everyone: It would be useful for local projects at Nebraska DOT. Due to lack of information for the projects (we wont have a route and log mile for it) from Steve H. - Maricopa County to everyone: Mic isn't working sorry. from Steve H. - Maricopa County to everyone: All of our events are located by route/referent. Not measures! from Steve H. - Maricopa County to everyone: Measures mean nothing to our SME's. They all understand "on road", "from referent offset" and "to referent offset". This is how we capture event locations. from Steve H. - Maricopa County to everyone: We do have a python lrs geocoder but it would be nice to have one out of the box. from Claire Inbody to everyone: Yes I would like to see what you have. from Tom Tyndall to everyone: Tom Tyndall's email is : [email protected] from Blaine Hackett to everyone: Yes, very helpful from Claire Inbody to everyone: Yes great to hear what folks are doing from Jeromy to everyone: I thought it went great man! Thanks! from MnDOT to everyone: Great format and discussions today!

Re: March RHUG - Facilitated Discussion · ‎03-06-2019

Great questions Patrick.

‎03-06-2019

Kyle, Yes, I was referring to the database log file. We topped over 200GB on log file that day. Since we are have not implemented using temporal polygons, we have given up on event temporality for a few select events. We truncate those events before running the process when we have new polygons, that way we only have 350K adds as the deletes already taken care of in a statewide run. Hope that helps.

How do you model your route ids? · ‎03-06-2019

How and why do you use what you have? Here at NCDOT, we currently use an 11 digit number. The first 8 digits have been in place for decades (1960's or earlier). The last three have only changed slightly from 2 digits before R&H. That change brought the LRS group in compliance with the rest of the enterprise.

‎03-06-2019

Nicole, My understanding is R&H Route dominance is all or nothing system wide and as you make changes to that configuration it will only apply moving forward and not update existing event data. It will only really apply to location where there is concurrency. It has been my experience in 10.5.1 the event data will also only move events down the stack of routes with an edit operation (realign or retire) to the correct route. The event data will not move up the route stack if you add a more dominant route in that location. You/business owners will have to go into Event Editor and reapply those events manually to the new route and depending on your business rules and data checks you will also have to manually retire the other events in those locations. For NCDOT, based on our 11 digit route id (see below) we have applied these rules, lesser is applied to all of the following: RouteClass, RouteQualifier, RouteNumber, RouteInventory, the reason for having inventory at the end is we have a few cases where routes flow opposite of each other (example I-73/74 in Richmond, Montgomery and Randolph Counties). If looking at only inventory direction of concurrent routes on a divided highway, you would have to show both sides. I-73 Northbound (inventory) is corouted with I-74 Westbound (opposite inventory) and I-73 Southbound (opposite inventory) is corouted with I-74 Eastbound (inventory). I-73 is the dominant route, regardless of the inventory code. Hope this helps.

‎03-05-2019

Maja, All our LRS editors have a training class on our documented business rules that must complete before they are allowed to edit in production. This includes them editing individually on a lower stage and having an experienced editor seat with them for while when they start editing on production. Our route id is 11 digits. Different routes classes have different uniqueness. Some are one number per county and others for the state. We have a simple counter program to track the next number. Roads and Highways does have some time overlap prevention and warnings built in. On top of that we have a robust data reviewer process set up that editors must run before posting. We also run system wide checks frequently to ensure bad data is not getting through. Since we edit in SDE, we can and do delete editors version when there is issues. While that might be extreme, it is quicker and safer to redo the work then to troubleshoot the existing problem and deal with unknown downstream issues. Most folks learn from these experiences and helps to prevent future issues. Its not 100% but education, training and verification help to cut down on the issue. Hope this helps and answers your question.

‎03-05-2019

Kyle, I would have done any work in a version and not on default, so you have an easy way to back out. I agree that a smaller batch would be better to try. While overall it might take longer, the risk is minimized with smaller data sets. I know when we have run our statewide spatially derived tool our adds and deletes are over 350K each for the three different event feature classes. I run this in a "edit" version, as you may recall this is at two levels removed from default (default, lockroot, edit) for NCDOT. Between each run, I would post to lockroot, others would post further but before they do, they run analyze, reconcile, post, sync replicas, analyze and compress before the next run. If you have to end the process, I would restore to before the process. You last known good. Some questions I would have are: do you need that many gaps? For our data we find it best practice to renumber the other side of the gap. For us the route name is not part of the route id. That is done as an event (streetname). Do you have an index and are there any null values on those indexes that could be slowing things down? Are you running any log files. As I recall with our spatially derived process I had filled up the log files and that crashed the process.

RH_User_Group_February_2019.pdf · ‎02-14-2019

Recorded meeting https://meetny.webex.com/meetny/lsr.php?RCID=a1df48f4aef646449e4cdbe4aaa143ca Chat window: from Amelia to everyone: Are batch jobs for DR still availabe in ArcPro? from Phil Hardy - AgileAssets to everyone: On the event overlap and gap checks can these be filtered? An example would be checking pavement condition records for every year. Within a year we are worried about overlaps and gaps, but not between years. Can this be accommodated?

RHUG 2/13 meeting chat question · ‎02-13-2019

During the data reviewer demo, the following question was asked in the chat window and was not answered. On the event overlap and gap checks can these be filtered? An example would be checking pavement condition records for every year. Within a year we are worried about overlaps and gaps, but not between years. Can this be accommodated?

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by RyanKoschatzky

Re: Roads & Highways - Extending middle section of multipart route

Re: Roads & Highways - Extending middle section of multipart route

Re: GIS-T RHUG SIG Meeting

GIS-T RHUG SIG Meeting

Re: Dealing with Coincident Routes

Re: Dealing with Coincident Routes

RH_User_Group_March_2019.pdf

Re: March RHUG - Facilitated Discussion

Re: bulk calibration of gapped local roads

How do you model your route ids?

Re: Trying to update Route Dominance

Re: In R&H; How do you ensure that primary key attributes - like the Route-ID - are and remain unique?

Re: bulk calibration of gapped local roads

RH_User_Group_February_2019.pdf

RHUG 2/13 meeting chat question

Re: It is too easy to accidently make an edit in t...

Re: Export Network in Arcgis Pro

Re: RH_User_Group_August_2024.pdf

Re: Modelling individual lane information.

RHUG working groups

Roads and Highways User Group (RHUG)