Minnesota Statewide Centerline Stakeholder Workshop, Day 1

1. Minnesota Statewide CenterlineStakeholder Workshop, Day 1 Exploring the Potential for a Collaborative Street Centerline Maintenance Model October 24-25, 2011

2. 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

3. 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

4. Shared Collaborative Data Maintenance Model

5. ESRI Solution Demo8: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

6. ESRI Solution DemoSession 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?

7. Break

8. MnDOT LRS Initiative11: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

9. 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?

10. Lunch12:00 – 1:00

11. Functional Model Structure1: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

12. Roadway Data Use CasesHow 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

13. Functional NeedsWhat geospatialfunctions use roadway data?

14. 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

15. 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.

16. Functional Model StructureSession 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?

17. Break

18. Minnesota Statewide CenterlineStakeholder Workshop, Day 2 Exploring the Potential for a Collaborative Street Centerline Maintenance Model October 24-25, 2011

19. Definition(s) of a Road8: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

20. 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.

21. Roadway System Owners

22. Definition(s) of a roadJurisdiction versus Geography 3 road jurisdictions within the same political boundary: State roads, County roads, and Private roads. Each of jurisdiction has an assigned data steward. Jurisdictions are associated with road authorities, not geographic extents.

23. Definition(s) of a roadSession 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?

24. Break9:30 – 9:45

25. Data Model Considerations9:45-11:30 Dan Ross, Andy Buck • Geometric representation • Dual tracks, one way streets, divided, ROW, pavement edges, lanes, platted • Addressing: Ranges on segments or separately as points • Direction of geometry • Traffic, cardinal directions • Topological model/consistency with other systems • Measurement schema • Identifiers: Streets (how many names, primary?), routes (number and format) Identify data structures required to support geospatial activities of use cases Provide input to upcoming data modeling sessions

26. Routing versus LRS

27. Data Model ConsiderationsSession Questions • What roadway representations does your organization need? • Are other representations needed? • Are multiple representations needed by your organization? • Do you have topological rules for treating road features? • What roadway core attributes does your agency’s work require? • How does this session help define the Who, What, When, Goals, and Outcomes of the Pilot Project?

28. Lunch11:30 – 12:30

29. Data Collection Issues & Roles12:30-2:00 Dan Ross, Andy Buck • Data stewards & custodians • Definitions / business rules for data collection • Data capture methods and formats Create working definitions for required workflow roles. Identify key workflow steps, integration points, and major processing steps.

30. Data Collection Issues & RolesSession Questions • What people/departments are the steward(s) of data in your organization? • How does data stewardship occur in your agency? • What methods (formal and informal) do you employ to resolve data conflicts within and beyond your organization? • Do you have the resources to do the work required? • How does this session help define the Who, What, When, Goals, and Outcomes of the Pilot Project?

31. Break2:00 – 2:15

32. Data Publishing and Distribution2:15 - 3:00 Dan Ross, Andy Buck • Discussion of issues related to cost for access • Differing distribution models depending on user • Differing distribution models depending on need • Disclaimers and liabilities of data use • Publication format: Actual data vs. Web services • Data extraction scenarios Identify data distribution requirements not previously discussed

33. Data Publishing and DistributionSession Questions • What issues do stakeholders share and which are unique in terms of releasing data to the public? • What data restrictions (to access) can/should be in place? • Does the data need to be modified prior to being released to the public domain/public use? • What work steps are required to convert the data into formats required by consumers? • How does this session help define the Who, What, When, Goals, and Outcomes of the Pilot Project?

34. Workshop Wrap-up 3:00 – 4:30 Dan Ross, MnGEO Geoff Maas, MetroGIS Coordinator Andy Buck, Applied Geographics • Summary of topics covered and points of consensus reached • Solicit ESRI response to the workshop sessions. How does this workshop define the pilot Who, What, When, Goals, and Outcomes?