Exploring the Potential for a Collaborative Street Centerline Maintenance Model Minnesota Statewide Centerline Stakeholder Workshop, Day 1 1 October 24-25, 2011
Workshop Introduction 8:00 – 8:30 Rick Gelbmann, GIS Manager, MetCouncil Geoff Maas, MetroGIS Coordinator Andy Buck, Applied Geographics Dan Ross, MnGEO • Workshop Introduction • Workshop Logistics 2
Workshop Goals • Understand and document stakeholder road centerline needs • Assess feasibility MnDOT as statewide road centerline curator • Come up to speed with MnDOT’s LRS initiative – ESRI Web API – Integration with existing and planned application and workflow architectures of authoritative sources and data consumers • Determine gaps between CSC model MnDOT LRS initiative • Develop a working definitions key terms as “road” • Define pilot project to explore statewide centerline initiative – Document scenarios, technology, policies, interactions, data flows, issues, and logistical realities 3
Shared Collaborative Data Maintenance Model Road Authority Regional Data Centerline Consumers Jurisdiction Road Authority Jurisdiction Authoritative Local Copy Extensions Regional Road Key Full Regional File Road Authority Geospatial Jurisdiction Mapping Web Data Curator Mapping Services Regional Computer Road Authority Applications Aided Dispatch Authoritative Road Centerlines Jurisdiction Maintenance Web Data Steward Data Update Planning Services Authoritative Routing Road Route Road Data Numbers Names Geometry Authoritative Source Authoritative Source Derived Copy (w/ local updates & Authoritative Source Extensions) 4
ESRI Solution Demo 8:30-11:15 Tom Brenneman, ESRI • Overview of the ESRI transportation data model • Demonstration of ESRI street network editing application • Function, operation, and integration w/ other tools • Product update: status, timeline, and development plan Learn the tools to build statewide centerline file Learn how centerline dataset will be used Identify requirements that may not be met by the ESRI solution 5
ESRI Solution Demo Session Questions • How is networkable node and segment geometry supported? • Can the ESRI solution integrate with existing authoritative source business processes and systems? • Can this model be extended by authoritative sources and consumers to manage attributes not in the model? • How do authoritative sources, via the CSC, provide input to and review of the Web API development? • OTHER STAKEHOLDER QUESTIONS • How does this session help define the Who, What, When, Goals, and Outcomes of the Pilot Project ? 6
Break 7
MnDOT LRS Initiative 11:15 – 12:00 Cassandra Isackson, MnDOT Office of Transportation Data & Analysis • Overview of MnDOT the LRS/LRM initiative • Highway Performance Monitoring System (HPMS) current reporting requirements • FY13 HPMS requirement for reporting ALL public roads using LRS (June 2014) • MnDOT’s role as authoritative source and custodian for a statewide centerline repository • Role of non-MnDOT authoritative sources (local, county, tribal, non-government) • Role of the Centerline Steering Committee Share info on MnDOT statewide centerline initiative Discuss potential reduction of data management redundancy and use of this process for other types of shared data management 8
MnDOT LRS Initiative Session Questions • How does MnDOT’s role satisfy the needs of the shared maintenance model and stakeholders? • What is the forum for resolving conflicts between authoritative sources and Mn/DOT? • OTHER STAKEHOLDER QUESTIONS • How does this session help define the Who, What, When, Goals, and Outcomes of the Pilot Project ? 9
Lunch 12:00 – 1:00 10
Functional Model Structure 1:00- 4:30 Andrew Buck, Applied Geographics • Use cases to be supported by centerline data model • Functional needs to be supported by centerline model • Core identification and implications • Reporting and reconciliation Determine baseline stakeholder functional needs for a statewide centerline dataset Equate functional needs to data structure needs 11
Roadway Data Use Cases How is roadway data used in your business ? • Desktop map creation • On-line map viewers • Base map data • Roadway length measurements / analysis • Buffering • Jurisdiction / zone identification/ assignment • Planning and permitting • HPMS reporting • Point and line event creation • Non-engineering construction and maintenance activities • Geo-location: Address, Intersection offset, Mile marker offset • Emergency & non-emergency routing to one or more destinations 12
Functional Needs What geospatial functions use roadway data? Use Case Name Activities Structure Desktop map creation Base Map Creation & Node and centerline segment geometry On-line map viewers Minimal identification attributes Simple Cartography Base map data Networked segment geometry Roadway length measurements / analysis Agreement Points Buffering Spatial Analysis Edge matching Jurisdiction / zone identification/ assignment Jurisdictions & planning attributes Planning and permitting Measured segment length HPMS reporting Statewide routes feature class for LRS Point and line event creation Linear Referencing support Non-engineering construction and Associated point and event tables maintenance activities Geolocation via Point feature class (preferred) Addressing & o Address Node and centerline segment geometry o Intersection offset Geolocation with address ranges (alternative) o Mile marker offset Emergency & non-emergency routing to one or Routable network layer with sufficient Routing and Response more destinations route selection attributes 13
Core Attributes Core identification and implications • LRS State Route Identifiers (for non-state roads) • Source Segment ID • State Segment ID Reporting and reconciliation • Identifying needs for inter-agency reporting • Mileage coding needs • Reconciliation of competing derivative dataset 14
Core Attributes • Model does not contain all of the data elements required for direct support of all business functions. • The model must integrate with database extensions and systems developed by the stakeholder community. 15
Functional Model Structure Session Questions • Does your organization have other use cases or functional needs? • What minimum attributes are needed for a Proof of Concept study? • What “core” attributes reside centrally? Can it be extended locally? • What are the primary reports your agency is required to produce using street/roads information? • How do you use derivative datasets and why are they important? • What road information does your organization want to acquire from/provide to other agencies? • How does this session help define the Who, What, When, Goals, and Outcomes of the Pilot Project ? 16
Break 17
Exploring the Potential for a Collaborative Street Centerline Maintenance Model Minnesota Statewide Centerline Stakeholder Workshop, Day 2 18 October 24-25, 2011
Definition(s) of a Road 8:00- 9:30 Dan Ross, MnGEO Andy Buck, Applied Geographics • Definitions of road - state, local, non-government, tribal, federal • Definitions of public versus private • Definitions of roadway status - active, proposed/platted, retired, temporary closure • Road authority and road ownership impact on use cases Consensus on a statewide centerline dataset working definition of a road Identify some of the gaps and overlaps caused by jurisdictional differences 19
Legal definition of Road Authority https://www.revisor.mn.gov/statutes/?id=160.02) "Road authority" means the commissioner, as to trunk highways; the county board, as to county state-aid highways and county highways; the town board, as to town roads; and the governing bodies of cities when the governing bodies or city streets are specifically mentioned. 20
Roadway System Owners 21
Definition(s) of a road Jurisdiction versus Geography Jurisdictions are associated A. with road authorities, not B. geographic extents. C. Jurisdiction A: County Roads Jurisdiction B: Private roads (Mall, Hospital) Jurisdiction C: State Roads & Trunk Highways 3 road jurisdictions within the same political boundary: State roads, County roads, and Private roads. Each of jurisdiction has an assigned data steward . 22
Definition(s) of a road Session Questions • Do gaps or overlaps in legal or de facto definitions hinder use cases? • How are authoritative source and road authority interrelated? • How does this interrelationship impact roadway data? • What agencies are responsible for road management in your jurisdiction? • How does your organization manage roadway information in your geography, but not within your jurisdiction (tribal, federal lands, non- government)? • Is there a consensus point to take away from this workshop session? • How does this session help define the Who, What, When, Goals, and Outcomes of the Pilot Project ? 23
Break 9:30 – 9:45 24
Recommend
More recommend
