E-books & White Papers

1 Overview Both government and private agencies recognize the need for accurate and com- plete road network data. Many of these agencies regularly use this type of data to manage transportation networks, analyze traffic volume, monitor real-time traf- fic flow or plan emergency responses. Sophisticated GIS applications often span multiple jurisdictions and require numerous data types and sources. As a result, in 1999, the Canadian Council on Geomatics mandated Natural Resources Canada and the Ontario Ministry of Natural Resources to standardize Canada's road cen- terline framework. is became Natural Resources Canada's (2010) National Road Network Guide to Best Practices for Data Acquisition and the standard to which the National Road Network (NRN) adheres. At Esri Canada, we have prepared this document as a revised version of the Natural Resource's NRN document. We intend for it to be used by mapping editors and GIS technicians with a focus on representing road networks within the framework of NG9-1-1, as established by the National Emergency Number Association (NENA). In this document, we follow the data needs and standards set out by NENA and the Community Map of Canada (2019), while drawing upon NG9-1-1 readiness assess- ments from ongoing consultation with Canadian municipalities and from roads and address experts. Road network data has evolved beyond local needs; instead, this type of data must meet the needs of multi-jurisdictional agencies, and it must also conform to com- mon data standards. is need has never been more obvious than with the develop- ment of the NG9-1-1 system. NENA, with input from Canadian subcommittees, has created GIS standards for supplying road network data to NG9-1-1 data aggregators. 2 Data Standards e following standards come from the document, National Road Network Guide to Best Practices for Data Acquisition. To maintain NG9-1-1 data standards, all compulsory data quality checks and attribution are described in Appendix A of this document. Beyond NG9-1-1 standards, mapping editors should also extend these standards to the generalized needs of community road networks. For all road features, mapping editors must maintain homogeneity in their data acquisition, creation and maintenance. ey should use the following guidelines: Requirements Road networks must be represented with appropriate feature attributes. Community Road Network Guide to Best Practices v4.0 1

• Cover
• 1 Overview
• 2 Data Standards
• 3 Road Features
• 3.1 Road Classification
• 3.1.1 Specialized Roads
• 3.1.2 Roundabouts
• 3.1.3 New Roads
• 3.2 Road and Centreline Representation
• 3.2.1 Grade Separated Road Crossings
• 3.2.2 Lanes Divided by Medians
• 3.2.3 Multi-Lane Intersections
• 3.2.4 Access and Exit Ramps
• 3.2.5 Cul-de-Sacs
• 3.2.6 Winter Roads and Ice Bridges
• 3.2.7 Minimum Size of a Road at Junctions
• 3.2.8 Roads Crossing Administrative Boundaries
• 3.3 Road Attributes
• 3.3.1 Address Range Assignment
• 3.3.2 Functional Road Classes
• 3.3.3 Number of Lanes
• 3.3.4 Surface Material
• 3.3.5 Route Number
• 3.3.6 Route Name
• 3.3.7 Exit Number
• 3.3.8 Road Level
• 3.3.9 Road Structure
• 4 Blocked Passage Features
• 5 Toll Point Features
• 6 Ferry Segment Features
• 7 Data Quality Checks for NG9-1-1
• 8 References
• Appendix A: Attribution
• A.1 Data Model Attributes
• A.2 Additional Attributes
• Appendix B: Feature Attribute Values (Domains)
• Appendix C: Attribute Data Specifications
• Figure 1 Road Segment Intersections
• Figure 2 Road Segment at End of Road (Dead End)
• Figure 3 Road Segment Crossing a Bridge
• Figure 4 Road Segments at Municipal Boundaries
• Figure 5 Road Segment Crossing a Railway
• Figure 6 Simple Roundabout at an intersection
• Figure 7 Named Roundabout
• Figure 8 Image of Complex Roundabout
• Figure 9 Two-way Road with Demarcated Traffic Lane
• Figure 10 Road without a Lane Marker
• Figure 11 Road with Parking Spaces along Sidewalk
• Figure 12 Road with Temporary Parking Lanes
• Figure 13 Road divided by a Median
• Figure 14 Centreline Separated by a Median
• Figure 15 Intersection with Right and Left Turning Lanes
• Figure 16 Freeway Interchange with Above Grade Crossings
• Figure 17 Access Ramp
• Figure 18 Street Name for Exit Ramps
• Figure 19 Cul-de-Sac without a Central Island
• Figure 20 Cul-de-Sac with a Central Island
• Figure 21 Minimum Size of a Road Element
• Figure 22 Intersection with an Offset Less than the Minimum Size
• Figure 23 Intersection with an Offset greater than the Minimum Size
• Figure 24 Address Range Assignment
• Figure 25 Address Range Assignment Split over a Median
• Figure 26 Cul-de-Sac with Even and Odd Address Range Assignment
• Figure 27 Cul-de-Sac with Address Range Following Main Road
• Figure 28 Relationship between Road Classes
• Figure 29 Bridge Road Structure
• Figure 30 Dam Road Structure
• Figure 31 Permanently Blocked Passage
• Figure 32 Blocked Passage with Removable Barrier
• Figure 33 Toll Point and Infrastructure
• Figure 34 Ferry Route between Two Boarding Points
• Figure 35 Multiple Ferry Routes from same Boarding Point
• Table 1 Road Segment Attributes
• Table 2 Additional NG9-1-1 Attributes
• Table 3 Ferry Connection Attributes
• Table 4 Toll Point Attributes
• Table 5 Blocked Passage Attributes
• Table 6 Street Type Prefixes and Suffixes
• Table 7 Directional Prefixes and Suffixes
• Table 8 Road Classifications
• Table 9 Closing Period
• Table 10 Traffic Direction
• Table 11 Digitizing Flag Direction (Left and Right)
• Table 12 Grade Level
• Table 13 Structure Type
• Table 14 Surface Material
• Table 15 Road Status
• Table 16 Toll Point Type
• Table 17 Blocked Passage Type
• Table 18 Country Left or Right
• Table 19 Province
• Table 20 Asset Responsibility
• Table 21 Acquisition Technique
• Table 22 Language Indigenous
• Table 23 Language