1. Centerline Unification through AZGEO
AGIC 2016 Track: Address NG Applications
Thursday, Sept 22nd 2016, 3:30pm
Joe Breyer, Ryan Blum Works Consulting

2. What We’ll Cover: Supply Chain Workflow / History
What’s on the AZGEO app
Six of the topologic issues found with centerline files for use in LRS building.
How they are currently found / exposed back to the database owner.
The future of the quality assurance procedures on AZGEO utilizing 1integrate rules engine from 1spatial.
Points, Lines, polygons are all supported.
Any feature class essentially become an LRM – so long as it has feature that cross the inventory routes.
Inventory routes could be rails or rivers in addition to roads.

3. The History of The Centerline Unification supply chain:
ADOT launched “Centerline Unification” project in 2012
Toward satisfaction of the federal “All Roads” initiative
Using ADOT’s centerlines for State Highways
Using E-911 systems as 15 local centerline providers
1 cross-state tribal centerline – no addresses (Navajo Nation)
21 (20 others + Gila River) in-State tribal centerlines – no addresses
3 months of integration work (per source) – now < 4 hours each
Local gov’ts have been good partners in providing data…
….and responding to ADOT-driven editing “requests” (through AZGEO)
Points, Lines, polygons are all supported.
Any feature class essentially become an LRM – so long as it has feature that cross the inventory routes.
Inventory routes could be rails or rivers in addition to roads.

4. website

5. Statewide gis data supply chain

6. Benefits to all involved Ship ADOT a Report of Changes
Mine Address (and other) Attributes into LRS events
15 sources edge-matched and unified
Benefits to all involved
Ship ADOT a Report of Changes
Editing occurs in One Agency per Road
Make Roads Meet at Boundaries
The Supply Chain
County Transmits Data thru AZGEO
Use ArcMap, unpack, provide feedback
Check & Eliminate Bifurcations
Ship Locals a Report of Changes
Compare This Submittal to Last
Auto-detected issues sent to owner
Assemble Statewide from 15 sources
Points, Lines, polygons are all supported.
Any feature class essentially become an LRM – so long as it has feature that cross the inventory routes.
Inventory routes could be rails or rivers in addition to roads.

7. THE PRODUCT:
Statewide complete centerline file endowed with address attributes for E-911 and NG 9-1-1
Statewide Linear Referencing for ADOT and the COG/MPOs

8. Benefits from the Statewide GIS Mapping Supply Chain
Linear Referencing System
Regional, State, National Layers
Quality Assurance/Control
Edge-matching through Demarks
Conflated & Condensed Output
Minimize Resource Requirements
Addresses and Attributes as Events
Metrics on GIS Responsiveness
Offsite Copy

9. CURRENT Centerline Quality Checks (Lrs data reviewer)
Concept of the LRS data reviewer has been around since early 2000’s as we saw the efforts in upgrading county centerlines into Arizona’s centerline file.
Began to materialize as a formal process when offering LRS based solutions for regional government agencies
Truly evolved into repeatable documented process during Arizona’s centerline unification efforts.

10. What to Do?
Utilize rich sources of local centerline/roadway data for use within larger geographic applications?
Each local agency has different database design (schema)
Each local agency commonly has specific area of focus (collection methods, rules, etc.)

11. Topological Data Issues
Dangles (& Overshoots)
overlaps
Non-Linear Segments
Centerline not correctly or not enough precision used when collecting/digitizing.
Centerlines overlap each other due to negligent collection techniques or due to design.
Centerlines contain arcs or curved segments.
Stacked vertices
Z-CUTBACKS
BIFURCATIONS
Duplicate vertices created at intersection points due to editing or created during gps data collection.
Incorrect vertices placement due inaccurate editing techniques or created during gps data collection.
Bifurcated routes created due to inaccurate centerline naming or due to inadequate description of roadway specifics.

12. Dangles
(& Overshoots)

13. Dangles (& Overshoots)
The issue: Dangles create inaccurate route networking and location naming as well as erratic ESRI comparison tool results.
THE SOLUTION: Use ESRI data reviewer to flag dangles within a centerline for owner fix…or if needed, fix using ESRI supplied solutions.
THE RESULT: More exact centerline allows for more exact solutions.
AND ULTIMATELY: Instances of dangles and overshoots dramatically reduced.

14. Stacked vertices
THE ISSUE: stacked vertices (two vertices with the same x,y location consecutively within the same line) can create erratic ESRI comparison tool results due to invalid geometry.
THE SOLUTION: use ESRI data reviewer to flag these locations within a centerline for owner fix.
THE RESULT: centerline data that facilitates comparison across versions.
AND ULTIMATELY: more accurate centerlines.

15. Overlaps
THE ISSUE: overlapping centerlines can create erratic ESRI comparison tool results. Overlapping centerlines can be valid.
THE SOLUTION: use ESRI Data Reviewer to flag overlaps within a centerline for owner review. If valid ask owners to indicate which is higher order road. (If needed) group overlapping centerlines to be able to analyze accurately.
THE RESULT: removal of all errant overlaps and firm understanding of valid ones.
AND ULTIMATELY: more accurate centerlines network.

16. Z-cutbacks
The issue: Z-cutbacks create inaccurate route lengths and hinder accurate analysis.
THE SOLUTION: Use ESRi Data Reviewer to flag z-cutbacks within a centerline network for owner fix.
THE RESULT: Centerline data that can be used for accurate length analysis.
AND ULTIMATELY: More accurate centerlines network.

17. Non-Linear Line Segments
THE ISSUE: Non-linear line segments cannot be used within ESRI Roads and Highways.
THE SOLUTION: They can be removed from a centerline network using the esri densify tool.
THE RESULT: centerlines can be used within ESRI Roads and Highways extensions.

18. Non-Linear Line Segments
THE ISSUE: Non-linear line segments cannot be used within ESRI Roads and Highways.
THE SOLUTION: They can be removed from a centerline network using the ESRI densify tool.
THE RESULT: Centerlines can be used within ESRI Roads and Highways extensions.
NON-LINEAR SEGMENTS

19. Non-Linear Line Segments
THE ISSUE: Non-linear line segments cannot be used within ESRI Roads and Highways.
THE SOLUTION: They can be removed from a centerline network using the ESRI densify tool.
THE RESULT: centerlines can be used within ESRI Roads and Highways extension.
NOW ALL LINEAR SEGMENTS

20. the lrs Problem – BIFURcations
THE ISSUE: Bifurcations create routing issues, which Lead to ambiguous events due to non-unique measures.
THE SOLUTION: They can be removed from a centerline network automatically within the LRS data reviewer process.
THE RESULT: Topologically correct routes.
AND ULTIMATELY: AUTOMATION Is unnecessary through response to feedback reporting.

21. the lrs Problem – BIFURcations
The issue: Bifurcations create routing issues, which lead to ambiguous events due to non-unique measures.
THE SOLUTION: They can be removed from a centerline network automatically within the LRS data reviewer process.
THE RESULT: Topologically correct routes.
AND ULTIMATELY: AUTOMATION is unnecessary through response to feedback reporting.

22. the lrs Problem – BIFURcations
The issue: Bifurcations create routing issues, which lead to ambiguous events due to non-unique measures.
THE SOLUTION: They can be removed from a centerline network automatically within the LRS data reviewer process.
THE RESULT: Topologically correct routes.
AND ULTIMATELY: AUTOMATION is unnecessary through response to feedback reporting.

23. the lrs Problem – Bifurcations
THE ISSUE: Bifurcations create routing issues, which lead to ambiguous events due to non-unique measures.
THE SOLUTION: They can be removed from a centerline network automatically within the LRS data reviewer process.
THE RESULT: Topologically correct routes.
AND ULTIMATELY: AUTOMATION is unnecessary through response to feedback reporting.

24. the lrs Problem – BIFURcations
THE ISSUE: Bifurcations create routing issues, which lead to ambiguous events due to non-unique measures.
THE SOLUTION: They can be removed from a centerline network automatically within the LRS data reviewer process.
THE RESULT: Topologically correct routes.
AND ULTIMATELY: AUTOMATION is unnecessary through response to feedback reporting.

25. the lrs Problem – BIFURcations
THE ISSUE: Bifurcations create routing issues, which lead to ambiguous events due to non-unique measures.
THE SOLUTION: They can be removed from a centerline network automatically within the LRS data reviewer process.
THE RESULT: Topologically correct routes.
AND ULTIMATELY: AUTOMATION Is unnecessary through response to feedback reporting.

26. Other Data issues found
Variance
SOURCES
DATA
DIFFERENT
Fields containing same data have different names across local data providers.
Fields contain more than one data item – need to parse different data items into specific fields, (Also QAQC results) to accurately collect data (road name & pave type).
Full Road names were parsed between many fields - Many different fields needed concatenation to create single source field.
Full road networks were parsed between many feature classes - Multiple feature classes needed concatenation to create single source road network.
Some local agencies have more than one master centerline/roadway file – had to run process to compare different files to create one source file for road network.
Road networks are using different projections – need to re-project incoming roadway files so as to have all incoming files using same projection.
Road network files contain more than roadways – need to remove non-roads from data (RR).
Data not complete – blank names, etc. need to be filled in before can be used in road networks.
Data has errors – need to run QAQC to clean up simple issues before using road networks (double blanks, no shapes, 0 shape length, non-standard characters).
Roadway network issues – overlapping centerlines, bad snaps, gaps, etc.

27. Future Centerline Quality Checks (1integrate by 1spatial)
Server solution which is contained completely within the AZGEO server infrastructure.
Allows for direct interaction by the data owners.
Prepares for full automation of Centerline Quality Checks.

28. AZGEO Website (azgeo.az.gov)

29. AZGEO Website (azgeo.az.gov)
Click on the “Arizona GeoData Supply Chain App”

30. AZGEO Website (azgeo.az.gov)
Click on the “Validate Your Data” button.

31. 1integrate for Server

32. Questions? Joe Breyer, PE, GISP Works Consulting
Phone: x301
Ryan Blum
Works Consulting
Phone: x303