Markings GIS Maintenance
This Wiki covers the Markings Work Order Digitization Process, Attribute Rules, Attribute Schema, and Domains.
Version Editing
The version ATD_ADMIN. ATD_Markings has been created, and it is under this version that individuals will work in separate versions while digitizing markings.
All attribution will occur in the working version that a user creates under the ATD_ADMIN.ATD_Markings version.
Edits are then reconciled and posted to ATD_ADMIN.ATD_Markings
Edits are then reconciled and posted to DEFAULT
Creating an Issue in GitHub
In GitHub there is an Epic that has been created to house all of the Markings Work Orders for each year. Search for Markings Work Order QA/QC - year under Epics in GitHub.
When Submitting an Issue
Use the date you start working on that set of work orders to fill in the mm/dd. The tags for the work orders are generally Impact: 3 - Minor, Service: Geo, Type: Data, Workgroup: SMB.
Finishing the Issue
There are times where you will have worked on more work orders then you started with and that is okay. Filling in the values for short line, specialty line, and specialty point features is done by sorting by the MODIFIED_DATE field and then selecting everything that was modified since you started on that set of work orders and grabbing the number of records selected.
Things to look out for
Finding the Location of the Work Order
One of the best things to do when there is an issue trying to find an address or intersection is to look at the attached plans. Generally there will be a way of identifying where the work was done, be it a line drawing from CAD or a marked up aerial image. But, there are times when there is no plan attached to the work order and you only have what comments may exist or the work that was actually completed.
An issue that comes up is when a road is incorrectly named in the work order. An example would be a work order that said work was done on 46th St when it was really on 45th St. Sometimes there will be comments in the work order saying it was done on this street instead of that one, but sometimes the work being done needs to be taken into context to correctly identify the street work was completed on.
One of the best things to do when there is an issue trying to geocode an address or intersection is to look at the attached plans. Generally there will be a way of identifying where the work was done, be it a line drawing from CAD or a marked up aerial image. But, there are times when there is no plan attached to the work order and you only have what comments may exist or the work that was actually completed.
An issue that comes up is when a road is incorrectly named in the work order. An example would be a work order that said work was done on 46th St when it was really on 45th St. Sometimes there will be comments in the work order saying it was done on this street instead of that one, but sometimes the work being done needs to be taken into context to correctly identify the street work was completed on.
Attribute Rule - Intersection ID
In the example above, if any feature were to be placed along E Stassney Ln along the mid-point between Intersection IDs 5152923 and 5154236, it would have an Intersection ID that is not from either intersection along E Stassney Ln, and will instead be coded to the neighborhood street to the north.
Keyboard Shortcuts
Last updated
Was this helpful?