This website uses cookies. By continuing to use this website you are agreeing to our use of cookies. 


Update Frequency: Not Planned
Latest Data Update: 2014-09-08
Status: Completed
Online Status: ONLINE
Publication State: Published
Publication Date: 2014-08-22
Download Stats: last 12 months
Dataset Size: 187 Files | 71MB


The Kinematic GPS (KGPS) data provide accurate high-resolution locational data of approximately 6400 km of roads in Great Britain using circular and/or linear transect data collected during two fieldwork campaigns (details below) carried out by the Landmap project team in order to validate the various Landmap image and elevation products. When processed, this data yields accurate 3-D coordinates that can be used for quality assessment purposes. Kinematic GPS is a technique used to enhance the precision of standard GPS, using a reference receiver of known location, such as a main road, to make corrections to the standard GPS-determined location yielding centimetre-level accuracy.

The Joint Information Systems Committee (JISC) funded Landmap service which ran from 2001 to July 2014 collected and hosted a large amount of earth observation data for the majority of the UK, part of which was buildings data. After removal of JISC funding in 2013, the Landmap service is no longer operational, with the data now held at the NEODC.

Campaign 1

The first campaign, carried out in September 1999, required the kinematic GPS profiles for a number of pre-defined circular routes. This suited a 'Real-time Kinematic' (RTK-GPS) survey technique in which both GPS code pseudorange and carrier-phase measurements are recorded. This method is capable of yielding sub-decimetre accuracy over short baselines, generally less than 50 km.

The observing schedule was such that the reference receiver was established at a location deemed to be the centroid of the day's route so that the baseline distances from the 'local' reference receiver to mobile receiver would be kept to a minimum preventing the accumulation of distance-dependent errors. The mobile receiver would then be driven along the predefined route recording satellite observations at a rate of 5 Hz. Once the route was completed, the local reference station team was picked up and the entire team prepared to observe the next scheduled loop.

The mobile team covered almost 4,000 miles during the 14 days of the first campaign with the predefined circular routes representing some 2,800 miles (4,506km) of that total.

Campaign 2

The second campaign which took place during May and June of 2000 was geared to a different set of objectives and therefore had an observing schedule different to that of the first campaign. There was a requirement to observe some long GPS profiles that would essentially span a number of satellite-pass strips / several stereo-pair strips permitting some checking of the strip matching procedures using orthorectification techniques.

The establishment of a 'local' reference receiver station alongside each section of these proposed transects would have been too demanding in both time and logistics so an alternative processing approach was decided upon. The observing procedure was identical to that of the first campaign with the exception that the 'local' reference receiver remained in the same location for the duration of the campaign. A high-precision geodetic GPS receiver was established at a point of known co-ordinates at University College London where it collected GPS observations for the 9 days of this second campaign. The mobile receiver was driven along the required profiles recording data at a rate of 5Hz.

The routes followed for this second campaign contained a number of features as requested by the SPOT processing team that would aid them in their orthorectification tasks. One particular request was that a number of crossovers should be performed at major junctions whereby a mile or two of additional observations were taken on the feeder roads for the junction in question. Such manoeuvres provide the processing / imaging team with a greater number of features to identity and refer to as part of their orthorectification quality assessment routines. The nature of the road network in some areas meant that several long stretches of road were retraced or intersected which allowed some error checking.

Citable as:  Landmap (2014): Kinematic GPS (KGPS) data for UK roads. NERC Earth Observation Data Centre, date of citation.
Abbreviation: Not defined
Keywords: Not defined


Previous Info:
No news update for this record
Previously used record identifiers:
Access rules:
Restricted data: please submit an application using the REQUEST ACCESS link for access.
Use of these data is covered by the following licence: When using these data you must cite them correctly using the citation given on the CEDA Data Catalogue record.
Data lineage:

Data collected and prepared by the Landmap team before a copy of the data was obtained by NEODC directly from Landmap.

File Format:
Data are available as shapefiles, which comprise of .shp, .shx and .dbf files. shp - shape format; the feature geometry itself shx - shape index format; a positional index of the feature geometry to allow seeking forwards and backwards quickly dbf - attribute format; columnar attributes for each shape, in dBase IV format Also provided are prj, sbn, sbx and xml files. prj - projection format; the coordinate system and projection information, a plain text file describing the projection sbn and sbx - a spatial index of the features xml - location and other associated information Free software can be used to open shapefiles, such as Quantum GIS (QGIS) or User-friendly Desktop Internet GIS (uDig) (see links on this record). Data are available by day or by campaign. kgps_all_circular and kgps_all_linear files represent all the data for the the first and second campaigns respectively. kgps_dayX where X is a number from 1 to 155 represent the data for a particular day of the campaigns. Days 1 through 13 inclusive represent campaign 1 and days 144 through 155 inclusive represent campaign 2.

Process overview

This dataset was generated by instruments deployed on platforms as listed below.
Output Description


No variables found.

Temporal Range
Start time:
End time:
Geographic Extent

Related parties
Authors (1)