LogoLogo
OS Docs HomeOS NGDOS APIsOS Download ProductsMore than MapsContact Us
  • More than Maps
  • Geographic Data Visualisation
    • Guide to cartography
      • Introduction to cartography
      • Types of maps
      • Symbology
      • Colour
      • Text on maps
      • Generalisation
      • Coordinate reference systems
      • Projections
      • Scale
      • Map legends
      • Map layout
      • Relief representation
      • North arrows
    • Guide to data visualisation
      • Introduction to data visualisation
      • GeoDataViz design principles
      • Types of visualisation
      • Thematic mapping techniques
      • Data visualisation critique
      • Accessible data visualisation
      • Ethical data visualisation
      • Software
      • Data
    • GeoDataViz assets
      • GeoDataViz basemaps
      • Stylesheets
      • GeoDataViz virtual gallery
      • Equal area cartograms
      • How did I make that?
        • Apollo 11 Landing
        • North York Moors National Park, 70 years
        • Snowdonia National Park, 70 years
        • Great Britain's National Parks
        • Great Britain's Islands
        • Great Britain's AONB's and National Scenic Areas
        • Famous shipwrecks of Pembrokeshire
        • Trig pillars today
        • Britain's most complex motorway junctions
      • #30DayMapChallenge
  • Data in Action
    • Examples
  • Demonstrators
    • 🆕Product Viewer
    • Addressing & location demonstrators
      • Address Portfolio overview
      • Which address product should you use?
      • AddressBase
      • AddressBase Core
      • AddressBase Plus
      • AddressBase Premium
      • Address Classifications
      • Addressing Lifecycle
      • OS Emergency Services Gazetteer
      • What are Vertical Streets?
      • Why are there differences in boundaries?
    • Contextual demonstrators
    • Customer best practice
      • Channel Shift
      • Data Management and OS Data Hub
      • End User Licence vs Contractor Licence
      • 🆕 IDs vs Spatial Relationships
      • Why we should capture good quality addresses at source
      • Why we Snap and Trace
    • Network Demonstrators
      • OS Detailed Path Network
      • OS Multi Modal Routing Network
        • OS Multi Modal Routing Network
      • Water Networks overview
      • OS MasterMap Highways Network and OS NGD Speeds
      • OS MasterMap® Highways Network and OS Open Roads™
    • OS MasterMap Generation APIs
      • Using the OS Features API
      • Using the OS Features API Archive
      • Using the OS Downloads API
      • Using OS APIs in ESRI Software
    • 🆕OS NGD (National Geographic Database)
      • OS NGD Address
      • OS NGD Boundaries
      • 🆕OS NGD Buildings
        • 🆕Building and Building Access Feature Types
        • Building Part and Building Line Feature Types
      • 🆕OS NGD Geographical Names
      • OS NGD Land
      • OS NGD Land Cover enhancements
      • 🆕OS NGD Land Use
      • OS NGD Land Use enhancements
      • 🆕OS NGD Structures
        • 🆕OS NGD Structures
        • Field Boundaries
      • 🆕OS NGD Transport Features
      • 🆕OS NGD Transport Network
      • OS NGD Transport RAMI
      • OS NGD Water Features
      • OS NGD Water Network
      • OS NGD API - Features
      • Ordering OS NGD data
      • Change only updates
      • OS NGD Versioning
      • Creating a topographic map from OS NGD Data
      • Analytical styling for OS NGD data
    • OS MasterMap® demonstrators
    • 🆕Product & API Comparisons
      • 🆕Comparison of Water Network Products
  • Tutorials
    • GeoDataViz
      • Thematic Mapping Techniques
      • Downloading and using data from the OS Data Hub
      • How to download and use OS stylesheets
      • How to use the OS Maps API
      • Creating a bespoke style in Maputnik
    • GIS
      • Analysing pavement widths
      • Basic routing with OS Open Data and QGIS
      • Walktime analysis using OS Multi-modal Routing Network and QGIS
      • Creating 3D Symbols for GIS Applications
      • Constructing a Single Line Address using a Geographic Address
      • Creating a Digital Terrain Model (DTM)
      • Visualising a road gradient using a Digital Terrain Model
      • Visualising a road gradient using OSMM Highways
    • 🆕APIs
      • 🆕Using OS APIs with EPC API
      • 🆕OS APIs and ArcGIS
  • Deep Dive
    • Introduction to address matching
    • Guide to routing for the Public Sector
      • Part 1: Guide to routing
      • Part 2: Routing software and data options
      • Part 3: Building a routable network
    • Unlocking the Power of Geospatial Data
    • Using Blender for Geospatial Projects
    • A Guide to Coordinate Systems in Great Britain
      • Myths about coordinate systems
      • The shape of the Earth
      • What is position?
        • Types of coordinates
        • We need a datum
        • Position summary
      • Modern GNSS coordinate systems
        • Realising WGS84 with a TRF
        • The WGS84 broadcast TRF
        • The International Terrestrial Reference Frame (ITRF)
        • The International GNSS Service (IGS)
        • European Terrestrial Reference System 1989 (ETRS89)
      • Ordnance Survey coordinate systems
        • ETRS89 realised through OS Net
        • National Grid and the OSGB36 TRF
        • Ordnance Datum Newlyn
        • The future of British mapping coordinate systems
        • The future of British mapping coordinate systems
      • From one coordinate system to another: geodetic transformations
        • What is a geodetic transformation?
        • Helmert datum transformations
        • National Grid Transformation OSTN15 (ETRS89–OSGB36)
        • National Geoid Model OSGM15 (ETRS89-Orthometric height)
        • ETRS89 to and from ITRS
        • Approximate WGS84 to OSGB36/ODN transformation
        • Transformation between OS Net v2001 and v2009 realisations
      • Transverse Mercator map projections
        • The National Grid reference convention
      • Datum, ellipsoid and projection information
      • Converting between 3D Cartesian and ellipsoidal latitude, longitude and height coordinates
      • Converting between grid eastings and northings and ellipsoidal latitude and longitude
      • Helmert transformation worked example
      • Further information
  • Code
    • Ordnance Survey APIs
    • Mapping
    • Routing with pgRouting
      • Getting started with OS MasterMap Highways and pgRouting
      • Getting started with OS MasterMap Highways Network - Paths and pgRouting
      • Getting started with OS NGD Transport Theme and pgRouting
      • Getting started with OS NGD Transport Path features and pgRouting
  • RESOURCES
    • 🆕Data Visualisation External Resources
Powered by GitBook

Website

  • Ordnance Survey

Data

  • OS Data Hub
On this page
  • What is a Vertical Street?
  • Why do they exist?
  • How do you know if a postcode is in a Vertical Street?
  • How do you join the Vertical Street data?
  • What if you ignore them?
  • What can you do with them?

Was this helpful?

  1. Demonstrators
  2. Addressing & location demonstrators

What are Vertical Streets?

PreviousOS Emergency Services GazetteerNextWhy are there differences in boundaries?

Last updated 1 year ago

Was this helpful?

What is a Vertical Street?

  • “Vertical Streets: A list of polygons for locations that contain more than one postcode, for example, office blocks and flats.” – Code-Point with Polygons – Overview​

  • Vertical Streets are a representation in the Code-Point with Polygons product of things like office blocks or flats where a single building contains more than one postcode​

  • For more information on Code-Point with Polygons please refer to the

Why do they exist?

Vertical Streets can exist for 2 main reasons:​

  • There are too many residential addresses in a building for one postcode so multiple postcodes are required (there are 121 addresses in Green Court shown below)​

  • There are multiple businesses in a building, some of which will have unique postcodes, meaning there are multiple postcodes in a building​

How do you know if a postcode is in a Vertical Street?

The information relating to Vertical Streets is only held in Code-Point with Polygons.

When Code-Point with Polygons is viewed in a GIS all of the Vertical Streets appear as small square polygons (shown in orange here), when they are clicked on they have a ‘postcode’ attribute beginning with V

This a Vertical Street reference and is in three parts.

  • V – denoting a Vertical Street reference

  • A 1 or 2 letter postcode region in this case of the image below it would be E

  • A 5-digit number starting at 00001 in each postcode region and rising sequentially, in this case of one of the postcodes below 00796

  • This makes a reference of VE00796

In Code-Point (show here in blue) the postcodes that form the Vertical Street are all within the building they relate to, sometimes stacked, sometimes spread out, but they do not have a reference back to the Vertical Street polygon they are part of

How do you join the Vertical Street data?

In the data supply for Code-Point with Polygons in the ‘Data’ folder will be a folder called ‘VERTICAL_STREETS’.

This contains a TXT files for each postcode area listing all of the postcodes that are part of Vertical Streets and their associated Vertical Street reference.

In the image below these would be the codes VLU00217 to VLU00224. These show that the Vertical Streets are within the Luton LU postcode area and are numbers 217 through to 224.

These can either be joined to the Code-Point with polygons data in a database or in a GIS, or can be left as a separate look-up table

If joined to the polygons data, then when a user clicks on the Vertical Street polygon in a GIS then the associated postcodes can be identified

What if you ignore them?

As of the July 2022 release of Code-Point with Polygons there are 150,513 Vertical Streets containing 231,864 postcodes. This is ~10% of the postcodes in Code-Point.

These postcodes contain a total of: 3,044,020 residential addresses and 918,401 commercial addresses. This is ~10% of addresses in AddressBase

Ignoring these will then skew any analysis that uses postcode data

What can you do with them?

A lot of recording of ‘events’ is done against postcode. For example, Covid test ordered by postcode. If Vertical Streets are ignored, then this will create gaps in the data and the recording of ‘events’ against postcode when it comes to visualising that data geographically.

The presence of a large number of vertical streets quickly indicates a high density of either businesses or residential properties.

From a resilience perspective, it quickly allows an emergency planner to identify buildings that have a high number of residential addresses or a number of businesses that might need to be evacuated in an emergency.


This content has been developed from what was originally a Lightning Talk PowerPoint slide set. These slides are available to PSGA members to view and download from the

PSGA members area of the OS website
Code=-Point with Polygons section of the OS website​
AddressBase Core shown over OS MasterMap Imagery Layer showing two tower blocks in Luton, one called Green Court
Vertical Street postcode polygons highlighted in orange, Code-Point points in blue
A combination image showing the list of lookup TXT files, a sample of the content and the associated area on a map
Distribution of vertical streets
Page cover image