Professional Documents
Culture Documents
OK RIS-7773-INS-Iss-1
OK RIS-7773-INS-Iss-1
Published by RSSB
© Copyright 2021
Rail Safety and Standards Board Limited
Uncontrolled when printed
New document effective 4/09/2021
Issue record
Superseded documents
This standard does not supersede any other Railway Group documents.
Supply
The authoritative version of this document is available at www.rssb.co.uk/railway-
group-standards. Enquiries on this document can be submitted through the RSSB
Customer Self-Service Portal https://customer-portal.rssb.co.uk/
Page 2 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
Contents
Appendices 21
Appendix A Additional guidance for the application of the SC0 file format 21
Definitions 28
References 29
RSSB Page 3 of 29
Uncontrolled when printed
New document effective 4/09/2021
List of Figures
Page 4 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
List of Tables
Table 2: Attributes 15
RSSB Page 5 of 29
Uncontrolled when printed
New document effective 4/09/2021
1.1.1 This document establishes requirements for infrastructure gauging data. This
document also sets out the most commonly used data format for the exchange and
interpretation of infrastructure data used in the process of gauging compatibility
assessment.
1.1.2 This document is complementary to other documents with the suite of gauging
standards including:
a) GIRT7073 Requirements for the Position of Infrastructure and for Defining and
Maintaining Clearances – this document sets out requirements for positioning
infrastructure and maintaining the position of track relative to infrastructure to
achieve gauge compatibility with rolling stock.
b) GERT8273 Assessment of Compatibility of Rolling Stock and Infrastructure –
Gauging and Stepping Distances – this document sets out specific requirements
and responsibilities for the assessment of gauge compatibility and stepping
distances between rolling stock and infrastructure.
1.1.3 This document can be adopted by infrastructure managers, contractors and gauging
consultancies under their respective safety/quality management system or when
specifying products and services.
1.2.1 Compliance requirements and dates have not been specified because these are the
subject of internal procedures or contract conditions.
1.2.2 If you plan to do something that does not comply with a requirement in this RIS, you
can ask a Standards Committee to comment on your proposed alternative. If you
want a Standards Committee to do this, please submit your deviation application
form to RSSB. You can find advice and guidance on using alternative requirements on
RSSB’s website www.rssb.co.uk.
1.3.1 Users of documents published by RSSB are reminded of the need to consider their
own responsibilities to ensure health and safety at work and their own duties under
health and safety legislation. RSSB does not warrant that compliance with all or any
documents published by RSSB is sufficient in itself to ensure safe systems of work or
operation or to satisfy such responsibilities or duties.
1.4.1 This document sets out a series of requirements that are sequentially numbered. This
document also sets out the rationale for the requirement, explaining why the
requirement is needed and its purpose and, where relevant, guidance to support the
requirement. The rationale and the guidance are prefixed by the letter ‘G’.
Page 6 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
1.4.2 Some subjects do not have specific requirements but the subject is addressed through
guidance only and, where this is the case, it is distinguished under a heading of
‘Guidance’ and is prefixed by the letter ‘G’.
1.5.1 The content of this document was approved by Infrastructure Standards Committee
on 11 May 2021.
1.5.2 This document was authorised by RSSB on 14 June 2021.
RSSB Page 7 of 29
Uncontrolled when printed
New document effective 4/09/2021
2.1.1 The infrastructure data file shall be identifiable from the file name.
Rationale
G 2.1.2 This requirement enables the transfer and use of correct infrastructure data for
gauging analysis.
Guidance
G 2.1.3 Common practice is to include references to track codes and linear distance within
the file name as a quick geographical guide to the part of the network where the data
file applies.
G 2.1.4 Common practice on the mainline railway has established folders for each engineer's
line reference (ELR).
2.2 Location
2.2.1 The infrastructure data file shall identify the geographical position within the rail
network to which it applies.
2.2.2 Where the infrastructure data file is associated with a specific structure, the data file
shall include a structure name or reference.
Rationale
G 2.2.3 Knowing the precise location and track to which the infrastructure data applies is
critical to the accuracy of the gauging analysis using the data.
G 2.2.4 These requirements have been established from industry practice for the mainline
railway.
Guidance
G 2.2.5 Practice from the mainline railway uses the following to identify location:
• Engineer's Line Reference (ELR) to identify the route (or part of route),
• Track code to identify the line/track on that route, and
• Linear distance in either miles or km to identify the position along the track.
G 2.2.6 It is commonplace for references to track codes and linear distance to appear within
the file name as a quick geographical guide to the part of the network where the data
file applies. Where there is any discrepancy between the geographical references in
the file names the geographical information contained within the file takes
precedence.
Page 8 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
2.3 Measurement
2.3.1 The infrastructure data file shall identify the date of the measurement.
2.3.2 The infrastructure data file shall identify the survey method used to measure the
infrastructure.
2.3.3 The naming convention shall be consistent with that used by the infrastructure
manager.
Rationale
G 2.3.4 Infrastructure position can move over time, either intentionally through modification
or maintenance activity, or through settlement and ground movement. The data
provides a snapshot of the infrastructure at any given time. Knowing the date of the
measurement is critical to the accuracy of gauging analysis, through the use of the
most recent data and therefore infrastructure position.
G 2.3.5 Different survey methods have different degrees of accuracy in measurement.
Knowing the method of survey is important to ensure that the correct allowances are
applied in the gauging compatibility assessment.
G 2.3.6 This requirement has been established from industry practice for the mainline
railway.
Guidance
G 2.3.7 The survey method refers to the technology used to take the measurement. Examples
of different survey methods could be laser profiling, structure gauging train or simple
platform gauge. Infrastructure managers will specify tolerances to be applied for
different survey methods.
2.4.1 The infrastructure data files shall describe the infrastructure at that location,
sufficient to enable the assessment of gauge compatibility by identifying the
following:
• Horizontal track radius;
• Datum rail (0,0 coordinate);
• Line speed;
• Rail coordinates relative to the true horizontal and vertical plane; and
• Structure profile coordinates relative to the true horizontal and vertical plane.
2.4.2 The file shall also identify the number of coordinate points contained within the file.
Rationale
G 2.4.3 These requirements ensure that the minimum parameters are described to enable the
infrastructure data to be used in gauging compatibility assessment.
G 2.4.4 The number of coordinate points are used to identify whether the data file is
complete. Missing coordinate points could be significant in the gauging assessment.
RSSB Page 9 of 29
Uncontrolled when printed
New document effective 4/09/2021
G 2.4.5 These requirements have been established from industry practice for the mainline
railway.
Guidance
G 2.4.6 The datum rail is established as the 0,0 coordinate and is the position to which all
other coordinates relate.
G 2.4.7 Practice from the mainline railway is to define the left most rail, when standing in the
four foot facing high mileage direction, as the datum rail. Where the infrastructure
data file adopts a different convention for the datum rail, this would be agreed
between the parties involved in the exchange of infrastructure data.
G 2.4.8 Good practice is to include vertical track radius within the file, where this is available.
Where vertical track radius is not available, it is assumed to be straight.
G 2.4.9 Good practice is to use design horizontal curve radius, where available, rather than
instantaneous radius which may include a component of lateral track irregularity that
would already be accounted for in the vehicle modelling process.
Page 10 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
Rationale
G 3.1.2 Use of the file convention as set out by these requirements enables the SC0 file to be
transferred and used by software in gauging compatibility assessment.
Guidance
G 3.1.3 The SC0 file format is the most common format used for the sharing of infrastructure
gauging data. It was originally developed in the late 1980s as a means of facilitating
the interchange of structure gauging profiles between structure profile measuring
equipment and personal computers (PCs).
G 3.1.4 Originally SCN, the file format has latterly become commonly known as the SC0,
hence SC0 has been used throughout this document as a generic name for this file
format. However, it also includes infrastructure data files with other SC? extensions,
see table 5 for a list of other file designations.
G 3.1.5 SC0 files represent a slice of the infrastructure at a point, therefore a structure may
be defined by many slices. Typically slices are taken at 5 m intervals, but this is
dependent on the complexity of the location and the structure.
G 3.1.6 Files with an SCN designation are unedited raw data files. As such they are
incomplete and are no longer considered suitable for transfer of infrastructure data.
G 3.1.7 An example of an SC0 file is set out in appendix A.2.
3.2.1 The SC0 file shall consist of header lines that provide the contextual information for
the coordinate data. These header lines shall consist of an alpha mnemonic followed
by an equals (=) sign.
3.2.2 The mnemonic codes used shall be consistent with the allowable mnemonic codes set
out in Table 1.
RSSB Page 11 of 29
Uncontrolled when printed
New document effective 4/09/2021
Page 12 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
RSSB Page 13 of 29
Uncontrolled when printed
New document effective 4/09/2021
Page 14 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
Rationale
G 3.2.3 These requirements enable the infrastructure data to be used by software in gauging
compatibility assessment.
G 3.2.4 Use of mnemonics not included within this document is permitted, but will not be
read, or understood, by industry standard gauging software.
Guidance
G 3.2.5 Table 1 identifies whether a parameter is required or optional. Required fields are
mandatory for this file format, optional fields are desirable to be included only if the
information is available.
G 3.2.6 Track Structure ID (TSID) is important for identifying the specific track structure from
which the features and attributes can be easily identified. As show in the table TSID
this is required where structure category (SCAT) and structure sub category (SSUB)
are not defined, while SCAT and SSUB are necessary where TSID is not defined. In the
table these fields are shown as R (O) or O (R) to show there is dependency between
them as to the requirement for inclusion in the file. TSID always takes precedence
over SCAT and SSUB.
G 3.2.7 The format for the "GPS=" line in table 1 is an NMEA string. NMEA is a widely used
standard for reporting outputs from global navigation satellite system receivers and
other navigation equipment, and is supported by all major manufacturers. For further
information see NMEA 0183 - Standard for Interfacing Marine Electronic Devices,
National Marine Electronics Association.
3.3 Coordinates
RSSB Page 15 of 29
Uncontrolled when printed
New document effective 4/09/2021
006 LH Rail
007 RH Rail
011 Dowel
014 Equipment
(equipment mounted to the structure
that has the potential to be moved)
015 Intrados
(this is the top point of a circular tunnel)
016 Monument
018 Vegetation
Table 2: Attributes
Page 16 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
Rationale
G 3.3.1.4 These requirements ensure that coordinate data can be interpreted for use in
gauging compatibility assessment.
Guidance
G 3.3.1.5 The attribute code is provided immediately after the coordinate on the same line and
provides the context for the coordinate.
G 3.3.1.6 The platform edge point in table 2 refers to a notional point where a line projected
upwards from the tightest platform point intersects with a line projected horizontally
from the platform surface at its extent. This is effectively ‘squaring off’ the platform
coping stone.
Rationale
G 3.3.2.4 These requirements enable the coordinate data to be interpreted and used by
software in gauging compatibility assessment.
Guidance
G 3.3.2.5 In a single track file the first two lines of coordinates will be rail coordinates, whereas
in a two track file the first four lines of coordinates will be rail coordinates. Table 3
shows example rail coordinates for a two track file.
RSSB Page 17 of 29
Uncontrolled when printed
New document effective 4/09/2021
G 3.3.2.6 Track cant is inferred from rail coordinates. Note that on 1.435 m gauge track, cant is
specified over 1.505 m, being the rail centre rather than the track gauge. Accordingly,
the cant may be calculated using the following formula:
( ) ( (
Cant mm = 1505 × sin tan-1
(Y RH - Y LH )
))
( X RH - X LH )
G 3.3.2.7 It is important to note that the 1.505 m value is based upon a nominal track gauge of
1.435 m and does not vary to accommodate gauge widening, local irregularities in
track gauge or rail wear.
Rationale
G 3.3.3.3 These requirements enable the coordinate data to be interpreted and used by
software in gauging compatibility assessment.
Guidance
G 3.3.3.4 Table 4 shows an example of structure profile coordinates:
Page 18 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
3.4.1 The direction of cant and horizontal curvature shall be identified by means of a plus
(+) or minus (-) sign, with left hand (LH) curves attributed positive and right hand (RH)
curves attributed negative (see figure 2). Adjacent tracks following the same
curvature shall adopt the inverse sign.
3.4.2 The direction of vertical curvature shall be identified by means of a plus (+) or minus
(-) sign, with hogging curves attributed positive and sagging curves attributed
negative (see figure 3).
Rationale
G 3.4.3 These requirements enable the effects of curvature and cant to be correctly
interpreted during gauging analysis.
Guidance
G 3.4.4 In a multi track layout an SC0 file contains structure profile data for more than one
track. On a two track railway a LH curve (+ve) Track 1 would typically be matched by a
RH curve (-ve) on Track 2, providing that both tracks follow the same curvature. This is
illustrated in the example shown in figure 2.
RSSB Page 19 of 29
Uncontrolled when printed
New document effective 4/09/2021
Page 20 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
Appendices
Appendix A Additional guidance for the application of the SC0
file format
A.1 File name
Guidance
G A.1.1 Historically files have had a multi-part file names, originally designed to be
compatible with MS-DOS when the SC0 format was created.
G A.1.2 For the mainline railway, files have been stored in different folders for each
engineer's line reference (ELR). For the purposes of this appendix when references are
made to the structure of the file name "ELR/" represents the folder.
G A.1.3 Files using a mile distance base would have had the following format: ELR/
mmmccytm.SC? where:
• mmm is miles
• cc is chains (Note 80 chains / mile)
• y is yards (0 = 0yds, A = 1 yd, B = 2 yds, C = 3 yds, etc.)
• t is track (see table x)
• m denotes mileage units
• ? denotes file designation (see table 5).
G A.1.4 Files using a km distance base would have had the following format: ELR/
kkkmmmtk.SC?. where:
• kkk is kilometers
• mmm is meters
• t is track (see table 6)
• k denotes km units
• ? denotes file designation (see table 5).
G A.1.5
File designation Description
SCP Platform
SCX Sixfoot
RSSB Page 21 of 29
Uncontrolled when printed
New document effective 4/09/2021
1XXX A Up
11XX B Up Main
11XX C Up Fast
12XX D Up Relief
12XX E Up Slow
13XX F Up Goods
2XXX G Down
3XXX M B-Directional
16XX N Up Bay
X4XX P Platform
15XX Q Up Loop
X5XX S Loop
X8XX T Other
Page 22 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
G A.1.8 National Gauging Database (NGD) file names can include additional information
such as: ELR\TSID-LINE-mmmccytM.SC0 where:
• TSID is the Track Structure ID
• LINE is the Track code (see table 6 ).
G A.1.9 In some circumstances, SCO files with identical names may appear in NGD data.
These will be identified as:
• ELR\TSID-LINE-mmmccytM.SC0
• ELR\TSID-LINE-mmmccytM(1).SC0
• ELR\TSID-LINE-mmmccytM(2).SC0 etc.
Such data may exist if measured at a longitudinal interval of less than 1 yard, or by
error.
Guidance
G A.2.1 Table 7 sets out an example of an SC0 File, which is stored as an un-encrypted,
readable, text file:
• Lines 1 – 17 contain header data
• Lines 18 - 19 contain (single track) rail data
• Lines 20 – 51 contain profile coordinate data.
ID Data
1 VER=5.01
2 NTK=1
4 MODE=SGT LaserFleX2
6 TSID=5461
7 SCAT=Overbridge
8 SSUB=Arched Overbridge
9 ID1=1100
10 DTYP=M
11 DATE=10/05/2016
12 DIST=31.70909
RSSB Page 23 of 29
Uncontrolled when printed
New document effective 4/09/2021
ID Data
13 ELR=AAV
14 LSP1=96.5
15 RAD1=328342
16 TTT1=0
17 NPT=34
Page 24 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
ID Data
Guidance
G A.3.1 Table 8 sets out deprecated mnemonics. These mnemonics have been used
historically, but are no longer used. They are retained here only as information for
backward reference.
RSSB Page 25 of 29
Uncontrolled when printed
New document effective 4/09/2021
Page 26 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
RSSB Page 27 of 29
Uncontrolled when printed
New document effective 4/09/2021
Definitions
Engineer's Line Reference A unique infrastructure reference for a particular section of track.
(ELR) Generally found in the Sectional Appendix or hazard directory.
Track Code A code identifying the specific track e.g. up main.
Mainline railway Mainline railway has the meaning given to it in the Railways and
Other Guided Transport Systems (Safety) Regulations 2006 but
excluding any railway in Northern Ireland; the dedicated high
speed railway between London St Pancras International Station
and the Channel Tunnel.
Deprecated Elements of the data format that are not longer desired, but
retained for information and backward compatibility.
Overhead contact Line Contact line placed above (or beside) the upper limit of the rail
(OCL) vehicle gauge and supplying vehicles with electric energy through
roof-mounted current collection equipment.
Page 28 of 29 RSSB
Uncontrolled when printed
New document effective 4/09/2021
References
The Standards catalogue gives the current issue number and status of documents published by
RSSB: http://www.rssb.co.uk/railway-group-standards.
Other references
RSSB Page 29 of 29