Data structure
This section describes the structure of the data in grid and contour forms.
Last updated
This section describes the structure of the data in grid and contour forms.
Last updated
The height data is presented as a raster dataset of height values which are calculated at the centre of the pixel. This method of creating the data means that there are no overlaps between tiles nor common values along the edge. Coordinate reference systems for DTMs may be used to calculate the DTM origin and coordinates of individual posts.
Due to local tidal conditions, the height of the mean high and low water mark varies continuously around the coast of Britain. The mean high and low water lines have been derived from our large-scale mapping and assigned constant height values, based on the average for each tile. This average value has been determined from local tide tables. The mean high and low water lines were used as heighted breaklines when creating the grid to ensure that the grid product is consistent with the contour product. This means that there may be a small discrete step in the height of tidal water between adjacent tiles. For areas of permanent tidal water, in the grid, the height of the mean low water has been extended out to the tile edge to ensure that the tile is complete. Heights in the foreshore area are interpolated between the mean high and low water heights.
The contours are presented as polyline and spot height features. The contour lines have been divided into tiles for product supply. The contour values can be viewed and analysed in a GIS.
The terms used for the feature types are drawn from the INSPIRE elevation specification. The draft INSPIRE elevation specification requires height values to be held in an attribute called propertyValue, which has been implemented in the new OS Terrain contour GML. In the shapefile format, the GML feature types and attributes have been followed but with a 10-character limit imposed on shapefile field names, for example, propertyValue is abbreviated to PROP_VALUE.
The contours are named master and ordinary, which are equivalent to index and standard contours in Ordnance Survey’s now withdrawn product, Land-Form PROFILE.
In the contour products, the mean high and mean low water lines have been derived from our large-scale mapping and assigned constant height values, based on the average for each tile. This average value has been determined from local tide tables. Inevitably, this means that there is a small discrete step between adjacent tiles. There are no contours supplied between the mean high and low water lines.
The LandWaterBoundary feature type has an attribute of waterLevelCategory, which has four possible sub-values: meanHighWater and meanLowWater, or meanHighWaterSprings and meanLowWaterSprings for Scotland. This attribution allows their display parameters to be changed to show individual features, as desired.
Spot heights have been created using an algorithm that selects the highest source data point within every enclosed contour. As they are from an interpolated surface of the real world, they cannot be guaranteed as summits or highest points of the feature, but it is intended that, in time, the height source data will be enriched by additional spot height data. The GML data model (available in the OS Terrain 50 Technical Specification) lists the spot height sub-value of spotHeightType, which allows the potential for formSpot, generic, mountainPass or summit to be used in future releases of the product. Currently, all spot height features are attributed as generic.
It is possible that there will be some instances of spot heights recording lower height values than the enclosing contour, but it is likely that these are the result of genuine depressions.
