Latest Contributions by RyanKoschatzky

I know some states have the street name in the route id so the field has to be variable. You can set the routeid as text or concatenation.  https://pro.arcgis.com/en/pro-app/latest/tool-reference/location-referencing/modify-route-id-padding.htm How you are you currently modeling the geometry for the lanes? Do you have one centerline for each lane or all the lanes? You could model either way. Main difference comes down when you make changes to the alignment of the route. Do you want to do the change once or many times (once for each lane)? That is a business decision.  You could have single centerline geometry for the route and an event for cracking that had fields for lane value and cracking value. All or some event feature classes could be set up like that. You could combine cracking, skid resistance, fwd etc in one or many feature classes. The more changes in the values, the more likely I would be to separate the different feature classes. Again, that's a business decision. You could have a single centerline geometry for each lane and an event for cracking with just a field for cracking value.  You could have single centerline geometry for the route and stack each lane as a separate routeid and an event for cracking with just a field for cracking value. Just case it’s possible doesn’t mean it’s the best option. I think this might be too messy but it’s a business decision. Hope that helps some. Ryan ... View more

I agree with Kyle that something like culverts is better as a point feature class in R&H. I would probably add fields for condition, length and pipe bearing to know the direction. R&H does well with events on or along the road ie direction, turn lane. Events perpendicular or types that change along with road like sound walls or ROW just don’t plot well.  ... View more

June's agenda and meeting information has been updated. ... View more

Can you use the time slider or remove definition query to query retired records? ... View more

Can you add a temporary route corouted with 8/2/2023 (old habit, might not be needed with delete routes). Then delete the bad time slices routes and load the correct time slices. Then delete the temporary route, if used. You might be able to keep the events on the delete route. Then maybe change the event From/To Dates. If not, than export the event data, modify the table and append events. A few ways I would try. Would be interesting to see what workflow/s esri would recommend to handle date issues in Pro.  ... View more

May's meeting details have been updated. ... View more

February's meeting details have been updated. ... View more

Thought it would be interesting to see what everyone's numbers where last year and what version your at 10.8 TransactionDate > '1/3/2023' AND TransactionDate < '12/31/2023' AND ActivityType = X Edit log Code/R&H Route action name/number of records 1 Create Route 2534 3 Reverse Route 107 4 Retire Route 638 5 Extend Route 1082 6 Reassign Route 604 7 Realign Route 668 12 Cartographic Realignment 28922 Total 34555 ... View more