Latest Contributions by RyanKoschatzky

Hi Courtney, Another resource for active users of the R&H product is RHUG, Roads and Highways User Group (RHUG) . Lots of good information all over the site. Most of the members (State, County and City) are not currently using the Pro version of the software as it is not at a 1:1 match for desktop functionality for most of our uses/business practices but it may be at that point for your use. Most folks are using 10.5.1 and have or in process of migrating to 10.7.1 til Pro is ready for us to make to that switch. For 10.5.1 we use SDE and have many different business units internal and external editing and consuming the data. Hope that helps. ... View more

Maja, We don't do desktop event editing. Nathan Easley should be able to answer your question about the toolbar. What I prefer to do is analysis the event data and issues on desktop and fix the issue in the table view within Event Editor or reapply new data and retire the existing records. When doing the table edits I use the Identify LRS Route location tool set to my event precision and select the location along the route where the event should change, then in Event Editor query the route id on that event layer. I use a copy/paste of the location measure from  Identify LRS Route location tool and apply the values in  the correct to/from fields.  Outside of individual editing we have used 3d party vendor tools to modify event data statewide. We can talk offline about that if you wish. ... View more

Nicole, We have made very similar fixes but I have some additional questions that might impact the fix or at least for us it can.  We use from date as the route start date, does 343D have the same from date as what 24D would have? Is 343D is built correctly if it was 24D? Does 343D have to exist when the fix is complete? I am also going to assume 24A is dominant over 343D, is that correct? Is 24D an active route anywhere else? What version are you using? We are still on 10.5.1 so it might would slightly different for you.   Our rules would require us to coroute 24A and 24D where possible, so 24D would start from the end of 24A to the start of 24A unless the begin/end is divided/couplet situation. Where corouted we would only apply event data on 24A and not 24D. Event data for 24D would only exist where 24D is the dominant route. To fix assuming 24D exists nowhere else and dates are equal between 24D and 343D, I would create 24D along its correct alignment, so it would be corouted with 343D and click apply updates, the events would not move up the route stack to 24D because of a bug and stay with 343D. Then retire 343D with it's same from date and click apply updates. By having the same from/to date 343D would not exist anymore in the data which seems to be correct as the route number was in error. You can still find the location but you would not have the timeslice active to select again. The events that where on 343D should then be applied to 24D and there should not be any changes to the 24A events. For us 343D would have a direction event of southbound and 24D would be have a direction event of westbound. We would have to edit the event record to show this change as opposed to adding a new record as the event timeslice would then still show an error. Other event data might also need to be updated if a similar event type scenario exists. ... View more