POST
|
The Roads and Highways User Group will meet the second Wednesday of every month from 12:30-2:00pm EST. Please contact Erin Lesh (ealesh@ncdot.gov) or Patrick Whiteford (pwhiteford@azdot.gov) if you have any questions or suggested topics for upcoming meetings. Each month, the agenda and virtual conference information will be added to the meeting invite and posted on the RHUG Geonet site. AGENDA: Announcements Esri Updates Discussion – Esri backpatching; LRS Training topics; LRS-enabled polygons
... View more
3 weeks ago
|
1
|
0
|
129
|
POST
|
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
3 weeks ago
|
1
|
0
|
17
|
POST
|
The Roads and Highways User Group will meet the second Wednesday of every month from 12:30-2:00pm EST. Please contact Erin Lesh (ealesh@ncdot.gov) or Patrick Whiteford (pwhiteford@azdot.gov) if you have any questions or suggested topics for upcoming meetings. Each month, the agenda and virtual conference information will be added to the meeting invite and posted on the RHUG Geonet site. AGENDA: Announcements Esri Updates Presentation - Complex Routes in Pro – Esri Discussion - R&H for non-highway features Event address for attendees: https://ncgov.webex.com/ncgov/onstage/g.php?MTID=eb2ee35640ae2c3d299de833cf0918e53 Event number: 178 311 7447 Event password: GasjXCCM574 Audio conference: To receive a call back, provide your phone number when you join the event, or call the number below and enter the access code. US Toll +1-415-655-0003 Access code: 178 311 7447
... View more
12-07-2020
10:34 AM
|
1
|
0
|
55
|
DOC
|
Audio @ https://community.esri.com/docs/DOC-15551-rhugmeetingoctobermp4
... View more
10-15-2020
11:18 AM
|
0
|
0
|
53
|
DOC
|
10-15-2020
10:28 AM
|
0
|
0
|
76
|
POST
|
Colin, I would think you could get rid of the calibration point as a route only needs two calibration points. What would be the use case for removing the calibration point? I know for us, we rarely mess with the calibration points directly. A large portion of our routes have more then two calibration points.
... View more
10-15-2020
07:28 AM
|
2
|
0
|
70
|
POST
|
Colin, NCDOT has 8 different business units using R&H. One business unit is responsible for the LRS and a few events. The rest only maintain their specific events. A data governance plan can help flush these details. Each business unit has their own wmx workflow jobs tailored to their business unit needs and permissions are controlled by their AD group (permissions is handled outside my group so I could be all off on the details). The same with Data Reviewer checks. While the jobs and DR checks have some common elements we allow each to be different because not all events are the same and not all business unit work the same. We have some with only one editor or up to 7 editors. A lot depends on how GIS experienced the business unit is and we have wide range of users. Most wmx jobs are based on a unit of work (need to fix some values, transportation project is completed, QC of legacy data, etc ) and can be open for one day or for the whole quarter. We go to state zero (no versions) 4 times a year as part of our publication and maintenance plan. Here is an example of the wmx jobs we have created for our LRS editors. Other business units only have one or two different jobs. One to edit and one for QC work. We use Default and Lock Root. Lock Root being Public and Default is Protected. We have a nightly script to post Lock Root to Default. We also have an edit and publication databases. Event owners have access to their data on edit and all other data comes from the publication stack as read only is my understanding. We use Conflict Prevention We can talk offline and to discuss the finer details if need be. Hope this helps.
... View more
09-25-2020
06:10 AM
|
1
|
0
|
147
|
POST
|
As Amit said Route Name is a more human-readable format. Here is an example of our concatenated Multi-Field Route ID with Route Name field. RouteClass US Route RouteQualifier Normal Route RouteInventory Non-Inventory (Southbound) RouteNumber 29 MaintCntyCode Mecklenburg MilePoint_ID 20400029060 RouteName US-29
... View more
09-15-2020
11:54 AM
|
1
|
0
|
38
|
Online Status |
Offline
|
Date Last Visited |
a week ago
|