Jump to content
Justin Shannon

vATIS beta update 3.1.2.0 now available

Recommended Posts

Version 3.1.2.0 of vATIS is now available for download from the web site, or via the automatic update utility built into the ATIS client.

 

The following items were added or fixed in this version:

 

  • Add time parsing rule: ####Z (where # is a number between 0 and 9) is now synthesized as "# # # # zulu"
  • Add support for facilities that use an IDS system


Controller (C1), Los Angeles ARTCC
Developer: xPilot, vATIS

Share this post


Link to post
Share on other sites

Can someone explain how the IDS endpoint URL works? I don't see anything in the docomeentation about it. Looking into integrating this with our IDS.

Share this post


Link to post
Share on other sites
Can someone explain how the IDS endpoint URL works? I don't see anything in the docomeentation about it. Looking into integrating this with our IDS.

 

Ditto. There's nothing in the docomeentation. Is there any information on this available?

Share this post


Link to post
Share on other sites

If you have an endpoint URL configured in the facility settings, vATIS will make a POST request to the URL with the following JSON object structure:

{
 "facility": "KMSP",
 "config_profile": "30-35 IMC",
 "atis_letter": "K",
 "airport_conditions": "SIMUL DEPENDENT, ILS RWY 30L APCH IN USE, ILS RWY 30R APCH IN USE, ILS *V RWY 35 APCH IN USE. DEPTG RWY 30L, RWY 30R. LAHSO IN EFCT, ACFT LDG RWY 30L EXPT TO HS TWY *A9 FOR CROSSING TFC, *8150 FT AVBL.",
 "notams": "SAY NO TO KILO",
 "time_stamp": "11/29/2019 8:32:25 PM",
 "vatis_version": "3.1.1.0"
}
 

It is up to you to configure your endpoint to accept and pass the data as you see fit.

Edited by Justin Shannon

Controller (C1), Los Angeles ARTCC
Developer: xPilot, vATIS

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...