Dawn’s history shows some of the background of the LHIs Old Mainframe LHI built from this history plus CLASS No comprehensive review, edits, etc ISTEA management systems further changed nature of LHI and its use Turbulent history of current automation

Mainframe updates in response to ISTEA Move to Highway Data Management System Need zero milepoints; no duplicates Mainframe “forgiving”, HDMS is not Move to MS Access Move to Oracle-based App-Express Move to RIS Tied to GIS

RESULT: A system that has been changed over many times in the last few years, but none of these involved a “real world” review or update of the data until it got to the GIS route-building stage

Print and distribute the listings Regions distribute to counties and munis Handwritten edits returned, reviewed by Regions, reviewed/edited by Main Office and entered into RIS Selected data reviews occur through-out the year by the Main Office Feedback to counties/munis via next year’s distribution

AUG/SEPT – Listings distributed JAN – Deadline to make current CHIPS MARCH – CHIPS deadline Reflects prior year mileage

Deleting or adding roads without adequate documentation Jurisdiction transfers without documentation from both sides Length changes of 0.01 or 0.02 miles Illegible changes

We review all requests and update when appropriate, but YOU CAN’T ALWAYS GET WHAT YOU WANT. You should have MORE THAN A FEELING before editing roads that have counted towards CHIPS funding Documents submitted for a mileage change need to COME TOGETHER and be consistent. Messy returns can be tricky to process; you can TURN THE PAGE for more space. When a resolution has no voting record or signature, it seems to be saying I WANT YOU TO WANT ME.

Sometimes requested edits do not change the data that is already there; LET IT BE. You may say that MY GENERATION has been at this for a long time, but data is not made 30 times more accurate by 30 years of experience alone. Adding Paper Streets or anything else not yet open to traffic would be like getting MONEY FOR NOTHING. Don’t depend on the GLORY DAYS of past inventories; always use the most recent listings. Before sending maps in the Main Office, make sure not to PAINT IT BLACK

Return rate > 93% for the third year in a row! Prior years ran 80 – 90 %

You sent listings in more regularly and, as a result: Tina kept up with most of the workload on her own Gina helped with the more complex issues Completed the entire LHI update with just two people and never had to resort to reassignment of staff as in the past

Added blank for contact address to LHI certificate Access routine for mailing addresses – Share tools among Regions On-line LHI data entry – An idea still on the books

Unilateral changes by the MO to: Milepoints, segment lengths Road names From/to descriptions (crossroads) Additions/deletions Edits from Counties/Municipalities

Repeated “refrains”: Nothing has changed in our system so there should be no changes in the Local Highway Inventory. These frequent changes cause a need for us to review the entire listing every year!

We try, but volume is too great – Number of changes – 1600 counties & municipalities Annual LHI update is the communication & coordination tool

Never, but it will slow down when: When RIS and TRADAS have been completed and are in a steady state When all data has been fully converted and is in a steady state When the 2010 Census review and FC mapping updates are complete

The errors have been there for many years but now we have tools that help us find them – GIS mapping of Federal Aid roads – Routine data editing and review – Availability of better review tools like Google Earth, orthoimages, Bird’s eye view