Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Description

The TSB is an independent agency, created by an Act of Parliament (the Canadian Transportation Accident Investigation and Safety Board Act). Its mandate is to advance transportation safety in the marine, pipeline, rail and air modes of transportation by:

  • conducting independent investigations, including public inquiries when necessary, into selected transportation occurrences in order to make findings as to their causes and contributing factors;

  • identifying safety deficiencies, as evidenced by transportation occurrences;

  • making recommendations designed to eliminate or reduce any such safety deficiencies; and

  • reporting publicly on our investigations and on the findings in relation thereto.

Rail Incident (Occurrence) consists of two types:

  • Reportable – Class 3

  • Non-reportable - Class 1,2,3,4,12

Originator

  1. Transportation Safety Board (TSB)

Use Cases

  1. As a Rail Safety Officer, I want to identify locations of frequent train derailments so that train operator can be notified to take special precaution.

  2. As a Rail Incident Analyst, I want to be able to analyse trends and patterns of rail incidents in order to identify hot spots.

Source(s)

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

TSB Rail Investigation

TSB
TC Smart Maps

CSV

2018

Monthly

Data Dictionary

Free

EGIS Data Folder: TSB_Rail.mdb
CSV

-Use preprocessed MDB file as provided.
-Non-spatial file.
-Updated on 15th of the month.

Remarks

  1. TSB Rail Incident dataset is a non-spatial tabular dataset. Preprocessing to geocode the occurrence location is required using the custom master milepost database.

  2. The data on occurrences are released on or soon after the 15th of each month, and date to the last day of the month preceding their release.

  3. EGIS Data Folder: \\ncras382\Application Source Files\EGIS\Smartmap Files\

Master Milepost Database Creation:

Interpolation of Railway Network milepost: downloaded shp file from National Railway Network Canada Open Data (e.g., SK folder, only tracks and marker post, and grade crossing as well) is partially manual and automated (use FME and ArcGIS to clean data). Several factors can affect the calculation of mileposts such as:

  1. Actual Segment length vs NRCAN length.

  2. Double or parallel tracks.

  3. Cross over tracks along double/parallel tracks.

  4. Track branch off

  5. Track direction

  6. More…

  • Create Main Track Summary Report:

  1. Create an aggregate of all track grouped by: OPERATORMK, RAILWAY, SUBD1END, SUBD1START, SUBD1NAME

  2. Extract actual length

  3. Calculate NRCAN length (i.e. SUBD1END-SUBD1START)

  • Build Continuous Track Segment:

  1. Filter TRACKCLASS=Main from *TRACK.shp (there are also spurs, branches off main track, and railway yards, which we don’t need those to interpolate location)

  2. Connect tracks to form a continuous segment grouped by the following attributes:
    i) RAILWAY
    ii) SUBDI1NAME
    iii) FROM
    iv) TO

  3. Compare/validate the length against NRCAN value.

  4. Validate polyline start/end direction using Grade Crossing milepost for consistency. Reverse direction or flag in the database if necessary.

  5. Validate NRCAN start/end values against Grade Crossing milepost for consistency. Readjust values in the database if necessary.

  6. Perform manual cleanup such as segmented tracks, parallel tracks, split etc.

  7. Repeat the process using the last modified dataset until all tracks are fixed.

  • Interpolate Milepost:

  1. Join the “Connected Track” with “Main Track Summary” database using RAILWAY, SUBD1END, SUBD1START, SUBD1NAME as primary keys.

  2. Extract actual length.

  3. Divide Track into equal segments of 0.1 mile.

  4. Extract/store the coordinates.

  5. Verify interpolated milepost against Grade Crossing milepost for accuracy. Fix and adjust any error if necessary.

  6. Store the newly created mileposts in the Master Milepost Database. **Note: Not all mileposts start at 0.

Disclaimer:

  1. Interpolated Milepost is only approximate. It is not verified nor validated for accuracy, therefore should be used for reference purposes only.

Process for EGIS integration

CSV File Transformation:

  1. Download Rail Occurrence Report CSV file from TSB.

  2. In FME, use the Feature Merger transformer to join Occurrence data and Master Milepost database, using Company, Subdivision and Milepost as primary keys to extract the Lat/Long.

  3. Insert a new attribute to hyperlink TSB Report for records with OccClassID=2 or 3.

  4. A typical Report URL looks like this: http://www.tsb.gc.ca/eng/rapports-reports/rail/2018/r18w0168/r18w0168.asp

  5. Replace r18w0168 with the OccNo and 2018 with OccYear.

  6. Transform the Lat/Long to point.

  7. Output to KML, SHP or GDB as required.

  8. Import into EGIS

Display Optimization:

  1. Sampled/thinned data (generated using data sampling technique) and Class 2 & 3 incidents are displayed at small and medium scale. With scale transition, original data are displayed at large scale thus improve display performance and reduce cluttering.

TC Smart Maps:

  1. Not all GIS applications can consume KML file directly due to its unique data structures such as networklinks, folders, models etc.

  2. Please contact Lawrence Chong, Digital Services Directorate for TC Smart Maps KML dataset and format translation.

  3. TC Smart Maps KML link: \\tc.gc.ca\tcgis\GISData\Google Mashup\TSB_Investigation\Rail\TSB_Investigation-Rail.kmz

Customization:

  1. Schema transformation: As required

  2. Denormalization: No Required

  3. Value coding: Not required

  4. Attribute renaming: As required to improve readability

  5. Attribute removal: It is highly recommended as some fields are unnecessary, this will also reduce file size and improve performance

  6. Geoenrichment: Feature symbolization is recommended to improve visualization. OccClassID=2 or 3 are reportable incidents. It can be symbolized differently and display at smaller scale.

  7. Format translation: As required.

  8. Language translation: French version available.

  9. Update frequency: As identified

  • No labels