Menu Sign In Contact FAQ
Banner
Welcome to our forums

AviatorsBot - A Telegram Bot for Weather Updates and Calculations

@Anders And thanks to your feedback I also discovered another issue, that runways which are only used in one direction, like runway 18 in EDDF caused an issue with the xwind command. Which is now fixed.

Here you also get the correct response for the three parallel runways:

And for the curious a look behind the curtain, the monitoring of the bots performance:

@LeSving Thank you! Main reason that I’m not using SMS is cost, but also that I want to send photos etc. At the current message rate it would cost about 600 EUR per month for the SMS gateway usage. SMS is actually the most expensive way to exchange data in the known universe, if you are up for a funny read from 2008: https://phys.org/news/2008-05-space-scientist-texting-expensive-scientific.html

Fly for your dreams
LOAV

ESTL has runways 11R/29L and 11L/29R
Cross-wind is reported like this

ESTL

Hi Fabian,
you’re probable very busy but just to let you know I emailed you.
Liebe Grüße ;)

has a Beagle...
LOWG Graz Austria

@Anders Thank you! As I suspected, this is caused by incorrect information from openAIP, which seems to be very wrong:

I updated the runways based upon the Swedish AIP. But it will take some time until this propagates into the bot. Since you also obviously know the airport better than me please cross-check my edit: https://www.openaip.net/node/161378 and I only checked the runways, so maybe you got further information to contribute too.

@Peter I also included the lightning strikes now and plan on adding more weather charts

New Feature: Lightning Strikes and Region Preference
You can now get a map of the current lightning strikes using: /strikes

Since I want to keep the bot worldwide, as far as possible, you can also include a region, for example North America: /strikes na
To make this less tedious you can also set your own region default using /region

I am currently working on a map of current SIGMETs in a region and SIGMETs in the vicinity of a specific airport, also including the SIGMETs in the subscription, so that you will get a message if a new SIGMET is published in the vicinity of a subscribed airport.

Fly for your dreams
LOAV

New Feature Online! Maps of SIGMETs and Flight Conditions

You can now use the /sigmet command to request a map of all SIGMETs and current flight conditions for a region.

Examples:

After getting the map you can send /sigmet to get the full sigmet.

For example:

/sigmet 6

WSCU31 MUHA 070705
MUFH SIGMET 2 VALID 070706/071106 MUHA-
MUFH HABANA FIR EMBD TS OBS AT 0700Z WI N2300 W08600 N2300 W08200
N2000 W08100 N2000 W08200 N2042 W08518 N2200 W08600 TO N2300 W08600
CB TOP FL420 MOV N05KT NC=
Fly for your dreams
LOAV

This is really neat.

Can you make it display the current Eurocontrol “ATC strikes” (it isn’t actually called that) map? I recall seeing it on their website but it was onlya tiny image.

Administrator
Shoreham EGKA, United Kingdom

TAFs seem to come rather late. Having taken a subscription in the morning, I got the 1100Z TAFs for LFLY, LFLL, LFBO, LSGG (1125Z TAF), LFGJ (1101Z TAF), ELLX, LSZB (1125Z TAF) at 1205Z, that is an hour late.

Also, later I got this sequence:

  • At 1335Z, TAF AMD LSZB 231328Z, TAF AMD LFLL 231331Z. That’s within a few minutes, good.
  • Then at 1338Z, TAF LSZB 231125Z, TAF LFLL 231100Z
  • Then at 13341Z, TAF AMD LFLL 231331Z, TAF AMD LSZB
    So there seems to be some bug in handling AMenDed forecast?
ELLX

lionel wrote:

(1101Z TAF), ELLX, LSZB (1125Z TAF) at 1205Z, that is an hour late.

Also, later I got this sequence:

At 1335Z, TAF AMD LSZB 231328Z, TAF AMD LFLL 231331Z. That’s within a few minutes, good.
Then at 1338Z, TAF LSZB 231125Z, TAF LFLL 231100Z
Then at 13341Z, TAF AMD LFLL 231331Z, TAF AMD LSZB
So there seems to be some bug in handling AMenDed forecast?

Hi lionel!

Sorry for the late response but I’ll look into it! Thanks for reporting it!

I’ve seen some issues with TAFs and also METARs being provided late out of the NOAA ADDS database.

Currently the handling of when to send an update works as follows:
Both a hash (digital fingerprint) and the date of the last sent update are stored in the database and if either changes when the new date is retrieved a message is sent. So if any one letter changes in the TAF, even if the date stays the same and update would be sent. TAF AMDs are not handled any differently by the bot, but might be on the NOAA side.

I’ll also check if there is anything in the server logs and let you know.

Fly for your dreams
LOAV
28 Posts
Sign in to add your message

Back to Top