Radiosonde Launch Site - Launch Times & Parameters

darksidelemm commented 3 years ago

To help provide better predictions of radiosondes launches for all the launch sites that appear on the tracker map, we need information on:

What times of the day, and what days of the week radiosondes are launched. (e.g 00Z/12Z Monday-Friday) What the target ascent rate, nominal burst altitude, and landing descent rates are. (e.g. 5m/s ascent, 26km burst, 6m/s descent) Some of this information we can get from other sources (e.g. the giant database of radiosonde telemetry that is SondeHub), but local knowledge can help too!

If you have any of the above information for a launch site near you, please reply to this issue so it can be incorporated in.

EDIT (Luke Prior): Please use the Google Form your response will be automatically posted here.

https://forms.gle/GserZmFAif5z9QXH9

darksidelemm commented 3 years ago

As an example of what information we need:

Launch Site: Mount Gambier, South Australia (Refer list here: https://github.com/projecthorus/sondehub-tracker/blob/testing/launchSites.json)
Launch Times: 00Z, Monday and Wednesday
Flight Profile: 5m/s ascent rate, 26km burst, 6m/s landing rate

14ri004 commented 3 years ago

Hello,

Guipavas site (Brest -France) 0h00z 12h00z Monday to Sunday mounted at 5m / s descent between 5m / s and 12m / s Max Altitude 34000/36000 m

what do you mean by gust of 26 km ?????

rs1729 commented 3 years ago

Here is the condensed ogimet data for 2021/06: ogimet_2021jun.txt.gz

station: [day._timeZ]rs_type(launch_time) ...

[day._timeZ] is from the date/time-block right after TTAA/TTBB. rs_type(launch_time) are from the blocks after 31313 at the end of TTAA/TTBB.

EDIT: a quick json version: soundings_2016jun.json.gz (date/time error) (not sorted)

yaakov-h commented 3 years ago

I’m not sure how this would best be represented in the JSON that you linked to, but Sydney Airport (YSSY) launches are 6AM local time, which is UTC +10 or +11 depending on the time of year… just to confuse things 🙃

darksidelemm commented 3 years ago

For Sydney we're using an assumption of 18Z launches, which is close enough for prediction purposes.

LukePrior commented 3 years ago

Here is the condensed ogimet data for 2021/06: ogimet_2021jun.txt.gz
station: [day._timeZ]rs_type(launch_time) ...
[day._timeZ] is from the date/time-block right after TTAA/TTBB. rs_type(launch_time) are from the blocks after 31313 at the end of TTAA/TTBB.

Hey thanks for this,

I'm having a look through and trying to figure it all out:

04417: [01._11Z]42308(11:15) [02._11Z]42308(11:15) [03._11Z]42308(11:16) [05._11Z]42308(11:15) [06._11Z]42308(11:16)

So I'm assuming this refers to Geosummit (Greenland)

Then we have 5 launches listed which I'm assuming are all targeting 12Z models given the ~11:15 launch time.

I'm a bit confused with the dates so it would appear they were launched on days 1,2,3,5,6.

What does this mean, I see others have entries up until day 30 so I'm assuming it is data from one month?

So if the data stops at 6 does that mean it is not regular?

rs1729 commented 3 years ago

@LukePrior just made json output, just launch-date/time and radiosonde_type. line by line. soundings_2016jun.json.gz (date/time error) I hope I didn't introduce conversion errors.

04417: [01._11Z]42308(11:15) [02._11Z]42308(11:15) [03._11Z]42308(11:16) [05._11Z]42308(11:15) [06._11Z]42308(11:16)

Station 04417, 01._11Z means day 01 in June at 11Z (that's the first raw block in the raw date, more important is the exact launch time at the end of the raw data for that sounding) Jun 01 at 11Z, rs_type 23, launch time 11:15Z Jun 02 at 11Z, rs_type 23, launch time 11:15Z Jun 03 at 11Z, rs_type 23, launch time 11:16Z Jun 05 at 11Z, rs_type 23, launch time 11:15Z Jun 06 at 11Z, rs_type 23, launch time 11:16Z

(The "11Z" in the first block is not so useful, it's not really the synoptic time 12Z. Maybe there would be a problem for the midnight soundings, if 23:15Z -> 00Z the next day, the date would change.)

Now in json:

{ "station": "04417", "datetime": "2021-06-01T11:15Z", "rs_type": "23", "datetime": "2021-06-02T11:15Z", "rs_type": "23", "datetime": "2021-06-03T11:16Z", "rs_type": "23", "datetime": "2021-06-05T11:15Z", "rs_type": "23", "datetime": "2021-06-06T11:16Z", "rs_type": "23" }

Here the ogimet data for 04417 and 2021/06: https://www.ogimet.com/display_sond.php?lang=en&lugar=04417&tipo=ALL&ord=DIR&nil=SI&fmt=html&ano=2021&mes=06&day=01&hora=00&anof=2021&mesf=06&dayf=30&horaf=23&send=send The uwyo has less reports, maybe the soundings are not so regular: http://weather.uwyo.edu/cgi-bin/sounding?region=naconf&TYPE=TEXT%3ARAW&YEAR=2021&MONTH=06&FROM=0100&TO=3023&STNM=04417

EDIT: Don't know if the stations report the date/time all the same way, here is an example for a midnight sounding, where the launch time is probably 2021-06-09T23:53Z:

42971:  [10._00Z]52108(23:53) [11._00Z]52108(23:56) [11._12Z]52108(11:56) [12._00Z]52108(00:01) [12._12Z]52108(11:39) [13._00Z]52108(00:01) [14._00Z]52108(00:03)

https://www.ogimet.com/display_sond.php?lang=en&lugar=42971&tipo=ALL&ord=DIR&nil=SI&fmt=html&ano=2021&mes=06&day=01&hora=00&anof=2021&mesf=08&dayf=30&horaf=23&send=send TTAA | 10/06/2021 00:00-> TTAA 60001 42971 [...] 31313 52108 82353= In my json list it might be one day of:

{ "station": "42971", "datetime": "2021-06-10T23:53Z", "rs_type": "21", "datetime": "2021-06-11T23:56Z", "rs_type": "21", "datetime": "2021-06-11T11:56Z", "rs_type": "21", "datetime": "2021-06-12T00:01Z", "rs_type": "21", "datetime": "2021-06-12T11:39Z", "rs_type": "21", "datetime": "2021-06-13T00:01Z", "rs_type": "21", "datetime": "2021-06-14T00:03Z", "rs_type": "21" }

Perhaps I should compare the 00Z_ to the 23:53 if there is a wrap around...

However, if you just want the typical launch times of a station, this shouldn't matter much.

LukePrior commented 3 years ago

@LukePrior just made json output, just launch-date/time and radiosonde_type. line by line. soundings_2016jun.json.gz I hope I didn't introduce conversion errors.
04417: [01._11Z]42308(11:15) [02._11Z]42308(11:15) [03._11Z]42308(11:16) [05._11Z]42308(11:15) [06._11Z]42308(11:16)
Station 04417, 01._11Z means day 01 in June at 11Z (that's the first raw block in the raw date, more important is the exact launch time at the end of the raw data for that sounding) Jun 01 at 11Z, rs_type 23, launch time 11:15Z Jun 02 at 11Z, rs_type 23, launch time 11:15Z Jun 03 at 11Z, rs_type 23, launch time 11:16Z Jun 05 at 11Z, rs_type 23, launch time 11:15Z Jun 06 at 11Z, rs_type 23, launch time 11:16Z

(The "11Z" in the first block is not so useful, it's not really the synoptic time 12Z. Maybe there would be a problem for the midnight soundings, if 23:15Z -> 00Z the next day, the date would change.)

Now in json:
{ "station": "04417", "datetime": "2021-06-01T11:15Z", "rs_type": "23", "datetime": "2021-06-02T11:15Z", "rs_type": "23", "datetime": "2021-06-03T11:16Z", "rs_type": "23", "datetime": "2021-06-05T11:15Z", "rs_type": "23", "datetime": "2021-06-06T11:16Z", "rs_type": "23" }
Here the ogimet data for 04417 and 2021/06: https://www.ogimet.com/display_sond.php?lang=en&lugar=04417&tipo=ALL&ord=DIR&nil=SI&fmt=html&ano=2021&mes=06&day=01&hora=00&anof=2021&mesf=06&dayf=30&horaf=23&send=send The uwyo has less reports, maybe the soundings are not so regular: http://weather.uwyo.edu/cgi-bin/sounding?region=naconf&TYPE=TEXT%3ARAW&YEAR=2021&MONTH=06&FROM=0100&TO=3023&STNM=04417

I started going through all the data and manually updated the first 50 stations but I don't think I will have the time to do them all. The process might be able to be automated if I round all the times to the nearest 3 hours then check if it occurs every day or only once a week.

rs1729 commented 3 years ago

@LukePrior see my EDIT above, there might be some problems around midnight. Or maybe the hours are just rounded... I made a new list. soundings_2016jun.json.gz Now it's

{ "station": "42971", "datetime": "2021-06-10 00Z (23:53Z)", "rs_type": "21", "datetime": "2021-06-11 00Z (23:56Z)", "rs_type": "21",  ... }

where 2021-06-10 00Z is from the first TTAA raw block, and (23:53Z) is the launch time. Maybe it is just rounded, 23:29 -> 23Z and 23:31 -> 00Z next day. De Bilt (06260) e.g.

"datetime": "2021-06-05 00Z (23:31Z)", "rs_type": "23", 
"datetime": "2021-06-05 23Z (23:29Z)", "rs_type": "23",

{ "station": "06260", "datetime": "2021-06-01 00Z (23:36Z)", "rs_type": "23", "datetime": "2021-06-01 11Z (11:16Z)", "rs_type": "23", "datetime": "2021-06-02 00Z (23:33Z)", "rs_type": "23", "datetime": "2021-06-02 09Z (08:48Z)", "rs_type": "23", "datetime": "2021-06-03 00Z (23:35Z)", "rs_type": "23", "datetime": "2021-06-03 12Z (11:35Z)", "rs_type": "23", "datetime": "2021-06-03 23Z (23:28Z)", "rs_type": "23", "datetime": "2021-06-04 12Z (11:32Z)", "rs_type": "23", "datetime": "2021-06-05 00Z (23:31Z)", "rs_type": "23", "datetime": "2021-06-05 23Z (23:29Z)", "rs_type": "23", "datetime": "2021-06-06 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-07 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-08 23Z (23:21Z)", "rs_type": "23", "datetime": "2021-06-09 23Z (23:27Z)", "rs_type": "23", "datetime": "2021-06-10 12Z (11:31Z)", "rs_type": "23", "datetime": "2021-06-11 00Z (23:34Z)", "rs_type": "23", "datetime": "2021-06-11 23Z (23:21Z)", "rs_type": "23", "datetime": "2021-06-12 23Z (23:22Z)", "rs_type": "23", "datetime": "2021-06-13 23Z (23:27Z)", "rs_type": "23", "datetime": "2021-06-15 00Z (00:01Z)", "rs_type": "23", "datetime": "2021-06-15 23Z (23:27Z)", "rs_type": "23", "datetime": "2021-06-16 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-17 12Z (11:31Z)", "rs_type": "23", "datetime": "2021-06-18 00Z (23:36Z)", "rs_type": "23", "datetime": "2021-06-18 11Z (11:29Z)", "rs_type": "23", "datetime": "2021-06-19 00Z (23:38Z)", "rs_type": "23", "datetime": "2021-06-20 00Z (23:45Z)", "rs_type": "23", "datetime": "2021-06-21 00Z (23:35Z)", "rs_type": "23", "datetime": "2021-06-21 11Z (11:14Z)", "rs_type": "23", "datetime": "2021-06-21 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-22 23Z (23:19Z)", "rs_type": "23", "datetime": "2021-06-23 23Z (23:24Z)", "rs_type": "23", "datetime": "2021-06-24 12Z (11:34Z)", "rs_type": "23", "datetime": "2021-06-25 00Z (23:34Z)", "rs_type": "23", "datetime": "2021-06-26 00Z (23:41Z)", "rs_type": "23", "datetime": "2021-06-27 00Z (23:39Z)", "rs_type": "23", "datetime": "2021-06-28 00Z (23:41Z)", "rs_type": "23", "datetime": "2021-06-29 00Z (23:40Z)", "rs_type": "23", "datetime": "2021-06-29 11Z (10:48Z)", "rs_type": "23", "datetime": "2021-06-30 00Z (23:38Z)", "rs_type": "23" }

and 23:30 -> 00Z next day:

{ "station": "98223", "datetime": "2021-06-01 00Z (23:30Z)", ...

Don't know how precise you want the launch time data. For stations the do regular soundings for synoptic times 00Z, 12Z, 06Z, 18Z, it is probably easier to find the typical launch time. But some stations operate only on certain days of the week or so (e.g. Uccle, Hohenpeissenberg).

LukePrior commented 3 years ago

@LukePrior see my EDIT above, there might be some problems around midnight. Or maybe the hours are just rounded... I made a new list. soundings_2016jun.json.gz Now it's

{ "station": "42971", "datetime": "2021-06-10 00Z (23:53Z)", "rs_type": "21", "datetime": "2021-06-11 00Z (23:56Z)", "rs_type": "21",  ... }

where 2021-06-10 00Z is from the first TTAA raw block, and (23:53Z) is the launch time. Maybe it is just rounded, 23:29 -> 23Z and 23:31 -> 00Z next day. De Bilt (06260) e.g.

"datetime": "2021-06-05 00Z (23:31Z)", "rs_type": "23", 
"datetime": "2021-06-05 23Z (23:29Z)", "rs_type": "23",

{ "station": "06260", "datetime": "2021-06-01 00Z (23:36Z)", "rs_type": "23", "datetime": "2021-06-01 11Z (11:16Z)", "rs_type": "23", "datetime": "2021-06-02 00Z (23:33Z)", "rs_type": "23", "datetime": "2021-06-02 09Z (08:48Z)", "rs_type": "23", "datetime": "2021-06-03 00Z (23:35Z)", "rs_type": "23", "datetime": "2021-06-03 12Z (11:35Z)", "rs_type": "23", "datetime": "2021-06-03 23Z (23:28Z)", "rs_type": "23", "datetime": "2021-06-04 12Z (11:32Z)", "rs_type": "23", "datetime": "2021-06-05 00Z (23:31Z)", "rs_type": "23", "datetime": "2021-06-05 23Z (23:29Z)", "rs_type": "23", "datetime": "2021-06-06 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-07 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-08 23Z (23:21Z)", "rs_type": "23", "datetime": "2021-06-09 23Z (23:27Z)", "rs_type": "23", "datetime": "2021-06-10 12Z (11:31Z)", "rs_type": "23", "datetime": "2021-06-11 00Z (23:34Z)", "rs_type": "23", "datetime": "2021-06-11 23Z (23:21Z)", "rs_type": "23", "datetime": "2021-06-12 23Z (23:22Z)", "rs_type": "23", "datetime": "2021-06-13 23Z (23:27Z)", "rs_type": "23", "datetime": "2021-06-15 00Z (00:01Z)", "rs_type": "23", "datetime": "2021-06-15 23Z (23:27Z)", "rs_type": "23", "datetime": "2021-06-16 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-17 12Z (11:31Z)", "rs_type": "23", "datetime": "2021-06-18 00Z (23:36Z)", "rs_type": "23", "datetime": "2021-06-18 11Z (11:29Z)", "rs_type": "23", "datetime": "2021-06-19 00Z (23:38Z)", "rs_type": "23", "datetime": "2021-06-20 00Z (23:45Z)", "rs_type": "23", "datetime": "2021-06-21 00Z (23:35Z)", "rs_type": "23", "datetime": "2021-06-21 11Z (11:14Z)", "rs_type": "23", "datetime": "2021-06-21 23Z (23:25Z)", "rs_type": "23", "datetime": "2021-06-22 23Z (23:19Z)", "rs_type": "23", "datetime": "2021-06-23 23Z (23:24Z)", "rs_type": "23", "datetime": "2021-06-24 12Z (11:34Z)", "rs_type": "23", "datetime": "2021-06-25 00Z (23:34Z)", "rs_type": "23", "datetime": "2021-06-26 00Z (23:41Z)", "rs_type": "23", "datetime": "2021-06-27 00Z (23:39Z)", "rs_type": "23", "datetime": "2021-06-28 00Z (23:41Z)", "rs_type": "23", "datetime": "2021-06-29 00Z (23:40Z)", "rs_type": "23", "datetime": "2021-06-29 11Z (10:48Z)", "rs_type": "23", "datetime": "2021-06-30 00Z (23:38Z)", "rs_type": "23" }

and 23:30 -> 00Z next day:

{ "station": "98223", "datetime": "2021-06-01 00Z (23:30Z)", ...

Don't know how precise you want the launch time data. For stations the do regular soundings for synoptic times 00Z, 12Z, 06Z, 18Z, it is probably easier to find the typical launch time. But some stations operate only on certain days of the week or so (e.g. Uccle, Hohenpeissenberg).

I have now integrated this data into the file:

https://github.com/projecthorus/sondehub-tracker/blob/testing/launchSites.json

Please let me know if you see anything wrong

markdconner commented 3 years ago

For the US launch sites using LMS-6 sondes, the typical profile is: Ascent rate: 5 m/s Burst altitude: 33,500 m Sea-level descent rate: 2.5 m/s

If you need it, I should be able to locate the lat/lon of all US NWS radiosonde sites. I don't know if I can filter for those using LMS-6 vs others, but might be able to make a stab at it with existing Sondehub data collection.

Launch times are normally 1100 and 2300 UTC. Occasionally (like now with a tropical system threatening the US East Coast), soundings will be added with launch times at 0500 and 1700 UTC.

rs1729 commented 3 years ago

What does "times":["0:00:00","0:06:00","0:12:00"] mean? Does "0:" mean "every day"? What is "times":["3:00:00","4:00:00","4:12:00","7:00:00","1:00:00","2:00:00","6:00:00"] then? Is 1=Monday or 1=Sunday or something else? I didn't see a description for this field.

Uccle usually does RS41-SGP+O3 soundings 3 times a week, Monday, Wednesday, Friday at 11:30Z. There are no reports at ogimet.

  {"station":"06447","rs_types":["23"],"lat":50.7969,"lon":4.3581,"alt":100,"station_name":"Uccle (Belgium)","times":["0:12:00"]},

Not sure if "times":["0:12:00"] is right then?

One remark: When airline traffic was reduced last year, some stations made additional soundings, e.g. Essen usually launched at 10:45Z and 22:45Z, now also at 04:45Z. Not sure for how long this will continue. De Bilt used to have RS41-SGP launches every night at 23:30Z, and Thursdays at 11:30Z RS41-SGP+O3. I believe there are more soundings now.

LukePrior commented 3 years ago

Does "0:" mean "every day"?

Yes

Is 1=Monday or 1=Sunday or something else?

1 is Monday through to 7 is Sunday.

Uccle usually does RS41-SGP+O3 soundings 3 times a week, Monday, Wednesday, Friday at 11:30Z.

I will update this, the daily 12Z was from an old data source.

LukePrior commented 3 years ago

For the US launch sites using LMS-6 sondes, the typical profile is: Ascent rate: 5 m/s Burst altitude: 33,500 m Sea-level descent rate: 2.5 m/s

Cheers I will get this updated to be the default for LMS6 sondes. We already have the lat/long for all US stations to 4 decimal places.

rs1729 commented 3 years ago

On Sondehub, De Bilt (06260) has the schedule:

Launch schedule:
- Wednesday at 00:00 UTC
- Thursday at 00:00 UTC
- Thursday at 12:00 UTC
- Sunday at 00:00 UTC
- Monday at 00:00 UTC
- Tuesday at 00:00 UTC
- Saturday at 00:00 UTC

Perhaps the schedule should be sorted (starting with "every day").

For De Bilt, "Friday at 00:00 UTC" is missing, i.e. it should be

Launch schedule:
- Everyday at 00:00 UTC
- Thursday at 12:00 UTC

{"station":"06260", ..., "times":["0:00:00","4:12:00"]}

There are occasional soundings on other days at 12Z, but the Thursday 12Z sounding is O3 as mentioned before. For O3 there is no special rs_type-code.

Some stations have two different radiosonde types, one is launched at midnight, the other at noon. Since it is difficult to get reliable information from the data, this could be something for a remark field.

rs1729 commented 3 years ago

Essen (10410):

Next launch: Sun Aug 22 2021 13:15:00 GMT+0200 (Central European Summer Time)
Launch schedule:
- Everyday at 00:00 UTC
- Everyday at 06:00 UTC
- Everyday at 12:00 UTC

Schedule is ok for June 2021. But Next launch: 13:15 GMT+2 ? Apart from UTC vs. GMT, is 11:15Z preset for all launch sites? In Germany they launch at 10:45Z and 22:45Z (and 04:45Z, 16:45Z).

darksidelemm commented 3 years ago

It's currently set to assuming launch is 45 min before the 'nominal' time (00/06/12/18Z). For prediction purposes this is close enough, but I can see it might cause some confusion if people are trying to use it to tell exactly when the launch is.

It's going to be quite difficult to maintain this list...

rs1729 commented 3 years ago

Maybe the "Next launch" info is not really needed. For prediction the synoptic times are enough.

LukePrior commented 3 years ago

On Sondehub, De Bilt (06260) has the schedule:
Launch schedule:
- Wednesday at 00:00 UTC
- Thursday at 00:00 UTC
- Thursday at 12:00 UTC
- Sunday at 00:00 UTC
- Monday at 00:00 UTC
- Tuesday at 00:00 UTC
- Saturday at 00:00 UTC
Perhaps the schedule should be sorted (starting with "every day").

For De Bilt, "Friday at 00:00 UTC" is missing, i.e. it should be
Launch schedule:
- Everyday at 00:00 UTC
- Thursday at 12:00 UTC

{"station":"06260", ..., "times":["0:00:00","4:12:00"]}
There are occasional soundings on other days at 12Z, but the Thursday 12Z sounding is O3 as mentioned before. For O3 there is no special rs_type-code.

Some stations have two different radiosonde types, one is launched at midnight, the other at noon. Since it is difficult to get reliable information from the data, this could be something for a remark field.

oh3bsg commented 3 years ago

Finland: Sodankylä, 2836, [RS41, RS92], "times":["11:30:00", "23:30:00"] 404.000 MHz Jokioinen, 2963, RS41, "lat":60.81,"lon":23.5,"alt":104,"times":["5:30:00", "11:30:00", "17:30:00", "23:30:00"] 403.000 MHz

More information: https://www.ais.fi/ais/aip/ge/EF_ENR_5_3_EN.pdf ==> chapter 2.2 Upper air sounding balloons

LukePrior commented 3 years ago

Finland: Sodankylä, 2836, [RS41, RS92], "times":["11:30:00", "23:30:00"] 404.000 MHz Jokioinen, 2963, RS41, "lat":60.81,"lon":23.5,"alt":104,"times":["5:30:00", "11:30:00", "17:30:00", "23:30:00"] 403.000 MHz

More information: https://www.ais.fi/ais/aip/ge/EF_ENR_5_3_EN.pdf ==> chapter 2.2 Upper air sounding balloons

I have updated the list: https://github.com/projecthorus/sondehub-tracker/pull/124 This is now live at testing.v2.sondehub.org please confirm everything is correct.

oh3bsg commented 3 years ago

Times are wrong Here is correct ones {"station":"02836","rs_types":[["24","404.000"],"42"],"lat":67.3667,"lon":26.6289,"alt":179,"station_name":"Sodankyla (Finland)","times":["0:11:30","0:23:30","3:10:30"],"notes":"Ozone sonde launched Wednesdays"}, {"station":"02963","rs_types":[["24","403.000"]],"lat":60.81,"lon":23.5,"alt":104,"station_name":"Jokioinen (Finland)","times":["0:05:30","0:11:30","0:17:30","0:23:30"]},

LukePrior commented 3 years ago

Times are wrong Here is correct ones {"station":"02836","rs_types":[["24","404.000"],"42"],"lat":67.3667,"lon":26.6289,"alt":179,"station_name":"Sodankyla (Finland)","times":["0:11:30","0:23:30","3:10:30"],"notes":"Ozone sonde launched Wednesdays"}, {"station":"02963","rs_types":[["24","403.000"]],"lat":60.81,"lon":23.5,"alt":104,"station_name":"Jokioinen (Finland)","times":["0:05:30","0:11:30","0:17:30","0:23:30"]},

Sorry I should have mentioned that we record the target time 00Z, 06Z, 12Z, 18Z and then assume the actual launch is 45 minutes before this time. In this case that will mean the times are off by 15 minutes but it should be sufficient for predictions

14ri004 commented 3 years ago

Hello, I just saw that the balloon burst height is 26000m on the balloon burst predictions, it is rather around 34000m / 35000m mainly for: Brest (France) M10 Trappes (France) M10 Bordeaux (France) M10 Nimes (France) M20 Camborne (England) RS41

I can see to retrieve other information on other sites

thank you

14ri004 commented 3 years ago

Hello, for info, for more than a month, NIMES (France) shipments of Météomodem M20, good weekend

llnz commented 3 years ago

New Zealand Radiosondes

Paraparaumu - MetService, RS41

Launch Site: Paraparaumu Aerodrome (New Zealand)
Launch Times: Daily 1035 and 2235 Local - roughly 1035Z and 2235Z
Flight Profile: 5m/s ascent rate, 26km burst, 12m/s landing rate

Whenuapai - MetService, RS41

Launch Site: Whenuapai (New Zealand)
- Launch Times: Daily 1035 and 2235 Local - roughly 1035Z and 2235Z
- Flight Profile: 5m/s ascent rate, 26km burst, 12m/s landing rate

Invercargill - MetService, RS41

Launch Site: Invercargill Aerodrome (New Zealand)
- Launch Times: Daily 1035 and 2235 Local - roughly 1035Z and 2235Z
- Flight Profile: 5m/s ascent rate, 32km burst, 12m/s landing rate

Lauder - NWIA, RS41-Ozone

Launch Site: Lauder (Not in launchSites.json - Central Otago, New Zealand)
Launch Times: Most commonly on Tuesdays 0935 Local - roughly Mondays 2135Z
Flight Profile: 4m/s ascent rate, 30km burst, 8m/s landing rate

LukePrior commented 3 years ago

New Zealand Radiosondes

Hi,

I have updated the list on testing.v2.sondehub.org please check in a few minutes (shift F5) and check if all the stations/predictions look good. We round all the times up to the nearest 3 hours.

Can you confirm if the local time listed on predictions for Lauder is correct I have a feeling it might be a day behind

https://github.com/projecthorus/sondehub-tracker/pull/130

ke7hr commented 3 years ago

The Phoenix, Arizona USA site launches during our "monsoon" season (summer in the northern hemisphere) but the exact start and stop dates are unclear. It appears to depend upon the anticipated upper air flow and moisture. They launch at 11:30 and 23:30 UTC. Updated listing below:

{"station": "74626", "rs_types": ["41"], "lat": 33.45, "lon": -111.95, "alt": 386, "station_name": "Wfo Phoenix, Az. (United States)", "times": ["0:11:30, 23:30:00"], "burst_altitude": 23967, "burst_samples": 129, "burst_std": 2324, "descent_rate": 13.7, "descent_samples": 128, "descent_std": 2.9},

Paul Jorgenson KE7HR Phoenix, AZ USA

rs1729 commented 3 years ago

Beauvechain (Belgium)

Sondes launched: iMet-4 (403.000 MHz)
Launch schedule:
- Tuesday at 21:00 UTC
- Thursday at 21:00 UTC
- Saturday at 21:00 UTC
- Monday at 00:00 UTC
- Monday at 21:00 UTC
- Wednesday at 21:00 UTC

Beauvechain launch times have a large variance. Most of the time it is between 22:15-22:45 UTC, sometimes earlier (probably depending on who is on duty...). So I would set:

- Everyday at 00:00 UTC

ke7hr commented 3 years ago

Las Vegas, NV USA NWS Office

Launching at 23:30 and 11:30 every day with the Lockheed 1680 MHz sonde.

Few receivers in the area (especially on 1680 - I am over 400 km away and it has to be a good wind...) but worth noting on the tracker for possible future receivers.

"rs_types": [["82", "1680.000"]], "lat": 36.04705, "lon": -115.18466, "alt": 695, "station_name": "Las Vegas, NV (United States)", "burst_altitude": 31000, "descent_rate": 5.0,

Paul Jorgenson KE7HR Phoenix, AZ USA

LukePrior commented 3 years ago

Las Vegas, NV USA NWS Office

Launching at 23:30 and 11:30 every day with the Lockheed 1680 MHz sonde.

Few receivers in the area (especially on 1680 - I am over 400 km away and it has to be a good wind...) but worth noting on the tracker for possible future receivers.

"rs_types": [["82", "1680.000"]], "lat": 36.04705, "lon": -115.18466, "alt": 695, "station_name": "Las Vegas, NV (United States)", "burst_altitude": 31000, "descent_rate": 5.0,

Paul Jorgenson KE7HR Phoenix, AZ USA

Should be live on testing but the lat/lon seem off.

ke7hr commented 3 years ago

The Las Vegas National Weather Service office is not at the airport, but rather where the circle is on your graphic. 7851 Dean Martin Dr, Las Vegas, NV 89139 Zoom into the location on the aerial view and you will see the red roofed building and the sonde tracking dome on the west side of the building. I believe that the launches are on the pad just north of the tracking dome.

Paul Jorgenson KE7HR Phoenix, AZ USA

LukePrior commented 3 years ago

The Las Vegas National Weather Service office is not at the airport, but rather where the circle is on your graphic.

My apologies.

In this case I need to try and find the ID and name for the station as reported to ogimet/igra2

ke7hr commented 3 years ago

I think the Las Vegas site is: 72388 VEF

Referenced from: http://weather.uwyo.edu/upperair/sounding.html http://weather.uwyo.edu/cgi-bin/sounding?region=naconf&TYPE=TEXT%3ALIST&YEAR=2021&MONTH=09&FROM=0200&TO=0200&STNM=72388

LukePrior commented 3 years ago

I think the Las Vegas site is: 72388 VEF

{"station": "72388", "rs_types": [["82", "1680.000"]], "lat": 36.04705, "lon": -115.18466, "alt": 695, "station_name": "Las Vegas, National Weather Service Office (United States)", "times": ["0:00:00", "0:12:00"], "burst_altitude": 31000, "descent_rate": 5}

Cheers that looks correct it should all be live now on the main site:

ke7hr commented 3 years ago

Looks good to me. Thanks,.

That University of Wyoming site might be a good resource to cross reference any other questions since they seem to have all regions.

k1mea commented 3 years ago

Albany launch's are at 00:00 UTC and 12:00 UTC

oh3bsg commented 3 years ago

Sundsvall, Sweden Every day at 00:00UTC and 12:00UTC Sonde: RS41 WMO code: 02365 Station latitude: 62.53 Station longitude: 17.45 Station elevation: 6.0

LukePrior commented 3 years ago

Albany launch's are at 00:00 UTC and 12:00 UTC

Albany, Albany International Airport (United States)?

k1mea commented 3 years ago

Yes

F5MVO commented 3 years ago

Hi, Nimes France launch now M20

14ri004 commented 3 years ago

Hi, I have already warned 3 times that Nimes is dropping M20 probes since July, but nobody takes this into account ??

F5MVO commented 3 years ago

Hi, Bourges France, its DFM-09

14ri004 commented 3 years ago

center of Ury (77 France) 48.337861N, 2.60012E Alt 120m manufacturer of METEOMODEM probes random launch of M10 and M20 probes

LukePrior commented 3 years ago

center of Ury (77 France) 48.337861N, 2.60012E manufacturer METEOMODEM loose M10 and M20 probes

Hi in the future so that I can quickly add these can you please provide:

Station Name (as reported on https://www.ogimet.com/home.phtml.en) Station ID (as reported on https://www.ogimet.com/home.phtml.en and to WMO) Station Coordinates (maximum of 6 decimal places + alt rounded to the meter) Sondes launched (refer to list here https://github.com/projecthorus/sondehub-tracker/blob/master/js/tracker.js#L37) Launch times (day of week and time of day rounded to 3 hours and in UTC time) Launch parameters (sonde frequency if constant, sonde burst height if constant, sonde ascent rate if constant, sonde descent rate if constant) Launch notes (any important notes to display on tracker e.g. Ozone Sonde launched on Mondays)

This is the entry I have created for your submission from your data and my research (does not seem to be an official launch site just testing for METEOMODEM hence the -2 ID):

{"station": "-2", "rs_types": ["63", "77"], "lat": 48.337861, "lon": 2.60012, "alt": 118, "station_name": "METEOMODEM Headquarters (France)"},

It would be really good if you could provide future suggestions in this format so I can quickly add them to the list.

Cheers

14ri004 commented 3 years ago

DGA Center of Biscarrosse <French Army) 44.35714N, -1.23813W DFM9 Alt 15m from the site random launches burst 20000m

I don't have more information to provide

LukePrior commented 3 years ago

DGA Center of Biscarrosse <French Army) 44.35714N, -1.23813W DFM9 Alt 15m from the site random launches burst 20000m

I don't have more information to provide

I have added this entry, in future please provide in this format following instructions above:

{"station": "-3", "rs_types": ["17"], "lat": 44.35714, "lon": -1.23813, "alt": 15, "station_name": "DGA Essais de missiles (France)", "burst_altitude": 20000},

ka9q commented 3 years ago

KNKX San Diego, Miramar MCAS/Mitscher Field Airport (USA) WMO index 72293 Location from Google Earth: 32.845125° N W117.123690°W 133 m ASL (current location in database is in error by ~1.5 km) Vaisala autosonde launcher, RS-41 SGP launches usually right at 1100Z and 2300Z, sometimes delayed a few minutes almost always transmits on 400.65 MHz Bursts around 33 km

LukePrior commented 3 years ago

KNKX San Diego, Miramar MCAS/Mitscher Field Airport (USA) WMO index 72293 Location from Google Earth: 32.845125° N W117.123690°W 133 m ASL (current location in database is in error by ~1.5 km) Vaisala autosonde launcher, RS-41 SGP launches usually right at 1100Z and 2300Z, sometimes delayed a few minutes almost always transmits on 400.65 MHz Bursts around 33 km

Hey,

Thanks for the report, I have updated the position and frequency.

https://github.com/projecthorus/sondehub-tracker/commit/08650d86c25445b0d039b3dd617bad72e1a3b15b

ka9q commented 3 years ago

Thanks! The NKNX location now looks right, but the launch times still show as 0000Z/1200Z. Do you want the actual time the balloon leaves the launcher? That's usually exactly an hour earlier, i.e., 2300Z/1100Z, though occasionally it's delayed by a few minutes.

projecthorus / sondehub-tracker

Radiosonde Launch Site - Launch Times & Parameters #114

EDIT (Luke Prior): Please use the Google Form your response will be automatically posted here.