Project

General

Profile

EUMETNET » History » Version 104

Jacob Maddison, 10/04/2016 10:33 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 101 Jacob Maddison
| 4 | 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 100 Jacob Maddison
|   |          | ASEU01      |             | 27/09: 06 UTC; 28/09: 06 UTC | |
20 1 Redmine Admin
|   |          | ASEU02      |             | 27/09: 06 UTC | |
21 100 Jacob Maddison
|   |          | ASDE04      |             | 27/09: 06 UTC ; 28/09: 06 UTC| |
22 93 Leo Saffin
|   |          | 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 90 Leo Saffin
|   |          | Egilsstadir |             | 27/09: 12 UTC | |
24 90 Leo Saffin
|   |          | Orland      |             | 27/09: 15, 18, 21 UTC; 28/09: 03, 06 UTC | |
25 95 Jacob Maddison
|   |          | Goteborg  |              |29/09: 06, 12, 18 UTC | |
26 95 Jacob Maddison
|   |          | Visby      |                  |29/09: 06, 18 UTC | |
27 100 Jacob Maddison
|   |          | Brest     |                  |28/09: 18 UTC; 29/09: 06, 18 UTC | |
28 94 Jacob Maddison
|   |          | Nordeney    |                  |28/09: 18 UTC; 29/09: 06, 18 UTC | |
29 101 Jacob Maddison
|   |          | Castor Bay |                | 28/09: 06, 12, 18 UTC; 29/09: 06 UTC | |
30 101 Jacob Maddison
|   |          | Lerwick |                     | 28/09: 18 UTC ||
31 1 Redmine Admin
|   |          | Cambourne  |         | 29/09: 06 UTC | |
32 1 Redmine Admin
|   |          | Herstnonceaux  |         | 29/09: 06, 12 UTC | |
33 103 Jacob Maddison
|   |          | Stavanger   |             | 27/09: 15, 18, 21 UTC; 28/09: 03, 06 UTC | |
34 101 Jacob Maddison
|   |          | Keflavik    | 3 IMO       | 27/09: 03, 18 UTC ; 29/09: 18 UTC| |
35 101 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 1 Redmine Admin
|   |          | 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 104 Jacob Maddison
| 5| 01/10 - 3/10| Azores |           | 01/10: 00 UTC |  Sondes were released to try and capture the inflow, ascent and outflow of the WCB of the "Saturday cyclone" | |
41 1 Redmine Admin
42 92 Leo Saffin
Total Confirmed Launches
43 92 Leo Saffin
EUMETNET: 39
44 92 Leo Saffin
IMO: 4
45 92 Leo Saffin
DLR: 6
46 92 Leo Saffin
UKMO: 10
47 54 Andreas Schäfler
48 1 Redmine Admin
h1. OTHER
49 1 Redmine Admin
50 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]
51 54 Andreas Schäfler
52 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]
53 1 Redmine Admin
54 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)
55 1 Redmine Admin
56 86 Ben Harvey
* *Norway*: 60 sondes available from Met Norway (contact person: Rich Moore)
57 86 Ben Harvey
58 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)
59 86 Ben Harvey
60 86 Ben Harvey
* *Canada*: 4xdaily regular launches from 6 stations throughout campaign period (contact person: Ron McTaggart-Cowan)
61 74 Andreas Schäfler
62 1 Redmine Admin
h1. EUMETNET OBSERVATIONS
63 1 Redmine Admin
64 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.
65 1 Redmine Admin
66 1 Redmine Admin
The EUMETNET programme supports NAWDEX with the following extra-observations:
67 1 Redmine Admin
68 1 Redmine Admin
# 1)	Radiosondes from land stations within the European Network
69 1 Redmine Admin
70 1 Redmine Admin
# 2)	E-AMDAR observations
71 1 Redmine Admin
72 1 Redmine Admin
# 3)	E-ASAP-radiosoundings from commercial ships
73 2 Redmine Admin
74 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.
75 2 Redmine Admin
76 5 Redmine Admin
The *point of contact* responsible for the coordination of all observations by the EUMETNET Observations Programme Management is
77 2 Redmine Admin
78 2 Redmine Admin
> Sabine Hafner
79 3 Redmine Admin
> EUMETNET Observations Programme Management
80 3 Redmine Admin
> Operations and Projects Manager
81 49 Andreas Schäfler
> Deutscher Wetterdienst (DWD)
82 4 Redmine Admin
> email: sabine.hafner[at]dwd.de
83 6 Redmine Admin
84 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.
85 7 Redmine Admin
86 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!).
87 8 Redmine Admin
88 9 Redmine Admin
---
89 8 Redmine Admin
90 8 Redmine Admin
h2. RADIOSONDES
91 10 Redmine Admin
92 10 Redmine Admin
93 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. 
94 10 Redmine Admin
95 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):
96 12 Redmine Admin
97 12 Redmine Admin
98 13 Redmine Admin
* Announcement of the required additional sondes for specific stations 1-2 days in advance by the NAWDEX community 
99 13 Redmine Admin
100 13 Redmine Admin
* announcement of a regular time interval for a defined time window 
101 13 Redmine Admin
102 13 Redmine Admin
* go/no-go decision 12-24 h in advance
103 13 Redmine Admin
104 13 Redmine Admin
* for details see list +[AS: add link]+
105 14 Redmine Admin
106 14 Redmine Admin
107 51 Ben Harvey
!{width:80%}Radiosonde_locs.png!
108 26 Redmine Admin
_Overview of the radiosonde stations within the European network_ 
109 16 Redmine Admin
110 16 Redmine Admin
---
111 16 Redmine Admin
112 16 Redmine Admin
h2. E-AMDAR
113 16 Redmine Admin
114 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. 
115 19 Redmine Admin
116 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.
117 19 Redmine Admin
118 20 Redmine Admin
The NAWDEX Team can activate different AMDAR regions that are defined as follows:
119 20 Redmine Admin
120 1 Redmine Admin
*	Area 1 (Scandinavia): 	LLC (4°E / 54°N) ;	URC (31°E / 72°N)
121 20 Redmine Admin
122 1 Redmine Admin
*	Area 2 (Iberia):	LLC (-11°E / 35°N); 	URC (4°E / 44°N)
123 20 Redmine Admin
124 1 Redmine Admin
*	Area 3 (Adriatic):	LLC (6°E / 37°N); 	URC (25°E / 48°N)
125 20 Redmine Admin
126 20 Redmine Admin
127 24 Redmine Admin
!{width:50%}Stations2.png!
128 25 Redmine Admin
_Location of the AMDAR areas that can be activated during NAWDEX_
129 19 Redmine Admin
130 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:
131 21 Redmine Admin
132 22 Redmine Admin
*	regular schedule on weekdays: 48h before, according to table
133 22 Redmine Admin
134 22 Redmine Admin
*	Data for Monday has to be requested until Friday noon
135 22 Redmine Admin
136 22 Redmine Admin
*	Request for Tuesday can be sent on Monday 
137 21 Redmine Admin
138 16 Redmine Admin
139 16 Redmine Admin
---
140 16 Redmine Admin
141 18 Redmine Admin
h2. EASAP
142 27 Redmine Admin
143 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,...). 
144 1 Redmine Admin
145 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. 
146 27 Redmine Admin
147 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.
148 27 Redmine Admin
149 29 Redmine Admin
!{width:50%}EASAP.png!
150 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._
151 29 Redmine Admin
152 27 Redmine Admin
---