Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed MIRE/safety data stuff. Moving to new page

Table of Contents

Introduction

Welcome to the Roadway Centerline wiki page!  This is an exhaustive 'deep-dive' of the inner workings of the DDOT GIS team's main reason for existence:  the centerline. 

GIS Centerlines

We maintain centerline-based roadway data for all roads and alleys open to traffic within the District of Columbia.  DDOT uses a linear referencing system (or LRS) to maintain both the centerline/road GIS as well as the various attributes and characteristics about that roadway.  There are 3 major components of our LRS-based centerline GIS:

From these 3 components, we derive a multitude of other data and products for many uses.  Some of the more popular ones are:

  • Street Segment Centerlines -  used by the Master Address Repository
  • Roadway Segment Centerlines  - will eventually be used as the common base routing network layer.
  • Intersection Approaches - used by Safety Data team for MIRE (see below)
  • Cross-section Data - complete view of our roadway elements as a cross-section.
  • Network Analysis Layer - (coming soon)

How We Update the Centerline and Other Data

  • Construction updates from Protrack+
  • Notifications from the public/other agencies

How We Check our Centerline and Other Data

  • Checks on Centerline
  • Checks on Cross-sections
  • Checks on Parking Data

History

In the years since it's inception, the simple centerline has changed quite a lot.  Read a bit more about the origins of the DDOT centerline:  from paper-based engineering drawings and ROW cards in the DC Office of the Survey all the way to our modern-day LRS.  We've come a long way and it's interesting to understand where we've been.  Visit the DDOT Centerline Legacy page for more.

Model Inventory of Roadway Elements (MIRE)

If you'd like to check out general info about MIRE, FHWA has a few helpful online resources:

  • MIRE 2.0 Report: Revision to the original report.
    Status
    subtletrue
    colourGreen
    titleNEW!
  • MIRE 1.0 Report: The original report that contains background information as well as a comprehensive overview of all required elements.
  • Data Collection Guidebook: Guide highlighting practical approaches to MIRE data collection, highlighting techniques and technologies as well as providing additional guidance.
  • MIRE FDE Cost Benefit Estimation: Required reading. This document goes into good detail and highlights what some states have already done.

MIRE FDE Data Collection

The MIRE Fundamental Data Elements (FDE) is a subset of  33 safety data items required by FHWA.  Below, the main table of required FDE are listed, with some additional items required by DDOT:

Info
titleNote

The actual list of FDEs is 37 - but if you remove duplicates of AADT, AADT Year, Governmental Ownership and Functional Class, the actual number is 33.  Each of these four items appear twice.

In the summer of 2017, DDOT contractors will begin collecting lane data in support of FHWA's MIRE safety data specification. The data will be collected using DDOT's linear referencing system (LRS):  Roads and Highways Roadway Characteristics Editor.  For a detailed review of the project, check out the blog article describing the data and proposed extraction process

  • Roadway Sections (Lanes) Centerline Project: visit our summary page.
  • Automated Extraction - from LRS to MIRE data elements using Python. <<<Page Needed>
Expand
titleClick Here to View MIRE FDE Details...

Roadway Segment

Intersection

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-70

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-122

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-66

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-124

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-67

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-125

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-76

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-23

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-75

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-130

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-78

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-103

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-68

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-257

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-69

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-104

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-71

Interchange/Ramp

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-73

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-53
 

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-74

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-140

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-91

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-142

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-77

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-45
 

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-105

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-48
 

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-79

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-49

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-103

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-250

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-104

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-251

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-65

Jira
serverOITI
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdbe66cdab-4c32-3f5c-afe8-7a06fa4f1ee4
keyRHDD-58

Additional Elements Captured by DDOT

Sidewalk Type + L/R (DDOT Type)

 

Sidewalk Width (the generalized width in feet of the sidewalk)

 Lane Type (DDOT Type) (through lane, bike lane, right turn only, etc) 

Dividers (includes medians (54), centerline striping type, etc)

 

Street Buffers (protections that do not divide opposing traffic,
e.g. continuous painted, curbed protections)

 Lane Directionality (DDOT Type) (direction of traffic as the centerline geometry ascends) Lane Width (DDOT Type) (width in feet of a given travel lane) 

Green = Items either in HPMS or already extractable via DDOT scripting

Orange = DDOT will capture Summer 2017

Red = Contractor will capture Summer 2017