CLOUDMAP - User requirement report

Authors: Hans Roozekrans and Paul de Valk (KNMI)

1. Summary

The aim of this report is to define user requirements of the use of satellite cloud data in operational weather forecasting, numerical weather prediction modelling and climate research. The term satellite cloud data has been used in a wide context and is not specifically related to the anticipated CLOUDMAP products. This approach is chosen to enable an extension of the CLOUDMAP product list in the course of the project anticipating on the user requirements.

At the CLOUDMAP kick-off meeting in November 1997 KNMI presented preliminary and qualitative user requirements of satellite cloud data based on experience within KNMI and from literature.

Operational forecasters need:

Climate researchers need:

These requirements are confirmed and further quantified by the work done by KNMI in the first two years of the CLOUDMAP project. This work included three milestones:

The CLOUDMAP user requirements are collected for three application fields:

2. Operational forecasting

2.1 Summary of information collected

Operational forecasting of clouds relies heavily on the frequent and timely distribution of cloud information. Forecasters consider a high product frequency as mandatory for cloud data. New development of future techniques should have a better performance compared not only to the present cloud products but also better than the available products foreseen in the (near) future.

As a framework for user requirements the specifications for cloud products from MSG will be described here and compared to the requirements as obtained by the questionnaire given in appendix C. The questionnaire was distributed during the CLOUDMAP workshop in Paris (May 26, 1998) and send to the meteorological services in Europe. Both requirements are presented in two tables given here below. Although the tables look very similar the reader may notice that there are differences between the two tables. In table 1 the SEVIRI pixel resolution should be interpreted as a horizontal spatial resolution of about 4 km.

There is an essential difference between table 1 and table 2. In table 1 the requirements are based on an instrument that will be launched in the beginning of the new century. These requirements are balanced between end user wishes and technical and economical feasibility.

Table 1: The description of cloud products derived from MSG.

Product of MSG

Frequency

Timeliness

Resolution

ERROR

Cloud mask

15 min

15 min

SEVIRI pixel

even slight cloud contamination should be detected

Cloud amount

15 min

15 min

SEVIRI pixel

10 % (MPEF)

Cloud types

15 min

15 min

SEVIRI pixel

 

Fog / Stratus

15 min

15 min

SEVIRI pixel

even slight low cloud contamination should be detected

Cloud top height (Nowcasting SAF)

15 min

15 min

SEVIRI pixel

5-10 K

Cloud top height (MPEF)

3 hr

1 hr

3x3 pixels

1K

Cloud thickness

15 min

1-2 hr

SEVIRI pixel

TBD

Layer Precipitable water

15 min

15 min

SEVIRI pixel

15-25 %

Precipitation

15 min

0.5 - 1 hr

SEVIRI pixel

TBD

Cloud motion vector

1 hr

30 min

25 - 100 km

Variable (quality flags)

 

Table 2: Cloud product requirements as derived for operational forecasting from a questionnaire (appendix C) distributed to several meteorological institutes.

CLOUD Product Requirements from Questionnaire:

Freq-uency

(MIN)

Timeliness

Horizontal resolution

Vertical resolution

ErroR

Cloud mask

15-30

asap - 10 min

1-5 km

 

10 %

Cloud amount

15-30

asap - 10 min

1-5 km

 

10-50%

Cloud types

15-30

asap - 10 min

1-5 km

 

10 %

Cloud top phase

15-30

asap - 10 min

1-5 km

 

20%

Fog/stratus

15-30

asap - 10 min

1-5 km

50 - 100 m

5 %

Cloud top height/

temperature

15-30

asap - 10 min

1-5 km

100 - 300 m/

0.5 - 2 K

10-30%

Cloud geometrical thickness

15-30

asap - 10 min

1-5 km

200 - 500 m

100m

Cloud water content

30-60

asap - 1 hr

1-5 km

 

30 40 %

Precipitation

30-60

asap - 1 hr

1-10 km

 

10-40%

Precipitation intensity

60

asap -1 hr

1-10 km

 

10 %

or 2 mm/hr

Cloud motion vector

60

asap - 1 hr

1-5 km

 

20-40%

Whereas the second table is a summary of desired cloud products by operational users without the limitation to a certain observation technique. Still the tables have very similar values in terms of Frequency, Resolution and, Timeliness. One should realise that the respondents work as operational forecasters. Forecasters are well aware of the possibilities and weaknesses of present and (near) future geostationary and polar satellites and may express their wishes according to these possibilities. It also shows that their requirements are realistic in terms of coming technologies.

Comparing table 2 to the table in the questionnaire one notices that the areal coverage category has been dropped. The opinions differed too much to capture them in a single value or range of values for spatial coverage. From the three given categories the global and regional coverage where the ones chosen predominantly.

The forecasting community considered cloud optical thickness, semitransparent flag and contrails maps as less relevant. Therefore they are omitted in table 2. Cloud top pressure and cloud top height both gave similar information. Only cloud top height is represented in table 2 together with cloud top temperature.

2.2 Conclusions

From the two tables we derive a table of user requirements, given in table 3. To accommodate all requirements of the forecasters the lowest boundary values are used. In some cases we compromise between the given boundary values of table 2 as we expect that these values will be applied for NWP model check. NWP model output is hourly so this sets the required frequency. NWP model check also relaxes the required timeliness. The horizontal resolution is comparable to the present resolution of the NOAA-AVHRR. Higher resolutions are of course acceptable but do not have a high priority. Higher vertical resolutions certainly have a high priority. A high vertical resolution for low clouds and fog is very important for aviation meteorology and has therefore a direct economical impact. The latter point is also reflected in the highest value for accuracy in the last column of table 3.

We are aware that there will be questions about technical and economical feasibility's but we choose to reflect the (coming) wishes from the forecast community, which in the future will rely more and more on satellite data.

Table 3: CLOUDMAP user requirements of operational weather forecasting

USER Requirements

Freq-uency

Horizontal resolution

Vertical resolution

Timeliness

ErroR

Cloud mask

15 min

1 km

 

5 min

10 %

Cloud amount

15min

1 km

 

5 min

10%

Cloud types

15min

1 km

 

5 min

10 %

Cloud top phase

15min

1 km

 

5 min

20%

Fog/stratus

15min

1 km

50 - 100 m

5 min

5 %

Cloud top height/

temperature

15min

1 km

100 m/

0.5K

5 min

10%

Cloud thickness

15min

1 km

200 m

5 min

100m

Cloud water content

1 hr

1 km

 

15 min

30 %

Precipitation

1 hr

1 km

 

15 min

10%

Cloud motion vector

1 hr

1 km

 

15 min

20%

Back to summary

3. Numerical Weather Prediction (NWP) models

3.1 Summary of information collected

The use of satellite data by NWP models has three applications each having its own requirements concerning the satellite data:

The last application is part of the job of operational forecasters. Therefore, the requirements concerning this use of satellite data are included in the "operational forecasting" part of this document.

Initialisation of NWP models

Numerical weather prediction is an initial-value problem. Nowadays, the quality of a NWP forecast is directly related to the accuracy of the initial analysis of the Earth-atmosphere system and thus to the availability of an adequate observation system. For many areas (oceans, sparsely populated land areas) the meteorological observation system is by far not adequate mainly due to economical reasons. In fact the situation is getting worse with the reduction of the number of observation stations in the densely populated areas (Europe and USA) in the last decade to reduce costs. With the coming of meteorological satellites the meteorological community has been started research the input of satellite data into the analysis modules of NWP models to fill in the gaps in the conventional observation network. Meteorological satellites provide excellent areal coverage, however the accuracy of the data is not at the same level as the accuracy of the conventional observations. To tackle this problem assimilation schemes and techniques are developed in order to filter satellite data sets before they are used for the model analysis. Studies on the impact of the input of satellite data on the NWP model forecasts all conclude that the level of impact is strongly related to the following aspects of the satellite data set:

The accuracy of the data is of less priority. It is better to initialise a model with up-to-date inaccurate data than with very accurate but old data covering only a small part of the model area.

An example: a study done at KNMI on the impact of the assimilation of ERS-scatterometer wind fields in the HIRLAM model demonstrated the need for high data coverage of the model area. In the first part of the study when ERS-1 data were available the impact of the scatterometer winds was negligible probably due to a bad areal coverage of the ERS-1 data. Later on the launch of ERS-2 enabled during a short period the so called tandem scenario with two satellites in operation. During this period the impact of the scatterometer data use on the HIRLAM forecasts increased significantly due to the much better areal coverage.

It is very difficult to quantify the two mentioned requirements (timeliness/frequency and areal coverage) for cloud products because not much experience on this is available yet. One clue could be derived from the specifications of the MPEF cloud products to be derived from MSG and meant for NWP model initialisation:

Product frequency: hourly

Timeliness: 30 minutes

Areal coverage: full disk

The semi-operational short-range cloud forecasting model of KNMI (MetCast) requires satellite cloud products with the following specifications:

Product frequency: hourly

Timeliness: 10 minutes

Areal coverage: METEOSAT B-format and pixel resolution

Improvement of physical parameterisation of models

The physical parameterisation of NWP models has been worked on intensively in the 1980’s with the aid of coherent and consistent satellite data sets on global radiation and cloud cover. It is believed that this work is mostly finished now and that improvement of the NWP forecasts does not rely on a further improvement of physical parameterisation of models.

New parameterisation schemes might be necessary if the horizontal and vertical resolution of models will be increased in the near future (the increased power of computers allows for this need). The requirements to satellite data to be used for this purpose should focus on the need for spatial and vertical resolution better than the resolution of the model itself. E.g. currently a 5 km resolution HIRLAM is under development. For this work satellite data with a better resolution than 5 km are required. Other important requirements to satellite data in this context are accuracy and independence to additional data. Timeliness, frequency and areal coverage have less priority for this application.

In the CLOUDMAP workshop the use of satellite cloud products in the context of NWP models was addressed several times mostly in relation to the validation of NWP analysis fields.

In relation to the focus of the CLOUDMAP project (concerning the type of satellites used) a few important remarks were made during the workshop:

The CLOUDMAP questionnaire is filled in by two people having NWP model use in mind. However, it is not clear what kind of use they had in mind: model initialisation, validation or development. The answers of the two respondents differ quite significantly. In table 4 their answers are summarised (the ranges indicate the difference in answers).

Table 4: Cloud product requirements as derived for NWP use from a questionnaire (appendix C) distributed to several meteorological institutes.

CLOUD Product Requirements from Questionnaire:

Freq-uency

(min.)

Timeliness

 

(Min.)

Horizontal resolution

(km)

Vertical resolution

ErroR

Cloud mask

15 - 60

1 - 60

1 - 20

 

10 %

Cloud amount

15 - 60

1 - 60

5 - 20

 

10 %

Cloud top phase

30 - 60

10 - 60

5 - 20

 

30%

Fog/stratus

15 - 60

1 - 60

1 - 20

50 hPa

10 %

Cloud top height / temperature

15 - 60

5 - 60

1 - 50

100 m / 3 K

10 %

Cloud geometrical thickness

15 - 60

5 - 60

1-50

50 hPa

?

Cloud water content

30-60

5 - 60

5 - 20

 

?

Precipitation

15 - 60

1 - 60

5 - 20

 

30 %

Precipitation intensity

15 - 60

1 - 60

5 - 20

 

2mm/hr

Cloud motion vector

60

5 - 60

10 - 20

100 - 200 hPa

?

 

3.2 Conclusions

The user requirements of NWP models to satellite data can not be defined as specific as has been done for operational forecasting. The problem lies in the fact that concerning the initialisation of models using satellite cloud products not much experience is available yet (except for the input of cloud motion vectors). Experience with other types of satellite data stresses the need for adequate timeliness, frequency and areal coverage. Accuracy is of less importance. For some products (e.g. cloud motion vectors) the accuracy of the height assignment is an important requirement of NWP models.

Table 5: CLOUDMAP user requirements of NWP model initialisation

USER Requirements

Freq-uency

Timeliness

Horizontal resolution

Vertical resolution

ErroR

Cloud products (in general)

1 hr

<30 min

5 - 10 km

50 - 100 hPa

N/A

The added value of the use of satellite cloud products for parameterisation of the models has been proved in the past and is still valid in relation to the development of high(er) resolution models. Again it is difficult to quantify requirements to the data concerning this type of use. In research environments requirements to data are in most cases not existent. The device is that all data in any form at any time are valuable. High accuracy of the data can be a requirement but synergy with other data (by interpolation, simulation, calibration, etc.) may solve the problem of inaccurate data in many cases. Timeliness is not an issue in this matter.

Back to summary

4. Climate research

4.1 Summary of information collected

The role of clouds in controlling the radiation budget of the Earth’s climate system is believed to be large. The investigation of this role involves the study of many complex dynamic and thermodynamic processes. These studies require global data sets of cloud observations with adequate spatial and temporal resolution. Satellites can only fulfil this requirement. This is one of the motivations of the CLOUDMAP project. The CLOUDMAP project is one of the many efforts to promote the use of satellite cloud data in climate research. Therefore, KNMI has searched literature to find information on other projects in which user requirements of climate research have been collected.

Long before the CLOUDMAP project the International Satellite Cloud Climatology Project (ISCCP) was started in 1983 in the framework of the World Climate Research Programme (WCRP). ISCCP aimed at a production of a 5-year global data set of cloud parameters derived from satellite data (METEOSAT, GOES, GMS, NOAA-AVHRR). The main object of the production of the global cloud data set was to contribute to an improved parameterisation of clouds in climate models. The ISCCP data set includes 30-day averages of cloud parameters for a 5-year period and is available on IBM tapes for scientific purposes. The ISCCP product specifications are listed in table 6. These numbers may give indications of what cloud information is needed in climate research.

Table 6: ISCPP product specifications

CLOUD Product Requirements from Questionnaire:

Freq-uency

Horizontal resolution

Vertical resolution

ErroR in

30 day averages

Total Cloud amount

3 hr

250 x 250 km

1 km

3 %

Cirrus Cloud amount

3 hr

250 x 250 km

1 km

5 %

Middle Cloud amount

3 hr

250 x 250 km

1 km

5 %

Low Cloud amount

3 hr

250 x 250 km

0.5 km

5 %

Deep Convective Cloud amount

3 hr

250 x 250 km

1 km

5 %

Cloud top temperature

of each cloud category

3 hr

250 x 250 km

1K

1 K

In the CLOUDMAP workshop the following remarks relevant for climate research were made:

The CLOUDMAP questionnaire was filled in by five respondents all aiming at the use of satellite data in climate research. Again the answers differ significantly and in table 7 the answers are summarised indicating a range of requirements.

Table 7: CLOUDMAP user requirements of climate research.

CLOUD Product Requirements from Questionnaire

Freq-uency

Horizontal resolution

Vertical resolution

ErroR

Cloud mask

1-3 hr

1-50 km

   

Cloud amount

1-3 hr

1-50 km

 

10-50%

Cloud types

1-3 hr

1-50 km

   

Cloud top phase

1-3 hr

1-50 km

 

10%

Fog/stratus

1-3 hr

1-50 km

   

Cloud top height/ pressure/ temperature

1-3 hr

1-50 km

100-500 m/ 50hPa/0.5K

10-30%

Cloud geometrical thickness

1-3 hr

1-50 km

500 m

500m

Cloud water content

1-3 hr

1-50 km

 

20%

Precipitation

5 days

1-50 km

 

cumulated /5mm class

Precipitation intensity

1-3 hr

1-50 km

 

3 Classes

Cloud motion vector

1-3 hr

1-50 km

   

Some parameters are omitted in accordance with the forecast table 2. Climatologists are interested in a global coverage of the earth. They are also interested in some classes of cloud particles with a distinction in size and shape.

4.2 Conclusions

Similar to NWP R&D (and research in general) it is difficult to define unambiguous user requirements for satellite data use in climate research. The way of using the data is determining the accents of the requirements:

A quantification of the different requirements is hardly possible. Table 7 shows the large ranges of requirements defined by climate researchers addressed until now.

Back to summary

APPENDIX A: Report on the 1e CLOUDMAP "user requirement" workshop

Date: May 26th 1998

Venue: UNESCO building in Paris, France

Setting and scope of workshop:

The first user workshop of the CLOUDMAP project was held in Paris, France. The venue was chosen as it coincided with the AMS/EUMETSAT Conference. At this conference many anticipated end-users were brought together providing an excellent occasion for a user workshop. This first CLOUDMAP user workshop was focused on all three anticipated uses of satellite cloud data (nowcasting, numerical weather prediction and climate research). The aim of the discussion part was to get feedback from the audience on their opinion on the use of satellite cloud data in general and of CLOUDMAP products in particular.

Programme:

11.30-11.35 Introduction to aims of workshop: Hans Roozekrans

11.35-12.00 Presentation of CLOUDMAP products: Jan-Peter Muller

12.00-13.00 Discussion using prepared statements

13.00-13.02 Handing out the user requirement questionnaire

Participants list:
(The initials in brackets are used in the discussion part of this report to identify persons who took part in the discussion. The comments made by the individual participants are not verbatim represented in this report and should not be treated as official). Ewen McCallum (UKMO): forecaster (EM)
Adam Dybbroe(SMHI): R&D (AD)
Frans Debie (KNMI): forecaster (FD)
Sylvia Barlag (KNMI): R&D (SB)
Antoine Zelenka (SMI): climate researcher (AZ)
Natasa Strelec Mahovic (MHS Croatia): forecaster (NS)
Wolfgang Benesch (DWD): climate researcher (WB)
George Pankiewicz (UKMO): numerical modeller (GP)
Michel Desbois (LMD, CNRS): climate researcher (MD)
Genevieve Seze (LMD, CNRS): climate researcher (GS)
Tor H. Skaslien (DNMI): forecaster (TS)
Rose Dlhopolsky (KNMI): climate researcher (RD)
Hans Peter Roessli (SMI): forecaster (HPR)
Frederic Parol (LOA/USIL): climate researcher (FP)
Fritz Hasler (NASA/GFSC/USA): R&D (FH)
Michel Schouppe (representative of EC/DG XII D-4) (MS)

Cloudmap partners present:
Peter Mueller (UCL) : CLOUDMAP co-ordinator (JM)
Hans Roozekrans (KNMI) (HR)
Paul de Valk (KNMI) (PV)
Richard Meyer (DLR-IPA) (RM)
Juergen Fischer (FUB) (JF)
Rene Preusker (FUB) (RP)
Lothar Schueller (FUB) (LS)
Manos Baltsonias (ETH) (MB)

Discussion report:

As a reaction to the presentation of Jan-Peter Muller the participants raised a number of questions.

EM: What new things is CLOUDMAP bringing?

JM: The ability to characterise multi-layered clouds and to distinguish cloudy pixels contaminated by cirrus clouds. Another CLOUDMAP feature is the ability to derive cloud top parameters without the need for additional data sources (e.g. NWP data).

GP: What is the time difference between the images used for stereoscopy?

JM: 7 minutes for the extreme viewing angles and smaller than 4 min for the intermediate viewing angles.

GP: The low frequency of observation renders the products as not very useful.

FD: We have an interest in the thickness of the cloud layer.

JM: We can not obtain a cloud thickness layer from satellite data.

The discussion was further guided by eleven statements (bold printed):

1: For the purpose of cloud information improvement of satellite data should primarily focus on: horizontal resolution or vertical resolution or temporal resolution?

WB: All three items are linked and therefore should not to be distinguished. The question should be raised: What is the continuity in the future for the data? Which data will be available on a long term for all application fields? Vertical resolution is relevant for cloud top, cloud base and layered clouds.

HPR: The goal is knowledge about the 3D/4D distribution of the clouds. The cloud base is relevant as it is linked to visibility.
In the future there will be a data set available from the MAP campaign including rapid scans and stereoscopy imagery (obtained from METEOSAT 6 and METEOSAT 7).

General impression: Forecasters prefer operational satellites like METEOSAT Second Generation (MSG) and EPS as they guarantee data continuity.

2: Users require satellite cloud products which are independent on additional (e.g.: NWP model) data for interpretation.

WB: Yes, for a combination of data sources to control and improve NWP performance.

EM: Yes, to see where the NWP models fail. The forecaster's task is to add value to the NWP model by including extra information (e.g. satellite imagery) to obtain a conceptual model of the weather.

3: Given the choice what would you prefer?:

NS/FD: Primarily height (m or hPa) related to temperature.
This supplies an extra check on NWP output to improve the forecast.

4: Which are important cloud types to be classified?:

EM: Primarily Stratus and fog. They have an important economical impact.

HPR: Of second order importance is Cirrus: for its impact on temperature and radiance balance

MD: Cirrus and low Stratus. Stratocumuli in tropical zones affect the radiation budget. Convective systems are relevant for e.g. vertical transport.

GP: Presently missing are low Stratus and Cirrus.

5: Contrails are relevant for?:

All: They are not relevant for forecasting.

GP: They are not required for NWP models

WB: They are valid for climate monitoring (on longer time scales)

6: Cloud particle size distribution is important for?:

All: Cloud shape is seen as more important. It has an effect on the radiation budget.

WB: Sizes are relevant for aircraft icing.

FD: Sizes larger than 10 mm are relevant for precipitation recognition.

7: Cloud opacity is important for?:

NS: Is not relevant for forecasting.

AZ: It is relevant to monitor long term climate changes. It is relevant for climate research.

All: The question was raised if it was relevant as NWP model input? This is not known.

8: Cloud top particle phase is relevant for?:

FD: Is relevant for aviation.

GP: Is relevant for validation of NWP output.

9: Precipitation information from satellite data?:

EM: Can you do that?! A good quality has to be assured.

GP: It can be used to study if the physics in NWP models is correct (GP has a poster at the Conference in which satellite data and radar data are linked to each other using a neural network). Concentrate on the tropics, the mid-latitudes are difficult.
There are new methods using microwave and IR imagery to derive precipitation information.

WB: We provide monthly averaged global precipitation. There are large areas where there are no observations.

AZ: I remind you at the 8th Satellite Meteorology Data Users Conference in 1997 where it was said: "a satellite is the poor man’s radar"

10: Satellite data of clouds are more useful than synops reports

General reaction of all: This is very provocative!

EM: We will need both! Whatever you do you will always need good ground truth!

WB: No, there are too much questions about the accuracy.

HPR: Synops are relevant, it depends on the situation/application.

AZ: Could you rephrase the statement and emphasise the synergy of point observations and satellite observation (e.g. to cover the gaps using some kind of interpolation technique).

11: Present satellite cloud data are sufficient/adequate and future satellite cloud data will be even more sufficient/adequate (e.g.: MSG/Metop)

HPR: Yes, present data are sufficient. The meteorological user community has to deal with a large increase in the data stream due to MSG.

FH: In the future 1 minute of rapid scans allows tracking of single clouds to derive accurate cloud winds.

HPR: EUMETSAT thinks about a combination of a full disk every 15 minutes in combination with a rapid scan mode to focus on certain phenomena.

Concluding remarks

The CLOUDMAP project partners would like to thank all participants for their valuable contributions to the workshop and the AMS/EUMETSAT Conference organisation for hosting the workshop.

Back to main text

APPENDIX B: Report on 2nd CLOUDMAP User Workshop

Date: April 21, 1999

Venue: Congresgebouw, Den Haag, The Netherlands

Setting and scope of workshop:

The second user workshop of the CLOUDMAP project was held in Den Haag. The venue was chosen as it coincided with the EGS 24th general assembly. Part of the workshop programme was scheduled as part of Symposium AO30 with the title "Use of satellite data in climate studies". The dedicated CLOUDMAP paper session was scheduled at the end of the day.

After the paper session and a small break (with some snacks and drinks) the real part of the workshop, an interactive discussion with users, was held.

The first CLOUDMAP user workshop, held during the AMS/EUMETSAT Conference in Paris at the end of May 1998, was focused mostly on the use of satellite cloud data in nowcasting and numerical weather prediction modelling. This second workshop was more focused, in line with the setting, on the use in climate research. The aim of the paper part of the workshop was to inform the audience on the work done in the CLOUDMAP project. The aim of the discussion part was to get feedback from the audience on their opinion on the use of satellite cloud data in climate studies in general and of CLOUDMAP products in particular.

Programme of workshop:

17.00 J.P. Mueller: CLOUDMAP evaluation of new macroscopic and microphysical cloud parameters from earth observation sensors for climate modelling.

17.15 A. Drescher, B. Schreiner: Application of high resolution MOMS/MIR data for CLOUDMAP validation.

17.30 H. Mannstein, R. Meyer: Automated contrail detection from AVHRR data.

17.45 H. Hetzheim: Mathematical theory and algorithms for detection of contrails.

18.00 L. Schueller, R. Preusker, J. Fischer: Retrieval of cloud optical and microphysical parameters from spaceborn imaging systems (MOS and MERIS).

18.15 R. Preusker, L. Schueller, J. Fischer: Cloud top height retrieval from measurements within the O2A band with the satellite imaging sensors MOS and MERIS.

18.30 Break

19.00 Discussion

20.00 Closing of workshop

Participants list (of discussion part):
(The initials in brackets are used in the discussion part of this report to identify persons who took part in the discussion. The comments made by the individual participants are not verbatim represented in this report and should not be treated as official).
Dr. Gary J. Robinson (ESSC, UK) (GR)
Lubomir Sdukup (Utia,Cas, Croatia) (LS)
Dr. Stephen Bakan (MPI für Meteorologie, Germany) (SB)
Dr. Tomas Halenka(Dept of Meteorlogy, Charles University, Czech) (TH)
Dr. David Chappell (ESSC, UK) (DC)
Dr. K. Pfeilsticker (University of Heidelberg, Germany) (KP)
Dr. Irina Melnikova (University of Tokyo) (IM)

CLOUDMAP partners (present at workshop):
Peter Mueller (UCL): CLOUDMAP co-ordinator (JM)
Hans Roozekrans (KNMI) (HR)
Paul de Valk (KNMI) (PV)
Hermann Mannstein (DLR-IPA) (HM)
Hartwig Hetzheim (DLR-IST) (HH)
Rene Preusker (FUB) (RP)
Lothar Schueller (FUB) (LSc)
Armin Drescher (DLR-IPE) (AD)

Report of discussion:

The discussion was guided by a number of 12 statements given with the aim to provoke the discussion.

1. Satellite data « other data
Are satellite data of clouds more useful than other data sources for application to climate research?

GR: Global coverage of satellite data is very helpful but the major problem is the calibration of the data on the long term.
Satellite data start to get useful for climate studies at time scales of a decade or more.
Satellite data can be useful to study the diurnal variation of clouds.

SB: It depends on the time scales under study.

HM: In the long term contrail study of DLR a NOAA satellite change always introduces sensitivity problems.

IM: Measurements in narrow spectral bands are required, this facilitates parameterisation of models.
Information on day to day variability but also vertical profile information obtained by aircrafts can be useful for climate research.

AD: Spatial resolution is very much related to radiometric accuracy.

2. Need for independent data
Do climate researchers require satellite cloud products which are independent of additional (e.g. NWP model, synops, etc.) data sources?

GR: Yes, keep it as clean as possible! Cross-correlation of data sources is a big problem in climate research.

HM: Independent data sources are useful to control model results.

3. Operational satellites
Are the present and future operational satellite cloud data sets (METEOSAT, MSG,NOAA) sufficient for use in climate research (eg ISCCP data set)?

GR: The big problem with the operational satellites is the calibration of data and products. The temporal resolution of the NOAA-AVHRR (3 hr) is sufficient.

SB: The quantity of the data in terms of spatial and temporal resolution is sufficient. However, the quality of the derived data sets is not sufficient.
We have to realise that different climate research subjects have different demands.

4. Experimental satellites
Do cloud data derived from experimental satellites (ERS, MOS, ENVISAT, EOS, ADEOS, etc.) have potential scientific value when used in climate research?

GR: Yes!

SB: The value is evident for case studies. For process studies they only have value if the calibration of data is stable for 10 years or more. Equal quality of data for 50 years would be a big step forward.

PM: We have to set realistic goals, no satellite programme has long term continuity funding.

5. How to increase satellite data use
What is the priority order for increasing the use of satellite data in climate research?:

IM: Again this depends on the scope of the research (e.g. temporal resolution has priority if the scope is to study the diurnal cycle). The priority is also related to its contribution to solve the calibration problem (which is the main drawback for use of satellite data in climate research).

GR: The highest priority should be set to data continuity for the purpose to create longer time series.

SB: First we have to assess in which way we make optimal use of satellite data:

-in a climate model,
-direct assimilation of observed cloud top radiances in a model,
-optimise the analysis for climate research,
-create long term consistent radiance data sets.

6: Cloud top height

Is cloud top height (CTH) information important in climate research?
If so, for which application? Which parameter has priority?:

SB: CTH can be used to estimate the convection strength and associated rain intensity.

GR: CTH can be useful for validation of models.
The choice of parameter does not matter because they are strongly related to each other.

Do you see the clouds move?

PM: Yes, but not when the clouds move in the along track direction.

6. Cloud type
Is cloud type information relevant for climate research?
If so, in which way should cloud types be classified?:

GR: Yes, both ways.

SB: Is this relevant for climatology studies? Clouds have a variable appearance, this 3D variability affects the radiation field.
The question arises how much information is required to obtain significant climatological parameters?

8. Contrails
What is the role and potential of information on contrails for climate research?

SB: The effect of contrails is quite well known: they change to cirrus or processed contrails. Coverage of contrails is sufficiently known. Still there are some unclear questions

9: Cloud particle size
Is cloud particle size distribution important for climate research?
If so, for which application(s)?

GR: This is fundamental information, in order to distinguish clouds from aerosols and its effect on radiation processes.

SB: The cloud particle size distribution has an important effect on radiation transport. It enables to distinguish between old contrails and cirrus.

10: Cloud optical thickness/geometrical thickness
Is cloud optical depth and/or thickness important for climate research?
If so, for which application(s)?

GR: Yes, optical thickness is very relevant for radiation transport models.

11: Cloud top phase
Is cloud top particle phase important for climate research?
If so, for which application(s)?

GR: Yes, this parameter is relevant; see 10

12: Polar vs geostationary
Are polar orbiting satellites relevant for climate research?

GR: They are both required as they are complementary, which is a necessary evil.

SB: Information about the ice coverage at the poles is most relevant for climate research.

Concluding remarks

Probably due to the very unfavourable time of the day, the number of climate researchers participating in the workshop discussion was rather disappointing. Nevertheless, the output of the workshop can be considered as very valuable for the CLOUDMAP project. The excellence of the participants has resulted into a few very clear conclusions on the usefulness of satellite derived cloud information in general and of the CLOUDMAP products in particular:

The CLOUDMAP project partners would like to thank all participants for their valuable contributions to the workshop and the EGS Congress organisation for hosting the workshop.

Back to main text

APPENDIX C: CLOUDMAP "user requirements" questionnaire

The following questionnaire has been composed by KNMI and sent out to 17 national meteorological institutes in Europe with the aim to obtain information from the user community on the current use of cloud information and on requirements for the future:

Details of respondent

Name: ……………………………………………………..............

Affiliation: …………………………………………………………

Function: …………………………………………………………..

Tel. no: +…………………………………………………..............

E-mail: ……………………………………………………............

Personal affiliation to cloud information

Please, choose one option:

Selection of application of cloud information

Please, choose one option (to help a clear interpretation of the information, provided by you, the further filling in of this questionnaire should be mostly representative for the field of application, you have selected):

Data sources for cloud information

Please, fill in roughly the percentage of importance for your chosen field of application

(the addition sum of the four percentages should be 100):

Current use of satellite data (for the purpose to obtain cloud information)

Please, fill in roughly the percentage of importance for your chosen field of application

(the addition sum of the two percentages should be 100):

Requirements to satellite cloud products

Please, fill in for each parameter relevant for your field of application as much as possible numbers.

Requirement

 

 

Parameter

areal coverage

(global/

continental/regional)

horizontal resolution

(km or m)

vertical resolution

(m or hPa)

data frequency

(minutes or hours)

time of delivery

(minutes or hours)

accuracy

(in dimension of parameter)

cloud mask

           

cloud amount or fraction

           

cloud type

           

cloud top phase

           

cloud optical thickness

           

semi-transparent cloud flag

           

contrail map

           

fog/stratus flag

           

cloud top temperature

           

cloud top pressure

           

cloud top height

           

(geometrical) thickness of cloud

           

cloud motion winds

           

liquid water content

           

precipitation flag

           

precipitation intensity

           

Priority of requirements to satellite cloud information (in general) in relation to operational use

Please, fill in roughly the percentage of importance for your chosen field of application.

Need for independence of additional data sources

To obtain quantitative cloud information using the current meteorological satellites additional data sources (NWP, synops, etc.) are necessary in many cases (eg cloud top heights).

Is it important/helpful for your application field to obtain accurate cloud information from satellite data without the need for additional data?

Further input to CLOUDMAP project

Are you willing to provide further "user" input to the CLOUDMAP project in a later phase (eg evaluation of CLOUDMAP products)?

Results of questionnaire:

KNMI received filled in questionnaires from 19 respondents coming from 13 countries. The answers have been summarised in table 1. The answers to the large table in the questionnaire are not included in table 1 since the answers are in many cases quite ambiguous and incomplete. It is tried to summarise the table in the questionnaire into some general conclusions, which can be found in the main text of this User Requirement report.

Table 1: Summary of results of questionnaire

Name of Institute: dnmi smi smi ukmo ukmo mic knmi hms hms zamg smhi dwd fmi lmd lmd kmi kmi inm inm
Are you a real end user?: yes yes yes yes yes yes yes yes yes yes no no no yes yes yes no yes yes
In which application field?:                   
a) general operational x x   x   x x x x x     x     x    
b) aviation operational       x     x   x                    
c) maritime operational       x                              
d) other operational       x             x               x
e) nwp modelling         x                       x  
f) climate research     x                 x   x x   x    
Data sources used for                   cloud information (in %):                   
a) synops 40 10 30 25 40 20 40 20 20 80 40 25 25 0 0 30 50 50 15
b) nwp 20 5 0 40 0 40 5 30 50 10 25 25 25 20 10 20 0 0 30
c) satellite 30 80 70 30 60 30 50 25 30 10 25 40 50 80 80 50 50 50 25
d) other: radar/sodar/sonde 10 5 0 5 0 10 5 25 0 0 10 10 0 0 10   0 0 30
Type of satellite used for                   cloud information (in %):                   
1) geostationary 20 90 100 85 50 100 95 99 90 100 50 55 40 80 80 90 100 50 85
2) polar 80 10 0 15 50 0 5 1 10 0 50 45 60 20 20 10 0 50 15
Priority in satellite cloud information (in %):
1) adequate areal coverage 10 3 40 15 25 10 20 10 20 20         30 30   15 10
2) horizontal resolution 10 30 30 15 10 30 20 18 30 25         15 25   15 20
3) vertical resolution 10 2 20 10 15 10 10 2 10 10         10 0   10 15
4) repetition time/data freq 10 30 20 15 25 30 20 20 10 20         30 20   10 20
5) time of delivery 30 30 5 15 10 10 10 10 10 10         0 0   10 20
6) accuracy/quality of data 30 5 5 30 15 10 20 40 20 15         15 25   40 15
Need for cloud information from satellites to be independent on additional information?                  
  no no yes yes no yes yes yes no no yes yes no yes yes no yes no yes

Legend to table 1:

dnmi : Norwegian Meteorological Institute
smi: Swiss Meteorological Institute
ukmo : United Kingdom Meteorological Office
mic: Meteorological Institute of Croatia
knmi: Royal Dutch Meteorological Institute
hms : Hungarian Meteorological Service
zamg: Austrian Meteorological Institute
smhi: Swedish Meteorological Institute
dwd: German Meteorological Service
fmi: Finnish Meteorological Institute
lmd: Dynamical Meteorological Laboratory (France)
kmi: Royal Meteorological Institute (Belgium)
inm: Instituto Nacional de Meteorologia (Spain)

clim: climatologist
nwp: numerical weather prediction

Additional remark:

DWD has put a remark on the questionnaire that it is willing to provide dedicated data for verification of CLOUDMAP products, e.g. IR and UM profiler data, radio sondes, sodar, lidar etc.

Back to main text