Latest Contributions by RyanKoschatzky

Welcome, that location would have been a nice to know 2 years ago when you guys hosted GIS-T.  I would be interested in seeing what you guys are creating. While I spend most my time with LRS data, I have been spending some time in in traffic safety space so we can better serve that group.  Another space to watch is Roads and Highways User Group (RHUG) ... View more

Ana, I don't know why you would get that but I would recommend posting on the RHUG geonet page @ https://community.esri.com/groups/roads-and-highways-user-group-rhug  Ryan ... View more

Samuel,   Interesting, a few thoughts as I percolate on the idea, the domain list for layer and especially type might get to long and that could lead to selection of incorrect types. Secondary the QC to ensure that doesn’t happen might be too complex and/or time intense.   Depending on construction techniques (really stepping outside my knowledge base) the events changes might be at more intervals and time than the data model can support as one event at least conceptually in my mind.   I could see breaking out the pavement event to include more event tables: ie Seal Coat, Surface, Binder, Base Subbase etc. Then creating a product outside R&H that overlays the events onto the linework. Calculate a field that takes into account all the pavement layers and gives the total for that segment.     Also, just spit balling, why not also add in a date field, you can capture when the material was applied.   I don’t think you should call it surface event as it is more than just that. Something like pavement event might be more appropriate to encompass all aspects of the event. ... View more

Colin, Instead of changing event 1 and retiring event 2. Why not add event 3 to the new alignment, using beginning and end toggle button. That should retire event 1 and 2. A manual option to cover behavior.  ... View more

Blaine, Sarah's team has done a good job setting this up for our enterprise to use inside and out of R&H. I would recommend verifying locations after running the tool as we have had areas that did not repopulate with new points and measures. BUG-00110740, fixed in 10.6.1 according to esri. As we are still at 10.5.1 I cannot confirm that. We did take the intersection point fc to help identify where milepoint was not connected to the network. MilePoint_ID in (select distinct milepoint_id from rome.LRSN_MilePoint_evw where todate is null except select distinct routeid milepoint_id from rome.LRSI_IntersectionPoint_evw where todate is null) and todate is null Found 11 legacy system routes that where islands onto the network that I am not sure I would have come across any time soon and another 33 routes that had topology issues. Most of the 33 routes go back to 10.3.1 days when we didn't have the robust system in place that we do now to catch these issues.  ... View more

@Nicole, that is how we have been using polygons to date. I think that having temporal polygons would be helpful for when people are using the timeslider, so the boundary data would match the routes and events vs having current boundaries and old routes and events. That sorta begs the following question, are people using the timeslider?  I uploaded an old GIS-T presentation that might help illustrate the issue of temporal polygons (pg 12-14). When I have time in the future I will try update the illustrations to be more useful.     GIST-T 2016 NCDOT evolution of temporal polygons for spatially derived events.pdf  ... View more

A few questions: Anyone using temporal polygons (ie city/town/county boundaries)?  Anyone doing any temporal QC’ing? If you have any routes that have been edited multiple times and the timeslices don’t line up correctly, is the delete routes tool (10.6 or higher) working for you? Did you have any coroutes involved? Would a delete timeslice option be preferred? Have you tried to save your event data and how did that go?  ... View more

We have a few location like this, two that come to mind are both Interstates. I-73/74 in Randolph and Montgomery counties and I-73/85 in Guilford county. For NC to follow your example US-54 would be the dominate route regardless of direction. All events* in R&H would go on US-54. Only US-54 would be counted for mileage as the dominate route. AADT is collected wherever/however we represent the route. We only collect AADT on ramps if safe and grade separated. Pavement is collected wherever/however we represent the route. They are a great resource to make sure we have all routes divided when they should be. If they have no place for the data, they are a unhappy customer.  Samples, we do not collect samples on ramps. We do have a different route type for ramps. Our HPMS coordinator is out til Oct, but I don't she would collect on a route/ramp flyover in these cases. *Fed Truck Route/STAA is different but that is story for a different time but we would have Truck Route marked on US-54 if it applied. ... View more

Andrew,  While the date/time may help for the external system, any and all queries you do will need to account for the date/time. When we looked at doing something similar that added too much complexity to a complex issue. We discovered a number of events I had entered in bulk through EE had date/time and I worked to change the values to be date only. Probably thought of this but can you use last edited date to grab just the active route record you need and not the other benign records? ... View more