Bruce D’ Autremont Digital Data Technologies, Inc. Jeremiah Glascock

1. Developing, Maintaining, and Using Ohio’s Linear Based Referencing System (a.k.a. Location Based Response System – LBRS) Bruce D’ Autremont Digital Data Technologies, Inc. Jeremiah Glascock Traffic Safety Analysis Systems & Services • Make no mistake, this presentation is ultimately about saving money, and most importantly – people’s lives. • We’ve heard DOT people say, “We’re able to map 80% of our crashes and are confident in our ability to locate high- hazard locations.” • This presentation will show you with convincing evidence that they should not be so confident and could be “not saving peoples lives” which is, quite frankly, why we are here.

2. LBRS Concept: Create it once Use it a bunch and Maintain it

3. Defining the Problem Create it once ▪ Use it a bunch ▪ And maintain it

4. Issues at the State DOT Level Every Jurisdiction in the state needs to be on the exact same Linear Referencing System (LRS) using the same Linear Referencing Method (LRM). Integrate a legacy(60+ years) GIS/LRS and create a new system that accurately(+- 1 meter) represents every Public and Private Road in Ohio. Bring mature, effective roadway information standards to this massive road network (125,000 + Centerline Miles) involving all levels of State and Local government. Match crash data effectively to House Numbers/Addresses, Intersections etc.

5. Standardization of Ramps and Interchanges including a complete Ramp/Interchange Inventory System (5,000 ramps)

6. Defining Part of the Local Government Problem Field Verified Point-based addressing – ensures jurisdiction’s homes, businesses, landmarks and other assets will be accurately located. Most do not have this. Geocoding, a mapping method that approximates address locations based on ranges assigned to a road segment, is unreliable for applications that require accurate locations and it wastes time that could save lives. “NextGen” 9-1-1 systems will require very accurate, attribute-rich, field-verified basemap data to function properly.

7. A Road with Many Names US40 Park Road North Street E. National Road Columbia Street E. Main Street W. National Road

8. To create “quality” data, some tried to use An orthophoto to create the centerlines Address data from the Assessor and other departments to populate the addresses It became clear that in order to obtain accurate, reliable data, ALL addresses and roads must be field-verified

9. Issues with Local Address Data Typically, 31% of existing county addressing data is: Incomplete Inaccurate Unreliable Existing 9-1-1 databases are often flawed, as well.

10. Field Verification Exposed Non-Matching Address Data • Fayette County • 4,236 records (37%) did not match 37% 63% 30% • Clark County • 16,882 records (30%) did not match 70% 31% • City of Gahanna (Franklin County) • 4,715 records (31%) did not match 69%

11. Orthophotos prove unreliable for roadway development 25% 37% • Road seems passable in orthophoto, but field-verification reveals otherwise

12. It will be difficult to use this road segment for routing purposes 25% 37%

13. Only field-verification would reveal this road segment as impassable

14. A non-existent bridge in Champaign County, Ohio

15. An unmarked, unpaved road in Jackson County, Ohio on the state inventory as “passable”

16. CREATE IT ONCE Create it once ▪ Use it a bunch ▪ And maintain it

17. Used by federal (high) level applications • Regional, multi-state • Minimal attributes, low resolution • $ INTEGRATION • Used by state level applications • State & Federal Programs • Multi-County Multi-State • More attributes, better resolution • $$ • Used by local level applications • Serve People • Multi-Neighborhood • Most attributes, best resolution • $$$ Create it once, use it many

18. Create It Once – The Solution… Location Based Response System (LBRS) State-level plan for every Ohio county Memorandums of Agreement between the Counties and the State Create spatially accurate street centerlines with field verified site-specific address locations, with emphasis on linear referencing/mileposts

19. What is LBRS, cont’d. • Avoids duplication of efforts • Fed, state, county and local levels were creating independent datasets that met their particular needs • The challenge for DDTI from the initial LBRS pilot project? • Create a dataset that meets the unique needs of the DOT with emphasis on linear referencing/milepost, while meeting the needs of county & local GIS, and most importantly, Emergency Response

20. LBRS Data Input Field Verified Roadway Information and Addresess

21. What’s so unique? The Next Generation Road Network that supports advanced applications contains these attributes…

22. Centerline Address

23. USE IT A BUNCH(a.k.a. – more ROI) Create it once ▪ Use it a bunch ▪ And maintain it

24. Linking Legacy Data to the LBRS

25. Examples of LBRS Users

26. AccuGlobe Extensions AccuGlobe 9-1-1 Dispatch/Mobile/Web used to locate emergency response locations

27. AND MAINTAIN IT Create it once ▪ Use it a bunch ▪ And maintain it

28. Issues With Addressing • PROBLEM: Erie County has 17 addressing authorities. • How do we: • Help them maintain their data? • Integrate it into their daily workflow applications (i.e. 9-1-1)? • With REAL-TIME data synchronization? • With built-in quality assurance?

29. Solution:AccuGlobe 2007 Addressing Plug-In SQL Based system Provides Dynamic(real-time) updating Provides One system for the Master Address Database Secure and EASY to use It’s REAL and it WORKS!

30. Data Maintenance Solution Maintenance software local authorities can use to add, modify or delete roads and addresses

31. Centralized GIS data maintenance svc. CLIENT DDTI AccuGlobe 2007 GIS Application Internet SQL Portal Server SQL Server Local GIS Data CQC Server

32. Centralized GIS data maintenance svc. • Multiple users can edit the GIS data (spatial and attribute) simultaneously via the Internet • Full history of edits are saved with audit trail • Computed attributes generated on servers • User enters only non-computable data • QC checks populate the error layer within seconds after the changes are committed for quick feedback • Nightly GIS data extract provides fresh data for GIS applications for other agencies

33. Maintenance E9-1-1 Planning Engineer Health Other/Etc Assessor COUNTY TOWNSHIP CITY/VILLAGE STATE Trustees E9-1-1 Zoning Engineer Other/Etc Other/Etc Data integration and dissemination

34. What the 9-1-1 Community is Saying about the LBRS • There is no substitute for geographic information collected in the field. This is especially true for address points in a 9-1-1 dispatch setting. The use of road centerlines exclusively in 9-1-1 simply is not adequate, particularly in rural settings where houses may be hundreds of feet off the public road and/or may share a long lane between many houses. Address ranges on road centerlines just cannot help with this level of detail the way an absolute coordinate on each structure is able to do. • GIS Director Erik Parker, Holmes County

35. Location Based Response System • OGRIP’s goal with LBRS is a statewide GIS • Create spatially accurate street centerlines with field verified site-specific address locations, with emphasis on linear referencing/mileposts • Multipurpose data designed for cross departmental use • Federal, county & local government GIS • State Departments of Transportation • Auditors, Engineers and other elected officials • Police, Fire, EMS • DDTI collects the following for all LBRS projects

36. Location Based Response System • Overpasses • Railroad Crossings & associated control types • School Zone Points • Speed Limit Signs and their value • Stop Signs • Traffic Signals • Turnarounds • Underpasses • Yield Signs • Private miles of centerline • Municipal miles of centerline • Township miles of centerline • County miles of centerline • Miles of centerline • State Routes • State US Highways • State Interstates • State Ramps • State Park Roads • Single Family Houses • Duplexes • Manufactured Homes • Apartments (single & multiple units) • Addressable Secondary Structures • Utility Structures • Commercial Structures • Addresses w/no visible structure • Alley Intersections • Bad Sign Points • Boundary Points • Bridges and Culverts • Flashing Signals & associated control types • Gates • GPS Points with attached X, Y and Z locations • Hydrants • Intersections • Landmark Points with descriptions • Milepost signs and their milepost values • MX Notes to flag multiple houses sharing a driveway 

37. Counties Mapped by DDTI

38. USING IT A BUNCH!How LBRS benefits a Safety Data System Create it once ▪ Use it a bunch ▪ And maintain it

39. Scrubbing and Locating Crashes Statewide TSASS is working with 19 counties and three MPO’s statewide representing almost 50% of all crashes. Safety funding programs are data driven and require three full years of scrubbed and located crash data. TSASS has a statewide crash data and crash report image repository going back to 1995. Our goal is to promote and help local governments to apply for safety funds that they otherwise would not have the resources to do so. LBRS allows TSASS and in turn the locals, to successfully , efficiently and accurately improve hazardous intersections.

40. TSASS utilizes ALL available field verified inventories collected through the LBRS effort. • Road Centerlines • Intersections • Address Points • Mile Posts • Boundaries • Landmarks • Railroad crossings • Bridges and culverts • Signs (including stop, yield, flashing signals, traffic signals) • GPS Points These include (in order of importance to how officers are referencing locations):

41. Building a Comprehensive Road Inventory (Stark County, Ohio as example) • DDTI LBRS Stark County: • 20,591 Intersections or road end-points • 164,250 Addresses • 29,510 roadway segments • DOT Roadway Inventory Stark County • 18,120 Intersections or road end-points • 0 Addresses (no address point data) • 24,420 roadway segments

42. Statewide, Intersection and Address related Crashes are the most referenced attributes.

43. For comparison: Stark County 2006-2008 Crashes By Reference Type 1% 17% Other Address 14% Milepost Intersection 68% Intersections are the most commonly referenced attribute and require a complete road centerline inventory!

44. Crashes located at intersections of “private” roads and the legacy roadway are often left out of the statistics.

46. Example: Disagreement of Locations

47. Now lets look at Address Referenced Crashes in Stark County in Ohio: Stark County 2006-2008 Crashes By Reference Type 1% 17% Other Address 14% Milepost Intersection 68% Addresses are the second most commonly referenced attribute and require point address information for accurate location.

48. Without address point data other methods used to locate the address referenced crashes include using County Engineer, Auditor and/or TIGER Address Data (in Blue) or other vendor datasets. • These address located crashes often are in “space” when comparing it to the legacy roadway and are not included in the Link/Node Statistics.

49. Let’s look at an example… Here are the different data sources. (DDTI centerline in black; ODOT Roadway Inventory in red. Now the crashes: Blue are located against DDTI dataset; Red located by ODOT. And now here are the crashes referenced to addresses only.

50. Address-referenced crashes suffer from additional problems not normally associated with LBRS data like gaps in the address ranges and inconsistent street names. • Address Range Geocoding will NOT provide accurate enough locations. • Consequences will be inaccurate tallies on segments and intersections.