Jump to the following:

By continuing, you agree to the use of cookies by us and third parties, which we use to improve your visit.

Improvements to OS data fulfilment

Additional changes to our order processes

In the light of your feedback and the release of Schema 9, we've improved how you order and receive OS data.

These changes apply to customer orders of:

  • OS MasterMap Topography Layer
  • OS MasterMap ITN – Road Network
  • OS MasterMap ITN – Road Network with Road Routing Information (RRI).

These changes came in to effect when Schema 9 was released, and are detailed below.

1 Changes to files

1.1 Simplifying file names

DVD supply structure:

data folder
doc folder
Label Information.txt

Online ordering (FTP) supply structure:

1234567 folder
ov folder

1.2 Removal of superfluous files

We are no longer supplying the following files:

  • Care_of_Media.pdf
  • mmfeedback.txt
  • mmfeedback.htm
  • newoslogo.jpg
  • Readme.txt

Information currently in the Readme.txt file will now be found on relevant product support pages. The GML summary file will remain unchanged, as will the label information file (provided for DVD orders only).

1.3 Simplified order detail information

Your data order file name remains consistent throughout the OS ordering and delivery process, making it easier to find.

For delivery via DVD:

The ‘Order Index’ and ‘Disc Contents’ files previously supplied are combined into a single ‘Order Details’ text file. The Order Details file gives high level order details such as the online reference and order number and is identical on each DVD applicable to the order. It also lists all the data files delivered in your order and identifies which disc the files are on. For geographically-chunked orders, there is no longer a list of chunks that are not supplied.

For delivery via FTP:

This single new file has replaced the ‘details’ and ‘directory’ files previously supplied. The Order Details file provides high-level order details, such as the online reference and order number, and lists all the data files delivered with your order. For geographically chunked orders, there's no longer a list of chunks that are not supplied.

1.4 Non-geo chunked files

The new fulfilment system is designed to give high levels of performance by using a new parallel-processing technique. As a consequence, a greater number of smaller files may be produced for a given order area. As before, these non-geo-chunked files must be loaded into a database before use.

2. Consistent data file naming

We have changed our ordering system to support the consistent naming of OS data.

For ‘geographically’ chunked data, we have removed the items in red: chunk size; complete, incomplete or empty; and the unique counter from the file extension:


So the new file name includes just order number and tile reference:


For ‘non-geographic’ chunked data, we have removed chunk size from the file extension:


So the new file name includes just order number and tile reference:


3. Feature Validation Data Set (FVDS)

The Feature Validation Data Set (FVDS) lets OS MasterMap users verify their data holdings. It's a list of TOIDs with their corresponding version number and version date. We are improving the way you select and manage FVDS.

If you previously received FVDS with your change-only update (COU) order, you will now receive this data as a separate order, delivered at the same time as your data order.

For new customers, when you initially take out your data contract, you can choose a format that includes FVDS. If you do so, a separate order for FVDS will be supplied.

Any existing customers who wish to receive an FVDS for their existing order will need to edit their holding via OS Orders and choose a format that includes FVDS. A separate order for FVDS will then be supplied.

FVDS files will follow the same naming methodology outlined in the section ‘Consistent data file naming’. The only change to the contents of the FVDS files is the removal of the carriage return (new line) that used to be found at the end of the files.

4. Fixed Grid

Until our system upgrade, your OSMM data was fulfilled using a ‘floating grid’, controlled by your area of interest (AOI) polygon. If you never changed your polygon your data was always supplied with the same 1km references.

However, if you expanded or reduced your AOI, your data supplied would then have probably had a different set of 1 km references. This has long been a source of confusion for some of you. We have now moved to a ‘fixed grid’ that removes this issue and confusion.

Due to this change, the first time you receive your data from our fulfilment system, your 1km references are likely to change. This should not be an issue for you and from then on the 1km references will not change.

If you receive Managed Great Britain Dataset(s) you will notice no grid change or alterations to your current supply.

However, we are including additional coastal/offshore data. So for geographically-chunked orders, additional files will be supplied to include this data.

The new fixed chunking grid might mean that if your order area polygon lines up with edges of the underlying fixed chunk grid, you will also receive chunks for adjacent grid squares. This is because the order area intersects with the extra grid squares, even if only at a point or along a line.

For example, if you loaded a tile list of one 5km tile and this conformed exactly to the same 5km area used to choose the chunks, you could get a maximum of 8 addition chunks adjoining this single chunk. Any feature crossing the boundary would feature in each chunk and require deduplication.

Back to top
© Ordnance Survey 2018