Latest Contributions by RyanKoschatzky

Graeme, Glad to hear it is helpful. I would set a personal calendar appointment with this link as I update the agenda and connection information monthly.  https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/rhug-monthly-user-meeting-agenda/m-p/1046315 In that thread there is also an excel file - RHUG meeting agenda master.xlsx that has all the previous agendas and links to all the presentations and recorded audio if available. It is also updated monthly after the meeting usually no later then Friday after. ... View more

I know that this thread relates to using Roads and Highways in ArcMap but I am wondering whether similar functionality exists when using Roads and Highways in ArcGIS Pro 3.0.0? In other words, if @ElAttar__Ihab was using ArcGIS Pro 3.0.0 when they asked: I loaded routes successfully in my network. I have a few gapped routes, lollipops and some loops in my network. Is there a tool to flag lollipops or  loops that have not properly calibrated on the initial load of the network ? what would the answer be?   ... View more

At INDOT we manage a large number of roadside assets off the linear referencing system using a combination of mobile and web based editing. Critical to these inventories is to have a human readable unique key be DB generated (on create) for every record and to offer a record ‘retirement’ method instead of offering a record ‘delete’ method. Workflows like the corridor sign replacement require a-spatial lists of data ordered by combinations of route/direction/side/measure/administrative unit. To do this: A one time effort is required to associate each asset to its reporting route_id and use geometry2measure to interpret a measure. Event data containing minimum fields like the unique key of the asset and it’s route/measure/from_date be loaded as an event into R&H. Regularly, FME is used on a frequency to: Compare differences between event records and non LRS assets to communicate: Need for retirement or end dating in either repository when mismatches in lists are evident. Theis can trigger a manual exploration/evaluation or trigger direct event and/or asset update. Data for inserts into the event layer when new inventory has been collected or retired. Data for updates to the event layer when changes in location have been detected in the last and current geometry. Finally, FME is used to; on a frequency, join asset inventories with linear referenced records to create directionally ordered lists of assets for use in the field for inventory completeness checks, sign orders and work orders. Using FME rather than an ESRI solution is IMHO more flexible and tailorable to the individual and ever moving requirements of these integrations. ... View more

I went through the tech-support and they filed a bug for this issue: BUG-000149190. ... View more

Hi Nathan, Noted and thank you for your response! Ed ... View more

"The goal is to use a version of the LRS network with the HPMS application where network edits were not performed beyond a specific date (10/1/2021). This will just need to be a static version."  Doesn't help now but it might in the future, we export sde at our quarterly cutoff to save a static version. So all our submitted edits have to happen before then otherwise it goes into next year's submittal.  ... View more

Hopefully you know routes impacted to limit the review and have a copy of the before dataset to compare the smaller dataset, not sure of another method. Hopefully others have some more ideas.  ... View more

Colin, We model that information as events and have split them out among many feature classes to account for the way each attribute can and do change for the level of detail we want. The bold is the feature class name and then fields for each. Lane miles is a post process calculated field in our publication data. LRSE_LaneWidth LaneWidth LRSE_Surface SurfaceDetail SurfaceThickness SurfaceType SurfaceWidth LRSE_ThroughLane LaneMiles ThroughLaneCount LRSE_LeftShoulder LeftPavedShoulderWidth LeftShoulderWidth LeftShoulderType LRSE_LeftTurnLane LeftTurnLaneType LeftTurnLaneWidth LRSE_RightShoulder RightPavedShoulderWidth RightShoulderWidth RightShoulderType LRSE_RightTurnLane RightTurnLaneType RightTurnLaneWidth LRSE_Median MedianType MedianWidth LRSE_Base BaseDetail BaseThickness Here is the link for the metadata for each field. https://xfer.services.ncdot.gov/gisdot/DistDOTData/NCDOTRouteCharacteristicsFieldDescriptions.pdf Probably more then it seems you want to do but simple to us/me and basically what we have used for the past 15 years. We can discuss more in-depth you if want.  ... View more