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 Change Only Update?
  • ​What can I order?​
  • Processing COUs​
  • Processing a COU
  • Example 1​ - Two new pre-build addresses are created in an LLPG
  • Example 2 - One record deleted in an LLPG because it was an error
  • Example 3 - One address updated in LLPG (geometry, attribution or both)
  • Example 4 - A pre-build address becomes live and in-use​
  • Important things to note

Was this helpful?

  1. Demonstrators
  2. OS NGD (National Geographic Database)

Change only updates

A Lightning Talk

What is a Change Only Update?

A Change Only Update (COU) file contains only features that have changed in the feature type since the last version​

The following attributes are used to determine how to process each of the records provided in your Change Only Update files​

  1. Unique Identifier: The unique identifier for the feature type, one of; UPRN, USRN, OSID​

  2. Version Date: This is the date when the feature was last updated in OS product databases.​

  3. Version Available From Date: This is the date when the feature became the latest version and was published to customers.​

  4. Version Available To Date: This is the date when the feature was superseded by an update or ceased to exist.​

  5. Change Type: This is a code list which gives more information about the type of change which has occurred, and in simplest terms can relate to:​

  • INSERTS​

  • UPDATES​

  • DELETES

Change Type
Definition

New​

The feature has been added to Ordnance Survey's master database.​

Moved From A Different Feature Type​

The feature has been updated, resulting in it changing feature type.​

Modified Attributes​

One or more attribute values, excluding the geometry, have been altered.​

Modified Geometry​

The geometry only of the feature has been altered.​

Modified Geometry And Attributes​

The geometry and one or more other attributes of the features have been altered.​

End Of Life​

The feature has been removed from Ordnance Survey's master database.​

Moved To A Different Feature Type​

A feature which has been updated, resulting in it being removed from this feature type and added to another one.​

​What can I order?​

COU Files are only available with:

  • CSV files, not Geopackages

  • A daily or monthly schedule​

  • Unfiltered OS NGD Supplies*

*Filtered Data: An OS Select+Build recipe which has been filtered by attribute values or a Data Package filtered by geographic coverage​

Unfiltered Data: A recipe or data package which has not had any filters applied (attribute or geographic)​

Geopackage files

Initial Supply
Update Options

Daily (filtered / unfiltered)​

Not available​

Monthly (filtered / unfiltered)​

Monthly Full Supply​

Annual (filtered / unfiltered)​

Annual Full Supply (from March)​

Comma-Separated Values (CSV) files​

Daily (filtered)​

Not available​

Daily (unfiltered)​

Daily COU​

Monthly (filtered)​

Monthly Full Supply​

Monthly (unfiltered)​

Monthly COU or Monthly Full Supply​

Annual (filtered / unfiltered)​

Annual Full Supply (from March)​

Processing COUs​

The process to load the COU files will depend on a number of factors based on your own environment and requirements, including:​

**There are two main scenarios that represent either extreme of the feature lifecycle options:​

  • Latest feature view​

  • Full feature Archive

Processing a COU

In the following examples, follow the flow chart down on the left and at each stage the correspondingly coloured tables on the right are the entries in the data tables relating to that stage

Example 1​ - Two new pre-build addresses are created in an LLPG

Example 2 - One record deleted in an LLPG because it was an error

Example 3 - One address updated in LLPG (geometry, attribution or both)

Example 4 - A pre-build address becomes live and in-use​

Important things to note

Automate the process: essential if doing daily!​

  • Transport Network : 1 month​

  • Water Network : 3 months​

  • Boundaries Collection: 6 months​

Child components: These are related tables including; cross reference, date time qualifier and related entities tables. These have no geometry and no ‘Change Type’ attributes. They have a unique id and also the unique reference of the ‘parent’ feature and it’s version date.​

  • related entities table: add_gb_prebuildaddress_altadd​

  • unique id (primary key): alternateaddressid​

  • Parent id (foreign key): uprn & featuretypeversiondate​


Links that may be useful:

PreviousOrdering OS NGD dataNextOS NGD Versioning

Last updated 6 months ago

Was this helpful?

: The update frequency for the different OS NGD collections are not all daily, for example:​

: COU files will contain any changes which have been made to the underlying data within the selected time frequency. If no changes have been made to a selected feature type of your choice, then you will receive a blank COU file.​

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

Database software

What are you loading it into?

Data loading method or software

How are you loading it?

Feature retention and lifecycle requirements**

How much data do you want to keep?

Gitbook: OS NGD data ordering and currency
Currency of OS NGD data
COU files can be empty
PSGA members area of the OS website
🆕
OS NGD Documentation Platform | osngd
Logo
OS Data HubOrdnanceSurvey
Logo
OS Select+Build | OS productsOrdnance Survey
Page cover image
Logo