1 / 24

Olmsted County’s Roadway Network Data Base

Olmsted County’s Roadway Network Data Base. Jan Chezick Mike Sloan. Development Team. GeoAnalytics – Louis Schoolkate (no longer with firm), Tom Ries, Ryan Reich Mn/DOT staff – Dan Ross, Denny Brott, Mike Barnes, Matt Koukol, Thomas Martin, Peter Morey

dinh
Download Presentation

Olmsted County’s Roadway Network Data Base

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Olmsted County’sRoadway Network Data Base Jan Chezick Mike Sloan

  2. Development Team • GeoAnalytics – Louis Schoolkate (no longer with firm), Tom Ries, Ryan Reich • Mn/DOT staff – Dan Ross, Denny Brott, Mike Barnes, Matt Koukol, Thomas Martin, Peter Morey • Olmsted County staff – Charlie Reiter, Phil Wheeler, Jan Chezick, Bruce Whetstone, Dave Wittman, Ron Hensley, Randy Growden

  3. Roadway Network Data Base • Microsoft SQL Server Database • ESRI’s ArcGIS and SDE Technology • Project kickoff – March 2000 • Design/Prototype – Fall 2002 • Project initiative began Summer 2004 • Data development began Spring 2005 • Roll-out January 2007

  4. Project Plan • Conceptual Design • Physical Design • Pilot project and testing • Framework development • Populating data base

  5. Project Goals • Maintain and develop the database simultaneously • Framework for developing local databases & applications • Build a product that will be compatible with Mn/DOT data and establish a protocol to share new linework with Mn/DOT to facilitate updating of state base map

  6. Project Goals • Identify our own Unique ID for Anchor Points and Anchor Sections • RNDB represents “as-built roadways” - Base map represents “platted” • Create a process for retiring Anchor Points and Anchor Sections for historical reference

  7. History vs Today

  8. Example of RNDB Editing

  9. Base Name ID’s

  10. Single Centerline vs Roadway Centerline

  11. “As Built” vs. “Platted”

  12. Addresses Range vs. Address Location

  13. Alias Road Names

  14. On/Off Ramps

  15. Roadway Network DatabaseKey Data Components • Centerline Cartography and foundational attributes  • Routes (I-90, US-63)  (Mn/DOT TIS Code) • Impedance (travel speed / time) (in development) • Networks (turning, one-ways) (future)

  16. MNDOT TIS Route Ids’

  17. RNBD – Packaged Data

  18. Current Applications • Basis for E911 Addressing • Compliments Address Point Location database (Includes RAS-ID from RNDB) • Emergency Management • Automated vehicle location base map to locate addresses • CityWatch - alert notification system to deliver time-sensitive information (ex: floods, spills, etc.) • New World dispatch software – address entry with point location of call for services

  19. Current Applications • Rochester Fire Department • response time polygons • station location planning • ISD 535 student locations • Olmsted County Public Works • sign inventory base reference layer

  20. Current Applications • Rochester Public Works • Bus routing geometry coincident with RNDB – allows for more accurate digitizing of new and existing routes, route changes and highly accurate distance measurements. • Jurisdictional and Truck Route Maps dependent on the accurate attributed RNDB • Traffic volume and turn count metering – data entry validation (Intersection attributes linked to RAP_ID) • Primary departmental base map includes the RNDB • Basis for field Road Map Book utilized by field staff

  21. Future Applications • Homeland Security • event planning, evacuation route testing, etc. • ISD 535 • routing applications • Emergency Dispatch Center • routing applications • City of Rochester & Olmsted County • building permit geocoding • Mayo Medical Transport • “quilt” into regional network for use with CAD Dispatching software. • Create map books for ambulances

  22. Future Applications • Rochester Public Works • Street inventory - signs, sidewalks, intersection controls, parking • Routing applications – analysis of bus routes for efficiency, coverage, etc. • Develop a road closures application – data entry of road closure event and output map for public service announcements • Migrate current centerline Road Restriction and Spring Load Restriction Truck Route maps to geometry of the RNDB • Rochester Public Utilities • routing applications (trucks, meter reading, etc.)

  23. Emergency Dispatch ApplicationDemonstration • Avel-Tech AVL System Mobile Computer Terminal Module (MCT) and Computer Aided Dispatch Module • Displays Law Enforcement marked squads and Fire units via icons on map in vehicles, including the location and unit number • Displays Incident location and incident number, along with red line connecting the unit to the incident Slide provided by Mike Sloan – System Support Coordinator - Olmsted County/LEC

  24. Public Safety Agency Information Rochester Police Department • 125 Licensed Officers Olmsted County Sheriff Office • 55 Licensed Officers Rochester Fire Department • 105 Sworn Firefighters Combined Police, Sheriff and Fire Dispatch Center • 120,000+ calls for service per year Slide provided by Mike Sloan – System Support Coordinator - Olmsted County/LEC

More Related