Geographic / Track Models

This page provides a comprehensive overview of the geographical and track model data sources utilised within the Rail BI platform. This includes their origins, update frequencies, primary applications and current challenges.

The Rail BI platform integrates multiple geographical and track data sources to support comprehensive asset management, cost modeling, and ETCS deployment planning.

Ongoing efforts focus on addressing data gaps, improving source reliability, and enhancing linking methodologies to ensure optimal accuracy and utility.

Data Source Overview

Model	Data Source	Update Frequency	Primary Application
ELRs	Various	By Network Rail request	Support interlocking definitions
Track Sections	RINM	By Network Rail request	Cost Scaling
Interlocking Milages	SSADS / Rail BI	Network Rail period	Linking assets to interlockings
Waymarkers	Digital Railway Team	By Network Rail request	Displaying interlockings on maps
LTDP Areas	Rail BI	Maintained within Rail BI by users	Grouping ETCS deployments
Train Batch Mapping	Train Fitment Modal	By Network Rail request	Train fitment workbank

Detailed Model Descriptions

Engineer's Line References (ELRs)

Data Source: Various

Description:

ELR definitions have been developed incrementally as additional asset data sources have been integrated into the platform. Unrecognised ELRs are added to the repository as they are identified.

Data Enhancement:

When opportunities arise, ELR names and start/end mileages are backfilled using exports provided by Network Rail personnel. Where asset or track section data contains ELR mileages that fall outside defined ranges, the ELR boundaries are extended accordingly.

Outstanding Issues:

• Network Rail does not maintain a definitive centralised source for ELRs
• ELR start and end definitions are difficult to establish definitively, even among Network Rail GIS teams
• Different ELRs frequently exhibit overlapping boundaries

Track Sections

Data Source: RINM (Railway Infrastructure Maintenance)

Description:

Track section data was originally imported from GEOGIS and is now sourced from RINM.

Primary Applications:

• Defining ELR boundaries
• Scaling costs of United of Measurement (UoM) LX SSADS - Tracks (the number of tracks traversing a signaled level crossing)
• Scaling Costs using UoM STK

Interlocking Milages

Data Source: SSADS / Rail BI

Description:

ELR boundaries for interlockings are managed by SSADS users and imported periodically into Rail BI. These definitions often contain gaps, which are addressed through a gap-filling algorithm that populates missing sections and allocates them to the nearest interlocking where feasible. The extent of these gaps is reported periodically to Network Rail.

Primary Application:

• Linking assets to interlocking areas
• Scaling costs using UoM RK

Waymarkers

Data Source: Digital Railway Team

Description:

Waymarkers contain geographical position data in both ELR - Mileage and Easting - Northing coordinate formats.

Primary Applications:

• Identifying geographical positions of assets defined solely by ELRs, such as STANOX points
• Displaying interlocking areas on a map
• Displaying interlockings on a map

Outstanding Issues:

• Waymarker data has not been updated recently and may no longer reflect current conditions; a well-defined source for updates is not currently available
• Coverage gaps exist within the waymarker dataset

LTDP Areas for Interlockings

Data Source: Rail BI

Description:

Interlockings are organised into logical, contiguous ETCS Long Term Deployment Plan (LTDP) areas. This mapping is maintained within Rail BI.

Primary Applications:

• Ordering and grouping interlockings on rollout calendars and Rail BI outputs
• Organising ETCS deployments into logical geographical areas
• Defining interlocking coverage for train operations

Outstanding Issues:

Train Batch Mapping

Data Source: Train Fitment Model

Description:

This dataset defines the LTDP areas traversed by each train batch (subclass - TOC combination). Ownership has been transferred to Rail BI, where it is maintained as a more granular Interlocking - Train Batch mapping. TABS data is currently under investigation to further refine this mapping.

Primary Applications:

• Train fitment planning aligned with ETCS signalling rollout schedules
• Train related outputs and map displays

Asset Linking Methodologies

ALCRM - SSADS Level Crossing Linking

Background:

All level crossings (LX) are catalogued in ALCRM, with a subset—predominantly signalled level crossings — also recorded in SSADS. Both sources are utilised within Rail BI, with SSADS providing superior data regarding crossing types and target renewal information.

Data Integration:

In principle, every SSADS level crossing should have a corresponding ALCRM entry. Unlinked entries may result in duplicated interventions and costs within the workbank. Successfully linked level crossings are displayed as single items incorporating both SSADS and ALCRM nomenclature along with the ALCRM UID.

Mapping Process:

Initial mappings were provided as part of the Level Crossing Workbank. Unmapped SSADS level crossings are reported periodically to Network Rail, as are unmapped ALCRM entries (though most are legitimate standalone entries). Geographical mappings are established wherever possible using matching ELR mileage data. New SSADS level crossings are reviewed periodically by Daniel Paxton for manual mapping to ALCRM records.

Level Crossing to Interlocking Linking

Purpose:

This linkage enables level crossings to be grouped into interlocking areas for calendar display purposes and defines level crossing routes within certain system components. When a project is defined by interlocking area, level crossings within that area are identified for equivalent work types and/or cost scaling based on level crossing counts.

Current Methodology:

Linking is currently performed geographically. An outstanding task exists to utilise the SSADS Parent ID, where available, to enhance linking accuracy.

Other Assets to Interlocking Linking

Description:

Various assets with associated cost quantities are typically identified by filtering based on ELR coverage defined within interlocking parameters.

Geographic Map Display Capabilities

Interlocking Display

The ELR definitions from SSADS and Rail BI (incorporating gap-filled data) are used to filter all waymarkers within the relevant area. These waymarkers, which contain Easting and Northing coordinates, are plotted on geographical maps to represent interlocking areas visually.

Level Crossing and Asset Display

Assets with ELR position data are mapped to the nearest available waymarker, providing approximate Easting and Northing coordinates for map plotting purposes.