Translation of linear reference crash data to on street cross street nomenclature
Download
1 / 15

Translation of Linear-Reference Crash Data to On-Street/Cross-Street Nomenclature - PowerPoint PPT Presentation


  • 138 Views
  • Uploaded on

Translation of Linear-Reference Crash Data to On-Street/Cross-Street Nomenclature. Crash Data Universe. 7,707 DHSMV Not in Local DBASE. 51,180 DHSMV in Local DBASE. 58,887 DHSMV Records 1999 – 2001. 2,019 DOT Not in Local DBASE but in DHSMV. 21,812 DOT RECORDS 99 & 00 ONLY.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Translation of Linear-Reference Crash Data to On-Street/Cross-Street Nomenclature' - dennis-navarro


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Translation of linear reference crash data to on street cross street nomenclature
Translation of Linear-Reference Crash Data to On-Street/Cross-Street Nomenclature


Crash Data Universe On-Street/Cross-Street Nomenclature

7,707 DHSMV Not in Local DBASE

51,180 DHSMV in Local DBASE

58,887

DHSMV Records

1999 – 2001

2,019 DOT Not in Local DBASE but in DHSMV

21,812

DOT RECORDS

99 & 00 ONLY

103,298 Hillsborough County and COT Crash Records

1999 - 2001

395 DOT Not in Either DBASE

4,403 DOT Not in DHSMV

19,398 DOT in Local Data


What is linear referencing
What is Linear-Referencing On-Street/Cross-Street Nomenclature

  • Roadway Section IDs

    • Section ID Comprised of three non-unique sets of data

      • County ID aa

      • Section # bbb

      • Subsection # ccc

        Forms Unique Roadway ID aabbbccc

    • Sections tend to follow State Road Numbers, but the relationship is not absolute

  • Mileposts

    • Three-digit precision ie: 10.687 Miles

    • Used with Roadway Characteristics Inventory (RCI) to record the location of:

      • Point Features/Events (Section – Milepost)

      • Linear Features (Section – Beginning Milepost – Ending Milepost)


What is linear referencing1
What is Linear-Referencing On-Street/Cross-Street Nomenclature


On street cross street crash data
On Street / Cross Street Crash Data On-Street/Cross-Street Nomenclature

  • Uses Intersection, Intersection Influence, and Offset Information

    • N. Florida Ave and Polk Street

    • At the Intersection

    • (or) Influenced by Intersection – 50 ft South

    • (of) Not at the Intersection – 200 ft North

  • Geo-location Methodology

    • Assign Crash Event to Appropriate Intersection (#@&*## !!!)

    • Filter Mid-block Crashes by Query of Intersection Influence Attribute

    • Either Remove Mid-Block Crashes or Use GIS Script to “back crashes off of the intersection”

Expletive Deleted


Pros and cons
Pros and Cons On-Street/Cross-Street Nomenclature


Pros and cons1
Pros and Cons On-Street/Cross-Street Nomenclature

Two Features

Drawn to Represent

Single Event



Locating crashes in gis using linear reference mileposts1
Locating Crashes in GIS using Linear Reference Mileposts On-Street/Cross-Street Nomenclature

  • A Route is a GIS Feature that has:

    • Common ID Attribute (Roadway ID aa.bbb.ccc)

    • XY coordinates

    • Geographic Length Attribute

    • M (measure) Attribute

  • A Route Event Theme is:

    • A table of Events such as Crashes, Point Attributes, Linear Attributes

    • Each Event Has

      • Roadway ID Attribute

      • Milepost Attribute (or Beginning and Ending MP info)


Associating route events with underlying point features
Associating Route Events with Underlying Point Features On-Street/Cross-Street Nomenclature

  • ArcGIS 8.x ArcTool Box “Nearest Node” Tool

    • Associate a Point Feature from one Coverage with the nearest Node in another coverage

  • Error Trapping

    • Check if all State Road Intersections are assigned Local Centerline Intersection Ids

    • Check if all Local Intersections within a buffer of State Routes are assigned a Section and Milepost #

    • Manually Review all Interchanges and Areas of Complex Geometry


Pros and cons2
Pros and Cons On-Street/Cross-Street Nomenclature

Difficult Many to One

Relationship


Pros and cons3
Pros and Cons On-Street/Cross-Street Nomenclature

Propagated

Spatial Error


Pros and cons4
Pros and Cons On-Street/Cross-Street Nomenclature

Local Centerline

Removes “Doglegs”


Associating crash data with intersections
Associating Crash Data with Intersections On-Street/Cross-Street Nomenclature

  • “Jump” Crash Event to Nearest DOT Intersection Feature

  • Store the Offset Distance

  • Transfer DOT Crash to Associated Local Centerline Intersection

  • Use Crash Offset Script to relocate crash to correct position using local centerline Geometry


Contact info
Contact Info: On-Street/Cross-Street Nomenclature

Demian Miller

Tindale Oliver & Assoc.

Tampa, FL

813.224.8862

[email protected]


ad