Latest Contributions by RyanKoschatzky

NCDOT, I have attached our 11 digit route id Field is RouteClass, RouteQualifier, RouteNumber and then RouteInventory We have two spots where Interstates are concurrent, but inventory direction is on opposite sides of the road. This order keeps the routes paired and prevents an inventory of the higher number trumping the opposite inventory side of the dominate pair. ie I-73 southbound is dominate over I-74 eastbound. We have no exception table like Kansas.  ... View more

Sam, We have had the issue in the past not as much now that I recall. Most times we find it’s a retired benign record (same From/To date) that has been left off centerline because of cartographic realignment. A few things, we use wmx to create our mxds, the point being is we have all the layers in the TOC unselectable at launch minus centerline. This is the first line to preventing the issue. Second, we use data reviewer that has a 1’ buffer around only the locked routes for that user in that version to cutdown on processing time. We use a geometry on geometry check, milepoint over centerline to find any issues before posting. If possible I will have them delete the version and try again as that is better then trying to fix the issue (this goes for most errors) once posted. As for a fix, on a lower stage I would try reshaping milepoint using trace on centerline to get them back in synch with each other. Hope that helps. Let us know if that works. ... View more

It's that time of year again. TransactionDate > '1/3/2020' AND TransactionDate < '1/1/2021' AND ActivityType = X Edit log Code/R&H Route action name/number of records 1 Create Route 3274 3 Reverse Route 69 4 Retire Route 1421 5 Extend Route 1446 6 Reassign Route 583 7 Realign Route 844 12 Cartographic Realignment 84236 Total 91873   ... View more