Land Information Ontario

Similar documents
User Guide for. Bathymetry. LIO Data Classes

Ministry of Transportation and Infrastructure jurisdiction (337 km) Federal Parks Canada jurisdiction (103 km)

Guide: Entering an Application for an Existing Groundwater Licence. in Virtual FrontCounter BC

Subject OWNERSHIP DETERMINATION - BEDS OF NAVIGABLE WATERS. Number Same

CHECKLIST: REQUIRED INFORMATION FOR AUTHORIZED REQUESTER APPLICATION

What is Integrated Land Management?

Lheidli T enneh Final Agreement. Lands

DESIGN CRITERIA MEMORANDUM

Best Practices for the Governance of ArcGIS Online Mitigating Chaos. Presented by: Laura Kingston, Land Information Coordinator, MTO October 18, 2017

LOCAL STREETS AND THE ARNOLD INITIATIVE

Network Connectivity and Mobility

Decision D ATCO Electric Ltd. Crystal Lake 722S Substation Telecommunications Tower Replacement

Harbourside Commercial Park Inc. Crown Corporation Province of Nova Scotia Business Plan

Guidelines for Traffic Counting. May 2013

The strive for a high quality road data base

Facilities Management Data Input, Editing and Management. Adrien Litton

Geometric Layout for Roadway Design with CAiCE Visual Roads

Automated Traffic Enforcement Technology Guidelines. Province of Alberta

Esri Best Practices: QA/QC For Your Geodata. Michelle Johnson & Chandan Banerjee

LINEAR REFERENCING SYSTEM (LRS) PILOT PROJECT REPORT

Terms of Reference. Project: Establishment of Energy Agencies in Ukraine (BMUB, IKI) PN

KANABEC COUNTY HIGHWAY DEPARTMENT Chad T. Gramentz, P.E. County Engineer 903 Forest Avenue East Mora, MN

Downtown Boise Multimodal Center

Ontario s Hydrometric Network and The Canada-Ontario Agreement on Hydrometric Monitoring

A parabolic curve that is applied to make a smooth and safe transition between two grades on a roadway or a highway.

Developing New Hampshire s Transportation GIS Data Model. Kirk Weaver March 30, 2004 GIS-T Symposium Rapid City, South Dakota

Digiroad Description of Data Objects. Release 4/2017 (November 20th 2017)

Memoranda of Understanding (MOU) & Memoranda of Agreement (MOA)

Natural Resources Values Information System (NRVIS) Data Class User Guide for. MNR Sign Site

Questions and Answers for Customers

Contents USER S MANUAL 1

Document Change Control

Investigation of Routing Options for the Nova Scotia Road Network (NSRN)

AED Design Requirements: Superelevation Road Design

City of Toronto Accessibility Design Guidelines 2015

Stock Return Form User Guide for Individuals/Corporations. For Agricultural Dispositions

Invasive Alien Plant Program. Part 2. Modules 2.2, 2.3 & 2.4. Prepared by Range Branch. Ministry of Forests and Range

Washington Statewide Trails Database Project

CONDITIONS OF SERVICE

CASE 1 TWO LANE TO FOUR LANE DIVIDED TRANSITION GEO-610-C NOT TO SCALE GEOMETRIC DESIGN GUIDE FOR MATCH LINE LINE MATCH. 2 (0.6m) shoulder transition

Riparian Areas Regulation Notification System Users Guide

The City of Mississauga may install Closed Circuit Television (CCTV) Traffic Monitoring System cameras within the Municipal Road Allowance.

OF ELECTRICAL AND ELECTRONICS ENGINEERS POWER & ENERGY SOCIETY

RCMP Support / Bylaw Services Department

Records Management and Retention

CITY OF KIRKLAND TRAFFIC IMPACT ANALYSIS GUIDELINES

Ministry of Energy, Mines and Petroleum Resources. Guide to Acquiring Crown Petroleum and Natural Gas Tenures

Interpretations for the SFI Standards and Rules. January 2017

PHASE I ENERGY STORAGE: LESSONS LEARNED

Section Qualifications of Audit teams Qualifications of Auditors Maintenance and Improvement of Competence...

PROJECT REPORT RCMP E DIVISION HEADQUARTERS RELOCATION PROJECT

DOWNTOWN TUNNEL / MIDTOWN TUNNEL / MLK EXTENSION PROJECT PROCUREMENT PROCESS

TMDD Standard v03.03c Errata

Alternative Fuel Vehicles in State Energy Assurance Planning

Investigation. City of Edmonton Office of the City Auditor. ETS Workforce Development. January 14, 2019

ELECTRONIC SUBMISSION FRAMEWORK (ESF)

MINISTRY OF NATURAL RESOURCES

New Jersey Statewide Transportation Data Model. Mark Gulbinsky November 5, 2004 NJDOT

OCCIO/OCCTO MANAGEMENT BOARD SECRETARIAT CORPORATE ARCHITECTURE BRANCH TECHNICAL STANDARDS SECTION. NTv2 (National Transformation Version 2)

ENMAX Generation Portfolio Inc.

National Speed Limit Register

INPUT DATA PROCEDURES

OPTIMIZING HIGHWAY PROFILES FOR INDIVIDUAL COST ITEMS

PUBLIC WORKS INTEGRATED PEST MANAGEMENT (IPM) CERTIFICATION PROGRAM (Ontario)

FY ICMA Benchmarking Results

Source Protection Information Atlas (SPIA) OMAFRA Consultants Information Day Source Protection Programs Branch April 23, 2018

List of EA Publications. And International. Documents

A Case Study about IFEZ(Song-do) Smart-City. Ryan LEE

A Business-driven Approach to Linear Network Management for Roads

Lecturer 2: Spatial Concepts and Data Models

PEFC N 04 Requirements for certification bodies and accreditation bodies

A Litter and Fly Tip Action Plan for Chichester District

Organizational Structure of the Toronto Environment Office

Alberta Electric System Operator Secord 2005S Substation Needs Identification Document

2009 MUTCD CONTENT Introduction Part 1 General Part 2 Signs Part 3 Markings Part 4 - Highway Traffic Signals Part 5 Traffic Control Devices for Low

NON-VDOT ADMINISTERED PROJECTS (NVAP) PORTAL

Johnson City Regional ITS Architecture Update Review Workshop. March 12, 2015

NCTCOG MTP Policy Bundle Application for TXDOT

Building Strategies & Sustainability

Baseline Candidate. Sex and Current Gender Input and Display. Quick Implementation Guide. Edition 1 20 th April 2010

Mines Branch. Private Aggregate Quarry Submitting an Application

Transition Curves for Roads Designers Manual

Overview September 7, 2017

Panel 1 National CSIRT Experience

Directive on security of network and information systems (NIS): State of Play

Adopted by La Mesa City Council July 9, 2013 Resolution

R1 R2 R3 C/I RC/I AP LR SC/I RP SP RESIDENTIAL *Single-Family Dwelling,

Subject YRRTC Accomplishments and Highlights

Metrolinx / Toronto Transit Plan April 28, Jack Collins Vice President, Rapid Transit Implementation

BENTON COUNTY CODE BENTON COUNTY CODE TABLE OF CONTENTS - COMPLETE CHAPTER 3.04 BCC RESTRICTIONS ORD. 386, EFFECTIVE DOGS AND DANGEROUS DOGS

FCM-RAC Proximity Initiative

APPROVED WORK ZONE TRAFFIC CONTROL TRAINING GUIDELINES TRAINING PROVIDERS / COURSES FOR CONTRACTORS / SUBCONTRACTORS

Georeferencing West Virginia DOT s Roadside Assets: An Asset Inventory Case Study. Geoff Dew April 13,

MINING LANDS ADMINISTRATION SYSTEM (MLAS) STAGE 1 CLIENT ENROLMENT USER GUIDE

Access Field Entrance Other Constructed Yes (Type)

THE SOUTHERN GATEWAY MANAGED LANES PROJECT. Public Meetings Summer 2015 June 23, June 25, July 7, July 9

Another Look at the Safety Effects of Horizontal Curvature on Rural Two-Lane Highways

BC OnLine. British Columbia Assessment System User s Guide. Last Updated April 12, 2016

THE SOUTHERN GATEWAY MANAGED LANES PROJECT. Public Meetings Summer 2015 June 23, June 25, July 7, July 9

Stem Beach Solar 1041 Application

Transcription:

Land Information Ontario Logical/Physical Data Dictionary For MNRF Road Segment (MNRRDSEG) and MNRF Road Network (MNRRDNET) Revision Date: February 10, 2016

Model Diagram Page 2 of 11

Data Dictionary Entity Name: MNRF ROAD SEGMENT Table Name: MNRF_ROAD_SEGMENT_FT DC Short Name: MNRRDSEG A road segment is the linear geometry of the road. Road segments can be consolidated into networks using the MNRF Road Network entity. To exist in the MNRF Road Segment layer the road must be, or have a path supporting conventional four-wheel street legal motor vehicles and satisfy one of the following: - Road crosses land owned by the MNRF - Road is the responsibility of the MNRF to maintain - Road is the responsibility of some other agent through an agreement or plan (i.e.: MOU, LUP, FMP), where if the agreement or plan is terminated the road will become the responsibility of the MNRF. When a road segment can no longer be traversed by a conventional four-wheel street legal motor vehicle, the status of the segment must be changed, but roads should never be deleted from this layer. See the STATUS field for more information. # ATTRIBUTE/COLUMN NAME DATATYPE REQ DESCRIPTION OGF Id A unique numeric provincial identifier assigned 1 NUMBER(13) OGF_ID to each object. The road network identifier for road asset management. Made up of three letter codes for the district, and three digits for a sequential ID of the network within the district. Ex: TIM001, TIM002, CHA001, etc. This attribute provides a direct link to network Road Network Identifier attributes for segments belonging to Asset 2 VARCHAR2(6) ROAD_NETWORK_IDENT Management Plan (AMP) networks. To access network attributes for non-amp networks, use the intermediate table MNRF_ROAD_NETWORK_AND_SEGMENT to allow a many to many relationship between segments and networks. 3 Road Authority ROAD_AUTHORITY VARCHAR2(10) The entity that has legal authority to enter into agreements with respect to the use and maintenance of the road segment. Valid Values: MNRF, MTO, Municipal, Federal, Private; should default to MNRF in the absence of information to the contrary. Value definitions: MNRF - means Ministry of Natural Resources and Forestry MTO - means Ministry of Transportation Municipal - means Road Authority is a municipal government Federal - means the authority lies with the Government of Canada (this can include first nations reserves) Private - The authority for the segment lies with a private citizen, company, or corporation Federal MNRF Page 3 of 11

4 Ownership Class OWNERSHIP_CLASS VARCHAR2(10) MTO Municipal Private Legal ownership of the road right-of-way and authority to assign responsibility for a road to another party. Classification: Federal, Crown, Private, Municipal The particular MNRF business need for this attribute is to track which roads are on Crown land even though the responsibility for the road may be assigned to a third party (e.g. SFL, Local Roads Board, etc.). The owner of the right-of-way is a stakeholder in the road regardless of who is the Road Authority and who has Responsibility for the road. In some areas it may be possible to derive this information from a topological overlay with land tenure information. Make sure however that the tenure information is accurate and up-to-date, noting that there may be text in the tenure agreements describing a road allowance that is not shown in the LIO tenure layers. Defaults to Crown, in the absence of information to the contrary. 5 6 Responsibility Class RESPONSIBILITY_CLASS Responsibility Detail RESPONSIBILITY_DETAIL VARCHAR2(30) VARCHAR2(80) Crown Federal Municipal Private A classification of the agents listed in the Road Responsibility Detail attribute. Classification: Ministry of Transportation (MTO), Municipal, Ministry of Natural Resources and Forestry (MNRF), Sustainable Forest License (SFL), Federal, MOU, n-freehold PLA Disposition. Defaults to MNRF, in the absence of information to the contrary. Federal MNRF MOU MTO Municipal n-freehold PLA Disposition SFL Name of the specific group or individual legally responsible for activities associated with a road including condition and maintenance. May refer to the reference number of a shared use agreement involving a number of parties. Responsibility Detail must be filled out when the Responsibility Class is neither MTO nor MNRF. Identify the reference to the legal agreement name & number (e.g. LUP District#-XXXXXXX ; MOU-District-XX-YR) and/or identify the name of the corporation (ex: Responsibility Class = Page 4 of 11

SFL, Responsibility Detail = Tembec). If the agreement is with a private individual, do not enter the name of the individual (or any personal contact information), only the agreement number, as this layer is non-sensitive and freely distributed. 7 National Road Class NATIONAL_ROAD_CLASS VARCHAR2(30) A functional (versus administrative) based classification system. The National Road Network (NRN) Class list is as follows: Local / Strata - A low speed thoroughfare dedicated to provide access to properties with potential public restriction, trailer parks, first nations, strata or private estates. Resource / Recreation - A narrow passage which has as a primary function access for resources extraction and also may have a role in providing an access for the public to back country. Winter - A road that is only useable during the winter months when conditions allow for passage over lakes, rivers and wetlands. te: If Winter is selected then it is implied that all values for Status, Passable, etc. all refer to the time period when the road would be in operation (e.g. Dec to April) te: While the NRN defines this attribute with more choices than what we are allowing here, if the road is not described by one of the values above then it does not belong in this layer. 8 Geometric Standard Class GEOMETRIC_STANDARD_CLAS S VARCHAR2(1) Local / Strata Resource / Recreation Winter The geometric standard road classification. Classes include A, B, C, and D. Guidelines specify minimum-maximum clearing width, speed, roadway width, horizontal curvature, maximum gradient, minimum sight stopping distance, minimum ditch depth, minimum culvert size, maximum aggregate size and granular structure. (PL 10.06.00 ARM-1992) This is the primary classification field for deriving the road value. Defaults to C. te: once this field is filled in we will drop Surface Type and Number of lanes. 9 FMP Road Class FMP_ROAD_CLASS VARCHAR2(1) A B C D Annual Report road class P - Primary B - Branch O - Operational This field must have its values calculated in to Page 5 of 11

10 11 12 Road Name ROAD_NAME Alternate Name ALTERNATE_NAME Status STATUS FMP_ROAD_CLASS where P => Primary, B => Branch, and O => Operational B O P VARCHAR2(150) The primary or official name of the road. VARCHAR2(150) VARCHAR2(15) Road name that has no official status but is used or known by the general public. Access roads on crown land are open to the public generally. However from time to time it may be necessary to restrict access to certain areas or to close a road entirely to all use. (Access Roads Manual 1992) Values include: Open, Closed, Decommissioned, and Restricted Defaults to Open, in the absence information to the contrary. Closed Decommissioned Open Restricted The management intent for the road segment as defined by the current use of the road or by the road use management strategy. 13 14 Road Use ROAD_USE Restriction Type RESTRICTION_TYPE VARCHAR2(20) VARCHAR2(15) Picklist: Forest Management Cottage/Residential Recreation Ministry Operations Aggregate Mining Renewable Energy Resource Management Tourism Other Commercial Aggregate Cottage/Residential Forest Management Mining Ministry Operations Other Commercial Recreation Renewable Energy Resource Management Tourism The type of restriction that applies to the road segment (if applicable). Mandatory when the Status is "Restricted", otherwise Restriction Type should be blank or null. Permissible values: Date, Activity, Destination, Vehicle Type, Other Page 6 of 11

15 16 Use Restriction Detail USE_RESTRICTION_DETAIL Maintenance Level MAINTENANCE_LEVEL VARCHAR2(160) VARCHAR2(15) Activity Date Destination Other Vehicle Type Brief details of the road use restriction (if applicable). Mandatory when the Status is "Restricted", otherwise Restriction Type should be blank or null. The frequency with which maintenance activities are carried out on the road segment. Defaults to t Maintained Meanings for permissible values: Routine - road maintained on a continuous basis to keep expected condition constant Limited - maintenance is limited to things like maintaining water crossings required to keep the road passable t Maintained - no official maintenance is carried out except for action to address environmental or public safety issues 17 18 19 Passable Flag PASSABLE_FLG Control 1 CONTROL1 Control 2 CONTROL2 VARCHAR2(5) VARCHAR2(4) VARCHAR2(4) Limited t Maintained Routine A 4x4 vehicle is able to drive the segment (TRUE or FALSE). Defaults to TRUE FALSE TRUE Road access control or decommissioning type (first) BERM - bern and/or ditch GATE - gated / physical barrier PRIV - private land SIGN - signed SLSH - pile slash WATX - water crossing BERM GATE PRIV SIGN SLSH WATX Road access control or decommissioning type (second) BERM - bern and/or ditch GATE - gated / physical barrier PRIV - private land SIGN - signed SLSH - pile slash WATX - water crossing Page 7 of 11

20 Surface Type SURFACE_TYPE VARCHAR2(10) BERM GATE PRIV SIGN SLSH WATX The surface type of the road. Paved Gravel Unsurfaced Defaults to Unsurfaced. te: this attribute is to be dropped once Geometric Class is filled in. 21 22 Number Of Lanes NUMBER_OF_LANES Year Constructed YEAR_CONSTRUCTED VARCHAR2(3) NUMBER(4) Gravel Paved Unsurfaced The number of lanes the road has. Picklist: 1, 1.5, 2 te: this attribute is to be dropped once Geometric Class is filled in. 1 1.5 2 The year in which the road segment was originally constructed. If construction spans more than one year then the year value should reflect the year that the segment was first opened to vehicular traffic. Defaults to current year. 23 Year Constructed Modifier YEAR_CONSTRUCTED_MODIFIE R VARCHAR2(12) A mandatory modifier to the Road Year Constructed attribute. Meanings of permissible values: Actual - the year is known; Approximate - the year is not known for sure; Before - the actual year is not known but it was sometime before the year entered. Defaults to Actual. 24 25 26 27 Service Year SERVICE_YEAR Date Last Maintained DATE_LAST_MAINTAINED Date Last Inspected DATE_LAST_INSPECTED Year Decommissioned YEAR_DECOMMISSIONED NUMBER(4) DATE DATE NUMBER(4) Actual Approximate Before The year in which the road segment last reentered service. Valid value is a four digit number that is equal to or greater than the Year Constructed The date of the last known maintenance performed on the road segment (if applicable). The last time the road segment was inspected (if applicable). The year in which the road segment was decommissioned (if applicable). There is a constraint forcing the value to be four digits in a logical range (i.e. 1990-2040) Page 8 of 11

28 Year Decommissioned Modifier YEAR_DECOMMISSIONED_MODI FIER VARCHAR2(12) BETWEEN 1990 AND 2040 A mandatory modifier to the Year Decommissioned attribute (if applicable). Meanings of permissible values: Actual - the year is known; Approximate - the year is not known for sure; Before - the actual year is not known but it was sometime before the year entered. Defaults to Actual. 29 30 General Comments GENERAL_COMMENTS FMP Road Identifier FMP_ROAD_IDENT VARCHAR2(2000) VARCHAR2(30) Actual Approximate Before This field should be used to capture all relevant notes for the segment in question. Including reasons for changes in attributes, past attribute values, management considerations, issues that have come up, or issues that the segment has been involved in. Annual Report road identifier (related to Forest Management Planning). 31 FMP Constructed Indicator FMP_CONSTRUCT_IND VARCHAR2(3) Indicates if constructed this year (related to Forest Management Planning). or If then calculate [YEAR_CONSTRUCTED] = (Year of Report) and [YEAR_CONSTRUCTED_MODIFIER] = Exact. te: Whether or not this field is marked be sure to check to see if they are already in the MNRF Road Segment Layer. See guide for updating MNRF ROAD SEGMENT for more details. 32 FMP Decommissioned Indicator FMP_DECOM_IND VARCHAR2(3) Indicates if decommissioned this year. or If then calculate [STATUS] = Decommissioned, [PASSABLE] = False, and [MAINTENANCE_LEVEL] = t Maintained. 33 FMP Access FMP_ACCESS VARCHAR2(8) Indicates road access control status. APPLY - this indicates that an access control is being applied to the road segment. REMOVE - this indicates that an access control is being removed from the segment. 34 FMP Maintenance Indicator FMP_MAINTAIN_IND VARCHAR2(3) APPLY REMOVE Indicates if maintained this year. or Page 9 of 11

35 36 37 38 39 FMP Monitor Indicator FMP_MONITOR_IND Geometry Update Datetime GEOMETRY_UPDATE_DATETIM E Effective Datetime EFFECTIVE_DATETIME System Datetime SYSTEM_DATETIME SHAPE SHAPE Indicates if monitored this year. or VARCHAR2(3) DATE Date/time the geometry was created or last modified in the source database. DATE Date/time the record was created or last modified in the source database. Date/time the record was loaded into or last DATE modified in the LIO database. DEFAULT: SYSDATE SDO_GEOMETRY Geometry attribute. Entity Name: MNRF ROAD NETWORK AND SEGMENT Table Name: MNRF_ROAD_NETWORK_AND_SEGMENT Intersection table between MNRF Road Network and MNRF Road Segment tables. # ATTRIBUTE/COLUMN NAME DATATYPE REQ DESCRIPTION 1 MNR Road Network ID Unique identifier in the MNRF Road Network NUMBER(13) MNRF_ROAD_NETWORK_ID table assigned by the LIO database application. 2 MNR Road Segment ID A unique numeric provincial identifier assigned NUMBER(13) MNRF_ROAD_SEGMENT_ID to each object. 3 Effective Datetime Date/time the record was created or last DATE EFFECTIVE_DATETIME modified in the source database. 4 System Datetime SYSTEM_DATETIME DATE Entity Name: MNRF ROAD NETWORK Table Name: MNRF_ROAD_NETWORK DC Short Name: MNRRDNET Date/time the record was loaded into or last modified in the LIO database. DEFAULT: SYSDATE A road network is a consolidation of one or more road segments and relies on the road segment for its geometry. A road segment may belong to one or more road network consolidations. # ATTRIBUTE/COLUMN NAME DATATYPE REQ DESCRIPTION Ogf Id A unique numeric provincial identifier assigned 1 NUMBER(13) OGF_ID to each object. 2 3 Network Business Identifier NETWORK_BUSINESS_IDENT Network Group NETWORK_GROUP VARCHAR2(80) VARCHAR2(80) A text string containing the business identifier for the road network assigned by the author of the network. Road networks can be used for a number of purposes, including naming routes (e.g. " Highway 17", "Trout Lake Road"), and organizing roads for forest management purposes or road use management strategies. This is the identifier that might be used to annotate a map. This is identifier could be used as a link to a Road Network Management Strategy database (for SFL and MNR road networks) A user defined text string allowing the road network to be assigned to a sub-type or group. This attribute can be used to group Business Page 10 of 11

4 5 6 7 8 9 10 11 12 Network Description NETWORK_DESCR Network Comment NETWORK_COMMENT Network Maintenance NETWORK_MAINTENANCE Network Monitoring NETWORK_MONITORING Network Access NETWORK_ACCESS Network Future NETWORK_FUTURE Network Transfer Year NETWORK_TRANSFER_YEAR Effective Datetime EFFECTIVE_DATETIME System Datetime SYSTEM_DATETIME Identifiers so that a Group/Business Identifier set would uniquely identify a particular road network A group could be used for selection when mapping and map labelling A group might identify the author of the road network. VARCHAR2(500) Description of the road network. May include why the network was created. VARCHAR2(100) Brief comments about the road network. Description of the maintenance plan for the road VARCHAR2(250) network. Used for audit and reporting purposes related to road use strategies Description of the monitoring program for the VARCHAR2(250) road network. Used for audit and reporting purposes related to road use strategies Description of the access controls planned or in VARCHAR2(250) place on the road network. Used for audit and reporting purposes related to road use strategies. Intent for the future use of the road once it is VARCHAR2(80) transferred to Ministry responsibility. Used for audit and reporting purposes related to road use strategies. Year that the road segments of the network were or are expected to be transferred to MNR VARCHAR2(15) responsibility. Used for audit and reporting purposes related to road use strategies DATE Date/time the record was created or last modified in the source database. Date/time the record was loaded into or last DATE modified in the LIO database. DEFAULT: SYSDATE Page 11 of 11