NR-L2-TRK-3100 Topographical, Engineering, Land and Measured Building Surveying - Strategy & General PDF

Network Rail Standards
Supplementary Information
The following information is associated with Network Rail Standard:

NR/L2/TRK/3100 Issue 1
Additional Content Access

Click the links below to access non PDF related content associated with this
standard.
Word Documents
 NR/L2/TK/3100/SU001
 NR/L2/TK/3100/SU002
 NR/L2/TK/3100/SU003
 NR/L2/TK/3100/SU004
If you have any questions, or need assistance, please contact IHS Support
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Information accessed via the links above is the property of the Copyright holder
IHS Additional Content Page
Copyright Network Rail

Provided by IHS under license with Network Rail Licensee=Colas Rail Limited/1121223091, User=Pike, Nicholas
No reproduction or networking permitted without license from IHS Not for Resale, 02/28/2014 04:03:23 MST
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Date: 4 September 2010
Compliance date: 4 December 2010
Issue record
Issue Date Comments
1 September 2010 First issue.
Compliance
This Network Rail standard is mandatory and shall be complied with by Network Rail
and its contractors if applicable from 4 December 2010.
When this standard is implemented, it is permissible for all projects that have
formally completed GRIP Stage 4 to continue to comply with the Issue of any
relevant Network Rail Standards current when GRIP Stage 4 was reached and not to
comply with requirements contained herein, unless the designated Standard Owner
has stipulated otherwise in the accompanying Briefing Note.
Reference documentation
NR/GN/TRK/3103, Topographic, engineering, land and measured building surveying
– Survey and mapping.
NR/L1/AMG/1010, Policy on working safely in the vicinity of buried services.
NR/L2/AMG/1030, Working safely in the vicinity of buried services
NR/L2/EDT/002, Computer Aided Design drawing specification.
NR/L3/MTC/PL0094, Planning and documenting the Safe System Of Work
Arrangements (formerly NR/PRC/MTC/PL0094).
NR/L3/TRK/3101, Topographic, engineering, land and measured building surveying
– Track.
Benchmarks to GNSS heighting – Virtually level. RICS (Royal Institution of
Chartered Surveyors) Guidance note.
OSGB36. A guide to Co-ordinate systems. Produced by the OS.
Thameslink Programme – Survey and Mapping Grids. CCMS No: N000-PP-
2570926.
Disclaimer
In issuing this document for its stated purpose, Network Rail makes no warranties,
express or implied, that compliance with all or any documents it issues is sufficient
on its own to ensure safe systems of work or operation. Users are reminded of their
own duties under health and safety legislation.
Supply
Copies of documents are available electronically, within Network Rail’s organisation.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Hard copies of this document may be available to Network Rail people on request to
the relevant controlled publication distributor. Other organisations may obtain copies
of this document from IHS. Tel: 01344 328039.
Page 2 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Contents
1 Purpose 5
2 Scope 6
3 Definitions 7
4 Roles and responsibilities 8
5 Planning 9
6 Survey risk management 11
7 Site access planning 13
8 Survey grids 14
9 Deliverables 22
10 GNSS surveys 25
11 Engineering, land, topographical and measured building surveying 26
12 Survey data management and quality assurance 27
13 Setting out 34
14 Site photographs 35
Appendix A Standards hierarchy 36
Appendix B Permanent ground marker types 37
Appendix C PGM data examples 47
Appendix D Railgrid and Snakegrid routes 49
Appendix E Survey report template 50
Appendix F Data derived from terrestrial laser scanning 52
Figure 1 – Standards suite 6
Figure 2 – Project Survey strategy 9
Figure 3 – GNSS example 24
Figure 4 – Conventional traversing example 24
Figure 5 – Six dimensions for bridge abutments 32
Figure A.1 – Standards hierarchy 36
Figure B.1 – Permanent Ground Marker Type 1 (for dense, very stable paved
surfaces) 37
Figure B.2 – Permanent Ground Marker Type 2 (for non-agricultural sites and
unpaved surfaces) 38
Figure B.3 – Concrete PGM 39
Figure B.4 – Example of Concrete PGM 39
Figure B.5 – Example of PGM in OLE mast base 40
Figure B.6 – Example of nail and marker arrangement 40
Figure B.7 – Example of TMG/spigot/stud 40
Figure B.8 – Leica GPH1 prism holder 41
Figure B.9 – Dimensions for spigot arrangement 42
Figure B.10 – “Forced centring” survey pillar 43
Figure B.11 – Example of “Forced centring” survey pillar 43
Figure B.12 – Alternative design of “Forced centring” survey pillar 44
Figure B.13 – Head of “Forced centring” survey pillar 44
Figure B.14 – Example of “Forced centring” survey pillar 44
Figure B.15 – Pillar construction specification 45
Figure B.16 – 14TK400 Instrument Wall clamp (Code: 3604070). 45
Figure B.17 – Demountable Table Mounting System (Code: 0301061). 46
Figure B.18 – Type 8 – BRE Levelling points 46
Figure C.1 – Example of completed PGM Witness Diagram 47
Page 3 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Figure C.2 – Example of GM schedule 48

Figure C.3 – PGM creation method 48
Figure D.1 – Railgrid and Snakegrid routes 49
Table 1 – Example of simple risk register 12
Table 2 – Example of risk management table 13
Table 3 – Survey Grid choices 15
Table 4 – Local scale factor in terms of National Grid Eastings 19
Table 5 – Examples of data types 29
Table 6 – GM verification 31
Page 4 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
1 Purpose
This standard has been written to enable Network Rail to utilise and specify
appropriately all high accuracy (better than ±100mm in position) Topographic,
Engineering, Land and Measured building surveying associated with Track, Building
and Civils, Signalling, Control and Plant, OLE, and Property. Such surveys are not
an automatic requirement for all projects. It specifically excludes ground
investigation, geotechnical, building condition, dilapidation surveys and surveys
associated with Network Rail owned and operated measurement trains.
The standard is intended to provide a clear and unequivocal way to project manager
and specify survey work, by identifying key stages to deliver good quality work to
satisfy current needs and also assist with those for the future. “Survey once and use
many times” thus providing better value for the money spent.
This standard fits with Network Rail policy on sustainability in that it seeks to embed
good sustainability policy and practice into our maintaining, renewing and enhancing
the railway. It also provides guidance and seeks to raise the competency of those
involved with specifying and managing surveying activities.
This is the initial document of a suite of standards that provides a strategy and
general introduction, establishing some basic principles that should be applied
across all disciplines. Further standards have been written covering the main
disciplines for which this form of surveying is utilised. A guidance note
(NR/GN/TRK/3103, Survey and Mapping techniques) has been written that provides
guidance on current techniques and the suitability of their application for the various
stages of the GRIP process. However, consultation with the Senior Survey Engineer
or team or the Project Survey Systems Engineer (Client’s Survey Manager) is
recommended as the technology in use for Surveying is a rapidly changing field of
activity.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
In conjunction with the standard, a number of training courses are being created to
develop the understanding of Topographic, Land, Engineering and Measured
building surveying appropriate for identified needs within Network Rail for Project
management, Contracts and procurement and other parts of the organisation.
The standard seeks to minimise site visits by specifying that all information needed is
collected in an appropriate manner, first time, preventing the need for re-visits and
emissions created by more vehicle traffic and the exposure of staff to further safety
risks. Multiple visits to site may also be limited by better forward planning, especially
when possessions are involved, deriving the most efficient use of time and also
driving down costs.
Network Rail considers that economic sustainability is about exceeding the
expectations of our customers, suppliers, stakeholders and funders. To do this, we
need to exploit the railway asset base more effectively by improving the way data
collected by our surveys is utilised in the corporate asset information systems in
addition to its initial use for projects. This way, Network Rail gets better value from
the investment in good survey information.
Page 5 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Topographic,
Strategy & general (This Engineering, Land and Track surveying
document) Measured Building standard
survey standards
NR/L2/TRK/3100 NR/L3/TRK/3101
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Survey and
mapping
techniques OLE surveying
guidance note standard
NR/GN/TRK/3103 NR/L3/TRK/3105
Civils surveying Commercial

standard Signalling property surveying
surveying standard
NR/L3/TRK/3102 standard
NR/L3/TRK/3106
NR/L3/TRK/3104
Figure 1 – Standards suite

The full hierarchy of the standards is given in more detail in Appendix A.
This standard is intended to be used with the discipline document related to the type
of survey required.
NOTE For example, where a track survey and then a design for S&C renewal is needed, this
standard and NR/L3/TRK/3101 would be consulted to understand what is required. A project survey
strategy would be defined as specified in this standard and the detailed specification would be derived
from NR/L3/TRK/3101.
A value-added benefit of appropriate techniques and standards being used is that of
a digital model of the infrastructure for future use in the corporate asset information
systems is created.
2 Scope
This Network Rail standard specifies all surveying activities for which a co-ordinated
Topographic, Engineering, Land, or Measured Building survey is required. This
standard is applicable to individual project scopes during the life-cycle of a renewal
or project.
It is intended to be used by the Project Manager or Designated Project Engineer
(DPE), in consultation with the Senior Survey Engineer or team or the Project Survey
Systems Engineer (Client’s Survey Manager), to define the most suitable survey
techniques.
This standard is also applicable to commercial remits.
Page 6 of 52
Ref: NR/L2/TRK/3100
Issue: 1
3 Definitions
For the purposes of this standard, the following terms and definitions apply.
Absolute accuracy
accuracy of a measured point related to the reference framework or survey grid.
DTM/DGM
Digital terrain or ground model
computer generated surface representing the surface of the ground from which
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
contours and volumes may be derived.
ETRF89
European Terrestrial Reference Framework
physical realisation of the ETRS fixed to the Eurasian Plate as defined in 1989, the
framework upon which GNSS in Europe works.
ETRS89
European Terrestrial Reference System defining parameters of the origin, scale,
orientation and adopted ellipsoid.
GNSS
Global Navigation Satellites Systems including GPS, Glonass & Galileo.
GRIP
Guide to Railway investment Projects detailing the stages all projects must pass
through
Level Datum
The level obtained directly from GNSS in ETRF89 and converted to OS Newlyn
datum utilising OSGM02 available directly from OS website.
NOTE 1 To achieve compatibility between adjacent ground markers (GMs) they should be
orthometrically levelled.
NOTE 2 OS Benchmarks are no longer maintained.
LiDAR
Light Detection And Ranging
Remote sensing technology that measures properties of scattered light to find range
and/or other information of a distant target using laser pulses. The range to an object
is determined by measuring the time delay between transmission of a pulse and
detection of the reflected signal.
OSGB36/OSNG
The Ordnance Survey grid
NOTE A direct link to it may obtained by using GNSS equipment and “OS Smart Net”.
Primary Control
First Order survey monuments (ground markers) providing the primary planimetric
and vertical control (benchmarks) for the survey
Page 7 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Secondary Control
Second Order ground markers between the primary control.
Survey Grid
Geodetic framework upon which the survey is based.
tertiary control
Third order ground markers, usually trackside, between the secondary control
Terrestrial Laser Scanning

TLS
Survey technique involving the use of a survey grade laser scanning instrument to
collect tens of thousands of measurement points per second and millions of points
per setup by rotation through a 360 degree field of view
NOTE The instrument can be mounted in a fixed position (static) or moving position (kinematic) such
as on a track measurement device.
track measuring device

TMD
Device formerly known as a track trolley, such as Amberg GRP series of track
geometry measurement devices.
TMG/spigot/stud Track machine guidance points

Installed to enable a survey prism to be attached directly.
NOTE These may replace the third order control in some areas. They are usually installed in OLE
masts or other fixed vertical structures.
total station
Combined electronic theodolite and EDM measuring equipment that also includes a
computer for computations and measured data storage.
trig heighting
A technique to obtain the height of a location by measuring the VA (vertical angle)
and SDi (Slope distance) that is computed to get the horizontal distance to the point.
NOTE To obtain best results this should be done from a minimum of two independent instrument set
ups.
TruView
Leica scan cloud publishing and viewing software providing instrument position view
of scan data with reflectivity light image superimposed on co-ordinated points.
4 Roles and responsibilities

Client’s Survey Manager
CSM
HQ Senior Survey Engineer, or Network Rail Survey Systems Engineer or Network
Rail project representative acting as Client’s Survey manager.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Page 8 of 52
Ref: NR/L2/TRK/3100
Issue: 1
5 Planning
5.1 Project Survey Strategy
A Project Survey strategy shall be created by the Project Manager with assistance
from the CSM prior to the commencement of work.
NOTE This is to achieve the integration of all survey and asset information data.
Strategy
GRIP (3- Data Users Survey Data

6)/Planning
Managem’t
Strategy Scope Designers Discipline Acceptance Data

Storage
Accuracy Site access Asset Construct’n Survey Auditing

Maint’ce Methodol’y
planning co- contractors
ordination
Figure 2 – Project Survey strategy

The Project Survey strategy shall be split into the following three sections:
a) Planning for GRIP 3 to GRIP 6 stages;
b) Data Users;
c) Survey Data Management
5.2 Planning for GRIP 3 to GRIP 6 stages

The Planning for Grip 3 to GRIP 6 stages shall include the following, where
applicable:
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Page 9 of 52
Ref: NR/L2/TRK/3100
Issue: 1
a) definition of survey budget associated with the associated risks for each GRIP
phase;
b) sources of any existing survey data for the area in question;
c) scope of survey including survey specification, survey grids, permanent
ground markers (PGMs) to be used and accuracy requirements;
d) strategy for the procurement of the survey and how this fits within the overall
project procurement strategy;
e) definition of the form of tender;
f) the make up of the Tender review team;
g) definition of the commercial/technical scoring spilt. Risks shall be
acknowledged in writing by a Project manager when commercially favourable
bids with limited technical abilities are favoured.
h) Identification of the post to plan and book track access.
NOTE This should be addressed at the earliest opportunity. The last opportunity is T-12
weeks. See clause 8.
i) how the sourcing of buried services records for the project area from Network
Rail Buried services team will be managed, as specified in NR/L2/AMG/1030.
5.3 Data Users

The project strategy shall define the following, where applicable:
a) the additional disciplines involved as well as the main discipline and their data
needs;
b) what the designers for the project shall receive; e.g. Will design for track be
done by Hallade or 3D methods?
c) what the construction contractor shall be provided with and the methodology
we want them to use to enable construction;
d) the data required by the maintainer at the end of the project to enable
maintenance of the infrastructure.
5.4 Survey data management

NOTE The survey is needed for all aspects of a project in a consistent fashion (i.e. property,
engineering, design, maintenance, monitoring, inspection, set-out and installation).
The Project manager shall ensure that survey data is stored in a “data management
system” enabling robust storage, searching and management of the data.
NOTE Such a system is not a document management system designed for Word and pdf documents.
Data shall be prepared in accordance with Network Rail standards, such as
NR/L2/EDT/002.
Survey data management shall include definition of the role of Client’s Survey
Manager (CSM) when applicable. They shall:
Page 10 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
a) undertake quality assurance (QA) checks to verify and validate (accept) the
pre-existing and new survey data. Critical items requiring QA shall be
identified in the project risk register. The degree of QA checks to be
undertaken shall be associated with the project risk register created by the
Project Manager or Designated Project Engineer and updated through out the
course of the project;
b) manage the interfaces between survey suppliers and audit the survey
contractors;
c) be responsible for the on going management, storage, maintenance and
updating of the survey data during the project life cycle, including the hand
back period;
d) take responsibility for managing the survey grid as specified in clause 9.
NOTE An example document for Survey and Mapping grids is from the Thameslink
Programme – Survey and Mapping Grids. CCMS No: N000-PP-2570926. CCMS is Network
Rail’s content management system.
e) manage the longitudinal chainage system.
NOTE For example, when track alignment design is being considered the start point of the
design metreage is required to be defined or, for an OLE survey, a longitudinal chainage may
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
be defined relative to the track ELR and chainage system.
6 Survey risk management

A survey risk register shall be set up by the Project manager or Designated project
engineer with assistance from the CSM.
NOTE 1 The Project manager or Designated project engineer wants a survey that they have
confidence in and, if obvious errors are found, they will lose that. Gross errors can cause
consequential losses on other parts of the project, such as delay and additional costs.
NOTE 2 An example of a simple risk register is given as Table 1. It is not exhaustive and other risks
may be identified.
Page 11 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Cause of risk Consequence Owner Mitigation

CSM to advise on
Delay in programme
Competence and Project manager/ appropriate companies
due to poor
capability of survey Contracts and providing full range of
deliverables from
company procurement services, not only from
multiple suppliers
“Link-up”
Plan 6 months or more
Site Access Delay in programme Project manager ahead and book
possessions
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Use standard
documentation to outlaw
Engineering
inappropriate local grid
Poor specification Surveyor revisit, Delay design
solutions and plan for
manager/CSM
access to allow pre-survey
visit
CSM to advise appropriate
Multidiscipline Engineering
Revisit, Delays and modern survey techniques
scope poorly design
cost overrun that collect all data needed
defined manager/CSM
in one visit
Project manager/ Project survey strategy
Engineering developed to enable
Survey planning Unforeseen costs
design Survey to be part of “whole
manager/CSM life project costs”.
Contract to define if day
Project
Delays and cost rate or fixed price service.
Weather manager/Contracts
overrun Plan work when bad
and procurement
weather least likely
Buried services searches
Project manager/
Permanent ground carried out six months in
Engineering
marker (PGM) Delay advance for site (12 week
design
installations minimum turn round
manager/CSM
needed)
External company
procedures and Network
Gross Errors Revisit, Delay Survey company Rail checking process
See clause 12.
Project manager/
Possible resurvey Project survey strategy
Survey data Engineering
when already defines how this will be
management design
completed done
manager/CSM
Project manager/
Possible resurvey Project survey strategy
Survey data Engineering
when already defines how this will be
management design
completed done
manager/CSM
Table 1 – Example of simple risk register
The approach to risk management shall be applied in a way similar to that for health
and safety issues.
Identified risk and likelihood considered shall be against impact to derive a risk
rating.
Page 12 of 52
Ref: NR/L2/TRK/3100
Issue: 1
NOTE An example of identified risk and likelihood given as Table 2.
Likelihood
Impact
Rating Before/After
Risk Control measure control measure
control measure
Incompetence 4 5 CSM to advise on appropriate companies not 20

of survey 1 5 only from “Link-up” 5
company
Site Access 4 5 Plan 6 months or more ahead and book 20
3 5 possessions 15
Survey 4 4 Project survey strategy developed to enable 16
planning 1 2 Survey to be part of “whole life project costs”. 2
Poor 4 5 Use standard documentation defining survey 20
specification 2 3 grid and plan for access to allow pre-survey visit 6
Multidiscipline 4 4 CSM to advise appropriate modern survey 16
scope poorly 3 3 techniques that collect all data needed in one 9
defined visit
Survey 4 4 Project survey strategy developed to enable 16
planning 1 2 Survey to be part of “whole life project costs”. 2
Weather 3 4 Contract to define if day rate or fixed price 12
2 4 service. Plan work when bad weather least 8
likely.
Permanent 5 4 Buried services searches carried out six-month 20
ground 2 2 in advance for site (12 week minimum turn 4
marker round needed).
(PGM) CAT used on site
installations
Gross Errors 3 5 Company procedures and Network Rail 15
1 2 checking process 3
Survey data 4 4 Project survey strategy defines how this will be 16
management 2 2 done 4
KEY
1 is low, 5 is high.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Table 2 – Example of risk management table
NOTE Application of control measures brings risks down to manageable level. Further control
measures can be needed to address the risk. Such a concept allows focusing on critical aspects of
survey planning
7 Site access planning

At the earliest stage, when it is established that a ground survey will be required, the
Project manager shall consideration the site access requirements as specified in
NR/L3/MTC/PL0094.
Page 13 of 52
Ref: NR/L2/TRK/3100
Issue: 1
NOTE Access to the track to undertake permanent way surveys is strictly controlled and can have a
lead time of six months to enable possessions in a green zone to be booked and arranged. It might be
possible to “piggy-back” another possession, arranged for a different purpose, but careful planning
and consideration of the other planned activities is needed so that these do not prevent the survey
taking place (e.g. storage of materials trains awaiting access to track renewals site) at the location
needed. In some instances, red zone working might be accepted but this cannot be assumed.
8 Survey grids
8.1 Choice of survey grids
NOTE 1 A project grid is important as it enables the curved earth to be mathematically defined as a
plane. A number of variations may be appropriate. The best to use is dependant on the nature of the
project and what other pre-existing infrastructure it is required to interface with.
A project requiring a survey shall utilise one of the following types of survey grids
where applicable:
a) WGS84/ETRF89;
b) Ordnance Survey national grid (OSGB36);
c) bespoke design of Absolute project grid (APG)
d) utilise a pre-existing survey grid (e.g. the London Survey grid (LSG));
e) Local project grid (LPG).
The Project Manager or Designated Project Engineer shall consult with the CSM to
define the appropriate survey grid and longitudinal chainage or metreage to be used.
NOTE 2 A description of these grids is shown in Table 3.
Page 14 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Grid When Comments

WGS84/ETRF89 (see 9.2.1) Establishment of new grid for an Based on GNSS observations
area giving Latitude and longitude
values
Ordnance Survey national grid Allows linking to existing OS Need to apply a Scale factor
(OSGB36) (see 9.2.2) mapping and Nation framework.
Absolute project grid (APG) (see Bespoke grid for specified Example is “Snakegrid” for a
9.2.3) purpose long thin project like a railway
with high accuracy needs and
length greater than 10 Km.
Existing survey grid (see 9.2.4) New project abuts an existing Care needed if grid extended
project with pre-existing grid that additional errors are not
that may be extended introduced as not working from
“whole to part”.
Local project grid (LPG) (see Simple grid that may be based Prudent to alter origin values so
9.2.5) on abridged OSNG values but they are not confused with
with unity scale factor. Use OSNG co-ordinates
when away from areas with
APG.
Table 3 – Survey Grid choices
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
The survey grid shall be defined on the ground by a network of permanent ground
markers (PGMs).
They shall be based on a hierarchy of Primary, Secondary or Tertiary PGMs.
NOTE 3 Once PGMs are defined on the ground, their preservation is essential to maintaining the
absolute accuracy and usefulness of the survey grid.
NOTE 4 Utilising a survey grid which is tied to National Grid monumentation (OSGB36, ETRF89,
LSG) via GNSS surveying provides centimetric reassurance of PGM maintenance and re-
establishment.
NOTE 5 PGM control networks should be sufficiently accurate to facilitate future engineering setting-
out. Only Slab track setting-out requires tolerances of ±2 mm in location.
8.2 WGS84 and ETRF89

8.2.1 General
NOTE WGS84 (World Geodetic system grid 1984) is the world wide co-ordinate grid on which GNSS
measurements are made. However, Global datums such as ITRS and WGS84 are not suitable for
national mapping, as tectonic movements of the Earth’s surface are apparent in these. Britain is
moving at 2 5 mm per year north-east with respect to ITRS. Over a decade such a change would be
significant in national mapping (the difference between ETRF89 and ITRS co-ordinates in Britain in
1999, was about 250 mm). To remove this effect, a fixed epoch GNSS co-ordinate system is used,
ETRF89. This represents all GNSS co-ordinates at the tectonic epoch 1989.0. A transformation is
used to convert WGS84 co-ordinates to ETRF89.
ETRF89 and EUREF is a European 3D reference grid based solely on space techniques
The co-ordinate system that GNSS measures to directly in Europe is set up to be ETRF89.
In day-to-day usage, this grid system shall be converted into one of the following four
grid systems for general usage:
Page 15 of 52
Ref: NR/L2/TRK/3100
Issue: 1
a) OSG36;
b) Absolute project grid (APG);
c) pre-existing survey grid;
d) Local project grid (LPG)
8.2.2 OSGB36
NOTE 1 In the earliest stages of most projects, it is best to utilise the national survey grid, whose
infrastructure is provided by the GB national mapping organisation, the Ordnance Survey (OS). This
enables the use of the mapping and aerial photography data from Network Rail’s service level
agreement with the OS. However, there are limitations to this grid in that it is based on a Transverse
Mercator map projection that introduces a scale factor, depending on how far the location is away
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
from the central meridian (a line running north south). Read 9.2.5 on LPG for a measure of the size of
the Scale Factors introduced. Distances also need to be reduced to mean sea level (MSL). This
means that a distance measured on the ground will not be the same as that measured from a CAD
drawing of the same place.
NOTE 2 For more information on OSGB36, read A guide to Co-ordinate systems, produced by the
OS.
8.2.3 Absolute project grid (APG)

NOTE 1 The limitations of OSGB36 may be overcome by using an Absolute project grid. This is a
bespoke project grid designed for use on a particular project and has carefully defined criteria
allowing its use within a defined area.
An example of this is the “Snakegrid” concept, which may used for any geographically long and thin
project over 10 km in length. This grid has been defined by using an approximate centreline of the
main route, known as a trend line and using bespoke algorithms, which incorporate the effects of
reduction to mean sea level (MSL) and scale factor so that errors will be no greater than 1/50,000 or
20 mm per kilometre (20 ppm). Consequently, all work using such a grid may be computed without
the application of a scale factor or consideration of reduction to MSL.
Such grids have been established for numerous routes (see Appendix D). Levels are based on OS
Newlyn datum and where new work is proposed in these areas these grids shall be utilised to avoid
the confusion of a proliferation of survey grids.
A GNSS control survey shall be carried out to form the main co-ordinate framework
or network.
NOTE 2 GNSS surveys are specified in clause 10.
Initially all control shall be computed using GNSS WGS84/ETRF89 co-ordinates.
Baselines shall also be observed to a minimum of three Ordnance Survey Active
Network GNSS locations to form a gross error check. Rinex data for these three OS
points and precise ephemeris data shall be downloaded and used for post
processing.
Real-time Active net GNSS co-ordination alone shall not be considered suitable for
primary, secondary or tertiary control. For high precision engineering survey
networks (i.e. rail survey or setting out works to sub-centimetre accuracy), GNSS
techniques shall be used as part of a network of permanent ground markers (PGMs).
The network shall consist of a hierarchy of PGMs as follows:
Page 16 of 52
Ref: NR/L2/TRK/3100
Issue: 1
a) Primary – 1st Order: established in pairs, with a good view on to the railway
located with a maximum spacing of 10 Km and a minimum interval of 5 Km;
b) Secondary – 2nd Order: established in pairs, with a good view on to the
railway. The maximum interval shall be 2 Km and the minimum interval for
2nd Order shall be 1 Km;
c) Tertiary – 3rd Order: established as the detailed work progresses often not
using GNSS techniques but conventional total station traversing as detailed in
the Track surveying standard NR/L3/TRK/3101.
For longitudinal track surveys, they shall either:

a) be located at a maximum spacing of 200 m but not less than 100 m apart; or
b) TMGs shall be established in OLE masts (or other stable structures) at a
maximum spacing of 80 m on both sides.
Where TMGs are installed for S&C surveys, they shall be established at a maximum
spacing of 50 m in suitable structures.
NOTE 3 Surveying for TMGs is specified in NR/L3/TRK/3101.
In open ground, a density of at least one permanent ground marker per hectare
(100 m²) shall be provided.
For Aerial survey and LiDAR uses. the Tertiary network shall be related to the “photo
control” to enable the 2D photography or LiDAR data to be related to the survey grid
and turned into 3D digital models.
For safety and security, all primary and secondary PGMs shall be established in
pairs, ideally a minimum 500 m apart and fixed into secure, immovable objects. At
least one of the pair shall have a clear sighting onto the railway.
NOTE 4 In the majority of cases these will be on or next to highway or pedestrian bridges or tunnels.
Survey PGMs shall be located where there is a good view of the sky with no
obstructions (to enable GNSS use).
Primary or secondary PGMs established on OLE mast bases shall not to be used
because of “multipath” issues with GNSS techniques.
NOTE 5 Consideration should be given to surrounding vegetation growth or future land use in urban
areas that could cause obstructions to PGMs.
8.2.4 Use of pre-existing survey grid

Where new work interfaces with an existing survey grid, the new work shall be tied in
to the former work by utilising the survey network set-up as part of the original
project as the Primary PGMs, then creating Secondary and Tertiary PGMs in
locations suitable for use on the new project.
When using an existing grid, the PGMs being used shall be verified on site and
validated.
Details of the pre-existing project grid shall be sought from the CSM of that project.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Page 17 of 52
Ref: NR/L2/TRK/3100
Issue: 1
NOTE An example of this is where the surveys for the Thameslink programme are tied into the
London Survey grid (LSG).
8.2.5 Local project grid (LPG)

NOTE This form of grid is suitable for use within a project area up to 10 km in length.
A GNSS control survey shall be carried out to form the main co-ordinate framework
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
as before.
At an agreed location a grid origin and orientation shall be defined (related to
OSGB36) to give positive co-ordinates and unity scale factor, within the area being
considered.
The CSM shall not accept the use of inappropriate techniques.
EXAMPLE
An example of the application of a local project grid is given as follows
Install and set up survey control ground framework for the site as per requirements for
the topographic survey needs.
Fix the location of a minimum of three permanent grounds markers (PGMs) using GNSS
to provide OSGB36 grid co-ordinate values for three PGMs. The use of OS Smart Net
(accuracy ±20 to 30 mm) is only appropriate to provide a link to OSGB36 and shall not
be used to provide high accuracy PGMs for track works.
“Take out the join” to compute the bearings and OS grid distances between the PGMs
from the Easting and Northing co-ordinates.
One of the PGMs shall be chosen, usually one in the middle of the site, or another by
agreement with CSM and the bearing to one other PGM shall be kept fixed.
A false origin for the local project grid shall be created based on the OS six figure
OSGB36 co-ordinates by removing the first two figures off the Easting and Northing for
the fixed PGM. Then, using the false origin co-ordinates (local project grid (LPG)) and
the fixed bearing to the accepted PGM, compute the co-ordinates of all other PGMs.
To convert from OSGB36 to local project grid, a scale factor needs to be applied. Table 4
shows the local scale factor in terms of National Grid Eastings at 10 Km intervals. 400
Km is the central meridian. The two columns of the National Grid Eastings indicate that
two points the same distance from, but on opposite sides of, the central meridian have
the same local scale factor.
The effects of the reduction of lengths to and from mean sea level need not concern us
here as differences in level are not significant enough over a small site area to require
attention. A height of 1000 ft above mean sea level will produce a difference of one part
in 20,000.
Grid distances from OSGB36 need to be converted into distances on the ground before
they can be used for computations on the local project grid.
Local project grid distance d = OS grid distance D ÷ Scale factor (SF) (1)
Page 18 of 52
Ref: NR/L2/TRK/3100
Issue: 1
National Grid Eastings Local scale factor

400 km 400 km 0.99960
390 410 0.99960
380 420 0.99961
370 430 0.99961
360 440 0.99962
350 450 0.99963
340 460 0.99965
330 470 0.99966
320 480 0.99968
310 490 0.99970
300 500 0.99972
290 510 0.99975
280 520 0.99978
270 530 0.99981
260 540 0.99984
250 550 0.99988
240 560 0.99992
230 570 0.99996
220 580 1.00000
210 590 1.00004
200 600 1.00009
190 610 1.00014
180 620 1.00020
170 630 1.00025
160 640 1.00031
150 650 1.00037
140 660 1.00043
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
130 670 1.00050

Table 4 – Local scale factor in terms of National Grid Eastings
Observed OSGB36 co-ordinates:

PGM1 521,300.000E 191,941.000N
PGM2 521,700.000E 191941.000N
PGM1 to PGM2 Bg = 90º Dist =400 m
To Convert to Local project grid

From Table 4 at 521 km Easting SF is between 0.99978 (520 km) and 0.99981
(530 km).
Scale Factor = (0.1 × 0.00003) + 0.99978 = 0.999783
Page 19 of 52
Ref: NR/L2/TRK/3100
Issue: 1
d = D ÷ SF from equation (1)

d = 400 ÷ 0.999783 = 400.087
Therefore the new PGM values in local project grid are:

PGM1 1300.000E 1941.000N
PGM2 1700.087E 1941.000N
For all Primary and Secondary PGMs, ETRF89 (GNSS), OSGB36 (OSNG) and APG or
LPG grid values shall be derived and included on a co-ordinate schedule.
8.2.6 Level datum

NOTE 1 Ordnance Survey benchmarks throughout the UK have now been superseded by GNSS
derived heights. The RICS (Royal Institution of Chartered Surveyors) Guidance note Benchmarks to
GNSS heighting – Virtually level should be consulted to understand further.
Heights shall be derived by GNSS for primary and secondary PGMs and
transformed to OS Newlyn datum using the transformation OSGM02 or successor
(from OS web-site).
The Post-processing of GNSS surveys shall be required to achieve the maximum
accuracy of derived heights and traceability of survey quality.
Double run levelling shall be undertaken between PGMs with standard levelling
techniques. Comparisons with already published values shall be made and any
discrepancies highlighted and agreement reached with the CSM on the final values
to be used.
NOTE 2 In accordance with good GNSS practice, comparisons to OSBMs, if available in the area,
should also be made and results highlighted to the CSM with differences noted.
NOTE 3 A relationship also exists between OS Newlyn datum and Chart datum, associated with
works around rivers and tidal areas. This relationship should be known and noted on deliverables
when relevant. Other datums have been used in the past such as the “OS Liverpool” datum and in
Scotland the “Caithness” datum, so where a new survey is related to legacy data, care should be
taken to use the appropriate datum.
8.2.7 Accuracy and adjustment of horizontal and vertical control

The primary PGMs shall be designed, observed, calculated and adjusted so that the
direct distance between adjacent PGMs, calculated from the adjusted co-ordinates,
is not in error by more than 1 in 75,000 (13.3 mm per km).
For distances between adjacent primary PGMs of less than 200 m, the maximum
error shall not be greater than ±2 mm.
The secondary PGMs shall be designed, observed, calculated, adjusted and
checked so that the direct distance between adjacent PGMs, calculated from the
adjusted co-ordinates, is not in error by more than 1 in 50,000 (20 mm per km). For
distances between adjacent survey control stations of less than 200 m, the maximum
error shall not be greater than ±3 mm.
The height difference between any two points used as principal survey stations or
other bench marks shall not be in error by more than ±(12√k) mm, where k is the
Page 20 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
distance in kilometres between the points being considered, or ±3 mm, whichever is

the greater.
NOTE For slab track, monitoring or high precision setting-out permanent ground marker networks,
the guidance provided in NR/GN/TRK/3100 should be followed.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
8.2.8 Longitudinal metreage
At the project outset a unique location shall be defined as the origin of the running
metreage or “single line of way”.
The PM and/or DPE shall check that the proposed metreage system is agreed with
the CSM.
NOTE 1 This does not have to start at 0 m and is usually set to be 1000 m or similar.
NOTE 2 For a railway track related design project, a certain rail or the centre line of the down main is
normally used as the reference metreage and this is made to coincide with a clearly defined location
on the ground, that is unlikely to change, such as the start of a tunnel, bridge or other structure.
Mileposts are often destroyed or physically moved during track renewals work, so they are not
suitable.
Using a reference metreage to provide a precise location reference (as opposed to
chainage distance along the line of way) to features which are not on the line of way,
a perpendicular or normal offset distance shall be used.
NOTE 3 On straight track, the position from which to assign the normal offset is clear.
On curved track, the position from which to assign the normal offset shall be defined
as a certain number of metres away.
NOTE 4 This is usually 10 or 20 m to low mileage.
NOTE 5 Historically such offset distances have not been recorded on asset databases or railway
diagrams and schematics (five-mile diagrams, signal schematics, etc.).
NOTE 6 To overcome and quantify the uncertainties with longitudinal chainage references, grid co-
ordinate systems are now being adopted in parallel. For example, the GEOGIS asset database which
records the ELR mileage of an asset also allows the input of a geospatial co-ordinate in OS National
Grid (OSGB36).
NOTE 7 Signal sighting forms now include co-ordinate locations too.
NOTE 8 Five-mile diagrams can also be viewed in parallel with the ELR dataset on the NR GI portal
which is defined in OSBG36.
NOTE 9 The ability of co-ordinate systems to define both chainage distance and location precisely
means these can now be considered the only accurate way to preserve and maintain a chainage
reference system.
8.3 Permanent ground markers (PGMs)
8.3.1 Location and design of permanent ground markers
NOTE 1 Permanent ground markers fall into two different categories:
a) photo control (temporary use) such as corners of manholes or buildings (easily identified from
aerial photography);
b) PGMs to be constructed as survey monuments for longer term use.
Page 21 of 52
Ref: NR/L2/TRK/3100
Issue: 1
All PGMs shall be stable for at least five years after installation. They shall in
protected locations suitable for frequent access.
PGMs shall be used as benchmarks except where located on rooftops.
NOTE 2 Where practicable, PGMs should not be located within 3.0 m of any rail.
NOTE 3 PGM types are shown in Appendix B. The Survey contractor may choose the most
appropriate marker for each location from this selection. Alternative designs may be accepted when
agreed by the CSM.
PGMs shall not be “feno” type markers, which may only be considered as temporary
GMs unless surrounded with concrete.
PGMs shall be a nail in a concrete base, structure or metalled surface unless agreed
with the CSM.
Ground markers shall conform to NR/L2/AMG/1030.
PGMs shall have a precise centring point with an accessible level contact point for
levelling staves.
For PGMs external to Network Rail’s boundary, arrangements shall be made by the
Survey Contractor with adjacent land owners for the construction of PGMs.
The distance between pairs of Primary and Secondary PGMs in the same vicinity
shall be around 500 m, or greater if line of sight is possible.
Each PGM shall be visible from at least two other PGMs at ground level.
NOTE 4 Buried services information requests are specified in NR/L1/AMG/1010. They require a T-12
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
week period for requests for information to be processed.
9 Deliverables
These are all expected to be prepared by the survey contractor.
9.1 Permanent ground marker witness diagram
A PGM witness diagram shall be produced for each PGM unless they consist of a
nail or TMG installed in an OLE base or mast.
The PGM witness diagram shall show its general location with dimensions to at least
three easily recognisable and durable points. These shall use Form
NR/L2/TRK/3100/Witness diagram 01.
NOTE Co-ordinates should be omitted and reference made to the schedule specified in 10.2. This is
so that a new set of witness diagrams does not have to be issued each time updates are often made
to a co-ordinate listing.
9.2 Schedule of permanent survey control stations

A schedule shall be prepared giving the following information in MS Excel format.
a) PGM name/identifier and order in comments (Primary, etc.);
b) ELR and mileage;
c) plan co-ordinates Easting (X), Northing (Y) (ETRF89, OSGB36 and APG or
LPG) and, where new values have been computed, if these supersede
Page 22 of 52
Ref: NR/L2/TRK/3100
Issue: 1
previous values. Details of traverse or other calculations and closures shall be

provided to back this up;
d) level (Z) value;
e) date used;
f) type of PGM, e.g. PK Nail, Brass rivet.
g) comments, e.g. Integrity of point (i.e. stable/unstable, destroyed), not found,
and ease of use.
Information shall also be given about the derivation of the PGM.

NOTE 1 See Appendix C for a GM Schedule example.
The style used shall be that shown in Appendix C, Figure C.2.
NOTE 2 Network Rail aspire that this data should be stored in a data management system, linked
with the witness diagrams to enable this data to be made available to future projects working in the
same geographical area.
NOTE 3 The responsibility for maintaining this information has yet to be identified. This entails not
only the management of the data but also the physical maintenance of the PGMs on the ground.
All information regarding the PGMs (whether new installations or those previously
installed) shall be provided to the CSM.
9.3 Horizontal and Vertical control network diagrams

A schematic or true to scale (TTS) plan in 3D Microstation v8, *.DGN format, shall be
prepared of the control network showing the PGM designation, horizontal and
vertical interrelationship between PGMs.
NOTE Examples are given in Figure 3 for GNSS, or Figure 4 for Conventional traversing. The
traverse diagram may include the distances, angles and reduced level of PGMs.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Page 23 of 52
Ref: NR/L2/TRK/3100
Issue: 1
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Figure 3 – GNSS example
Figure 4 – Conventional traversing example
9.4 Survey report

On completion of the fieldwork and adjustment, a comprehensive survey report shall
be prepared. The survey report shall include:
Page 24 of 52
Ref: NR/L2/TRK/3100
Issue: 1
a) introduction and date survey carried out, including a summary of the planned
and actual programme of work and delivery schedule;
b) scope of survey works and deliverables surveyed from the control. This may
be extracted from the survey remit or brief;
c) a description of the methods, equipment, survey software (capture and
processing), and staff employed on the project;
d) survey difficulties encountered;
e) horizontal and vertical control network diagrams;
f) schedule of PGMs;
g) PGM witness diagrams;
h) description of the method of adjustment of the horizontal and vertical net
including GNSS and Star*Net listing (.txt file) or computations. This shall show
those PGMs held fixed, those allowed to float, residuals, standard errors of
control stations and error ellipses. Confirmation of survey accuracy required
and achieved shall be provided. The input raw survey data shall also be
shown in the listing file;
i) a quality management report describing the procedures used to test the
accuracy, completeness and reliability of data and the results of tests
including an interpretation of results supplied;
j) comments on the specification and results and recommendations for future
work;
k) a screen capture of the folder structure on the suppliers file storage system
related to the survey including a list of all the raw data files generated for the
project;
l) a draft of the report shall be submitted for comment and amendment by the
CSM.
NOTE A template of suggested headings has been included as Appendix E.
10 GNSS surveys
The establishment of Survey PGMs shall be undertaken utilising GNSS techniques
requiring Land Surveying grade GNSS receivers, unless agreed with CSM and
recorded in the Project survey strategy.
NOTE 1 These are Dual frequency receivers capable of receiving signals from GPS, Glonass and
Beidou, Compass, Galileo, or others when available. These are not the same type of receivers used
for the collection of Asset Information for input into a Geographical Information System (GIS).
For PGM surveys, ETRF89 co-ordinates (Observed directly by GNSS receivers)
shall be obtained, unless agreed with CSM and recorded in the Project survey
strategy.
NOTE 2 ETRF89 co-ordinates are then capable of being converted into the project’s chosen survey
grid whereas simple local project grid Cartesian co-ordinates might not be.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`--- Page 25 of 52
Ref: NR/L2/TRK/3100
Issue: 1
11 Engineering, land, topographical and measured building surveying

NOTE Survey grids and PGMs are specified in clause 8. GNSS PGM Control surveys are specified in
NR/GN/TRK/3100.
11.1 Deliverables
The following deliverables listed shall be provided by the survey contractor upon
completion of the survey unless stated:
a) Survey Report, as specified in 9.4. This shall include digital copies of the PGM
list, all Star*net files (*.dat, *.lst and *.prj), network diagrams (*.dgn 3D),
levelling runs with reductions adjustments files (*.xls) and witness diagrams
with photos and location plans (*.jpeg or *.dgn);
b) final electronic survey data files prepared as a full cartographic three-
dimensional string digital ground model in accordance with NR/L2/EDT/002.
The data shall be prepared in sections of no greater than 10 km in length;
c) MX Genio and Land XML v1.1 format output of 3D survey;
d) Where data suitable for input into Laser Rail Clear route software for gauging
and passing clearance assessment is required, it shall be prepared in the form
of *.Sc0 format files;
e) Network Rail reserves the right to request suppliers to provide any data from
raw survey data files collected on site to survey calculations undertaken at
any time and details of any quality assurance (QA) undertaken;
f) site photographs at time of the survey as specified in clause 15.
In relation to laser scan surveys, where undertaken, the following shall apply.
a) All registered point clouds in *.IMP format and supporting databases used to
generate unified and cleaned databases shall be provided. The files shall be
supplied in the same database structure they were created in with consistent
filenames to achieve functioning reference files.
b) All files suitable for publishing on web enabled software such as Leica
Truview, Point tools or other similar software systems shall also be delivered
(image resolution to be 2048 × 2048 and encoding error at 200 m to be
0.04 m).
c) Scan data from TMD mounted or kinematic scanning shall be provided.
d) All registration log files related to scan processing (static and kinematic)
showing control point and cloud to cloud registration residuals shall be
provided.
Network Rail shall have ownership rights to all data generated from scan surveys
and TruView publishing, whether delivered or not by the supplier, including the right
to a free copy of all data for archive and security of access.
Page 26 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Data derived from terrestrial laser scanning shall be as specified in Appendix F.
11.2 Data preparation

The contractor may use survey systems other than Microstation V8 or later to
prepare data, but shall convert that data completely and without omission or
distortion to Microstation V8 or later format in 3D prior to delivery.
To allow survey data validation, data shall also be provided in MX Genio and Land
XML v1.1 format.
The Survey contractor shall self certify data in accordance with Forms A and B, prior
to submission to Network Rail where the data will be examined by the CSM.
NOTE 1 It is expected that Forms A and B will be updated during the lifespan of this standard.
Where other data formats are required (i.e. *.IMP, TruView, 3D models), the supplier
shall confirm the delivery format software required by Network Rail and achieve full
compatibility.
NOTE 2 Network Rail utilises Microstation for all 3D CAD data and updates versions regularly.
The contractor shall be responsible for the costs of maintaining software versions
and formats of deliverables with the current requirements of Network Rail.
12 Survey data management and quality assurance

12.1 General
The CSM shall be responsible for acceptance of digital survey data in the form of
Microstation drawings, MX Models or Land XML v1.1 files as specified in 11.1 and
the completion of the Survey Form A and Form B checklists.
The CSM shall delegate tasks within the checklists to appropriately competent staff
as required.
12.2 Survey shelf-life, Data maintenance and Survey requirements strategy

NOTE 1 All survey data should be assumed to have a “shelf life”. Confidence in the data will diminish
over a period of time as the data becomes older. It is the responsibility of the Project Manager,
Designated Project Engineer or Discipline Engineering Manager, in consultation with the CSM, to
assess if the existing data is appropriate and what kind of quality assurance processes need to be
undertaken, to assure that the data is “fit for the purpose” to which it will be put. The “shelf life” of
survey data might be extended by undertaking a limited resurvey or simple measurements at critical
locations.
For example, a plain line permanent way survey will have a “shelf-life” of a maximum of six months as
the track position can be moved by the passage of trains or, in the worst case scenario, the track
might have been tamped, changing its position. In critical areas, an embargo on tamping might need
to be agreed with the Maintainer.
PGM data has a longer “shelf-life” and can be expected to last a minimum of five years providing it
has been installed in a robust manner, in solid surfaces.
For Signalling or OLE surveys, the accuracy of the survey is not required to be of the same order and,
therefore, the “shelf life” may be extended. However, it is possible to use more accurate data for a
purpose that requires less accurate data, but not vice versa.
Page 27 of 52
--``,,,``,`,````,```,``

Ref: NR/L2/TRK/3100
Issue: 1
Where existing data has been identified as “fit for purpose”, the Project Manager,
Designated project engineer or discipline engineering manager shall put in place
within the Project Survey strategy the identification of additional survey needs, plus
ongoing maintenance and update requirements over the project’s life-cycle, including
the hand back period.
RAG methodology shall be used, i.e.:
• Red: high risk;
• Amber: medium risk;
• Green: low risk.
NOTE 2 The list of data types given in Table 5 is not comprehensive. Table 5 should only be used as
a guide.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Page 28 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Risk
Data type Consequence Checking method Comments
(RAG)
GMs Unable to locate Proving survey and Red Used for whole life of
and overlay audit. project and afterwards.
information from See 13.5.1. Facilitates “joined up
different disciplines thinking” and planning
Platform surfacing Delay and Design Comparison Green Cost implication
and coping rework against other
available data
sources e.g.
imagery
Tunnel walls Clearance Review of survey Red Major additional costs for
infringement data for re survey and re
redundancy of assessment of
observations clearances
Ironwork Design rework Review of survey Amber Some additional costs
data for
redundancy of
observations
Dimension
Foundation Minor rework consistency Green
Dimension
Brickwork/ Design rework consistency Green
blockwork
Earthworks Design rework Use DTM and Green Design checks should
Troughing Re-positioning of compare cross prevent abortive site
new structures to sections for construction works
avoid clashes significant
differences Avoids additional
Green
construction costs
Plain line, S&C Delay and Design Use standard Red Significant additional
alignment rework checking costs
techniques as
Datum plates given in 12.5.2.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Amber
Drainage Delay Derive long Green Ultimately all would give

sections along increased maintenance
drainage runs and costs.
sense check
Formation, Sand Additional materials Costs savings from

or bottom ballast used and likely poor Site checks against reduced materials
design Green needed
track quality
OLE Wiring, Delay and Design Derive long Red Some additional costs
including Height rework sections along wire
and Staggers runs and sense
check
Table 5 – Examples of data types
12.3 Resourcing principles for Quality Assurance (QA)

The survey data shall be provided to the CSM and checked to allow completion of
“Survey Form A” by a Network Rail project representative.
Page 29 of 52
Ref: NR/L2/TRK/3100
Issue: 1
NOTE 1 Further checks require the completion of “Survey Form B” as specified in 12.6, for some
types of data, e.g. data for use with MX or Bentley Railtrack.
Each check form as required shall be pre-certified by suppliers own checks before
provision of the data to Network Rail.
NOTE 2 The CSM should assess the competency of Network Rail project personnel to undertake the
survey checks and provide confirmation of formal delegated authority. Those marked “S” should be
undertaken by a qualified surveyor and those marked “C” by a suitably competent CAD operator.
Other checks will be undertaken by project design consultants utilising the data by superimposing it
over pre-existing data. Each party checks the other’s data by an informal process. Where
discrepancies are found, they should be reported back through the individual project manager to the
CSM so that site verification is initiated.
12.4 Survey QA verification and validation

Proving surveys and quality audits may be carried out by a project representative
and CSM on the Survey contractor or consultant dependant on the risks identified in
the survey risk register.
Risks associated with critical items requiring QA verification and validation shall be
listed in the survey risk register as specified in clause 6.
All field observations, field sheets and edits undertaken on those prior to use,
calculations, digital files, and the order they have been run in shall be retained and a
complete audit trail kept for possible inspection.
Survey contractors shall self certify certain checks with the supply of deliverables.
Some site verification and office data validation shall be undertaken.
NOTE 1 This may involve a resurvey of 10% of existing information in critical areas by a third party
contractor. This is to achieve confidence in the surveys performed by the survey contractors.
Confidence in our suppliers will be built up over a period of time and less verification of data on site
will then be required.
Two forms of QA verification and validation may be needed:
• Prior to design – QA verification and validation of an existing or a new survey;
• Prior to construction of the design – Identifying changes that have taken place rendering the
design in need of updating or the removal of PGMs required for the setting out that need to be
replaced.
Reference to the survey risk register shall inform how the QA verification and
validation is undertaken.
NOTE 2 Issues prior to construction may have an especially significant impact and thereby introduce
major risk to the implementation.
12.5 Survey site verification

12.5.1 GM verification
NOTE 1 Using PGM witness diagrams, the locations of these PGMs will be found and their suitability
verified by completing a PGM Inspection Audit sheet (NR/L2/TRK/3100 Site PGM Inspection Audit
Sheet).
Page 30 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
A sample of 20% shall be verified for the first occasion with a new supplier. After an
appropriate level of satisfaction has been achieved, the sample size may be
gradually reduced to 5%.
NOTE 2 An example is given in Table 6.
Sample Unacceptable No. not to
Verification size
No. of GMs be exceeded before next
Audit No.
% lower level of audit
1 20 20% (4) 2
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
2 20 10% (2) 1
3 20 5% (1) N/A
Table 6 – GM verification
NOTE 3 When a network of survey ground markers has been established, a re-measure of a traverse
leg (angle and distance) and the difference in level between the GMs will provide a check on that part
of the traverse. Ideally, a different process to check the GMs will be used to provide an independent
verification, e.g. when the control network has been established by GNSS, a conventional closed
traverse would be used to verify the results and vice versa.
NOTE 4 As an alternative to the project undertaking a check, in many instances, this data will be
utilised by a third party and their own measurements will provide the assurance that the data is
correct.
12.5.2 Detail survey verification

NOTE 1 A similar concept to that explained for the GM verification should be undertaken for the detail
survey. Over a number of jobs, by the same survey contractor, the degree of verification may be
relaxed if errors are not encountered.
NOTE 2 Using a plot of the site, as required, verification will check the relative locations of points of
detail. Some of this verification may be achieved utilising site photographs and other available data
such as “Omnicom” video survey data and OS Mastermap or Aerial orthophotos (True to scale
imagery). This will provide a means of identifying that the relative position of features appears to be
correct.
Where certain dimensions are classed as “critical” or perceived as “high risk” in the
survey risk register, a site visit shall be undertaken by the CSM or a project
representative to check a proportion of these.
Page 31 of 52
Ref: NR/L2/TRK/3100
Issue: 1
NOTE 3 For instance, the clearance to a structure as derived from a digital ground model or the “six
dimensions” defining the squareness of bridge abutments for an over bridge, as shown in Figure 3.
This is particularly critical when the bridge is a skew structure
Figure 5 – Six dimensions for bridge abutments
12.6 Survey validation

NOTE This exercise concentrates on the survey data provided. Does the data meet the specification
in terms of technical content?
12.6.1 Survey Form A (NR/L2/TRK/3100 Survey Form A checklist)

Low level of technical input needed, e.g. does the deliverable conform to the
specification in terms of:
1. Extents of survey work?
2. Deliverable items specified in scope?
3. Survey grid used?
4. Longitudinal metreage/chainage defined. The datum for start of chainage
system shall be defined?
5. Digital format of deliverable and verification plots?
6. Archiving of record copy of deliverable?
7. Title sheet, name and survey notation in the correct format and consistent with
Network Rail requirements?
NR/L2/TRK/3100, Survey Form A checklist shall be used to record these checks.

This includes columns for self certification by the suppliers. Only a signed CSM
checked form shall be considered complete.
12.6.2 Survey Form B (NR/L2/TRK/3100 Survey Form B checklist)

12.6.2.1 Acceptance of detail
NOTE 1 High level technical knowledge is needed, e.g. detailed checking of data provided.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`--- Page 32 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Some of these checks shall be carried out by a person deemed competent by the
CSM in surveying, signified by (S). Others shall be carried out by a person deemed
competent by the Project Manager or Designated Project Engineer in the use of
Microstation and or Bentley Railtrack/MX, signified by (C).
NOTE 2 The following items should be reviewed in detail. The number refers to item on Survey
NR/L2/TRK/3100 Survey Form B checklist. Where the nature of the survey is for a different purpose to
a track survey, a similar check sheet should be devised by the project team with assistance from the
CSM. Such checks are the only consistent way of achieving consistent high quality deliverables.
1. Survey control report as defined in Section. (S)
2. Utilities service report (when applicable). (S)
12.6.2.2 Digital survey data

3. Do the drawings conform to NR/L2/EDT/002? (C)
4. Rail survey overlap points provided and shall be checked to show that within
tolerance. Where a separate permanent way, as observed model, giving all strings
before joining, is provided; the Horizontal and Vertical overlap positions for a
minimum of three coincident points on adjacent strings shall be reported off in
Bentley MX or Bentley Railtrack. These shall be analysed to achieve a comparison
accuracy of better than ±5 mm in both plan and elevation. This process shall be
carried out prior to a master string being generated. Then the supplied main model
shall be reviewed at the overlap locations so that a bearing change has not been
introduced over the overlap areas. (C)
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
5. Check survey features using comparison with other available datasets (e.g. OS
Mastermap, Aerial photographs, Aerial mapping).
6. Has the MX Model naming and string labelling convention been complied with?
Some checks of the data provided are dependant on the nature of the survey. (C)
7. Check for Null levels in strings. (C)
8. Check where strings cross or where gaps are present that this is intended and that
the amount of detail is as specified. (C)
9. Check that the models have been appropriately split up according to height. i.e.
High Level and Low level models. High level is to include all bridge details and any
structures over the ground, e.g. Gantries, Buildings, Walls on over line structures.
(C)
10. A check of a ground model may be done by constructing an MX Master
Alignment across typically the longest length of the survey. The model may then be
sectioned based on this alignment to produce cross sections. Review these sections
and consider if there are large variations between adjacent points. Are these
expected? Does the model need amending by transferring strings to the “High level”
model? (C)
11. Produce contours for the ground model and check for errors highlighted by
strange shaped contours (towers or depressions). (C) This is most easily achieved
by producing a DTM.
Page 33 of 52
Ref: NR/L2/TRK/3100
Issue: 1
12. For permanent way surveys, a number of checks may be undertaken in MX and
by outputting the data to MS Excel, to check rail string continuity so that the data is
suitable for use by designers, e.g. check that the rail strings are not made up of a
series of small strings 200 m long. One long continuous string is needed for design.
Where this has been constructed from several smaller strings is the geometry
continuous. Are straights “dog-legged” instead of straight causing a bearing
discontinuity? Use horizontal regression analysis and cant/versine trace as a guide
(12.5 mm either side of the normal). (C)
13. Check survey positions on rails are the appropriate distance apart, e.g. 10 m on
straight and five metres on curve. Are there two points very close together that are
shown by a bearing discontinuity (change of one degree between points, or
excessive changes in gradient greater than 2 degrees between adjacent points,
Absolute gradient greater than 0.025 (1:40)? Minimum point spacing not less than
0.1 m, maximum point spacing not greater than 12 m. (C)
14. Output of the co-ordinates of rail strings into MS Excel enables the gauge
(±10 mm of 1435 mm, >1435 measured in plan) and cant to be easily checked. (C)
15. Does the survey start or end on a transition curve. (C)
16. Where TMGs installed, check position of studs relative to gantry locations or
other supporting structures and report those out of position. Vertical check to check
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
TMGs are correct height above plain of rails.
13 Setting out
NOTE 1 This is when a design of new construction is marked out on the ground in three dimensional
space, for construction implementation. It is also known as “Dimensional control”.
Prior to construction, the PGM network shall be revisited by the Implementation
contractor to verify and validate what was done before and any PGMs that have
been destroyed shall be replaced.
Often the PGMs may be located in areas where construction is to take place, so
suitably located primary construction PGMs shall be installed and co-ordinated in
areas clear of the construction work, unlikely to be damaged by site activities.
NOTE 2 Some have called this the “Iron ring”.
The CSM shall accept the updated PGM framework prior to any construction work
commencing.
NOTE 3 Most of the techniques and equipment used are the same as conventional surveying and
setting out is simply another application of engineering surveying.
NOTE 4 Further details on setting out in the generic form may be found in “Surveying for Engineers”
– Uren & Price or Setting out procedures for the Modern Built Environment – CIRIA publication. For
details specific to a rail project see Survey Setting Out on West Coast Projects - W127-IEN-TR-PRO-
005000.
When specific locations have been set-out using co-ordinates, a record of the “as
set-out” value shall be recorded and compared directly with the “as designed”
location in such a way as to able to be reviewed and signed off by the CSM as a QA
check.
Page 34 of 52
Ref: NR/L2/TRK/3100
Issue: 1
14 Site photographs
NOTE 1 Site photographs are an invaluable aid to understanding a site. They might not be needed
for all surveys. A visit to the site during daylight is necessary for meaningful photographs.
Where site photographs are created, they shall be taken at a defined location, either
using survey grid co-ordinates or ELR and chainage and with the direction facing
being identified (up/down, east/west, facing low mileage direction or in direction of
increasing mileage, etc.).
NOTE 2 A sensible rule of thumb is to always take with back to low mileage and any photo without a
direction indicated shall be assumed thus.
NOTE 3 A useful means of identifying photo locations is to use the OS landline or OS Mastermap of
the site and annotate the photo number at the location and the direction in which the photos have
been taken by an arrow.
NOTE 4 Photographs of the site may form a project survey deliverable.
Page 35 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Appendix A
Standards hierarchy
This standard (NR/L2/TRK/3100) is the first on the left hand side in Figure A.1.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Figure A.1 – Standards hierarchy
Page 36 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Appendix B
Permanent ground marker types
B.1 General
Whenever possible, survey consumables such as ground markers, paint and
fieldbooks shall be sourced by users from sustainable sources. The use of spray
paints and “professional graffiti” shall be kept to an absolute minimum. PGM
materials shall be used that are long lasting.
Ground markers shall be installed as specified in NR/L2/AMG/1030.
NOTE This specifies a prior records search and a CAT scan being undertaken to locate possible
buried services.
B.2 Permanent Ground Marker Type 1
Figure B.1 – Permanent Ground Marker Type 1 (for dense, very stable paved
surfaces)
Page 37 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
B.3 Permanent Ground Marker Type 2
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Figure B.2 – Permanent Ground Marker Type 2 (for non-agricultural sites and
unpaved surfaces)
B.4 Permanent Ground marker Type 3

A rust resistant steel rod, nominal length 20 mm × 1.0 m, centre-punched on top to
form a reference, shall be driven to refusal and surrounded by minimum 450 mm
diameter × 500 mm deep concrete backfill. The top shall be flush with the ground.
A simple arrangement as shown below is suitable for GMs to be stable for two to five
years. Such a GM arrangement is suitable for Tertiary order control surveys
The point may either be a nail, bolt or a pot marked steel pin, set in the concrete.
Page 38 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Figure B.3 – Concrete PGM
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Figure B.4 – Example of Concrete PGM
B.5 Permanent Ground marker Type 4

Permanent Ground Marker (For dense, stable paved surfaces)
A simple “PK” type nail will be needed in such surfaces where the addition of a
coloured washer might invite vandalism.
Page 39 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Figure B.5 – Example of PGM in OLE mast base
Figure B.6 – Example of nail and marker arrangement
B.6 Track Machine guidance point (TMG/spigot/stud) Type 5

For details on installation methods, contact the CSM.
Figure B.7 – Example of TMG/spigot/stud
Page 40 of 52
--``,,,``,`,````,```,```,,``

Ref: NR/L2/TRK/3100
Issue: 1
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Figure B.8 – Leica GPH1 prism holder
Alternative types of TMG points do exist. However, all new installations shall conform
to the dimensions given for the spigot arrangement, in Figure B.9. Tolerance in
manufacture shall be ±0.1 mm. Any variance from this shall be accepted by the
CSM.
a) Centre of prism to prism mount TMG clip on point is fixed at 67 mm.
b) Top of TMG to prism mount TMG clip on point is fixed at 9 mm.
c) The shank length, although previously allowed to be variable, shall be 38 mm
(required for Palas).
d) The diameter of the TMG top to bottom, is 12 mm.
The only exception is the 19 mm TMG mounting nut width that may be another
smaller AF size.
Page 41 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Figure B.9 – Dimensions for spigot arrangement
B.7 Non-OLE Route Pillar Type 6

For Primary or Secondary work or where an accurate first order GM is required for a
construction site, a “forced centring” pillar arrangement shall be used.
The instrument sits on top of the pillar eliminating centring errors.
The 150 mm plastic pipe shall not be made of ribbed drainage pipe and shall be filled
with concrete (not earth). The completed pillar shall be firm and not wobble.
The pipe may be of circular or rectangular cross-section and may be shorter (of the
order of 800 mm above ground level) if it is to be used for mounting datum plates or
TMG/spigots/studs. However, the requirements of relating to the positioning of TMG,
for Pallas use, shall still be satisfied.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`
Page 42 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Figure B.10 – “Forced centring” survey pillar
NOTE Photographs courtesy of West Coast Rugby project and North London Line improvements
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Canyon monitoring project

Figure B.11 – Example of “Forced centring” survey pillar
Page 43 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Figure B.12 – Alternative design of “Forced centring” survey pillar
Figure B.13 – Head of “Forced centring” survey pillar

Note: Screw thread on which to attach the survey instrument or target.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Figure B.14 – Example of “Forced centring” survey pillar
Page 44 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Figure B.15 – Pillar construction specification
Cube of concrete 1.25 × 1.25 × 1.25 m, four 20 mm L-shaped rebar fixed with
cruciform, 250 mm diameter drainage pipe filled with concrete at same time as cube
topped with pillar plate.
Pipe extends above top of cube by between 1.0 m and 1.4 m.
B.8 Type 7 - Demountable tables

Type 7 - Demountable tables should be para bolted to a vertical surface. These
examples are from SCC Catalogue, p. 116. There are significant cost differences
based on stability of the table.
Figure B.16 – 14TK400 Instrument Wall clamp (Code: 3604070).
Page 45 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Figure B.17 – Demountable Table Mounting System (Code: 0301061).
B.9 Type 8 – BRE Levelling points

The shape and design of this bolt may be varied with possible savings to be made
on material of construction, but M10 screw fitting should remain.
Figure B.18 – Type 8 – BRE Levelling points
Page 46 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Appendix C
PGM data examples
The PGM co-ordinate values may be included or reference may be made to a co-
ordinate schedule or listing (when co-ordinates are still to be computed). The level is
assumed to be the orthometric level unless stated otherwise.
Care should be taken that the correct project grid name has been referenced.
Figure C.1 – Example of completed PGM Witness Diagram

--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Page 47 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Method note Verified (Date)

Miles.chains/ Eastings Northings
PGM Id. ELR Line Height Remarks Plan Height Plan Height
yds (Grid) (Grid)
Rivet and
LEC 01 Dec 01 Dec
G7921 79.0462 UM 204679.807 199862.588 110.025 disc in OLE PRE EH
1 07 07
mast base
Rivet and 15
LEC 25 May
G7927 79.0610 UM 204579.304 199979.053 109.529 disc in OLE TR SR June
1 07
mast base 07
Figure C.2 – Example of GM schedule
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Plan Height
Primary point existing co-ords
PRE EH Existing height value accepted
accepted
PRG Primary point fixed by GNSS GNSS Fixed by GNSS observations
Secondary point existing co-ords Levelled from two OS Bench Marks
SDE OBM 2D
accepted by double run
Levelled from two OS Bench Marks
SD Secondary point fixed from primary OBM 2S
by single run
Levelled from one OS Bench Mark
TR Tertiary point fixed form secondary OBM 1D
by double run
Levelled from one Ordnance
FT Fourth order fixed from side shot OBM 1S
Survey Bench Mark by single run
Remote point none occupiable Levelled by double run between
RP DR
fixed by multiple observations accepted values
Levelled by double run between
SR
accepted values
TH Trig heighting
Figure C.3 – PGM creation method
NOTE These abbreviations shall be used with the method note in Figure C2
Page 48 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Appendix D
Railgrid and Snakegrid routes
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
Figure D.1 – Railgrid and Snakegrid routes
Page 49 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Appendix E
Survey report template
Introduction
This should include the Scope of survey works, date survey carried out, including a
summary of the planned and actual programme of work and delivery schedule.
Personnel and Equipment

This should be a description of the survey equipment, surveying software (capture
and processing), and staff employed on the project. This should include details of
difficulties encountered in completing the work, e.g. track access, missing Client
provided PGMs, etc.
Methodology
Survey PGM Network
This should be a description of the methods employed, the numbers of PGMs and
the hierarchy employed covering: Primary horizontal control, Secondary horizontal
control, Tertiary horizontal control and Vertical control network.
Adjustment procedure
This should provide a description of the method of adjustment of the horizontal and
vertical net including GNSS and Star*Net listing (.txt file) or computations (as
provided in an Appendix). This should show those PGMs held fixed, those allowed to
float, residuals, standard errors of PGMs and error ellipses. Confirmation of survey
accuracy is required and achieved. An example of input raw survey data should also
be shown in the listing file.
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
It should include a quality management report describing the Quality assurance

procedures used to test the accuracy, completeness and reliability of data in the
field, during the processing and the results of tests including an interpretation of
results supplied.
Detail Survey
Evidence of track survey overlaps should be given for track surveys.
Deliverables
This should be an explanation and listing of what has been delivered.
Page 50 of 52
Ref: NR/L2/TRK/3100
Issue: 1
Conclusions and recommendations

This should include comments on the specification, results and recommendations for
future work.
Appendices
Client Supplied Fixed Control
Horizontal and vertical control network diagrams (True to scale or schematic)
Least Squares network adjustment Report
Comparison of any GNSS Network with OS Active Ties
Levelling Schematic diagram and Misclosure Reports
Traverse Control Observations, Bowditch Traverse Closures and/or Least Squares
Block Adjustment of Traversing/ TMGs
GNSS Derived Height / Spirit Level Height Comparison
Schedule of PGMs and TMGs
PGM Witness Diagrams
A screen capture of the folder structure of the suppliers file storage system related to
the survey including a list of all the raw data files generated for the project.
Page 51 of 52
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

Ref: NR/L2/TRK/3100
Issue: 1
Appendix F
Data derived from terrestrial laser scanning
NOTE 1 Registered point clouds are the basic deliverable from laser scanned surveys.
Where laser scanning is used for surveying, this shall automatically be considered
deliverable. Where RGB (Red Green Brown) colour registration is used, photographs
shall also be included in the deliverables.
A topographical survey specification shall include the following deliverables as
outputs from the 3D laser scan surveys.
a) registered point cloud data in scanworld, combined and unified database
outputs (*.IMP files);
NOTE 2 This can include RGB (colour) registration.
b) TruView published scan clouds – including index file – in light intensity and/or
colour format. Published TruView images shall have an image resolution of
2048 × 2048 with an encoding error at 200 m of 0.04 m;
c) 3D Wire frame model: a 3D CAD model that simply uses line work to produce
a framework (e.g. the outline of the side of a cube);
NOTE 3 This is the basic CAD requirement for as-built surveys and general arrangement
plans.
d) In addition one of may be required:
1) 3D Surface model: joining lines in a series of blocks to define surfaces e.g.
all the surfaces of a cube given and linked to one another;
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
NOTE 4 This should allow sections and simple floor plans to be constructed.
2) 3D Surface plus model: as with 1) but with the addition of main features
such as doorways, windows, main structural members;
3) 3D Solid Model: the level of detail and accuracy of model in relation to
surveyed features shall be determined on a project by project basis and
location by location where appropriate.
NOTE 4 Solid models are generally more appropriate for design work rather than as-built
detail.
Page 52 of 52
13/07/2010
Version 1
Standards Briefing Note
Ref: NR/L2/TRK/3100 Issue: 1

Title: Topographic, Engineering, Land and Measured building surveying – Strategy and general
Publication Date: 04/09/2010 Compliance Date: 04/12/2010
Standard Owner: Professional Head [Track]
Non-Compliance rep (NRNC): Senior Survey Engineer
Further information contact: Chris Preston Tel: 07515-627050
Purpose: Scope:
This standard is applicable to individual project scopes during the
This document is the first of a suite of surveying standards. It life-cycle of a renewal or project.
provides a strategy and general introduction, establishing some
basic principles that should be applied across all disciplines. Such surveys are not an automatic requirement for all projects.
It is intended to be used by the Project Manager or Designated
The document has been written to enable Network Rail to utilise Project Engineer (DPE), in consultation with the Senior Survey
and specify appropriately high accuracy (better than ±100mm in Engineer or team, or the Project Survey Systems Engineer
position) all Topographic, Engineering, Land and Measured (CSM/Client’s Survey Manager), to define the most suitable survey
building surveying associated with Track, Building and Civils, techniques.
Signalling, Control and Plant, OLE, and Property.
It specifically excludes ground investigation, geotechnical, This standard is also applicable to commercial remits.
building condition, dilapidation surveys and surveys associated
with Network Rail owned and operated measurement trains. Further standards are being published or are being written
The standard is intended to provide a clear way to project covering the main disciplines for which this form of surveying is
manage and specify survey work, provide guidance to Project utilised.
managers and Designated project engineers and seeks to raise
the competency of those involved with specifying and managing
surveying activities.
What’s New:
NR needs to exploit the railway asset base more effectively by improving the way data collected by our surveys is utilised in the
corporate asset information systems in addition to its initial use for projects and the standard facilitates a more consistent approach.
The standard creates a renewals and project role called the Client’s Survey Manager (CSM).
A Project survey strategy shall be developed comprising:

a) Planning for GRIP 3 to GRIP 6 stages;
b) Data Users;
c) Survey Data Management
The strategy also identifies a Survey risk register, defines the Survey grid, PGM hierarchy and Project longitudinal design
chainage/metreage.
Within the standard the Project deliverables are defined including the contents of a Survey Report.
The policy on Survey data management and Quality assurance is set out.
Appendices cover a more detailed look at the Structure of the standards, PGM types, an example of PGM witness diagram and co-
ordinate schedule, routes for which a Snakegrid exists, a Survey report template and notes on data derived from terrestrial laser
scanning (point clouds).
A number of training courses are being created to develop the understanding of Land, Engineering Measured building surveying
appropriate for identified needs within Network Rail.
NR/GN/TRK/3103, (Survey and Mapping techniques guidance note) has been written that provides guidance on current techniques
and the suitability of their application for the various stages of the GRIP process.
Affected documents:
Reference Impact
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---

13/07/2010
Version 1
Briefing requirements: Where Technical briefing (T) is required, the specific Post title is indicated. These posts have specific responsibilities
within this standard and receive briefing as part of the Implementation Programme. For Awareness briefing (A) the Post title is not mandatory.
Please see http://ccms2.hiav.networkrail.co.uk/webtop/drl/objectId/09013b5b80417471 for guidance.
Briefing Post Team Function

(A-Awareness/
T-Technical)
A Senior Programme managers Infrastructure Projects
A Project managers Infrastructure Projects
A Track maintenance Engineers
A Assistant TMEs
A Buried services engrs
A Engineering Mgrs Infrastructure Projects
A Scheme Design Engineers (EE)
A Programme Commercial managers Contracts & Procurement
T Senior Design Engineering and/or Design Asset Management
Managers (CEM/DEMs)
--``,,,``,`,````,```,```,,```,`,-`-`,,`,,`,`,,`---
A Engineering Interface Manager(s) Infrastructure Projects

A Route Asset Managers
T Senior Renewals and Enhancement Engineers Asset Management
(Track)
T Senior Design Engineers / Design Engineers / Asset Management
Senior Project Engineers / Project Engineers
(Track) – irrespective of Function/Team
A Compliance Managers
A Outside Parties Engineers
*NOTE: Contractors are responsible for arranging and undertaking their own Technical and Awareness Briefings in accordance with their own processes and procedure


NR-L2-TRK-3100 Topographical, Engineering, Land and Measured Building Surveying - Strategy & General PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NR-L2-TRK-3100 Topographical, Engineering, Land and Measured Building Surveying - Strategy & General PDF

Uploaded by

Copyright:

Available Formats

Network Rail Standards

The following information is associated with Network Rail Standard:

Additional Content Access

IHS Additional Content Page

Copyright Network Rail

Copyright Network Rail

Copyright Network Rail

Figure C.2 – Example of GM schedule 48

Copyright Network Rail

Civils surveying Commercial

Figure 1 – Standards suite

Terrestrial Laser Scanning

track measuring device

TMG/spigot/stud Track machine guidance points

4 Roles and responsibilities

GRIP (3- Data Users Survey Data

Strategy Scope Designers Discipline Acceptance Data

Accuracy Site access Asset Construct’n Survey Auditing

Figure 2 – Project Survey strategy

5.2 Planning for GRIP 3 to GRIP 6 stages

5.3 Data Users

5.4 Survey data management

Copyright Network Rail

be defined relative to the track ELR and chainage system.

6 Survey risk management

Cause of risk Consequence Owner Mitigation

NOTE An example of identified risk and likelihood given as Table 2.

Incompetence 4 5 CSM to advise on appropriate companies not 20

Table 2 – Example of risk management table

7 Site access planning

Copyright Network Rail

Grid When Comments

8.2 WGS84 and ETRF89

8.2.3 Absolute project grid (APG)

For longitudinal track surveys, they shall either:

8.2.4 Use of pre-existing survey grid

8.2.5 Local project grid (LPG)

National Grid Eastings Local scale factor

130 670 1.00050

Observed OSGB36 co-ordinates:

To Convert to Local project grid

d = D ÷ SF from equation (1)

Therefore the new PGM values in local project grid are:

8.2.6 Level datum

8.2.7 Accuracy and adjustment of horizontal and vertical control

Copyright Network Rail

distance in kilometres between the points being considered, or ±3 mm, whichever is

week period for requests for information to be processed.

9.2 Schedule of permanent survey control stations

previous values. Details of traverse or other calculations and closures shall be

Information shall also be given about the derivation of the PGM.

9.3 Horizontal and Vertical control network diagrams

Figure 3 – GNSS example

Figure 4 – Conventional traversing example

9.4 Survey report

NOTE A template of suggested headings has been included as Appendix E.

11 Engineering, land, topographical and measured building surveying

Copyright Network Rail

Data derived from terrestrial laser scanning shall be as specified in Appendix F.

11.2 Data preparation

12 Survey data management and quality assurance

12.2 Survey shelf-life, Data maintenance and Survey requirements strategy

Copyright Network Rail