Every architectural project begins with a question that sounds almost too simple to ask: what is actually there? Before massing studies, before precedent boards, before the first sketch, someone has to establish the site, its edges, its neighbours, its access and its context. In the UK, the answer to that question nearly always starts with Ordnance Survey.
Ordnance Survey (OS), Great Britain’s national mapping agency, maintains one of the most detailed national maps in the world. For architects, its large-scale data is more than a backdrop. It is the drawing that a project grows from, and the evidence that a planning authority uses to understand where a proposal sits. This article looks at how practices use OS data across the early stages of a project, and where its limits are.
What OS large-scale data actually contains
The dataset most architects encounter is OS MasterMap Topography, now delivered through the OS National Geographic Database (OS NGD). Rather than a picture of a map, it is a collection of individual features: every building outline, road edge, kerb line, pavement, path, wall, fence line, watercourse and area of land, each stored as its own object with a classification.
Three characteristics make it useful for design work:
- It is surveyed at large scale. In urban areas, OS captures detail to support mapping at 1:1250, with rural areas captured at 1:2500. That is fine enough to show individual garden walls and building footprints.
- It sits on the British National Grid. Every feature has real-world coordinates, so a base map dropped into CAD is positioned correctly and can be aligned with surveys, aerial imagery and other data.
- It is continually maintained. New buildings and changes to the landscape are added on a rolling basis, so a map ordered today reflects recent change in a way older paper maps cannot.
Stage one: understanding the site
At feasibility stage, a base map answers the practical questions quickly. How large is the plot? How close are the neighbouring buildings? Where does the site meet the public highway? Which way does it face? A practice can measure frontages, check separation distances and test a rough footprint against the boundaries within an hour of receiving the data.
This is also where context begins to shape design. The grain of the surrounding streets, the rhythm of plot widths and the position of nearby buildings all inform how a new building should sit. A good base map shows the site as part of a place, not as an isolated parcel.
Stage two: from map to drawing
Once a project moves forward, most practices want the base data inside their own drawing environment. This is where file format matters. A PDF map is fine for reference, but a vector drawing in DWG or DXF format lets the team work on top of the real geometry.
Well-prepared CAD base maps separate features onto named layers, with buildings, roads, kerbs, water and boundaries each on their own. That makes it easy to switch off what isn’t needed, restyle the base so the proposal stands out, and trace accurate outlines of existing buildings. Many practices now order CAD planning maps online at the start of a job rather than redrawing context by hand, which saves hours and removes a source of error.
Where level changes matter, OS height products add another layer of understanding. Spot heights and contours from OS terrain data give an early sense of slope and drainage before a measured survey is commissioned.
Stage three: planning drawings
When it comes to submitting a planning application, OS mapping becomes a formal requirement rather than a convenience. Local planning authorities expect a location plan at an identified scale, usually 1:1250 or 1:2500, with the application site outlined in red and any other land owned by the applicant outlined in blue. Most also require a block or site plan at 1:500 or 1:200 showing the proposal in relation to the site boundaries.
These plans must be based on up-to-date mapping and carry the correct copyright notice and licence number. Applications using unlicensed or out-of-date maps, or a red line that fails to include access to a public road, are commonly invalidated. For practices handling many small applications, consistent and correctly licensed base maps remove an entire category of avoidable delay.
Where OS data stops, and survey begins
It is important to be clear about what a base map is not. OS data is captured for national mapping, not for construction. It is accurate enough for context, feasibility and planning drawings, but it is not a substitute for a measured topographic survey when detailed design begins.
A topographic survey records exact levels, boundary features, drainage, tree positions and canopy spreads, and details at a precision that national mapping does not attempt. On a tight urban site, or wherever a building sits close to a boundary, the measured survey should take over as the reference drawing. The best workflow uses both: OS data for the wider context and early decisions, and a commissioned survey for the site itself.
Legal boundaries need care too. OS maps show physical features such as walls, fences and hedges, while HM Land Registry title plans show general boundaries. Neither is a definitive legal boundary, so where a design depends on exactly where a line runs, it is worth checking title documents and talking to the client early.
Licensing: the part that is easy to forget
OS data is protected by Crown copyright and database rights. Using it in drawings that are shared or published, including planning submissions, requires an appropriate licence. Buying maps through an OS licensed partner covers this for the use you are buying them for, and the supplier will include the correct copyright statement and licence number on the output.
Reusing an old base map from a previous project, or tracing over a web map, can create both a licensing problem and an accuracy problem. Ordering fresh mapping for each site is usually cheaper than dealing with either.
Conclusion
A base map is the least glamorous drawing in any architectural project, but it is the one every other drawing depends on. Getting it right, with accurate, current, properly licensed OS data in a format the team can actually work with, means that the design conversation can start from what is really on the ground. And in a planning system where small errors can cost weeks, that foundation is worth more than it first appears.
