Welcome to a searchable version of my Trig Point database. This is a relatively new addition to the website and came about after a couple of email exchanges with people who wanted a way to isolate lists of trig points for specific areas of the country. My original Trig Points table provided some of these (e.g. the Lake District), but I was encouraged to make it more interactive. A fuller recounting of the thought process behind the creation of this resource, is described in this blog post: Foul Weather Alternative.
Although there is a comprehensive search and data modelling page on the Trigpointing.uk website, it doesn't really do what I was trying to accomplish, so I think there's still a place for this resource within the wider trigpointing community. There is also a trig point database resource on the Harold Street website, but again, it doesn't quite match what I was trying to do here.
You can download an Excel spreadsheet containing all the trig point data that make up this database, by clicking the button below.
Select an area from one of the four fields at the top of the panel. Note that selecting both a National Park and an AONB will result in no returns and in general it's best not to select more than one of the top four fields, as you may restrict your results. Only English National Parks and AONBs are identified in the database.
Then you can filter the results using the next four fields in the panel. Select a trig point type (or leave blank for all trig points) and select a specific trig point 'condition' (or leave blank for all conditions).
The Above Ground option will filter all trig points you're likely to have to dig for (such as Berntsens and Buried Blocks). Select [Yes] to avoid packing a spade.
The Visitable option will filter all trig points whose condition is equal to 'Destroyed', 'Possibly Missing' or 'Inaccessible'. Select [Yes] to avoid hunting for trig points that are no longer there!
The final selection will define your sort condition, sort order and the maximum number of results returned. Be careful using [All] in Max Results, it could produce a very big list!
This database uses data taken directly from two main sources: Trigpointing UK and the Ordnance Survey trig point database
Not all trig points extracted from the OS database have height data associated with them. Some have 0m height information. What height data there is, is mainly provided for Triangulation Pillars.
Not all trig points are associated with an OS Landranger map sheet; for example “TP0338 – Revelstoke” is to be found in the TPUK database but is not in the full list of trig points downloaded as part of the Landranger sheets exercise (it should be on Sheet 201). However, it can be found in the OS database if searched by FB Number (S3393).
Height data for trig points in this database is typically only accurate to 10m, this is due to the way the data has been collated and extracted, not in any way due to the accuracy of the OS, which is of course is generally faultless.
Around 5% of Triangulation Pillars have no Landranger map number associated with them. This could be because they are in Ireland or because the pillars are destroyed or even because they are non-typical OS pillars, such as those associated with the Great Glen project.
Allocating countries to trig points is done by a combination of OS National Grid prefix letters (NH, HU, etc) and the Landranger sheet number and as such is not especially accurate where the borders of Scotland and Wales meet those of England. Where a Landranger sheet is available, this more granular data is used to determine the country, however even some Landranger sheets are shared between two countries. In this case a Wales-England or Scotland-England value is entered. In the event of no Landranger sheet number for a trig point, the two digit OSNG prefix is used, which is even less accurate than the Landranger sheet. A similar nomenclature is used here.
The sorting of trig points by hill classification is riddled with inaccuracies. In most cases matching the grid reference of a hill top and the grid reference of a trig point to find a match is impossible at even 100m accuracy (6 digit grid reference). As such I have made a match at the square level (4 digit grid reference), such that if a square contains a trig point and a Marilyn (for example) then the database reflects that as a Marilyn with a trig point, even though the trig point could be on a nearby hill. This method also leads to duplication; so a grid reference with two classified tops (not unusual, especially in particularly hilly areas) will show a trig point on both tops. Time and my data manipulation ability (or lack of it) has led to this compromise approach.
You use this data at your own risk. All data is provided 'as-is' with no accuracy guaranteed.