Change to DCP messages from the Public DCP Service

The DCP Service header coding will be updated on 2 November 2020.

Friday, 02 October 2020

DCP data flows (tn)

The DCP Service header coding of DCP messages available from the Public DCP Service will be updated to increase the total number of Bytes of the DCP Service header from 86 to 88 Bytes. The change to the new DCP file format is planned for operational release on 2 November 2020. As a result, all DCP messages available on the operational Public DCP Service from 2 November onwards will conform to the new DCP Service header coding with a header of 88 Bytes. Note: DCP messages with a transmission timestamp from before 2 November will still have the old 86 Bytes DCP Service header, even if downloaded after the operational release of the change. This change will allow the processing of HRDCP (High Rate DCP) messages up to the maximum size as per TD 16 - Meteosat Data Collection and Distribution Service.

The DCP messages processed after the implementation of this change will still conform to the coding as described on the Meteosat Data Collection Services (DCS) web page under the section 'How to retrieve data via the internet', with the only change being the increase in the total number of Bytes of the DCP Service header from 86 to 88 Bytes. This increase in total number of Bytes results from an increase in the 'SIZE OF DATA' field from 3 to 5 Bytes. The changes to the DCP Service Header are demonstrated in the following tables, detailing the DCP Service Header coding before and after the change:

DCP Service Header before change.
DCP Service Header after change.

The Public DCP Service offers the option to access and view a display of individual DCP messages. Minor changes to the display of DCP messages on the Public DCP Service will be released together with the change to the new DCP Service Header coding. These are:

  • Additional fields have been displayed to allow the user to view “HRDCP PlatformLength”, “HRDCP SequenceCounter”, “HRDCP EngineeringInfo” and “HRDCP CRC” parameters. These parameters will have a value of zero for SRDCP (Standard Rate DCP) messages.



The change to the DCP Service header coding has been implemented on the validation environment of the Public DCP Service. Users are invited to access the validation environment in order to test their systems prior to the release of this change on the operational environment on 2 November 2020. Users are invited to provide comments to User Service Helpdesk, if they experience any issues on the validation environment.

Demonstrational DCP Extraction Script

A one-off demonstrational DCP extraction script has been prepared by EUMETSAT and can be accessed from our ftp server. The script unzips and decodes the downloaded DCP file and extracts the information into separate files with filename DCP_<ADDRESS>_<DATE>-<TIME>.bin containing the quality record and DCP transmission message. The script works with the new DCP Service header coding only. Before the new DCP file format is implemented on the operational environment, the use of the script can be tested on the validation environment. Note: This script is provided as a one-off demonstration of the DCP messages extraction and will not be maintained by EUMETSAT.

The script call syntax is as follows:

python3 <source folder> <DCP Download File>

For more information, contact our User Service Helpdesk.

We use essential cookies to ensure that we give you the best experience on our website. To analyse website traffic we also use third-party performance cookies. If you are ok with the use of essential as well as non-essential cookies, please select Accept & Continue. Instructions on how to prevent the use of non-essential cookies are available under our Terms Of Use, or simply select Decline Cookies.