Project

General

Profile

EUMETNET » History » Version 119

Jacob Maddison, 10/10/2016 10:46 AM

1 54 Andreas Schäfler
h1. OVERVIEW
2 54 Andreas Schäfler
3 89 Leo Saffin
List of NAWDEX radiosondes from all sources. Requested future sondes are plain text, confirmed launches are *bold*, failed launches are -striked-.
4 84 Ben Harvey
5 89 Leo Saffin
| IOP | Time period | Station| Nr Sondes| Release times| Aims|
6 90 Leo Saffin
| 1 | 16-17/09 | Lerwick    | 24 EUMETNET | 16/09: *18*, *21* UTC; 17/09: *03*, *06*, *09* UTC | |
7 90 Leo Saffin
|   |          | Castor Bay |             | 16/09: *18*, *21* UTC; 17/09: *03*, *06*, *09* UTC | |
8 90 Leo Saffin
|   |          | Torshavn   |             | 16/09: *18*, *21* UTC; 17/09: *03*, *06*, *09*, *15*, *18* UTC | |
9 90 Leo Saffin
|   |          | Keflavik   |             | 16/09: *21* UTC; 17/09: *03*, *06*, *09*, *15*, *18*, *21* UTC | |
10 90 Leo Saffin
| 2 | 21-22/09 | Ittoqqortoormiit | 4 EUMETNET | 21/09: *15*, *18*, *21* UTC; 22/09: *03* UTC | |
11 90 Leo Saffin
|   |          | Keflavik         | 2 IMO      | 21/09: *18*, *21* UTC | |
12 90 Leo Saffin
|   |          | Keflavik         | 1 DLR      | 21/09: *15* UTC | |
13 90 Leo Saffin
| 3 | 23-25/09 | Lerwick    | 17 EUMETNET | 24/09: *09*, *15*, *18*, *21* UTC; 25/09: *03* UTC | |
14 90 Leo Saffin
|   |          | Castor Bay |             | 24/09: *09*, *12*, *15*, *18*, *21* UTC; 25/09 *03* UTC | |
15 90 Leo Saffin
|   |          | Brest      |             | 25/09: -03-, -06-, -09-, -15-, -18-, -21- UTC | |
16 90 Leo Saffin
|   |          | Lerwick    | 7 UKMO      | 23/09: *21* UTC; 24/09: *03* UTC | |
17 90 Leo Saffin
|   |          | Castor Bay |             | 23/09: *09*, *12*, *15*, *18*, *21* | |
18 116 Jacob Maddison
| 4/5 | 26-29/09 | Azores      | 43 EUMETNET | 27/09: *00* UTC; 28/09: *00* UTC | The Azores sondes and the ships (around the Azores) were requested because the region showed a large forecast sensitivity due to the positioning of tropical cyclone Lisa in this area and how it affected the midlatitude weather. Therefore the observations were intended to reduce uncertainty in the forecasts of tropical cyclone Karl's recurvature and in the North Atlantic and later interaction with a separate extratropical cyclone. |
19 115 Jacob Maddison
|   |          | ASEU01      |             | 27/09: -06- UTC; 28/09: -06- UTC | |
20 115 Jacob Maddison
|   |          | ASEU02      |             | 27/09: -06- UTC | |
21 115 Jacob Maddison
|   |          | ASDE04      |             | 27/09: -06- UTC ; 28/09: *06* UTC| |
22 110 Jacob Maddison
|   |          | Torshavn    |             | 27/09: *03*, *06*, *09*, *15*, *18*, *21* UTC | On Tuesday the DLR Falcon and the FAAM had a coordinated flight as Karl passed over the North of Scotland. This was associated with a PV streamer at upper levels streching from Iceland over the North of Scotland and forming a cut off that moved with the surface cyclone over Norway and was associated with large amounts of precipitation. The remaining sondes listed here aimied to capture these features which follow the flight by HALO the previous day and were sampled by the coordinated leg between the DLR falcon and the FAAM from Torshavn to the west coast of Scotland. |
23 110 Jacob Maddison
|   |          | Egilsstadir |             | 27/09: -12- UTC | |
24 110 Jacob Maddison
|   |          | Orland      |             | 27/09: *15*, *18*, *21* UTC; 28/09: *03*, *06* UTC | |
25 110 Jacob Maddison
|   |          | Goteborg  |              |29/09: *06*, *12*, *18* UTC | |
26 110 Jacob Maddison
|   |          | Visby      |                  |29/09: -06-, -18- UTC | |
27 110 Jacob Maddison
|   |          | Brest     |                  |28/09: *18* UTC; 29/09: *06*, *18* UTC | |
28 110 Jacob Maddison
|   |          | Nordeney    |                  |28/09: *18* UTC; 29/09: *06*, *18* UTC | |
29 110 Jacob Maddison
|   |          | Castor Bay |                | 28/09: *06*, *12*, -18- UTC; 29/09: -06- UTC | |
30 110 Jacob Maddison
|   |          | Lerwick |                     | 28/09: -18- UTC ||
31 110 Jacob Maddison
|   |          | Cambourne  |         | 29/09: -06- UTC | |
32 110 Jacob Maddison
|   |          | Herstnonceaux  |         | 29/09: -06-, -12- UTC | |
33 110 Jacob Maddison
|   |          | Stavanger   |             | 27/09: *15*, *18*, *21* UTC; 28/09: *03*, *06* UTC | |
34 110 Jacob Maddison
|   |          | Keflavik    | 3 IMO       | 27/09: *03*, *18* UTC ; 29/09: *18* UTC| |
35 110 Jacob Maddison
|   |          | Keflavik    | 5 DLR       | 27/09: -06-, -09-, -15-, -21- UTC; 28/09: -06- UTC | |
36 101 Jacob Maddison
|   |          | Castor Bay  | 9 UKMO      | 26/09: *15*, *18*, *21* UTC | |
37 110 Jacob Maddison
|   |          | Lerwick     |             | 27/09: *03*, *06*, *09*, *15*, -18-,-21- UTC | |
38 103 Jacob Maddison
|   |          | Ekofisk  |   6 Norway    | 28/09: 18 UTC ; 29/09: 06, 18 UTC| |
39 103 Jacob Maddison
|   |          | Stavanger |             | 28/09: 18 UTC : 29/09: 06, 18 UTC| |
40 117 Jacob Maddison
| 6 | 01 - 6/10| Azores | 54 EUMNETNET  | 01/10: 00 UTC; 02/10: 00 UTC; 05/10: 00 UTC; 06/10: 00 UTC |  Sondes were released to try and capture the inflow, ascent and outflow of the WCB of the "Saturday cyclone", the ridge building across Greenland, Iceland and Norway as well as heavy precipitation downstream in central Europe | |
41 105 Jacob Maddison
|   |          | ASDE03  |             | 01/10: 06, 18 UTC; 02/10: 06 UTC | |
42 105 Jacob Maddison
|   |          | ASDK01  |             | 01/10: 06, 18 UTC | |
43 106 Jacob Maddison
|   |          | Brest      |              | 01/10: 21 UTC; 04/10: 06, 18 UTC; 05/10: 06, 18 UTC| |
44 105 Jacob Maddison
|   |          | Tasilaq    |             | 02/10: 15, 18, 21 UTC; 03/10: 03, 06 UTC| |
45 105 Jacob Maddison
|   |          | Ittoqqortoormiit   |             | 02/10: 15, 18, 21 UTC; 03/10: 03, 06 UTC | |
46 105 Jacob Maddison
|   |          | Egilsstadir  |             | 02/10: 12 UTC | |
47 105 Jacob Maddison
|   |          | Jan Mayen    |             | 02/10: 15, 18, 21 UTC ; 03/10: 03, 06, 09 UTC| |
48 105 Jacob Maddison
|   |          | Goteburg    |             | 02/10: 18 UTC | |
49 105 Jacob Maddison
|   |          | Stavanger    |             | 03/10: 03, 06, 09 UTC | |
50 1 Redmine Admin
|   |          | Andoya   |             | 03/10: 03, 06, 09 UTC | |
51 1 Redmine Admin
|   |          | Orland    |             | 03/10: 03, 06, 09 UTC | |
52 106 Jacob Maddison
|   |          | Zadar     |             | 03/10: 18 UTC; 04/10: 06 UTC | |
53 106 Jacob Maddison
|   |          | Brindisi    |             | 03/10: 18 UTC; 04/10: 06 UTC | |
54 106 Jacob Maddison
|   |          | Beograd     |             | 03/10: 18 UTC; 04/10: 06 UTC | |
55 118 Jacob Maddison
|   |          | Poprad-Ganovce|             | 03/10: 18 UTC; 04/10: 06 UTC: 05/10: 06, 18 UTC| |
56 1 Redmine Admin
|   |          | Sriveri     |             | 05/10: 00 UTC; 06/10: 00 UTC | |
57 118 Jacob Maddison
|   |          | Ittoqqortoormiit|         | 06/10: 09 UTC | |
58 118 Jacob Maddison
|   |          | Ajaccio|                  | 06/10: 06, 18 UTC | |
59 118 Jacob Maddison
|   |          | Pratica di Mare|          | 06/10: 06, 18 UTC | |
60 118 Jacob Maddison
|   |          | Nimes|                    | 06/10: 06, 18 UTC | |
61 118 Jacob Maddison
|   |          | Keflavik |  7 IMO         | 01/10: 21 UTC; 02/10: 03, 06, 09, 15, 18, 21 UTC | |
62 118 Jacob Maddison
|   |          | Keflavik |  3 DLR         | 01/10: 18 UTC; 02/10: 12, 18 UTC | |
63 119 Jacob Maddison
| 7 | 07-12/10 | Ittoqqortoormiit |   EUMETNET | 07/10: 06, 09, 15, 18 UTC | |
64 119 Jacob Maddison
|   |          | Tasilaq|                  | 07/10: 06, 09, 15, 18 UTC; 09/10: 18 UTC; 11/10: 06, 18 UTC | |
65 119 Jacob Maddison
|   |          | Jan Mayen|                | 08/10: 18 UTC; 10/10: 06, 18 UTC | |
66 119 Jacob Maddison
|   |          | Egilsstadir|              | 09/10: 06, 18 UTC | |
67 119 Jacob Maddison
|   |          | ASDU04|                    | 09/10: 06, 18 UTC | |
68 119 Jacob Maddison
|   |          | ASDE01|                    | 09/10: 06, 18 UTC; 10/10: 12, 18 UTC | |
69 119 Jacob Maddison
|   |          | Brest|                    | 10/10: 06, 18 UTC | |
70 119 Jacob Maddison
|   |          | Azores|                    | 10/10: 00 UTC; 11/10: 00 UTC | |
71 119 Jacob Maddison
|   |          | Lisbon|                    | 11/10: 18 UTC | |
72 105 Jacob Maddison
73 105 Jacob Maddison
74 1 Redmine Admin
75 92 Leo Saffin
Total Confirmed Launches
76 112 Jacob Maddison
EUMETNET: 79
77 113 Jacob Maddison
IMO: 5
78 92 Leo Saffin
DLR: 6
79 114 Jacob Maddison
UKMO: 14
80 54 Andreas Schäfler
81 1 Redmine Admin
h1. OTHER
82 1 Redmine Admin
83 87 Ben Harvey
* *Keflavik*: 60 sondes available from Icelandic Met Office (contact person: Nína Petersen) [covering 00, 03, 12 and 18 UTC releases in coordination with DLR]
84 54 Andreas Schäfler
85 87 Ben Harvey
* *Keflavik*: 62 sondes available from DLR (contact person: Martina Bramberger) [covering 06, 09, 15 and 21 UTC releases in coordination with IMO]
86 1 Redmine Admin
87 86 Ben Harvey
* *France*: all sondes requested via EUMETNET, except for Paris (XX sondes by Météo France, requests will be organized by P. Arbogast and G. Rivière)
88 1 Redmine Admin
89 86 Ben Harvey
* *Norway*: 60 sondes available from Met Norway (contact person: Rich Moore)
90 86 Ben Harvey
91 86 Ben Harvey
* *UK*: 30 sondes available from UK Met Office (contact person: John Methven), and XX sondes from Capel Dewi (requests will be organized by Geraint Vaughan)
92 86 Ben Harvey
93 86 Ben Harvey
* *Canada*: 4xdaily regular launches from 6 stations throughout campaign period (contact person: Ron McTaggart-Cowan)
94 74 Andreas Schäfler
95 1 Redmine Admin
h1. EUMETNET OBSERVATIONS
96 1 Redmine Admin
97 1 Redmine Admin
EUMETNET is a grouping of 31 European National Meteorological Services that provides a framework to organise co-operative programmes between its Members in the various fields of basic meteorological activities. These activities include observing systems, data processing, basic forecasting products, research and development and training. EUMETNET's mission statement is.
98 1 Redmine Admin
99 1 Redmine Admin
The EUMETNET programme supports NAWDEX with the following extra-observations:
100 1 Redmine Admin
101 1 Redmine Admin
# 1)	Radiosondes from land stations within the European Network
102 1 Redmine Admin
103 1 Redmine Admin
# 2)	E-AMDAR observations
104 1 Redmine Admin
105 1 Redmine Admin
# 3)	E-ASAP-radiosoundings from commercial ships
106 2 Redmine Admin
107 2 Redmine Admin
All observation types perform operational (regular) observations. During the NAWDEX observation period the NAWDEX team can activate the observation types and ask for increased observation frequency. This manual explains the procedure to activate them.
108 2 Redmine Admin
109 5 Redmine Admin
The *point of contact* responsible for the coordination of all observations by the EUMETNET Observations Programme Management is
110 2 Redmine Admin
111 2 Redmine Admin
> Sabine Hafner
112 3 Redmine Admin
> EUMETNET Observations Programme Management
113 3 Redmine Admin
> Operations and Projects Manager
114 49 Andreas Schäfler
> Deutscher Wetterdienst (DWD)
115 4 Redmine Admin
> email: sabine.hafner[at]dwd.de
116 6 Redmine Admin
117 6 Redmine Admin
The available funding covers 65 k€ (50k€ for additional radiosoundings and 15 k€ for AMDAR data. Depending on the price per sonde which varies from country to country we envisage 200-250 additional soundings. During the NAWDEX period we will regularly get a status report on our balance by Sabine Hafner.
118 7 Redmine Admin
119 47 Andreas Schäfler
All requests have to be sent from the email-address: *sounding[at] nawdex.org* to the respective points of contacts. Contacts are provided by Andreas Schäfler. Below you find templates to each Observation type. The template-text has to be copied to the body of the request-email (NO ATTACHMENT!).
120 8 Redmine Admin
121 9 Redmine Admin
---
122 8 Redmine Admin
123 8 Redmine Admin
h2. RADIOSONDES
124 10 Redmine Admin
125 10 Redmine Admin
126 48 Andreas Schäfler
Andreas provides a table of the available radiosonde stations that NAWDEX can access within the European Radiosonde Network and the affiliation to the respective national weather service for each station. All regular observation intervals and the possible additional sounding release times are listed in the table. 
127 10 Redmine Admin
128 47 Andreas Schäfler
For NAWDEX we can choose a subset of the list of stations depending on our needs. The requests are send with the "Radiosonde-Email-Template":https://internal.wavestoweather.de/nawdex/attachments/download/39/NAWDEX_EUMETNET_template_RADIOSONDES.doc. The list specifies advance warning deadlines for our requests. The template-text has to be copied to the body of the request-email (NO ATTACHMENT!). Generally we agreed on the following activation schedule (with some differences regarding activation for weekend and Monday):
129 12 Redmine Admin
130 12 Redmine Admin
131 13 Redmine Admin
* Announcement of the required additional sondes for specific stations 1-2 days in advance by the NAWDEX community 
132 13 Redmine Admin
133 13 Redmine Admin
* announcement of a regular time interval for a defined time window 
134 13 Redmine Admin
135 13 Redmine Admin
* go/no-go decision 12-24 h in advance
136 13 Redmine Admin
137 13 Redmine Admin
* for details see list +[AS: add link]+
138 14 Redmine Admin
139 14 Redmine Admin
140 51 Ben Harvey
!{width:80%}Radiosonde_locs.png!
141 26 Redmine Admin
_Overview of the radiosonde stations within the European network_ 
142 16 Redmine Admin
143 16 Redmine Admin
---
144 16 Redmine Admin
145 16 Redmine Admin
h2. E-AMDAR
146 16 Redmine Admin
147 19 Redmine Admin
E-AMDAR (Aircraft Meteorological Data Relay) facilitates the fully automated collection and transmission of weather observations from commercial aircraft. The E-AMDAR programme is an integrated component of the WMO Global Observing System (GOS) of the World Weather Watch (WWW) Programme. The system is operated by EUMETNET Member NMHS in collaboration and cooperation with partner airlines. E-AMDAR provides ascent/descent profile measurements at airports. 
148 19 Redmine Admin
149 50 Andreas Schäfler
The regular schedule is that every 3 hours a profile is produced from airports where E-AMDAR airplanes are starting and landing. Some airlines are already providing 1 hourly profiles, depending on the user needs. For NAWDEX it is planned that the NAWDEX organization tells E-AMDAR Team, from which area (1, 2 or 3) additional data are requested. E-AMDAR Team makes the changes in the E-AMDAR Optimisation Systems so that 1 hourly profiles, where available, are activated in the requested area.
150 19 Redmine Admin
151 20 Redmine Admin
The NAWDEX Team can activate different AMDAR regions that are defined as follows:
152 20 Redmine Admin
153 1 Redmine Admin
*	Area 1 (Scandinavia): 	LLC (4°E / 54°N) ;	URC (31°E / 72°N)
154 20 Redmine Admin
155 1 Redmine Admin
*	Area 2 (Iberia):	LLC (-11°E / 35°N); 	URC (4°E / 44°N)
156 20 Redmine Admin
157 1 Redmine Admin
*	Area 3 (Adriatic):	LLC (6°E / 37°N); 	URC (25°E / 48°N)
158 20 Redmine Admin
159 20 Redmine Admin
160 24 Redmine Admin
!{width:50%}Stations2.png!
161 25 Redmine Admin
_Location of the AMDAR areas that can be activated during NAWDEX_
162 19 Redmine Admin
163 47 Andreas Schäfler
E-AMDAR observations can be activated with the "E-AMDAR-Email-Template":https://internal.wavestoweather.de/nawdex/attachments/download/40/NAWDEX_EUMETNET_template_EAMDAR.doc by choosing one of the above mentioned areas. The template-text has to be copied to the body of the request-email (NO ATTACHMENT!). Lead times for the activation are:
164 21 Redmine Admin
165 22 Redmine Admin
*	regular schedule on weekdays: 48h before, according to table
166 22 Redmine Admin
167 22 Redmine Admin
*	Data for Monday has to be requested until Friday noon
168 22 Redmine Admin
169 22 Redmine Admin
*	Request for Tuesday can be sent on Monday 
170 21 Redmine Admin
171 16 Redmine Admin
172 16 Redmine Admin
---
173 16 Redmine Admin
174 18 Redmine Admin
h2. EASAP
175 27 Redmine Admin
176 42 Andreas Schäfler
EASAP radiosoundings are performed onboard ships (Container ships) that do their regular sevice on routes in the North Atlantic between Europe and North America. All soundings are performed by the crew members (not members of the weather Services) that volunteer. So it is their decision to whether they can release additional sondes as of course their focus is put on their regular duties (nautics,...). 
177 1 Redmine Admin
178 43 Andreas Schäfler
The big advantage for is that the ships are often in data sparse ocean regions. Ships perform regular ascents at various times which depend on location (reduced number of ascents near harbours) and the daily work onboard.W ithin the EASAP-Data Portal (infomation can be given by Andreas Schäfler) we are able to inform ourselves about the ship routes and ships. 
179 27 Redmine Admin
180 46 Andreas Schäfler
Request are sent with the "EASAP-Email-template":https://internal.wavestoweather.de/nawdex/attachments/download/45/NAWDEX_EUMETNET_template_EASAP.doc the ships are requested to perform 6-hourly ascents. The template-text has to be copied to the body of the request-email (NO ATTACHMENT!). The Email-contact Information is provided by Andreas Schäfler or Sabine Hafner. Sondes can be requested at the main synoptic times, at 00, 06, 12 and 18 UTC.
181 27 Redmine Admin
182 29 Redmine Admin
!{width:50%}EASAP.png!
183 1 Redmine Admin
_Radiosonde ascents from EASAP ships between 4 and 6 September. Releases are not regular so that it is difficult to predict future positions. However when we know the direction of the ship we will be able to define appropriate regions to activate the right ships._
184 29 Redmine Admin
185 27 Redmine Admin
---