Change only updates

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

​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

Comma-Separated Values (CSV) files​

Gitbook: OS NGD data ordering and currency

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!​

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

• Transport Network: 1 month​

• Water Network: 3 months​

• Boundaries Collection: 6 months​

COU files can be empty: 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.​

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 its 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:

OS NGD Documentation Platform | osngd

OS Data HubOrdnanceSurvey

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