Markings GIS Maintenance
This Wiki covers the Markings Work Order Digitization Process, Attribute Rules, Attribute Schema, and Domains.
Last updated
Was this helpful?
This Wiki covers the Markings Work Order Digitization Process, Attribute Rules, Attribute Schema, and Domains.
Last updated
Was this helpful?
Was this helpful?
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
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.
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.
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.
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.
Lastly, there will be times when an intersection is given, but does not exist. An example would be W Cesar Chavez St and S 1st St. On Google Maps, it shows S 1st St connecting with W Cesar Chavez St, but in TRANSPORTATION.street_segments both Guadalupe St and Lavaca St continue south of W Cesar Chavez St until they come together at the bridge. At that point it becomes S 1st St. Because of this, the Locate geocoder fails to find the intersection and you have to manually locate it. Again, it is easy to find this intersection as it is well known where those segments are, but can pose a problem if something like Cameron Rd and Pleasant Rd are given as an intersection as it is not as commonly known.Geocoding
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.
Lastly, there will be times when an intersection is given, but does not exist. An example would be W Cesar Chavez St and S 1st St. On Google Maps, it shows S 1st St connecting with W Cesar Chavez St, but in TRANSPORTATION.street_segments both Guadalupe St and Lavaca St continue south of W Cesar Chavez St until they come together at the bridge. At that point it becomes S 1st St. Because of this, the geocoder fails to find the intersection and you have to manually locate it. Again, it is easy to find this intersection as it is well known where those segments are, but can pose a problem with something like Cameron Rd and Pleasant Rd are given as an intersection as it is not as commonly known.
In some cases the Attribute Rule calculating the nearest Intersection ID will pull an Intersection ID from an intersection point that is not connected to the road segment that feature is place on. This is because the Intersection ID is pulled from a Thiessen polygon layer created from the Intersection points. Due to this calculation method, make sure to check the Intersection ID that is calculated when creating new features. This field is editable and a new Intersection ID that makes more sense can be added.
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.
These are Selection shortcuts using keyboard and mouse to select markings assets easier. See the ESRI article on Navigation options—ArcGIS Pro.
