Ontario Railway Network (ORWN) User Guide Data Classes V.2 Land Information Ontario Guide

ORWN TRACK ORWN STRUCTURE LINE ORWN STRUCTURE POINT ORWN CROSSING ORWN JUNCTION ORWN MARKER POST ORWN STATION

Issued: 2013-Aug-1

Disclaimer This technical documentation has been prepared by Her Majesty the Queen in right of Ontario as represented by the Ministry of Natural Resources (the “Ministry”). No warranties or representations, express or implied, statutory or otherwise shall apply or are being made by the Ministry with respect to the documentation, its accuracy or its completeness. In no event will the Ministry be liable or responsible for any lost profits, loss of revenue or earnings, claims by third parties or for any economic, indirect, special, incidental, consequential or exemplary damage resulting from any errors, inaccuracies or omissions in this documentation; and in no event will the Ministry’s liability for any such errors, inaccuracies or omissions on any particular claim, proceeding or action, exceed the actual consideration paid by the claimant involved to the Ministry for the materials to which this instructional documentation relates. Save and except for the liability expressly provided for above, the Ministry shall have no obligation, duty or liability whatsoever in contract, tort or otherwise, including any liability or negligence. The limitations, exclusions and disclaimers expressed above shall apply irrespective of the nature of any cause of action, demand or action, including but not limited to breach of contract, negligence, strict liability, tort or any other legal theory, and shall survive any fundamental breach or breaches. Additional Information For more information about this document, please contact Land Information Ontario at (705) 755-1878 or email [email protected] This document was prepared by: James Gratton, Data Analyst, Land and Resources Cluster, Business Solutions Services, Applications Delivery, Enterprise Application Integration Section. With additional thanks to: Carla Jordan-Cooke, Bill Millar, Dennis Gertridge, Richard Abraham from the Ontario Ministry of Natural Resources, Geographic Information Branch, Mapping and Geomatic Services Section, Base Data Infrastructure Unit (BDI). Marcel Sabourin - Senior Project Officer and Guy Bergeron of Natural Resources Canada, Centre for Topographic Information, GEOBASE National Railway Network (NRWN) project whose standards from which the Ontario Railway Network (ORWN) have been adopted.

Table of Contents DISCLAIMER ...... 2 ADDITIONAL INFORMATION ...... 2 INTRODUCTION ...... 4 PHYSICAL MODEL (IMPLEMENTED) ...... 7 NOTE TO ORWN DATA USERS ...... 8 ABOUT SUBDIVISIONS ...... 8 TRACK SEGMENTATION RULES ...... 10 TRACK FEATURE REFERENCES BY OTHER ORWN LAYERS ...... 10 ORWN COMMON ATTRIBUTES ...... 11 ORWN TRACK (ORWNTRK) ...... 15 ORWN STRUCTURE LINE (ORWNSTLN) ...... 31 GROUPING ORWN STRUCTURE FEATURES ...... 39 ORWN STRUCTURE POINT (ORWNSTPT) ...... 40 ORWN CROSSING (ORWNCROS) ...... 42 GROUPING ORWN CROSSING FEATURES ...... 43 ORWN JUNCTION (ORWNJUNC) ...... 52 ORWN STATION (ORWNSTN) ...... 55 ORWN MARKER POST (ORWNMKPO) ...... 61 APPENDIX 1: ORWN MAINTENANCE AND UPDATES ...... 64

Introduction In 2009, the Ontario Ministry of Natural Resources (OMNR), along with other Canadian Provincial counterparts were invited to participate in a Natural Resources Canada (NRCAN) initiative to define the National Railway Network (NRWN) to be stored and maintained in GEOBASE. The project’s goal: to define a national standard for railway network spatial and attribute information. The NRWN project involved extensive consultation with information owners of railway geospatial datasets from both Private and Public sectors. At the same time, the OMNR’s Base Data Infrastructure (BDI) program re-examined the business needs for their own NRVIS/LIO railway-themed information. As crucial internal business requirements were reflected in the proposed NRWN data standards, BDI launched a project to adapt these into LIO Warehouse Database versions of the NRWN geospatial layers. The end-result of this project is seven (7) new Ontario Railway Network data classes:  ORWN Track (line segment)  ORWN Structure Line (line segment)  ORWN Structure Point (point feature)  ORWN Station (point feature)  ORWN Junction (derived point feature)  ORWN Crossing (point feature)  ORWN Marker Post (point feature)

Diagram demonstrating inter-relationship of NRWN/ORWN layer features - Courtesy J. Gratton

This document is intended as a guide to the scope and context of the information collected for the ORWN information class. Additional information about GEOBASE datasets can be found on the Federal Government Website. Note: The data examples in the guide are provided for context only, and may not reflect the actual information collected for the features. Any errors belong to the author. General Overview of the National Railway Network (NRWN)

Notes: A unique National Identifier (NID) (1) is assigned to every Track, Track Segment, Subdivision, Crossing, Marker Post, Structure (Line + Point), Station and Junction feature. Common metadata about the feature (2) is captured for all NRWN layers (shaded gray in diagram above.) TRACK (3) is the basic starting point of the NRWN, and each TRACK feature has up to two Subdivision references (4). A TRACK is made up of 1 or more TRACK Segments (5) that share the same uniform

5 characteristics. Each Track has 1 Owner, 1 (main) Operator (6), and up to 4 Users (7). NRWN Layers Crossing, Marker Post, Structure (Line + Point) and Station reference a Track (and Subdivisions) that the feature is associated with (8). The association to these attribute values is achieved via the Track NID. Each feature also has a documented distance within a referenced Track Subdivision that it is located within with (9). A distance can be documented for both referenced Subdivisions. Railway Structures are represented as either a linear (line) (10) or point feature (11). Crossing (12) and Structure (13) features from the same layer can form an amalgamated (grouped) feature that is assigned a unique National Identifier (NID). A Station can have up to 4 companies (users) working out of the facility (14). To simplify maintenance, NRCAN has deliberately omitted Junction-to-Track associations for Junctions (15) in GEOBASE as their locations are mostly derived.

The start and end distances provided with referenced railway subdivisions, together with event (crossings, marker posts, structures, stations) distances along the subdivision suggest that the NRWN/ORWN data could be adapted to a Linear Referencing System in the future.

Physical Model (Implemented) CAVEAT: At this time, Natural Resources Canada GEOBASE does not have plans to create a normalized geodatabase for their implemented NRWN dataset. NRWN will in the interim be maintained as denormalized (flattened attributes) layers by GEOBASE staff. As a consequence and as an exception to LIO database normalization standards, the Ontario Railway Network (ORWN) version of the NRWN model has been implemented in the LIO database in the same denormalized fashion at the request of the Information Owner’s business area (Base Data Infrastructure). NRWN field names were also retained in the ORWN model. This simple design will facilitate ORWN Data Class updates derived from NRWN data exports. If and when work proceeds to normalize the NRWN database, the ORWN version of the model will be updated. If desired, users may still build interlayer relationships for the Track and Subdivision references via the TRACK_NID.

7 Note to ORWN data users ORWN layers will be loaded into the Land Information Ontario (LIO) Warehouse with pre-populated data derived from denormalized GEOBASE NRWN data layer exports. With the exception of data revision date fields, all fields in the NRWN/ORWN dataset are assigned values, even when there is no attribute information available about the feature. The default values are listed below: Value Comments This value is common in numeric fields where information -1 is not available or applicable for the feature. “-1” is used in these instances as “0” (zero) can be a legitimate value e.g. Subdivision Start Distance. None Found mostly in free-text fields (e.g. names) where information is not available or is not applicable. The NRWN geodatabase stores numeric code lookup values instead of text for all permissible values. To make the dataset more user-friendly, the ORWN version differs by storing the full text value instead of the numeric code. The following section is a primer about other referenced information that will be found in the ORWN data: About Subdivisions A Subdivision is an administrative unit of a national or regional network of tracks used to transport freight and/or passengers. A Subdivision is identified by a name or number, and/or a colour and is delimited by a Junction point at each extremity. Several railway Subdivisions are often interconnected to form a greater administrative Railway Division. In railway practice, the Subdivision Start Distance always begins at 0.00 (Mile or Kilometre)

Extent of the Webbwood Subdivision of the Huron Central Railway in Northern Ontario

Information about a Subdivision in NRWN includes: Attribute Example Description Name (using previous diagram) Unique National Identifier (NID) Subdivision 1867ddb0dc2b17df937b1 assigned to every Subdivision in NID 204350c4a66 GEOBASE. Subdivision Name, number or colour Webbwood Name associated to the Subdivision. Subdivision Location where the Subdivision Start 0.00 starts (expressed as a distance). Distance Subdivision Location where the Subdivision 179.10 End Distance ends (expressed as a distance). Unit of distance for the Subdivision Subdivision Start and End points Unit Of Mile* expressed as either Mile or Distance Kilometre. * Many Canadian railway companies still use the imperial system (miles) to identify Subdivision distances. In ORWN, Subdivision Start and End Distance points are represented in the Junction layer where the field value for Subdivision Limit Indicator = “Yes”. Where a Subdivision limit is not defined by a switch, diamond or end junction, a virtual Junction feature is created at the Subdivision’s transition point with a Junction Type of “Administrative”. Subdivisions often have Marker Posts affixed to the side of the rail at regular intervals whose markings generally increase in value as the line progresses westward or northward. For additional information, refer to the Marker Post section of this document. Subdivision associations will be primarily made through the ORWN Track layer, where each Track feature must be associated to one (1) and in rare cases two (2) Subdivisions. Likewise, each Subdivision is associated to one or more Tracks.

Additional Information The University of Alberta Library online Atlas of Alberta Railways provides an excellent example of a Canadian Pacific Railway (CPR) Subdivision map which can be viewed at University of Alberta Library.

Track Segmentation Rules How track and track segment features are defined by NRWN/ORWN.

Example of a Track as defined by National Railway Network GEOBASE standards A “Track” is defined by the presence of a Junction at both ends as illustrated in the diagram above. Each Track is assigned a unique National Identifier (NID). This value is stored in the Track NID field. A “Track” is made up of one or more track segments, with a new feature created whenever there is a change in one or more of the track attributes e.g. a different Track Operator, Status, Design Speeds etc. Rules:  A separate feature is created for each track segment in the ORWN Track layer.  Each track segment is assigned a unique NID and this value is stored in the Track Segment NID field.  A grouping of unique segments defined for a “Track” can all share the same Track NID, as demonstrated in the diagram below.

Example of a Track made up of 4 segments – a segment is created every time there is a difference in one or more Track attribute values between adjacent segments. Track Feature References by Other ORWN Layers As explained in the General Overview of the NRWN (p.5), a reference to the parent Track and associated Subdivision information are present in the other supporting ORWN layer features (Mile Post, Structure Line/Point, Crossing, and Station). These associations are made through the Track NID, though no hard interlayer relationships have been implemented with the ORWN model.

The diagram below illustrates how typical Track/Subdivision associations are made by other ORWN layers.

In this example a Marker Post reference to the Track it is associated to is made through the Track NID, with the following information carried across: The Track’s NID, Name and Classification (yellow), and first (mauve) and second (green) Subdivision’s NID, Name and Unit of Distance. Associated layers will also store the distance that the feature is located in the referenced Subdivision(s) (rose). In this example, the Marker Post is at mile 174.00 within the Webbwood Subdivision. ORWN Common Attributes The following attributes are common to all LIO ORWN data class features, and are listed once here in this section for document brevity sake.

Logical Attribute Name Field Type Description and Context Physical Field Name OGF ID Unique Ontario Geospatial Feature (OGF) NUMBER (13) OGF_ID ID assigned to all LIO database features. A unique National Identifier (NID) that is used by Natural Resources Canada (NRCAN) as a key in their geospatial information holdings. It is based on the Universal Unique Identifier (UUID), a randomly generated 32 character key that National Identifier is guaranteed to always be unique. VARCHAR(32) NID Note: NRCAN strips the "-" (hyphen) separator from their generated identifiers. e.g.: 0554ddb0-dc4b-11df-937b- 0800200c9a66 is stored as 0554ddb0dc4b11df937b0800200c9a66 The state, province or territory that the Administrative Area VARCHAR(7) feature is located in. For ORWN this field’s ADMINAREA value will always be “Ontario” (ON). This 11

Logical Attribute Name Field Type Description and Context Physical Field Name field will be used as a filter to trap for non-Ontario data during ORWN data import. Standards Version The version number of the standards used VARCHAR(5) SPECVERS to create the feature e.g. 1.0 The security classification of the dataset determined by Natural Resources Canada Security Classification VARCHAR(12) GEOBASE for the National Railway SECURCLASS Network data. NRWN data are all “Unclassified”. The character date that the spatial data Geometry Creation was created (Format: YYYYMMDD). Date VARCHAR(8) Note: If the month or day is not known, GEOCREDATE the corresponding characters are left blank. The character date that the spatial data Geometry Revision was revised (Format: YYYYMMDD). Date VARCHAR(8) Note: If the month or day is not known, GEOREVDATE the corresponding characters are left blank. Geometry Acquisition The type of data source or technique used Technique to populate (create or revise) the VARCHAR(25) geometry (spatial) data. GEOACQTECH Click here to see permissible values The planimetric accuracy of the represented feature expressed in (whole) meters as a Circular Map Accuracy Standard (CMAS).

Geometric Planimetric The value in this field represents the Accuracy NUMBER(3) accuracy difference between the mapped GEOACCURA feature against its real-world location. For example, a value of 10 meters for a mapped feature suggests that a person should be able to find it on the ground within 10 meters of its mapped coordinates. The affiliation of the organization that Geometry Provider generated (created or revised) the VARCHAR(25) GEOPROVIDE geometry (spatial) data. Click to see permissible values Attribute Creation VARCHAR(8) The character date that the attribute data 12

Logical Attribute Name Field Type Description and Context Physical Field Name Date was created (Format: YYYYMMDD). ATTCREDATE Note: If the month or day is not known, the corresponding characters are left blank. The character date that the attribute data Attribute Revision was revised (Format: YYYYMMDD). Date VARCHAR(8) Note: If the month or day is not known, ATTREVDATE the corresponding characters are left blank. The type of data source or technique used Attribute Acquisition to populate (create or revise) the attribute Technique VARCHAR(25) data. ATTAQTECH Permissible values identical to those for Geometry Acquisition Technique.

The affiliation of the organization that Attribute Provider generated (created or revised) the VARCHAR ATTPROVIDE attribute data. Permissible values identical to those for Geometry Provider. Effective Datetime Date/time the record was created or last DATE EFFECTIVE_DATETIME modified in the source database. System Datetime Date/time the record was loaded into or DATE SYSTEM_DATETIME last modified in the LIO database.

Geometry Acquisition Technique Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the type of Unknown -1 data source or technique used to populate the object. None 0 No value applies. Other 1 Other value than those listed. Data collected using a Global Positioning System (GPS) GPS 2 device. Orthoimage 3 Orthorectified satellite imagery Orthophoto 4 Orthorectified aerial photo. Vector Data 5 Digital vector data Paper Map 6 Conventional source of information like a map or a plan. Field Completion 7 Information gathered from people directly in the field.

Raster Data 8 Data resulting from a scanning process. Digital Elevation 9 Data coming from a Digital Elevation Model (DEM). Model Aerial Photo 10 Aerial photography not orthorectified. Raw imagery 11 Satellite imagery not orthorectified. Geometric information that has been computed (not Computed 12 captured). END Geometry Provider Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the Unknown -1 feature’s provider. Other 1 Other value than those listed. Federal 2 Federal department or agency. Provincial/ 3 Provincial/territorial department or agency. Territorial Municipal 4 Municipal department or agency. Private 5 Private sector organization or agency. END The next section provides details about the individual ORWN layers.

ORWN Track (ORWNTRK) A track provides a guide for the movement of trains and other equipment. In general, one linear feature represents the two rails of a track. A track is bounded by two junction points and is segmented at each change in attributes along its course. Note: A Track has:  One (1) Owner and one (1) main Operator (e.g. Canadian National)  Up to four (0-4) Users (e.g. VIA)  Up to two (1-2) associated administrative Subdivisions that it belongs to. ORWN Track segments are represented as linear (line) features in this layer.

Top: Siding off of the main Huron Central Railway line in Blind River, Ontario. The siding is used by a local trucking company to load logs into hopper cars to be delivered to the E.B. Eddy pulp mill in Espanola. Aerial Photo: FRI 2008. Photo: J. Gratton May 31, 2010 ORWN Track represents the core building block of the ORWN, upon which other track-related features such as junctions, stations, structures and marker posts are associated to.

The primary ORWN Track attributes are as follows (logical view for clarification):

Logical Attribute Name Field Type Description/Context Physical Field Name National Identifier (NID) assigned to every Track feature in the National Railway Network (NRWN) geodatabase. Each Track feature is defined by a junction Track NID at both ends and is made up of one or more VARCHAR(32) TRACKNID uniquely identified Track segments (See Track Segment ID description). As such, the same Track NID may be referenced by one or more unique track segments. A unique National Identifier (NID) assigned to every Track segment with uniform characteristics. Track Segment ID VARCHAR(32) Note: Each Track segment will be assigned a TRACKSEGID unique identifier, and a group of Track segments may reference the same Track NID (See Track NID description). Name associated to the track by a national or sub national agency. Note: A value of "None" will be stored in this field when information is either not applicable or not available. Track Name VARCHAR(100) TRACKNAME Not every Track will be assigned a name, the values found in this field will be mostly reserved for supporting lower track classifications such as yards and sidings that are known locally by name e.g. “Knapford Yards” or “Wellsworth Siding #2”. Functional classification based on the importance of the role that the track Track Classification VARCHAR(20) performs in the connectivity of the rail TRACKCLASC network. Click here to see permissible values

Level of authority that issued the certificate Regulator VARCHAR2(10) of fitness to the Track Operator. REGULATOR Click here to see permissible values

Logical Attribute Name Field Type Description/Context Physical Field Name The type of railway transport used on the Transport Type VARCHAR2(10) track. TRANSPTYPE Click here to see permissible values Identification of what is transported on the Use Type VARCHAR2(25) track. USETYPE Click here to see permissible values The nominal distance between the two outer rails (gauge) of a railway track. Gauge VARCHAR2(10) Note: Ontario does not have Narrow Gauge GAUGE railways. Click here to see permissible values The number of tracks represented by the track geometry. Number of Tracks NUMBER(1) For the most part, standard NRWN practice NUMTRACKS is to be spatially accurate with a 1:1 ratio. 1 segment will represent 1 track in the ORWN Track layer. Indication whether the railway is provided Electrification Flag with an electric system to power vehicles VARCHAR2(8) ELECTRIC moving along it. Click here to see permissible values The status of the Track feature. Click here to see permissible values Note: Abandoned track systems are not stored in NRWN as rails are removed from Status VARCHAR2(20) the track bed and the feature is no longer STATUS considered a railway. The track bed right-of- way is usually sold or transferred to an organized/unorganized municipality and rehabilitated for use as a recreational trail or access road, or allowed to revert to nature. Maximum allowable operating speed for freight trains (as measured in the "Unit of Design Speed Speed" field). Freight NUMBER(3) Note: A value of -1 will be stored in this SPEEDFREIT field if the speed information is not available or applicable.

Logical Attribute Name Field Type Description/Context Physical Field Name Maximum allowable operating speed for Design Speed passenger trains (as measured in the "Unit Passenger NUMBER(3) of Speed" field). SPEEDPASSE Note: A value of -1 will be stored in this field if the speed information is not available or applicable. Units of measure applied to the value stored Unit of Speed in the Design Speed fields (Miles Per Hour VARCHAR2(20) UNITOFSPEE OR Kilometres Per Hour OR Unknown). Click here to see permissible values Unique identifier (ID), usually a number, assigned to the track and used internally by Track Source ID a national or sub-national agency. VARCHAR2(50) SOURCEID Note: A value of "None" will be stored in this field when information is either not applicable or not available. The English name of the rail company that operates the track. Note 1: A track operator is a railway company responsible for maintaining the Operator English track, signalling system, bridges, tunnels, Name VARCHAR2(100) stations, depots, wharfs, and other OPERATOENA infrastructures connected with the track. Note 2: A value of "None" will be stored in this field when information is either not applicable or not available. Example: Huron Central Railway Inc. The French name of the rail company that operates the track. Operator French Note: A value of "None" will be stored in this VARCHAR2(100) Name field when information is either not OPERATOFNA applicable or not available. Example: Chemin de fer Huron central

Logical Attribute Name Field Type Description/Context Physical Field Name The reporting mark associated to the Operator or Carrier as assigned by a national or sub national agency. The reporting mark usually represents the Operator Reporting company acronym. For example, the Mark VARCHAR2(10) reporting mark for Canadian National is CN. OPERATORMK Note: A value of "None" will be stored in this field when information is either not applicable or not available. Example: HCRY = Huron Central Railway Location where the operator portion of the Operator Start Subdivision starts (expressed as a Distance NUMBER(5,2) distance). The unit of measure is identified OPSUBSTART in the Operator Unit of Distance field. Example: 0.00 Location where the operator portion of the Operator End Subdivision ends (expressed as a distance). Distance NUMBER(5,2) The unit of measure is identified in the OPSUBEND Operator Unit of Distance field. Example: 179.10 Unit of distance used by the operator for Operator Unit of their operating start and end distances Distance VARCHAR2(9) expressed as either Mile, Kilometre or OPSUBUDIS Unknown.

Owner English The English name of the company that owns Name VARCHAR2(100) railway equipment and/or facilities. OWNERENA Example: Canadian Pacific The French name of the company that owns Owner French Name VARCHAR2(100) railway equipment and/or facilities. OWNERFNA Example: Canadien Pacifique The next set of attributes identify the Track Users (up to 4 – denormalized) Note: The Track Operator, User and Owner can all be the same company. Track User 1 English Track User reference 1: Name VARCHA2(100) The English Name of the company that uses TRKUSR1ENA railway equipment and/or facilities. A track

Logical Attribute Name Field Type Description/Context Physical Field Name may have up to four users. Note: A value of "None" will be stored in this field when information is either not applicable or not available. Example: Huron Central Railway Inc. Track User reference 1: The French Name of the company that uses railway equipment and/or facilities. A track Track User 1 French may have up to four users. Name VARCHAR2(100) Note: A value of "None" will be stored in TRKUSR1FNA this field when information is either not applicable or not available. Example: Chemin de fer Huron central Track User reference 1: The reporting mark associated to the User as assigned by a national or sub national agency. The reporting mark usually Track User1 represents the company acronym. For example, the reporting mark for Canadian Reporting Mark VARCHAR2(10) TRKUSR1RMK National is CN. Note: A value of "None" will be stored in this field when information is either not applicable or not available. Example: HCRY

Track User 2 English Track User reference 2: Name VARCHA2(100) See description for Track User 1 English TRKUSR2ENA Name.

Track User 2 French Track User reference 2: Name VARCHAR2(100) See description for Track User 1 French TRKUSR2FNA Name. Track User 2 Track User reference 2: Reporting Mark VARCHAR2(10) See description for Track User 1 Reporting TRKUSR2RMK Mark.

Logical Attribute Name Field Type Description/Context Physical Field Name Track User 3 English Track User reference 3: Name VARCHA2(100) See description for Track User 1 English TRKUSR3ENA Name. Track User 3 French Track User reference 3: Name VARCHAR2(100) See description for Track User 1 French TRKUSR3FNA Name. Track User 3 Track User reference 3: Reporting Mark VARCHAR2(10) See description for Track User 1 Reporting TRKUSR3RMK Mark. Track User 4 English Track User reference 4: Name VARCHA2(100) See description for Track User 1 English TRKUSR4ENA Name.

Track User 4 French Track User reference 4: Name VARCHAR2(100) See description for Track User 1 French TRKUSR4FNA Name.

Track User 4 Track User reference 4: Reporting Mark VARCHAR2(10) See description for Track User 1 Reporting TRKUSR4RMK Mark. The next set of attributes is reserved for Subdivision references (denormalized). Only in rare instances will a Track have a 2nd Subdivision reference. Subdivision reference 1: National Identifier (NID) assigned to the subdivision. A subdivision is an administrative unit of a national or regional network of tracks used Subdivision1 NID to transport freight and/or passengers. A VARCHAR2(32) SUBDI1NID Subdivision is identified by a name or a number, and/or a colour and is delimited by a junction point at each extremity. Note: A value of "None" will be stored in this field when information is either not applicable or not available. Subdivision reference 1: Subdivision 1 Name VARCHAR2(100) Name, number or colour associated to the SUBDI1NAME subdivision.

Logical Attribute Name Field Type Description/Context Physical Field Name Note: A value of "None" will be stored in this field when information is either not applicable or not available. Example: Webbwood Subdivision reference 1: Location where the subdivision starts (expressed as a distance). Subdivision 1 Start NUMBER(5,2) Note: A value of -1 will be stored in this SUBD1START field if distance information is not available or applicable. Example: 0.00 (Webbwood Subdivision) Subdivision reference 1: Location where the subdivision ends (expressed as a distance). Subdivision 1 End NUMBER(5,2) Note: A value of -1 will be stored in this SUBD1END field if distance information is not available or applicable. Example: 179.10 (Webbwood Subdivision) Subdivision reference 1: The unit of distance used by a railway Subdivision 1 Unit company for associated subdivision distance of Distance VARCHAR2(9) values expressed as either Mile, Kilometre SUB1UNITDI or Unknown. Example: Mile

Subdivision2 NID Subdivision reference 2: VARCHAR2(32) SUBDI2NID See description for Subdivision 1 NID. Subdivision 2 Name Subdivision reference 2: VARCHAR2(100) SUBDI2NAME See description for Subdivision 1 Name. Subdivision reference 2: Subdivision 2 Start NUMBER(5,2) SUBD2START See description for Subdivision 1 Start Distance. Subdivision 2 End Subdivision reference 2: NUMBER(5,2) SUBD2END See description for Subdivision 1 End

Logical Attribute Name Field Type Description/Context Physical Field Name Distance.

Subdivision 2 Unit Subdivision reference 2: of Distance VARCHAR2(9) See description for Subdivision 1 Unit of SUB2UNITDI Distance. LIO and ORWN Common Attributes

Track Classification Permissible values: NRWN Value Definition Code Value used when it is impossible to determine the track Unknown -1 classification. Main 1 Main track of the network. Track of lower rank that comes off the main track. It is Siding 2 double-ended to rejoin the main track. (see example on p.12) Track of lower rank that comes off the main track. It is single ended and does not rejoin the main track.

Spur 3

Pictured above: Example of a Spur off of the Huron Central Railway on Trunk Road in Sault Ste. Marie, Ontario. This spur is used to offload fuel at the tank farm. - Image: © Google Earth

Complex series of railway tracks for storing, sorting, or loading/unloading rolling stock and/or locomotives. Railway yards have many tracks in parallel for keeping rolling stock stored off of the main line, so that they do not obstruct the flow of rail traffic.

Yard 4

Pictured above: Example of a Yard near the end of the Huron Central Railway in Sault Ste. Marie, Ontario. - Image: © Google Earth Connecting 5 Track which branches off a Subdivision that establishes a connection to another Subdivision. Short connecting track between two or more other tracks.

Crossover 6

Pictured above: Example of a Crossover near the Toronto Metro Convention Centre. - Photo: J. Gratton, Sept. 2006

Track arranged in the form of the letter “Y”. This track formation is often used by trains to reverse the locomotive’s direction.

Wye 7

Pictured above: Example of a Wye used by the Huron Central Railway in Sault Ste. Marie, Ontario. Right: SW view from the Wye’s end (red asterisk). Image: © Google Earth, Photo: J. Gratton March 28, 2011 Average route a ferry boat takes over a waterbody when transporting trains between two fixed locations on the rail network.

Ferry Route 8

Above: C.P. Rail Ferry “Windsor” circa 1940 (now scrapped) Photo Credit: Historical Collections of the Great Lakes END Regulator Permissible Values: NRWN Value Definition Code Unknown -1 Value used when it is impossible to determine the regulator type. Other 1 Other value than those listed. Federal 2 Federal government. Provincial 3 Provincial government. Municipal 4 Municipal government. END

Transport Type Permissible Values: NRWN Value Definition Code Unknown -1 Value used when it is impossible to determine the transport type. Railway transport usually consisting of two parallel rails (tracks) on which a powered-vehicle or locomotive pulls or pushes a connected rolling stock along a rail line in order to transport freight or passengers from one destination to another.

Train 1

Canadian Pacific freight train in British Columbia Image Source: Wikipedia Railway transport based on a single rail (track) which acts as its only support and guideway.

Monorail 2

Toronto Zoo Monorail - Image Source: Wikipedia

NRWN Value Definition Code Railway transport system used in large urban areas which runs on separate track from other transport systems; is usually electrically powered and mostly runs under ground.

Subway 3

Toronto Subway Train - Image Source: Wikipedia

Railway transport system used in urban areas, which often runs at street level, sharing road space with motor traffic and pedestrians. Tramways are usually electrically powered.

Tramway 4

Toronto Transit Commission (TTC) Tramway – Image Source: Wikipedia Railway transport based on a single overhead rail (track), acting as support and guideway, from which a vehicle is suspended beneath to move along the railway.

Suspended 5

The Wuppertal Schwebebahn, Germany Suspension Railway Image Source: Wikipedia END

Use Type permissible values: NRWN Value Definition Code Value used when it is impossible to determine the use type of the Unknown -1 track. Freight 1 Track is used solely for the transport of freight. Passenger 2 Track is used solely for passenger service. Track is used solely by a tourist operator. Tourist 3 A good example of Tourist use is the South Simcoe Railway in Tottenham, Ont. Freight Track is used for freight and passenger service. and 4 Passenger Freight and 5 Track is used for freight and tourist service. Tourist END Gauge Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the gauge of the Unknown -1 railway track. Standard 1 Rails are 1.435 metres apart. Narrow 2 Rails are 0.967 metres apart. Other 3 Other type (value) of gauge not defined or listed. END Electrification Flag Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the existence that Unknown -1 the railway is electrified. Presence 1 Railway is powered by electricity. Absence 2 Railway is not electrified. END Status Permissible Values: NRWN Value Definition Code Unknown -1 Value used when it is impossible to determine the status. Under 1 Track system is currently being built. Construction Discontinued 2 Track is still present but no longer in use. Operational 3 Track is operational.

NRWN Value Definition Code Seasonal 4 Track is operational for a limited time (season). END Unit of Speed Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the unit of Unknown -1 speed. Miles Per Hour 3 Speed is expressed in miles per hour. Kilometres Per 4 Speed is expressed in kilometres per hour. Hour END NOTE With the exception of ORWN Junction, all other ORWN layers will include Track and Subdivision attribute references. As these attributes are described above in the ORWN Track model, the references will be mentioned, but not be covered off in detail in this guide. The attributes are listed in full and are colour coded in each respective ORWN layer model diagrams.

ORWN Structure Line (ORWNSTLN) A Linear (line) representation of a structure built to support, or protect a track. Note:  Track Structures are represented as a linear (line) feature in this layer  Features in this layer should not be duplicated in the ORWN Structure Point layer.

Pictured above: The “Red Sucker Tunnel” on the CPR line at Mile Post 71, Heron Bay Subdivision on the north shore of Lake Superior Southeast of Coldwell, Ontario in this photo dated @1917. Source: Railway Wonders of the World, Frederick A. Talbot, 1945. Right: The same tunnel as represented spatially in the ORWN Structure Line layer.

ORWN Structure Line attributes are as follows:

Logical Attribute Name Field Type Description/Context Physical Field Name National Identifier (NID) assigned to every NID VARCHAR(32) Structure feature in the National Railway Network NID (NRWN) geodatabase. Unique identifier assigned to the structure when it is part of a set of separate adjoining structures grouped to form one common structure. This identifier allows for the reconstitution of a structure Structure ID feature that is fragmented by junctions. VARCHAR(32) STRUCID Note: A value of "None" will be stored in this field when information is either not applicable or not available. See note about Grouping/Amalgamating ORWN Structures Features The English language version of the railway Structure English structure name as assigned by a national or sub Name VARCHAR(100) national agency. STRUENNAME Note: A value of "None" will be stored in this field

Logical Attribute Name Field Type Description/Context Physical Field Name when information is either not applicable or not available. Example: Red Sucker Tunnel The French language version of the railway structure name as assigned by a national or sub Structure French national agency. Name VARCHAR(100) Note: A value of "None" will be stored in this field STRUFRNAME when information is either not applicable or not available. Example: Tunnel Suceur Rouge The type of structure used to support or protect the Structure Type VARCHAR(15) track. STRUCTYPE Click here to see list of permissible values Subdivision reference 1: Distance at which the structure is positioned along the subdivision. The unit of measurement is Subdivision 1 identified in the associated Unit of Distance field for Distance NUMBER(5,2) the Subdivision. SUBD1DIST Note: A value of -1 will be stored in this field if distance information is not available or applicable. Example: The Red Sucker Tunnel is located at mile 71.00 of the Heron Bay Subdivision. Subdivision reference 1: Subdivision 1 A qualifier about the value stored in the Subdivision Distance Type VARCHAR2(15) 1 Distance field. It describes the type of distance SUB1DISTY associated to a track feature. Click here for list of permissible values. Subdivision 2 Subdivision reference 2: Distance NUMBER(5,2) See description for Subdivision 1 Distance. SUBD2DIST Subdivision 2 Subdivision reference 2: Distance Type VARCHAR2(15) SUB2DISTY See description for Subdivision 1 Distance Type. Track and Subdivision referenced attributes through Track NID LIO and ORWN Common Attributes

Structure Type Permissible Values: Value NRWN Code Definition Value used when it is impossible to determine the structure Unknown -1 type. Manmade construction that supports track(s) on a raised structure and spans an obstacle such as a depression, water, a road or other tracks.

Example 1: A steel railway bridge spanning the Mississagi River west of the town of Blind River, Ont. Bridge 1 Photo: J. Gratton May 22, 2010

Example 2: Two bridges, one over Lauzon Creek (left) and one over the old King’s Highway (right). Both located along the Huron Central Railway, Webbwood Subdivision in Algoma Mills, Ontario. Photo: J. Gratton March, 2010

Value NRWN Code Definition Manmade construction that supports track(s) on a moveable raised structure and spans an obstacle such as a river, a road or other tracks.

Bridge 2 Moveable

Example: A railway lift bridge spanning the Soo Locks in Sault Ste. Marie Michigan. The bridge lifts vertically to allow the passage of Great Lakes freighters through the St. Mary River locks on their way to/from Lake Superior. Photo Source: © Google Earth Street View

Manmade roofed structure that protects Track(s) from snow or rock slides. Note: There are no snow sheds on any of Ontario’s railway networks.

Snow Shed 3

Example: A snow shed on the C.P.R. line on Ross Peak in the Selkirks, British Columbia, in this late 19th century glass-plate photograph taken by Norman Caple. Photo Source: City of Vancouver Archives–Public Domain

Enclosed manmade construction built to get track(s) through or below a natural feature or other obstructions.

Tunnel 4

Example: St. Clair railway tunnel in Sarnia, Ontario. Source: © Google Earth Street View

Device used to channel water or as a passage for a trail or road under Track(s). Note: Because of their size and orientation beneath tracks, the majority of culverts are represented as points in the NRWN/ORWN Structure Point layer.

Example 1: A double concrete water crossing in a marshland Culvert 5 area near the Mississagi First Nations, west of Blind River, Ont. Photo: J. Gratton May 22, 2010

Example 2: A steel culvert under the Huron Central Railway rail bed near the Mississagi First Nations west of the town of Blind River, Ont. Photo: J. Gratton May 22, 2010

Manmade linear structure built along a waterway or floodway to control the flow of water and supporting track(s). Example: VIA Rail train passing over the Seguin River Dam, Bala Subdivision near Parry Sound, Ontario.

Dam 6

Photo: Screen capture from anonymous video END

Subdivision 1 Distance Type Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the distance Unknown -1 associated to the track event. None 0 No value applies. Distance value is posted on the track event location “in the real Posted 1 world”. Distance value was interpolated between two distances posted on interpolated 2 track events. Distance value was a calculated length from a given point of calculated 3 reference. END

Grouping ORWN Structure Features Below is imagery of a railway bridge in Campbellton, New Brunswick with the overlaid spatial NRWN Structure Line layer.

Imagery: Google Earth – Spatial Data: NRWN Structure Line layer Although we can see in the imagery that the railway bridge is one structure on the ground, the bridge is represented as two separately identified features in the NRWN Structure Line layer. Each represented feature above has been assigned a unique NID, as there are two separate railway tracks going over the bridge. Using the shared Structure ID permits us to document the separately stored features as belonging to the same structure on the ground as demonstrated in the chart below. Bridge (top) Bridge (bottom) NID: NID: 7c42d980969843a8b3f00e3b7d5535e2 d4097e9b228f4b1880f0cb9475b0123e STRUCID: STRUCID: 0bf76519eab14f68bcf652bafa893716 0bf76519eab14f68bcf652bafa893716

Note: The grouping of Structure Point features follows the same principle described above.

ORWN Structure Point (ORWNSTPT) Point representation of a structure used to support or protect a track. Note:  Track Structures are represented as a point features in this layer.  Features in this layer should not be duplicated in the ORWN Structure Line layer.  ORWN Structure Point attributes are identical to the ORWN Structure Line layer except that the point version features are not assigned English/French names.  Because of their size and orientation to the track(s), culverts are most likely to be represented as a point feature in this layer as illustrated below.

Above: Culvert under the rail bed of the Huron Central Railway near Mississagi First Nations, west of the Town of Blind River Ontario. Photo: J. Gratton May 22, 2010

The ORWN Structure Point attributes are as follows:

Please refer to ORWN Structure Line Attributes section for descriptions.

ORWN Crossing (ORWNCROS) The location along the rail network where a track crosses another network. It identifies the location and type of crossing that traverses either on, above or below a track. A crossing includes any structure supporting that part of the track or facilitating the crossing. Crossings are often equipped with public warning signs and audio/visual signalling safeguards to control and protect vehicular and pedestrian traffic. Crossings are represented in the LIO ORWN Crossing layer as point features.

Example: Huron Street railway level crossing in Sault Ste. Marie, Ontario. It is located at mile point 0.64 along the Algoma Central Railway line, Soo Subdivision. Top Left: as mapped. Top Right: As seen from the ground.

Photo: J Gratton Nov. 11, 2010

Note: The distance that the Crossing is located along the Subdivision can often be found written behind the Crossing’s warning sign (above top right) and on nearby automated warning signal control boxes (top

left). Emergency contact telephone numbers are also prominently displayed on the control boxes. Photo: J. Gratton Nov. 8, 2010 Grouping ORWN Crossing Features Below is imagery from St. John’s, New Brunswick of a road overpass (Crown Street) on top of a double-line track and highlighted by the NRWN Track and Crossing data. It should be noted that these types of crossing are not typically equipped with any warning signs or signals

as they do not impede the flow of either road or rail traffic. Imagery: Google Earth – Spatial Data: NRWN Crossing layer Though the road overpass is itself one single physical object on the ground, it is spatially represented in the NRWN layer as 4 separate crossing points; and assigned a unique NID for each feature on the track that intersects a road lane (red triangles in diagram). Grouping the 4 separate points with the same ID in the Crossing ID field (shaded yellow in diagram) informs the user that the road overpass is considered to be one single crossing as seen in the chart below. Crossing (top left) Crossing (top right) NID: NID: d032cfeacf504dd681d3a3ba948a1f7e d293ead6ed1344a99f1028f41ee524ac CROSSINGID: CROSSINGID: b8ee8c1aa72e40d58b45c527871f593f b8ee8c1aa72e40d58b45c527871f593f

Crossing (bottom left) Crossing (bottom right) NID: NID: a8c9a33ba8904a6b86db1aa9e7aba33b 763a109468d7433189ea133fc7cba124 CROSSINGID: CROSSINGID: b8ee8c1aa72e40d58b45c527871f593f b8ee8c1aa72e40d58b45c527871f593f

ORWN Crossing attributes are as follows (logical view for clarification):

Logical Attribute Name Field Type Description/Context Physical Field Name National Identifier (NID) assigned to every NID VARCHAR(32) Crossing feature in the National Railway Network NID (NRWN) geodatabase. Unique National Identifier (NID) assigned to the crossing when it is part of a set of neighbouring points forming an amalgamated crossing. Crossing ID VARCHAR(32) CROSSINGID Note: A value of "None" will be stored in this field when information is either not applicable or not available. See note about Grouping ORWN Crossing Features Level of Crossing Indicates the grade level of the crossing. VARCHAR(15) LEVELCROSS Click here to see list of permissible values

Logical Attribute Name Field Type Description/Context Physical Field Name The type of feature that intersects with the Crossing Type VARCHAR(25) crossing. CROSSINTYP Click here to see list of permissible values Warning System Type of warning signal installation at the crossing. Type VARCHAR(20) WARNINGSYS Click here to see list of permissible values The functional classification of the road feature that crosses the track in relation to the road Functional Road network it belongs to. Classification VARCHAR(20) Note: Permissible values are identical to those ROADCLASS used for the National Road Network (NRN). Click here to see list of permissible value The name of the feature that crosses the track. Crossing Type Name VARCHAR(100) Note: A value of "None" will be stored in this field CROSSTYPNM when information is either not applicable or not available. Number assigned to the route at the crossing. Note 1: Defined as a character field to accommodate alphanumeric Route Number values Route Number VARCHAR(10) such as “17b". ROUTENUMBE Note 2: A value of "None" will be stored in this field when information is either not applicable or not available. Crossing The accessibility of the road or trail at the Accessibility VARCHAR(7) crossing. CROSACCES Click here to see list of permissible values Unique number assigned to the crossing by Transport Canada ID Transport Canada. NUMBER(9) TCID Note: A value of -1 will be stored in this field if information is not available or applicable Subdivision reference 1: Distance at which the crossing is positioned along the subdivision. The unit of measurement is identified in the associated Unit of Distance field Subdivision 1 for the Subdivision. Distance NUMBER(5,2) Note: A value of -1 will be stored in this field if SUBD1DIST distance information is not available or applicable. Example: The crossing seen in the photo at the beginning of this section is located at mile 0.64 of the Soo Subdivision. The crossing seen in the 2nd photo is located at mile 174.29 of the Webbwood Subdivision.

Logical Attribute Name Field Type Description/Context Physical Field Name Subdivision reference 1: Subdivision 1 A qualifier about the value stored in the Distance Type VARCHAR2(15) Subdivision 1 Distance field. It describes the type SUB1DISTY of distance associated to a track feature. Click here to see list of permissible values. Subdivision 2 Subdivision reference 2: Distance NUMBER(5,2) See description for Subdivision 1 Distance. SUBD2DIST Subdivision 2 Subdivision reference 2: Distance Type VARCHAR2(15) SUB1DISTY See description for Subdivision 1 Distance Type. Track and Subdivision referenced attributes through Track NID LIO and ORWN Common Attributes Level of Crossing Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the Unknown -1 crossing’s level at the track. The Crossing is at the same grade as the Track. Example: ‘At Grade’ or level crossing at the th At Grade 1 intersection of 5 Line road and Algoma Central Railway in Sault Ste. Marie, Ontario. Photo: J. Gratton, May 27, 2011 Track passes OVER the infrastructure.

Example: The Algoma Central Railway Over 2 line crossing over Hwy. 17 north of Sault Ste. Marie, Ontario.

Photo J. Gratton, May 27, 2011

NRWN Value Definition Code Track passes UNDER the infrastructure.

Example: Huron Central Railway Under 3 crosses UNDER the Hwy. 17 overpass east of Thessalon, Ontario.

Photo J. Gratton, May 27, 2012 Combination 4 Track passes under an infrastructure and over another one. END Crossing Type Permissible Values: NRWN Value Definition Code Other 1 Another type of crossing not listed. Trail for motorized recreational Trail 2 vehicles, non-motorized vehicles, or pedestrians. Hydrographic feature such as river, stream, lake, wetland Hydrographic 3 etc. Any public or private way or course available for vehicle or Road 4 pedestrian use. Track 5 Grade separated track that crosses another track. Pipeline 6 Pipeline Electrical Power 7 Electrical Power Line Line END

Warning System Type Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the type of Unknown -1 warning installation at the crossing. None 0 No signage or traffic control device present at the crossing. Flashing Lights and Bell activated by railway equipment/employee.

Example: Automated Flashing Lights and Bell along the Huron Central Railway – Webbwood FLB 1 Subdivision and Frontenac Street in Sault Ste. Marie, Ontario. This crossing is located at Mile Post 174.29

Photo: J. Gratton November 8, 2010

Flashing Lights, Bell and Gate Arms activated by railway equipment/employee.

Example: Automated Flashing Lights, Bell and Gate Arms along the Huron Central Railway – FLBG 2 Webbwood Subdivision and new Hwy.17 bypass in Sault Ste. Marie, Ontario. This crossing is located at Mile Post 174.0.

Photo: J. Gratton November 8, 2010

Standard Reflectorized Railway Crossing Sign.

Example: Standard Crossing Sign found at a private crossing along the Huron Central Railway- Webbwood Subdivision and old King’s SRCS 3 Highway in Algoma Mills, Ontario.

Photo: J. Gratton March 31, 2010

NRWN Value Definition Code Stop Sign.

Example: Stop Sign found at a private crossing leading into the Lafarge Lime processing centre in Algoma Mills, Ontario, Huron STOP 4 Central Railway, Webbwood Subdivision.

Photo: J. Gratton April 24, 2011

Railway Crossing Sign and Stop Sign.

Example: Standard Reflectorized Railway Crossing Sign and Stop Sign, located at mile 101.9 SRCS and STOP 5 of the Huron Central Railway, Webbwood Subdivision.

Photo: J. Gratton May 14, 2011

Highway Traffic Signals activated by railway Traffic Signal 6 equipment/employee. Closed Gate 7 Gate that is closed when crossing is not in use. Signals indicating whether it is safe or not safe for Walk Don’t Walk 8 pedestrians to use the crossing. Other 9 Other type of traffic control device than those listed. END

Functional Road Classification Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the Unknown -1 road classification. None 0 No value applies. An unimpeded, high-speed controlled access thoroughfare for through traffic with typically no at- Freeway 1 grade intersections, usually with no property access or direct access, and which is accessed by a ramp. Pedestrians are prohibited. A high-speed thoroughfare with a combination of Expressway/Highway 2 controlled access intersections at any grade. A major thoroughfare with medium to large traffic Arterial 3 capacity. A minor thoroughfare mainly used to access Collector 4 properties and to feed traffic with right of way. A low-speed thoroughfare dedicated to provide full Local/Street 5 access to the front of properties. A low-speed thoroughfare dedicated to provide access to properties with potential public restriction such as: Local/Strata 6 trailer parks, First Nations, strata, private estates, seasonal residences. A low-speed thoroughfare dedicated to provide access Local/Unknown 7 to the front of properties but for which the access regulations are unknown. A high-speed thoroughfare dedicated to provide Alleyway/Lane 8 access to the rear of properties. A system of interconnecting roadways providing for Ramp 9 the controlled movement between two or more roadways. A narrow passage whose primary function is to provide access for resource extraction and may also Resource/ Recreation 10 have served in providing public access to the backcountry. Rapid Transit 11 A thoroughfare restricted to public transit buses. A stretch of road permitting vehicles to come to a Service Lane 12 stop along a freeway or highway. Scale, service lane, emergency lane, lookout, and rest area. A road that is only useable during the winter when Winter 13 conditions allow for passage over lakes, rivers, and wetlands. Farm 14 A stretch of road that is located in a farm field.

Road Accessibility Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the Unknown -1 type of accessibility of the road or trail at the crossing. Unrestricted access at the crossing by a road or trail Public 1 that is opened and maintained by a road authority. Access by road or trail at the crossing is not public.

Private 2

END

Subdivision 1 Distance Type Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the Unknown -1 distance associated to the track event. None 0 No value applies. Distance value is posted on the track event location Posted 1 “in the real world”. Distance value was interpolated between two interpolated 2 distances posted on track events. Distance value was a calculated length from a given calculated 3 point of reference. END

ORWN Junction (ORWNJUNC) Virtual connector point feature of the National Railway Network (NRWN). A Junction may be located at:  the intersection of three or more sets of tracks;  the track end;  the transition of a national, provincial, or territorial boundary;  the beginning and end of a Track Subdivision Junctions are stored and represented in the LIO ORWN Junction layer as point features. Note: Because junction location features are mostly derived and are sometimes virtual (not visible on the ground), NRWN did not make Track/Subdivision references.

Top Left: Mapped Track Junctions for a siding used by a local trucking company in Blind River, Ontario to load pulp logs destined for a mill. Top Right: Mapped Junction 1 as seen on the ground looking west along the Huron Central Railway – Webbwood Subdivision. Note the manual Junction “switch” on the far right as well as the open hopper wagon on the siding. Photo: J. Gratton May 21, 2010

ORWN Junction attributes are as follows:

Logical Attribute Name Field Type Description/Context Physical Field Name

NID National Identifier (NID) assigned to every VARCHAR(32) NID Junction feature in the National Railway Network (NRWN) geodatabase. A true or false indicator if the junction is a point of transition at a National, Provincial Boundary Transition or Territorial border. Indicator VARCHAR(5) Permissible values: BNDYTRIND Value NRWN Code Definition False 0 False True 1 True

A true or false indicator if the junction is a point of transition between track Subdivision Limit subdivisions. Indicator VARCHAR(5) Permissible values: SUBDLIMIND Value NRWN Code Definition False 0 False True 1 True

The type of junction connection located at the end, along or at an interconnection Track Junction Type VARCHAR(15) between three or more tracks at grade TRAJUNCTYP level. Click here to see list of permissible values LIO and ORWN Common Attributes

Track Junction Type Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the type of Unknown -1 track junction. Position of an administrative transition. E.g. Subdivision and/or Provincial/Territorial boundary when a physical Administrative 1 junction type such as a switch, diamond or end is not present at the point of transition. Track configuration which allows a train to cross over another track at grade level in order to pursue its path. Example: Brampton Diamond, Mile 15.6 of the Halton Subdivision on the Orangeville and Brampton Diamond 3 Railway, Brampton, Ontario.

Connection to a single track leading to a dead end (Track terminates). Example: Mile 0 of the Algoma End 4 Central Railway Soo Subdivision near the Station Mall in Sault Ste. Marie, Ontario. Photo: J. Gratton August 15, 2010

Mechanical installation not listed enabling railway trains to be Other 5 guided from one track to another. END

ORWN Station (ORWNSTN) Location identified by a station name sign and designated by that name in a time table (schedule listing the time at which certain events, such as arrivals and departures at a station are expected to take place). Note: A station or stop does not necessarily have to be a building. Ref: FGDC-STD-014.7b-2008

The Algoma Central Railway (ACR) Station located at Soo Subdivision mile 0 in Sault Ste. Marie, Ontario. Photo: J. Gratton August 15, 2010

Stations are represented in the ORWN Station layer as point features.

The primary ORWN Station attributes are as follows:

Logical Attribute Name Field Type Description/Context Physical Field Name National Identifier (NID) assigned to every Station NID VARCHAR(32) feature in the National Railway Network (NRWN) NID geodatabase.

Logical Attribute Name Field Type Description/Context Physical Field Name The English language version of the station name as assigned by a national or sub national agency. Station Name English Note: A value of "None" will be stored in this field VARCHAR(100) STNENNAME when information is either not applicable or not available. Example: Algoma Central Railway Station. The French language version of the station name as assigned by a national or sub national agency. Station Name French VARCHAR(100) STNFRNAME Note: A value of "None" will be stored in this field when information is either not applicable or not available.

Station Type VARCHAR(20) Identifies the type of station. STNTYPE Click here to see list of permissible values A value indicating the number of platforms available Number of Platforms NUMBER(2) at the station. NUMPLATFR Note: A value of -1 will be stored in this field if information is not available or applicable. Station User Reference 1: The English language version of the company name Station User 1 using the facility. English Name VARCHAR(100) Note: A value of "None" will be stored in this field STNUSR1ENA when information is either not applicable or not available. Example: Algoma Central Railway Station User Reference 1: The French language version of the company name Station User 1 French using the facility. Name VARCHAR(100) STNUSR1FNA Note: A value of "None" will be stored in this field when information is either not applicable or not available. Station User Reference 1: The reporting mark associated to the User as assigned by a national or sub national agency. The Station User 1 reporting mark usually represents the company Reporting Mark VARCHAR(10) acronym. For example, the reporting mark for STNUSR1RMK Canadian National is CN.

Note: A value of "None" will be stored in this field when information is either not applicable or not available.

Logical Attribute Name Field Type Description/Context Physical Field Name Example: ACR (Algoma Central Railway) Station User 2 English Track User reference 2: VARCHAR(100) Name See description for Station User 1 English Name. STNUSR2ENA Station User 2 French Track User reference 2: VARCHAR(100) Name See description for Station User 1 French Name. STNUSR2FNA Station User 2 Track User reference 2: VARCHAR(10) Reporting Mark See description for Station User 1 Reporting Mark. STNUSR2RMK Station User 3 English Track User reference 3: VARCHAR(100) Name See description for Station User 1 English Name. STNUSR3ENA Station User 3 French Track User reference 3: VARCHAR(100) Name See description for Station User 1 French Name. STNUSR3FNA Station User 3 Track User reference 3: VARCHAR(10) Reporting Mark See description for Station User 1 Reporting Mark. STNUSR3RMK Station User 4 English Track User reference 4: VARCHAR(100) Name See description for Station User 1 English Name. STNUSR4ENA Station User 4 French Track User reference 4: VARCHAR(100) Name See description for Station User 1 French Name. STNUSR4FNA Station User 4 Track User reference 4: VARCHAR(10) Reporting Mark See description for Station User 1 Reporting Mark. STNUSR4RMK Subdivision reference 1: Distance at which the station is positioned along the Subdivision 1 subdivision. The unit of measurement is identified in Distance NUMBER(5,2) the associated Unit of Distance field. SUBD1DIST Note: A value of -1 will be stored in this field if distance information is not available or applicable. Subdivision reference 1:

Subdivision 1 A qualifier about the value stored in the Subdivision Distance Type VARCHAR(15) 1 Distance field. It describes the type of distance SUB1DISTY associated to a track feature. Click here to see a list of permissible values.

Subdivision 2 Subdivision reference 2: Distance NUMBER(5,2) See description for Subdivision 1 Distance. SUBD2DIST

Logical Attribute Name Field Type Description/Context Physical Field Name Subdivision 2 Subdivision reference 2: Distance Type VARCHAR(15) SUB2DISTY See description for Subdivision 1 Distance Type. Track and Subdivision referenced attributes through Track NID LIO and ORWN Common Attributes Station Type Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the type of station Unknown -1 type. Scheduled stop along a Subdivision where passenger may board or Passenger disembark. 1 Station An example of a passenger station be seen at the beginning of this section. Stop along the Subdivision where operating business occurs.

Maintenance 2

Above: A Maintenance Station on the Huron Central Railway, Webbwood Subdivision mile 102.4 in the town of Blind River. This station is used for track maintenance purposes. Note the rail-capable track inspection/maintenance vehicle parked in front – Photo: J. Gratton, May 2010.

NRWN Value Definition Code Station providing a service that allows for the movement of intermodal freight containers to other transportation type networks.

Right: C.N. Intermodal Terminal in Brampton, Ontario

Intermodal 3

Photo Source: CN –Media Image Centre

Other 4 Other station type than those listed. Mixed 5 Station providing both passenger and freight services. Scheduled stop along a Subdivision where infrastructure is present Freight 6 for the management of freight cars. END

Subdivision 1 Distance Type Permissible Values: NRWN Value Definition Code Value used when it is impossible to determine the distance associated Unknown -1 to the track event. None 0 No value applies. Distance value is posted on the track event location “in the real Posted 1 world”. Distance value was interpolated between two distances posted on interpolated 2 track events. Distance value was a calculated length from a given point of calculated 3 reference. END

ORWN Marker Post (ORWNMKPO) Sign indicating the distance along the network. For example, signs are often posted at intervals along a railway Subdivision indicating the distance from its point of origin in miles or Kilometres. Marker Posts are represented in the LIO ORWN Marker Post layer as point features.

An example of a marker post found along the rail line of the Huron Central Railway in the Algoma Mills area on the North Shore of Lake Huron. Photo: J. Gratton March, 2010 Within the use context of railways, marker posts can be found at set intervals (mile or kilometres) affixed to poles or stakes. Marker Posts are used by railway company staff as reference points for time-table progress, track maintenance work orders and for reporting rail conditions and incidents. Marker posts are often used by railway crews and the Ontario Ministry of Natural Resources (OMNR) to report and/or respond to the location of trackside fires. Note: The distance indicated on the marker post (in either miles or kilometres) reflects the sign’s position relative to the Subdivision’s point of origin. Using the above photo as an example, this sign is located 90 miles west of where the Webbwood Subdivision begins (Sudbury), and mapped as a point feature (pictured right).

With the Webbwood Subdivision’s point of origin in Sudbury, the number found on the each marker would increase in value as you progressed westward (or northward) on the rail line. ORWN Marker Post attributes are as follows:

Logical Attribute Name Field Type Description/Context Physical Field Name National Identifier (NID) assigned to every marker NID VARCHAR(32) post feature in the National Railway Network (NRWN) NID geodatabase. Subdivision reference 1: Distance at which the marker post is positioned along Subdivision 1 the subdivision. The unit of measurement is identified Distance NUMBER(5,2) in the associated Unit of Distance field. SUBD1DIST Note: A value of -1 will be stored in this field if distance information is not available or applicable. Subdivision reference 1: Subdivision 1 A qualifier about the value stored in the Subdivision 1 Distance Type VARCHAR(15) Distance field. It describes the type of distance SUB1DISTY associated to a track feature.

Logical Attribute Name Field Type Description/Context Physical Field Name Click here to see a list of permissible values.

Subdivision 2 Subdivision reference 2: Distance NUMBER(5,2) See description for Subdivision 1 Distance. SUBD2DIST Subdivision 2 Subdivision reference 2: Distance Type VARCHAR(15) SUB2DISTY See description for Subdivision 1 Distance Type. Track and Subdivision referenced attributes through Track NID LIO and ORWN Common Attributes

APPENDIX 1: ORWN Maintenance and Updates Note: The process illustrated below is tentative and may vary once agreements between NRCAN and the OMNR have been confirmed and formalized. The following is a basic overview of how ORWN data will be maintained and updated.

1) LIO Editor users will be accessing a data view of the LIO Warehouse DB ORWN data. 2) Any reported suggested ORWN feature changes will be reported by LIO Editor users to Base Data Infrastructure (BDI) staff using screen captures and other referenced information. 3) BDI staff will compile proposed ORWN changes into an interchange format to be provided to NRCAN GEOBASE NRWN staff. Given the stable nature of railway data, this is not expected to be required often. Data submission to NRCAN will be made on a scheduled basis (e.g. annual).

4) GEOBASE NRWN staff will evaluate the proposed changes, which may involve consulting Railway Companies and/or Transport Canada where appropriate to do so. BDI will be notified whether the proposed changes were approved or not. If approved, GEOBASE staff will incorporate the changes in the NRWN database. 5) On an annual basis, NRWN GEOBASE will export of the NRWN datasets in the agreed-upon data exchange format with BDI. BDI will then download the NRWN data and prepare it for LIO Warehouse DB loading. ORWN layer data refresh may involve posting only the updated ORWN features, or complete layer replacement. 6) Once the ORWN datasets are loaded into the LIO Warehouse database, the updated information is available to users (LIO Editor, LIO data distribution system, AGS).