Latest Contributions by RyanKoschatzky

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

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