VATATIS Features

Config Based Formatting

The powerful ATIS formatting provided by VATATIS is all made possible by our config based system.
With these configs we can quickly and easily tune a new format for any region in VATSIM. Everything from tweaking individual words in the ATIS to the whole order of the ATIS.

  • Airport Configs

    The Airport configs are what gives us the base info needed to start processing an ATIS.
    Without the airport config, we can't support an airport at all.
    In the config, we start off with an airports ICAO, then we include everything from which ATIS format to use, to the airport names, the magnetic variation and even the individual approaches each runway supports.
    Using these settings we can offer customization down to the individual airport level, not just the region level.

  • Position Configs

    The position configs allow us to load the different ATC positions for a region into our system.
    While this is an optional config for a region, it does allow the use of the For_xxx_contact_xxx Node described further down
    In the config we start with the VATSIM position identifier, then add the name and frequency and we can add additional tags such as mark a position as an event only position.

  • ATIS Configs

    The bread and butter of our ATIS system, the ATIS config is what allows us such a fine control of the output of our ATIS system.
    Each config starts with an arbitrary identifier, meaning we can even have multiple configs per region to support different airports.
    After that, we define the nodes to be used and the order to use them. Then inside each node we can define further options such as to break (' .. ') after that node, or to tweak different words in the node, the possibilities are almost endless.

Node based processing system

Our Node based processing system is what allows us such flexibility in how we format any given ATIS.
By processing each different segment as a node based on the config, we can process in whatever order we want, regardless of the METAR format.
Want your Temps before your winds? Easy. QNH right at the start? No problem. Whatever you want, we can do with our node based system.
Below is a list of our current nodes that can be used in an ATIS, the options they currently support and the features they give.

All nodes support the break (Insert desired text, default is ' .. ', after the node) and force_break (Insert desired text, default is ' .. ', after the node regardless of the content or lack thereof of the node) options

  • Altimeter Node

    This node processes the QNH or Altimier from the METAR.
    Currently it has no additional options as it automatically detects QNH or Altimeter from the METAR

  • Approach Node

    The approach node processes the selected IFR approaches for the ATIS.

    • The expect option - Allows changing of the expect part of 'expect ILS DME approach' to any desired text
    • The approach option - Allows moving of the word 'approach' from after the approach type to before. I.E. 'expect ILS DME approach' vs 'expect approach ILS DME' the expect part of 'expect ILS DME approach'
    • The from_config option - Changes the source of the approaches. Default (false) is to grab the approach type(s) from the apptype parameter in the Euroscope URL. When set to true, it pulls the approach types for each runway from the airport config, meaning you don't need to use the apptype parameter at all.
    • The check_default option - Tells the system to check for defaults for that runway. Default (false)
    • The include_runway_number option - Tells the system to include the runway number with any approach type. Default (false). Only works when check_default is also true
    • The app_types option - Allows overriding of the default text for any approach type. I.E. if ILS defaults to ILS DME in our system, this option allows changing that to just ILS on a per config basis.

  • Becoming Conditions Node

    This node processes any BECMG conditions reported in the METAR.
    Currently it has no additional options as it automatically processes anything in accordance with the rest of the config if the node is enabled and BECMG is reported in the METAR

  • Cloud Node

    The cloud node processes the cloud layers from the METAR. The cloud node supports all Octives (FEW, SCT, BKN, OVC) and Vertical visibility (VV). It also supports the following cloud types: CB, CI, SC, ST, TCU.
    The node also supports CAVOK, NCD, NSC, SKC and CLR. Finally we can configure the Cloud node to ignore clouds above a specificed height on a per airport level.

    • There are options for each cloud layer type (BKN, OCV etc...) that allow the output text for each of those to be customized
    • The units option - Allows changing of the FT units of the cloud altitudes to any desired text
    • The type option - Changes where the cloud type (TCU, CB, etc...) is in the text, either before the height or after the height
    • The cloud option - Allows changing of the 'Cloud' text leading the cloud output to any desired text
    • The cloud_after_first_type option - Allows moving the clouds text after the first type of clouds. I.E. Clouds scattered 5000ft becomes scattered Clouds 5000ft
    • The type_after_level option - Allows moving the type after the level of the clouds. Supports either 'none', 'not_first' or 'all' as options.
  • On Contact Node

    The on contact node controls the 'on first contact' string. Currently we have 3 available formats.

    • Format 1: 'on first contact with {AIRPORT NAME} ATC notify receipt of {ATIS LETTER}'
    • Format 2: 'Inform ATC on initial contact that you have information {ATIS LETTER}'
    • Format 3: 'Inform ATC that you have information {ATIS LETTER}'
    • Format 4: 'Acknowledge information {ATIS LETTER} on first contact'

  • For Contact Node

    The For Contact node is a very interesting node. Currently in use only in VATNZ, it inserts a string such as 'for ground and tower contact Approach 119.3' into the ATIS.
    This node requires the position config to be included for the region.
    It pulls the current online controllers from VATSIM and then, using the info from the Airport and Position configs, it determines who the lower and upper controllers for an airport are.
    Once it knows that, it will produce the string based on the lowest available position

    • There are no current options for this node outside of the Airport and Position configs

  • Info Node

    The info node grabs and processes the ATIS letter from our database.

    • There are no current options for this node

  • Location Node

    The location node parses the name of the airport from the airport config

    • There are no options currently for this node beyond the use of a different name vs full_name in the Airport config. This node uses full_name if available, otherwise falls back to just name.

  • NOSIG Node

    The NOSIG node simply processes any NOSIG reported in the METAR if enabled, rather than just skipping it.

    • There are no current options for this node

  • Ops Node

    The Ops Node is the overall control node for any operations info

    • Closed Ops Node

      The Closed Ops node handles processing any closed runways or taxiways
      There are no current options for this node

    • Frequency Ops Node

      The Frequency Ops node handles manual parameters relating to different open/closed frequencies
      There are no current options for this node

    • Heli Ops Node

      The Heli Ops node handles processing approach and runway information provided for Helicopters
      There are no current options for this node

    • Low Vis Ops Node

      The Low Vis Ops node handles processing any low visibility procedures
      There are no current options for this node

    • Ops Met Reports Node

      The Ops Met Reports node handles processing airmet, sigmet and windshear warning information
      There are no current options for this node

    • Windshear Runway Node

      The Windshear Runway node handles processing any windshear warnings for a specific runway
      There are no current options for this node

  • Recent Conditions Node

    This node processes any RE conditions reported in the METAR.
    Currently it has no additional options as it automatically processes anything in accordance with the rest of the config if the node is enabled and RE is reported in the METAR

  • Remarks Conditions Node

    This node processes any RMK conditions reported in the METAR in accordance with it's sub nodes.

    • Remark wind Node

      The Remark wind node handles processing winds reported in METARS specific to the ENOR FIR
      There are no current options for this node

  • Runway Node

    The runway node parses the runways in use from the URL arr and dep parameters. It automatically handles multiple runways and parallel runways.

    • The runway option - Allows changing of the runway text. I.E. changing Rwy to Runway
    • The departure option - Allows changing of the departure runway text.
    • The in_use option - Turns the addition of 'in use' to the runway text on and off
  • Arrival Runway Node

    The Arrival Runway node processes only the arrival runways. Used when you want to put a different node between the arrival and departure runways.

    • The runway option - Allows changing of the runway text. I.E. changing Rwy to Runway

  • Departure Runway Node

    The Departure Runway node processes only the departure runways. Used when you want to put a different node between the arrival and departure runways. Automatically handles parallel runway ops.

    • The runway option - Allows changing of the runway text. I.E. changing Rwy to Runway
    • The departure option - Allows changing of the departure runway text.

  • RVR Node

    The RVR node processes any RVR values in the METAR. Currently it only returns 'RVR values available on air traffic control frequency'. Future work is planned for improving this node.

    • There are currently no options for this node.
  • Surface Node

    The surface node parses METAR data to determine the runway condition. Currently returns either 'runway condition wet' or 'runway condition dry'

    • There are currently no options for this node.
  • Temp Node

    The temp node parses the temperature and duepoint from the METAR.

    • There are currently no options for this node.
  • Temporary Conditions Node

    This node processes any TEMPO conditions reported in the METAR.
    Currently it has no additional options as it automatically processes anything in accordance with the rest of the config if the node is enabled and TEMPO is reported in the METAR

  • Text Node

    The text node allows any freeform text to be inserted into the ATIS, with or without additional conditions

    • The text option - The text to insert into the ATIS
    • The condition option - optional - The condition that must be true to insert the text. An example is where the Canadian format inserts text if multiple approach types exist.
  • Time Node

    The time node parses the time from the METAR.

    • The issued option - Allows changing of the issued part of 'issued at' to any desired text

  • Transition Level Node

    The transition level node parses the transition level from the airport config

    • The use_tables option - Tells the node to adjust the TL based on the QNH. Default (blank), accepts a string that tells it what table to use to get the correct TL based on the QNH
  • Vis Node

    The vis node parses the visibility from the METAR. Automatically handles detection of units, supports 9999 as an input (KM only) and supports fractions (1/2, 1/3, 1/4, 1/5, 1/8) (SM only)

    • The more_than_10km_format option - Tells the node which format to use if vis is reported as 9999
  • WX Node

    The wx node parses the weather conditions from the METAR. Supports every weather condition in the METAR format, supports multiple WX conditions, supports NSW and VC options

    • The weather option - Allows changing of the 'present weather' string to any desired text
    • The moderate option - Allows changing of the 'moderate' string to any desired text
  • Wind Node

    The wind node parses the wind conditions from the METAR. Supports wind calm (wind below 4kts), Variable wind, variable between wind, gusting wind.
    The node also pulls the magnetic variation for the airport and applies it to the wind.

    • The surface_wind option - Allows changing of the 'surface wind' string to any desired text
    • The units option - Allows changing of the ' kts' string to any desired text
    • The degrees option - Allows changing of the 'degrees' string to any desired text
    • The gusting option - Allows changing of the 'gusting' string to any desired text
    • The degrees_after_var option - Allows adding the 'degrees' text after any variable conditions
    • The calm_below option - Tells the node below what speed to consider wind calm. Default is 4kts
  • 2000ft Wind Node

    The 200ft wind node parses the wind conditions from the twotfw url parameter. Supports everything the wind node does.

    • There are currently no options for this node.

Automatic ATIS letters

VATATIS has done away with the manual setting of ATIS letters in Euroscope.
Instead, we maintain a rolling ATIS letter in our database and rolls over with every new METAR, 24/7.
When you request an ATIS, this letter is pulled from the database and inserted into the ATIS.
In addition to changing with new METARS, the letter will change when runways or other ops info is changed if it was changed more than 2 minutes after the latest METAR.
If desired, this system can be disabled for a specific region.

Notification System

VATATIS has a built in notification system that allows us to push notifications to controllers via the ATIS text box.
When notifications are sent, requesting the ATIS again will cycle to the next notification or get the ATIS if no more notifications are available.
Currently the recording of seen notifications is done on an IP address basis. Meaning if you move to a different IP, you will see the active notifications again.

URL based control system

VATATIS currently has 1 method of controlling the ATIS. The URL system.
The URL system involves changing the URL parameters in Euroscope to get the desired output.
Most of the parameters are automatic, however there are some that are manual parameters whos details are described in the Docs page

Web based control system - Coming soon!

METAR Search

By going to the METAR page on our website, you can search and get a formatted output of any VATSIM metar in the world.
You can also see the previous METAR which is useful to see what the changes were between current and previous METARS

VATSIM SSO

VATATIS supports VATSIM SSO as it's sole login system.
While it is currently optional, future features will require you to be logged in via VATSIM SSO

Unsplashed background img 1
Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more