At the WMO Commission for Basic Systems (CBS) ET-OWFPS Meeting on 22-24 October 2014 in Geneva, a draft document on standardized surface verification of deterministic NWP products was agreed. The document specifies the content of the future exchange of surface scores between global centres and is available here:     Standardized Surface Verification for Deterministic NWP

ECMWF will be collecting and archiving the scores. Data will be exchanged in an ASCII-based format which is simple but flexible and is similar to the format used WMO exchange of upper-air scores.

Data format

Data file consists of score values and corresponding metadata in an ASCII format.

Every score value is described by the full set of key attributes, like its parameter, station id, month, step etc. Parameters describing one score value at one station are organised into a record. Each record corresponds to one score value. A record is a collection of pairs key=value separated by commas. A record spans one line. Value of the key which is not given in the current record is inherited from the previous record, except for the value parameter v which has to be present in each record.

Each record has the following format:

centre=centre, model=model_id, d=yyyymm, t=time, s=forecast_step, st=station_id, lat=latitude, lon=longitude, lam= model_grid_latitude , lom= model_grid_longitude , se=station_elevation, me=model_orography_elevation, par=parameter, sc=score, th=event_thresholds, n=sample_size, v=mean_value

If the value is not available the record either should not be given at all or the value should be set to NIL (v=nil); every record must contain the key v (value of key v is not inheritable from previous record).

Example

centre=ecmf,model=0001_fc,d=201410,t=0,s=24,st=11520,lat=50.02,lon=14.38,se=302,me=248,par=tp24,sc=me,th=na,n=31,v=0.95
s=48,v=1.15
s=24,sc=ct,th=5,v=1/16/12/2
s=48,v=3/13/11/4

Values of keys

parameterdescriptionunit
t2mair temperature at 2 meters above the model orography, corrected to the actual station elevation using the constant lapse rate 6.5K/1000mK
td2mdewpoint at 2 meters above the model orographyK
rh2mrelative humidity at 2 meters above the model orography%
tp06total precipitation accumulated over previous 6 hoursmm
tp24total precipitation accumulated over previous 24 hoursmm
ff10mwind speed at 10 meters above the model orographym/s
dd10mwind direction at 10 meters above the model orographydeg
tcctotal cloud coverokta (rounded to nearest okta for contingency table)

 

scoredescription 
me

mean error (bias)

 
maemean absolute error 
rmseroot mean square error 
ct

contingency table values,
scanned from bottom up, then left to right

The rank of a contingency table is defined by number of values in the key event_thresholds
(rank_of_ct = len(event_thresholds)+1)

 

NB. Please note how those contingency tables are constructed.
For an event like "10m wind speed >15m/s" a corresponding contingency
table would traditionally be

 obsnon-obs
fcHF
non-fcMR

but following the definition of 2x2 contingency table on the left the table should be

 ob<1515≤ob
fc<15RM
15≤fcFH
2x2ob<th1th1≤ob
fc<th1AB
th1≤fcCD

v=C/A/D/B

3x3ob<th1th1≤ob<th2th2≤ob
ob<th1ABC
th1≤ob<th2DEF
th2≤obGHI

v=G/D/A/H/E/B/I/F/C

4x4ob<th1th1≤ob<th2th2≤ob<th3th3≤ob
ob<th1ABCD
th1≤ob<th2EFGH
th2≤ob<th3IJKL
th3≤obMNOP

v=M/I/E/A/N/J/F/B/O/K/G/C/P/L/H/D

 

event_thresholddescription
15threshold for a 2x2 contingency table, e.g. if par=ff10m this is an event of 10m wind speed
5/10/15thresholds for a 4x4 contingency table for 10m wind speed

 

Procedures for exchange of data

Coming soon...