Preparing for Metop-C data

Metop-C has been placed in same orbit as Metop-A and -B and at equal distance to both platforms, with LT equator crossing at 09:30 UTC, the same as for Metop-A and -B ('tristar' configuration – see Figure 1, left). This platform phasing is the most favourable phasing for LEOP and satellite and instrument and in-orbit verification (SIOV), providing the best margin at the data downlink stations.

During the course of commissioning, and based on early data-user feedback, the decision will be made to either remain in a tristar phasing configuration or to shift Metop-C 180 degrees opposite Metop-B (original A/B configuration) with Metop-A in-between ('trident' configuration – see Figure 1, right).

Once we start to disseminate Metop-C data, you will be able to subscribe via our Earth Observation Portal (EOP).

Watch the Metop-C launch on YouTube

What observations will Metop-C collect?

• Vertical profiles of temperature and humidity in the troposphere, even in the presence of clouds.
• Vertical profiles of ozone concentration, column contents of NO₂, SO₂, CO and other atmospheric constituents, properties of aerosols.
• Imagery and properties of clouds.
• Sea surface temperature, wind at the surface of the ocean and sea ice.
• Soil moisture, vegetation, land surface temperature.
• Measurements of charged particles in the space environment.

What are the main applications of Metop data?

Metop-C data dissemination via EUMETCast Satellite

Metop-C global data are being made available to cal/val partners.

Once operational, they will be available to all registered users from the High Volume Service on Transponder 1.

The information below will help you prepare your EUMETCast reception systems to be ready to receive Metop-C data. Note: TP1 = Transponder 1.

A) DVB reception changes

If your system is ready for reception from the High Volume Service on Transponder 1 (HVS-1), go to section B).

1. Users currently receiving Metop-A/B data (i.e. receiving only the Basic Service on TP1 and not High Volume Service) can simply reconfigure the existing receiver to receive the Basic Service and the High Volume Service, please note that a bigger antenna is needed to receive both services.
2. Please follow the DVB receiver setup guides in the Devices section on the Reception Station Set-up page to configure the receivers for TP1.
3. Linux users that have installed the dvb-eumetcast package using the EUMETSAT provided tar/rpm/deb packages can update to the latest version supporting all EUMETCast services on all transponders using multiple DVB cards or a DVB card with multiple inputs. The latest dvb-eumetcast package is supporting Metop-C channels and is available for download from our ftp site:
   ftp://ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Linux/DVB_devices/Common_Apps/

B) Tellicast client changes to receive Metop-C data on TP1

Metop-C global data will be disseminated on HVS-1 using the following channels:

Tellicast client configuration change: for the users that already receive HVS-1, add to cast-client-channels_hvs-1.ini the following:

Linux configuration file:

[channel]
name=E1H-EPS-1
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-1
tmp_directory=data/tmp/hvs-1

[channel]
name= E1H-EPS-2
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-2
tmp_directory=data/tmp/hvs-1

[channel]
name= E1H-EPS-3
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-3
tmp_directory=data/tmp/hvs-1

[channel]
name= E1H-EPS-5
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-5
tmp_directory=data/tmp/hvs-1

[channel]
name= E1H-EPS-6
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-6
tmp_directory=data/tmp/hvs-1

[channel]
name= E1H-EPS-8
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-8
tmp_directory=data/tmp/hvs-1

[channel]
name= E1H-EPS-10
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-10
tmp_directory=data/tmp/hvs-1

[channel]
name= E1H-EPS-11
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS-11
tmp_directory=data/tmp/hvs-1

Or, alternatively, use a single target directory for Metop-C:

[channel]
name=E1H-EPS*
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/E1H-EPS
tmp_directory=data/tmp/hvs-1

Or, alternatively, add (or use the existing) generic entry for all data on HVS-1:

[channel]
name=*
receive_buffer_size=8000000
target_directory=data/eumetcast/hvs-1/default
tmp_directory=data/tmp/hvs-1

You can use your own directories, but the location of tmp and target directory must be in the same file system.

Windows configuration file looks similar, using the Windows specific tmp and target directories, e.g.:

[channel]
name=E1H-EPS*
receive_buffer_size=8000000
target_directory=\EUMETCast\received\hvs-1\default
tmp_directory=\EUMETCast\tmp\hvs-1

For more information, contact our User Service Helpdesk .

Working with the United States

The EUMETSAT Polar System is Europe’s contribution to the Initial Joint Polar System (IJPS) shared with the National Oceanic and Atmospheric Administration (NOAA) of the United States. In order to provide an enhanced coverage with a higher revisit frequency at mid latitudes, EUMETSAT’s Metop satellites fly in the mid-morning polar orbit while the NOAA JPSS satellites fly in the complementary afternoon orbit.

Global Metop data are acquired twice per orbit, approximately every 50 minutes, at Svalbard, Spitzbergen, and McMurdo, Antarctica, and processed products are delivered approximately two hours after sensing to users worldwide for ingestion in global numerical prediction models.